In This Article
The android.process.media keeps stopping error is one of the oldest Android crashes still in circulation, originally caused by a corruption in the media scanning service that indexes audio, video, image, and download files for every app that asks. On Android 15 and 16 the underlying media provider has been rewritten under scoped storage, but the error message persists when its database gets corrupted or when a third-party app pushes malformed metadata into it.
The fix is almost always a clean cache reset of the Media Storage and Download Manager system apps, in the right order. This guide walks the full fix sequence in under five minutes, plus the deeper steps for the small set of cases the cache reset does not resolve.
TL;DR
The pick: The pick: Clear storage on Media Storage and Download Manager in Settings, All apps, show system. Reboot. Resolves more than eighty percent of cases.
Runner-up: Runner-up: Boot into Safe Mode to identify the third-party app pushing malformed metadata, almost always a music tagger, gallery app, or downloader.
Skip if: Skip if: The error only appears when a specific external SD card is mounted. That is hardware, not the media provider, and the fix is to replace the card.
For a deeper reference, see Google’s official Android Help Center.
What the error actually means
Android maintains a system-wide media index, the MediaProvider, that catalogues every audio, image, video, and document file across internal storage. The android.process.media service runs that indexer plus the Download Manager. When its SQLite database gets corrupted, by a malformed ID3 tag, a broken JPEG EXIF block, a truncated file from a failed download, or a third party app writing garbage into a tracked location, the service crashes and Android shows the keeps stopping dialog.
On Android 15 and 16 the underlying database lives in a scoped-storage area you cannot reach directly. The fix path is to clear the system app cache and storage, which forces a full rebuild of the index from scratch.
The clean cache reset, in order
Open Settings, Apps, See all apps, then tap the three dot menu and choose Show system. Scroll to Media Storage. Tap it, then Storage and cache, then Clear cache, then Clear storage. Repeat for Download Manager. Reboot the phone. The MediaProvider rebuilds the index on first boot, which takes between thirty seconds and a few minutes depending on how much media is on the device.
On a Samsung Galaxy the system app name is different, Media Storage may appear as External Storage. The flow is identical. On Xiaomi and Oppo skins the menu path is the same but the system app may be labelled differently in localized regions, look for Media Storage or Media Provider.
When that does not fix it, the Safe Mode test
If the error returns within minutes of reboot, a third party app is pushing bad metadata into the index. Boot into Safe Mode, hold power, long press Power off in the dialog, accept Reboot into Safe Mode. Safe Mode disables every third party app. If the error disappears, the culprit is a third party app, almost always a music tagger like Music Tag Editor, a gallery alternative like Simple Gallery Pro, or a downloader like Advanced Download Manager.
Uninstall the suspect apps one at a time, reboot out of Safe Mode after each one, and watch for the error to return. The last app uninstalled before stability returned is the cause.
The SD card factor
If the error only fires when an external microSD card is mounted, the card is dying. Failing SD cards return read errors on individual sectors, which corrupts the media files stored there, which makes the indexer crash repeatedly trying to read them. Move important files off the card, run a full chkdsk or fsck through a desktop card reader, and replace the card if errors persist. A SanDisk Ultra or Samsung EVO microSD costs less than ten dollars and is an order of magnitude more reliable than a no-name card.
Phones launched in 2024 and 2025 from Pixel and OnePlus dropped the microSD slot entirely, so this section only applies to Samsung Galaxy A series, Motorola, and the budget Android segment.
The nuclear option, reset app preferences
If clear cache, Safe Mode, and SD card replacement all fail to resolve the issue, the system app permission grants may be corrupted. Settings, Apps, three dot menu, Reset app preferences. This re-enables disabled system apps, resets notification preferences, and clears default app associations. It does not delete user data. After the reset, reboot and re-grant any permissions the apps prompt for.
The truly nuclear option is a factory reset, Settings, System, Reset options, Erase all data. Back up first. A factory reset always resolves the error because it rebuilds the entire MediaProvider state from scratch on first boot.
The setup, step by step
- 1
Clear Media Storage
Settings, Apps, show system, Media Storage, Storage and cache, Clear storage.
- 2
Clear Download Manager
Same flow, find Download Manager in system apps, clear storage.
- 3
Reboot
Power off and on, wait for the index to rebuild, normally a minute or two.
- 4
Boot into Safe Mode
Hold power, long press Power off, accept Reboot into Safe Mode.
- 5
Uninstall suspect apps
Music taggers, alternative gallery apps, and downloaders are the usual culprits.
FAQ
Does clearing Media Storage delete my photos?
No. Media Storage is the indexer that catalogues your media, not the storage itself. Clearing it forces the index to rebuild from your actual files, which remain untouched. You may temporarily see fewer photos in the Gallery until the rebuild completes.
Why does the error keep coming back?
Because a third party app is continuously pushing malformed metadata or corrupt files into a tracked storage area. Boot into Safe Mode to confirm the third party app cause, then uninstall the culprit, usually a music tagger, a gallery alternative, or a downloader.
Will a factory reset definitely fix it?
Yes, a factory reset always fixes the error because it rebuilds the entire MediaProvider state from scratch on first boot with no inherited bad data. It is the nuclear option, only use it after the cache reset, Safe Mode test, and SD card check all fail.
Does this affect newer phones like the Pixel 8a?
Less often than older phones, because Android 14 and newer use a more resilient MediaProvider implementation under scoped storage. When it does happen on a Pixel 8a, the same cache reset flow applies and resolves it just as fast.
Bottom line
The android.process.media keeps stopping error is a database corruption issue at heart, and the fix order, clear cache on Media Storage and Download Manager, Safe Mode test for third party app culprits, SD card check, reset app preferences, factory reset, resolves nearly every case. The first two steps take five minutes and clear the vast majority. If you are still seeing it after a factory reset, that points to failing internal storage, which is a hardware issue.
