How to Speed Up Android Emulator

In this tutorial, you'll learn about How to Speed Up Android Emulator. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

The Problem

The Android emulator is painfully slow. App launches take minutes, UI interactions lag, and development becomes frustrating. The emulator is running without hardware acceleration or with inefficient settings.

Quick Fix

Step 1: Enable hardware acceleration (KVM on Linux)

sudo apt update && sudo apt install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils -y
sudo adduser $USER kvm

Log out and back in, then verify:

kvm-ok

Expected:

INFO: /dev/kvm exists
KVM acceleration can be used

Step 2: Use an x86/x86_64 system image

In Android Studio's AVD Manager, create an emulator with:

• ABI: x86_64 or x86 (not arm64-v8a or armeabi-v7a)
• API Level: A recent stable level (e.g., API 34)

x86 images use KVM for near-native performance. ARM images run without hardware acceleration and are extremely slow.

Step 3: Reduce emulator memory and resolution

In AVD Manager, edit the virtual device:

• RAM: 1536 MB (or lower for lightweight testing)
• VM heap: 256 MB
• Display resolution: 720x1280 (smaller = faster rendering)
• Graphics: Hardware (GLES 2.0)

Click Show Advanced Settings and uncheck Enable Device Frame to save GPU resources.

Step 4: Launch with quick boot

emulator -avd Pixel_6_API_34 -no-snapshot -accel on

Or use cold boot only when needed:

emulator -avd Pixel_6_API_34 -no-snapshot-load

Quick boot saves and restores the emulator state, skipping the full boot sequence.

Step 5: Use command-line performance flags

emulator -avd Pixel_6_API_34 -gpu host -memory 1536 -cores 4

-gpu host uses your physical GPU for rendering. -cores 4 allocates 4 CPU cores to the emulator.

Step 6: Disable snapshot for faster cold boot

In AVD Manager, edit the device and set Boot option to Cold boot. This avoids loading a potentially corrupted snapshot.

Step 7: Use a Wear OS or small-screen emulator

Smaller screen resolutions render faster. A Wear OS emulator or a phone with a 720p display is noticeably quicker than a 4K tablet.

Step 8: Check ADB for responsiveness

adb shell getprop sys.boot-completed

Expected:

1

If the emulator is running but slow, adb logcat may show GC pressure or ANR warnings.

Alternative Solutions

Use a physical device for development. USB debugging provides real hardware performance without emulation overhead.

Prevention

• Always use x86/x86_64 system images with KVM/haxm acceleration.
• Keep the emulator running between debugging sessions instead of stopping/starting.
• Allocate enough RAM to the host machine (16 GB+ recommended for Android development).
• Close unnecessary host applications to free CPU and GPU resources.