Android Emulator so slow

Question

I know there has been quite a few posts on this but all the solutions given in these posts have not worked.

I made a Android 3.2 emulator and am trying to run a hello world application. I set the device ram size to 1024(any bigger and the emulator will crash and give this error)

Failed to allocate memory: 8
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I am on windows 7 64bit edition. As I said I am trying to run a hello world application that. I tried to use the snapshot feature to make it load faster but the emulator sits on the "android" logo page for like 5 minutes.

Even once the emulator loads up and I try to click around on backbuttons and other default applications on the emulator it is like a slideshow.

The solution is to plug in an actual Android 3.2 device. Sucks, I know. — Matt Ball, Jul 27 '11 at 21:48
I would invite people to try this option: http://stackoverflow.com/a/17394245/1204249 — amp, Jun 30 '13 at 19:52

score 4 · Accepted Answer · answered Jul 27 '11 at 21:48

unless you really need some of the new functionalities of 3.2 I would recommend you develop on an earlier sdk... I personally use 1.6 and 2.1 for most of my apps and the difference in load time and general emulator speed is enormous.

EDIT: especially considering you are only writing helloWorld at this present

score 1 · Answer 2 · answered Oct 22 '12 at 21:56

1

Please try 896 instead of 1024. It seems like a bug with 1024 value.

answered Oct 22 '12 at 21:56

Dmitry Sobolev

927
15
18

no it's not a bug with 1024 value, I've tried 512 and 896 and it's still taking ages to load – Varda Elentári Feb 23 '13 at 16:00

score 1 · Answer 3 · answered Jul 27 '11 at 21:50

I had this exact problem. I thought it was my hardware but I got the latest emulator and it still sometimes crashes but by taking a snapshot I've got my loading times down from 10 minutes to 1 minute.

I'd verify those times, and give you my version numbers but I run it off of external storage and it seems I've since uninstalled Java :(

It was working with the last release about 6 months ago. The rush to update Android SDK stopped about that time too, as I recall.

score 0 · Answer 4 · answered Feb 28 '13 at 10:12

If you are using the ADT Bundle for development, then go to AVD Manager and select Device definitions tab on the top.

Then click new device button and create a new device with minimum resources. And create a new virtual device with the newly created device.

It will work like a charm. I dont know the exact reason why. but it works for me.

score 0 · Answer 5 · answered Sep 17 '13 at 20:58

Try Android x86. It's much faster than the Google Android emulator. Follow these steps:

Install VirtualBox.
Download the ISO file that you need.
Create a virtual machine as Linux 2.6/Other Linux, 512 Mb RAM, HD 2 GB. Network: PCnet-Fast III, attached to NAT. You can also use a bridged adapter, but you need a DHCP server in your environment.
Install Android x86 on the emulator, run it.
Press Alt+F1, type netcfg, remember the IP address, press Alt+F7.
Run cmd on your Windows XP system, change the directory to your Android tools directory, type adb connect .
Start Eclipse, open the ADT plugin, find the device, and enjoy!

edwindh · Answer 6 · 2014-07-28T20:02:34.227

0

I have the same problem too, but using the android emulator is very low, another option is to emulate a device using a Virtual Machine.

In this case, you have to install Virtual Box, then download an ISO file (android 4.4 RC2) and the proceed to install and configure. In my opinion it is a better way to test your app.

http://edwindh.blogspot.com/2014/07/emular-uma-tablet-ou-smartphone-com.html

edited Jul 28 '14 at 20:02

answered Jul 21 '14 at 20:04

edwindh

99
1
4

Android Emulator so slow

6 Answers6