How to Fix “Google Play Services Keeps Stopping” on Android

To fix the “Google Play services keeps stopping” error on Android, restart your device, clear the cache for both Google Play Services and the Google Play Store, and ensure Android System WebView is fully updated. If background crashes continue, clearing Play Services storage and re-authenticating your primary Google account will rebuild corrupted system database tokens and restore background sync.

Quick Take: Fastest Working Solutions

If you need to stop repeated crash popups immediately, apply these proven fixes in order of speed and diagnostic impact:

Initial Diagnostics and Prerequisites Before Troubleshooting

Before modifying application storage or altering system permissions, check these three core device prerequisites to prevent troubleshooting errors:

Step-by-Step Fixes for Google Play Services Crashing

Work through the following sequence progressively. The steps start with non-destructive cache clearances and move to deeper system resets only if the error persists.

Step 1: Perform a Clean System Restart

A standard soft restart terminates zombie processes, clears volatile RAM, and forces the Android init system to reload fundamental background framework daemons. Hold your device’s Power and Volume Up buttons simultaneously, select Restart, and allow the operating system to complete its full boot cycle before opening any apps.

Step 2: Clear Cache for Google Play Services and Play Store

Corrupted temporary cache files in either the Play Services client library or the Google Play Store client can cause continuous crash loops. Clearing the cache removes temporary files without touching saved logins, payment methods, or app data.

1. Open your device Settings and tap Apps (or Apps & notifications).
2. Tap See all apps, then locate and select Google Play services.
3. Tap Storage & cache, then select Clear Cache.
4. Navigate back to the app list, select Google Play Store, tap Storage & cache, and tap Clear Cache.

If app store downloads remain stalled after clearing the cache, you may also need to troubleshoot pending Play Store downloads to release hung download manager queues.

Step 3: Clear Storage for Google Play Services

If clearing the cache does not resolve the crash popups, the underlying local SQLite database used by Play Services may be corrupted. Clearing storage resets this database entirely.

Critical Data Warning: Clearing storage for Google Play Services will delete locally cached transit cards, COVID-19/health passes, and virtual payment card tokens stored in Google Wallet. You will need to re-verify your payment cards once the service restarts, as documented in the official Google Play Help guide.

1. Open Settings > Apps > See all apps > Google Play services.
2. Tap Storage & cache, then tap Clear Storage (or Manage Space on older Android builds).
3. Tap Clear All Data at the bottom of the screen and confirm the prompt by tapping OK.
4. Restart your device to allow the Play Services daemon to generate a clean local database.

Step 4: Force an Update for Google Play Services

Google Play Services runs as a background framework that distributes core APIs—including location tracking, OAuth authentication, and Play Integrity checks—independently of major OS upgrades, as detailed in the Google Play services developer documentation. If an automated background update stalls, you can trigger a manual check:

1. Open Settings and navigate to Security & privacy (or Google > All services on newer Android versions).
2. Scroll down and tap System services > Google Play services.
3. Tap Update if a newer build is available.
4. Alternatively, open your mobile browser and navigate directly to the hidden Google Play Store package link for Play Services to check for a pending update button.

Step 5: Update or Roll Back Android System WebView and Google Chrome

Many system-level Google crashes are not caused by Play Services itself, but by the rendering engine powering its embedded login dialogs: Android System WebView. When a WebView update contains a broken compilation flag, any background service attempting to render authentication prompts will terminate abruptly.

1. Open the Google Play Store, tap your profile icon in the top-right corner, and select Manage apps & device.
2. Under the Updates available section, check for Android System WebView and Google Chrome.
3. If updates are available, tap Update for both packages.
4. If the crashes began immediately after an update, go to Settings > Apps > Android System WebView, tap the three-dot menu in the upper right corner, and select Uninstall updates to roll back to the factory-installed version.

This rollback technique is confirmed in an Android Community Product Expert advisory as the primary recovery method during widespread rendering engine regressions.

Step 6: Reset Android App Preferences

If an app has restricted background data access, disabled critical notification channels, or revoked system-level runtime permissions from Play Services, the daemon may crash whenever it attempts an unauthorized hardware call. Resetting app preferences restores all default permissions without wiping your personal files or installed applications.

1. Go to Settings > System > Reset options (on Samsung devices: Settings > Apps > Three dots > Reset app preferences).
2. Tap Reset app preferences.
3. Confirm by selecting Reset apps.

This action re-enables any inadvertently disabled system services and resets background battery restrictions to factory defaults, which is useful when attempting to troubleshoot app crashes on Android across multiple applications simultaneously.

Step 7: Remove and Re-Add Your Primary Google Account

When OAuth security tokens become invalid or synchronization handshakes lock up on Google’s remote authentication servers, the local Play Services process crashes in an infinite loop trying to refresh the session.

1. Open Settings > Passwords & accounts (or Accounts & backup > Manage accounts on Samsung).
2. Select your primary Google account.
3. Tap Remove account and confirm your device PIN or biometric prompt.
4. Restart your phone immediately.
5. Return to Settings > Passwords & accounts, tap Add account > Google, and sign back in with your credentials.

Once re-authenticated, your phone will re-sync your contacts, calendar entries, and cloud preferences cleanly. You can fine-tune these connections through your device settings to manage Google account sync settings properly.

How to Verify That Google Play Services Is Stable

After completing the troubleshooting steps, verify that the background service has stabilized before returning to normal use:

1. Check Play Protect Status: Open the Google Play Store, tap your profile avatar, select Play Protect, and tap Scan. A successful scan confirms that system security APIs are communicating normally.
2. Trigger a Manual App Update: Download or update any lightweight app from the Play Store to ensure the package installer daemon and download queue execute without errors.
3. Test Location Services: Open Google Maps and tap the crosshair icon. If your device locates your position immediately without throwing a service error, Play Services location APIs are functioning.
4. Verify System Firmware Patch Level: Ensure your underlying OS framework is updated to match newer Play Services API requirements via the official Android update support page.

Advanced Troubleshooting: OEM Limits and System Integrity

If standard storage and account resets fail to stop the crashes, the issue typically stems from OEM-specific background process management, architecture mismatches, or modified firmware.

Aggressive OEM Battery Optimization (Samsung, Xiaomi, OnePlus)

Hardware manufacturers frequently implement custom battery-saving software that force-closes background services to extend battery life. When an OEM task-killer terminates Google Play Services while it is writing to a system database, the database becomes corrupt, resulting in persistent crash loops.

To prevent OEM interference, navigate to Settings > Apps > Google Play services > Battery and set the policy to Unrestricted. On Samsung One UI devices, open Settings > Battery > Background usage limits and verify that Play Services is not listed under Sleeping apps or Deep sleeping apps. Adjusting these parameters helps you correctly manage Android battery optimization settings without breaking critical push notification channels.

Corrupted APK Sideloads and CPU Architecture Mismatches

Manually sideloading Google Play Services APK files from third-party repository sites is a leading cause of fatal service stops. Google distributes Play Services in distinct variant packages compiled for specific CPU architectures, screen pixel densities (DPI), and Android API levels.

Installing an armeabi-v7a (32-bit) build on a modern arm64-v8a (64-bit) device—or installing a build targeting Android 15 on an Android 13 device—causes immediate crashes. If you previously sideloaded a package, go to Settings > Apps > Google Play services, tap the three dots in the upper right, and tap Uninstall updates to revert to the factory build compiled for your specific hardware.

Custom ROMs, Root Conflicts, and Play Integrity Failures

If you run a custom Android ROM (such as LineageOS or Pixel Experience) or have modified system partitions with root solutions like Magisk or KernelSU, Google’s Play Integrity API and hardware attestation routines will flag the environment. If the underlying GApps package (such as NikGApps or MindTheGapps) was flashed with incorrect partition permissions, system binaries will fail to mount.

To isolate software conflicts from third-party root modules, boot Android in safe mode to evaluate if Play Services runs stably without background overlay interference.

Where This Approach Has Limits

While software troubleshooting resolves the vast majority of Play Services errors, certain hardware and platform conditions cannot be fixed through system settings alone:

• End-of-Life Android Versions: Google periodically deprecates Google Play Services support for legacy Android releases. If your device runs Android 5.0 (Lollipop), Android 6.0 (Marshmallow), or earlier, newer Play Services APIs are no longer backported, and certain cloud-dependent services will stop working permanently.
• Non-GMS Certified Devices: Modern Huawei smartphones and uncertified grey-market Android devices lack official Google Mobile Services (GMS) licensing. Sideloaded GMS frameworks on these devices frequently crash due to server-side device certificate rejections by Google.
• Physical eMMC or UFS Flash Memory Degradation: If your smartphone suffers from hardware-level bad sectors in its internal flash memory, database tables written by Google Play Services will continually corrupt regardless of how many times you clear data or factory reset. If crashes return within hours of a full factory wipe across multiple apps, the flash storage hardware is failing.

Key Takeaways

Frequently Asked Questions