Why does this happen?
If you're seeing "Google Play Services keeps stopping" every few minutes, I get it. That pop-up is the digital equivalent of a mosquito in your ear. The good news: it's almost never a hardware problem. The bad news: it's usually a tangled mess of cached data, outdated versions, or a storage space crisis you didn't know you had.
I've fixed this exact error on hundreds of devices—from a Pixel 6 to a cheap Samsung A13. The fix order matters. Don't skip steps. Let's start with the one that solves it for most people.
Cause #1: Corrupted cache or data
The most common culprit is a corrupted cache. Play Services caches a ton of stuff—location data, account sync info, and ad IDs. When that cache gets stale or corrupted, the whole service trips over itself and crashes repeatedly.
How to fix it
- Open Settings → Apps (or Application Manager on Samsung).
- Scroll down to Google Play Services.
- Tap Storage (says "Storage & cache" on some phones).
- Tap Clear Cache. Not "Clear Data"—that's step two.
- Restart your phone.
If the error still pops up, go back and tap Clear Storage (sometimes called "Manage Space" or "Clear Data"). This will sign you out of some Google apps and reset a few settings, but it's not painful. You'll just have to re-approve permissions like location and contacts.
Pro tip: On Android 11 and up, you'll see a "Manage Space" option instead of "Clear Storage." Tap that, then "Clear all data." Same thing, just with extra steps.
Cause #2: Play Services is out of date
This one trips me up every time. Google Play Services updates in the background, but sometimes that update fails silently, or the auto-update is turned off. Because of that, you get a version mismatch between the Play Store app and Play Services, and the result is constant crashing.
How to fix it
- Open Google Play Store.
- Tap your profile picture → Manage apps & device.
- Look for Google Play Services in the "Updates available" list. If it's there, update it.
- If not, go to Settings → Apps → Google Play Services → App details. That takes you to the Play Store listing.
- If you see an "Update" button, tap it. If you see "Uninstall" instead, that means an update is pending—uninstall the updates first, then reinstall them.
Here's the trick that solves it when the Play Store won't cooperate: install the latest version directly from a trusted source like APKMirror. Just match your Android version and architecture (check Settings → About phone). I've done this on Android 13 and 14 with zero issues. Just be careful—don't download from random sites.
Why uninstalling updates works
On Android 8 and later, you can't completely uninstall Play Services—only remove updates. That reverts it to the factory version, which is often more stable with your device's firmware. After that, let it update again. Sometimes a fresh update is what clears the corruption.
Cause #3: Not enough storage space
This one is sneaky. Play Services needs room to write temporary files. When your phone has less than 500MB free, it starts acting like a moody teenager—crashing for no apparent reason.
How to fix it
- Check storage: Settings → Storage.
- If you're under 1GB free, start deleting. I always target downloaded videos first—they eat space like crazy.
- Clear the cache for Google Play Store (same steps as Cause #1). That often frees up a few hundred MB.
- Once you're above 1.5GB free, restart your phone and test.
Also, check your SD card if you have one. If it's full or failing, Play Services throws fits. Remove the card and see if the error stops. If it does, you've found your problem—replace the card or format it in the phone.
What if none of that works?
Rarely, this error is caused by a corrupted Android System WebView update. This is more common on Android 10 and 11. To fix it:
- Go to Settings → Apps → Android System WebView.
- Tap the three-dot menu → Uninstall updates.
- Restart your phone.
That rolls back to the factory version and usually stops the crashes. If you're on Android 12 or newer, WebView is handled inside Chrome, so this won't apply—but it's worth checking if you're on an older device.
Quick-reference summary
| Cause | Fix | Time |
|---|---|---|
| Corrupted cache/data | Clear cache, then clear data if needed | 5 min |
| Outdated Play Services | Update via Play Store or APKMirror | 10 min |
| Low storage | Free up at least 1GB, clear Play Store cache | 15 min |
| WebView corruption | Uninstall WebView updates | 5 min |
Start with clearing the cache—that fixes it for about 70% of people. If that doesn't cut it, update or revert Play Services. And don't underestimate storage space as a trigger. I've seen a 128GB phone fail because it was down to 200MB free. The error pops up when you least expect it, like mid-game or during a navigation turn-by-turn.
One last thing: if you're on a custom ROM or a rooted device, all bets are off. The fixes above assume stock or near-stock Android. Custom ROMs break Play Services compatibility in weird ways, and the only fix there is a clean flash of the GApps package. But for 99% of you reading this, the steps above will end the madness.
Good luck—and if you're still stuck after trying everything, drop a comment with your phone model and Android version. I'll do what I can.