It's really weird.
Ever since I've updated to the new ADT&SDK (22.6.0), I can't create any AVD. Not even the built in ones. I tried setting different Android Os versions, different memory values,... I've played with many configurations . Nothing helped.
I've tried to even uninstall and re-install the entire SDK manager, and it didn't work.
it lets me fill all of the fields, but pressing "OK" doesn't do anything. it doesn't even close the window.
Here's a sample screenshot:
Can anyone please help?
OK, so it seems it's a known bug.
for now, the workaround is to create the AVDs via the AVD manager, by running the AVD manager outside of eclipse- just run "AVD Manager.exe" and that's it.
Related
Just started getting this. No idea why.
I tried 3 different new devices and get this for all of them.
Just use Genymotion as your emulator. Fast and easy to use. You just need virtual box to install it.
Please go to the SDK manager and check if the components have been downloaded properly or not.
You might need to remove and re-download them as this happens if the image was corrupted.
I just started getting something similar too.
If I set the scale option to 'Auto' everything works as intended. I assume Google have mode some changes but not updated everything properly.
Reinstalling the Android SDK worked. Took a few attempts to get it right. Had to uninstall and then reinstall. Picked x86_64 image in the end
Then I was able to go to my various virtual devices and use the Repair Device links as seen here to fix them:
I know this question has been asked multiple times on this and other sites but I still have no luck with dealing with this. So before I uninstall everything I want to see if there are anymore opinions.
Like the others I am trying to create (this computers) first AVD but have been presented with a greyed out 'OK' button. I have installed all of the latest packages, including the latest ARM package. I have restarted the software and computer to no avail. I have used AVD before but this is the first time it haden't worked for me.
Helpful opinions will be welcomed.
You must have everything selected, that includes at least 5 things:
a AVD name, a device, a Target API Level, a CPU, a Skin, the memory is mostly automatically filled and the SD Card is optional, so it looks like this:
I have eclipse juno 4.2.1 Android SDK already installed, I've created an Android application and while creating new AVD
the Ok button is always disabled although I've determined all it's specifications
here is the specifications I've entered
I don't know why
Any ideas!
Thanks.
No system Images You installed,
Go to window->Android SDK Manager, and download System images for avd for that specific target
You can check if you have any spaces in the "AVD Name".
just restart eclipse.Although you download it still needs a restart.
Look at the CPU/ABI section on your screenshot. It is clearly saying that there is no system image installed for the targeted version.
Go to SDK Manager and install 'ARM EABI v7a System Image' for your target version.
Hope it helps!
After I follow to above solution what I download the system image, but the disable of OK button cannot be reactivated by system image. I tried to refine the parameter setting that RAM is less than 758M bytes (less than hardware configuration) for HTC One X. There is alright to reactivate the "OK" button.
The program of SDK Manager is required to check the available RAM in your machine whether for the testing in simulation of SDK Manager. I tried to use less RAM size in ADV virtual device and then system can enable "OK" button instantly.
I just had to select a skin from the drop-down menu to enable the ok button.
Possible alternative solution
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.
I am having a problem similar to this question:
AVD Manager don't start
but I do not understand the answer and how it worked. I cannot find AVD anything, anywhere.
My AVD Manager had been working fine and well and then suddenly it stopped.
I am not 100% sure if it was working well before I added on the Kindle Fire emulator because I had already had some AVDs set up and didn't try to create a new one before I added this in.
I updated ADT and I am pretty sure it is an android configuration problem, not Eclipse.
Any suggestions would be greatly appreciated.
I had the same problem, then I realized I had Java EE running in the top left corner, not just Java. In the write hand corner, exit out of the Java EE and start a just Java one, and it will have the AVD Manager you seek.
Yep, I had this too. It is caused by a corrupted AVD image. I followed the instructions (and added a comment) to the below Google Code issue;
http://code.google.com/p/android/issues/detail?id=41024
Follow the instructions there and enjoy the remaining AVD insufficiencies... :S
The title pretty much says it all. I was making a simple Hello-world app and after having recompiled it a few times the newest versioned stopped showing upp in the avd. It was stuck with the same version no matter how many times i tried recompiling. After having uninstalled the app in the avd, relauched the avd a couple times, etc it started working normally again and updated for each recompile.
Now i just started a new project, added a few buttons and stuff to it and this problem appears again. No matter what I do, it just shows the state of a newly-created project without any editing. I.e with a textfield saying something like "hello*name*activity"
Edit: After playing around a bit more i.e. uninstalled the app in the avd, wiped userdata in the avd, restarted the avd, restarted eclipse, it still just showed the helloactivity-text instead of my app. Finally i rebooted my computer which "solved" it. Very annoying. I can especially imagine this being frstrating when you're not even sure if it's the new or the old version of the app shwing upp, like when trying to fix a bug.
Any idea as how to fix this issue?
Thanks in advance!
I have run into this with Eclipse's incremental updates, try a clean build, uninstall the app (I see you already tried this) from the avd and finally file a bug report.