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

PANIC: Missing emulator engine program for 'arm' CPUS

I am getting the same issue as mentioned in below link.But this one has been put on hold and I am still seeking for a solution.
https://stackoverflow.com/questions/27146511/panic-missing-emulator-engine-program-for-arm-cpus-eclipse
So I would like to frame the question and ask here. Until yesterday, emulator were working fine. But since today I am receiving the following error while I am trying to open emulator
PANIC: Missing emulator engine program for 'arm' CPUS
My AVD:
This is the error I am receiving:
I have updated and installed components through SDK Manager and I even tried to restart eclipse and my pc as well.
I tried creating new AVD But nothing worked here.
Thank You in advance.

In my case, my PATH environment variable was set incorrectly. It was including
<sdk-path>/sdk/tools
Instead of
<sdk-path>/sdk/emulator
emulator.exe exists in both of these directories, so the emulator command will work either way. However, emulator-arm.exe only exists in my emulator directory.

It is related to Avast Antivirus, has found bunch of emulator-arm files in its quarantine. Problem started couple of hours ago.
What I did as temporary solution: restored emulator-arm from quarantine, added it to avast exception, paused Avast, run AVD, then resumed Avast

This error happened to me when I re-formatted my computer and tried to copy and paste my old SDK files into my newly formatted computer.
I needed to re-download the SDK’s API stuff. For example, when I re-download API 19, it added these files in red and my Emulator for API 19 worked. API 18 & 17 kept giving me the "PANIC: Missing emulator engine program for 'arm' CPUS." error message. API 18 & 17 were the files I copied and pasted in.
Just delete everything and re-install it. Especially the Tools folder.

I had the same error but I solved it differently from the others. I was trying to create an emulator to test on an older Android version on my Mac.
My mistake was I had selected the wrong tab (see screenshot). I should have clicked the "x86 Images" tab instead of the "Other Images" tab to avoid this error:
Emulator: PANIC: Missing emulator engine program for 'arm' CPU.

This error indicates that there are some missing components in the Android SDK Tools!
In my case, for some reason, Avast Antivirus recognizes the tools/emulator-arm.exe as a threat and puts it in the virus chest!
This started happening since I've updated the SDK manager and everything to latest (tools 23.0.5)
Once I've restored the emulator-arm.exe file and disabled Avast for 10 minutes, I was able to start the emulator without problems!
Note: I've tried to add the file as exception to the Avast AV but it still removes the file from my system.
Please check if your SDK Tools installation is complete and update (delete first?) everything, or at least the Tools section in the SDK Manager!
I hope that helps!

I got the same error a few minutes ago. Look into antivirus chest and try to check if emulator-arm.exe is there. Try add the file to exception of antivirus.
It is working for me. (I have got avast!). Hope this will help you

I had the same problem in the same time as you guys and I am also using Avast. But I could not find the file in the chest of Avast.
So what worked for me was to reinstall the Tools of Android SDK:
Open Android SDK Manager
Select Android SDK Tools
Click "Delete 1 package"
Once it is done, reselect Adroid SDK Tools and click "Install 1 package".
Hope it helps.

I know this is a crazy old topic, but I ran into this same problem and had a hard time solving it. This topic kept popping up on all the searches
The quick work around is to simply copy everything from
/sdk/tools To /sdk/emulator without overwriting anything.
My path looks like this
C:\Users\MyProfile\AppData\Local\Android\sdk\tools

I got the same error too this morning... and I've got Avast !
"Restore and add to exclusion" seems not to work in this case, so i manually added the exclusion...
Solution:
1- Go to Avast Control Panel > Scan > Quarantine > Right Click on "emulator-arm.exe" > Restore and add to exclusion...
2- From Avast Main Screen > Parameters > Active protection (2nd item) > File Agent (click on the wheel) > Exclusions (4th item on the left menu) > Add the complete file path of emulator-arm.exe at the bottom of the list.
Then it works for me...

Avast Antivirus is sensing emulator-arm.exe as a thread and blocking from some reasons. When you add it exclusions in Virus Chest page with right-click -> "restore and add to exclusions" it's not solved in future runnings. To solve this permanently in Avast 2015 :
Settings ->
Active Protection ->
File System Shield ->
Customize ->
Exclusions then add thread as a exclusion . And then press ok.

in my case,there was missing arm eabi v7a system image for api level 22. After downloading it started to work. so make sure that Your arm eabi v7a system image is installed for the particular API Level

If you are trying to use an Android Virtual Device (AVD) with an Android Version, whose SDK platform version you have not installed, this error also appears.
Download all the Android SDK versions whose AVD you might use, i.e., be sure you have the API level installed whose AVD you will use.
Furthermore, check the first line the next image in the column CPU (this was also giving an error). Change the CPU of your AVD, to x86 and then it will work.

There can be the bugs / updates happened in the OS. So, instead of updating in .profile, /etc/environment, or .bashrc file to point adb, emulator etc, put (copy and paste) all the emulator folder inside /usr/bin directory. Install adb tool from the terminal. This should solve everything.
And/Or, update your all environment variables in /etc/bash.bashrc file. Note that: /etc/bash.bashrc file is what gets executed everytime you open the bash terminal.

Will SDK Manager suppport for windows-8

Will SDK Manager support for windows-8. I installed the android sdk for Windows 8.
But when I open the android sdk manager, a cmd-like screen just briefly flashes on for half a second then disappears. I have no idea what's going on and how to get this thing working.

I am facing same problem on Windows 8.1.
I saw following solution on internet:
Open /sdk/tools/android.bat file.
and
change
“set java_exe=” line to
set java_exe="C:\Program Files\Java\jre7\bin\java.exe"
Note:
The java.exe path could be different on your system.
But it didn't work in my case, try it on your side.
One thing strange is that if we run "/sdk/tools/android.bat" directly it works, but it does not run through "SDK Manager.exe" file.
Any other person facing same problem and got any solution?

Will SDK Manager support for windows-8
Yes, it works perfectly in Windows 8 also.
Follow below steps which worked for me :-
Go to (sdk-folder)/tools folder (For me it is C:\Users\Ajay\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools)
Open the file android.bat in any text editor.
Go to the line where set java_exe is located
Set the Path of java.exe which is located in your JRE. For ex : set java_exe="C:\Program Files\Java\jre7\bin\java.exe"
Save the file and try it again, now it should work !

Match your Machin's Java bit system with your android SDK bit system, i.e install a JDK x86 if you got android SDK x86. And usually android SDK works fine with Java x86 versions.

"No system images installed for this target" even though Image is installed

So I'm trying to create an AVD Simulator, and I keep getting the "No system images installed for this target" error when trying to create a 4.2.2 system even though the image is installed (See picture of SDK Manager).
My system is x64, does that make a difference?

After SDK Update I had the same problems with API Level 19 and
in my case restarting eclipse didn't solve it.
For some reason, in the sdk/system-images/android-19 directory, sub-folders with system images (armeabi-v7a and x86) were placed within "default" directory.
I just moved them into android-19 directory (if eclipse is running at the same time, you will have to restart it).

You just need to restart the tools. I have seen this bug before. The appropriate installed images will show up after the restart.
You can also try to refresh within the 'Packages' menu, but the easiest thing, is to restart the tools.

Goto sdk\system-images and open the folder of the current API you are using (eg.android-19 folder in your case).
Now you'll find a folder named 'default', open it and you'll see the folder named 'armeabi-v7a' or which ever system image you've installed.
Now move the folder 'armeabi-v7a' to the directory sdk\system-images...i.e simply out of the 'default' folder.
That's it.
I had the same problem and this method worked for me. :D

I restart eclipse.it worked out for me,issue is resolved.

I just had this same issue. My problem was solved by killing eclipse (Command + Q) because I'm a Mac user. So, if you're under other operative system be sure to kill the Eclipse's process and relaunch it.

Lots of potentially useful answers here, but none of them were worked for me.
On my Mac, I have both Android Studio and Visual Studio installed. One would hope that they would automatically look for an Android SDK in the same place, but no, not necessarily.
In Android Studio, go to Tools -> Android -> SDK Manager. In the window that pops up, make a note of the Android SDK Location. It should be something like
/Users/[user]/Library/Android/sdk
Next, in Visual Studio, go to Tools -> SDK Manager. In the window that pops up, the path that should be selected on the left is Projects -> SDK Location -> Android. On the right, click the Locations tab. For me, the Android SDK Location path was set to something like
/Users/[user]/Library/Developer/Xamarin/android-sdk-macosx
I changed this to the path that Android Studio was using, and that fixed the problem for me.

Very simple. I restarted Eclipse, reloaded my project and when creating a new emulator, the problem is gone

Found this thread when I did a search on Google for the same error.
So I just wanted to add that if anyone comes across this thread but you are using Android Studio. You only have to restart the Android Studio. I did and now I can see what I installed.

Make sure you have rights to all the files in the android-sdk-linux directory using:
sudo chown $USER -R ./android-sdk-linux

how to resolve this emulator: ERROR: unknown skin name 'WVGA800' solution

i am trying to start the android emulator from eclipse classic (juno)
and it keeps giving me this error:
ERROR: unknown skin name 'WVGA800'
I developed my software using eclipse indigo, but since I installed eclipse juno and imported the same project it started to give me this error. any idea why? and how to resolve this issue?

My solution was to create a new custom virtual device from the android virtual device manager and use that.

For me on Mac OS X this error went away when I selected the skin in advanced setting it was saying is unknown.

I had the problem and fixed it... Here the main idea of the issue is that the emulator can't find your android-sdk base directory.. so what is the fix? here I will explain..
Find where you have installed your sdk. To do so go to Start->All Programs->Android SDK Tools->SDK Manager.. You will see that the path is written on the top of the window.. copy it somewhere so we need it later.. call it "SDK Path"
Go to Start and Right Click on Computer and select "Properties".. Then select the last option on the left menu which is "Advanced System Settings".. Go to the "Advanced" tab and click on the "Environment Variables.." on the first list see if there is a variable called "ANDROID_SDK_ROOT".. If it's there then check if the value is the same as the "SDK Path" we copied in the step 1.. if they are not the same then change the value of it to the SDK Path...and check if your problem is solved. if not then go to step 3..
If the "ANDROID_SDK_ROOT" matches the SDK Path or your problem didn't solve in step 2 then the problem is probably caused by your username.. This was my actual problem. my username had special characters in it like ( !,#,#,... ) or even spaces in some times. Speaking technically as I am myself a programmer, when the emulator program was trying to open the path, it was giving out an error because it couldn't open it because of the special characters..Guessing that the SDK is installed in your Local App Data folder ( Users\\AppData\Local ) as mine was, you should access it with another Enviroment Variable called "LOCALAPPDATA" which links to your Local App Data folder.. So in your SDK Path change the "drive:\Users\\AppData\Local" to "%localappdata" and your problem will be solved .. For example mine was "C:\Users\MiNuS !3\AppData\Local\Android\android-sdk" and I changed it to "%localappdata%\Android\android-sdk"... (without the double quotations)..
The same problem is present in some other java programs. I had the problem with the Zend Studio too...
Hope it will solve your problem,
Good Luck

I bumped into the same problem in Android Studio on Mac OS X 10.6.8 and there it helped to create a new AVD with target API Level 17 (the only one available after the standard setup it seems). None of the pre-existing AVDs work, however, only the new one (the old ones all use target APIs lower than 17).

The path to where it looks for the skin is in the ~/.android/avd/$deivce-name$.avd/config.ini
My issue like this occured because I had copied an avd to a different computer and the path was incorrect on that new computer.

One solution, if you're happy to do this, is to not use a skin. To do this:
1> Tools/AVD Manager
2> Select the device
3> Click the pen icon in the "Actions" Column
4> Uncheck "Enable Device Frame"
Alternatively, if you want to select a preexisting skin, you can click on "Advanced Settings" and scroll down to the "Custom skin definition" drop down box.
And to see instructions on how to create a custom skin, you can click on "Advanced Settings" and scroll down to "How do I create a custom hardware skin", which links to here: https://developer.android.com/studio/run/managing-avds#skins

I had the same issue as I moved my avd files between systems and as in your case you have moved the relevant files. So the solution as to go to the .android folder and make changes to the files with .ini of conf in their names. In there you will see that the paths to various resources are different as a result of the move you made. So put in the correct path values.
That was how I solved mine.

You may need to update your AVD manager. WVGA800 is the default skin for the emulator. You might try to update your software

As you upgrade your Android Studio, the skin.path value can become no longer valid. The best approach is to copy the set of screens to your own folder path. This way the screens are in more permanent folders.
For example for Macbook:
Find ~/Applications/Android Studio 1.5.1.0.app/Contents/plugins/android/lib/device-art-resources
Copy device-art-resources folder to a place like ~/dev/device-art-resources
For each config.ini in each of your avd folder, change skin.path value to point to the screen of your choice

For SDK-only installed
For who has not installed Android Studio but has only the SDK, to add a new device, or change a skin to an old device is
$ANDROID_HOME/tools/android avd

My solution was to change the skin to nexus 5x !!

I solved by uninstalling and reinstall the emulator.
In Android Studio, go to:
Tools -> SDK Manager
Appearance & Behavior -> System Settings -> Android SDK
SDK Tools tab
Uncheck the Android Emulator check box, and hit the Apply button.
Do the same, checking the Android Emulator check box.