Whenever I am trying to launch my emulator it launches but only the android logo is shown ,after waiting for many hrs also it does not work.
Device-3.2"QVGA(ADP2)320*480 (mdpi)
API Level-17
It's well known that the factory emulator is extremly slow. The trick here is that the factory emulator needs to run on an ARM machine, so it needs to convert the ARM calls to your your x86 (or 64 bits) processor calls. It's likely to never run fast at all. In this situation, you may want to trust on the factory x86 images that make use of Intel's HAXM drivers, not available to everyone, and I couldn't manage to make it work myself, but it's useful to know that.
However! Since a while ago, I started using Genymotion's emulators. They rely on an actual virtual machine, which is way way faster than anything a factory emulator could achieve. Even if I'm running it on the lowest Mac Mini out there, it's pretty smooth. I'd personally give it a try (well, precisely, I gave a try)
https://www.genymotion.com/
Try allocating more memory for it to use. The Android Emulator is super slow as it is, but if you are not giving it enough memory it has the ability to never load.
Google emulator uses ARM opcode, a kind of machine language. It must convert from ARM opcode to Intel opcode. That's why it's slow. The problem seems not to be RAM but CPU. Improving CPU will improve the emulator.
References to solve this issue:
Making the Android emulator run faster
If you are using your emulator in windows than you can use Microsoft Andriod Emulator.
Install microsoft android emulator in your windows os
If it is taking too much time in loading make sure you have installed the "HAXM installer" in SDK tools , Also make sure "Hyper V" option is also unchecked in "Turn Windows features on or off" in Control Panel --> Program and features.
Only After unchecking this feature you can install the HAXM installer.
After doing this the Emulator will not take time to load.
Try creating the Android virtual device with more RAM than usual. The usual is 1 GB. Even though I tried this on another lower end PC, it was still slow. I think it can be a problem with your hardware. Lower end hardware tends to have problems running emulators.
The problem seems not to be RAM but CPU. Improving CPU will improve the emulator.
Related
I am working on an android application, uing eclipse IDE. However it takes around 10-15 minutes to load my AVD and run the application.
My system Configuration:
RAM 8GB
intel Core2Duo Processor 2.53GHz.
OS: windows 7
Is their any alternative to increase our AVD's speed, without changing my systems hardware configurations.
You can setup an Android Virtual Machine using VirtualBox :
http://www.howtogeek.com/164570/how-to-install-android-in-virtualbox/
And to deploy to the virtual box :
android emulation on virtual box in eclipse
I tried this a while back and it was quite a performance improvement difference. I haven't done this in a while because I bought a pretty high end phone and I just use that now.
Is their any alternative to increase our AVD's speed
Using the x86 emulator will help.
That being said, your computer would appear to have issues. With that configuration, even the ARM emulator should take at most a minute or two, at least on Linux. Windows 7 perhaps adds some more overhead, but I would not expect it to be that much.
Also, bear in mind that you can usually keep your emulator open all day -- you do not have to exit and restart the emulator for most work.
GenyMotion have an Android Emulator that is pretty rapid. (not an AVD)
http://www.genymotion.com/
Genymotion is an emulator using x86 architecture virtualization,
making it much more efficient!
Taking advantage of OpenGL hardware acceleration, it allows you to
test your applications with amazing 3D performance.
It's free for personal use, has preconfigured devices (like N7 or Samsung GS3 etc).
I think you'll really like it.
You can select the snapshot options. On the first next start, a snapshot will be created. This will improve the launch speed of the emulator every other start...
Android Emulator takes from 15 to 20 min to start up and mostly crash thereafter on my Laptop no matter what kind of Android mobile or setup Im using. Im one a total lost on what i could do to make it run on a usable level.
Im running it in windows 8 on my labtop with 8 gb ram and a AMD quad-core on 1.6 GH.
Make sure you've installed the "Intel x86" system image for the API level platform you're using and then make sure your emulator is using that in the CPU/ABI dropdown in its configuration.
That will speed it up significantly over using the ARM image.
The only other thing you can try is to use snapshots, then you'll only have to sit through the long start up once. Snapshots have always been kind of glitchy for me though and I've stopped trying to use them, which reminds me, if you are using snapshots, try turning them off, that might help too.
This also happens to me when trying to run a full-spec device. I lower the specs and resolution quite a bit since I don't even have enough memory to allocate for a 1GB ram virtual device.
The first boot will take some time. You can configure your emulator to use snapshots which will speed up the boot time considerably. Look into running the x86 image which will increase the performance of your emulator. Keep in mind if you have any armeabi-targeted binaries, they will not work (not an issue for most people).
I have intel i7 quad core with 4GB of ram but when I try to run my app on the emulator, God it takes a hell lot of time. Some times more than 5 minutes. I am not emulating any game or graphics intensive thing. I am learning android so just trying simple aps but still it is very slow. Moreover today I found this emulator has stop playing any music or sound I used the in the programs, I made previously. What can be the reason of this weird behaviour and slow speed.
How can I fix it? I am on Windows 7
PS: when I try to type in an app from user keyboard, the emulator doesn't take any input unless I use the emulator keyboard. Can I change its settings to take input from keyboard.
Regards
Open android sdk manager, in extras, install "Intel Hardware Accelerated Execution Manager", and use x86 images (there are two available, one 2.3.3, one 4.0.3) provided by intel.
On windows, android SDK Manager only downloads the installer of IntelHaxm, so you have to go in and install it yourself. Usually you can find it under
android-sdk\extras\intel\Hardware_Accelerated_Execution_Manager and install IntelHaxm.exe as admin.
4GB of RAM imho is not enough, windows 7 and eclipse together takes more than 2GB out on my system. 8GB is minimum and the more the better.
The emulator has always painfully slow for me; I've never gotten any of the standard speed suggestions to work. However, if you have a device available, testing directly on it is much, much faster.
I have installed Android SDK on my computer. I have a intel i7-2600 processor and a Zotaxc 460 gtx fermi and 12 gb of ram. Basically saying, it shouldn't be running slow. Any suggestions on how to speed up the apis? or is it just slow?
Assuming you are referring to the Emulator and not Eclipse or something, you can speed up the Emulator a bit by choosing a smaller screen size for the virtual device, like HVGA instead of WVGA, etc. But that only goes so far. The emulator is just not very fast right now. They are working on it, however. I believe they show some of their early work in this Google I/O session.
If you mean the AVD (the android device emulator) is running slowly, then it is behaving as expected. Perhaps you have an android device you can plug in and run your app on? I would recommend you download developer drivers for whatever device your using instead of the bloated ones they try to get you to download.
Good luck.
Here is some usefull question that is about speed of android emulator:
Why is the Android emulator so slow? How can we speed up the Android emulator?
Eclipse performance can by improved by setting eclipse.ini. For example I have set -Xms512m
-Xmx2048m. Without this options, Eclipse has too few memory to open my project.
Disable the boot animation with -no-boot-anim, "Disabling the boot animation can speed the startup time for the emulator."
I keep wanting to use VitualBox for Mobile App Development, but I can't seem to get the emulator to run fast enough inside the already-emulated 32-bit machine.
Is there any way around this?
Now while it doesn't seem to me like there is an answer to this question, I figured I'd ask it anyway.
P.S. I have a 64-bit machine.
This should do the trick: 4 (or more) core CPU, plenty of ram (>4GB) and install the virtual operating system on a disk other than the one your main OS uses (e.g. firewire/esata external drive).
Another virtualization software might be faster too, but that I don't know.
You could use the x86 build of android in another virtual machine instead of the emulated arm of the current SDK one... (rumor is google is going to move in that direction anyway). Last I tried this, it booted/ran much faster than the arm emulator running on a physical machine, but the mouse emulation was painfully slow, maybe they've fixed that now.
(You have to set up adb over tcp manually or with your own script so that eclipse or whatever knows about this target)