10
votes

After updating AS now emulator quits every time I start it. Below is the screenshot I managed to capture before it disappeared. enter image description here

In the logs the following are printed

14:49 Emulator: WARNING: change of renderer detected.

14:49 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'

14:49 Emulator: deleteSnapshot: for default_boot

14:49 Emulator: qemu: unsupported keyboard cmd=0x84

14:49 Emulator: qemu: unsupported keyboard cmd=0x84

14:49 Emulator: Process finished with exit code 0

I already tried the following:

  1. Delete all my virtual devices and created new ones.
  2. Wipe Emulator data.
  3. Tried to lunch emulator manually in AVD.
  4. Launch emulator with the option "Cold boot now".

And none of them worked. Any help will be appreciated!

10
Any news on this? - Sampgun
@Sampgun I have not fixed it yet! - Nux
Ok I have something...I deleted everything and simply downloaded the Android Studio executable. Run everything and now it works. - Sampgun
Anyway sometimes it fails to run with the same error. - Sampgun
@Sampgun I did the same thing. Uninstalled everything and Downloaded new AS. but It the error still persists. got tired and I use my phone right now - Nux

10 Answers

7
votes

I had the same problem. What worked for me:

  1. Editing the AVD configuration and on Graphics I selected "Software".
  2. Lower uncheck "Device Frame".(without this step it was keeping crashing).
  3. Wipe data
  4. Cold boot.

And now it works fine. Hope my advice will help to anyone.

15
votes

I had the same problem and this worked for me.

enter image description here

6
votes

I solved this problem. If riot games are installed on your computer, stop Riot Vanguard and try again. enter image description here

2
votes

I found a blog post which allowed me to fix the problem. Follow these steps:

  1. In Tools > SDK Manager, make sure HAXM is installed and up-to-date. You can also manually install it from Github and restart Android Studio. enter image description here

  2. Open environment variables and add a new variable ANDROID_SDK_HOME, set the value to C:\Users\<yourUserNameHere>\AppData\Local\Android\Sdk enter image description here

  3. Go to C:\Users\<yourUserNameHere>\.android and copy the avd folder to C:\Users\<yourUserNameHere>\AppData\Local\Android\Sdk enter image description here

  4. Now open Android Studio and try again.

1
votes

I experienced the same issue when updating Android Studio to version 3.4.

What worked for me was editing the AVD configuration and on Graphics I selected "Software -GLES 1.0". This made my emulator successfully boot up again.

Then I just went back to the Graphics configuration and selected "Hardware - GLES 2.0" again, which made my emulator go back to its usual performance.

Hope that helps!

0
votes

In the Android virtual Manager -> Actions -> arrow down -> Cold Boot Now. And ready.

enter image description here

0
votes

I recently experienced this problem.

I updated my windows 10 1904 to 2004, this solved my problem

0
votes

If you use Windows10. Update your windows 10 1904 to 2004, this way I solved my problem

0
votes

if your using visual studio to run your emulator . 1-restart your pc. 2-run your emulator from android studio first. this solved my problem.

0
votes

I was trying to create an emulator for Android 10 (the one for Android 9.0 worked fine) but I also got the error:

Resetting for cold boot: emulation engine failed

After some digging on the World Wide Web I found that I did not have the Android SDK 10.0 (Q) installed.

Steps (from Android Studio):

Step 1: Open SDK Manager (Tools -> SDK Manager)

Step 2: Choose your missing Android SDK and click Apply enter image description here

Step 3: Wipe the data from existing virtual device (Tools -> AVD Manager -> Right-click on virtual device -> Wipe Data)

After the installation I right-clicked on my already existing virtual device and choose Wipe Data. I'm not sure it this is necessary though. Note that the same error - Resetting for cold boot: emulation engine failed - appeared but then it booted up correctly. enter image description here