How to Fix “Unfortunately Google Play services has stopped” on Android
What “Google Play services has stopped” means
Google Play services isn’t an app you open — it’s the background engine that a huge share of Android runs on. It handles location services, push notifications, Google sign-in, Maps, Gmail sync, Cast, in-app updates, and the Play Store’s connection to your phone. When you see “Unfortunately Google Play services has stopped,” that engine has crashed. Android restarts it automatically, which is why the pop-up sometimes comes back every few minutes like clockwork.
What makes this error annoying is the blast radius. Because so many apps lean on Google Play services, one crash can ripple outward: Maps loses your location, Gmail stops syncing, push notifications go silent, and third-party apps that use Google sign-in start failing too. People often blame the individual apps, but the common thread is the service underneath them. This pattern is especially common on Samsung, Xiaomi, and older budget phones after a major system or services update.
The good news: this is one of the most common and most fixable errors on Android. It’s almost never a virus and almost never hardware. Google Play services holds a lot of temporary data and sync state, and that data corrupts more easily than you’d expect — a bad update, an interrupted download, or storage dropping near empty can all leave it crashing on every launch. Clearing its cache ends the loop for most people, and updating it ends it for most of the rest. Work through the steps below in order, easiest first.
Common causes
- Corrupted cache or data in Google Play services: the most common trigger — a bad update or interrupted sync leaves the service crashing every time Android restarts it.
- Outdated Google Play services version: newer Google apps and third-party apps expect a newer services version; the mismatch crashes the old one repeatedly.
- Critically low storage: under roughly 1 GB of free space, the service can’t write its data files and enters a crash loop.
- Google Play services accidentally disabled: it can end up disabled after tinkering in Settings > Apps, leaving dependent apps and the service itself in a broken state.
- Botched system or services update: leftover corrupted temp files after an update can crash the service at every boot until the cache partition is wiped.
How to fix “Google Play services has stopped” — step by step
Start with steps 1 through 3 — a restart, a cache clear, and an update fix the great majority of cases without touching your data.
- Restart your phone and force-stop Google Play services. Hold the Power button, tap Restart, and wait for the phone to come back up. A simple restart ends the crashed services process and clears temporary memory buildup. If the pop-up keeps appearing, go to Settings > Apps, find Google Play services (tap the three-dot menu and choose Show system apps if you don’t see it), and tap Force stop. If this was a one-time crash, the message never comes back — you’re done in a minute.
- Clear the Google Play services cache — then its data if needed. Go to Settings > Apps > Google Play services and tap Storage & cache. Tap Clear cache first and use the phone for a while. If the crash returns, come back to the same screen and tap Manage space > Clear all data. A corrupted cache or data file in this core component is the single most common cause of the crash, and this step fixes it in most cases. You won’t lose your apps, photos, or files — you may just need to re-grant a few permissions afterward.
- Update Google Play services to the latest version. Open the Play Store, search for “Google Play services,” and tap Update if the button appears. If you can’t find the listing by search, go to Settings > Apps > Google Play services, scroll down, and tap App details in store to jump straight to it. Outdated services versions clash with newer Google apps, and an update often ends the crash loop on its own. While you’re there, open the Play Store menu and install all pending app updates too.
- Free up storage and set the correct date and time. Google Play services misbehaves badly when free space drops under about 1 GB — it can’t write its data files and crashes in a loop. Delete unused apps, old videos, and downloads in Settings > Storage until you have a few gigabytes free. Then go to Settings > System > Date & time and turn on “Set time automatically” and “Set time zone automatically.” A wrong clock breaks Google’s security certificates, which can silently crash the services underneath everything else.
- Reset app preferences and remove your Google account. Go to Settings > System > Reset options and tap Reset app preferences — this restores all disabled apps, default apps, and blocked notifications to their defaults without deleting any data, and fixes the case where Google Play services was accidentally disabled. If the crash persists, go to Settings > Passwords & accounts, remove your Google account, restart the phone, and sign back in. A corrupted account sync is a classic hidden cause of repeated services crashes.
- Install pending system updates — factory reset as a last resort. Go to Settings > System > Software update and install anything available; manufacturers regularly ship fixes for services-level crashes. Before resetting, boot into recovery mode (power off, then hold Power + Volume Up) and choose “Wipe cache partition” to clear corrupted system temp files without touching your data. If the crash still returns daily after everything above, back up your photos, messages, and files, then use Erase all data (factory reset) from Settings > System > Reset options. A clean system ends the error, but only take this step when nothing else worked.
Did this fix it? Quick checklist
- The “Google Play services has stopped” pop-up no longer appears after a restart
- Maps finds your location, Gmail syncs, and push notifications arrive normally
- Google Play services shows an up-to-date version in Settings > Apps
- You have at least 1–2 GB of free storage in Settings > Storage
If the pop-up only appears when you open one specific app, that app may be the trigger — update it, or test in safe mode (hold Power, long-press Power off, tap Reboot to safe mode) to see if a third-party app is the culprit. If it started right after you installed an app from outside the Play Store, uninstall that app first. And if you recently traveled, check the date and time — a phone stuck on the wrong time zone crashes Google’s security checks in a very convincing loop.
Frequently asked questions
What is Google Play services, and why does everything depend on it?
It’s the background engine behind most Google features on Android: location services, push notifications, Google sign-in, Maps, Gmail sync, Cast, and the Play Store itself. Third-party apps call into it constantly, so when it crashes, lots of unrelated apps misbehave at the same time.
Will clearing Google Play services data delete my photos, apps, or files?
No. Clearing the cache or data of Google Play services only removes its temporary files and sync state — your photos, apps, downloads, and accounts stay. You may need to re-grant a few permissions afterward, but nothing personal is lost.
Why can’t I uninstall Google Play services to fix it?
It’s a core system component, not a normal app — Android doesn’t offer an Uninstall button for it because removing it would break the Play Store, Maps, Gmail, and nearly every app that uses a Google sign-in. The correct moves are clearing its cache and data, updating it, and resetting app preferences, exactly as described above.
Does the “Google Play services has stopped” error mean my phone has a virus?
Almost certainly not. This is one of the most common software crashes on Android and is nearly always caused by a corrupted cache, an outdated services version, critically low storage, or a bad system update — not malware. If you downloaded an app from outside the Play Store right before it started, uninstalling that app in safe mode is worth a check.
Why does the error keep coming back every few minutes?
Because something restarts the crash loop each time Android relaunches the service. The usual loop triggers are a corrupted data file (fixed by Manage space > Clear all data), a services version that conflicts with your apps (fixed by updating it), or storage so full the service can’t write (fixed by freeing space). Work through steps 2 to 4 in order and the loop breaks.