Im trying to run an Android Emulator on Android Studio with Graphics: Hardware-gles 2.0, but when i turn it on, Android Studio shows me the following message:
But, when i set graphics: Software-gles 2.0 it works fine.
I would like to use hardware acceleration, but I am willing to work with software-GLES 2.0 if necessary.
My computers specs:
AMD ryzen 7 2700x (Hyper-V ON, SVN ON)
NVIDA 1660 super Gigabyte OC
16 GB RAM DDR4
Windows 10 21H2 64 bits
Motherboard is ASUS ROG-STRIX b-450f
Adittional info:
I have already updated the emulator and every option in the SDK manager
apparently, it does work correctly with API 28 devices, but not 29 or 30
I have tried to run the emulator via powershell, and this is the output:
PS C:\Users\andjo\AppData\Local\Android\Sdk\emulator> ./emulator -avd Pixel_XL_API_29
INFO | Android emulator version 30.9.5.0 (build_id 7820599) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
INFO | added library vulkan-1.dll
Thank you for your attention!
Related
I install android studio following android docs instructions. I run emulator and after about 10 minutes I see this error or this error. After that I tried some configurations, I change emulator RAM and heap size, turn on GLES 2.0 software and hardware. And all works good when I increase RAM to 4096mb, increase heap size to 2048mb, select cold boot and run emulator from console by command ./emulator -avd Pixel_3a_API_33 -gpu host. And when after that I select quick boot again emulator work very slowly.
Hardware:
Ram: Netac 16gb 3200mhz
APU: AMD A10 9600P
OS: Fedora 36 and Fedora 37, I tried both systems
I expect that I will be able to run emulator in android studio not in console, and with quick boot on Fedora.
I just installed Android Studio yesterday. I have all of the latest versions for the emulator, studio and adb.
I created a new emulator using Android Q API 29 arm64-v8a (Android 10). When trying to launch this I am getting The emulator process for AVD Pixel 5 API 29 has terminated.. I am not sure what the issue is. I have tried the following.
Adding advancedFeatures.ini
Making sure I have enough HDD space
Restarting
Making sure everything is up to date.
When launching from the terminal I get the error:
C:\Users\User\AppData\Local\Android\Sdk\emulator>emulator -avd Pixel_5_API_29
INFO | Android emulator version 31.2.10.0 (build_id 8420304) (CL:N/A)
PANIC: Avd's CPU Architecture 'arm64' is not supported by the QEMU2 emulator on x86_64 host.
I am not sure what to do at this point. Not sure why Android Studio would offer these if the program cannot run it. I am on a Samsung S9+ and I am trying to develop using the same architecture.
look at BobMorane's answer
https://stackoverflow.com/a/71216466/19299549
#ifdef __x86_64__
if (sarch == "arm64" && apiLevel >=28) {
PAPANIC("Avd's CPU Architecture '%s' is not supported by the QEMU2 emulator on x86_64 host.\n", avdarch);
}
#endiF
My Android emulator runs very slow on my Ubuntu machine. I need it to run faster, because some apps are slowed down so much, that they change their behaviour (they use the camera).
System specs:
-x86_64
-Intel(R) Core(TM) i7-5600U CPU # 2.60 GHz
-20GB Ram
-512Gb HDD
I use Ubuntu 20.04 and Android Studio 4.1.1 (fresh installation).
I use this AVD: Pixel2 1080 x 1920: 420dpi API 28 Android 9.0 (Google X86_ARM) CPU/ABI: x86
In the extended menu I chose Graphics: Hardware - GLES 2.0. I also disabled GPS, audioInput and audioOutput with no performance improvements.
I did not try this, because selecting Hardware - GLES 2.0 worked for me and the avd started normally (but still very slow).
Other system images are equally slow though.
I tried:
sudo modprobe msr
sudo rdmsr 0x3A
and it returns 5, so VT-X is enabled
Is the hardware the bottleneck, or is something configured wrongly? Maybe it is the HDD that slows the emulator down? I tried running the emulator on Windows and it's insanely fast. The windows machine is stronger though.
Update 11.12.2020:
I also verified my KVM installation using this command:
./emulator -avd Pixel2Api28Arm -accel-check
It returned this:
28Arm -accel-check
accel:
0
KVM (version 12) is installed and usable
accel
So this does not seem to be an issue.
I was having the same problem (KVM working, but slow x64 emulator on x64 host), and found a solution here, which is to disable automatic snapshot creation.
Run your emulator, and click on the three dots (...) to open the settings:
In the settings, click "Snapshots":
Switch to the "Settings" section on top:
Set "Auto-save current state to Quickboot" to No:
It'll ask you to restart the emulator, click Yes:
My android emulator showing error & not opening.
If someone helped, I am very thankful.
Emulator: WARNING: unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
Emulator: Unexpected feature list: MultiDisplay VulkanNullOptionalStrings YUV420888toNV21 YUVCache
Gradle build finished in 11 s 518 ms
ADB rejected shell command (getprop): closed
Emulator: Process finished with exit code -1073741819 (0xC0000005)
I had the same problem, you have to update your emulator in sdk manager:
1.launch sdk manager
2.settings->appearance and behavior->system settings->android sdk
3.SDK Tools
Update Android Emulator
I have Dell G5 5587 with Win10 and I have exactly same issue from yesterday morning. After some updates to Android studio emulator stop working and crash on start up. I was trying to install Android.Q (API 29) x86 and x86_64 versions everything without any success. I try to change GPU to auto, software, hardware, change amount of RAM and all with the same crash result.
Unfortunatelly I can't say what to do to resolve the issue but i try to install new Virtual Device with Android Pie (API 28) with default settings and it's working so at least I can continue with my work till issue is resolved.
Based on the error message I think it's connect somehow to graphic card itself (I have Nvidia Geforce MAXQ 1060) or graphic drivers (notice that nvidia control center icon suddenly disapper from startup icons).
This happened to me when I was trying to run the API 29 emulator with Hyper-V instead of HAXM. To work around it, I turned off Hyper-V and installed HAXM.
29 is partially installed and we can do nothing about it except to wait for the big update...
I am trying to start the emulator in Android Studio, but for some reason it won't turn on. I've installed HAXM and invalidated caches and restarted AS but it still won't work. It is stuck at "Waiting for target device to come online". This is the response I get:
Hax is enabled
Hax ram_size 0x60000000
HAX is working and emulator runs in fast virt mode.
emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
09/19 16:25:06: Launching app
Error while waiting for device: Timed out after 300seconds waiting for emulator to come online.
What else can I do?
EDIT: My PC specs:
Windows 10 Pro x64
Intel(R) Core(TM)2 Quad CPU Q8300 # 2.50GHz 2.50GHz
8.00 GB RAM
NVIDIA GeForce GT 610
190GB free space
Under Android SDK Manager you have to install Intel x86 Emulator Installer there. Android SDK Manager
check it out also:
Error in launching AVD with AMD processor
First, click on File -> Invalidate Caches/Restart.
If this solution is not working, try to update the build.gradle of your project.
For example, update the compileSdkVersion to 25, (the supports libs to 25), the buildToolsVersion 25.0.2 and the targetSdkVersion to 25. Don't forget to sync your gradle after that.