I updated some android studio components 2 days ago and everything messed up. Now I cant use android emulator since it exits immediately the moment it gets lunched.
I already tried the following:
- Delete all my virtual devices and created new ones – didn’t work.
- Wipe Emulator data – didn’t work.
- Tried to lunch emulator manually in AVD – didn’t work
- Launch emulator with the option Cold boot now. – Emulator displayed this message Cold boot: requested by the user and exit.
- Uninstall Android Studio and deleted whole SDK folder and downloaded everything new – didn’t work may be bacause the problem is within latest release.
- Tried to downgrade Emulator manually! I asked it here – I downloaded the previous release and deleted everything in sdk\emulator and put files there, Deleted all virtual devices and create new ones. Pressed run. this message pops up when emulator start Cold boot different AVD Configuration and then it exits again. This is may be I didn’t downgrade all emulator related tools, I don’t know how!. And sometimes different message pops up saying Resetting for cold boot: emulation engine failed and exits.
None of these worked and I am out of ideas.
Here are logs get printed before emulator flash disappearance.
16:00 Emulator: C:\Users\Nux\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: error while loading state for instance 0x0 of device ‘goldfish_pipe’
16:00 Emulator: deleteSnapshot: for default_boot
16:00 Emulator: qemu: unsupported keyboard cmd=0x84
16:00 Emulator: Process finished with exit code 0
Several issues have been submitted already:
This issue has been fixed in HAXM 7.4.1, So just make sure you are using latest HAXM. Check latest version here
Temporary solution to this problem is to decrease number of cpu.ncore from 4 to either 1 or 2.
Go to avd and find your virtual device and inside edit config.ini then change ncore=4 to ncore=2
Path to config.ini for my virtual device is
You can also go to this path from AVD manager. Click drop down of device of your choice and click show on disk
It worked for me. source https://issuetracker.google.com/issues/132481542
Caution: Emulator may be slow.
Hope this problem is fixed in next update.
I’m getting the same thing, but I’m unable to consistently produce the error.
When I get the error I perform the following steps:
Close the emulator if it somehow opened with that error message (that’s happened to me)
Wipe the drive
Start the emulator from AVD
Once the emulator is up, I hit run and select the running emulator.
THIS is not a fix for whatever the hell is going on with our ‘goldfish_pipe’, but it is something that I’ve been able to do to work around it. It’s the equivalent of – spinning 3 times, gargling water and saying a prayer backwards. >.<
That being the case, I’m following this thread for any solutions. If I discover anything new I’ll post it, but if anyone can reproduce this error please let me know how.
i just lowered the RAM to < 768MB, worked for me
Try below steps
- Disable any anti-virus software you are using.
- Restart Android studio
- Create a new virtual device or Wipe data if you have an existing one
- Start virtual device with “Cold Boot Now”
If the above steps work then add below exceptions to your anti virus software
- C:\Program Files\Android\*
It seems the windows update is the culprit. The only solution I found is to signUp for windows insider and get the latest release under “fast” option in windows 10. I am running build 18941.rs_prerelease.190713-1700 and the emulator is working now. Hope this helps until this version of windows goes to production.
Issue solved. I have reinstalled Win10 Home Edition and all other software including Android Studio and Emulators.
@Nux, I hope that helps.
I added Android Studio related folders to exclusion of Avast and that fixed the problem.
Avast and some certain anti-virus programs pick adb.exe as malware.
Edit: Turns out it’s not the above mentioned problem, I’m facing the issue of the emulator crashing randomly yet again. Sometimes it boots up fine, most of the time it doesn’t.
I recently got this exact same issue and tried all the possible solution, i had a minor windows update that was paused since 7 days back, and what i did was to simply install it and the emulator started to work again.