Develop Reference

Error while starting emulator

I am running an android application on emulator. It was working fine till yesterday and today I updated android studio. I am getting following error.
How to resolve this?
emulator: WARNING: Increasing RAM size to 1GB emulator:
ERROR: x86 emulation currently requires hardware acceleration! Please ensure Intel HAXM is properly installed and usable.
CPU acceleration status: HAXM must be updated (version 1.1.1 < 6.0.1).

I had to uninstall version 1.1.1 by going to:
C:\Users\userid\AppData\Local\Android\sdk\extras\intel\Hardware_Accelerated_Execution_Manager>
then type in silent_install.bat -v to verify the current version.
then silent_install.bat -u to uninstall
then silent_install.bat to install version 6.0.1 in my case.

Go To Your Android SDK ----> Run SDK Manager as Admin.
GO down and check Extras---> Update Intel Emulator Accelator (HAXM installer).
Then Restart Android Studio and Run Your AVD.

I had the same issue, apparently, i had installed HAXM manually directly from Intel. And I guess it's conflicting with that of the Android SDK.
So I downloaded and installed the updated version from Intel at HAXM download page. This solved my HAXM [conflict] problem

At first you have to uninstall HAXM from:
Control panel > Add/remove program
After that go to here and download HAXM and install it manually.
This worked for me .

If the SDK manager thinks you have the latest version, simply go to the SDK folder and run the silent_install.bat file.
Mine was here:
C:\Users\userid\AppData\Local\Android\sdk\extras\intel\Hardware_Accelerated_Execution_Manager\silent_install.bat
It will start working immediately, no need to restart Android Studio. It's probably because the SDK manager had insufficient permissions.

When I tried to install version 6.0.3 after I downloaded the update, intelhaxm-android.exe showed a windowed message for 1/10sec (i.e. I could not read it, since I don't know how to stop time) and did nothing after that. I had to locate and run 'setup.exe' among the files extracted by intelhaxm-android.exe. This time there was a prompt saying "Intel Hardware Accelarated Manager version 1.1.1 is already installed. Do you want to install version 6.0.3?" I replied 'Yes', an installation Wizard was opened and that was it. HAXM 6.0.3 was finally installed and the emulator run again.
(Note: You might have to locate the exact 'setup.exe' file (there are four od them) that was run in the installation. You can locate it towards the end of the log file created by intelhaxm-android.exe. The message is something like that: "{temp folder}\Intel\HAXM\6.0.3\2016-09-13_14-35-22\setup.exe was launched".)

Can't find AVD Manager in Mac OS

I'm running Eclipse Juno and have installed the SDK manager for Android for the Mac OS. Things seemed to be going fine, could import old projects as new Android app.
The problem is I can't find the AVD manager. I went to Windows-> and I do not see options for SDK manager or AVD manager.
I went to run a project and it asked me to create a device using the AVD manager, so it's installed, I used it. Is my set up incorrect? Does the latest version of Eclipse just not have it?

I was using the wrong version of Eclipse. You need to install Eclipse per usual, download the Android SDK, then use the one in the version in the adt-bundle-mac directory. That one is the one with the version of Eclipse with the Android plugins. Just answered this for anyone else who is having this problem.

Android - Can't create new v4.0 AVD

I've made a fresh eclipse reinstall + Android SDK v4.0. I am trying to create a new 4.0 AVD and getting this error:
[2011-10-21 11:36:38 - SDK Manager] Unable to find a 'userdata.img' file for ABI armeabi to copy into the AVD folder.
Reading How to create an AVD for Android 4.0, I checked SDK manager and I have 'ARM EABI v7a System Image' installed. to be on the save side I un-installed and reinstalled it.
I also copied 'C:\Program Files\Android\android-sdk\platforms\android-13\images' into 'C:\Program Files\Android\android-sdk\platforms\android-14'
Still getting the same error. I have no problems creating 2.1 AVD.
Note: I'm running Win XP
Issue fixed itself after restarting the PC.

THis worked
http://learn2program.wordpress.com/2011/11/17/beginning-android-4-with-intellij-idea-unable-to-find-a-userdata-img-file-to-copy-into-the-avd-folder/
Apparently the location of the image file changed recently.
Basically, in eclipse, go to run/debugconfig/android app/new config/target/automatic(yes, reclick it)/manage and then follow the sdk manager reinstall methods.
I'm in the middle of it now and this report is somewhat from memory since the download is occurring as I type this. OK, it worked to get the AVD in. Hello World is next ! :)

If you have installed the Android SDK provided by google and once again via Eclipse you install the SDK while configuring ADT plugin. System wont recognize the first installation.
There for as "user1123966" said you can solve it
OR by going to Windows-> preferences -> android-> and change the SDK location to the First Installation.
I would recommend you to go for first option and uninstall the first installation.

Issue resolved after restarting my machine.

The location of userdata.img changed in more recent versions of the Android SDK and Eclipse hasn't been adjusted to accomodate it yet. Here's what worked for me:
Within your Android SDK folder, take all the files from system-images/android-15 (or whatever API version you have) and move them to platforms/android-15. For me, this meant moving two folders: armeabi-v7a and x86. I was able to make an AVD fine after that.

i was recently facing the same problem and tried all solutions here, but none was working for me.
my fault was, that i didn't made a choice in the CPU/ABI section, after creating a new devie in the avd-manager. (Guess I started with a bad tutorial, since this field was left open there too...)

In case you can't get it to work after the above comments, you should try to update your ADT version (to at least 20). After that I was able to install ARM EABI v.. System Image and it worked fine.

To avoid "unable to find a "userdata.img file for ABI armeabi to copy into the AVD folder" error when creating Android 4.0.x AVD, you should make sure the "ARM EABI v7a System Image" is installed in all the "Android 4.0.x" sections in SDK manager. and don't forget restart AVD manager after all packages are installed completely.

I had the same issue. Here's my context and how I solved it.
When I was opening my Android SDK Manager through Start > All Programs > Android SDK Tools > SDK Manager, I was able to see the ARM EABI v7a System Image package and it was actually installed.
When I was opening my Android SDK Manager through Eclipse, I wasn't even able to see the ARM EABI v7a System Image package.
I figured out after that the SDK Manager I was accessing through the Start menu was located at C:\Program Files (x86)\Android\android-sdk while the SDK Manager I was accessing through Eclipse was located in C:\Users\$(CURRENT_USER)\android-sdks
So I removed the whole C:\Users\$(CURRENT_USER)\android-sdks folder and reconfigured Eclipse to use C:\Program Files (x86)\Android\android-sdk folder : Window > Preferences > Android then browsed SDK Location field to C:\Program Files (x86)\Android\android-sdk.
This is one of the many reasons you could have this error so just adding my personal case and solution.
Cheers.

update ARM EABI v.. System Image by Android SDK Manager

Android SDK setup help

Im having some weird issues setting up the SDK in eclipse, when i go to make a project i cant select anything in the build target. I have installed the eclipse plugin and the SDK but im not sure whats going on. Some help please, thanks!

You are not able to see the build target because you have not installed any Android virtual device in your AVD Manager.
AVD Manager is located at the same place where SDK Manager resides(in windows startmenu-programs-android SDK Tools)
Open AVD Manager with administrator privilege and install any build target you choose. Then try in the eclipse . It will work fine.

Android:Android SDK and AVD Manager doesn't launch after did SDK upgrade?

I have Android development eclipse setup on Mac OS X. I recently did Android SDK upgrade from 1.5 to available versions such as 1.6, 2.0.1 and 2.1 and docs. After did upgrade, automatically restarted my Macbook and installed all new versions. After this, when i try to launch "Windows->Android SDK and AVD Manager", it doesn't launch at all. What might be the reason? Does anyone has the solution?
The reason why i'm trying to launch Android SDK and AVD Manager is, i need to add new Android virtual device(avd) target for 2.0.1 and 2.1 versions, for that i'm trying to launch Android SDK and AVD Manager.
Thank you in advance.

It seems the latest version of the Android SDK AVD Manager requires that there be a few directories (empty) before the AVD Manager will launch.
In the SDK install directory, there must be sibling directories to tools for "platforms" and "add-ons".
Create those directories, restart Eclipse, then launch AVD Manager.
And that should do it.
Then You can Update All and get platforms.

Well this is actually caused by the fact that android is installed on c:\program files folder (the commands executed by android consider that the called folder is c:\program which is a non existent folder and this issue is due to the space in the name of this folder).
So the solution is to reinstall your program under a folder with non spaced name (for example c:\Android) and it should be fine.
Note: this problem can also be related to a problem of jre problem so make sure you have the appropriate version for android sdk.

Have you tried launching Eclipse with the -clean option?
The clean option clears any cached data Eclipse might be using, so it may resolve the SDK/AVD Manager issue you are encountering.
Here is a more in-depth explanation:
http://www.eclipsezone.com/eclipse/forums/t61566.html
Here is one example of launching Eclipse from a command line (Terminal) in OSX with the -clean option:
http://www.brooksandrus.com/blog/2007/06/30/run-eclipse-from-the-command-line-on-os-x/

You might have to update your "SDK tools" as well as downloading the Android v2.1 SDK itself. I had the problem where after downloading v2.1, suddenly nothing worked as I got the message I needed to update to SDK tools rev5 - that update doens't happen automatically when you go to the AVD manager and download the "available packages". I don't know if it's the same on a Mac, but on the PC it was as simple as going to "Help -> Check for Updates" in Eclipse.

the newer version of the SDK tools is probably in a different folder than the old version, so update
Window -> Preferences -> SDK Location.
Paul
Check the install is ok by running the commands from the tools directory manually to check it's not an issue with the install

I had a similar problem and traced it to a faulty swt.jar file in the folder
[adroid_sdk]\tools\lib[platform]
Downloaded a new one from http://www.eclipse.org/swt/ and put all the files into the above directory. For me [platform] was "x86", but it might be different for you, though I only had 3 folders to choose from and I dont think it will hurt if you put the files in all of them.