Android "Unfortunately, X has stopped" — Real Fixes

You're using an app on your Android phone — could be a Samsung Galaxy S23, a Pixel 7, or even a budget Moto G — and suddenly you get that dialog box: "Unfortunately, [app name] has stopped." No details, no traceback, just a dead app and a shrug from your phone.

What's actually happening here is that the app's process crashed — either because it ran out of memory, hit a corrupted cache entry, or couldn't load a resource. Android's ActivityManager detects the unhandled exception and shows that dialog. But here's the thing: 90% of the time, it's fixable without a factory reset. Let me show you how, starting with the fix that works most often.

Clear the App Cache — The First Thing to Try

This is the most common cause. Android apps store temporary files in a cache directory — think thumbnails, auto-filled form data, downloaded images. Over time, that cache can get corrupted: maybe a file was partially written when the phone ran low on storage, or an app update left stale data from the old version. When the app tries to read that corrupted file on launch, boom — it crashes.

Clearing the cache doesn't delete your login info or personal data. It just wipes those temp files. Here's how:

1. Open Settings → Apps (or App Manager on Samsung).
2. Find the app that's crashing — scroll the list or search for it.
3. Tap Storage (or Storage & cache).
4. Tap Clear cache. Don't touch Clear data yet.

That's it. Restart the app and see if the crash is gone. On my Pixel 7, this fixed a stubborn Google Photos crash that appeared after the December 2023 update. The cache had a corrupted thumbnail index from an old backup process.

Clear App Data — When Cache Isn't Enough

If clearing the cache didn't work, the problem likely runs deeper. The app's main data store — its database, settings files, saved credentials — might be corrupt. This is common after restoring a phone from backup, or when an app update changed its data schema and the old data doesn't match.

Clearing app data is more aggressive: it resets the app to its fresh-out-of-the-box state. You'll lose any local settings, login sessions, or offline files. For apps like Gmail or WhatsApp, the cloud will sync your data back after you sign in again. But for offline games like Alto's Odyssey, say goodbye to your progress unless it was backed up.

1. Same path: Settings → Apps → pick the app → Storage.
2. This time, tap Clear data (or Manage storage → Clear all data).
3. Confirm the dialog — it's a one-way door.

Launch the app again. It'll behave like you just installed it. On a Samsung Galaxy A54, this fixed "Unfortunately, Messages has stopped" that happened every time you tried to open an MMS — the SMS database had a corrupt message header from a failed import.

Uninstall Updates — The Nuclear Option for System Apps

Sometimes the crash is on a system app you can't remove — like Google Play Services, Samsung Health, or Android System WebView. These are built into the OS, but they get updated through the Play Store. And sometimes an update rolls out with a bug. The fix here is to uninstall the updates, reverting the app to the factory version that originally shipped with your phone.

Why would a system app update cause a crash? Google and manufacturer apps are tested against Google's own framework, but not always against every custom ROM variant (One UI, ColorOS, MIUI). A WebView update in early 2023, for example, crashed Chrome on some Xiaomi phones because it conflicted with a custom skin change.

1. Go to Settings → Apps → tap the three-dot menu (top-right) → Show system apps.
2. Find the system app that's crashing — for example, Android System WebView.
3. Tap the app, then tap the three-dot menu again → Uninstall updates.
4. Confirm. It'll take a few seconds, and the app returns to the factory version.

After this, go to the Play Store, find that app, and tap Disable auto-update (in the app's Play Store page, tap the three-dot menu, uncheck Enable auto-update). You can wait a few days for Google to push a fixed version, then manually update.

This fix saved my mom's Xiaomi Redmi Note 12 when "Unfortunately, Settings has stopped" appeared after a MIUI update. The Settings app's latest update had a layout bug on that specific screen resolution — reverting fixed it instantly.

Quick-Reference Summary Table

If none of these work, you might be dealing with a hardware issue — bad RAM or storage — or a deeper OS corruption that needs a factory reset. But in my experience, one of these three fixes handles 9 out of 10 "Unfortunately, X has stopped" dialogs. Try them in order. Don't jump straight to a factory reset.