Develop Reference

AVD not starting (no error message)

I know that this was running on my system half a year ago, so I don't know what else to do.
I deleted every Android-related cofig-folders in my home directory. The newly generated config files are located in my home directory as well.
I'm starting Android Studio with an empty project (just created it new), click on "AVD Manager", install a Nexus6 with Nougat x86 (API Level 25) and then I'm hitting the "Launch this AVD in the emulator"-button.
At the bottom of Android-Studio a progress bar appears along with "Starting AVD...", but as the progress bar hits 100% nothing else happens.
No error message, no process being started, simply nothing happens after hitting that button.
I installed the package from the AUR https://aur.archlinux.org/packages/android-studio. I'm using LXDE as the DE.

Looks like android studio needed to install emulator when it was updated...
I got this problem after updating android studio and it was solved by the installing the emulator from SDK manager

After the last update my emulator stopped working without throwing any error. I had to edit my .bashrc to set it to use the system libraries.
Open your .bashrc file by typing the following commands on terminal:
cd ~/
gedit .bashrc
Add this line to the end of the fine:
export ANDROID_EMULATOR_USE_SYSTEM_LIBS=1
Restart the computer.
Edit: Instead of restarting you can also run source ~/.bashrc

Android emulator was not updated in my Android Studio. I went to SDK manager and installed the updated version from tools tab and then it started working.

I went to Tools > Android > AVD Manager
I then edited the desired device [galaxy_note_4] in my case, Selected Software - GLES 2.0, under Emulated Performance.
Worked for me, hope this helps

I went to AVD manager and cleared out my existing devices and just created a new one. Seemed to do the trick for me.

Just delete your avd and try to create a new one then you can see the error logs in idea.log.
In my case it couldn't find userdata.img for some reasons.

For me what worked was:
Select all x86 images in the respective phone model. Go to "show package details" in Android Studio within the "SDK" under the selected models and enusre the x86 image options are selected for the respective chosen model.
Also make sure no other applications are open at the backend not even the browser. Because even that is leading to hang may be due to the configuration of the system that I have.

In my case updating Intel Hardware Accelerated Execution Manager (HAXM) did the trick.
You can do it in SDK Manager under the SDK Tools tab

android studio - emulator doesn't work and genymotion doesn't get recognized

I'm building an app in Android Studio (beta) 0.8.9, though I can't seem to get emulators running. I've made a Nexus 4 and 5 emulator through the options, but I can't seem to get them started. It shows this in the Run App tab.
Waiting for device.
"C:\Program Files (x86)\Android\android-studio\sdk\tools\emulator.exe" -avd smallEmulator -netspeed full -netdelay none
So either it's not starting up, or I'm just an impatient SOB.
I've also downloaded Genymotion and started up an emulator through that, but now Android Studio doesn't recognize the emulator anymore. I try to run my app and check for any running devices, but it doesn't show up, despite the fact that it actually is running.
I've added the Genymotion plug-in, to no avail. No idea what went wrong.
I also have a One Plus One, which I'm not sure how I can debug on that. They don't seem to have drivers for that and haven't immediatly found anything on Google so far.
Any help would be much appreciated.
EDIT: I fixed my problem. I used Genymotion to fix the problem. The running emulator wasn't turning up, because the android SDK's weren't linked to one another. Genymotion and Android Studio used different ones. So I edited Genymotion's settings to use the same one of AS and now it works!

First of all, update android studio. Check if the emulators run from the AVD manager outside Android Studio, I mean by starting it up manually from ur SDK installation folder (AVD Manager.exe) . Check the path of ur emulator in .ini file in C:>Users>user-name >.android>avd. U can make a system variable for ur SDK folder "ANDROID_SDK_HOME" and place the .android folder's content there (the whole .android folder). Sometimes "resetting the adb" after u run emulator may work.

There may be an easier fix than what was previously mentioned. Try opening Android Studio, go to File, Settings, plugins. Select the “Browse Repositories” button at the bottom of the page. Scroll down the displayed page to find “Genymotion”; select it and install it.
When it has installed, restart Android Studio. Again, go to File, Settings, then go to Other Settings. Genymotion should show up as an option. There will be a field that asks for the path to the Genymotion folder.
Mine was: C:\Program Files\Genymobile\Genymotion. At any rate, enter the path, click Apply or OK and Android Studio should recognize Genymotion (You may need to restart AS once again). Now you should have a small red icon on Android Studios tool bar; when you hover over it a pop up that identifies it as “Genymotion Device Manager”. Click on it, select a device to load, click start and allow the virtual device to start completely. Now run your Android Studio project; the Android Studio “Device Chooser” will pop up. You should see the Genymotion device you’d started previously, select it and you’re good.
Hope this helps…

new AVD can't click on OK button, not system image [duplicate]

This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)

THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems

To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.

1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device

Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins

INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...

I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6

I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.

Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.

Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.

i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing

I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.

Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)

For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed

Give some value for your sd card. May be something like 100 or 200

Android emulator error: "System UI has stopped"

I have recently set up my Android development environment. Every thing is alright but when I run my emulator it takes to much time with an error dialog on the emulator screen says- "Unfortunately, System UI has stopped" and no application runs on it.
I have recently shifted to 64bit windows7 and using JDK7 and eclipse juno for 64bit.
My emulator configuration is given below:
can anyone suggest me what is wrong with it?

This is still "unanswered", but it probably has been resolved.
I just want to share my experience and clarify a few things, some of which may not matter. Anyway, if this helps someone else that's great.
I had this problem on one machine (a new, but slower machine), but not another (the faster one) when running a 4.0.3 emulator. It is not a hardware problem though, and CPU speed doesn't make a difference.
Both machines are fully up-to-date ADT (Eclipse 4.2.x and Android 4.2.2 (API 17) SDK environments.
Editing, or even Deleting the emulator and then recreating it did NOT fix it.
The best solution is to locate and update the config.ini file. In Windows 7 (x64) I found the config.ini file in %USERPROFILE%\.android\avd. It was located in a folder ICS_4.0.3_API_15.avd [*see AVD names below].
NOTE: First make sure you have “show hidden files, folder, or drives” turned on in Explorer or you won't see the ".android" folder.
Not sure it matters, but my entry said hw.mainKeys=no, not hw.mainKeys=false as some have suggested. Changing it to hw.mainKeys=yes seems to have fixed the problem.
AVD Names - Your AVD name will be different from mine. I just add the Release name/API level in the name so I can quickly scan the list and go to a release, such as Honeycomb, Ice Cream Sandwich, Jelly Bean, etc. (e.g., ICS_4.0.3_API_15.avd)
There's more information in another thread at < Unfortunately System UI has stopped >. It starts by asking a seemingly tangential question, but gets to the same place.

This issues has happened to me a few times, and has always been resolved by cold booting the emulator.
On OS X:
Open Android Studio. Navigate to Configure > AVD Manager.
Under Actions > dropdown triangle on the right > Cold Boot Now:
Here is a photo of what the menu looks like
I'm not sure what this looks like on Windows, maybe someone can confirm that it is similar?

What seems to have worked for me and others is to change the hw.mainKeys setting in your config.ini to true:
hw.mainKeys=true

Close avd and eclipse then Delete .android file created in your user folder then try to create a new emulator this help me most of the time.It may helps you

My case. Android SDK was placed here D:\android-sdk\ for a nearly year ago. After one of recently SDK updates I'v got "Unfortunately, System UI has stopped". I'v created number of divices with different RAM amount, VM heap size, screen size, API level(problem seems to be only on API14+), etc. At finish i noticed that new devices was created at the location C:\users\XuserX\.android\avd
After reading this post solution was simple: create ANDROID_SDK and ANDROID_SDK_HOME system variables with value d:\android-sdk\
Hope this post helps somebody.

just switch off and on hte button in emulator ... it can remove that problem

This is also happening if your device definition name has " character in the name, like Kindle Fire HD 7".
Once I removed the apostrophe symbol, error was gone.

In Android Studio Tools -> AVD manager -> Actions -> dropdown▾-> Wipe Data

Go AVD Manager and just click "Wipe Data" for your emulator in Android Studio.

It might be a little late, but I used to face this problem every time I started my AVD. Also the cold boot option was just a temporary fix for me.
I checked the android version that I had installed on my emulator, and noticed the ABI version was x86.
I downloaded the X86_64 version and I have not faced that annoying error anymore.

AVD manager won't start anylonger in Eclipse

When I press the AVD Manager button in Eclipse, nothing happens (and I mean nothing) ...
When I try to run an app, I get the message "No compatible targets were found. Do you wish to add a new Android Virtual Device? When I click "Yes", I get the "Android Device Chooser" Window. This is completely empty (no devises listed). So I check the radio button "launch new Android Virtual Device", which activates the "Manager" button. But when I click this button, again nothing happens ...
So, for some reason my AVD Manager won't start up.
PS: The AVD Manager did work before, when I was going through the "Hello World" exercise. For some reason it stopped working. I tried reinstalling the whole SDK and Eclipse thing, to no avail. I work with Windows 7.
Any suggestions?

i had the same problem. so i uninstalled the sdk (C:\Program Files (x86)\Android\android-sdk) and deleted the C:\Users\hp.android folder (make sure to delete this folder else the problem will exist even after reinstallation). upon reinstallation everything worked perfectly...

Try to install or reinstall the AVD system image in Android SDK Manager in Eclipse.

You might have not set the sdk path. to do so,
step1: go to windows menu option
step2: click on preference,
step3: select android
step 4: change the android sdk path and restart eclipse