I'm trying to use Genymotion Android as my android emulator in conjunction with Oracle's VirtualBox Software on my mac. I created a Nexus 5 4.4.2 virtual device that worked a few days ago, but now every time I run Genymotion, I get the following:
Unable to connect to your virtual device! Genymotion will now stop. Check your VirtualBox network configuration.
For more information refer to: https://cloud.genymotion.com/page/faq/#collapse-nostart
I haven't changed anything in VirtualBox over the last few days, and in fact when I open VirtualBox, it shows the virtual device being run in it's preview frame, but I can't get it to run in Genymotion. Any thoughts??
I faced this problem in Ubuntu , it was solved by re installing Virtual Box DKMS kernel module, a similar solution must exist in Mac also.
Related
I'm trying to debugging (whith Visual Studio) my android app (using ADB) on Virtual Machine created with Hyper-V.
Through this guide (https://bitbucket.org/chabernac/adbportforward/wiki/Home) I was able to show visual studio (installed in the virtual machine) my device (Samsung S8) as a debugging device.
The problem is that when I start debugging from the virtual machine to my device (connected in the same wifi network) I get this error:
Cannot start debugging: Cannot connect to 127.0.0.1:29308:
No connection could be made because the target machine
actively refused it 127.0.0.1:29309
Couldn't connect debugger.
You can see more details in Xamarin Diagnostic output and the full exception on logs.
On Xamarin Diagnostic output can't see anything that can make me understand what the problem could be.
Can you help me? Thanks
I think you must download latest SDK platforms tools Android.
I installed genymotion android emulator on linux Ubuntu 16.04 and download some virtual devices for it. After I start a virtual device, it disappears after 5-10 seconds. I tried some other api's and virtual machines and it's the same.
When I run the virtual device from VirtualBox, it gives me an error just like this picture:
I have the exact same configuration with Genymotion on a newly installed Unbuntu 16.04 box. I came across the this in Genymotion's FAQ section. It appears that this can be caused by incompatible video drivers. I'm running an Nvidia GeForce 210. The stock Unbuntu install selected an X.Org open source video driver. By going to Additional Drivers and selecting the proprietary, tested driver from Nvidia, I was able to correct this problem. I did have to reboot after the changing the driver as well.
I am getting below error:
emulator: ERROR: Unfortunately, there's an incompatibility between
HAXM hypervisor and VirtualBox 4.3.30+ which doesn't allow multiple
hypervisors to co-exist. It is being actively worked on; you can find
out more about the issue at http://b.android.com/197915 (Android) and
https://www.virtualbox.org/ticket/14294 (VirtualBox) Internal error:
initial hax sync failed
While it say work is under going, I can run studio on my collegue's machine with same OS(WIN 7), and same machine specs.
Is there a work around this issue currently ?
I received the follow error:
ERROR: Unfortunately, there's an incompatibility between HAXM
hypervisor and VirtualBox 4.3.30+ which doesn't allow multiple
hypervisors to co-exist. It is being actively worked on; you can find
out more about the issue at http://b.android.com/197915 (Android) and
https://www.virtualbox.org/ticket/14294 (VirtualBox)
To solve this problem I only needed to close Docker on Mac.
I had the same problem. While researching I found out about this https://forums.docker.com/t/cant-using-docker-for-mac-with-android-emulator-haxm/8939/3
Apparently, Docker and Android emulators using HAXM cannot run together. I had Docker running in my system. I stopped it and the emulator was able to run without a problem.
If you have Docker installed and running, stop it and try again.
I was trying to emulate an Ionic 1 app on an Android emulator with ionic emulate android -lcs and encountered the same error:
emulator: ERROR: Unfortunately, there's an incompatibility between HAXM hypervisor and VirtualBox 4.3.30+ which doesn't allow multiple hypervisors to co-exist. It is being actively worked on; you can find out more about the issue at http://b.android.com/197915 (Android) and https://www.virtualbox.org/ticket/14294 (VirtualBox)
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Internal error: initial hax sync failed
I solved it by saving and suspending execution of all other running VMs with the following steps:
1) Quit Docker for Mac by clicking the whale icon in the top bar and selecting "Quit Docker". I believe this is required because the Docker Daemon (server) of Docker for Mac and Docker Toolbox automatically runs in a Linux VM when the Docker Client is running (you do not need to and cannot run it manually with dockerd or docker daemon). The Docker Client is running when the whale icon is in the top bar.
2) Stop all Vagrant VMs running on the host machine by running vagrant halt, as they may be using Virtual Box as the provider. Check their state changes to Powered Off by running vagrant status.
3) Stop all Virtual Box VMs by running virtualbox to open Virtual Box GUI and then Right-click any VMs and select Close > Save State
4) Close and re-open your Terminal window before retrying
I simply stopped running Docker on Mac.
The emulator then was able to run properly.
You likely have two emulators that are trying to use the same resources on the computer i.e. both the Google one and the Genymotion (VirtualBox) one. Who knows how long/if that will be addressed. If you are running Genymotion you use VirtualBox. So, try to run the Oracle VM Virtual Box Manager and check that no virtual machines are running and shut down any that are. You should be able to run emulators in studio again, just make sure you pick one (Genymotion) or the other (Android AVD manager).
There was an update on the thread that Mehmed found It is not necessary to stop Docker. If you have run all the Android Studio updates, you have the Intel installer already downloaded at Users/your_user/Library/Android/sdk/extras/intel/Hardware_Accelerated_Execution_Manager/IntelHAXM_6.1.1.dmg. You need to run the installer yourself.
I had the similar problem and I did the following:
1) Stopped the Docker for mac (Quit)
2) I use 2 monitor (One Mac Screen + Extended another screen), I disconnected the second monitor and it works fine.
In my case (macOS), stop/quit docker does not help. I need to run boot2docker poweroff.
Verify that you don't have more that one Virtual Machine running at the same time.
For Windows Users:
Close all open emulators.
Open Task Manager.
End Process: All instances of adb.exe.
End Process: All processes which has Virtual Box or VBox... in Description.
Restart Emulator.
I've installed the RTM build of VS2015 with the Android Tools. I can launch the emulator manager and see the list of installed images. When I click the green triangle to start an image, it shows a progress bar and the text "Launching emulator..." and XDE opens up with the message "OS is starting"
After a while, XDE shows an error message:
[Window Title]
Visual Studio Emulator for Android
[Content]
The emulator is unable to connect to the device operating system:
Couldn't set up the UDP port.
Some functionality might be disabled.
[Close]
Strangely, when I look in Hyper-V Manager, the image seems to be running perfectly.
I have already removed the GuestDisplayNameProvider line from xdesku.xml, which was previously resulting in the error: "Failed to read from dev/hw_random: No such device" on startup.
So I finally fixed this issue, it's because I had broken virtual ethernet adapters. Here's what I did to fix it.
Remove Hyper-V through by turning off the windows feature.
Reboot
Open device manager and go to network adapters.
Remove all of the Hyper-V Virtual Ethernet Adapters
Enable Hyper-V through by turning the windows feature back on.
Reboot
Try to run your emulator, you should notice that the Virtual Ethernet Adapters are recreated and working.
This occurred after disabling then re-enabling Hyper-V. To fix the problem:
Delete all virtual switches in Hyper-V Manager, delete all virtual machines in Hyper-V Manager, uninstall all profiles in Visual Studio Emulator for Android. Then reboot the machine (just to be sure). Then, open Visual Studio Emulator for Android, download the profile you want, and then click "play". The relevant switches, VMs, etc will all get created fresh now.
Go to "C:\Program Files (x86)\Microsoft XDE\10.0.10586.0\SKUs\Android\" and open xdesku.xml with notepad and remove the following line: GuestDisplayProvider="VsEmulator.OpenGLGuestDisplay.
If your emulator freezes on "OS is starting" but Hyper-V shows "OS" , follow the following link:
https://stackoverflow.com/a/32006888/948236
It works for me.
Add new virtual switch helped me a lot.
I download GenyMotion Android Emulator with Virtual VM pack. Everything worked out well till the Virtual device download process. The virtual device was downloaded successfully but when I try to run the virtual device by hitting the play button, a small window pops-up that says Initializing virtual device and then Starting Virtual device. After a few seconds, it opens up the Virtual Device window but it disappears immediately. I've been trying to get GenyMotion running on my Windows XP PC for the last 3 days. I'm urging to get my hands on GenyMotion Android Emulator. Could anyone please help me?
PS: I've already scanned my PC with Anti-MalwareBytes and Avira Antivirus but the problem still persists.
I had the same problem (or at least the same symptoms). Try to start the VM directly from the Oracle VM Virtualbox (not via the Genymotion GUI). You should find the Virtualbox somewhere like "C:\Program Files\Oracle\VirtualBox\VirtualBox.exe"
When you start the virtual device that way, you get at least a more or less meaningful error message that you can google for solutions. In my case, I had to enable Virtualization in my BIOS and update VirtualBox to the latest version twice. After the first try there was something wrong with the kernel drivers. So I restarted the setup and clicked "Repair" to re-install the VM drivers.
Also don't save the machine state when you close the VM. It's safer to always do a cold boot. As soon as you can start the VM from the Oracle GUI, you should be able to so with Genymotion. Only by starting the VM with Genymotion the virtual device gets connected to ADB and therefore can be used with your IDE.