The popup itself is almost the least of it. "Google Play Services keeps stopping" appears, you tap Close app, and it comes back a minute later — but meanwhile the real damage spreads quietly: Gmail stops syncing, Maps can't pin down your location, the Play Store opens to a blank screen, and notifications from half your apps simply never arrive.
That's because Google Play Services isn't really an app. It's the shared engine room underneath Google's apps and thousands of third-party ones, handling sign-in, push notifications, location, and downloads on their behalf. When it crashes in a loop, everything that rents space in that engine room stumbles with it. The encouraging part: a looping crash almost always traces back to Play Services' own version or data — both of which you can repair. The fixes start there.

Quick Answer: Treat the version first: open Settings → Apps → Google Play Services → App details in store and install any pending update. If it's already current — or the popup began right after it updated — clear its cache (Storage & cache → Clear cache), then roll its updates back (Fix 3). Those three moves between them end most crash loops. Covers Android 10 through 14.
In This Guide:
- Fix 1: Update Play Services Before Anything Else
- Fix 2: Clear the Cache It's Tripping Over
- Fix 3: If It Started After an Update, Remove That Update
- Fix 4: Clear Its Data for a Genuinely Fresh Start
- Fix 5: Correct the Clock
- Fix 6: Reset App Preferences (Revives Disabled Components)
- Fix 7: Use Safe Mode to Catch an Interfering App
- Signs the Fault Runs Deeper Than Play Services
- Play Services Questions, in Plain English
Fix 1: Update Play Services Before Anything Else

An outdated Play Services build falling behind the apps that depend on it is the single most common reason the crash loop starts. Apps update constantly; if Play Services lags a few versions behind, eventually one of them asks it to do something it doesn't understand yet, and down it goes — repeatedly.
- Go to Settings → Apps → Google Play Services. (Not visible? Tap the three-dot menu → Show system.) On Samsung (One UI) it's Settings → Apps; on Xiaomi (HyperOS), Settings → Apps → Manage apps.
- Scroll to App details in store and tap it — this opens Play Services' own Play Store page, which search often won't show you.
- If an Update button is there, tap it and let it finish.
- Restart the phone and use it normally for ten minutes. If the popup stays away, you're done.
This route also matters when the Play Store itself won't open properly — the settings shortcut reaches the update page without needing the store to behave first.
Fix 2: Clear the Cache It's Tripping Over

Play Services accumulates temporary files around the clock — location data, sync state, authentication tokens. A damaged file in that pile can crash the service every time it reaches for it, which is why the popup returns on such a regular rhythm:
- Open Settings → Apps → Google Play Services again.
- Tap Storage & cache (on Samsung, simply Storage).
- Tap Clear cache — cache only, for now.
- Restart the phone and watch for the popup over the next few minutes of normal use.
Clearing the cache deletes nothing of yours. It forces Play Services to rebuild its temporary files from scratch, and if one of those files was the problem, the loop ends here.
Fix 3: If It Started After an Update, Remove That Update
The mirror image of Fix 1: sometimes the crash loop begins within hours of Play Services updating itself, because the new build has a bug that only shows up on certain phones. The timeline is the give-away — phone fine yesterday, update overnight, popups all morning.
- Open Settings → Apps → Google Play Services.
- Tap the three-dot menu in the top-right corner and choose Uninstall updates.
- Restart the phone. Play Services is now back to the version it shipped with — older, but stable.
- Leave it there for a day or two, then let it update again through Fix 1's store page. By then, the version on offer is typically the corrected one.
Don't try to prevent the update forever. Play Services genuinely needs to stay current for security and for other apps to work; the rollback is a bridge across a bad release, not a destination.
Fix 4: Clear Its Data for a Genuinely Fresh Start
If the cache clear didn't break the loop, the corruption sits deeper — in the service's stored data rather than its temporary files. Clearing data resets Play Services to the state it was in when the phone was new:
- Go to Settings → Apps → Google Play Services → Storage & cache.
- Tap Clear storage — on some phones this is labelled Manage space → Clear all data.
- Restart the phone and give it a few minutes connected to Wi-Fi.
Set expectations correctly: your Google account, apps, and files all survive — nothing personal is stored in Play Services. What does happen is a short re-sync period, and a handful of apps will ask again for permissions they were granted long ago. That flurry is normal and settles quickly. Because of it, this fix sits fourth and not first: it's heavier than a cache clear, and most loops never need it.
Fix 5: Correct the Clock
Play Services spends its life negotiating secure connections with Google's servers, and those servers check your phone's clock as part of the handshake. A device whose time has drifted — after a long flight, a dead battery, or a manual change — can have its requests refused so abruptly that the service crashes rather than reporting a polite error.
- Open Settings → System → Date & time. On Samsung (One UI), it's Settings → General management → Date and time; on Xiaomi (HyperOS), Settings → Additional settings → Date & time.
- Turn on Automatic date & time (also called "Set time automatically") and Automatic time zone.
- If they were already on, switch them off and on again to force a resync.
- Restart the phone and check whether the popup returns.
Fix 6: Reset App Preferences (Revives Disabled Components)
Here's a cause nobody suspects: Play Services depends on a small crowd of other system components, and if one of them was disabled at some point — by you tidying up, or by another app — Play Services can crash every time it reaches for the missing piece. Resetting app preferences switches everything back on:
- Go to Settings → Apps.
- Tap the three-dot menu and choose Reset app preferences, then confirm.
- Restart the phone.
The honest cost: this also resets permissions and notification settings for all apps, so over the next few days apps will ask again for camera, location, and notification access as you use them. No app data is deleted. It's a mild nuisance in exchange for reviving anything that was wrongly switched off.
Fix 7: Use Safe Mode to Catch an Interfering App
If the loop survives everything so far, ask a different question: is something else on the phone breaking Play Services? Safe Mode answers it by running the phone with only its built-in apps:
- Hold the power button, then long-press Power off on screen until Reboot to safe mode appears, and tap OK.
- Use the phone in Safe Mode for a while — open Maps, Gmail, the Play Store.
- If the popup stops, a third-party app is interfering. Restart normally and uninstall recently added apps one at a time, checking after each, starting with the newest.
- If the popup continues in Safe Mode, the fault is in the system itself — move to the closing section.
Signs the Fault Runs Deeper Than Play Services
A crash loop that survives Safe Mode is telling you the problem sits below app level. Work through these in order: first, storage — open Settings → Storage and free space until at least 2–3 GB is available, because Play Services needs room to write its working files and misbehaves badly on a full phone. Second, the system itself — install any pending update under Settings → System → System update (Samsung: Software update; Xiaomi: About phone → HyperOS version), since a half-applied system update can leave Play Services mismatched with the OS. Only after both should a factory reset enter the conversation, and only after a full backup via Settings → System → Backup. It's genuinely the last door, not the next one. Covers Android 10 through 14.
Play Services Questions, in Plain English
Can I just uninstall Google Play Services and be done with it?
No — and you wouldn't want to. It's a core system component with no full uninstall option, and disabling it breaks sign-in, notifications, location, and the Play Store across most of the phone. The closest available move is Fix 3, uninstalling its updates, which is safe and reversible.
Why did this start the morning after my phone updated?
Because updates are the trigger in both directions. Sometimes a new Play Services build carries a bug that crashes on particular models (Fix 3 exists for exactly this); sometimes a system update leaves an older Play Services behind, and the mismatch crashes it instead (Fix 1). The morning-after timing narrows the diagnosis to those two fixes.
The popups stopped, but my battery is draining faster. Connected?
It can be. A crashing service that restarts constantly works far harder than a healthy one, and heavy battery use by Play Services during a crash-loop period is a known side effect. Once the loop is fixed, give the phone a full charge cycle — if Play Services still tops the battery list afterwards, revisit Fix 4, since a fresh data reset also clears stuck sync loops that keep the service awake.
Watch: Google Play Services Has Stopped Fixed Step by Step
Prefer a walkthrough? This video covers the 'Google Play Services has stopped' error step by step:
Video by Global TechWorld Solutions — full credit to the creator.
Related Guides:
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026