How to Fix com.google.android.gms (Google Play Services) High CPU on Android
com.google.android.gms is Google Play Services, the background engine that syncs your Google account, location and app updates. A high CPU reading is usually caused by a stuck sync, an app hammering location, or corrupted service cache. Clear its cache, fix the syncing app, and update the service instead of disabling it. This illustrated guide covers 3 methods and 21 steps, with a separate picture for every step.
-
1. Check battery and CPU usage
Open Settings, Battery, then Battery usage and switch the view to show system processes. Confirm Google Play Services is actually high rather than an app using it.
-
2. Note what you were doing
Remember whether the spike began after installing an app, a system update, or enabling location, so you can target the real trigger later.
-
3. Restart the phone
Hold the power button and tap Restart. This clears a stuck background sync that often causes the CPU to stay high indefinitely.
-
4. Recheck after the restart
Wait a few minutes after the phone boots, then check usage again. If the CPU has dropped, the cause was a temporary stuck process.
-
5. Open Google Play Services app info
Go to Settings, Apps, see all apps, and tap Google Play Services. If it is hidden, use the app info shortcut from a search in Settings.
-
6. Clear the cache
Tap Storage and cache, then Clear cache. This removes temporary files without signing you out or deleting personal data.
-
7. Reboot once more
Restart the phone again so the service restarts cleanly with fresh temporary files.
-
8. Update Google Play Services
Open the Google Play Store, tap your profile icon, then Manage apps and device, and update Google Play Services if an update is offered.
-
9. Update the Google Play Store itself
In the same Updates area, update the Play Store app as well, since an old store can leave services out of date.
-
10. Update the app that caused the spike
Update the most recently installed or updated app, because outdated apps often loop on an old Google API call.
-
11. Check Play Protect
In the Play Store, open Play Protect and run a scan to rule out a malicious app driving the CPU load.
-
12. Clear the Google Play Store cache
Open the Play Store app info, go to Storage and cache, and clear its cache to fix a stuck download loop.
-
13. Verify services are current
Reopen Google Play Services app info and confirm it shows a recent version and no pending update.
-
14. Check CPU again under normal use
Use the phone normally for ten minutes, then recheck battery usage to confirm the CPU has settled.
-
15. Review accounts on the phone
Open Settings, Accounts and check for an old or duplicate Google account that may be failing to sync in the background.
-
16. Remove a stale account
If you find an account you no longer use, remove it so Play Services stops retrying the sync repeatedly.
-
17. Check apps with location access
Open Settings, Location, app permissions, and list apps allowed to use location all the time.
-
18. Restrict unnecessary location access
Change location permission to 'Only while using the app' for apps that do not need background location.
-
19. Turn off background Wi-Fi scanning
In Settings, Location, Location services, switch off Wi-Fi and Bluetooth scanning if you do not rely on them.
-
20. Pause large Google Photos backup
Open Google Photos, go to Backup settings and pause backup temporarily to see if the CPU load drops.
-
21. Watch CPU after each change
Change one setting at a time and recheck usage, so you can identify which trigger was responsible.