AVD Manager - Cannot Create Android Virtual Device

Question

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 Manager. I then click "New" and am presented with the "Create new Android Virtual Device (AVD)" window. The problem is, I can't get the "OK" button to not be greyed out. I choose Nexus 7 from "Device", I give the AVD a name, I choose "Android 4.2 API Level 17" as the target. And no matter what I do for the rest of the settings, the "OK" button continues to be greyed out. I am not presented with any errors. Any idea as to what I may be missing and why the window would not allow me to proceed by clicking "OK"?

I'm having the exact same problem, but as per @Ralgha's answer, I've already installed `ARM EABI v7a System Image`. My CPU/ABI dropdown list is actually empty; there's nothing for me to select. Any thoughts? — dragonridingsorceress, Dec 22 '12 at 12:43
You may want to try using different API versions. I went ahead and installed every API version that I could. Depending on the API version I choose, I have the ability to choose different CPU emulators. I have also installed the Intel HAXM which made a WORLD of difference when running the emulator. — ossys, Dec 31 '12 at 17:32
I've installed multiple API versions (not all of them, but all the 4.x ones) and there's still nothing in my CPU/ABI list. Any other suggestions? — dragonridingsorceress, Jan 03 '13 at 02:37
I can vouch for dragonridingsorceress. same story here. i'm using a mac book pro, with Eclipse Indigo. — David T., Jan 03 '13 at 18:06
@DavidT. Try selecting a Device from the first dropdown. It will autofill everything but Name for you. See: http://stackoverflow.com/questions/14003009/android-virtual-device-manager-cannot-create-avd/14207730#14207730 — dragonridingsorceress, Jan 08 '13 at 03:22
@dragonridingsorceress hahah, i figured it out after a bit of frustrating. thanks!! — David T., Jan 09 '13 at 19:54
Hello @dragonridingsorceress, would you mind sharing what solved your problem for others to see? It may help someone else, thanks! — ossys, Jan 16 '13 at 05:25
Hi purlogic, as I explained in my comment above to @DavidT., I had to select a preset Device from the first dropdown. — dragonridingsorceress, Jan 23 '13 at 02:23

score 140 · Accepted Answer · answered Dec 19 '12 at 18:57

140

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.

answered Dec 19 '12 at 18:57

Khantahr

8,156
4
37
60

1

I went to Windows -> Android SDK Manager and installed the ARM EABI v7a System Image. – ossys Dec 19 '12 at 20:11
23

Don't forget to restart Eclipse (if you are using it) after installation. – easycheese Sep 08 '13 at 18:30
8

After installation if ARM EABI v7a System Image, don't forgot to restart Eclipse. And if it is already installed then please make sure your device name does not contain _"spaces"_ like (Nexus 4). If your name has space the "OK" button will remain disabled. – shripad20 May 15 '14 at 15:15
1

to add to it, it doesn't like single letter in Name field :) – Dileep Sep 23 '14 at 12:15
I also doesn't like spaces. – Brandon Nov 22 '15 at 17:42

score 25 · Answer 2 · answered Dec 27 '12 at 17:02

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

answered Dec 27 '12 at 17:02

mungflesh

776
11
22

1

Yes, I restarted eclipse after install SDK version, then it showed up on AVD manager. :) – Emmy Mar 18 '13 at 20:56

score 22 · Answer 3 · answered Jan 24 '14 at 09:50

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.

answered Jan 24 '14 at 09:50

Sebastian Carroll

1,386
12
12

3

It would be nice if they specified that as a requirement – Sophie Jul 14 '14 at 00:25

score 14 · Answer 4 · answered Mar 07 '14 at 09:52

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.

answered Mar 07 '14 at 09:52

Laszlo Sisa

221
3
5

1

This worked for me when I had the problem adding Virtual Devices – denil Mar 11 '14 at 03:20

score 9 · Answer 5 · answered Aug 03 '14 at 21:14

9

you need to avoid spaces in the AVD name. & Select the "Skin" option.

answered Aug 03 '14 at 21:14

Anshu Kumar Gupta

181
1
4

score 6 · Answer 6 · answered Mar 09 '14 at 05:28

6

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

answered Mar 09 '14 at 05:28

Philip

1,068
3
12
21

score 5 · Answer 7 · answered Sep 01 '14 at 02:32

5

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

answered Sep 01 '14 at 02:32

phsource

2,326
21
32

1

This was it for me :-) – Zippy Jan 16 '15 at 18:02

Chris Johnson · Answer 8 · 2013-01-22T20:30:04.680

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.

edited Jan 22 '13 at 20:30

answered Jan 22 '13 at 20:21

Chris Johnson

131
1
5

Hi, and welcome to SO! Your answer is a bit a "me, tooish". Generally on SO, "me tooish" type stuff is discouraged for answers. It might be better to put something like this in the comments. – DWright Jan 22 '13 at 20:42
1

I agree entirely. I planned to add this as a comment to the answer above, but as a new contributor, I don't have enough reputation to do that yet (Current:1, needed:50). I better get busy! – Chris Johnson Jan 23 '13 at 07:12

score 3 · Answer 9 · edited Dec 17 '20 at 19:09

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.

edited Dec 17 '20 at 19:09

peterh

11,875
18
85
108

answered Mar 03 '13 at 06:40

amit

31
1

score 3 · Answer 10 · edited May 02 '13 at 06:02

3

You need to open up your SDK Manager and make sure everything is installed, especially System Image. After that will be alright!

edited May 02 '13 at 06:02

ılǝ

3,440
2
33
47

answered May 02 '13 at 05:39

lili caspia

31
1

1

Hello, lili and welcome to stackoverflow! Did you see the other comments/answersunder? It seems this was already suggested and this is not the reason. – ılǝ May 02 '13 at 06:01

score 3 · Answer 11 · answered Mar 14 '14 at 11:32

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.

vsecades · Answer 12 · 2013-12-12T17:44:13.650

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.

edited Dec 12 '13 at 17:44

answered Dec 12 '13 at 17:39

vsecades

129
2
7

score 2 · Answer 13 · answered Jan 03 '14 at 15:48

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 1 · Answer 14 · answered Mar 16 '14 at 05:47

1

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

answered Mar 16 '14 at 05:47

ond

11
1

This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient [reputation](http://stackoverflow.com/help/whats-reputation) you will be able to [comment on any post](http://stackoverflow.com/help/privileges/comment). – iTech Mar 16 '14 at 06:21
@iTech This is an answer to the question, it's just a poor one. ond: please expand upon your answers more in the future, thanks! – Mar 16 '14 at 07:18

score 0 · Answer 15 · answered Jan 14 '17 at 04:31

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 -2 · Answer 16 · edited Mar 14 '14 at 04:29

-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

edited Mar 14 '14 at 04:29

jvperrin

3,368
1
23
33

answered Mar 14 '14 at 04:08

Hemalatha

11

AVD Manager - Cannot Create Android Virtual Device

16 Answers16

Linked