Open your Mac’s Terminal (or Command Prompt, if you’re a Windows user) and then ‘change directory’ so the Terminal is pointing at Android SDK’s ‘Tools’ folder. My command looks like this: cd /Users/jessicathornsby/Library/Android/sdk/tools. Next, launch the emulator you created (myemulator) with the -gpu on flag, for example. Daftar rekomendasi emulator Android untuk PC Windows dan Mac yang dapat dipertimbangkan. If you have an older PC but you still want to run Android apps on it, check out which ones are the most lightweight emulators available! These are Best Android Emulators for PC. Install any of these Android Emulators and try Android apps on your PC. Bluestacks 2 is the best Android Emulator. Why Android Studio emulator is extremely slow? Asked 2 years, 10 months ago. I use this configuration on MAC.

Android Studio Emulator Slow

The Question :

Want to improve this question? Update the question so it focuses on one problem only by editing this post.

Closed 2 years ago.

I have got a 2.67 GHz Celeron processor, and 1.21 GB of RAM on a x86 Windows XP Professional machine.

My understanding is that the Android Emulator should start fairly quickly on such a machine, but for me, it doesn’t. I have followed all the instructions in setting up the IDE, SDKs, JDKs and such and have had some success in starting the emulator quickly, but that is very rare. How can I, if possible, fix this problem?

Even if it starts and loads the home screen, it is very sluggish. I have tried the Eclipse IDE in version 3.5 (Galileo) and 3.4 (Ganymede).

• Alternate is Genymotion. genymotion.com. This is much mcuh faster. Straightforward installation.
• I have found the emulator to run way (and by way I mean waaaay) faster on linux. I’ve got a laptop with dualboot, on windows the emulator takes about 15 minutes to start up, with linux about 30 seconds. I do not know about other operating systems like OSX, but feels like a windows thing to me.
• Android Studio 2.0 is reported to not only have a much faster emulator, but employ “instant run”, which allows certain changes in your source, such as the XML, to be deployed in seconds to the target without the APK having to be rebuilt and redeployed. See android-developers.blogspot.co.uk/2015/11/…
• i think your ram is very small for an emulator to run faster.
• One way of avoiding confused comments could be to have a little notice box saying the question is older than, say, 2 years old. Tech is changing rapidly, and you would want age to affect rank, even though the question shouldn’t be closed/archived as on lesser sites.

The Answer 1

Update

You can now enable the Quick Boot option for Android Emulator. That will save emulator state, and it will start the emulator quickly on the next boot.

Click on Emulator edit button, then click Show Advanced Setting. Then enable Quick Boot like below screenshot.

Android Development Tools (ADT) 9.0.0 (or later) has a feature that allows you to save state of the AVD (emulator), and you can start your emulator instantly. You have to enable this feature while creating a new AVD or you can just create it later by editing the AVD.

Also I have increased the Device RAM Size to 1024 which results in a very fast emulator.

Refer to the given below screenshots for more information.

Creating a new AVD with the save snapshot feature.

Launching the emulator from the snapshot.

And for speeding up your emulator you can refer to Speed up your Android Emulator!:

The Answer 2

IMPORTANT NOTE: Please first refer to the Intel list about VT to make sure your CPU supports Intel VT.

HAXM Speeds Up the Slow Android Emulator

HAXM stands for – “Intel Hardware Accelerated Execution Manager”

Currently, it supports only Intel® VT (Intel Virtualization Technology).

The Android emulator is based on QEMU. The interface between QEMU and the HAXM driver on the host system is designed to be vendor-agnostic.

Steps for Configuring Your Android Development Environment for HAXM

1. Update Eclipse:Make sure your Eclipse installation and the ADT plug-in are fully up-to-date.

2. Update your Android Tools:After each Eclipse plug-in update, it is important to update your Android SDK Tools. To do this, launch the Android SDK Manager and update all the Android SDK components. To take advantage of HAXM, you must be on at least release version 17.

• Download the x86 Atom System Images and the Intel Hardware Accelerated Execution Manager Driver. Follow the image below:

• Install the HAXM Driver by running “IntelHaxm.exe”. It will be located in one of the following locations:

  • C:ProgramFilesAndroidandroid-sdkextrasintelHardware_Accelerated_Execution_Manager

  • C:Users<user>adt-bundle-windows-x86_64sdkextrasintelHardware_Accelerated_Execution_Manager

  If the installer fails with the message that Intel VT must be turned on, you need to enable this in the BIOS. See the description for how to do this in Enabling Intel VT (Virtualization Technology) .

• Create a new x86 AVD: Follow the image below:

• Or as for new SDK,

The Answer 3

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

1. Install VirtualBox.
2. Download the ISO file that you need.
3. 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.
4. Install Android x86 on the emulator, run it.
5. Press Alt+F1, type netcfg, remember the IP address, press Alt+F7.
6. Run cmd on your Windows XP system, change the directory to your Android tools directory, type adb connect <virtual_machine_IP>.
7. Start Eclipse, open the ADT plugin, find the device, and enjoy!

The Answer 4

UPDATE: The latest version of Android studio (2.x) made major improvements to the bundled emulator. It’s responsive and has a whole bunch of features.

For those still interested:Try using Genymotion. You can download a version for Windows/Mac OS X/Linux after registering. A plugin for Eclipse is also available:

The installation of the plugin can be done by launching Eclipse and going to “Help / Install New Software” menu, then just add a new Update Site with the following URL: http://plugins.genymotion.com/eclipse. Follow the steps indicated by Eclipse.

This emulator is fast and responsive.

GenyMotion allows you to control various sensors of your device including the battery level, signal strength, and GPS. The latest version now also contains camera tools.

The Answer 5

The emulator included in your (old) version of Eclipse is very slow.

Recent emulators are faster than they use to be in 2010. Update your SDK/IDE.

Personally, I use a real phone to do my tests. It is faster and tests are more realistic. But if you want to test your application on a lot of different Android versions and don’t want to buy several phones, you will have to use the emulator from time to time.

The Answer 6

The startup of the emulator is very slow. The good thing is that you only need to start the emulator once. If the emulator is already running and you run your app again, the emulator reinstalls the app relatively quickly. Of course, if you want to know how fast it will run on a phone, it is best to test it on a real phone.

The Answer 7

Intel released recommended installation instructions for the ICS emulator on May 15, 2012. This worked for me. The emulator is now fast and the UI is smooth.

The first half of the instructions are detailed enough, so I will assume you were able to install the Intel x86 Atom System Image(s) using the Android SDK manager, as well as Intel HAXM.

Android Emulator Mac Free

Now to ensure that everything else is set up so you can enjoy a highly performing emulator:

And start it:

If HAXM is working properly, you may see this message when launching the emulator:

HAX is working and emulator runs in fast virtual mode

Otherwise, you may see this error:

HAX is not working and the emulator runs in emulation mode emulator:
Failed to open the hax module

• Use GPU emulation. You cannot use the Snapshot option when using GPU emulation as of this writing. Ensure that GPU emulation is set to “yes”.

• Set the device memory to 1024 MB or more, but not more than the Intel HAXM setting. I use 1024 MB per device and 2048 for HAXM.

Always double-check the settings after saving! The emulator is very picky about what it allows you to set, and it will revert configurations without telling you.

With these settings the software keyboard no longer appears, nor do the on-screen back, menu, and recent keys. This appears to be a limitation of the current ICS Intel x86 system image. You will need to use the keyboard shortcuts.

On Mac OS you will need to hold fn + control for the F1 – F12 keys to work. Page up/down/left/right can be performed using control + arrow keys.

The Answer 8

You can create emulator.bat with following command to start the emulator. It will start faster.

Or on Unix (Mac or Linux flavors):

The Answer 9

I’ve noticed that the emulator starts much faster if there’s no Dalvik Debug Monitor Server (DDMS) connected. So if you start the emulator from Virtual Device Manager “SDK Setup.exe” and Eclipse is not started, the emulator works faster.

If you start the emulator from Eclipse: DDMS is there, so sometimes the emulator is extremely slow, but sometimes it’s faster.

The Answer 10

Emulators are slow. There’s really nothing you can do about it, but there are alternatives to the emulator.

To make your emulator faster, you can host a GPU and use a lighter Android version (Android 2.3 (Gingerbread)).Developing on a Mac would be better. Why use an emulator, BTW? Using a real phone makes more sense.

The Answer 11

As of Revision 17 of Android SDK Tools, the emulator can use graphic acceleration and CPU-provided extensions for better efficiency. The prerequisites and full configuration and user notes are at:

For enabling GPU aceleration, run the emulator from the command line or add “-gpu on” to the additional emulator command line options in the AVD configuration.

For using the CPU machine extensions, you have to install the driver (caution because it can conflict with existing VirtualBox or VMware drivers). Once it’s installed it will be used automatically whenever you use an x86-based AVD.

The Answer 12

Try to disable your antivirus. Maybe it will make emulator a little bit faster.

The Answer 13

Android SDK rev. 17 supports Virtual Machine Acceleration using AMD and Intel virtualization technologies.

This feature can improve the emulator performance a lot!

See the following section in the Android emulator documentation for more details: Configuring Virtual Machine Acceleration

Don’t forget to install the appropriate driver for your operating system:

After you have installed the drivers and downloaded an Android X86 system image (as described in the documentation) you should be able to create a new AVD using the x86 image:

For example:

• Target: Intel Atom x86 System Image – API Level 10
• CPU/ABI: Intel Atom (x86)

The Answer 14

The option -cpu-delay <delay> described in Emulator Startup Options can help.

The Answer 15

The emulator seems to slow itself down when idle. This is made apparent by rapidly mousing over the keys on the side and observing the light-up responses. As a workaround, I pass -icount auto to QEMU when starting the emulator. You can make a batch file called my_avd.bat to do it for you:

• @my_avd — launch a virtual device named ‘my_avd’
• -no-boot-anim — disable animation for faster boot
• -qemu args... — pass arguments to qemu
• -icount [N|auto] — enable virtual instruction counter with 2^N clock ticks per instruction

This made animations buttery smooth and sped up adb install tenfold.

The Answer 16

Android emulator release 9 has a new “snapshot” feature. You can save the state of the emulator (make an image of the emulator) and avoid booting when you start the emulator.

The Answer 17

You can review the emulator issues on the Google I/O 2011: Android Development Tools talk, starting a 0:40:20.

The emulator runs slowly because the complete Android environment is running on emulated hardware and the instructions are executed on an emulated ARM processor as well.

The main choking point is rendering since it’s not running on any dedicated hardware but it’s actually being performed through software rendering. Lowering the screen size will drastically improve emulator performance. Getting more/faster memory isn’t going to help.

They’ve mentioned, at the time, that they’re developing an interface that would allow the emulator to pipe certain instructions through the host hardware, so eventually, you’ll be able to leverage emulator performances with the raw power of desktop hardware.

The Answer 18

The current (May 2011) version of the emulator is slow particularly with Android 3.0 (Honeycomb) primarily because the emulator does not support hardware GL — this means that the GL code gets translated into software (ARM software, in fact) which then gets emulated in software in QEMU. This is crazy-slow. They’re working on this problem and have it partially solved, but not with any sort of release quality.

Check out the video Google I/O 2011: Android Development Tools to see it in action — jump to about 44 minutes.

The Answer 19

Use the Intel x86 Emulator Accelerator

First, install the Intel x86 Emulator Accelerator (HAXM). This can be downloaded directly from Intel or using Android SDK Manager. In the SDK Manager, it’s located under Extras.

In the version of Android Studio I used (0.8.9), Android SDK Manager downloads HAXM but doesn’t actually run the installer (I assume this will be fixed in later releases). To run the installer I had to go to C:Program Files (x86)Androidandroid-studiosdkextrasintelHardware_Accelerated_Execution_Manager and manually launch intelhaxm.exe.

HAXM works with Intel devices, so created a new Emulator with Intel CPU.

Create a new AVD using Intel Atom x86

This improved things considerably, but the emulator was still feeling a bit sluggish. The final step was selecting Use Host GPU in Android Virtual Device Manager (AVD).

After these changes, Android Emulator was launching in 5-10 seconds and running without any noticeable lag.Be aware that these features are hardware dependent (CPU/GPU) and may not work on some systems.

The Answer 20

Try Genymotion for Android Studio. Blazing fast! Just needs one time installation. No more AVD pain.

The Answer 21

A new option is the Visual Studio Emulator for Android–it’s fast, Hyper-V, x86, and free to download even without VS.

The Answer 22

To add further information to this.

I have recently upgraded my Ubuntu installation to Ubuntu 10.04 LTS (Lucid Lynx) which in turn updated my Java version to:

And now the emulator (although takes a while to start) seems to be running faster than previously.

It might be worth people upgrading their JVM.

The Answer 23

Here’s what I noticed nobody mentioned it at all.

Assign all available processors to the emulator

Here’s what you can try. It does speed up the emulator for me, especially during loading time. I noticed the emulator is only using a single core of the available CPU. I set it to use all available processors.

I’m using Windows 7.

When the Android emulator is starting, open up the Task Manager, look under the Process tab, look for “emulator-arm.exe” or “emulator-arm.exe *32″… Right click on it, select Processor Affinity and assign as much processor as you like to the emulator.

The Answer 24

After developing for a while, my emulator became brutally slow. I chose wipe user data, and it was much much better. I am guessing that it takes time to load up each APK file you’ve deployed.

The Answer 25

Android emulator is dead slow. It takes 800MB memory while running.If you are on Windows, You can use Microsoft Android Emulator. It is superb, provides you functionalities more than Android Studio Emulator. And most important it is fast ( consumes 13MB only).It comes with Visual Studio 2015 Technical Preview. I am using it and happy with it. I downloaded and installed entire VS pack, I need to look how we can install VS Emulator only.

EDIT:Try https://www.visualstudio.com/vs/msft-android-emulator/

The Answer 26

Well, since somebody suggested Android x86 as an alternative testing emulator, I’ll also present my favorite. This might not be an alternative for everyone, but for me it’s perfect!

Use the Bluestacks Player. It runs Android 2.3.4 and is very fluid and fast. Sometimes it is even faster than a normal device. The only downside is, that you can just test apps on the API Level 10 and just on one screen size, but it’s perfect just for testing if it’s working or not. Just connect the Player with the adb by running

After compiling, it installs instantly. It is very impressive, considering I have rather an average computer hardware (dual core with 4 GB of RAM).

The Answer 27

I had intermittent slow emulator (SDK v8.0) load times, up to three minutes on Intel Core i7 920 2.67 GHz CPU running on Xubuntu 10.04 VirtualBox 3.2.12 guest with Eclipse (3.6.1) loaded. I changed the VirtualBox guest memory from 1024 MB to 2048 MB and from that point on, I never experienced the slowness again (load times consistent at 33 seconds, CPU load consistent at 20%). Both Eclipse and the emulator are memory hogs.

The Answer 28

I noticed that the my emulator (Eclipse plugin) was significantly slowed by my Nvidia graphics card anti-aliasing settings. Removing 2x anti aliasing from the graphics menu and changing it to application controlled made it more responsive. It is still slow, but better than it used to be.

The Answer 29

To reduce your emulator start-up time you need to check the “Disable Boot Animation” before starting the emulator. Refer to the Android documentation.

If in case you don’t know, you do not need to close the emulator every-time you run/debug your app. If you click run/debug when it’s already open, your APK file will get uploaded to the emulator and start pretty much immediately. Emulator takes annoyingly long time only when it started the first time.

Here are some tips to speed up the Android emulator: How to speed up the Android Emulator by up to 400%.

The Answer 30

Good way to speed up Android Emulator and app testing is Install or Upgrade your Android Studio to Android Studio 2.0 version and then go to app open Settings/Preferences, the go to Build, Execution, Deployment → Instant Run. Click on Enable Instant Run. And After That This will ensure you have the correct gradle plugin for your project to work with Instant Run.

And Instant run will look like this

However Android Studio is right now in Preview you can try it now.

I recently upgraded from Eclipse to Android Studio and I’m not really liking the experience. I’m comparing them both on a Windows 7 64 bit ultimate with 16GB of ram and Intel i7 4770 running NVidia Geforce 780 with the latest NVidia drivers if it matters and I’m running the latest JDK and the latest Android Studio.

The Android Studio is very slow in building the project which I can live with but it’s also extremely resource intensive and sometimes slows down the PC to a crawl.

Whenever I’m building or running anything in AS, my PC seems to become extremely sluggish. It also causes flickering of screen and occasionally blanking my second monitor if I click on “Gradle build running” spinner which I find very odd. The RAM usage also shoots up to ~3GB which I find excessive for doing nothing (this is when it’s idle after a few builds).

In addition, the panels at the bottom of AS keep jumping around which is a horrible user experience (moves from Android to Messages to Version Control or anything else on an ad-hoc basis depending on what’s happening which is very, very annoying).

What I would like to know is basically:

1) How do I make Android Studio run better? I may be doing something wrong or missing some updates that I’m not aware of and I’m sure others have also noticed these behaviors and have found some solutions to it.

2) How do I “pin” the bottom panels so that they don’t jump around and instead, let me, the user, navigate to them when I wish to instead of automatically switching them?

Many thanks and my apologies again if it’s not the correct place for these questions.

Edit 1
Some more comments:

• I’m using the latest stable build as of today. The build is Android Studio 1.2.2 Build # AI-141.1980579, Build on June 3, 2015
• The behavior happens when using either Java 7 or 8. It doesn’t appear to be related to the version of Java.
• I am not using Presentation Mode. Just the vanilla view.
• Doing the changes to the build configuration (thanks to @Blackbelt and his answer) appears to have helped with the build but the other problems with sluggishness and general user experience remain.

to sum it up

1) in AndroidStudio’s settings > compile enable checkbox named Compile independent modules in parallel.

2) Under Help> Edit Custom VM Options I have:

p.s. Some people say Note, instead of VM options, it’s better to combine can be overriden by combining those lines into one line single command in gradle.properties, like this :

org.gradle.jvmargs=-Xms1024m -Xmx4096m ……

3) I have an old dual core with 4GB ram, running ubuntu. Qs command line option I have only --offline (which specifies that the build should operate without accessing network resources). I also enabled the remaining checkboxes and now it’s running ok:

• Make project automatically

• Use in-process building Configure on demand

• Check the AndroidStudio’s settings, under compile that the checkbox Compile independent modules in parallel is enabled.

Under Vmoptions I have

I have an old dual core with 4GB ram, running ubuntu. Qs commandline option I have only --offline , which specifies that the build should operate without accessing network resources. I enabled also the remaining checkboxes:

1. Make project automatically
2. Use in-process building

3. Configure on demand

   and it is running ok

Edit

It is possible to provide additional options through studio.vmoptions located at (just replace X.X with version):

• Windows: go to %USERPROFILE%.AndroidStudioX.Xstudio.exe.vmoptions (or studio64.exe.vmoptions)

• Mac: ~/Library/Preferences/.AndroidStudioX.X/studio.vmoptions

• Linux: ~/.AndroidStudioX.X/studio.vmoptions (and/or studio64.vmoptions)

Increasing the value of -Xmx should help a lot. E.g

will assign 4G as max heap, with initial value of 1G

Edit:

On windows the defaults are stored into C:Program FilesAndroidAndroid Studiobin*.vmoptions. The IDE allows you to tweak those values through Help->Edit Custom VM options (thanks to @Code-Read for pointing it out).

Tips to make android studio fast:

Enable Offline Work:

1. Click File -> Settings. Search for “gradle” and click in Offline work box.
2. Go to Compiler (in same settings dialog just below Gradle) and add --offline to Command-line Options text box.

Improve Gradle Performance

gradle can be optimized too. The easy way is to modify the settings in global gradle.properties (create it if not exists in the following folders: Windows – C:usersyour_name.gradle; Linux- /home/<username>/.gradle/; Mac- /Users/<username>/.gradle/; ) and in that file, add these two lines:

For More: http://www.viralandroid.com/2015/08/how-to-make-android-studio-fast.html

I detected another reason – Thumbs.db, which affected performance badly.

Go to File > Settings > Editor > File Types and in field Ignore files and folders add this: Thumbs.db;

Now, Android Studio runs like a charm.

Adding more memory helped me:

1. Click “Help”
2. Edit Custom VM Options

Android Studio 2.1.2 Edit Custom VM Options:

3. Change values

like below:

4. Restart Android Studio

• I cant start without saying: if you have any chance, spend a bit more money for better parts/PC, it helps much..
• Some people say, that OS causes much slowness. For example, XP or LINUX (or etc) is said to perform 70% faster (Cant tell why).

• Disable VCS by File > Settings > Plugins and disable the following things :
  CVS Integration; Git Integration; GitHub; Google Cloud ... things; Subversion Integration; hg4idea;
  

• Editor is a resource eating too (especially on Large Monitors) and slow. Make it much much faster: click Help > Edit custom VM options and add these lines :

  -Dsun.java2d.d3d=false
-Dsun.java2d.opengl=true

  save it and Restart Android Studio.

• If Android Studio has a proxy server setting and can’t reach the server then it takes a long time to build and waiting for a timeout. Removing it helps much. File > Settings > Appearance & Behavior > System settings > HTTP Proxy.
• (quote from this link):

Modules are expensive… On my current project I had to build some libraries from scratch and had to fork some that almost fitted my needs but not quite! If that modules are not constantly modified, it’s important to have this into consideration: the time needed to compile them from scratch, or even to check if the previous individual module build is up-to-date, can be up to almost 4x greater than to simply load that dependency as a binary .jar/.aar.

Hint: run the gradle build -profile for an HTML report showing where
the time goes regarding the build process.

Note: keep that “unnecessary” modules in your version control system
for the eventuallity of a quickfix/improvement in that dependency.

• In your Gradle build script, use only
  specific Google Service, like: compile 'com.google.android.gms:play-services-maps:...'
  Instead of full Google Library: compile 'com.google.android.gms:play-services:...'
  (Compile time goes from 2 minutes to around 25 seconds).

• Gradle configures every project before executing tasks, regardless of whether the project is actually needed for the particular build. In global gradle.properties adding this will help much: org.gradle.configureondemand=true

• Surprisingly, some people say , they solved problem by reducing: 1) heapsizes to -Xmx256m (instead of higher values); 2) Emulator Ram-size (from Edit AVD > Advanced Settings);

• Don’t run multiple projects simultaneously.
• Don’t close emulator after using once (use same emulator for running app each time). If you test large apps, better to use a real Mobile ( instead of emulator )
• clean your project every time after running your app in emulator – click Build > Clean Project (or Rebuild)

It’s not compiling that’s hurting me here, it’s the typing. I could disable all the smart features and be back to notepad++ like TomTsagk suggested in a comment. For today I need more cores and RAM.

Playing devil’s advocate I’d argue that typing shouldn’t require a 16Gb PC octacore PC. Liked Sajan Rana’s advice but things are so slow here it felt mostly a placebo.

To be fair I am using 1.4RC1, which is just short of being in the stable branch. Turning the internet off helped a little. The new feature of simultaneous Design (Preview) and Text views working with XML layouts is very helpful.

No, it is ridiculous. Never leave the stable channel.

Just for anyone looking, after upgrading to El Capitan, I noticed a huge lag with the IDE. After increasing a ton of RAM and using the suggestions above, it turned out that I needed to update the legacy Java, and reinstall via: https://support.apple.com/kb/DL1572?locale=en_US

After installing this, all lag was gone.

As you are learning, performance problems with AS are not trivial to diagnose! In my case, an array of 9215-character-long strings (see below) was causing AS to dump threads every time I typed a few characters. The thread dump in turn caused AS to freeze for many seconds at a time. This bug appeared in the Windows 64 bit release of AS 2.2, still occurs in 2.2.1, but was not present in 2.1.

Finding out that long strings were causing my lockups involved a lot of trial and error. But, I learned a lot in the process, to wit:

• idea.log contains excellent diagnostics (Help->Show Log in Explorer);
• If you see extreme, but intermittent slowdowns, suspect AS is dumping threads. This will be reported in idea.log. If threads are being dumped, the dumps will tell what code AS was executing when the problem occurred;
• Find out whether the problem occurs in other projects. If not:
  • Look for unusual content in the project file you are editing when it happens (atypical indentation, long lines, overall size, special characters, etc.);
  • Try exporting settings from another project (File->Export Settings) and importing them to the problem project (File->Import Settings);
• If so:
  • If threads were dumped, consult these and text in idea.log near in time to the dump notices for details;
  • Consult idea.log for messages about memory consumption and see other answers to this question such as https://stackoverflow.com/a/30818099/5025060 for advice regarding memory and other tunables.

BTW, for the present I have worked around the problem I describe above by moving my long strings into a separate file (a new class containing only the array itself). I try not to edit this file with AS:

In case setting -Xmx4096m -XX:MaxHeapSize=256m (and etc.. mentioned in above answers) doest work, then do this manually:

Step 1 : Start Android studio and close any open project (File > Close Project).

Step 2 : On Welcome window, Go to Configure > Settings.

Step 3 : Go to Build, Execution, Deployment > Compiler

Step 4 : Change Build process heap size (Mbytes) to 1024 and Additional build process to VM Options to -Xmx512m.

Step 5 : Close or Restart Android Studio.

I just want to share my case:

1. if you need play-store library, don’t compile all of it, just compile library that you need. example: if you only need maps library instead of compile 'com.google.android.gms:play-services:9.0.2' do this compile 'com.google.android.gms:play-services-maps:9.0.2' on your gradle
2. Dont use OpenJDK for the java, I use java 7 oracle and it works well. if yout need to change default java do this on linux terminal sudo update-alternatives --config java and pick the number

I’m using ubuntu 32bit 4GB RAM. that’s all the issue I ever encounter with AS.

I’ve quickly resolved this issue by upgrading gradle (Android Studio seems to use old version).

1) Download latest version (https://gradle.org/gradle-download/) and unpack somewhere.
2) Update path in Android Studio: File > Settings > Build, Ex../Gradle

This worked for me!
Open build.gradle (it’s inside your project) and change the both jcenter to mavenCentral

(you can do it in Global file too: C:Program FilesAndroidStudiopluginsandroidlibtemplatesgradle-projectsNewAndroidProjectrootbuild.gradle.ftl however, you will need to do this modification again after AndroidStudio upgrade)

In one particular system I looked at, this issue was caused by an over-zealous anti-virus that was interfering with Gradle, the build manager for Android Studio. It seems every time Gradle was “touching” a .jar file, the virus checker was unzipping the .jar and scanning it for viruses first. The Gradle build could only continue once the unzipping and scan was complete, thus leading to very long build times (5 min plus). Since Android Studio, by default, runs a Gradle build when you start up, it manifests as an extremely slow start-up.

The problem is extremely easy to check for:

1. While you are experiencing the symptoms of a slow Android Studio, press Ctrl– Alt–Delete and open Windows Task Manager.
2. Click on the Processes tab to see the active processes and sort by CPU. If you see an anti-virus taking significant amounts of CPU percentage intermittently while Android Studio appears to be loading, it is likely to be the same issue.
3. You can verify further by looking at the scan logs of the anti-virus to see if it is indeed, examining the .jar files.

To solve this, you will have to add the correct directories to the “excluded folders” of your anti-virus. Assume that your Windows username is “Username” and you have installed Android Studio on C: drive. You would then request to exclude from the virus check the following directories:

Please note that you may need to take additional security precautions if you exclude these directories and you should co-operate with your security department in the workplace. This may involve setting up your own Maven repository if deemed necessary.

(I am aware that this is a late answer, but none of the previous answers have addressed this potential issue)

DO NOT EDIT studio.vmoptions ,It may not work.

In gradle.properties file (in app directory) add this :

I noticed that AS transfers too much data from/to HDD. It is very annoying, especially when starting to write a new line of code. So, I think, better will be reinstalling a hard disk with SSD. I have i5 with 6 Gb of memory, and the CPU seldom loads more than 50% even at build time. So, the most weak place is HDD.

Click Help > Edit Custom properties and add this line:

… worked successfully for me to fix the speed issues (Windows 10 64-bit). It’s absolute voodoo as far as I’m concerned (I haven’t done any research on why that should work), and there is a warning above that property that it can cause blinking and fail to repaint on some graphics cards, but there you go. (Inspired by LairdPleng’s comment, further information)

SSD usage is recommended. Check that project and repository caches (~/.gradle/, ~/.m2/repository if you use maven repository) is placed on SSD too. Yes, it reduces some SSD resource, but speed up development as rocket (‘SSD for you’, not ‘you for SSD’).

More details about improvements read this post.

• I should mention that if you are using Mac, downloading and running an app from the App Store (like “iBoostUp” etc.) which will clean out unused system files can speed up your computer dramatically, including AS.

• I also found that adding more memory to my Mac sped up AS as well.

Okay. I will agree that every answer written above will somehow help the cause. I am one of those who is on the same boat. With nothing working my way, and Android Studio refusing to build on the Offline mode due to the associated dependencies, I did something that eased my problem within minutes.

Every time I build the gradle, I turn off my internet. ( Notice that the Offline mode is not checked). I don’t know how and why but this works.

Well, one thing that worked for me is using physical android device instead of emulator. As in my PC( i5 and 4GB RAM ) the android studio takes about 700MB of memory and the emulator takes another 700. Thus the whole performance of the computer goes down. Working with a physical device saves the strain from the emulator.

Even i do have core i5 machine and 4GB RAM, i do face the same issue. On clean and rebuild the project gradle build system downloads the files jar/lib fresh files from internet. You need to disable this option available in settings of your Android studio. This will re-use the cached lib/jar files. Also the speed of Android studio depends on speed of your hard disk also. Here is detailed blog-post on how to improve too slow Android studio.

There are many ways to speed up Android Studio.

• Speed up gradle build time.

  1.Go to Project gradle.properties file and remove comment from both line.

  2.copy gradle.properties file to your .gradle folder so that you don’t need to setup for every project.

• Enable Work Offline so that Android studio/Gradle don’t need to check for newer file over internet every time.

Visual Studio Android Emulator Slow

My Android Studio was not only slow in general use, but also when building.

Here’s what I did:

1. Uninstalled Android Studio (Don’t delete, uninstall it and check delete the SDK too). Then delete Android folders located in C:Users folder namely: .android, AndroidStudioX.X
2. Uninstall the SDKs via the SDK manager, remove everything ( If there is lef SDK folder, delete them )
3. Download and Reinstall the latest build for Android Studio (v2.1.2 as of this writing); Install only the SDK/Emulators you need;

It’s fast now.

My Story before that:

My laptop sports an Intel Core i7-3612QM and 8gig of ram. When I builded, all the 4 cores/8 threads were on 100% usage. My entire system froze until the ~10 minute wass done. Gradle took me like ~10 unproductive minutes of slow down. This is very annoying. I am using Android Studio since 1.4. There were also tremendous slow down when I copy paste code to and from, selecting menus, right-click context menus, editing manifest, editing gradle files, opening layout files, rendering in the UI Editor, etc. Its was very unusable most of the time.

Due to frustration, I did the above steps. Its fast now. Very usable just as before. I build for only ~20 seconds compare to ~10minutes before that. Also, Android Studio eats about 6gig with emulator and browser with lots of tab open, unlike before its hovering on 98% RAM usage. Not just that, I even saved 45 gigs of space for whatever reason. I only use couple of SDKs and Emulators when I checked the Android SDK folder, it occupies 45gig of space! I think the IDE is having a hard time accessing/IO on my SDK folder.

If you’ve tried other given solutions and still experiencing the same issue, it may be time to remove Android IDE/SDKs altogether and start anew (it might take you sometime to setup that newly, but its worth it. Considering I’ve been suffering this sluggishness for months and cost me my productivity).

Android Studio Emulator Slow Mac Download

I really guess that this might be caused by cumulative patches that has been done since then. Or the 45 gig SDK folder on my poorly defragmented drive. I don’t know and I could be wrong.

Thank you! HTH

Android Studio Emulator Slow Mac Air

Android Developers channel made by Google, just uploaded a video for optimizing the IDE and here is the link

Android Studio Emulator Download

Tags: android