At the moment I'm developing an application with Android wear support but I have no smartwatch. Now I want to test my application on an emulator but that is the problem. The emulator need up to 1.5 hours to start. I created one with following settings:
<!-- language: lang-none -->
Target Google APIs (Google Inc.) API lev 22
CPU/ABI Google APIs Intel Atom (x86)
Device 5.1" WVGA (480x800: mdpi)
Skin No Skin
RAM 512 //also tried with 768
VM Heap 32
Internal Storage 200
Use Host GPU true //also tried with false
I installed HAXM, enabled it in the BIOS settings and if run
sc query intelhaxm
I get the status 4 like it is written here. I set the HAXM memmory to 2GB so it should be enought. I also do not run any other VM software and I have even reinstalled my Windows. The only interesting information from the LogCat is that there are many lines (up to 70%) of Suspending all threads
My computer has the following Hardware:
<!-- language: lang-none -->
Windows 7 x64
Intel Core 2 Quad Q6600
8GB RAM
Do you have any ideas why my emulator is so slow?
EDIT: Here I posted the target for a smartphone device but it's also so slow for wearable devices so Genymotion is no real alternative because it has no images for them.
The Android Emulator is very slow. The main reason is because it is emulating the ARM CPU & GPU, unlike the iOS Simulator, which runs x86 code instead of the ARM code that runs on the actual hardware.
Toggle your ScreenSize and Monitor dpi to get a lower scale - it will increase your speed of loading and usage.. SnapShot can also be Handy
There are several options:
Reference: Source
Run Android Image in VirtualBox. http://www.android-x86.org/download
You can use the Intel x86 System images, I'm not sure but they might be faster
Note: I read somewhere that Anti Virus Softwares scan the Image of Emulator which make it slow. I need to confirm it.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With