Develop Reference

Android Studio 4.0 Emulator Black Screen

Suddenly my Android Emulator stopped working and it shows only black screen. I tried ADB devices with cmd and it says device offline. My Android Stuido version 4.0 . Intel HAXM version 7.5.6 . Android Emulator version 30.0.12 . I also tried this command in cmd --> "emulator -avd Pixel_3a_API_28 -gpu host". then it says " emulator: INFO: QtLogger.cpp:68: Critical: UpdateLayeredWindowIndirect failed for ptDst=(1429, 210), size=(300x21), dirty=(300x21 0, 0) (A device attached to the system is not functioning.) ((null):0, (null)) ". I also tried changing quick boot to cold boot in virtual device verify configuration. Tried changing android system image to lolipop, marshmallow. Tried changing avd device to pixel, nexus, generic devices and tablets. Non of them worked. Is there anyone who can give me a solution for the problem? My device has seperate VGA(GTX 1050ti). Windows version Windows 10 V2004.

The Emulator has a lot of problems since the last update. I got the same problem and I tried to solve it in many ways , and it worked suddenly and stopped working 2 days later.
Until they make it work properly I advise you use Genymotion or a regular phone.

Same problem had happened with me ....In my case the problem was about selection of wrong system image file .I had installed R (Api level 30) x86 for my emulator but it starts giving me problems so instead i installed R(Api Level 30)x86_64 for my emulator and fixed all . Make sure you install x86_64 system image file and give a try

Trying to Emulate KitKat in Android Studio

I am trying to debug an app (with min. API 10) that runs fine on a real device running Nougat (API 24) but the app crashes during specific tasks on a real device running KitKat (API 19).
I use Android Studio.
I want to emulate a device running API 19 to understand what is making the app crash, using the bugger in Android Studio.
I created several new virtual devices in the Android Virtual Device Manager and selected the KitKat system image (API19) (Android 4.4.4) (google APIs), but when I launch the emulator for these devices, the emulator crashes after showing the Android logo. And I cannot reach the home screen.
I have no problem running API25 on emulated Nexus 5 or 6.
Where should I start looking to fix my issue ?
Thanks

Ensure you are using the latest x86 Google APIs system images from the SDK Manager as well as the latest Android Emulator. As of writing this, it should be revision 29 for the API 19 system image (see screen shot):
Revision 29, should work:
To further troubleshoot, you can run the emulator from the command line to see any error output. To to this, run the following commands from your Android SDK location, as indicated in the Android Studio SDK Manager window.
$ ./tools/bin/avdmanager list avd (this will list all AVDs on your machine, identify the API 19 AVD that you want to run and note the "Name:" field.
$ ./emulator/emulator -avd Nexus_5_API_19 (with Nexus_5_API_19 being the name of your AVD on your machine.)
Note any error messages. If you find an error with the emulator, you can file a bug here: https://developer.android.com/studio/report-bugs.html

Android Virtual Device on Virtual Box

ist it possible to run AVD on VirtualBox?
I have Ubuntu 14 installed on it.
I have downloaded new Android Studio but with a bit obsolete tools 25.2.5 what allows to use "android" command.
I have created such AVD:
Available Android Virtual Devices:
Name: AVD1
Device: Nexus 6 (Google)
Target: Android 4.0.3 (API level 15)
Tag/ABI: default/armeabi-v7a
Skin: 1440x2560
When I launch it i can see only black screen and nothing happens.
I heard that it's not possible to run AVD on emulated operation system, but don't know if it's true. Is there any solution to overcome this problem?
And if not, what you would reccoment then? Should I find some online emulator, test on phycial device or maybe install AVD on my host system (Windows), and test on Windows. But i don't know if I can take file generated on Ubuntu and test on Windows??
Thank you in advance!

Android AVD emulator hangs while loading

I seem to have messed up AVD Emulator and need some expert help in solving the problem.
Here are the symptoms:
When I try to open my_avd (my default avd) from AVD Manager, it takes a very long time to load (approx 10 - 20 mins). When loading completes, it just hangs and does not respond to any clicks (unlock mode!).
I try loading my app on this emulator, it is abandoned with:
"emulator-5554 disconnected! Cancelling 'com.app.xyz.xyzactivity activity launch'!"
When trying to launch 'my_avd' from terminal ('...android-sdk-linux/tools $ ./emulator -avd my_avd'), the load time is less, but it abandons with a "Segmentation fault" error in terminal.
I have tried deleting & re-creating my_avd multiple times, but no go.
Have tried increasing the 'Device ram size' to 1024 also, but even that did not help.
Tried the 'Snapshot: Enabled' mode while creating my_avd, but that only worsens the problem.
Have reinstalled eclipse, android sdk, etc.
I am using Eclipse, Android 4.0 (API 14) on Ubuntu 11.x (x64 processor with ia32-libs installed).
Any help/ suggestions will be highly appreciated.
Thanks in advance
Ram

Try another API version. I have this problem with API 14 and 15, but works fine with all the others. If you can't get it to work with, for example, the API 8 or 10 then you got a problem with your AVD emulator. I would suggest you to let the Eclipse choose the device for you (based on the your target version and the devices registered on your AVD Manager). Check the configurations of the device and make sure that they are the same of the real device you're emulating. Here goes the Motorola_spice_key (android 2.3.3) config:
Name : Motorola_spice_key
Device : 2.7'' QVGA(240x320:ldpi)
CPU/ABI : ARM(armeabi)
Target : Android 2.3.3 (Api level 10)
skin : 240x320
snapshot: true
Memory - RAM/VMHeap : 512 / 16
Internal Storage: 200MiB
SD Card : 512Mib
Try this one. If fails, then you might have to reinstall the emulator.

android emulator is start but window show blank screen

WARN/WindowManager(61): No focus window, dropping: KeyEvent{action=0 code=82 repeat=0 meta=0 scancode=229 mFlags=8}

That seams a problem of 1.6
Upgrade to 2.1 and shall disappear.

I was faced with a blank black screen after the emulator was started by Titanium and none of the emulator buttons such as Menu or Home did anything.
To fix it I entered the following commands from the sdk / tools directory:
android list avd
This listed the emulator images. In my case it listed two:
Available Android Virtual Devices:
Name: titanium_3_WVGA854
Path: C:\Users\xxx\.android\avd\titanium_3_WVGA854.avd
Target: Android 1.6 (API level 4)
Skin: WVGA854
Sdcard: C:\Users\xxx\.titanium\android.sdcard
---------
Name: titanium_8_WVGA854
Path: C:\Users\xxx\.android\avd\titanium_8_WVGA854.avd
Target: Google APIs (Google Inc.)
Based on Android 2.2 (API level 8)
Skin: WVGA854
Sdcard: C:\Users\xxx\.titanium\android.sdcard
In my case I wanted the Android 2.2 API so I entered
emulator #titanium_8_wvga854

its only a problem of computer memory, sometimes when we build again and again by eclipse or other IDE, it consumes memory (don't know why maybe because of leaks) and it memory is user 90% , so that sometimes it creates problem for emulator launching and takes a lot of time to get launched.

windows xp
Running Android emulator version 10.0 (build_id OPENMASTER-104271)
Kill the emulator which cause a dumprep.exe which I killed too.
You just need to resave the AVD configuration. Perhaps something got corrupted
In eclipse > Android SDK and AVD Manager, select your AVD Name and click Edit ...
Click Edit AVD ( resaves your settings )
select your AVD Name and Click Start...

Disabling Host GPU in the settings for the AVD worked for me. This was a problem for me with 2.3, but not 5.0.