Android 14 'System UI Isn't Responding' Fix After Update

You tapped the update button, the phone rebooted, and now every few minutes you get that gray "System UI isn't responding" dialog with Wait and Close app buttons. Close app makes it worse. Wait makes it come back. I've seen this on Pixels after the March 2024 patch, on Samsung One UI 6.1 devices, and on a bunch of Motorola Edges that pulled the February build late. The culprit is almost always one of three things: a corrupted SystemUI cache, a third-party overlay (yes, your icon pack counts), or a stale framework resource from the OTA that didn't unpack cleanly.

Work down this list. Stop when the dialog stops appearing. Reboot between steps if you can, it resets things and makes the next test meaningful.

Step 1 — The 30-second fix: hard reboot and safe mode

I know, "turn it off and on" is a cliche. It's also the fix about 20% of the time here, so don't skip it. A proper hard reboot clears the zygote state and any half-initialized SystemUI process from the OTA.

Hold Power + Volume Up for about 12 seconds until the screen goes black and the boot logo reappears. On Pixels it's Power + Volume Down. On Samsungs, hold Power and tap Restart, then pick Restart again.
Let it fully boot. Don't touch anything for 60 seconds after the lock screen appears.
If the dialog comes back within two minutes, boot into Safe Mode. Hold Power, then long-press the Restart option on screen. You'll see a "Safe mode" prompt.

In Safe Mode, every third-party app is disabled. If SystemUI behaves in Safe Mode but not normally, you've got a bad overlay or a rogue app. If it still crashes in Safe Mode, the problem is at the system level and you can jump to Step 3.

Quick check: did you install any icon pack, theme, or APK the night before you updated? That's your prime suspect. Uninstall it before you do anything else.

Step 2 — The 5-minute fix: clear SystemUI and launcher data

This is the fix that works most often. SystemUI keeps its state in /data/system_ce/0/ and caches a ton of stuff in its own data directory. When the OTA lands, that cache often points at resources that no longer exist, and SystemUI spends its whole life retrying and timing out. Watchdog kills it, the dialog shows up, everyone has a bad day.

You can't clear SystemUI data from the Settings app — the option is grayed out on most builds. Use ADB instead. Enable Developer Options (tap Build number seven times in About phone), turn on USB debugging, plug into a PC with platform-tools installed.

adb shell pm clear com.android.systemui
adb shell pm clear com.google.android.apps.nexuslauncher
adb shell pm clear com.sec.android.app.launcher

On a Pixel the launcher is com.google.android.apps.nexuslauncher. On Samsung it's com.sec.android.app.launcher. On OnePlus it's com.oneplus.launcher. Clear whichever matches your device. If you don't know, run this first:

adb shell pm list packages | grep -i launcher

The screen will flash black and the wallpaper resets. That's normal. SystemUI respawns immediately. Give it 60 seconds to rebuild its cache, then check whether the dialog returns.

If you don't have ADB and don't want to install it, you can do a rough equivalent from Settings: Apps > Show system apps > System UI > Storage > Clear cache. Clearing data there is usually blocked, but the cache clear alone fixes a surprising number of cases.

Step 3 — The 15-minute fix: wipe cache partition or roll back the patch

If Step 2 didn't take, the framework cache itself is likely stale. You need to wipe the cache partition. Most modern Android 14 devices don't expose this from the recovery menu anymore (Google killed it on Pixel 5 and later in favor of A/B seamless updates), but Samsungs, Motos, Nokias, and most OnePlus models still do.

Power off completely.
Hold Volume Up + Power (or Volume Up + Bixby + Power on older Samsungs) to boot into recovery.
Use volume keys to highlight Wipe cache partition, hit Power to select.
Pick Reboot system now.

This does not touch your data. It clears /cache and the dalvik/ART intermediate files, which is exactly where the OTA left its garbage.

No cache partition option? You've got two remaining options:

Option A: Uninstall SystemUI updates

On some OEM builds, SystemUI itself is delivered as a component update. Go to Settings > Apps > Show system apps > System UI > three dots > Uninstall updates. This rolls SystemUI back to the factory build baked into the ROM. It'll pull the update again on the next Play Store sync, but by then the cache is clean.

Option B: Roll back via OTA or Fastboot

If you're on a Pixel with an unlocked bootloader, flash the previous factory image with the --skip-reboot flag using the flash-all.bat script from Google's factory images page. You'll lose nothing but time. If you're locked, sideload the previous OTA via ADB:

adb reboot recovery
adb sideload previous-ota.zip

Make sure you grab the OTA for the exact build you were on before the patch. Flashing a wrong-build OTA aborts with a signature error, which is annoying but harmless.

What doesn't help (skip these)

Factory reset. It's the nuclear option and it rarely fixes this specific error because the issue is in system caches that a factory reset does clear, but it also wipes your data for something ADB fixes in 30 seconds. Try the steps above first.
"Battery optimization off for System UI." Doesn't touch the ANR watchdog. Skip it.
Third-party "phone cleaner" apps. They often make this worse by killing SystemUI at bad moments and triggering the dialog themselves.
Clearing data on Google Play Services. Related symptom, unrelated cause. You'll just have to sign back into everything.

If nothing worked

You're probably looking at a genuinely broken patch for your specific device and build number. Check your build fingerprint under Settings > About phone > Build number and search the exact string. If you're on a Pixel 6 or 7 with the March 2024 build AP1A.240305.019.A1, for example, there were widespread SystemUI reports. Google shipped a hotfix within a week. In that case, the right move is to wait for the next OTA, or sideload it early from Google's OTA images page.

One last thing: if the dialog only appears right after unlock, not during use, that's a different bug — usually a lockscreen widget or the fingerprint HAL timing out. Clear the lockscreen widgets in Settings > Display > Lock screen and see if it clears up.