Fix for the Android Emulator (Android Simulator) crashing during launch

8 Comments on Fix for the Android Emulator (Android Simulator) crashing during launch

UPDATE 2017.08.03: This should be fixed with the release of HAXM 6.1.1. Make sure you’re running the latest version of Android Studio

On a recent project I was working on, I wasn’t able to start the Android Emulator/Simulator anymore from within Android Studio. Every time I launched it from Android Studio it would start, but then – without any errors or warnings – close all by itself.

When I switched to launching the Android Emulator from the Command Line instead, I finally got to see an error message:

$ cd $(dirname $(which emulator)) && ./emulator -avd Nexus_5X_API_25
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x60000000
HAX is working and emulator runs in fast virt mode.
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync HAX vcpu contextInternal error: Initial hax sync failed

Aha, a clue! One Google Search Coupon later it turns out the thing preventing the emulator from running was that other thing using vcpu’s, namely docker.

👉 Killing docker will let you run the Android Emulator without any problems.

I haven’t tested other suggested solutions (such as tweaking the settings of the virtual device), but at least this one did it for me.

Did this help you out? Like what you see?
Consider donating.

I don’t run ads on my blog nor do I do this for profit. A donation however would always put a smile on my face though. Thanks!

☕️ Buy me a Coffee ($3)

Published by Bramus!

Bramus is a frontend web developer from Belgium, working as a Chrome Developer Relations Engineer at Google. From the moment he discovered view-source at the age of 14 (way back in 1997), he fell in love with the web and has been tinkering with it ever since (more …)

Unless noted otherwise, the contents of this post are licensed under the Creative Commons Attribution 4.0 License and code samples are licensed under the MIT License

Join the Conversation

8 Comments

  1. Thank you! Suddenly today my Android emulator refused to start (and of course I need to get a few things done urgently), turned out that docker was the culprit (a recent update resulted in it being enabled).

    Reply

  2. Hi, for me was VBox, just for those who come into this issue and not having Docker running. Nevertheless, it lead me to look for VBox which I knew I had running.

    Reply

  3. But what can I do if I’m actually running docker containers as part of my app setup? Any ideas

    Reply

  4. I found this useful (source https://forums.docker.com/t/cant-using-docker-for-mac-with-android-emulator-haxm/8939/11):

    Considering the bug fixed: HAXM 6.1.1 (available as a part of Android Studio or on Intel website at https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager ) is designed to coexist with Docker/VirtualBox/HVF hypervisors on Mac OS

    Important note, taken on Intel’s website:

    The SDK Manager will download the installer to the “extras” directory, under the main SDK directory. Even though the SDK manager says “Installed” it actually means that the Intel HAXM executable was downloaded. You will still need to run the installer from the “extras” directory to finish installation.

    Reply
    1. Reply
  5. Pingback: android - Emulador de Android Dispositivo de bloqueo cuando inicio en Android Studio (Linux)
  6. Pingback: android - Émulateur Android Appareil crash dès le début de la dans Android Studio (Linux)

  7. Hi there,
    I’ve been struggling with this issue for the past few weeks and would appreciate some help. How can I kill docker in Windows 10?

    Reply

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.