Intel HAXM is also used to accelerate the Tizen* emulator, but this is out of scope in this documentation.
We then explain how to use the NDK to compile x86 native code and the correct way to submit APKs containing x86 native libraries to the Google Play store. This document explains all the steps required to accelerator the emulator and how to work with it.
Over and over again, we have heard from many Android developers that the emulator is slow and painful to work with, but this should not be the case! If you are using a fairly up-to-date computer with an Intel® processor that has Intel® Virtualization Technology enabled running Microsoft Windows* or Apple Mac OS*, then you can use the Intel® Hardware Accelerated Execution Manager (Intel® HAXM), or KVM for Linux*, to accelerate the Android Emulator by an order of magnitude very easily, which will speed-up your testing and debugging of your Android applications. If you are an Android* developer who is unhappy with the performance of the Android emulator, then this document is for you.
# Build the emulator, which will be another coffee break. Mkdir -p $HOME/emu-master-dev & cd $HOME/emu-master-devĮxport XCODE_PATH=$(xcode-select -print-path 2>/dev/null)Ĭp -r MacOSX-SDKs/MacOSX10.13.sdk/ "$XCODE_PATH/Platforms/atform/Developer/SDKs" Probably best to go get a coffee here or run on a server if you have poor internet Lightly tested guide heavily pulling from the readme of the repo: # Get the google repo tool - you can skip if you already have itĬurl > /usr/local/bin/repo & chmod +x /usr/local/bin/repo If you can't wait, you should be able to build off that branch. This looks like it should be released in the emulator 30.1.5 (see log ) which should be in the next canary build. This is the reference to the commit fixing this issue for Big Sur.
Old information, kept for educational value: ~/Library/Android/sdk/emulator/emulator -gpu host -feature HVF -avd pixel_3a_api_29 This can be accomplished by running the following command in your terminal where -avd is the name of your emulator device with spaces turned to underscores.
It should be available "soon" according to the Googler's working on this.Īnother note, if you experience poor performance in your emulator you may wish to try using the host's GPU for rendering. The dev build, 30.2.0 does not contain this fix. The Android Emulator team has pushed 30.1.5 which fixes this issue in stable.