I have recently installed Android Studio and all its updates using sdks manager. When I try to start the emulator i can see this:
emulator -netdelay none -netspeed full -avd Nexus_5_API_21_x86
HAX is working and emulator runs in fast virt mode It seems good. The emulator start but only thing i can see is a black screen. I use the default AVD created by the app. It has google api's x86 system image, 1gb ram, 64mb vm heap and 200mb intel storage. I tried to uncheck "Use Host GPU" but it did not solve the problem.
6,715 9 9 gold badges 55 55 silver badges 104 104 bronze badges asked Jan 9, 2015 at 16:18 351 1 1 gold badge 4 4 silver badges 10 10 bronze badges check answer in stackoverflow.com/questions/27567007/… Commented Jan 9, 2015 at 16:31 Commented Aug 24, 2015 at 20:20I have recently the same issue in emulator, Nexus 5 (Android O). I have go to Android Virtual Device Manager and Wipe User Data and it solved my Problem.
I ran into the same your issue, this is what I did that works: My one starts working with Nexus_4_API_25 (tried even with Nexus 6, Nexus 5 and Nexus One none of them was working!!) Create a new ADV from Android Studio ( bare in mind that i didn't allow the new front and rear camera to the new device, so switch them off) So go to Terminal and go to the folder where your emulator is and lists your emulators, my one:
~/Library/Android/sdk/tools/emulator -list-avds After run your emulator with the gpu hosted on your machine:
~/Library/Android/sdk/tools/emulator -avd Nexus_4_API_25 -gpu host It will start the emulator and then you can run your app in it. Hopefully this can helps someone else.
answered Jul 18, 2017 at 13:47 Alexiscanny Alexiscanny 579 7 7 silver badges 15 15 bronze badgesI ran into this issue, and what solved it for me was unchecking everything that has to do with snapshots.
I assume that my snapshot was corrupt somehow.
Uncheck loading and saving to snapshots.
answered Jan 9, 2015 at 16:37 348 2 2 silver badges 8 8 bronze badges For me isn't this the problem. Loading and saving to snapshots was already unchecked. Commented Jan 11, 2015 at 15:52Same problem for me, I solved it by using x86_64 system image instead of x84, maybe x86 image has some bug on some host system, e.g. Windows 10.
answered Apr 5, 2017 at 9:08 241 3 3 silver badges 6 6 bronze badgesI'm embarrassed to say I lost too much time before I realized I just needed to click the Power Button to wake it up.
answered Nov 9, 2022 at 14:31 TryTryAgain TryTryAgain 7,780 13 13 gold badges 48 48 silver badges 84 84 bronze badgesSame! And with the way my tool window was sized and positioned, the Power button wasn't even visible on the toolbar
Commented Aug 8, 2023 at 11:30 oh my god. I this issue troubled me for hours! What stupid power buttion is it? Commented Oct 31, 2023 at 20:57 You would think it would be on by default like it is in IOS simulator. Thank you Commented Feb 10 at 2:24Faced the same issue, I solved by reducing the AVD version. In the AVD manager choose create a lower version e.g. I was using Nexus 5 and created a Nexus 4 which worked well.
If this solves it means you need to upgrade your machine, RAM etc.
answered Dec 1, 2015 at 14:24 21 1 1 bronze badge Made no difference, still get the black screen. Commented Apr 11, 2018 at 16:13Also look at your skins - some have found it works with the WVGA800 skin. Others here have found it's due to the high RAM requirements of the Nexus 5 AVD itself. I think Nexus 5 takes almost 1600. Try either decreasing the RAM allocation in the AVD ('Advanced settings') - or reinstall HAXM with a higher RAM limit.
answered Jan 9, 2015 at 16:57 1,675 1 1 gold badge 12 12 silver badges 9 9 bronze badgesif you have avast antivirus installed In Avast antivirus under Settings (parametres) tab > Troubleshooting (depannage), you should uncheck "Enable Hardware-assisted Virtualization" ("activer l'assistance a la virtualisation").
Now restart your computer it should work if not re-install the Intel's HAXM which can be found under ~SDK_LOCATION\extras\intel\Hardware_Accelerated_Execution_Manager
answered Jun 24, 2017 at 18:00 Ridha Rezzag Ridha Rezzag 3,910 1 1 gold badge 36 36 silver badges 42 42 bronze badgesI had the same issue that the x86 emulator would hang during startup (black screen, no logo). The answer to my problem had to do with me using Eclipse ADT with an old SDK prior to upgrading to Android Studio on the same computer.
I am running Ubuntu and the configuration files are stored in the .android folder of the home directory, i.e. ~/.android. I saw references to the old SDKs in the config files and deleted the whole folder. After that the x86 emulator started working again.
In hindsight, what gave it away was that when I started using ARM images the emulator worked. I had only used x86 images with qemu in the past.
answered Aug 16, 2015 at 22:33 1,261 12 12 silver badges 11 11 bronze badges
simplest solution of that things is that switching graphics mode it really help you
answered Oct 8, 2021 at 15:23 15 3 3 bronze badgesI have also got same issue but wipe the Android Emulator and relaunched worked but only thing is we need to do again setup for all previous settings
answered Feb 3, 2022 at 20:19Ran into this after running a long overdue upgrade to Android Studio, where existing settings were imported into the upgrade.
Getting all the SDK updates was not enough. The issue was finally resolved after Invalidate-Cache & Restart
