System UI has stopped or System UI isn’t responding error affects the part of Android that draws and manages the phone interface.
When System UI crashes, you may see problems with:
- the status bar;
- notification shade;
- Quick Settings;
- navigation buttons or gestures;
- lock screen;
- recent apps;
- parts of the Home screen.
The most useful first question is:
Did the problem start after an Android update, after installing or changing an app, or when the phone became nearly full?
That usually points you toward the right fix much faster than trying random resets.
Do not disable or remove System UI. It is a core Android component responsible for navigation and other interface elements. Diagnose the crash rather than treating the component as an unwanted app.
Start With the Symptom
Use the behavior of the phone to narrow it down.
| What happens | What to check first |
|---|---|
| One crash, then phone works normally | Restart |
| Crashes began after an Android update | System update, launcher, system cache if available |
| Crashes stop in Safe Mode | Third-party app conflict |
| Home screen and recents also fail | Launcher or theme |
| Notification shade and status bar fail | System UI itself |
| Phone is nearly full | Storage |
| Crashes continue in Safe Mode | Android system or firmware issue |
| Phone is unusable even after restart | Manufacturer support or recovery options |
1. Restart the Phone
Restart once before making deeper changes.
A normal reboot reloads System UI and other Android processes.
If the error does not return, it was probably a temporary process failure.
If the phone is frozen, use the manufacturer-specific forced restart method for your device.
2. Install Pending Android Updates
If System UI started crashing after a recent software change, first check whether a newer patch is available.
Open the phone’s software-update settings and install any pending update.
On Pixel:
Settings > System > Software updates
On Samsung:
Settings > Software update
Other Android brands use similar menus.
A manufacturer may release a follow-up patch when a firmware update introduces interface instability.
If the phone is already fully updated, continue below instead of repeatedly checking for the same update.
3. Test Safe Mode
Safe Mode is one of the most useful diagnostic steps when System UI crashes repeatedly.
Google says Safe Mode temporarily disables downloaded apps. If the problem disappears there, a third-party app is likely responsible.
The exact Safe Mode method varies by manufacturer, so use the method for your phone.
Once in Safe Mode, use the phone for a few minutes.
The error stops in Safe Mode
Focus on recently installed or updated apps.
Common conflict candidates include:
- third-party launchers;
- theme apps;
- icon packs;
- lock-screen apps;
- screen overlay tools;
- cleaner or booster apps;
- battery-management utilities.
Remove recent apps one at a time and restart normally after each removal.
If you have trouble leaving Safe Mode, see Android Stuck in Safe Mode.
The error continues in Safe Mode
A downloaded app becomes less likely.
Focus next on:
- Android updates;
- launcher data;
- storage pressure;
- system cache where supported;
- firmware problems.
4. Clear the System UI Cache
Some phones let you access System UI from the app list.
Open:
Settings > Apps
Then show system apps if needed and open System UI.
If the phone provides a cache option:
Storage > Clear cache
Clearing cache removes temporary files.
Do not clear System UI storage casually. Resetting its stored data can change interface behavior and settings, and many devices do not expose that option anyway.
If your phone does not show System UI in the Apps list, skip this step.
Clearing this cache does not erase photos, contacts, messages, downloaded files, or installed apps. Keep it distinct from Clear storage, which resets stored data rather than just temporary files.
5. Check the Default Launcher
System UI and the launcher are separate components, but they interact closely.
If the Home screen, recent apps, widgets, or gesture navigation also started failing, test the launcher.
If you use a third-party launcher
Switch back to the manufacturer’s default launcher.
Then restart the phone.
If the error stops, the launcher or one of its customizations is likely involved.
If you use the default launcher
Update it through Google Play, Galaxy Store, or the manufacturer’s normal update path if an update is available.
Do not clear launcher storage first unless you are prepared to rebuild the Home screen layout.
If you recently changed Home screen behavior, see How to Remove the Search Bar From an Android Home Screen for launcher-specific differences.
6. Remove Recent Theme, Icon, Overlay, or Cleaner Apps
This step is most useful when the crash started soon after customization.
Temporarily remove or disable:
- custom themes;
- icon packs;
- font replacement tools;
- lock-screen customization apps;
- screen overlay utilities;
- aggressive cleaner apps;
- battery optimization utilities.
Then restart the phone.
Do not uninstall unrelated apps in bulk.
The goal is to test the most plausible recent change.
7. Free Up Storage if the Phone Is Nearly Full
Very low free storage can make Android less stable.
Google recommends freeing storage when the device is nearly full because it can affect app and system performance.
Open:
Settings > Storage
Remove or move:
- large videos;
- old downloads;
- unused apps;
- duplicate files;
- offline media.
There is no need to target an arbitrary percentage.
The important point is to avoid running Android with almost no free space.
For a more complete cleanup process, see How to Free Up Storage Space on Android.
8. Reset App Preferences Only When System Apps Were Disabled or Restricted
Reset App Preferences can help when you previously changed system-app behavior.
It can restore things such as:
- disabled apps;
- default apps;
- some permissions;
- background restrictions;
- notification settings.
Use it when you suspect a required system component was disabled or restricted.
Do not use it as a routine System UI fix just because restarting failed.
See Reset App Preferences on Android for what changes and what does not.
9. Wipe the Cache Partition Only if Your Phone Still Supports It
Some Android phones, especially certain Samsung models, still provide a recovery option called Wipe cache partition.
This can be worth trying when the problem begins after a major firmware update.
The exact recovery method varies by model.
If your phone does not show a cache-partition option, skip it.
Many newer Android devices no longer expose this function.
Do not select Wipe data/factory reset by mistake.
10. Check Whether the Problem Is Actually Android System Intelligence
System UI and Android System Intelligence are not the same thing.
Use this page when the interface itself is failing, such as:
- status bar crashes;
- notification shade freezes;
- navigation disappears;
- recent apps stop responding;
- lock-screen interface breaks.
If the error message specifically says Android System Intelligence keeps stopping, use Android System Intelligence Keeps Stopping instead.
That component powers smart features and requires a different troubleshooting path.
11. What to Do if the Crash Started Immediately After an Update
If System UI was stable before an Android update and began crashing immediately afterward:
- Restart once.
- Install any newer system patch.
- Update the launcher and Google system components.
- Test Safe Mode.
- Remove recent launcher or theme customizations.
- Use cache-partition recovery only if the device supports it.
If the crash continues even in Safe Mode, a firmware bug becomes more plausible.
Google’s Android support notes that system updates are managed by the device manufacturer, so persistent post-update crashes should be reported to the manufacturer when normal troubleshooting does not resolve them.
12. When a Factory Reset Is Actually Reasonable
A factory reset should be late in the process.
Google explicitly recommends trying other troubleshooting steps before resetting because a factory reset erases the phone’s local data.
Consider it only when:
- System UI still crashes in Safe Mode;
- the phone is fully updated;
- storage is not critically low;
- launcher and customization conflicts have been ruled out;
- the problem is severe enough to make the phone difficult to use;
- the manufacturer has no better recovery step.
Before resetting:
- confirm your Google Account credentials;
- back up photos, contacts, messages, and important files;
- make sure you can restore any authenticator or banking access you need.
Do not factory-reset simply because System UI crashed once or twice.
13. When Manufacturer Support Makes More Sense
Contact the manufacturer or an authorized repair center when:
- the phone cannot stay usable long enough to back up data;
- System UI crashes even in Safe Mode;
- the problem began after a failed update;
- the phone repeatedly reboots;
- touch, display, audio, or other hardware functions also fail;
- the device was dropped or exposed to liquid;
- the error continues after a properly completed factory reset.
At that point, the problem may involve firmware corruption or hardware rather than a normal app conflict.


