I had the emulator running once and had to remove it because I had to work with virtualBox as you cannot run hyper-v and virtual box together.
As I had the emulator running, it means that my system is compatible. I am running windows 10 with i7 processor.
The installation process went smooth but when I tried to create a virtual device the process gets stuck at
Copying .vhd files and creating virtual machine
I tried following the steps shown here Visual studio (2015) emulator for android not working - XDE.exe - Exit Code 3
But It does not work.
what is the way where I can completely remove everything and start from scratch.
Well, if you want to start from scratch, my suggestion would be, make a backup of projects, uninstall VS 15, uninstall emulator, uninstall other plug-in, clear temp, restart, then install again. Quite a long process, which is anyway should not be recommended.
Related
Ok so my Visual Studio Android emulators stopped working this morning. First I was was receiving a networking error and so I tried to delete and re-create them, but the creation keeps getting stuck on "Copy .vhd files and creating virtual machine". The last time I tried it I let it sit on that step for over half an hour, and that was after trying first this Visual studio (2015) emulator for android not working - XDE.exe - Exit Code 3 then this Visual studio android emulator will not start fully
Oh and I completely uninstalled and re-installed Visual Studio Emulator for Android.
Any thoughts would be greatly appreciated.
I finally got a VM to download and execute after reinstalling Hyper-V (un-check Hyper-V from Windows Features, reboot, re-check it, reboot). I've gone through many of the referenced cleanup steps many times prior to trying that, though I did perform a repair of the Visual Studio Emulator for Android and deleted all of the device profiles just before reinstalling Hyper-V.
this is more of a benign bug in android studio. Whenever I wake my computer from sleep or hibernate the connection between the emulator and android studio is not proper and I have to restart the emulator and try again, so as a result of that (I think) all the dead emulators are always shown in the listing when trying to run the app.
And FYI I don't usually restart/shutdown my computer (once in 10 days or so). I was just wondering if there was a way to fix this bug without having to restart the computer.
Screenshot of problem
Thanks in advance!
I am having the same issue using Windows 10 hibernate.
Try terminating the adb.exe process in the task manager. Sometimes you will find two or more adb.exe processes, kill them all. Then close all running emulators (if any) and disconnect all physical devices.
You don't have to restart android studio or eclipse.
After dong this, all unknown/null emulators should be gone (at least in my case).
Did you open multiple android studio and use the terminal in android studio?
you can close all android studio, and restart them. the unknown emulator will be gone
Week ago I created Android vms and I was able to run from Hyper-v window but i wasn't able to run from VS for Android. Yesterday I removed all vms from Hyper-v becouse i had problems with Windows Phone virtual machines. Now I have luckly working Windows Phone machines but I cant make any Android machines becouse every time when I create new machine VS for Android freeze on "Copying .vhd files and creating virtual machine". I tried to reinstall VS Emulator for Android but it doesnt help. What I have to do for fix this?
Same thing happend to me as well, and it very easy to fix this
uninstall visual studio emulator for android
restart your pc/laptop
download and install fresh copy of visual studio emulator for android
let me if this works for you
Feel Free to ask if any error occurs
I have a new machine running Win 8.1 x64, fully patched, with the latest Android SDK and Java JDK. I installed the latest Intel HAXM package as well. Everything fired up and worked great. The emulator would boot in about 30 seconds and each time I'd run an app from Android studio it would start up over there pretty quickly. But then I closed the emulator window (the UI itself showing the virtual phone). After that, I could never get it to come up again unless I rebooted. After a reboot it again works fine the first time, but never again after I close it. I have tried the following:
Running automatically from Android studio as well as launching manually from the command prompt using Intel's recommended options. Same problem either way.
Killing the emulator-x86.exe process, closing Android studio, unloading the Intel HAXM driver and then restarting all of that. No luck.
Running adb kill-server. No luck.
When creating the AVD I tried both the x86 and x86_64 versions, same result either way.
And yes, I have several real devices that work fine to test with. This is just perplexing that everything works perfectly the first time, yet something is hanging around messing up any further launches until a reboot occurs.
Any ideas on what is causing this or how to go about debugging it further?
-JT
It was working fine till I updated the Android SDK tools from the SDK Manager to version 24.1.2. However a virtual device was running at the time of the update and it asked me to close 3 processes in order for the update to continue. I thought the virtual device was interfering so I closed it and tried to proceed with the update,it gave me the same error. Therefore I cancelled the update and closed the studio. After restarting the studio,it gave an error saying the SDK could not be found and would not let me do anything else. I uninstalled the studio after deleting the SDK folder and reinstalled it. I downloaded the system images needed for the virtual devices and some other packages and created a new virtual device. When I tried to run the application,it gave me the dialogue box to chose the virtual device,I chose the newly created one and it gave the command to start the device. Yet no emulator window for the device appeared.
D:\sdk\tools\emulator.exe -netdelay none -netspeed full -avd MTK
emulator: device fd:5500
HAX is working and emulator runs in fast virt mode
HAXM is installed and it worked fine before. On checking the task manager upon launching the application,an emulator-x86.exe process appears briefly before disappearing. Nothing happens after that. Launching the program again gives the same result. If I try to launch the device from the AVD manager,I get the same result. I have tried using the arm images,varying the ram size,snapshot enabled/disabled,use HOST GPU enabled/disabled,system restarted,removal of /.android content,setting up the SDK in a different drive and deleting the ANDROID_SDK_HOME system variable and resetting it.
I have also tried with Genymotion. The virtual device window briefly appears and I can the see the android logo at startup but then it says "player.exe has encountered a problem and needs to close. We are sorry for the inconvenience." I have tried it using both the Genymotion Android SDK tools and the custom Android SDK tools to no avail. If I try to delete the device it says please stop the virtual device before deleting it even though it is not running.
I spent most of my day trying to solve exactly the same problem until one of my colleagues remembered he had exactly the same issue and that was related to Docker.
Docker uses Hypervisor Framework which is incompatible with the HAXM used by the Android emulator. Therefore if you try to run the Android emulator while Docker is running it will just quit without a warning. Quitting Docker will allow to use the simulator - Docker for Mac conflict with Android emulator
Sometimes it is because you are low on memory, or it might be an AVD specific glitch. I had many (20) devices saved in my AVD and was lower than normal on memory on my laptop. The native emulator folder would disappear right away but genymotion worked fine.
I removed the old devices and create a new one from scratch in AVD and the problem disappeared.