score:140

Accepted answer

you either haven't selected a cpu/abi target in the dropdown below the target, or you haven't installed a system image. open your sdk manager and ensure that you've installed arm eabi v7a system image under the android 4.2 section.

score:-2

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

score:0

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.

score:1

i opened monitor.bat in android-sdks\tools and started the device manager there and i was able to create the avd.

score:2

i actually hit on this problem a week ago. the issue had to do with not using an updated eclipse version of the android sdk plugin with the latest version of the sdk. it was a fun problem overall, but it disappeared as soon as i updated it.

i had even updated the avd images and no luck. apparently the old plugin cannot see the new image layout or something. this is for version 22.3 of the sdk.

score:2

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.

score:3

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.

score:3

you need to open up your sdk manager and make sure everything is installed, especially system image. after that will be alright!

score:3

if you have changed the sdk path somehow it will not be able to find the sdks you installed even though it is listing them fine.

i solved by openig android sdk manager and in that dialog choosing the menu tools -> manage avds. and when you open manage avds directly from the toolbar of eclipse you should refresh to see the avd you created.

score:4

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.

score:5

another thing that tripped me up: the "name" field must be a single word and must not have spaces!

score:6

try to create an avd with the monitor.bat in the tools-folder, that worked out for me!

score:9

you need to avoid spaces in the avd name. & select the "skin" option.

score:14

i had the same problem, although all required packages were installed. i closed down eclipse, ran monitor.bat in the \android-sdks\tools\ folder, opened the avd manager from there, and i was able the create virtual devices here.

score:22

first, make sure you don't have spaces (or other illegal characters like '+','=','/',etc) in the "avd name" field. spaces broke it for me.

score:25

i had trouble creating an avd.

either:

  • re-start eclipse after installing sdk versions from the sdk manager, or
  • you should run the "avd manager.exe" outside of eclipse

Related Query

More Query from same tag