Android 'Unfortunately, Settings has stopped' fix

Quick answer

Go to Settings > Apps > See all apps > Settings (gear icon) > Storage & cache > Clear cache. That's it. Restart your phone. You're done.

Why this happens

The Settings app is basically a system UI that reads configuration files stored as cached data. When that cache gets corrupted—usually after a system update, a failed app install, or a battery pull—the app crashes on launch. The error message "Unfortunately, Settings has stopped" is Android's generic way of saying "I can't parse my own config."

Google's Android System WebView has been a known culprit since Android 10. A bad WebView update can cascade into the Settings app because Settings uses WebView for rendering some UI elements (like the About phone screen). Samsung and Pixel devices are most prone to this, but it happens on any Android phone running 8.0 or later.

Main fix – clear Settings cache

1. Open your app drawer and tap Settings. If it crashes immediately, use the notification shade quick settings—long-press the gear icon there. That sometimes bypasses the crash.
2. If that fails, open Settings from the quick settings panel (swipe down twice, tap the gear). On some phones (Samsung One UI), you can also hold the gear icon for 5 seconds to enter a hidden system UI tuner.
3. Scroll down to Apps (or Applications on older Android).
4. Tap See all apps.
5. Find the app named Settings (gear icon). Not "Settings Storage" or "Settings suggestions"—the main one.
6. Tap Storage & cache.
7. Tap Clear cache. Do not tap Clear storage unless you're okay with resetting all your Settings preferences (Wi-Fi networks, display settings, etc.).
8. Go back, then restart your phone.

What's actually happening here is you're removing the corrupted temporary files that the Settings app reads at startup. The app rebuilds them fresh from the system config on next boot.

If that doesn't work – alternative fixes

1. Update or uninstall Android System WebView

Open the Play Store, search for Android System WebView. If there's an update, install it. If it's already up-to-date and Settings still crashes, uninstall updates: go to Settings > Apps > See all apps > tap the three-dot menu > Show system > find Android System WebView > tap the three dots > Uninstall updates. Restart your phone. I've seen this fix Settings crashes on Pixel 6 and 7 phones after a Chrome update broke WebView.

2. Boot into Safe Mode

Safe mode loads only system apps. If Settings works there, a third-party app is interfering. To boot safe mode on most Androids: press and hold the power button, then long-press Power off until the safe mode prompt appears. Tap OK. Once in safe mode, open Settings—if it works, uninstall recently installed apps one by one until the crash stops.

3. Wipe the cache partition

This clears system-level cache across all apps, not just Settings. It's a deeper clean. Steps vary by phone, but generally:

• Power off the phone.
• Press and hold Volume Up + Power (Samsung) or Volume Down + Power (Pixel) until recovery mode appears.
• Use volume keys to navigate to Wipe cache partition, press power to select.
• Confirm, then reboot.

This doesn't delete your personal data—only temporary system files. On Samsung Galaxy S21 and newer, you might need a USB-C to PC connection to enter recovery. Annoying, but it works.

4. Last resort – factory reset

If nothing else works, backup your data and do a factory reset. Go to Settings > System > Reset options > Erase all data (factory reset). This is nuclear, but it wipes whatever is corrupt at the system level. I'd only do this if you've tried everything above and the Settings app still crashes on every launch.

How to prevent it from happening again

Keep Android System WebView updated, but don't install beta versions. The beta track for WebView has caused Settings crashes on multiple Android versions (I've seen it on Android 11 and 13). Also, avoid force-closing the Settings app—let it manage its own cache. If you use a third-party launcher (Nova, Lawnchair), check for updates after a system update, because launchers can trigger Settings crashes when their overlays conflict with the new system UI.

One more thing: on Android 12 and later, disable Settings > Accessibility > Installed apps > Draw over other apps for any app you don't trust. Overlays from apps like Facebook Messenger or a flashlight app can cause the Settings UI to trip over itself.