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:
Related
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
I installed a fresh api 19 emulator (x86 variant) and it doesn't get past the splash screen. someone told me that sometimes it gets finicky that way and I should delete the device and create a new one, so I tried doing that but it goes back to the same problem, infinite "android" splash screen.
how do you diagnose stuff like this? I have several other, newer emulators and they all work.
I have the device frame off just to make sure it is not that.
It is using the 5x as the basis for the device.
I increase the heap size to 256mb, and the ram to 2gb, but otherwise don't change much.
Try changing the graphics mode from Hardware/Auto to Software:
Go into the AVD Manager, select the Virtual device, and click "Edit"
Find "Emulated Performance" -> Graphics, and switch that from auto (or hardware) to Software.
It will not perform well compared to in Hardware mode, but it may give you insight into what is causing the problem if it runs this way. Hopefully Google/Jetbrains will get that figured out in a future update.
I ended up posting a bug report. The bug has been confirmed, given medium priority, and a work-around solution has been outlined which I can confirm works.
I recently had to reinstall Android Studio as a last ditch attempt to fix the "java_find.exe not found" bug. Unfortunately, this new build seems to have a radically different AVD interface that makes me unable to configure a lot of aspects of my virtual devices that I would have been able to with the original format and worse seems to only create emulated devices that never progress past the boot-up screen. After an extensive amount of google-ing I seem to be the only one on the planet who has this interface, so any explanation or advice would be massively appreciated.
(EDIT) Here's an image of an emulated device I just made. For the API I have no other option other than different versions of 21. In this case I chose the first option.
However, the same problem still persists where the emulator never progresses past the android screen. (It's been running for 10 minutes now when before my emulators would start in less than two.)
I've also just noticed this error hidden way in the bottom left corner of android studio.
"Could not find a matching system image for ABI x86, API 19/null: Could not find a matching system image for ABI x86, API 19/null"
Could this be related at all?
After an extensive amount of google-ing I seem to be the only one on the planet who has this interface
Fear not! I have the same screen. I installed android studio last week and I'm on the Beta version 0.8.14
Unfortunately, this new build seems to have a radically different AVD interface that makes me unable to configure a lot of aspects of my virtual devices that I would have been able to with the original format and worse seems to only create emulated devices that never progress past the boot-up screen.
I just created an AVD for the sole purpose of trying to recreate the issue. I created an AVD with a Nexus 4 and api 19 (kitkat 4.4.2), then booted it by pressing the play button in the Actions area.
It did take a couple mins (~4) but eventually it booted and now works fine.
any explanation or advice would be massively appreciated.
Explanation: sadly don't have one
Advice: reinstall and see what happens. Or show me your actual virtual devices screen so I can try and reproduce your errors.
Edit
I created a new AVD with the same specs as yours, and it booted fine.
Do you have these system images installed? (in SDK manager) or at least the one(s) you are trying to use for your AVD
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 looking to create AVDs to test my apps on, and i'm trying to figure out the correct settings for a square screen such as the new Motorola Flip Out. I don't see a wikipedia article for it, or many specs...
On a related note, what about tablets? Actually.. Why aren't there a set of AVD instances with params from popular devices.. or at least a site that lists them for each of the 60+ devices.
Thanks in advance :)
The Motorola Flipout has a 320x240 screen.
For the specs of many other phones there are quite a few sites where you could find all the details. For example phonearena.com is one of them.
At the risk of getting another dubious badge for resurrecting old threads, I'll give the semi-official Motorola response... :)
Nearly every Motorola handset is accompanied by an SDK addon that includes a system image and a skin. In a few cases, the addon contains only the skin. Just download the archive and make sure the top-level directory of the archive is in into /addons. After that, you should be able to create new AVDs based on the addon. I find that it's a lot easier to use the GUI AVD Manager than a command line, but both are usable.
Download the addons at http://developer.motorola.com/docstools/tools/
Good luck.