"System UI has stopped": what it means and how to fix it

"System UI has stopped" (or "System UI isn't responding") means the part of Android that draws the screen around your apps has crashed. The status bar may vanish, the navigation buttons may stop working, and the message may come back every few seconds. It looks serious, but the cause is usually small and fixable.

What is System UI?

System UI is the app that draws everything around your apps: the status bar with the clock and battery, the notification shade, quick settings, the volume panel, the lock screen notifications and the navigation bar or gesture handle. Its package name is com.android.systemui, and every Android phone has one. Samsung, Xiaomi and others build their own versions on top of Google's.

Because so much depends on it, the system restarts System UI automatically when it crashes. That is why you see the error, a brief flicker, and then the status bar returns. When the crash repeats, the phone becomes hard to use. Our System UI page covers the app itself.

Why does System UI keep stopping?

The most common causes, roughly in order:

• A faulty update to a shared component. Android System WebView and the Google app are used by many parts of the phone. A bad release can crash apps across the system at once. In March 2021 a WebView update made apps crash on many phones at once until Google pushed fixed versions of WebView and Chrome.
• Themes, icon packs and launchers. Anything that changes how the system draws itself can feed System UI something it does not expect, especially right after a system update.
• Overlay and customization apps. Apps that draw over other apps, change the status bar, or add edge panels and gestures hook into the same areas System UI controls.
• Live wallpapers and home screen widgets that misbehave after an update.
• Very low storage. When the phone is almost full, apps cannot write the small files they need, and system parts crash first.
• A package removed or disabled with ADB. If you recently debloated the phone, a component System UI depends on may now be missing.
• A bug in a system update. Less common, and usually fixed by the next update.

How do I fix "System UI has stopped"?

Work down the list and stop when the error goes away. Each step is more disruptive than the one before.

1. Restart the phone

A restart clears a crash caused by a stuck process. If the error does not come back, you are done.

2. Undo the last change

Think about what changed just before the errors began. Switch back to the default theme and icon pack, set the stock launcher as your home app, remove new widgets, and switch to a static wallpaper. If you disabled packages with ADB, re-enable them. Our guide to restoring a disabled system app has the commands.

3. Update your apps and the system

Open the Play Store, tap your profile picture, then Manage apps & device, then Update all. Make sure Android System WebView, Chrome and the Google app are current. Then check for a system update in Settings. Phone makers often ship fixes for these crashes within days.

4. Roll back a recent update

If the crashes started right after one app updated, roll that app back. In Settings > Apps, show system apps, open the app (for example Android System WebView or Google), tap the three-dot menu and choose Uninstall updates. This returns it to the version that came with the phone. Let it update again a few days later, once a fixed version is out.

5. Test in safe mode

Safe mode starts the phone with only its own apps. On most phones you open the power menu, then touch and hold Power off or Restart until a Safe mode prompt appears. If the error stops in safe mode, an app you installed is the cause. Restart normally and remove recently installed apps one at a time until it stops.

6. Free up storage

Aim to keep a few gigabytes free. Delete large videos, clear downloads, and remove apps you no longer use. Settings > Storage shows what is taking the space.

7. Clear System UI's cache

In Settings > Apps, show system apps and open System UI. Tap Storage (or Storage & cache) and then Clear cache. Some phones hide this button for System UI; if yours does, skip this step. Do not clear its storage unless your phone maker's support tells you to.

8. Reset app preferences

On a Pixel this is Settings > System > Reset options > Reset app preferences; on Samsung it is in the three-dot menu of Settings > Apps. It re-enables disabled apps and resets default apps, notification blocks and background restrictions. It does not delete data, but you will need to set your defaults again.

9. Clear the cache partition or reset

Some phones, including many Samsung models, have a Wipe cache partition option in recovery mode. It removes temporary system files without touching your data. Your phone maker's support site lists the button combination. If nothing else works, back up your phone and do a factory reset from Settings > System > Reset options.

What if the error loops and I can't use the phone?

If the message reappears so fast that you cannot reach Settings, start in safe mode with the buttons. On most phones you power the phone off, turn it on, and hold Volume down while it starts until "Safe mode" appears in the corner. In safe mode, remove the app or theme you suspect, then restart normally. If you cannot get that far, recovery mode and a factory reset are the remaining options.

Can I disable System UI to make the error go away?

No. System UI is not an add-on you can live without. Disabling or removing com.android.systemui leaves the phone without a status bar, notifications, quick settings or navigation, and on many phones it causes a boot loop. Our verdict for it is Do not remove.

When should I contact my phone maker?

If the error continues after a factory reset, or appears on a brand-new phone, the cause is in the phone's own software or hardware. Contact the maker or your carrier, mention the exact message and the software version from Settings > About phone, and ask whether a fix is in a pending update.