Develop Reference

Android Studio 2.0 Cannot launch AVD in emulator

I can successfully launch AVDs for the targets Android 5.1 (Google APIs) and Android 6.0 (Google APIs), both using CPU=x86. However the AVD I create for Android 4.1 (Google APIs) using CPU=arm cannot be launched. When I try to launch it I see a dialog:
Cannot launch AVD in emulator.
Output:
emulator: ERROR: This AVD's configuration is missing a kernel file!!
emulator: ERROR: ANDROID_SDK_ROOT is undefined
Since two AVDs do work I'm sure ANDROID_SDK_ROOT is defined. I've also verified that File -> Project Structure -> SDK Location is correct.
I have also run the Android SDK Manager, uninstalled all API 16 items and reinstalled these API 16 items:
SDK Platform
Intel x86 Atom System Images
ARM EABI v7a System Image
Google APIs
Sources for Android SDK
Within the Android SDK Manager all other libraries and packages are up to date. And I have restarted my Windows 7 computer.
Also note that I am forced to create this API 16 AVD for CPU=arm rather than using CPU=x86 as the Android Virtual Device Manager, when showing available system images, does not show an x86 image for target=Android 4.1 with Google APIs).
Does anyone know what the problem is? Or suggest things I can try to debug this issue?
Edit from a day after opening this question: Since I've seen no answer I'm assuming this is another Android Studio bug. I've input this bug report - https://code.google.com/p/android/issues/detail?id=207494

I got same error while trying to run ARM based emulator which is of API 16. I got this error when ARM images are downloaded from the android-studio itself( Not using Standalone SDK Manager option under System Settings->Android SDK in android-studio).
I solved this by launching Standalone SDK Manager from android studio. Then open Tools->Manage AVDs from Standalone SDK Manager menu. Here you can find your emulators. I observed that my ARM CPU emulator shows question marks in the columns named Platform,API label,CPU/ABI. Which seems to be some sort bug. Select the Emulator and click on edit. Choose the Target API,CPU/ABI properly and then click ok.
Now my emulator works perfectly. This solved my problem.
I figured out that updating android-studio caused this problem for me.

Not able to start AVD in Android studio

I am new to the android world, I am starting Clicking run button to start the AVD but nothing is happening.
If I am clicking Debug option then the AVD i have created does not show in the running device option.
In console this is shown
"C:\Users\shivamkumar07\Desktop\softwares\Android\adt-bundle-windows-x86_64-20140624\ADT Bundle\sdk\tools\emulator.exe" -avd Nexus_S_API_19 -netspeed full -netdelay none"
Here are few screen shots:
The AVD Which I have created:
I have used API 21 Android 5.0 and API 19 Android 4.4.2 but both are not working.
I have also set the target device in the Edit Configuration option, Here is the screen shot:
I am not able to understand how to test my project in the android virtual device? is there some problem with API level or something else? Since I am a beginner I am not familiar with many of the concepts of Android world.
Please help
Thanks in Advance!!

Go to SDK Manager and check at the very bottom if you have installed "Intel X86 Emulator Accelerator (HAXM Installer)". Install it if you don't have it.
Take into account that you'll need to run the downloaded file since it's an installator. If you mouse over the row on SDK Manager you'll be able to see the intallation path.

My issue was that I had to install Android Emulator from the SDK Download manager.

I was also getting the same issue. But Finally I have got the solution. You just need to follow the some steps:-
Goto file option in android studio and click on invalid cache and restart
Then rebuild the project
Then click on one of the option in available devices
Finally you will see to start the AVD automatically
Note :- Behalf of start the AVD from AVD Manager, start it from run.

Why can't I create an AVD for any other targets other than android 2.3.3?

I've been trying to create an AVD 4.0 and I've selected 5.4'' FWVGA as the device.
When I select the target as 2.3.3 the AVD gets created successfully for any device. I've downloaded all the packages as well. When I select the device by default the target comes as 2.3.3.

I guess you havent installed the system image, go toy our SDK Manager and check if you have installed the image of each SDK version.
And check this link :
Error while starting android emulator: FB::flushWindowSurfaceColorBuffer: window handle 0x4 not found

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.