"Unfortunately, Google Play services has stopped." You tap OK. It comes back. Meanwhile Gmail won't open, the Play Store crashes on launch, Maps freezes — because nearly every Google-powered function on your phone runs through this one background service.
First, the reassurance: this error doesn't delete anything. Your apps, photos, and accounts are intact — the service connecting them to Google just crashed. You can't uninstall Google Play Services — it's a protected system component. The six steps below repair it instead, in the order most likely to work. Covers Android 10 through 14.
One distinction: this guide targets the single crash dialog — after a bad update, a restart, or when opening a specific app. If the popup returns every few seconds in an endless loop, that's the repeating variant, and our Google Play Services keeps stopping guide covers that loop specifically.
In This Guide:
- What "Google Play Services Has Stopped" Actually Means
- Fix 1: Restart and Force Stop the Crash Loop
- Fix 2: Clear Google Play Services Cache and Data
- Fix 3: Update Google Play Services Properly
- Fix 4: Uninstall Its Updates and Reinstall Fresh
- Fix 5: Fix Date & Time and Clear the Services Framework
- Fix 6: Re-add Your Google Account and Free Up Storage
- Watch: The Error Fixed Step by Step
- Frequently Asked Questions
What "Google Play Services Has Stopped" Actually Means
Google Play Services isn't an app you open — it's the background engine behind sign-in, push notifications, location, and sync for Gmail, Maps, the Play Store, and most third-party apps. When it crashes, everything built on top of it wobbles. The usual triggers:
- A bad or half-installed update: Play Services updates itself silently in the background. If the update corrupts — a reboot mid-install, a failed download — the new version can crash on launch.
- Corrupted cache or data: the service stores authentication tokens and sync state locally; stale or oversized cache can crash it.
- Wrong date and time: Google's servers reject authentication when the phone's clock drifts too far. Manual date/time settings are a classic, overlooked cause.
- Low storage: with almost no free space, the service can't write the files it needs and dies.
- A broken Google account sync state: a stale token in the account manager can crash the service every time it tries to authenticate.
Note: Google Play Store is a different app from Google Play services, and they crash independently. If your Store crashes without this dialog, our Google Play Store keeps crashing guide is the right one.
Fix 1: Restart and Force Stop the Crash Loop
If the dialog keeps reappearing, nothing else works until the loop stops. A restart clears the crashed process — and if the popup blocks the power menu, hold power + volume down for ~10 seconds to force a reboot:
- Hold the power button until the power menu appears, then tap Restart.
- After the reboot, wait a full minute before opening anything — Play Services finishes initializing in the background, and tapping apps too early can re-trigger the crash.
- If the dialog returns immediately, go to Settings → Apps → three-dot menu → Show system → Google Play services and tap Force stop. If Force stop is greyed out on your phone — that's normal — move on to Fix 2.
- Test by opening Gmail or the Play Store. If they launch, the crash was a one-time stuck process.
Fix 2: Clear Google Play Services Cache and Data
The most effective fix for this error. Clear cache removes corrupted temporary files without touching your apps, accounts, or data; clear data goes further, wiping the service's stored sync state and tokens so they rebuild cleanly. Do them in this order:
- Open Settings → Apps, tap the three-dot menu, and select Show system. Without this, Google Play services won't appear in the list.
- Scroll to Google Play services and tap it. (Careful: don't pick Google Play Store — similar name, different app.)
- Tap Storage & cache, then Clear cache.
- Restart the phone and test. If the dialog is gone, stop here.
- If it returns, go back to the same screen and tap Clear storage / Clear data, then Manage space → Clear all data if shown. This can reset things like saved Play Store payment methods — they re-sync, but may need re-verifying.
- Restart once more. The service rebuilds its data on boot, which takes a minute or two.
Samsung One UI: filter → Show system apps; Xiaomi HyperOS: Apps → Manage apps → three dots → Show all apps; Pixel: See all apps → three dots → Show system.
Fix 3: Update Google Play Services Properly
An outdated build is the most common trigger after a fresh setup or a long period offline. The tricky part: Google Play services doesn't always show an Update button in the Play Store. Here's how to force the update through:
- Open the Play Store, search "Google Play services", and open its page. If it shows Update or Install, tap it.
- If the page shows only Uninstall/Disable (or nothing useful), use the system route: Settings → tap your profile/Google account → All services → System services (on some phones: Settings → Security → Google Play services) and look for an Update prompt there.
- Still nothing? In the Play Store, open your profile → Manage apps & device → Updates available and update everything — Play Store, Google app, and Chrome.
- After updating, restart the phone — Play Services changes only fully apply on boot — and give it 10–15 minutes on Wi-Fi. The service sometimes finishes its own background update silently after that.
Fix 4: Uninstall Its Updates and Reinstall Fresh
If the error started right after an update, the update itself is the suspect. Rolling back removes the faulty version and lets your phone pull a clean copy:
- Go to Settings → Apps → Show system → Google Play services (same path as Fix 2).
- Tap the three-dot menu → Uninstall updates. This reverts the service to the factory version that shipped with your phone.
- Restart the phone. The factory version is stable by definition — the error should stop here.
- Now let it update cleanly: open any Google app (Gmail, Maps). It will prompt you to update Google Play services — accept, and let the update finish over Wi-Fi without interrupting it.
- If no prompt appears, use Fix 3's system route to update manually.
After uninstalling updates, some apps will refuse to open until the service updates again — that's expected, and it's why step 4 follows immediately.
Fix 5: Fix Date & Time and Clear the Services Framework
Two quiet causes live here. First, the clock: Google's servers reject authentication when your phone's time drifts more than a few minutes, and Play Services crashes instead of handling it. Second, the Google Services Framework — the component linking your phone to Google's servers — can hold corrupted sync data:
- Open Settings → System → Date & time (Samsung: Settings → General management → Date and time; Xiaomi: Settings → Additional settings → Date & time).
- Turn ON "Set time automatically" and "Set time zone automatically". If already on, toggle them off and on to force a fresh sync.
- Now clear the Framework's cache: Settings → Apps → Show system → Google Services Framework → Storage → Clear cache. (On some phones it's listed as Google Service Framework — same thing.)
- Restart the phone and watch for the dialog over the next hour. Framework-related crashes often return slowly, not immediately.
This sounds too simple to matter, but it's the fix behind many "appeared out of nowhere" cases — especially after crossing time zones or a dead battery resetting the clock.
Fix 6: Re-add Your Google Account and Free Up Storage
The final pair: a broken account authentication state, and a phone too full for the service to function:
- Remove your Google account (Settings → Accounts → Google → Remove account). This signs you out of every Google app but deletes nothing — everything is in the cloud.
- Restart the phone, then add the account back (Settings → Accounts → Add account → Google). A fresh sign-in generates new authentication tokens, which clears the stale-token crashes.
- If you see repeated "Authentication is required" errors during this process, our authentication-required fix guide handles that specific wall.
- Check storage: Settings → Storage. If free space is under ~1–2 GB, Play Services can't write what it needs — delete unused apps, clear large app caches, move photos to the cloud.
- Last check — a system update: Settings → System → System update. Old OS builds running new Play Services versions is a genuine mismatch source on older phones.
Watch: The Error Fixed Step by Step
This tutorial walks through the "Google Play services has stopped" repair on a real device:
Video by Izzy Laif — full credit to the creator.
Related Guides:
FAQs
What's the difference between "has stopped" and "keeps stopping"?
"Has stopped" is the one-time crash dialog — the service crashed once, often after an update or restart. "Keeps stopping" is the repeating loop, with the popup returning every few seconds. The fixes overlap, but the loop variant usually needs the deeper steps our keeps-stopping guide focuses on.
Will clearing Google Play Services data delete my apps or photos?
No. Clear cache removes temporary files only. Clear data removes the service's stored sync state and tokens — saved Play Store payment methods may need re-verifying. Your installed apps, photos, messages, and accounts are untouched.
Why does the error appear right after I restart my phone?
Play Services initializes during boot — corrupted data or a failed update makes it crash the moment it starts, which only looks like the restart caused it. Fixes 2 and 4 target exactly this.
Can I just uninstall Google Play Services?
No — it's a protected system component. You can only uninstall its updates (Fix 4), which reverts it to the factory version — the closest thing to a reinstall, and usually enough.
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026
