Turning off Google Play Services-linked activity on one Android phone produced nearly two extra hours of battery life. The test pointed away from Google Play Services itself and toward the Google app as the main source of the drain.
Discover and Hey Google
The phone was still using battery with the screen off, and Google Play Services sat near the top of the battery list. The Google app was driving most of the activity, because its location access, voice features, and background syncing kept calling on Play Services through wake locks.
Two changes cut that load. Discover stopped the Google app from loading articles and images in the background for the feed. Hey Google in the Gemini app, under Talk to Gemini hands-free, stopped the microphone from listening around the clock for the wake word.
Restricted Google app battery use
Setting the Google app’s battery use to Restricted went further by limiting background jobs, scheduled tasks, and network activity. That setting does not shut the app down entirely. It narrows when the app can wake up and keep work going after the screen turns off.
Android already uses Doze mode and App Standby to rein in background activity. Even so, the phone test showed those tools did not prevent the Google app from keeping Play Services busy enough to show up as a battery issue.
Play Store battery standards
Late 2025 brought a stricter battery bar on the Play Store. Excessive wake-lock tracking became a core quality standard, and Google and Samsung set out to close the gap in wake-lock tracking.
That matters because wake locks let an app keep the processor running after the screen turns off. If Google Play Services looks like the obvious culprit, the fix may be to test the app that is triggering it first, then switch the features back on if something useful disappears.
The open question is how much battery life the same Google app changes would save on other Android phones.
