Visual Studio Android Emulator Will Not Start Fully

Question

I create an empty cordova application in visual studio 2015 and start debugging using Android visual animated emulators (first with lollipop and then with kitkat). XDE starts and OS is starting... displayed on the screen. It lasts so long until it displays

The emulator is unable to connect to the device operating system; The device did not response to the connect request. Some functionalities might be disabled'

After the dialogue closes, he remains there forever until I kill the emulator. Killing an emulator causes an error from the visual studio.

Could not start emulated device 'VS Emulator Lollipop Phone'.

When I open hyper-v, I see vm in the list and appears as working. When I connect, I see the console screen below

Answer 1

I know this problem has existed for a while, but I just found a new solution for people who may still encounter this problem ...

I had the same problem (stuck on "OS Is Starting") for API v 21 and 22. API v23 images started, but could not be debugged - the application will work immediately after a crash.

Bug fixed:

• Turn off emulator
• Open Hyper-V Manager
• Go to Android Image Settings
• Expand the processor configuration node
• Go to the "Compatibility" section of the node
• Check the box "Transfer to a physical computer with a different version of the processor"

Apparently, this is due to the fact that the new processor architectures are incompatible with Android images or something like that - in fact, it doesn't matter if this works :)

Answer 2

I ran into the same problem. I tried disabling OpenGL by deleting: GuestDisplayProvider = "VsEmulator.OpenGLGuestDisplay" in xdesku.xml, as suggested in other answers.

First, the virtual machine will boot (you can connect to it from the Hyper-V manager), but the emulator window itself will not connect to the machine (stuck on the "OS starts", and then after a crash while with the following message: "The emulator cannot connect to the device’s operating system: it was not possible to automatically determine the IP address of the guest system. Some functions may be disabled. ")

This answer is https://stackoverflow.com/a/2126269/ and that overflow.site/questions/92903 / ... helped me solve the connection problem and I was able to display the virtual machine inside the emulator window.

However, the emulator did not work properly (problems with scaling, without the Home, Back buttons, etc.) until I returned the line "VsEmulator.OpenGLGuestDisplay" and after deleting my profiles and rebooting several times.

To summarize, if you encounter the same problem on a computer that supports Hyper-V, you can try using "-version" - the following steps:

• Ideally, uninstall any other Virtualisation software such as VMWare, Virtual Box, and VPN clients such as Cisco VPN (if you cannot do this, please be careful at step 13).
• Reboot
• In the Visual Studio Emulator for Android dialog box, delete all installed device profiles.
• Delete all Hyper-V virtual switches - go to Hyper-V> Virtual Switch Manager> Remove all virtual switches
• Run XdeCleanup.exe (usually in "C: \ Program Files (x86) \ Microsoft XDE \ 10.0.10240.0")
• Also remove all additional virtual network adapters remaining in "Control Panel> Network and Internet> Network Connections" (after the previous steps, as a rule, you should only have physical adapters)
• Make sure network sharing is disabled on all network adapters (right-click, Properties, Split, Disable). Allow other network users to connect through this Internet connection to the computer ")
• If you deleted the GuestDisplayProvider="VsEmulator.OpenGLGuestDisplay" in xdesku.xml (usually in "C: \ Program Files (x86) \ Microsoft XDE \ 10.0.10240.0 \ SKUs \ Android"), NOW IS GOOD TIME TO GO BACK.
• Reboot
• You might want to fix the emulators: go to Programs and Features> Microsoft Visual Studio Emulator for Android> Modify and click "Repair" (although I must say that this always fails for me).
• Reboot
• Open Visual Studio Emulator for Android and install then run one of the profiles (for example: 7 '' KitKat (4.4) XHDPI Tablet - similar to Asus Google Nexus 7)
• It may already be working, but if not, make sure the network adapters are configured correctly. Stop your emulator, then go to Control Panel> Network and Internet> Network Connections and right-click on vEthernet adapters, then Properties and make sure that you only have the following fields marked in the "Network" list: Intervention from another virtualization or network software and drivers : Client for Microsoft Networks, QoS Packet Scheduler, File and Printer Sharing for Microsoft Networks, Microsoft Protocol LLDP Driver, Link-Layer Topology Discovery Mapper I / O Driver, Link-Layer Topological Responder, Internet Protocol Version 6 (TCP / IPv6), Int Internet version 4 (TCP / IPv4)
• Reboot
• Try running the emulator again in "Visual Studio Emulator for Android."
• If it still does not work, try deleting and re-creating profiles and loading reboots ...

There are probably several stages of redundancy here, but I think it covers everything you should try (the key seems to require the correct configuration of network adapters). If I missed some things or if you think some steps are useless, please comment.

Answer 3

After many searches, I got this job. Hope this helps. I found it in the comments on the MSDN article for Android emulator with Visual Studio 2015

New images may work if you disable OpenGL by going to Program Files (or Program Files x86 if you are on a 64-bit machine) \ Microsoft XDE \ 10.0.0.0 \ SKUs \ Android \ xdesku.xml and delete this line: GuestDisplayProvider = "VsEmulator.OpenGLGuestDisplay". However, without enabling OpenGL, you will not be able to take advantage of many new features.

Answer 4

On my system, I started it again after turning off the disabled vEthernet (internal internal internal switch emulator internal Ethernet Ethernet port). I did not have to reboot.

Answer 5

I went through the steps in @Gyum Fox's answer and still haven't been happy for me.

While Visual Studio Emulator for Android creates the first instance of the emulator, several virtual network switches are also being created. For a laptop, usually three instances of vEthernet are created; one for a wired LAN, one for Wi-Fi, and another an internal virtual switch for guest connections.

In my case, vEthernet for the wired LAN was successfully created, and the Visual Studio Emulator for Android process hung up. This can be seen from the Hyper-V Manager and Virtual Switch Manager .

Using Virtual Switch Manager , I successfully created the missing Wi-Fi virtual switch with these steps. Well, in the end it worked. Read on.

• In the Virtual switches list , select New virtual network switch ...
• Under What type of virtual switch do you want to create? , select External .
• In the External network: drop-down list : select a Wi-Fi adapter.
• Click the Create Virtual Switch button.
• Change the Name: to match the name of your Wi-Fi adapter.
• Click the Apply button.

In my case, however, after clicking Apply , an error message indicated that the Wi-Fi adapter was connected. Hmmm.

I launched the View Network Connections applet, and the Wi-Fi adapter did not show that it was connected to the bridge. (When a network bridge exists, the word Bridge is added in the Status column.) I suspect that somewhere in the registry dusty digital bits are hiding.

This is what I understood for me.

• Right-click on the Wi-Fi device.
• Select Add to Bridge .
• Right-click the Wi-Fi device again.
• Select Remove from Bridge .

Now back to the steps to create a virtual switch for a Wi-Fi network. Stages must be completed successfully.

And now you can go back to creating the Android emulators you want.

One final thought ... If you don’t see any virtual switches being created, I suspect that this may mean that the wired LAN can have dusty digital bits hanging you. In this case, Id try using the add-and-remove-from-bridge trick on the wired LAN adapter to make sure this is clear to you.

And now, I believe that it’s simple enough to do the add-and-remove-from-bridge trick on a network adapter without creating a virtual switch. For me, creating a virtual switch was proof that the problem was fixed. YMMV; -)

Answer 6

I found that my problem was with the Windows Firewall with some enterprise policies that my company applied to all computers. As soon as I stopped the Windows Firewall service, it worked fine.

Answer 7

I also had this problem, and it was not only for Android emulators, but for all Windows phone emulators.

This is what I did to fix the problem.

• Uninstall Genymotion and Virtual Box (I had it on my system and this did not solve the problem).
• Removed all virtual adapters. this is the hard part. None of the adapters could be removed from the Hyper-V virtual manager. I had to use powershell and run remove-vmswitch -Name "V-adapter name" -force In addition, I could not remove all adapters from this, and I found this link " https://social.technet.microsoft.com/Forums / windowsserver / en-US / e49df568-4f4c-47b7-b30c-952d1e26ca58 / cant-remove-failed-virtual-switch-from-hypervs-virtual-switch-manager? forum = winserverhyperv "and removed all the virtual adapters
• restart the computer.
• After that, there were no v-adapters in the Hyper-V virtual manager

• Run XdeCleanup.exe (just in case)

• In addition, I turned off the virus protection firewall

After that, I was able to run the emulator from "Visual Studio Emulators for Android"

Answer 8

I am adding a separate answer, although the insight provided by Gyum Fox provided the keys that I need to try other things ...

[NOTE. The last time I could use emulators (~ 3 weeks ago), my wireless disconnected and I used a wired connection on my Dev laptop. I ran out of free space on my switch, so it turned on the wireless network again as the only connection option. It may be completely by accident, but read on and I will let you decide.]

After following the Gyum steps without success, I decided to turn off the wireless network, and then try to start the emulator.

Wouldn't you know that ... it worked without a problem! 8 -}

As soon as I started the emulator, I turned on the wireless network again and the emulator connected to it.

I'm not a network guy, so I'm not even going to try to understand. This is a little PITA, but hey ... if it works !!!; -}

Answer 9

On my machine, I can run the emulator, but when trying to deploy and debug I got an OpenGL error. I realized that my problems started after I installed Docker. On a whim, I decided to close Docker and disconnect the vEthernet network connection (DockerNAT). This fixed my problem. Now that I need to use the Andoird emulator, I have to close Docker. Then, when I finished debugging, I turn on / restart Docker.

Answer 10

One of the reasons I ran into this problem is because I did not install the Android SDK in the default folder. Therefore, I had to follow these instructions in order to be able to debug my application: https://msdn.microsoft.com/en-us/library/mt228282.aspx#ADB

I had to create the "Android SDK Tools" folder and add the "Path" key with a value for my SDK, which in my case was "E: \ Android \ Android_SDK"