Hey there, I’ve run into this exact emulator headache with older Android versions in Android Studio 3.1 before—let’s walk through some tried-and-tested fixes to get those KitKat/Jelly Bean/ICS emulators behaving properly!

1. Tune AVD Performance Settings #

First, head to your AVD Manager, select the problematic legacy device, and hit the pencil icon to edit it. Jump into the Show Advanced Settings section:

• Set Graphics to Software - GLES 2.0: Older Android builds often clash with hardware acceleration in newer Studio versions, and software rendering is more stable here.
• Bump up RAM to at least 1GB (just don’t exceed half your system’s total RAM to avoid slowing down your host machine).
• Increase VM Heap to 256MB or higher—this gives the emulator more memory to handle older, less optimized Android code.

2. Resolve Virtualization Conflicts #

Older emulators hate conflicting virtualization tools. Here’s how to fix it:

• Windows: Disable Hyper-V (it messes with HAXM, which the emulator relies on). Open Control Panel > Programs > Turn Windows features on or off, uncheck Hyper-V, then restart your PC. After reboot, make sure HAXM is installed via SDK Manager > SDK Tools.
• Mac/Linux: Update HAXM to the latest version compatible with Android Studio 3.1. Outdated HAXM versions are a common culprit for lag with ancient Android builds.

3. Use x86 System Images #

When creating or editing your AVD, always pick the x86 system image instead of ARM. x86 images leverage HAXM for way better performance, whereas ARM images are notoriously slow and buggy for older Android versions. For extra stability, go with the Google APIs variant of the system image—it often has hidden compatibility fixes for emulators.

4. Add Custom Launch Flags #

Force the emulator to play nice with legacy versions by adding these command-line flags:

1. Right-click your AVD in AVD Manager and select Edit Configurations.
2. Under the Emulator tab, paste these into Additional command line options:

   -gpu swiftshader_indirect -no-snapshot-load
   

   • -gpu swiftshader_indirect: Forces a more stable software rendering pipeline for old Android versions.
   • -no-snapshot-load: Skips loading potentially corrupted snapshots that can cause freezes or unresponsive buttons.

5. Downgrade the Emulator Component (Last Resort) #

Android Studio 3.1’s default emulator has some bugs with super old Android versions. Try downgrading the emulator tool:

1. Open SDK Manager > SDK Tools.
2. Check Show Package Details next to Android Emulator.
3. Install an older version like 27.0.2—this release was far more stable for legacy Android builds.

Quick ICS-Specific Tip #

Ice Cream Sandwich is extra finicky. If it’s still freezing or flickering, create an AVD with a smaller screen size (like 480x800) and disable unnecessary hardware features (camera, GPS) in the AVD settings—less resource load goes a long way here.

内容的提问来源于stack exchange，提问作者Nicolo' Dovico