I have an older AMD processor with integrated graphics (AMD Athlon II x4 640) and the android emulator runs really slow. The integrated graphics don't work with the "Use Host GPU" option and I can't use the faster Intel system images because I have an AMD processor.
I have heard Genymotion is faster but I can't use it since my integrated graphics don't support OpenGl 2.0+.
What would be the best upgrade: getting a graphics card or getting a new computer with an Intel processor?
A physical mobile phone connected via USB is faster than the emulator running on a amd rig. My current budget forces me to test this way but hey there mobile apps might as well do some testing when I'm out and about.
I apologize in advance for recommending a purchase of a product which is not allowed but you can get a decent inexpensive no contract phone in the US a lot cheaper than a new intel rig.
You can do following steps to speed up Android Emulator
1)Install HAXM in your SDK manager>Extras>HAXM.
2)Create Lower RAM Size Emulator if you have less RAM in your computer.
3)Close Other Unnecessary Process from TaskManager while you are running Emulator.
4)Use less Screen density(ldpi,mdpi) at the start.
5)Increase RAM of Your Computer Emulator will speed up.
6)Update your sdk with latest update
Related
When I first started using the emulator than came with Android Studio, it was running very sluggish even with HAXM enabled. I decided to play around with the RAM allowance along with switching between the Software and Hardware option but no dice. I decided later to install Genymotion due to the good reviews and it runs as slow as it does with the other emulator. I've also checked to see if Intel VT was enabled and it was. I also don't run any major applications during the emulation.
I've tried a number of methods and I've yet to find and fix this problem of the poor performance of these emulators.
The processor I'm using is a quad core i5-6300HQ with 8 gigs of ram and a GTX960M graphics card. Windows, Genymotion, and Android Studio (with its SDKs) are all installed onto an SSD.
Is there a method of fixing this that I've missed?
Thanks.
The Resolution I'm using is 1440x2560.
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.
Well dont know for sure but all the native emulator in android are very slow.
I suggest that you use the Genymotion which is very faster emulators for android than native.
It will give you user experience almost as of devices though it does have the same limitation of android native emulators.
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:
One option is the Visual Studio Emulator for Android--it's fast, Hyper-V, x86, and free when you install Visual Studio 2015 (currently in Preview; free download).
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.
One thing i figured out about a slow AndroidX86 in a VirtualBox...maybe it help you.
I have an older system. A Board with a P45Express chipset and only a dual core [E8400].
I have two 1 Gig LAN Ports on my Asus P5Q Deluxe Board [iam connected cia cable to my router]. One is working through the Northbrigde, the othe one works over a PCIe Lane. Since i use the PCIe Port, my AndroidX86 runs alot faster.
Before, when i used the NB supported port, it took me minutes to get a stable connection to the www. It looks like that the VM slows down hard, if the www connection is not supported by a good mainboard connection.
I dont use 3D accleration,i use VBoxSVGA and only PAE/NX and "Nested Paging".
Maybe that can help you abit.
Sorry for my bad english :/
1.Make sure you are using 64-bit operating system.
2.Use host GPU while starting Emulator.
3.Update you graphic drivers if u have graphic card
If you want to make the Android emulator faster and more responsive, you can configure it to take advantage of hardware acceleration. View this link for more details.
Configuring Graphics Acceleration
Try this configuration:
CPU/ABI: Intel Atom (x86);
Device: Nexus 5;
Keyboard: Hardware Keyborard present;
Skin: Skin with dynamic hardware controls;
Ram: 2048;
VM Heap: 64;
Internal storage: 200 MB;
SD Card: 500 MB;
Emulation Options: Use Host GPU;
You have not described which IDE you are using for development. I use Eclipse and with this configuration the emulator go up very fast. Maybe if this won't fix your problem try to use Android studio and the relative emulator which should be better (with the same configuration.
I was experiencing the same issue and almost give up on learning android until I found Genymotion. It is highly recommended.
One cause can be old HAXM driver:
Update here:
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
Mine was very slow with 6.0.1 but fast with 6.1.1
My Android emulator runs painfully slow on my PC so I was thinking about installing Ubuntu on a virtual machine and running the AVD there. Do you think it would be faster if I did so?
you have two solution.
one, you install AndroVM on VirtualBox.
AndroVM
this way is very faster, but bit difficult to setup and controll.
other way is create AVD which is made in Intel x86.
Configuring the x86 Emulator
this way is very fast too.and setup and controll is very easy compare to general emulator.
but this way require CPU which support Intel VT / AMD-V
both way is good,please choose you like :)
I would put my money on Linux - as it has less of a footprint OS wise.
On the other hand, Windows is by far more used, so if they've developed it and put time into the one that is used the most, it could be Windows.
As a side note: there are several new android emulators that run on windows, some I've seen actually interface with the hardware (this avoids a layer of abstraction).
If your concerned with speed, you will get better performance with less programs running as the emulator is process intensive. (My i7, 8gb ram, is usable for developing - though nothing beats a device... Or nexus for that matter)
To connect to your computer: Debugging on my phone (Eclipse, Android)
I do not know what to do. I purchased a new laptop, hp pavillion i5 6GB RAM, started Android 3.2 emulator and it is still as slow as unusable!!!
It's not that it is slow, it's that I cannot do anything.
I set 1GB of RAM, disabled camera on emulator and run it. When I click on Applications, they first load for 30s and then I am not able to start any app, not mine, not default ones. All I can do is return to desktop and open Applications menu.
I see people complain that the emulator is slow and I am not even able to make it run. What is worse, my laptop eats games like a sandwich, but it chokes with Android emulator 3.2. The same is with Android 3.0 emulator!
Can anyone help me set up the emulator so that I can run it on my machine?
PS. if you want, I will record a video and post it to visually see what I am talking about.
I do not know what to do. I purchased a new laptop, hp pavillion i5 6GB RAM, started Android 3.2 emulator and it is still as slow as unusable!!!
The Android emulator uses a single core. If you had gone with a Core i7 with Turbo Boost, that would have helped. Your Core i5 is not an especially powerful CPU on a per-core basis.
The Android 3.x emulators also do all graphics purely in software (no hardware graphics acceleration) and convert ARM instructions to x86 on the fly.
Can anyone help me set up the emulator so that I can run it on my machine?
Start by using the Android 4.0 emulator, with the latest Android development tools. This uses your desktop's GPU for graphics rendering, and it helps performance a bit.
If that proves insufficient, you can start switching to x86 emulator images if you are not doing NDK development (where you will tend to want to test on ARM). At the moment, the only official x86 image is for 2.3.3, but there is an unofficial one for 4.0.3 built from the AOSP that runs exceptionally fast (at least on Linux, haven't tried it on Windows).
My only suggestion to you would be to change the "ADB Connection Timeout (ms)" in Eclipse under Window->Preferences->Android->DDMS. I am using a HP Pavillion 486 laptop, and was really struggling with the emulators. I changed the default timeout value from 5000 ms (5 sec) to 60000 ms (1 minute). This didn't solve all of my problems, but it did help in the startup of both the emulator and my applications.
My current laptop has Intel Core2 Duo P9500 #2.53GHz with 4GB memory. Running android emulator on Eclipse is quite a pain (very very slow). Any recommended/minimum system requirement for android developers out there?
Right, it does not have a stand-alone graphics card, it has embeded Intel Graphics Media Accelerator GM45.
A faster processor and hard-drive should help.
Honeycomb will run slow on any computer. But, no matter what you are using, shrinking the resolution of the Emulator/AVD a bit can help.