Android emulator shows nothing except black screen and adb devices shows "device offline"

Question

I am just trying to start development in Android. So, the problem is that when I try to launch an emulator by issuing the command emulator @A2, an emulator comes up on the screen. But even after waiting for as long as 2-3 hrs, all it shows is a black screen. Not even the Android home screen or the Android logo. Just a black screen. And while initially "adb devices" shows the emulator as offline.after 2-3 minutes the list of attached devices becomes blank.

I searched all over net and tried all the steps mentioned there like kill and restart adb, install java/android in a directory without spaces, but to no avail.

My Jdk and Android installations are in following folders:

C:\Java32BitInstallation C:\AndroidSdkInstallation Here's the list of stuff I have downloaded/installed for it:

Android SDK Tools, revision 13
Android SDK platforms tools, revision 10
SDK platform Android 4.0.3, API 15, revsion 1
Jdk jdk-7u3-windows-i586

In my path variable, I have added *C:\AndroidSdkInstallation\android-sdk\platform-tools;C:\AndroidSdkInstallation\android-sdk\tools;C:\Java32BitInstallation;C:\Java32BitInstallation\bin*

Also after reading somewhere from net I have added JAVA_HOME variable with its value as C:\Java32BitInstallation\ But still no use.

I have both IntelliJ and Eclipse installed on my system. But since for starting the emulator, I am not using any of these, I don't suspect any foul play with these.

I have been trying for past 10-12 days and have not been able to start the emulator, let alone write my first "Hello world" program.

Additional notes: My system is a Windows 7 (64 bit) machine. Earlier I had installed 64 bit version of jdk, but the problem was present that time too. Now after searching on internet, I uninstalled that and installed 32 bit version of Java. But, again no use. One thing, though, this 32 bit version of Java (jdk 7 update 3), first install jre as part of jdk installation and then installs jre 7. So now I have 2 folders: jre and jre7 in the C:\Java32BitInstallation directory. Could this have to do anything with my emulator not turning up. Do I need to specify additional environment variables or modify the existing one?

BTW, did I mention the logcat shows nothing.

I don't know if you managed to solve this issue. Recently I had the same problem. Try running emulator with `emulator -debug-init -logcat '*:v'`. This might lead you to the root cause. Mine was afailing ServiceManager. It appeared I had removed a few ServiceManager files. — Markus, Aug 08 '12 at 13:43
I encountered a black screen in the middle of running my program on the emulator. Granted your issue sounds like an avd setup issue, i just wanted to let others know that memory leaks can also cause a black screen. My logcat didn't show Garbage collector GC_MESSAGE until I wiped avd, restart logcat, and re-run emulator. Hope this helps someone cause I just spent a good while deleting and re- creating AVDs when it wasn't my problem.. :-/ — cjayem13, Aug 20 '14 at 15:49
Please have a look in below link. It's worked fine for me. http://stackoverflow.com/questions/23509626/android-emulator-shows-nothing-but-blank-screen — Android, Nov 11 '14 at 09:11
@Markus where does the "emulator" command works? Not in platform-tools — Shirish Herwade, Mar 18 '16 at 08:36
What worked for me was just turning my Mac on and off...go figure — FabioR, Jun 18 '19 at 20:50
@FabioR: on mac you can press Command+Option+Escape, select `qemu-system-i386` and **Force Quit**. The equivalent approach should also work on other OS's. — ccpizza, May 05 '20 at 20:40
@ccpizza i tried that, but only by restarting my Mac it worked...maybe it was something hardware related, in any case, thank you — FabioR, May 06 '20 at 19:25
Having the same problem in 2021 with Android Studio 4.2 after a fresh installation and reading this post from 2012 makes me ask basic questions about this software. But I guess since it's from Google it must be good and I have to find the error on my site. — Grimm, Jun 30 '21 at 17:34
I had the "black screen" issue today (recently started using cordova) and using a lower version system image (Android 9 instead of Android 10) solved the issue. — akinuri, Oct 14 '21 at 09:58
I tried wiping data but that not worked for me so i simply created a new emulator and that worked properly for me — Developer, Dec 19 '21 at 05:33

score 140 · Answer 1 · edited Oct 30 '20 at 16:39

140

Update 25.07.2018:

The latest Android Studio version does not have this option anymore. If the problem persists try to switch between the values of the "Emulated Performance" dropdown in the Verify Configuration dialogue (if available) or refer to the Configure Emulator graphics rendering and hardware acceleration.

Update 26.02.2014:

There are two hints in the Configuring Graphics Acceleration chapter from developer.android.com.

Caution: As of SDK Tools Revision 17, the graphics acceleration feature for the emulator is experimental; be alert for incompatibilities and errors when using this feature.

and

Start the AVD Manager and create a new AVD with the Target value of Android 4.0.3 (API Level 15), revision 3 or higher.

So Android 4.0.3 (API Level 15) seems to be the minimum requirement for graphics acceleration.

Original answer

I have had the same issue with the latest Android SDK.

I simply deactivated the checkbox "Use Host GPU" within the settings of the virtual device and it started working again.

The "Use Host GPU" does only work for me with Android 4.2 as "Target".

edited Oct 30 '20 at 16:39

Dorian

7,749
4
38
57

answered Nov 16 '12 at 15:37

jaltek

2,402
1
23
16

3

ok, got it. I had to update some stuff with my SDK manager. Unfortunately, i can't tell you exactly which update was the right one, but I guess it has to do with the processor emulators. – muetzenflo Mar 14 '13 at 19:11
91

For me it's the opposite - I have to turn "HOST GPU" on to make it work. Only problem is that I can't take screenshots in that mode :/ – Elad Avron Oct 29 '13 at 13:04
@EladAvron: Agreed - for me, it only works *with* the host GPU option enabled, too. – O. R. Mapper Dec 15 '13 at 13:59
Then why is the option available for all, not just 4.2 avds? – NoBugs Jan 05 '14 at 09:16
Me too 4.4.2 needed Host GPU on. MacbookAir OSX10.8.5 – albertpeiro Mar 14 '14 at 10:28
3

Host GPU needs to be on for me on Ubuntu 12.04 and android sdk 19 – Johan Bjäreholt Mar 20 '14 at 18:31
I had to turn on "HOST GPU" to make it work, too. This applied both to the ARM ABI and the HAXM Intel Atom emulator. OS X 10.9.5 is my host machine. – Brian Cunnie Sep 28 '14 at 21:16
Make sure you've waited enaugh - especially when the last message is still `Waiting for HOME ('android.process.acore') to be launched...` === meaning Eclipse waits for device's OS to be loaded... sometimes it takes a few MINUTES to lauch... – jave.web Dec 04 '14 at 20:51
Running the emulator in x86 mode, Android 5.0.1 (API 21), 10" tablet. Had to turn "Host GPU" *off*. – David Airapetyan Mar 10 '15 at 06:47
1

Cant find this option - using Android Studio 2.3.3 – Dean P Nov 29 '17 at 14:55
It works for me, I just change the vertical orientation. – Rostan Feb 23 '19 at 22:36
2

Android 4.0.3 emulator works after I have turned on gpu mode in Android Studio 3.4 (Linux, Windows 10). You cannot change the options in the Verify Configuration dialog. It forces turn off gpu mode whatever you have selected in the Emulated Performance. So change config.ini directly. hw.gpu.enabled=yes and hw.gpu.mode=on. The config files is normally in /user folder/.android/avd/emulator name.avd/. – Sungsuh Park Apr 24 '19 at 03:28
Inside Emulator Settings I changed Emulated Performance -> Boot Option -> Cold boot from Quick boot and it started. I tried with Quick Boot again, but it didn't work. – Prashant Oct 14 '19 at 07:26

score 133 · Answer 2 · answered Oct 04 '17 at 09:51

133

I 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.

answered Oct 04 '17 at 09:51

Krunal Kapadiya

2,853
3
16
37

9

Worked for me. Thanks. – Sadda Hussain Jul 26 '19 at 05:37
1

Worked for me in 2020 running on Windows through command line – ViktorMS Mar 01 '20 at 09:20
3

This is the most common solution. Should be the accepted answer. – Dror Bar May 10 '20 at 13:50
1

This also worked for me on Linux with Android Studio 4.1.12. I am puzzled that this happens without any errors registered anywhere. – Jette Feb 02 '21 at 08:18
Thanks a lot dear, it worked like charm :) – Kamlesh Feb 03 '21 at 11:51
This worked for my Android 6.0 (API 23) emulator with the `x86_64` CPU - Thanks! – HelloImKevo Sep 24 '21 at 19:47
Works for me still. – Neo May 04 '23 at 05:43

score 83 · Answer 3 · answered Mar 05 '14 at 22:39

83

I had issues with getting the larger devices to emulate (Nexus7 and 10), while the phone sized emulators worked great. Would just keep getting a black screen with nothing for hours with the tablets. What helped was actually the OPPOSITE of what most people here are recommending: after setting the tick box for 'Use Host GPU' and setting the target to the highest android (4.4.2 at the time of this writing) the 7 and 10 work as expected!

answered Mar 05 '14 at 22:39

ahetman

1,274
11
17

17

This also worked for me. Making sure Use Host GPU was ticked and setting the target to Android 4.4.2. – R Brill May 20 '14 at 12:14
1

Thanks. I ticked option and 4.2.2 started working! I believe what other people mentioned as well. What a bizard java world!! – JQ. Sep 28 '14 at 12:51
With or without the "Use Host GPU" checked, API level 14 wouldn't work for me. API level 17 worked with "Use Host GPU" checked. – vishvAs vAsuki Mar 02 '15 at 00:00
This also worked for me, I'm on a MacBook early 2015 without any discrete graphic card. – Simon Stender Boisen Nov 19 '15 at 15:10
Worked also for me on a MacBookPro10,1 – ocroquette Dec 19 '15 at 11:58

score 66 · Answer 4 · answered Mar 23 '19 at 17:10

66

Have you tried the power button :) ... it really worked for me. Actually emulator saves the device state before closing so at the last run if you switched off the device & closed the emulator then in the next run it will load previous state & display switched off phone aka blank screen. Although there might be many other causes of this issue.

answered Mar 23 '19 at 17:10

panky sharma

2,029
28
45

6

This should be mentioned in the answers above. The first day with Android Studio and I was afraid to click this button, cause I thought it's going to shut down the phone and it cost a lot of time to turn it on again. Yes, a black screen means that the phone switched off and you should wake up it with to power button like in the real device. – kojot Oct 09 '19 at 19:59
1

This saved me so much headache and time, thank you so much. I had accidentally pressed this button when wanting to close the emulator, did not think of it when troubleshooting when it went black next time I ran my app – Meenohara Nov 12 '19 at 05:33
Come to think of it, I think this was actually the problem for me all along. Thanks! – James Mar 14 '21 at 09:05
Thankz for this.Just turn on it by tapping the power button or use (ctrl +p). – Rishal Nov 25 '22 at 08:41
I did in fact try that, figuring that this might be the case, but it didn't help – Kira Resari Dec 19 '22 at 15:44
This saved me lol. Previously turned off my emulator by pressing that button and then i was going crazy over it not starting up haha. Thanks ! – Vikingslord Apr 27 '23 at 04:56

score 39 · Answer 5 · answered Jun 27 '14 at 17:09

39

Checking "Wipe user data" in the Launch Options fixed it for me.

Go to Android Virtual Device Manager->Select your device->Start->Check "Wipe user data"->Launch

answered Jun 27 '14 at 17:09

wizurd

3,541
3
33
50

1

This worked for me on a Mac that runs emulators through team viewer. In Android Studio 2.0, this option appears in the downward arrow next to the edit button -> "Wipe Data" – behelit Apr 12 '16 at 07:13
Works fantastic. If emulator is built from source (android pie aosp_x86_64-userdebug in my case), whenever executing root directory make command, the emulator need to be launched with ```-wipe-data``` argument to make it boot correctly. – yc2986 Jan 13 '19 at 19:37

score 23 · Answer 6 · answered Mar 03 '15 at 18:36

Mac Users: Unfortunately, if you have an older Mac (late 2009 for example) and are using Yosemite, you cannot use HAXM for 64 bit architecture. According to the release notes on HAXM:

HAXM driver does not support emulating a 64 bit system image on Intel systems based on Core microarchitecture (Core, Core2 Duo etc.). All systems based on Nehalem and beyond are supported. (Corei3, Core i5 and Core i7 machines).

I spent a day trying to figure this problem out when I came upon this quote. The only thing that works is to use the non-x86 version of the latest OS (e.g. Lollipop Android 5.0.1 armeabi-v7a) in your AVD

I'm facing this issue , is there any solve !? – Mahmoud Niypoo Dec 25 '22 at 09:17 — Mahmoud Niypoo, Dec 25 '22 at 09:17

score 16 · Answer 7 · answered Jul 10 '20 at 01:01

16

How i solved the issue.. Open AVD manager, CLick on the drop-down arrow:

select >> wipe data after that u can select >> cold boot now..

It worked for me

answered Jul 10 '20 at 01:01

Dayo Jaiye

948
1
10
17

score 9 · Answer 8 · answered Jan 15 '15 at 15:33

9

Here is how i got it solved : I ran the emulator with following command :

sudo /home/code/Android/Sdk/tools/emulator -avd Nexus_S_API_21 -netspeed full -netdelay none -debug-init -logcat '*:v'

and received the following in the output :

NAND: could not write file /tmp/android-code/TMP7.tmp, No space left on device. (similar error, could not reproduce it)

So, i just freed up some disk space from my /home directory in ubuntu (for windows free the C: drive space) and it then booted smoothly.

answered Jan 15 '15 at 15:33

Sunil Kumar

6,112
6
36
40

I used the command: `sudo /home/code/Android/Sdk/tools/emulator -avd Nexus_S_API_21 -netspeed full -netdelay none -debug-init -logcat '*:v' ` to start my AVD and see the log and found that the device can't access laptop camera so I edited the config to disable the camera. After that, all worked fine! – Mo Zaatar Jul 08 '17 at 13:26

score 9 · Answer 9 · edited Jan 07 '19 at 10:35

9

Do factory reset in "Android Device Manager".

In newer versions of Android Studio, this is called "Wipe Data", and it is in the right-click menu for the device in the virtual device manager.

edited Jan 07 '19 at 10:35

Florian Winter

4,750
1
44
69

answered Nov 11 '18 at 08:15

Ali Rasoulian

419
6
12

This worked for me, thank you. In VS 2019, go to Android Device Manager, right click and, "factory reset". I had a black screen emulator and this resolved the problem for me. – Evan Nov 14 '19 at 18:35

score 9 · Answer 10 · answered Jul 15 '19 at 01:49

Also had this issue out of the blue. Android studio was taking up 100% of CPU and in expo I had the following error:

Couldn't start project on Android: Error running adb: This computer is not authorized to debug the device. Please follow the instructions here to enable USB debugging: https://developer.android.com/studio/run/device.html#developer-device-options. If you are using Genymotion go to Settings -> ADB, select "Use custom Android SDK tools", and point it at your Android SDK directory.

Cold boot fixed it for me, like boltup_im_coding's answer. You can also cold boot this way if it's already running (with the black screen).

Stop emulator if it is running, click on "Wipe Data" option displaying in screenshot then restart your emulator will solve your issue 100%. Thanks. — Kamlesh, Feb 03 '21 at 11:54

score 5 · Answer 11 · answered Oct 07 '14 at 13:32

Make sure that you've installed the latest HAXM revision. I had the same blank screen problem with version 1.0.1 while 1.0.8 was already available. The installer can be downloaded via the SDK tools, to actually install the module you would have to execute

android-sdk-directory\extras\intel\Hardware_Accelerated_Execution_Manager\intelhaxm.exe

score 5 · Answer 12 · answered Mar 01 '18 at 05:22

5

I changed it to always "cold boot" to fix my problem. Prior to this, when I ran adb devices it always showed as offline.

answered Mar 01 '18 at 05:22

boltup_im_coding

6,345
6
40
52

1

Cold booting worked for me as well. Did it once, have not had a problem since....However, every once in a while it does happen... – newITguy Aug 17 '18 at 18:19

score 5 · Answer 13 · answered Dec 14 '19 at 09:43

Had this issue on my Nexus 7,Nexus 10 & Pixel as well that means in all the emulators.

After days of struggling with this issue, I figured it out finally. Well, there are a lot of answers above which may work or may not for you because their configuration may vary slightly than yours.

I'll tell you my solution:

When creating those emulators, I checked Hardware - GLES 2.0 in Graphics for better performance. And for me it was the issue.

If you've done the same then,

Go to AVD Manager -> Select your emulator -> Click on Edit configuration (in Actions column marked as pencil) -> in Emulated performance - Graphics -> Select Software - GLES 2.0.

Then click on Show Advanced Settings -> Set none for both Front and Back camera and hit Finish.

Now select your emulator in AVD Manager and click on Dropdown arrow in Actions column -> select Cold Boot Now.

And yay you're ready to go

score 5 · Answer 14 · answered Jun 27 '21 at 16:31

5

Helped for me (windows 10, intel):

Disable Hyper-V in windows
Uninstall HAXM ( "Intel Hardware Accelrated ..." in control panel)
reboot
Install HAXM using android studio (Settings -> Android SDK -> SDK Tools -> Intel x86 Emulator Accelerator (HAXM Installer) -> install)
Run emulator (Also you may try Wipe VD data/Cold boot VD)

answered Jun 27 '21 at 16:31

Dmitrii Matunin

275
4
5

1

Thanks ! works on me. December 2021 – Ryan Aquino Dec 29 '21 at 13:23
1

Thanks! works for me too. March 2022. – kiritoXF Mar 29 '22 at 09:13
I just clicked on Emulator "Round switch" button. and it worked. – garish Jul 27 '22 at 15:09

score 4 · Answer 15 · answered Jun 18 '13 at 07:20

By the sound of it you have a misconfigured device. If you do it will never start and never show anything in Logcat.

I'd recommend creating a new device using one of the default "Device Definitions" available in the AVD Manager. It's as easy as highlighting the device type you want in the "Device Definitions" tab and clicking the "Create AVD..." button, then filling out a few details. I'd start by adjusting "Internal Storage" to around 8GB and (maybe) an "SD Card" of 2GB while leaving everything else the same. Try starting the device and if you see "Android" pop up onscreen you're running. The first boot usually takes awhile so just hang on and watch Logcat for any issues (the "DDMS" perspective helps here).

If you still see a black screen with a default device definition you've got problems elsewhere that are causing the device to fail. Digging through logs may be your only chance if that's the case. You can always try re-downloading the ADT and re-installing the SDKs if nothing else works.

The goal here is to get you up and running with a (very) basic device, so don't shoot for uber impressive specs at this point, just shoot for trying to make it run. Once that happens try adjusting the settings one-by-one until you have it spec'd out the way you like. Just keep in mind that the emulator has its limitations and its no substitute for a real device (Although it works most of the time ;)

Surprised to see a response after almost one year of posting the question. I had tried the steps earlier you mentioned, but that did not help. I upgraded the SDk and it worked. — user1314305, Jun 19 '13 at 16:42

score 3 · Answer 16 · answered Feb 21 '14 at 06:51

3

This is a known bug if you selected "Use host GPU" option while creating AVD. https://code.google.com/p/android/issues/detail?id=28614
Uncheck the option and it should work!

answered Feb 21 '14 at 06:51

Himanshu Likhyani

4,490
1
33
33

score 3 · Answer 17 · answered Jun 12 '14 at 13:45

3

Just try to set CPU/ABI on "Intel Atom (x86)" and deactivate the checkbox "Use Host GPU".

answered Jun 12 '14 at 13:45

Agita

110
2
5

RAHINUR RAHMAN · Answer 18 · 2017-08-27T04:13:55.293

The Problems associated with the Black window of the emulator:

Happens when a new windows is installed. Problem associated with graphics of the windows is on the CD of windows .You have to Update windows and follow the following steps.

If Emulated Performance Graphics is (Software GLES then select it to-->Automatic)

Or If Emulated Performance Graphics is (Automatic then select it to-->Software GLES)

this alternation can solve this problem.

score 3 · Answer 19 · answered Jan 29 '19 at 14:36

3

I was having this issue on my Mac. When you create the device if you change "Graphics" from "Automatic" to "Software" it fixes the issue, or it least it did for me.

answered Jan 29 '19 at 14:36

NineBlindEyes

579
8
18

My emulators showed a black screen when moved to a secondary monitor on Mac. This solved it for me. – Tormod Haugene Jan 12 '21 at 14:03

Sam · Answer 20 · 2019-04-25T05:13:59.803

The following fix worked for me:

Locate the AVD folder in ~/.android/avd
Open config.ini
Replace the following settings with these values:
```
hw.gpu.enabled=yes
hw.gpu.mode=on
```
Save and close the file
Do not open the AVD settings screen within Android Studio or it will revert the above settings
Start the emulator

Thanks to Sunsugh Park for providing the fix.

I have reported this to Google at Black screen starting API 15. Please star the issue to get them to fix it.

Edit

Actually, while the emulator booted ok, it crashed after opening an app. So the emulator team must have disabled hardware graphics for a reason. Unfortunately, it appears to be impossible to get the emulator to work.

score 2 · Answer 21 · edited Jul 30 '18 at 00:01

I had the same problem on API 28, and the fix turned out to be as below;

Enabling Skia rendering for Android UI

When using images for API 27 or later, the emulator can render the Android UI with Skia, which can render more smoothly and efficiently.

To enable Skia rendering, use the following commands in adb shell:

su
setprop debug.hwui.renderer skiagl
stop
start

https://developer.android.com/studio/run/emulator-acceleration#accel-graphics

score 1 · Answer 22 · answered Apr 05 '12 at 04:21

1

I too got the same problem. When i changed the Eclipse from EE to Eclipse Classic it worked fine. in Win professional 64Bit. Have a try it may work for you too..

answered Apr 05 '12 at 04:21

SenthilPrabhu

661
6
29

1

Hi Senthil, Thanks for the reply. I guess its not a question of Eclipse version, bcoz I am not using eclipse to start the emulator. I am using android sdk tools t=for it. – user1314305 Apr 05 '12 at 04:47
1

oh.. Then wait for sometime some one may help you..! I am sorry,,, – SenthilPrabhu Apr 05 '12 at 05:57

score 1 · Answer 23 · edited Apr 29 '21 at 10:39

I've managed to launch and debug an Android testing application on the Android emulator through Delphi.

I have Windows 7 64 bit, 4GB RAM, a dual core processor at 3GHz and Delphi XE 5.

Below is a link that I've prepared in a hurry for my colleagues at work but I will make it better by the first chance:

Debug Android Apps with Delphi

Forgive my English language but I am not a native English speaker. I hope you will find this small tutorial

score 1 · Answer 24 · answered May 16 '14 at 14:50

1

For a workaround try Android 4.0.3 (API 15) with the Intel Atom (x86) image. I could capture DDMS screenshots with both "use host gpu" and HAXM enabled. Only this combination worked for me.

answered May 16 '14 at 14:50

Zsolt Safrany

13,290
6
50
62

score 1 · Answer 25 · answered Dec 17 '14 at 09:41

I also had the same problem. I figured out that the HAXM hardware accelerator was recently updated but not reinstalled since the update manager just updates the installer package which get saved to your hard drive. You will need to remove HAXM and then run that installer package to complete the update. Usualy this gets installed into ANDROID-SDK-ROOT\android-sdk\extras\intel\Hardware_Accelerated_Execution_Manager. Where ANDROID-SDK-ROOT is the location where your android sdk is located.

score 1 · Answer 26 · answered Jun 30 '15 at 21:19

1

For me, I had to turned off both front and back camera. Hope this helps!

answered Jun 30 '15 at 21:19

Jag

75
1
6

Oh thx, in my case i had to choose emulate back or front-camera – stephanfriedrich Oct 23 '15 at 11:00

score 1 · Answer 27 · answered Jan 10 '19 at 12:16

1

I had the same problem. Here's my solution (for Mac OS). I just downgrade the version of the Android Emulator (from 28.0.3 to 27.3.8). Here is a detailed instruction how to do it.

answered Jan 10 '19 at 12:16

Vladyslav Panchenko

1,517
1
19
23

same. nothing solution above help, takes so much time. just downgrade emulator version (my case: from v32.1.14 to v31.3.13) then problem solved. (android 12 API 31 x86_64) step to downgrade emulator: 1. Download manual: https://developer.android.com/studio/emulator_archive 2. Replace .../sdk/emulator 3. done – Syahreza Fauzi Jul 26 '23 at 10:06

score 1 · Answer 28 · answered Feb 01 '19 at 16:58

I use Microsoft's lightning fast Android Emulators utilizing Hyper-V, and I had the same black screen for every Android emulator that I created no matter how I set the GPU Mode (auto, host, mesa, angle, swiftshader, off). Though my situation is apparently different form that of the OP, I thought it might be useful for those using Microsoft Android emulators and coming here after searching "android emulator black screen".

The solution in my case is updating all the Android tools:

   Visual Studio > Tools > Android > Android SDK Manager > Tools

As of today (2019-02-01), Android emulators would have this black screen problem if you have a fresh install of Visual Studio 2017. VS shows notifications automatically for updates of NuGet packages, extension tools, etc., but NOT for Android tool updates. You have to check and update them manually.

score 0 · Answer 29 · answered May 15 '18 at 22:09

I was having this problem after I got the blue screen of death while running my emulator. Here's my solution (for Windows at least). My solution is too completely re-install the AVD. The problem with the normal un-installation process for Android Studio is that it doesn't remove everything, so if your AVD files are corrupted, they will remain corrupted on re-install.

In order to fix this, I deleted two directories:

C:\Users\(My Username)\.Android

and

C:\Users\(My Username)\.AndroidStudio3.1

Then I re-ran in the installer.

I think this is the most foolproof solution if your emulator was previously working because it forces a complete refresh of the AVD component of Android Studio.

score 0 · Answer 30 · answered Oct 01 '18 at 01:58

Another source of error could be the length of the PATH system variable (on Windows systems). Running intel based images with a PATH variable longer than 2047 characters, seems to pass an empty value of this variable to the console / emulator, so it cannot start correctly.

Here is an article describing this behaviour: https://software.intel.com/en-us/articles/limitation-to-the-length-of-the-system-path-variable

I had the same problem. Reducing the total length of this system variable to 1354 chars by removing unused / non-existent paths fixed it for me.

score 0 · Answer 31 · answered May 23 '19 at 05:30

I had the same problem in win10 64bit, too. After a lot of searching, I found this solution.(If you're using an intel system(CPU, GPU, Motherboard, etc.)) Hope it work for you, too.

step 1: Make sure virtualization is enabled on your device:

Reboot your computer and then press F2 for BIOS setup. You should find Virtualization tag and make sure it is marked as enabled. If it's not enabled, no virtual devices can run on your device.

step 2: Install/Update Intel Hardware Accelerated Execution Manager(Intel HAXM) on your device:

This software should be installed or updated for any AVDs to run. You can download the latest version by googling "HAXM". After download, install .exe file and reboot your computer.

score 0 · Answer 32 · answered Jun 15 '20 at 04:52

0

I had faced the same problem.By selecting wipe data worked for me.

answered Jun 15 '20 at 04:52

Vijay Palaskar

526
5
15

score 0 · Answer 33 · answered Nov 16 '20 at 02:44

0

Also faced this issue, tried most answers, none help. Finally, the following actions helped me:

Uninstall HAXM in SDK tools
Reinstall HAXM
Reboot PC
Wipe VD data
Cold boot VD

Not sure if it helps you, just for a reference.

answered Nov 16 '20 at 02:44

MadHatter

301
3
12

Ray Chakrit · Answer 34 · 2022-06-25T12:45:49.170

0

You should look at EventLog under the Emulator. It'll reveal some more detail.

If there is no error message, try Device Manager>Edit>Graphics=software because hardware incompatibility can cause black screen.

Reboot the computer may fix emulator offline problem.

If nothing can help, delete the AVD and recreate it.

edited Jun 25 '22 at 12:45

answered Jun 21 '22 at 14:02

Ray Chakrit

404
5
7

score 0 · Answer 35 · answered Dec 19 '22 at 15:46

0

For me what worked was duplicating the device, then deleting the old device and starting the app for the new one. No configuration changes needed.

answered Dec 19 '22 at 15:46

Kira Resari

1,718
4
19
50

score 0 · Answer 36 · answered Jul 18 '23 at 07:25

0

I disabled my Nvidia graphics card and totally forgot to re-enable it. So, that was the problem, and enabling the graphics card again solved my issue.

answered Jul 18 '23 at 07:25

Chanaka N. Bandara

247
1
3
10

Android emulator shows nothing except black screen and adb devices shows "device offline"

36 Answers36

Edit

Linked