AVD Emulator stuck on loading screen in Android Studio

前端 未结 7 706
攒了一身酷
攒了一身酷 2021-01-01 08:49

I decided to try Android Studio 2.0 having used Eclipse in the past but I\'m having considerable difficulty getting the AVD to load correctly. I\'ve done quite a bit of goog

相关标签:
7条回答
  • 2021-01-01 09:18

    At one point my laptop hit a kernel panic and restarted while running an active AVD emulator session. When attempting to restart the emulator, the emulated device (Pixel 3) stayed stuck on the startup splash logo screen.

    Fix steps:

    1. Stop hung emulator session.

    2. rm ~/.android/avd/name_of_emulated_device.avd/*.lock

    3. rm ~/.android/avd/name_of_emulated_device.avd/*.qcow2

    4. Restarting the emulated AVD should now be successful.

    Windows equivalent for ~/.android should be C:\Users\.android, but I can't confirm this myself.

    Note: You will likely lose any additionally installed apps and current work that was on the AVD.

    0 讨论(0)
  • 2021-01-01 09:27

    You should Increase your ADB emulator Heap to the minimum required.

    in your case: 512M

    into your AVD Manager:

    • Click Edit on your Emulator
    • "Show Advanced Settings" at the bottom
    • Go to: "Memory and Storage"
    • Edit the VM heap value to 512 MB
    • Finished

    Image:

    Works for me.

    0 讨论(0)
  • 2021-01-01 09:29

    Unfortunately, increasing the heap size didn't help in my case. The virtual device was actually running fine before with the previous amount of heap.

    What I eventually ended up doing was just creating a new virtual device through the AVD manager leaving most of the fields the default value. The new device ran fine and booted up as expected and was able to run my app. It's possible something in my first virtual device became corrupted.

    0 讨论(0)
  • 2021-01-01 09:29

    I had the same problem. I'm running El Capitan 10.11.5 with a 2.0GHz Intel Core 2 Duo and 8GB RAM, Android Studio 1.5.1.

    After upgrading to Intel x86 Emulator Accelerator (HAXM Installer), rev 6.1.1 and deleting my API 14 SDK and related files, the newly installed API 23's Google APIs Intel x86 Atom System Image would not get past the Android logo screen.

    After much trial & error, the Intel x86 Atom System Image (not Google APIs Intel x86 Atom System Image) for API 15 finally loaded the home screen on the emulator after ~ 8 min and one android system crash.

    Will try the Intel x86 Atom System Image for API 23 later. Hope that helps.

    0 讨论(0)
  • 2021-01-01 09:33

    I had the same problem and none of the steps listed here helped me, either.

    But since the solution that worked for me was not mentioned here yet, I thought it might help you or one of the others finding this thread:

    What did work for me was disabling certain settings in my Avast Antivirus as proposed by the Android studio troubleshooting page here.

    My version of Avast did not have the setting "Use nested virtualization when available", however just turning off "Enable Hardware assisted virtualization" (note: restart is required for it to take effect) solved the problem just fine.

    So if you are using Avast or another Antivirus which manipulates virtualization, be sure to look through the correspondent settings.

    0 讨论(0)
  • 2021-01-01 09:36

    For me this worked: in AVD(Tools->AVD) click on the small arrow for desired emulator then click on "Wipe data".

    After that, it successfully started - passed the android logo screen - although a bit slowly.

    0 讨论(0)
提交回复
热议问题