235

Ok Button not clickable

For some reason, the OK button is not clickable when I try to create an AVD. Does anyone know what I'm doing wrong?

Cœur
  • 37,241
  • 25
  • 195
  • 267
gratsby
  • 3,107
  • 4
  • 20
  • 20

8 Answers8

276

Simply because CPU/ABI says "No system images installed for this target". You need to install system images.

In the Android SDK Manager check that you have installed "ARM EABI v7a System Image" (for each Android version from 4.0 and on you have to install a system image to be able to run a virtual device)

In your case only ARM system image exsits (Android 4.2). If you were running an older version, Intel has provided System Images (Intel x86 ATOM). You can check on the internet to see the comparison in performance between both.

In my case (see image below) I haven't installed a System Image for Android 4.2, whereas I have installed ARM and Intel System Images for 4.1.2

As long as I don't install the 4.2 System Image I would have the same problem as you.

UPDATE : This recent article Speeding Up the Android Emaulator on Intel Architectures explains how to use/install correctly the intel system images to speed up the emulator.

EDIT/FOLLOW UP

What I show in the picture is for Android 4.2, as it was the original question, but is true for every versions of Android.

Of course (as @RedPlanet said), if you are developing for MIPS CPU devices you have to install the "MIPS System Image".

Finally, as @SeanJA said, you have to restart eclipse to see the new installed images. But for me, I always restart a software which I updated to be sure it takes into account all the modifications, and I assume it is a good practice to do so.

enter image description here

HpTerm
  • 8,151
  • 12
  • 51
  • 67
  • I had the same problem and it got working after I had installed "MIPS System Image" for Android 4.0.3, Android 4.1.2, Android 4.2. Android SDK Manager: revision 21.0.1 – Maksim Dmitriev Dec 23 '12 at 15:36
  • 23
    Ah, since I was running from eclipse, I had to restart eclipse to get the new system images to show up. – SeanJA Dec 27 '12 at 17:45
  • 4
    I've already installed the packages twice and the next run, the program says they're not installed. – KI4JGT Jan 19 '13 at 20:47
  • @KI4JGT it's hard to tell what the problem is with what you say. Give perhaps more details, system, eclipse version etc or screen copies of your config or perhaps start a new question on your problem so that you have room to give more details. – HpTerm Jan 20 '13 at 18:57
  • @KI4JGT I had the same problem too, until I realised that the sdk path used by eclipse is not the same as the one you expect. Go open up the SDK manager via eclipse and look closely at the "SDK path" on top. – A Person Mar 02 '13 at 15:24
  • 3
    The most important is :) you have to restart eclipse after installing system images – Superbiji Apr 17 '13 at 07:39
  • Amend, please: "a system images" --> "system images" (in the beginning) – RedRidingHood Jul 25 '16 at 20:10
31

Had to restart the Eclipse after completing the installation of ARM EABI v7a system image.

igr
  • 10,199
  • 13
  • 65
  • 111
James
  • 311
  • 3
  • 2
12

This can happen when:

  • You have multiple copies of the Android SDK installed on your machine. You may be updating the available images and devices for one copy of the Android SDK, and trying to debug or run your application in another.

    If you're using Eclipse, take a look at your "Preferences | Android | SDK Location". Make sure it's the path you expect. If not, change the path to point to where you think the Android SDK is installed.

  • You don't have an Android device setup in your emulator as detailed in other answers on this page.

Brad Parks
  • 66,836
  • 64
  • 257
  • 336
  • 1
    This! I too had multiple copies and was banging my head against the wall. Thanks for the answer! – Alagappan Ramu Jan 28 '14 at 14:25
  • How can I check if I have multiple copies @AlagappanRamu, @BradParks? Thanks! – Adam Jan 15 '17 at 22:19
  • @Adam - look at "Preferences | Android | SDK Location" in Eclipse - is it the same folder location you've been updating? If not, there's your 2 locations! – Brad Parks Jan 16 '17 at 02:13
6

For Ubuntu and running android-studio run to install the packages (these are not installed by default):

android update sdk
Niels
  • 482
  • 1
  • 5
  • 18
4

I had the same problem while creating AVD with 4.2.2 images, I resolved it by doing the following :

  1. Check if there exist a "default" folder in adt-bundle-windows-x86_64-20131030\sdk\system-images\android-17.

  2. If it exists then move the contents(downloaded system images) of the "default" folder to adt-bundle-windows-x86_64-20131030\sdk\system-images\android-17.

Hope this helps.

Vinay Jain
  • 1,653
  • 20
  • 28
  • Yes! :) And do this while Eclipse/ADT is closed, or restart it. – akauppi Mar 17 '14 at 14:04
  • Great! I'm on Ubuntu and didn't expect this solution to work but it did! Another workarround is to to run ./android (the SDK manager) from cmd line not from inside Eclipse then go to menu Tools -> Manage AVDs -> button "New". Then it shows the system images. In Eclipse it doesn't... at least for me. – WindRider Jun 13 '14 at 13:32
2

I want to update this question with a screenshot of a recent Android Studio. It took a bit of poking around to find where to install new system images.

You get to the SDK Manager through one of two paths. Option 1. Tools > Android > SDK Manager Option 2. Android Studio > Preferences > Appearance & Behavior > System Settings > Android SDK (This is for Mac; adapt for others.)

In the pane "SDK Platforms," check the "Show Packages" box to see the system images.

Select the ones you want, click "Apply" and voilà!

enter image description here

benevolentprof
  • 1,507
  • 2
  • 13
  • 24
1

I had to move the folders inside a folder named "default" to the android-## folder so Eclipse could see the images.

GuilleGlad
  • 21
  • 2
0

There is a new possible error for this one related to the latest Android Wear technology. I was trying to get an emulator started for the wear SDK in preparation for next week. The API level only supports it in the latest build of 4.4.2 KitKat.

So if you are using something such as the wearable, it starts the default off still in Eclipse as 2.3.3 Gingerbread. Be sure that your target matches the lowest possible supported target. For the wearables its the latest 19 KitKat.

Jay Snayder
  • 4,298
  • 4
  • 27
  • 53