Skip to content
Get a quote

Android Emulator errorAndroid Emulator: “System UI isn’t responding”

The Android Emulator shows a System UI isn’t responding dialog, often during or right after boot, and the app you launched with flutter run or Android Studio barely moves. The virtual device isn’t getting enough memory, CPU or graphics from your computer, or its saved snapshot is in a bad state. It isn’t a bug in your app.

Short answer

Tap Wait once; on first boot it often recovers. If it keeps coming back: in Device Manager, edit the AVD, raise RAM under Advanced settings and set Boot option to Cold boot, then start it again. If that isn’t enough, switch Graphics acceleration to software, wipe the device data, or create a new AVD with a lighter system image that matches your computer’s CPU.

Why the emulator’s System UI hangs, and the fix

  1. 01

    Too little RAM for the system image

    “Increasing the size uses more resources on your computer but supports faster emulator operation.” Android Developers, Create and manage virtual devices (Memory and Storage: RAM)

    New system images, especially ones with Google Play, need more memory than older AVD defaults give them. Edit the AVD, open the advanced settings, and raise RAM, keeping enough free on your computer for Android Studio and the build.

  2. 02

    A bad quick-boot snapshot

    Quick boot restores a saved snapshot, and a snapshot saved while the device was struggling brings the problem back each time. Cold boot it, and wipe its data if the dialog persists. Also check free disk space: a nearly full AVD or host disk stalls the System UI too.

    # emulator lives in <Android SDK>/emulator, for example ~/Library/Android/sdk/emulator on macOS
# lists AVD names, then cold boots one
emulator -list-avds
emulator -avd Pixel_8_API_35 -no-snapshot-load

# Device Manager: Menu > Wipe Data, then start the device again

  3. 03

    Graphics acceleration the computer can’t handle

    “Run the emulator using the -gpu swiftshader mode.” Android Developers, Troubleshoot known issues (Emulator runs slowly after an update)

    Google’s troubleshooting page suggests a graphics driver update and software rendering when the emulator runs slowly after an update. It is the same class of symptom, so it is worth trying here. Software rendering is slower but steadier.

    emulator -avd Pixel_8_API_35 -gpu swiftshader

  4. 04

    No VM acceleration, or the wrong CPU architecture

    “Hardware acceleration is enabled by default on most machines.” Android Developers, Configure hardware acceleration for the Android Emulator

    An emulator without hardware virtualization, or an ARM image on an Intel PC, runs far too slowly for the System UI. Use an image that matches your CPU (x86_64 on Intel and AMD, arm64 on Apple silicon). Google notes acceleration is on by default on most machines; on Windows without Hyper-V (WHPX) or Linux without KVM access, turn it on.

Checked against the vendor’s docs on : Android: Create and manage virtual devices; Android: Troubleshoot known issues with Android Emulator; Android: Configure hardware acceleration for the emulator.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Related: Xcode “Unable to boot the Simulator” · Android “SDK location not found” · Android INSTALL_FAILED_INSUFFICIENT_STORAGE

Questions

More on this error

Should I test on a real phone instead?

For day-to-day work it is often faster: enable developer options and USB debugging, plug it in, and flutter run picks it up. Keep an emulator for Android versions you don’t own.

Does the error affect my app on users’ phones?

No. It is the emulator’s own system interface stalling on your computer. If your app also freezes on real devices, that is a separate problem.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.

Describe your problem All fixes