The Android emulator freezes with 'System UI isn't responding' during Flutter runs
System UI isn't respondingShort 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.
Fix it fast
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-check2Match what you see, then jump to its fix
- 1
The emulator will not start, or hangs soon after start, on a nearly full diskThe machine is short on free disk spaceFix - 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
Glitches or freezes right after an emulator or graphics driver updateThe graphics mode does not suit the machineFix - 4
The freeze happens every time the same virtual device starts from its saved stateA stored Quick Boot snapshot is stale or brokenFix
- 1
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 12Fix
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 images3Verify
The emulator starts and the dialog stops appearing.
emulator -list-avdsConfirmed by developer.android.com
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-ok2Fix
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 restart3Verify
-accel-check now prints that the hypervisor is installed and usable.
$ANDROID_HOME/emulator/emulator -accel-checkConfirmed by developer.android.com
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 auto2Fix
Start once with software rendering, or set Graphics to Software in the AVD's advanced settings.
emulator -avd <avd_name> -gpu swiftshader3Verify
The device boots and stays responsive for a few minutes of Flutter hot reload.
flutter run -d emulator-5554Confirmed by developer.android.com
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 Boot2Fix
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 boot3Verify
A fresh cold boot reaches the home screen and the app installs.
flutter devicesConfirmed by developer.android.com
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
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 fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 causes, each with a fixMobile apps
Gradle cannot create LibraryVariantBuilderImpl in a Flutter Android build
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl
This error appears when the Android Gradle plugin (AGP) cannot run in the Gradle or IDE you use.
3 causes, each with a fixMobile apps
Flutter release build cannot open the keystore: HmacPBESHA256 not available
Algorithm HmacPBESHA256 not available
The keystore is a PKCS12 file protected by a newer algorithm than the Java that is reading it understands.
3 causes, each with a fixMobile apps
Android install error: the package conflicts with an existing package of the same name
The package conflicts with an existing package by the same name
Android allows only one app per application ID, and an update must be signed with the same certificate as the installed version.
3 causes, each with a fixMobile apps
Android resource linking fails with resource android:attr/lStar not found
error: failed linking references.
The lStar attribute exists only from Android API 31.
2 causes, each with a fix