I am new to android development, and I am having problems with Android Studio and the emulator. Both running together slow both systems to a crawl. My machine has Windows 10 Home and Linux Mint KDE 18.2 on it.
I have been trying to get it to work on both OSes. On Windows 10, I have 4gb of RAM, HAXM installed, and everything closed, it is somewhat usable (not much).
On Linux, I have 10gb of RAM (because of swap space). On KDE, it does not work at all. On fluxbox (with everything else closed), it is doable, but still slow.
In Android Studio (on Linux), I have increased the VM heap to 2gb, and enabled offline gradle work. With the emulator, I am using the Nexus 5x emulator (api v. 7.1.1, x86_64) with the device frame turned off, the RAM at 1024, and the heap at 256.
On Linux, memory does not seem to be the issue; when I open a system monitor, it shows both processors running at 100%. Basically, what can I can I do now?
If anyone needs any more info, just ask. Thanks in advance.
Edit
I did see this question: Why is the Android emulator so slow? How can we speed up the Android emulator?
This question is about the android emulator w/ eclipse. Also, I have tried the suggestions in that post. The suggestion I would like to do (use a snapshot) does not seem to be present in Android Studio (v 2.3.3).
Related
I am facing the same problem. I have ASUS ROG 17 inch Laptop, 16GB RAM, i7 processor, nvidia graphics card 3gb RAM , Windows 7 Home Edition service pack 1, Android studio 3.62, HAXM 7.56, Android Emulator 30.0.5, Android SDK 29.0.6. When I starts my emulator, nexus 6p API 28, Android 9.0, it tooks almost 3 to 4 minutes. and after booting it display message, System UI is not responding,. Wait or close app. When i click wait, it will took a while and starts successfully. But sometimes, It won't. I have to close Android Studio, shut down the system and restart it again. I wondered, why its not working smoothly on such a high configuration laptop.
The solution is that you can't do anything about it. You have assigned 2GB of RAM, but that's too low for the emulator (though it shows that as recommended).
The only way about it is to create and run a new emulator with the default configurations, i.e. don't change anything in the memory or RAM section.
This solution worked for me although the performance of the emulator isn't too good.
Please let me know the recommend requirement to run the eclipse and Android emulator simantaniously?
I've a laptop powered by Intel i3 processor 1.7 GHz clock speed, 4 GB RAM and windows 10, Bitdefender antivirus installed but I'm not able to work on these tools smoothly. But on desktop powered by 2.8GHz dual core 3GB ram it works smoothly.
The Android emulator is only showing Android logo at very slowly and it doesn't starts up for about 10 minutes on idle.
Please list down all the recommended requirement which are required to run eclipse and Android emulator simantaniously and smoothly on laptop.
I suggest switching to Android Studio. Support for ADT has ended. Moreover, make sure that you have updated Android SDK. There were improvements in emulators and system images in the last years, which made them faster. You can also switch to Linux (e.g. Ubuntu) because then you can use hardware acceleration for emulators. I'm not sure if it's working on MS Windows. If this won't help, you can try Genymotion.
Do you use Intel HAXM https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager and x86 image in AVD to improve the performance?
In any case, imho to run smootly AVD on a notebook you should have an i7 ULV 2c/4t (i7 4500U or better) and 8gb of RAM.
For development purpose do not use eclipse now, use Android Studio because Google has stopped there support to eclipse. In android studio you can use Genymotion it is faster then eclipse's android emulator.
And about your question the ADT emulator is very slow you have to wait a log time to its get started.Your laptop's configuration is enough. you can use Bluestack http://www.bluestacks.com/ or simply connect your android device via usb and run it on directoly using ADB.
I have 2 machines, one runs Windows 7 and another Mac. Hardware config is almost the same in the two, 2.4 with 4G RAM.
I notice the android simulator is slow in Windows 7, whould it run faster if I intsall Eclipse and Android SDK on the Mac machine?
what about Eclipse and Android SDK in general?
I think android device is better option that simulator it is much much faster than simulator. If you are planning for serious development then you should buy one android device.
I have a 13" Macbook pro (2010 model, 2.4ghz, 4 gig ram) and the emulator is pretty slow on it... I tend to develop mostly on my Linux desktop, which is 2.4ghz machine as well, and while the emulator is slow it's still MUCH faster than the Mac. Eclipse runs about the same on both... actually the Mac might even be slight faster since it has a SSD.
It's been my experience from watching other Macs run the emulator that the emulator is just slow on Mac :(
I know Google recently updated the the ADK to include speed improvements for the emulator, but I haven't tried that yet.
Try running it on mac, I did the same and found that the emulator runs much faster on mac, as compared to windows.
I have a windows 7 laptop 2 yrs old (8GB, i5) and 15inch MacBook pro 2012 (16GB, i7). I might also note that I am primarily a .NET developer, so I should be bias towards OSX.
I found that running the emulator and the ide on a mac runs faster than windows. I know the mac is considerably faster than my windows box but the difference in the speed of eclipse/emulator doesn't jive. The emulator runs smoother. Eclipse compiles faster on my Mac. The debugger settles/attached to hardware devices quicker.
My experience developing with Eclipse (Android SDK) is much more pleasant on the Mac than windows
I develop primarily on a desktop running Windows 8 since most of our apps are written in C#, I always found debugging painful on both a Samsung S3 and using the emulator.
I had read about using Intel HAXM which is available in the Android SDK Downloader, but never enabled it since I use Hyper-V on my desktop as well.
Fast forward, I'm now using a MacBook Pro because of needing to do iPhone development as well. I installed HAXM on the MacBook, and it made the x86 Android emulator run extremely fast.
TLDR: Install Intel HAXM on a machine with a modern CPU and you'll find running apps on your machine significantly faster.
If you do have Hyper V installed, you can disable it temporarily by creating a boot entry that causes Windows to boot with it disabled.
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 experience with the Android emulator is that it is so slow that it is unusable. I see threads related to the issue going back over a year. The lack of a coherent response to the question is unacceptable (this is not the Community's fault).
Question: Has anyone that has experienced extreme slowness (more than 15 minutes to launch) actually resolved this issue so that startup is less than a couple of minutes? If so, what did you do?
Please note that I am not trying to tie the emulator to Eclipse. I am teaching mobile web app development using jQTouch. The web apps are testing by running the emulator standalone and opening the Browser.
While my machine is a little dated, I have no trouble running Vista, Office, PowerStudio, etc. Here are details to add to the data around this issue.
OS: Microsoft Vista, 32-bit
Processor: Intel Celeron M CPU 520 # 1.60 GHz
Memory: 1.5 GB
Symantec Antivirus - Disabled
Emulator Start with no animation - did not help
Startup time in excess of 20 minutes
Java Version: 1.6.0_21
AVD Settings: Device RAM size 1024, Snapshot support enabled both in AVD and startup. - ram size and snapshot did not help
Google needs to acknowledge the issue and provide guidance about what development environments actually work. If there were a recommendation for platform, java version, memory, etc., I would follow it.
Right now I have no options other than to tell students that the Android emulator doesn't work. The only android solution is to buy a real phone, which limits testing to a single Android version and configuration.
Students are not having trouble with the iOS simulator running on the Mac.
If someone that works for Google could actually comment, that would be great.
Thanks,
Dale
The Android emulator is just that, an emulator -- it is emulating an ARM processor. Emulation will never be as fast as native. Given you are using such a large amount of your computer's memory for the emulator, you are likely having to page consistently, which will add to making the performace suffer.
The iOS simulator on the other hand is just a set of APIs that matches the iOS SDK and pretends to be an iOS device, but is running all code natively on the machine with all the resources, processor speed and memory the machine has, and likely to run significantly faster than running on the actual device.
I have no problem running the Android emulator on my old Core Duo T2400 # 1.83GHz with 2GB of RAM. The startup time can be a few minutes, but once it is running it works well with only occasional lag.
My desktop with a Core 2 Quad Q6700 # 2.66GHz with 2GB RAM tears through the emulator.
Both machines have run the emulator under Windows and Linux with varying Java versions getting similar results. My guess is that your processor is a little on the weak side.
check this article How to speed up the android emulator by up to 400
Or in brief, download an android-x86 build here, install with virtualbox, find ip address of android vm by alt+F1 and netcfg (alt+F7 to go back to graphical mode), and connect to the vm using adb (say adb connect 192.168.1.5).
Just used it, much more faster.
I've found the emulator to be very slow too - I think it's best to have a working android device and just have the emulator for a backup 'second opinion' or a reference device. It's usable but much slower than my phone, even though my current device is quite low end.
Eventually, I found that sending my code to the physical device (or emulator) was becoming a bottleneck so I build a small framework to allow me to develop most of the work as a desktop application. This has worked very well so far and has sped up my development turn around considerably. Your milage may vary.
Try using Genymotion emulator for android which is fast and also support all major platforms including Linux/Mac and windows. It also has specific emulator image files to emulate actual mobile devices like Xeperia Z or Nexus 4 and so forth.
Use Genymotion. It s is a very fast android emulator.
Android emulator is just a emulator, it emulates an Android device. It's like virtualization, you share your computer's resources with emulator, you'll need to have the latest processor and at least 8GB or RAM to run faster. About RAM: Windows and background programs consumes a part of your resources, if you upgrade your computer resources, the consumption of these software will be almost insignificant and you'll have a lot of resources for your emulator (supposing you also have Eclipse or Android Studio running).