I've seen this question around stack overflow. Tried various solutions and none work for me. Lowered the RAM size, changed VM Heap size, made sure I have Intel x86 Emulator Accelerator (HAXM installer) installed but nothing works. Some people recommend Genymotion but I think there's an annual fee.
Only the original AVD that came with Android Studio works, NEXUS 5X API 24.
I added a new Nexus 6 API 21 AVD and it doesn't load past "android" load screen. I made a custom AVD and it doesn't load as well pass "android" load screen.
All 3 AVD's run on x86 CPU/ABI and 3GB size on disk.
The only difference is the NEXUS 5X AVD uses Nougat Android 7.0 x86 while the custom AVD and Nexus 6 uses Lollipop Android 5.0 x86 because I want to develop app with Screen Capture.
So what can I do to make the emulators work?
Related
I'm having some issue with Android Studio's Android Virtual Device (AVD) emulator. I can build and run my apps but the emulator is never properly displayed, as I can't even see any emulated device at all. I've tried different graphics drivers, different graphics (dedicated vs integrated), different Android devices, re-installed Android Studio and it's components, re-installed Intel HAXM multiple different ways, and still nothing. I'd try a different version of Android Studio but I need this version for a class I'm taking this semester. Anyone got any tips?
Device Info:
Dell XPS 15 9550 Signature Edition; BIOS 1.13.1
Windows 10 Educational 1909 Version 10.0.18363 Build 18363
Intel Core i7-6700HQ CPU
NVIDIA GeForce GTX 960M GPU
Toshiba NVMe THNSN5512GPU7 NV 512GB SSD
16 GB DDR4 RAM
Using Android Studio 3.5.3, Android Emulator 29.3.4, Android 9.0 and 10.0, and Intel x86 Emulator Accelerator (HAXM installer) version 7.5.4.
I can supply more troubleshooting info upon request but I left it out in the post as I think it scared people away from my question last time I included it.
When I create a Virtual Device in Android Studio, it takes 4+ GB of disk space when freshly created with the default settings. It normally takes between 500MB and 1.5GB as I could see on some other questions related to Virtual Devices and the screenshots of the official Android documentation.
Here's a screenshot of my devices when freshly created with default settings:
My Virtual Devices
As you see, the Pixel phone is taking 4.5GB of space and the Nexus 5X is taking 4.3GB.
Also, we did exact same process with a colleague and here's a screenshot of her freshly created Virtual Devices:
My colleague's Virtual Devices
As you can see, in her case, the Pixel phone is taking 503MB and the Nexus 5X is taking 1.1GB.
We both used the same default settings as you can see here:
Virtual Devices settings 1
Virtual Devices settings 2
We both have the same platforms:
MacOS High Sierra 10.13.6
Android Studio 3.1.3
Does anyone have idea of what is generating this oversizing on my Virtual Devices?
Thanks for your help.
Today i accidentally solved the issue. I needed to perform some updates on the Android Studio while installing some libraries and i updated:
Android Platform SDK 28 (which was the one i was using for my Virtual Devices) to Revision 6 and the Google APIs Intel x86 Atom System Image for that SDK to Revison 5.
I also updated the Android SDK Platform Tools to 28.0.1, the Android SDK Tools to 26.1.1 and the Intel x86 Emulator Accelelator (HAXM Installer) to 7.3.0.
Then, i needed to test on another Virtual Device and it was created and ran starting at 1.0 GB. So i decided to delete my current devices and create them again after this update. I created once again the two Virtual Devices that are show above on the question and the results were the following:
Pixel phone -> Now starts at 1.0 GB
Nexus 5X phone -> Now starts at 1.1 GB
Which is four times less than before the update.
So, basically, the solution and recommendation is to try to keep everything up to date! :)
I'm new to developing an Android App using Android Studio. I've been following this example app on their website: https://developer.android.com/training/basics/firstapp/running-app.html#RealDevice
The problem is, when I try to run using the emulator or my real device (Samsung S5) using the instructions on that link, I still couldn't find my device. I get an error when using the emulator that would take 10 minutes to load on my 2 GB RAM computer (only to fail).
emulator: WARNING: Crash service did not start
emulator: Classic qemu does not support SMP. The hw.cpu.ncore option from your config file is ignored.
Cannot set up guest memory 'android_arm': Invalid argument (in red text)
Other considerations:
1. My processor is AMD and not Intel, so the Intel x86 Emulator Accelerator (HAXM installer) doesn't work for me.
2. I used the Nexus 5 emulator device with API level 21. I tried it with Nexus 6 emulator device with API level 23. No luck on both.
3. I've placed my Samsung S5 device on Debugging Mode but it never showed up on the "connected device" area when running the app.
I've searched for other questions relating to it. But my luck has run out. The fact that I got a slow computer adds to the bad luck.
You might be experiencing these problems due to allocation of excessive amount of RAM for the virtual device which wont be available for the device.
set it to something like 1024MB or 768MB and try again.
I usually use 3 emulator to test the apps (JB, KK and Lollipop). But now I am using my Surface Pro and I can't use a lot of emulator. Then I only use my real nexus 5 device but it is a problem because I am using code for v21 and v19, and I can't test v19.
Is it possible to install the app forcing the v19 in my Nexus 5 with Lollipop?
no.
the nexus 5 with Lollipop is a Nexus 5 with Lollipop (API level 21).
your choices are:
struggle with the emulator on a slower computer
buy another device for testing
buy/use a faster computer
flash the factory image of KitKat on the nexus 5 from here: https://developers.google.com/android/nexus/images (not great option in my opinion)
The only solution would be that when creating a new emulator, you can select x86 in the ABI column which would use Intel HAXM to run the emulator faster.
You can use GENY MOTION ,It is faster then your emulator and its free for personal use.
You can find it there https://www.genymotion.com
I am a new learner of android development .When I was creating an AVD then it said that "on windows emulating RAM greater than 768M may fail depending upon system load.Try progressively smaller values of RAM if the emulator fails to launch" . respective screen shots are as fallows :
warning
stuck:
I tried to decrease the RAM size after that and tried 400 instead of 1024 but it couldn't open the AVD home page .I waited more than one hour but all in vain .I am using Android 4.4 API level 19 .I don't know why this happening and stuck at this situation.I want to know that where is the problem ,why it's not running .My PC configuration is :
OS: Windows 7 RAM: 2 GB Processor : Core2Duo
AVD is quite slow at times. Tips to speed it up significantly:
Download the Intel x86 Atom System Image from your Android SDK Manager for API 19
Then download and install
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
If you have a graphics card I would try to enable Host GPU option
Example settings for your AVD:
- CPU/ABI: Intel Atom (x86)
- Emulation Options: Use Host GPU