I just installed the Android Eclipse Plugin and the Android SDK from Google yesterday. I open the AVD Manager window by going to Window -> Android Virtual Device Ma
On Kubuntu 12.04, Eclipse Kepler, ADT installed, I experienced the same symptoms. The ARM EABI v7a System Image was already installed. The way out was to run the tool from the command line, then it did not complain. I guess a restart of eclipse could have done the trick but I am not sure any more if I tried dit or not.
Hey guys I had the same problem but now I got it: Check which API you are selecting and for that API version is CPU/ABI available or not. If it's available then your work is done! Select the device according to the windows supporting it.
Launching the AVD Manager from Visual Studio 2015 resolved this issue for me.
I had (a lot of packages) all the required packages installed but hadn't used them for some time & had issues detecting them in the SDK manager. I attempted all the solutions provided above to no avail, including running the AVD after running the monitor.bat file in 'android/sdk/tools'.
I then launched the AVD from VS in 'Tools->Android->Android Emulator Manager' and it detected both 'Google APIs Intel Atom x86' & the ARM EABI v7a system Images right off the bat!
Target is set to API Level 23.
I had trouble creating an AVD.
Either:
Had the exact same trouble... loading the ARM EABI v7a System Image worked for me too. Thanks very much.
I had previously seen on the Android SDK manager that a system image with the same name (ARM EABI v7a System Image) WAS installed on my system for a more recent SDK (Android 4.2). Consequently I thought it would negate the need to install the earlier Android 2.2 SDK ARM image, but apparently not.
If you are having AVD creation problems, just try to put it inside a new folder (eclipse, android sdk, avd) and then you just run it and it should work. Just open Eclipse in that folder and run as usual