Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

The Android emulator freezes with 'System UI isn't responding' during Flutter runs

ErrorSystem UI isn't responding

Short answer

That dialog is Android saying its own system process is starved or stuck inside the emulator. It is not a Flutter bug. Free disk space, check hardware acceleration, switch the graphics mode if rendering misbehaves, and cold boot the virtual device so a broken snapshot is not reloaded.

  • Applies to Android Studio current stable, Android Emulator current, Flutter 3.x stable
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Check whether the emulator can use hardware acceleration at all. The output names the hypervisor, or says why it is missing.

    $ANDROID_HOME/emulator/emulator -accel-check
  2. 2Match what you see, then jump to its fix

    1. 1The emulator will not start, or hangs soon after start, on a nearly full diskThe machine is short on free disk spaceFix
    2. 2-accel-check reports no hypervisor, or the AVD uses an ARM image on an Intel or AMD PCNo hardware acceleration, so the guest runs as pure softwareFix
    3. 3Glitches or freezes right after an emulator or graphics driver updateThe graphics mode does not suit the machineFix
    4. 4The freeze happens every time the same virtual device starts from its saved stateA stored Quick Boot snapshot is stale or brokenFix

What does the error look like?

  • System UI isn't responding

Cause 1 of 4

The machine is short on free disk space

1Check

The emulator checks free space when it starts and does not start with less than 5 GB free. Low space can also cause crashes and hangs.

df -h ~ | tail -n 1

2Fix

Free at least 5 GB, for example by deleting old AVDs and unused system images in Device Manager.

# Android Studio > Device Manager > delete unused virtual devices
# SDK Manager > remove unused system images

3Verify

The emulator starts and the dialog stops appearing.

emulator -list-avds

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 4

No hardware acceleration, so the guest runs as pure software

1Check

VM acceleration needs a hypervisor (Hypervisor.Framework on macOS, KVM on Linux, Windows Hypervisor Platform on Windows) and a system image that matches the CPU architecture. It cannot run inside another VM.

$ANDROID_HOME/emulator/emulator -accel-check
# Linux only:
sudo kvm-ok

2Fix

Enable the hypervisor for your system (on Windows turn on Windows Hypervisor Platform, on Linux install KVM) and use an AVD image whose architecture matches your CPU.

# Windows: Turn Windows features on or off > Windows Hypervisor Platform, then restart

3Verify

-accel-check now prints that the hypervisor is installed and usable.

$ANDROID_HOME/emulator/emulator -accel-check

Confirmed by developer.android.com

Did this fix it?

Cause 3 of 4

The graphics mode does not suit the machine

1Check

Docs say an unsupported graphics acceleration option is likely to cause crashes or wrong images, and that software mode is advised when auto or host give trouble. On Apple silicon, hardware mode uses MoltenVK, which does not cover every Vulkan feature.

emulator -avd <avd_name> -gpu auto

2Fix

Start once with software rendering, or set Graphics to Software in the AVD's advanced settings.

emulator -avd <avd_name> -gpu swiftshader

3Verify

The device boots and stays responsive for a few minutes of Flutter hot reload.

flutter run -d emulator-5554

Confirmed by developer.android.com

Did this fix it?

Cause 4 of 4

A stored Quick Boot snapshot is stale or broken

1Check

The emulator saves a Quick Boot snapshot on exit and loads it on start. Android documents that if the emulator fails to boot from a snapshot you should cold boot.

# Android Studio > Device Manager > the device's menu > Cold Boot

2Fix

Use Cold Boot once. To avoid snapshots for this device, edit the AVD, open advanced settings, and set Boot option to Cold boot.

# Device Manager > Edit this AVD > Show Advanced Settings > Emulated Performance > Cold boot

3Verify

A fresh cold boot reaches the home screen and the app installs.

flutter devices

Confirmed by developer.android.com

Did this fix it?

How do I stop it coming back?

  • Keep at least 5 GB free where the Android SDK and AVDs live.
  • Leave Graphics on Automatic and only change it when a driver or emulator update breaks rendering.
  • Close heavy apps before starting the emulator; snapshot loads and saves need free RAM.
  • Update the emulator and system images from SDK Manager.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Google Play says the app does not support 16 KB memory pages

check_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8a

Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not.

5 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.