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.
Related
I'm not able to change the ram size in the memory and storage section of the AVD manager in the android studio. I wanted the emulator to run a little faster (I have 8GB RAM). The controls are completely gray out.
If you create an AVD with "Recommended" system image then you can't change the "Memory and Storage" parameters neither when you create AVD nor when you edit your AVD.
Solution:
You should select your "Image" from "x86 Images" tab and then change "Memory and Storage" parameters in the next page.
It happened to me with an image with the pre-installed playstore app. Maybe it is an android SDK bug. Try to create one with no playstore app.
Look for your avd folder, then look for the folder of the image you want to change and edit the config.ini.
change the value of
hw.ramSize
Here is a solution for Android 4.1 that worked for me.
Create AVD as usual over AVD Manager
Open location on the disk where AVD data is saved
open the config file that is there over the notepad. Inside should be a line that starts with the hw.ramSize line. There you should change the number of MB you want. Save changes, close file.
In Android Studio click File > Reload All from Disk
If you select View Details you should see there that ram size is changed now.
I hope it will help.
You can do so by editing the config.ini file of the int the avd settings look for this
>hw.ramSize
Editing is disabled,but you can create a new virtual device by using Clone Device.. option.Once installation of OS is complete, edit the RAM again in Advanced Settings before clicking Finish.
Further adding to the answer by Fresher, it seems that even x86 images don't work(atleast its the case with my mac OS).
Here is the screenshot:
Advanced Settings:
What worked for me:
I just used "Clone Device" in Hardware selection wizard(the first one that opens after you click on the "AVD manager"
Then setup your ram here:
Once you hit "Finish", you will see your cloned device appear in the hardware selection wizard like this:
Then go ahead as usual.
just get the emulator whith api which has no google play from x86 images,just set your ram size, then change image to the api which has google play it has worked for me
creating
changing ram size
changing android image
selecting android image
It has worked and I have play market
I can't change the graphics to software as I'm sure this is the fix for my AVD not launching.
The option is greyed out (see screenshot). Has anyone has experience with this? I couldn't find anyone who had the same issue.
I'm running the latest version of Android Studio on Ubuntu 17.04.
Actually, this problem seems to be limited to devices with Play Store available, so Nexus 5X and Nexus 5 images will be forced to use Automatic Graphics, but all other devices allow you to choose either Automatic, Hardware or Software graphics.
edit: I've just tested this today and it seems to no longer be the case. At least on MacOS with Android Studio 3.3.2, I can now make a Nexus 5X image with Play Store and Hardware Graphics. I'll do more testing at home later, on Windows and Linux to see if it's related to OS or graphics drivers.
I also think it's related to whether the Playstore is contained or not, but I cannot explain why.
Dielson Sales already gave the answer which worked for me - unfortunately only in a comment to this answer. I just thought it's worth to make a "real" answer out of it:
Edit the config.ini file of the AVD. Under Linux it's located under /home/<user>/.android/avd/<AVD-name>/config.ini
(in my case <AVD-name> is Nexus_5X_API_29.avd).
In a text editor change the lines
hw.gpu.enabled=no
hw.gpu.mode=auto
either to
hw.gpu.enabled=no
hw.gpu.mode=off
or to
hw.gpu.enabled=yes
hw.gpu.mode=host
This setting remains even if opened in the Android Virtual Device Manager of Android Studio. It's just not editable there.
I also tried this, which I found in another AVD:
hw.gpu.enabled=yes
hw.gpu.mode=software
But this is then changed to "no" / "off" by the Android Virtual Device Manager.
I didn't look any further so far. hw.gpu.mode=off worked for me. Otherwise my whole Kubuntu hangs (using the Nouveau driver, not the NVidia driver)
Seems like the problem was with the choosen VM. If I choose a Nexus 4, it runs just fine.
I am little late on this thread but following are my findings and solution. I am using Ubunut 18.04 and faced the same issue. The solution is to edit AVD and under Emulated Performance, change the grpahics to Software. The problem was that this option was disabled for me. I was unable to change graphics drop down.
I did some more research and found that while creating AVD if you choose default/existing device definition on first screen, you will not be able to edit graphics drop down.
The solution is to create a "New Hardward Profile" while creating AVD and use your new profile. Now, you will be able to edit "Grahics" drop down.
Hope this helps....
It seems all emulators with Play Store cannot emulated performance. I am using AS 4.0
Open Android Virtual Device Manager Android Studio, change VMHeap to 512, RAM to 4096 MB. Then restart Android Studio.
I think It's just a bug!
Solved the issue by selecting any virtual device had the option enabled and after finishing the installation I just clicked on edit and reselected the device I wanted and the option was still enabled.
Click on edit button from here.
Then change the device to the one you want.
For those who are still searching for solutions on how to make it work with an image containing google play store: install / update your GPU drivers solves the problem. On my Ubuntu 20 this was the issue.
I'm working on mac os - after i upgrade my os my emulator stoped working and one of the solution was to change the graphic settings from hardware to software - since i couldn't - came here ---> turns out Android Emulator HAXM on macOS High Sierra is left out from security reasons
follow this link : https://developer.android.com/studio/known-issues#deploy
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.
I'm running Eclipse Juno 4.2 on Ubuntu 12.04 32-bit, with all Android SDK versions installed, android plug-in for Eclipse up to date also.
I've been reading some android tutorials online and I see that the AVD Manager (the Edit AVD screen only) looks a bit different comparing with my version:
On mine are missing the Hardware settings at the bottom of the screen.
In addition I don't have the options to change the screen resolution also.
Does anybody experience the same? Is it because of the OS (in my case Ubuntu), or the new version of ADT doesn't have these settings any more, or is it just a bug?
I would like to post images but for some reason the editor doesn't let me do it, it keeps displaying an error that I need at least 10 reputation.
Is it because of the OS (in my case Ubuntu), or the new version of ADT doesn't have these settings any more, or is it just a bug?
AVDs created using the newer version of the AVD Manager use the Device Definition tab for the things you seek. There you can create new devices, and when you create an AVD, you choose the device you want from the Device drop-down.
I would like to post images but for some reason the editor doesn't let me do it, it keeps displaying an error that I need at least 10 reputation.
That is because you are new to StackOverflow. Feel free to upload images elsewhere on the Web and link to them from your questions.
I'm using the Eclipse IDE (Juno 4.2) and the latest Android/Google ADK.
The ability to load/use custom skins seems to have disappeared. When creating a device in the AVD (android virtual device manager), it was possible to specify a skin from drop-down {skins had to be loaded into the sdk/android-##/skins}. The directory(s) are still there but adding skins does not allow/permit selecting it in any part of the virtual device creation process.
I'm running Eclipse Juno 4.2 on both a windows and mac os.
developer.android.com docs still show UI that for selecting custom skins.
Is is possible to still use custom skins is there now a restriction on skins?
The only way I've found to do this is to manually edit the config.ini file for your AVD. Change the field "skin_name" to the name of the skin you want to use and change "skin_path" to the path to the skin, relative to the sdk directory.
So if your skin was part of an SDK add-on, an AVD config.ini that looks like this:
skin_name=1280x800
skin_path=1280x800
Would be changed to:
skin_name=MyDevice
skin_path=add-ons\addon_device_vendor_api\skins\MyDevice
Or in your example:
skin_path=platforms\android-##\skins\MySkin
The Docs don't appear to have been updated for revision 21 of the ADT yet, so maybe they'll have more information in the future. I'd really like to know if there's a way to do this from within the Device Manager, but this is the only way I've found to do it.
After Update your ADT to version 21.
In Older Version each time you have to set Add Custom Screen if you want custom Device Configurations.
In ADT21 Oversion you can get this thing done by
open AVD Manager, u can define your custom screen in "Device Definition"
Alternative (Much Easier approach)
in Newest Version you Don't Need to Set Custom Device
Configurations from the above Suggestion as much easier way is available for it. you >Just Have to Make Emulator With your Device
Configurations and after you will see those Configurations with
Emulator Name Inside Graphical Layout of XML
like after Created my Emulator of Nexus7 Emulator with Android 4.2 with Name as "Nexus7_Android_4.2" i will get this Device Configuration in Graphical Layout of xml automatically.
Below is the Screen Shot of it.
Hope it will Help you.