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 Selected directory is not valid home for Android SDK

I installed android studio but while selecting android SDK I am getting following error. I tried solution which is on this post but no luck. How can I solve this?

I had this problem, select SDK folder (NOT SDK->sources or SDK-platforms)

I resolved with the instructions here,
http://www.blog.teamguru.in/2018/04/06/selected-directory-is-not-a-valid-home-for-sdk/
Just close current error window and let run the android studio
Open the SDK manager as shown below
Click on Edit SDK location as shown below
Simply press next button if there is correct location for SDK you want to install there
Let it be downloaded
Install platform and SDK tools and
Enjoy

Try restarting the application. Close all related studio processes, then right click "run as administrator".
You should be fine after this.

I got the same issue. You must enable the Android Support Plugin
Configuration > Plugin > Android Support Plugin. Check it.

Close error window
Go to gradle tab
select "Gradle settings", wrench icon
Search for SDK setup
Select appropriate sdk for your device.
Next, two times
Wait for install
There is all..

None of the other answers work. After the installation, immediately close Android Studio, then start it as administrator. A message might popup asking for the sdk manager location. Ignore it (Close the popup). Go to Tools > SDK Manager and click on the edit button on the right of Android SDK Location. Then click Next, next and you're good to go. Android Studio will let you install the sdk manager.

I had the same problem but what I found is that it requires the parent folder of the following things AVD manager,SDK manager,tools,platform-tools,build-tools etc.So what you need is to find the parent directory of these things, which you might find with a name such as android-sdk or android-sdk-windows(in case you are using windows OS).Make sure the above said contents are in that folder and select it.I hope you will find this useful.

Download the SDK from http://developer.android.com/sdk/index.html
Start SDK manager and make everything up to date
Also, make sure you have set the language level to
7.0 Diamonds, ARM, Multi-catch, etc

I had this problem on Linux. Apparently you need write access to some place in that directory, so I just took ownership of the entire thing:
sudo chown -R thomas:thomas /opt/android-sdk
Could be that something similar is going on on Windows as well.

If like me, a MacOs user which has installed Android Studio on my Mac and if you've tried everything you can think of but was still unable to set the Android SDK directory in Android Studio, follow the next steps (I know the site where I got the bundle is a freeware site but the package is the right one):
1. Download adt-bundle-mac (Android Developer Tools) from [here][1].
2. Unzip the file and browse into the unzipped folder.
3. Copy only the sdk dir to /Users/username/Library/Android
4. Open Android Studio, the error about the SDK folder which is not set will pop up, set the path to the SDK to "/Users/username/Library/Android/sdk".
5. Now Android Studio will accept the path and you're good to go.
I wasted about 2 hours until I fixed it so I hope that by writing this answer I'll save you some 2 hours.

The sdk folder contains the platform-tools folder.
I copied this folder and named it platforms, then it worked for me.

Just delete(preferably permanently) all the android directories in whatever location they are present(e.g. C:\Program Files\Android, C:\users\respective user\respective android folders). Remove the installer as well(if possible). Make sure to save all your Android Studio files in some external storage (preferably).
The main thing is to get Android studio with SDK.
Now go to the android studio website and install android studio leaving all settings default. There you will also get to install the SDK and it's linking.
It will take some time to load and will load nearly 1.5 GB files.
This worked for my case.

In my case I wasn't giving him admin permission

Steps to follow:
Close Android Studio.
Restart Android Studio and Give the path of Empty Folder .
Install Sdk in that folder(Sdk will automatically install and will get configure automatically.)

With Android Studio 4.1.2 the easiest thing is to close the project (file / close project). That's how you get to the wizard that automatically sets up the SDK for you.
The default location that it suggests is /Users/stan/Library/Android/sdk (exactly the same that I was trying to set up manually but AS kept saying it's invalid)

"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

"Unable to find a userdata.img file for ABI armeabi..."

Once again I've made the mistake of updating Eclipse with the latest Android SDK/tools and have rendered it useless.
Running Eclipse on a Mac.
When I try to create an AVD it tells me it is "unable to find a userdata.img file for ABI armeabi". I've read all the similar questions here that tell me to go to Run/Run Configurations and make sure I have the latest "ARM EABI v7a System Image" downloaded. I've done that. I've restarted my machine. Still no joy.
FWIW I'm not trying to create a 4.x emulator; just 2.3.3. UPDATE: I can successfully create a 2.2 emulator with all the same parameters (screen size, storage card size, memory, etc.) as I was trying for 2.3.3. Also, I can successfully create a 4.x emulator with those parameters. Just not 2.3.3.
Again, I've read all the similar questions. Doing what I did seems to have solved the problem for several developers running Win7. Other questions end with someone saying, "I'm downloading the file now" but no update as to whether it worked or not. In my case, after downloading the file I see no change in behavior.
Thanks for any help.

Check the highlighted part is installed or not..
if it is installed you can find this under CPU.. Select it and click create avd

Step 1) Open Eclipse and click on Run Configurations (pull down the arrow next to the Run or Debug button).
Step 2) Select "Android Application" and click "New"
Step 3) Select the "Target" tab and select "Automatic" (Click once more even it is selected and the list box below is disabled"
Step 4) Click on the "Manager..." button
Step 5) In all the "Android 4.0.X" sections, select "ARM EABI v7a System Image" checkbox
Step 6) Click the "Install X Package..." button
Reference: http://tech.thecoolblogs.com/2012/01/unable-to-find-userdataimg-file-for-abi.html#ixzz1u2EMZGt7

Install the ARM EABI img from the sdk manager for android 4.0 your problem will be solved

This error is happening because the location of userdata.img file has changed since Android 4 (API Level 14). So we need to reinstall the ARM EABI package. Follow the steps given at
http://tech.thecoolblogs.com/2012/01/unable-to-find-userdataimg-file-for-abi.html

I had the same problem and this is how I solved it:
In Eclipse:
Window > Android SDK Manager
Select ARM EABI v7a System Image
Install package
Done. You should be able to create your AVD now.
Good luck!!

Now with Android 4.1 (API 16), make sure you install the ARM EABI v7a System Image in the Android SDK Manager. This works perfectly in Eclipse Indigo on Mac OSX.

Actually, you still need to install Google USB Driver in Extras in the bottom of Android SDK manager.

Solved a problem after I realized that newly created AVDs were being saved in user folder (user foo) C:\HOME\foo and Android plugin was trying to find them in C:\Users\foo.
I have set environment variable (this will change save avd folder).
ANDROID_SDK_HOM=C:\Users\foo
Make sure you create your AVD again since you have changed save location now.
That solved a problem, I assume the proper way would be to set look-up folder but could not figure out how to change that.

I was getting the same erorr, even after deleting and re-installing that package. I looked at the sdk folder, and found that the images were all the way under
...\sdk\system-images\android-10\x86\images\x86
Looking at thow the PAI 17 images were stored, I copied everything in that directory and moved it to
...\sdk\system-images\android-10\x86
Now it works fine :)

It can be solved from command line by running:
update sdk -u -a -t android-16,sysimg-16

I had the same problem when using the command line.
I fix it by copying the files under
...\sdk\system-images\android-X\armeabi-vY\
into
...\sdk\platforms\android-X\images
Maybe you need to create first the folder images

In my case it was related to "No system images installed for this target" even though Image is installed.
Following this answer, I moved c:\adt\sdk\system-images\android-23\default\x86 up one folder to c:\adt\sdk\system-images\android-23\x86, and after that I got the error:
Unable to find a userdata.img file for ABI armeabi...
On a hunch, I created a symlink/junction to the original folder, and it worked. I used this:
mklink /j "c:\adt\sdk\system-images\android-23\default\x86" "c:\adt\sdk\system-images\android-23\x86"
It's just that you need it in both folders. I used a junction instead of simply copying the folder so as not to waste space.

Starting the Android emulator in SDK tools, revision 12

I updated the Android SDK tools from revision 11 to revision 12, and the emulator now fails to start. When I try to run emulator.exe, I get:
invalid command-line parameter: Files\Android\android-sdk\tools/emulator-arm.exe.
Hint: use '#foo' to launch a virtual device named 'foo'.
please use -help for more information
The path to emulator.exe is C:\Program Files\Android\android-sdk\tools.
How do I fix it?

As was previously suggested, it does seem to be caused by the fact that there is a space in the default installation path of the Android SDK: C:\Program Files\Android\android-sdk\
There are a couple of possible solves, though-
move installation directories to paths that do not contains spaces (as already mentioned)...
but simpler and possibly slightly less cumbersome is simply adjusting the path in Eclipse to use 8-dot-3 directory name(s). Since I'm running Win7, I have two Program Files directories, the second one being "Program Files (x86)" which is where the sdk installed. So the 8-dot-3 path is PROGRA~2. Thus, I simply changed the "SDK Location" value in the Android Preferences in Eclipse from C:\Program Files\Android\android-sdk\ to C:\PROGRA~2\Android\android-sdk\ and everything now works fine.
If you don't know the 8-dot-3 name of your desired path, just fire up a Command Prompt and execute "DIR /X"... the short name will be displayed next to each directory.

Same problem for me, though this is my first time trying to work with Android SDK in general. I believe the problem is with the location of the SDK. Note the "paramater" "Files\Android\android-sdk\tools/emulator-arm.exe." I believe there is a bug in google's code where it doesn't have the directory the SDK is located in in quotes, meaning, if there is a space anywhere in the directory name, it won't work. Can someone with their SDK in a directory with no spaces confirm my theory?
To work around the issue, you can call "C:\Program Files\Android\android-sdk\tools\emulator #foo" from the command line, where "foo" is the name of your emulator.

I got this problem just now, and I found a solution.
My path to the emulator-arm.exe is C:\Program Files\Android\android-sdk\tools. When I try emulator-arm #my_avd from the command line (my_avd is my Android Virtual Device name), it works.

I fixed this problem on Windows XP. Just cut from "C:\Program Files\Android\android-sdk" and paste content directory to "C:\Android\android-sdk". Set my system varaible 'ANDROID_HOME'="C:\Android\android-sdk". Set path to Android SDK in Eclipse as "C:\Android\android-sdk". That's it!
Everything works fine.

Since the cause of this issue is the space within filepath names of the Windows install directory then another workaround is to use the file short names (i.e. 8.3 alias filenames).
Specifically, if root install directory for Android SDK is
c:\Program Files\.. then use c:\PROGRA~1\..
or if
c:\Program Files(x86)\.. then use c:\PROGRA~2\..
You can then launch the SDK Manager via the command-line by running:
start c:\PROGRA~2\Android\android-sdk\tools\android.bat

Fixed in r13. Update your SDK Tools!

I think you are saying you changed the minSDK version of your app and now the emulator wont run...? this is because your emulator is the wrong version... assuming you changed the minSDK of your app correctly, all you need to do is create a emulator with the same SDK version. Open the Android SDK / AVD manager (icon top right of screen next to print token) and create a emulator with minSDK 12.

Moving your Android SDK folder to somewhere that the complete path will be without white spaces will fix the problem.

I also got this problem after updating SDK Tools from revision 11 to 12.
I found it was a problem with a space in the upper directory name where android-sdk-windows resides, then I copied both 'eclipse' and 'android-sdk-windows' directories from my 'Program Files (x86)' to the root of drive D:.
All is solved now!

As an alternative to PROGRA~2 method (which is not working for example in Intellij IDEA), you can create a symlink named, for example, prg to Program Files (run mklink /? from command line to learn how to do it), then run emulator as C:\prg\Android\android-sdk\tools\emulator.exe. Change path to SDK/emulator in your IDE also.

I had a same problem when I setup r12. I found out this problem was caused by blank spaces in the path you setup android SDK. The solution is that you should move the folder of android SDK to a place without spaces, in your case : E:\andriod-sdk or D:\abc\xyz\android-sdk.