Google Play Store Now Warns You About Apps Hogging Your Phone's Battery Life

Google Play is tightening control on how Android apps use wake locks, linking poor behaviour to store visibility. A new “Excessive Partial Wake Lock” metric in Android Vitals now guides developers, and repeated breaches may trigger warnings on Play Store listings and reduced presence across discovery areas.

The wake lock technical quality enforcement targets apps that keep devices awake in the background for long periods. According to Google, affected apps may see warning banners on their store page, lower ranking in recommendation feeds, and closer tracking within Android Vitals next to measures like crashes and ANRs.

'Excessive Partial Wake Lock' Explained

Google defines the “Excessive Partial Wake Lock” threshold using recent user sessions. A non-exempt partial wake lock held for at least two hours on average, with the screen off, in more than 5% of sessions over the previous 28 days, counts as excessive and can trigger enforcement treatment.

Some wake locks are treated as acceptable because they follow direct user choices. Exemptions cover audio playback, location use that the user started, and user-initiated data transfers such as uploads or downloads. These activities may continue to use wake locks without affecting the “Excessive Partial Wake Lock” metric in Android Vitals.

Google Play Metric Design

The metric was built with input from Samsung and refined after feedback from app creators. It moved out of beta last year and is now active for all developers. The measure focuses on how long apps hold partial wake locks during typical user sessions, helping teams understand where battery drain occurs.

Google explains that foreground services and partial wake locks behave differently and should be used for separate tasks. Foreground services keep an app alive for visible work but still allow the CPU to sleep. Partial wake locks block CPU sleep, so developers are advised to acquire them rarely and release them as soon as possible.

Google Play Optimisation Tools

Google recommends starting with the Android Vitals dashboard to identify problematic wake locks. If the source is unclear, developers can record a System Trace and analyse it using the Perfetto UI to locate inefficient code paths, including those in third-party SDKs.

The company advises reviewing or replacing inefficient SDKs and using system tools instead of manual wake locks. For user-initiated uploads or downloads, developers should use the UIDT API, while WorkManager is recommended for periodic background tasks, with checks on worker stop reasons to avoid misconfigured jobs.

For specific use cases, Google suggests companion device APIs for Bluetooth operations, system-managed wake locks with WorkManager for location tracking, and sensor batching, the Recording API, or Health Connect for frequent sensor activity. For remote messaging, developers should use Firebase Cloud Messaging, holding wake locks only while processing network packets.

These wake lock quality measures are being rolled out gradually across affected apps on the Google Play Store, with updated documentation and developer feedback channels provided by Google.