This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200
Ok I have eclipse Galileo Build id: 20100218-1602, I was having a problem with my Logcat, and seen a post that recommended updating the SDK, so I updated the SDK to the latest version. This made the eclipse program give me a message saying this SDK needs ADT 14 or higher. I have tried to update the ADT without success. At this point, I've tried to delete and uninstall everything, and that has been impossible. There is no uninstall program and the eclipse folder will not delete. Does anyone have a recommendation on how to delete eclipse from my Window 7 computer? Or a way to revert back to my old SDK? This is driving me nuts. Thanks!
ADT 14 works only with Eclipse Indigo version.
Eclipse does not need any installation it contains a direct runnable exe. If you are unable to delete the folder then try restart your PC or try a software that will unlock the folder or atleast show you the processes that have a lock on that particular folder. You can close these processes on your own.
Once you install ADT 14 with eclipse indigo update the Android SDK. It should be straight forward.
i recommend a new install. while an update will easily take 2 to 4 hours (from rev 15 to rev21, with appropriate sdks, etc), you can download the complete ADT ECLIPSE bundle in much less time (410 MB) on regular 10Mb broadband.
i tried updating on Java EE Indigo from rev 15 to rev 21 (sdk tools) and ran into a big, big mess. not worth it. gave up and reinstalled eclipse. faster process and much sturdier result.
Download ADT bundle here, then
follow these instructions
since ECLIPSE is an executable that uses java virtual machine to run, it does NOT need to be installed (especially handy on windows). just unpack the bundle into your Program Files folder and execute the file eclipse.exe (if running under Vista / 7, you MAY need to run always as Administrator, i have a published recipe for Admin installing here).
after installing and checking if everything is OK, rename or delete your OLD eclipse folder.
if you use the same workspace that you were using previously, you should not miss a beat: the same projects will be open as when you last left your workspace, and your run and debug configs should be there, too.
ECLIPSE ROCKS!
I had a working Eclipse setup with 3.6.2 and SDK tools from version 11, and it has been building my main project just fine for quite a while.
For a different project, I thought I needed to upgrade my SDK to the latest and greatest - at this point API 14 (ICS 4.0).
I cannot even reconstruct the steps I went through, but what happened was that my project would seem to build, but I would see that it would say that it was skipping a post-compiler step, and at the end I would have no APK.
I also noticed that it updated my .classpath so that the output path was bin/classes instead of .bin.
Along the way I tried updating my Eclipse to the latest version (Indigo 3.7.1) but this didn't help.
I solved the problem eventually with help from this post on the Google Android forum:
http://code.google.com/p/android/issues/detail?id=21031
For me personally the biggest issue seemed to be solved as follows (qutoe from comment 25 in the forum post)
"I seem to solve the problem with .apk files not being built automatically until run/debug is used (comments #10, #11 etc.). Go to Windows -> Preferences -> Android -> Build and uncheck "Skip packaging and dexing until export or launch" then restart Eclipse. Works for me."
But there is other useful material there. Different people with different projects seem to have different problems with this setup.
I still don't understand the change in the classpath, but it doesn't seem to matter.
In addition, I found a discussion of installing the ADT with Eclipse Indigo which was helpful here in Stackoverflow:
Eclipse Indigo - Cannot install Android ADT Plugin
I also found that I guess because of various uninstalls/reinstalls, for some reason it stopped excluding my .svn directories from the sources. This Stackoverflow post was helpful with that:
Why is eclipse trying to copy my .svn folders from src to bin, and how can I make it stop?
Finally: a tip for really and truly uninstalling Eclipse - everybody says there is no uninstall, and there isn't, but there is a directory that Eclipse leaves in your home directory (in windows 7 under c:\users\) called .eclipse -
Zap it if you really want to start fresh.
In addition, for less extreme measures, there is Project->Clean inside Eclipse, and you can invoke eclipse with "eclipse -clean" for additional cleansing effects. No idea what, but various helpful people along the way suggested trying that to solve problems.
Ah yes - when I first installed Indigo and tried to build, I got a warning that my Java Compiler Compliance level was not up to snuff, which was simply not true - I have only Java 1.6 installed on my machine.
See this post for somebody who had similar experience:
http://marakana.com/forums/android/general/374.html
For me, what worked was simply going to Project, Properties, Java Compiler, then click on Configure Workspace Settings, and click on Ok in the dialog. Didn't need to actually change anything. Just showed it that everything was ok!
Eventually I indeed did clean out my Eclipse and Android installations (including the aforementioned .eclipse directory, and there's also an .android directory in your home directory which you may want to erase if uninstalling the Android SDK Tools doesn't do that - this actually is uninstallable). Installed everything from scratch and then used the additional information provided above and now it's building my APK.
I hope this saves somebody the hours I spent getting my build back in shape.
I recently installed a fresh copy of Motodev. When I type the name of object and a period after it a popup comes up with a list of all of the methods available to that object. Ever since I started using this new copy of Motodev if I have an object with a very large amount of available methods this process freezes the whole program for several seconds.
RelativeLayout and EditText are the two that I have personally noticed that this is a problem with, but I suspect any object that has a large number of methods will cause this. It was never a problem before. Has anyone else seen this issue and if so how did you fix it? I do like having the list pop up so that I can see all of the methods available to me so I'd like to leave that feature turned on if at all possible.
Looks like you figured this out already, but I'll say it for future readers. There is an update to MOTODEV Studio specifically to work with ADT 8.0.1. There were some API changes in ADT that required us to update Studio also. ADT 8.0.1 requires Studio 2.0.1, which is based on Eclipse Helios. There are installers on the MOTODEV site as well as an updater for Eclipse.
Because of the complexity of dependencies with all the Eclipse plugins, I suggest to download the .zip archive at MOTODEV rather than using the "Install Updates" method. I find that I get timeouts quite often at home on broadband that don't happen at work with a bigger pipe.
Also, Studio 2.1 will be available some time within the next week (~Jan 25) and will work with the 2.3 SDK and ADT 8.0.1.
UPDATE: 2/14/11 - It would appear that the correct answer is found at comment #8 in this link: http://code.google.com/p/android/issues/detail?id=7850
Tim will need to formally accept this answer at some point...
Which is as follows:
For those of you with this problem, here's what you can do until the fix is publicly available:
1. Download https://android.googlesource.com/platform/frameworks/base/+archive/<branch>.tar.gz where is one of those listed here (froyo-release for 2.2, the file is about 113MB): https://android.googlesource.com/platform/frameworks/base/+refs
2. Extract the contents of base/ in the tar into "/platforms/android-/sources" where is 8 for froyo, 7 for eclair, etc.
3. Enjoy fast content assist in 3.6!
If you are using eclipse v3.6 (Helios) this is a known issue with ADT - the android dev site recommends using v3.5 or v3.4 of eclipse until the problem is resolved.
EDIT: It might be dependent on the version of ADT you are using - I can't find the recommendation to use v3.4 or v3.5 anymore. Perhaps things were fixed with ADT 8.0.x Check which versions you are using anyway.
Am I the only Eclipse developer whose workbench quickly sputters, wheezes, crashes or hangs and makes me use Windows 7 Task Manager to hard-bounce it?
I've got dedicated, Android-only (as it were) installations of Eclipse Helios (3.6) and Galileo (3.5) with the very latest Android SDK (0.9.7.v201005071157-36220) using android-sdk_r06-windows.zip. I'm running Windows 7 Professional 64-bit, but 32-bit Eclipse (Helios and Galileo) and a 32-bit jdk1.6.0_20.
It is true that these are both Eclipse Java EE installations and not the bare-bones Java-only (non-WTP) versions. I haven't tried that yet. I followed a tutorial that said to use Helios, but said nothing about what not to include (like WTP which I ordinarily use in my work).
I can avoid much of the trouble by editing XML files using the standard Eclipse XML Editor and avoiding the Android SDK's various XML editors, but very quickly, things stop working and the whole thing caves in on itself.
I've tried bumping memory in eclipse.ini, -Xms128m, but that hasn't helped.
I'm looking to hear from someone who's gotten over this mess or who knows what I should have done.
Any ideas?
Thanks in advance for any and all comments.
Russ Bateman
After a week of frustration I reached the conclusion that you cannot install Android for use in Eclipse Java EE, my usual mode. Instead, use the plain Java Eclipse. My definitive installation became Eclipse Galileo SR2 IDE for Java Developers. I added these lines to eclipse.ini, though I probably did not have to be so generous:
-vmargs
-Xms256m
-Xmx1024m
-XX:PermSize=128m
-XX:MaxPermSize=512m
In order to distinguish this version of Eclipse from my usual Java EE development version on my task bar, I found an icon to graft onto it at http://www.large-icons.com/stock-icons/free-large-android-icons.htm and selected one that looked most like the green Android icon.
Add this line -XX:MaxPermSize=256m to your eclipse.ini file right after -vmargs. I have no idea why, but apparently it's a known bug. I can get you the source where I found this solution if you'd like, it took me a fair bit of googling