Guide · 9 min read
Android Vitals Battery Drain: The Wake Lock Threshold That Costs You Play Store Rankings in 2026
Google and Samsung rolled out a formal battery-drain penalty for the Play Store starting March 1, 2026: apps that exceed a 5% excessive partial wake lock rate over a rolling 28-day window lose placement in recommendations, may drop in search ranking, and — worst of all — get a visible battery-drain warning on their store listing that users see before tapping install. Here's everything you need to understand, measure, and fix before the warning appears on yours.
Excessive partial wake lock: the 5% threshold and 2-hour session rule
Google flags your app as a battery-drain offender when more than 5% of user sessions in the previous 28 days accumulate excessive partial wake locks. A session is classified as excessive when it holds more than 2 cumulative hours of non-exempt wake lock time in a single 24-hour period. Both numbers matter: a single 3-hour wake lock on one device counts as one excessive session; a 20-minute wake lock occurring 7 times on the same device adds up to 2.3 hours and also counts as one excessive session.
A partial wake lock — created via PowerManager.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK, tag) — keeps the CPU running while the screen is off. It's the mechanism background tasks use to guarantee execution time: syncing data, processing notifications, uploading logs. Holding one for hours drains the battery at near-foreground rates without any screen-on justification — which is exactly why Google measures it separately from general background CPU usage. This is a deliberate API call, not an incidental processing cost.
The 28-day rolling window means a bad release haunts you for a full month even after you've shipped the fix. If your app was over threshold from October 1 to October 14, you will not fully clear the metric until November 11. Release the fix as fast as possible — waiting for the next sprint cycle costs four additional weeks of visibility penalty with no upside.
Battery-drain warning on your Play Store listing: what users see before installing
When an app crosses the 5% bad-session threshold, Google adds a visible warning badge to the Play Store product page reading approximately: "This app may drain your battery faster than usual." It appears in a prominent position on the listing — above the screenshots strip — and is visible to every user who lands on your product page, whether from search, recommendations, or a direct link.
The warning was developed in collaboration with Samsung and may appear across Samsung's Galaxy Store as well, doubling the surface where users see it. Unlike star ratings, which can be mitigated by driving new reviews, the battery-drain badge is binary: you are either under the threshold or you are not. A 4.5-star app with a battery-drain badge converts worse than a 3.9-star app without one in any category where battery life enters the consideration set — which in 2026 is most categories.
The practical impact is conversion drag even before the discovery penalty takes effect. Users who arrive via branded search still see the warning. Users who follow a press article link still see it. Your Play Store feature graphic still displays, but the battery-drain badge sits between the header and the screenshots, neutralizing the visual impression before the user reads your first line of description copy.
Play Store discovery exclusion: which recommendation surfaces you lose
Exceeding the excessive wake lock threshold removes your app from Google Play's algorithmic recommendation surfaces — the "For You" feed, "Similar apps" sections on competitor listings, and curated collection recommendations. For most indie apps, algorithmic recommendations drive 30–50% of organic installs, making discovery exclusion the more damaging part of the penalty compared to the listing badge.
The discovery exclusion compounds directly with the retention ranking signals Google already uses. Apps with strong DAU/MAU ratios and Day-30 retention normally receive a ranking lift in recommendations — see the Play Store retention algorithm guide for how those signals work. An app with adequate retention but a battery vitals violation gets excluded regardless of its retention score. An app with poor retention and a battery violation gets deprioritized at every stage of the organic funnel simultaneously, and the combined effect is disproportionate to either penalty alone.
Editorial featuring — the Today tab and curated collections — also requires clean Android Vitals. Google's editorial team screens apps for vitals status before surfacing them in promoted placements. An app that would otherwise qualify based on design quality and review ratings will not be selected if battery vitals are in the red. Fixing the wake lock issue is a prerequisite for competing on the surfaces where the highest-value installs originate.
Android vitals dashboard: locating the offending wake lock tag in Play Console
Open Play Console and navigate to Android vitals → Battery → Excessive partial wake locks. The dashboard shows your current bad-session rate as a percentage over the last 28 days, with a threshold indicator for green (below 5%), yellow (approaching), or red (over threshold). Below the summary, a table lists each wake lock tag name alongside its average hold duration and the percentage of sessions it appears in.
The tag name is the string passed as the second argument to PowerManager.newWakeLock(). Well-maintained SDKs prefix their tags with their package name — e.g., com.google.firebase.iid:wake-lock — making it straightforward to identify which dependency is responsible without reading source code. Sort the table by average duration descending: the tag with the longest average hold time is almost always the primary offender.
If the culprit tag is not recognizable as your own code, search the exact string on GitHub. Most Android SDK repositories include their literal wake lock tag in source, making it fast to confirm which library version introduced it and whether a newer version has already fixed it. The Android Vitals dashboard gives you the evidence to attach to a bug report if the fix has not shipped.
Common SDK offenders: the libraries most likely behind your excessive wake lock rate
The most common sources of excessive partial wake locks are push notification delivery SDKs, background location services, and raw PowerManager calls in app code that should have been migrated to WorkManager. In roughly that order, they account for the majority of threshold violations that Play Console surfaces to developers.
Firebase Cloud Messaging holds a wake lock during notification payload processing. For most apps this is brief enough to be irrelevant — but high-volume notification apps delivering hundreds of notifications per session can accumulate enough FCM wake lock time to cross threshold. The fix: ensure you are on the latest Firebase Android SDK (recent versions have reduced hold time significantly) and batch your notification dispatches rather than sending bursts of individual messages. If your own app code uses raw PowerManager.PARTIAL_WAKE_LOCK calls, migrating to WorkManager eliminates them entirely — WorkManager handles scheduling without holding a manual partial wake lock. This audit often surfaces alongside API 36 compliance work, since the same deprecated API patterns appear in both.
Background location tracking via LocationManager with a wake lock is the single most reliable way to exceed threshold in any non-navigation app. The pattern — keeping GPS active in the background with a manual wake lock to prevent process death — produces near-continuous excessive sessions for any user who runs the app in the background for more than two hours. The modern replacement is FusedLocationProviderClient with WorkManager or the Geofencing API, neither of which requires holding a partial wake lock manually. If your app uses continuous background location for a feature that does not demand it, consider whether that feature is worth the vitals cost — and audit whether it is actually used enough to justify it.
What is exempt: audio playback, foreground services, and user-initiated transfers
Three categories of wake lock usage are explicitly exempt from the excessive partial wake lock metric and do not count toward your 5% threshold: audio playback, user-initiated data transfers, and wake locks held inside a foreground service.
The foreground service exemption is the most widely misunderstood. If your app calls startForeground() and holds a partial wake lock inside that service, the session is not classified as excessive — the user has a visible notification confirming the app is running in the background. This is why music streaming and podcast apps are not penalized despite holding wake locks for hours: they use foreground services with audio-type classification. If you have a long-running background task with a legitimate user-visible reason, wrapping it in a foreground service is the correct pattern. Note that the 2026 Google Play permissions policy update added new constraints on which foreground service types are permitted — see the Play Store permissions update guide for whether your foreground service classification is still compliant.
User-initiated data transfers — anything triggered by a deliberate user action, such as tapping a download button or manually triggering a sync — are also exempt. The metric targets involuntary background drain, not drain the user consented to in the moment. Timer-based background sync that runs without user input is not covered by this exemption even if it operates on behalf of user data; it must be genuinely user-initiated at the session level to qualify.
ANR rate and crash rate: the other Android Vitals signals that affect Play Store ranking
Application Not Responding (ANR) rate and crash rate are separate Android Vitals metrics with their own thresholds that affect Play Store discovery — an ANR rate above 0.47% of daily active users, or a crash rate above 1.09%, triggers the same discovery exclusion as battery drain, without producing a visible listing badge.
The absence of a user-visible badge makes ANR and crash violations easier to miss. Your organic install rate may be declining because of discovery exclusion while your listing looks clean to users who do arrive. Pull the Android Vitals dashboard after every release and on a monthly cadence regardless. If your battery vitals are clean but organic install rate is flat or declining despite strong ASO work, ANR rate and crash rate are the next metrics to check.
All three metrics — battery drain, ANR, and crash rate — form the technical health cluster Google evaluates for recommendation eligibility. An app green on all three is eligible for the full recommendation surface. An app red on any one is excluded. These signals also feed directly into the Play Store retention ranking algorithm: apps with high Day-30 retention but poor vitals get deprioritized against apps with slightly lower retention and clean vitals, because Google's model treats poor vitals as a leading indicator of future churn.
Fix wake lock issues before the badge appears on your listing
The 28-day rolling window means the cost of delay compounds: every day you ship without a fix is another day of bad sessions accumulating toward threshold. Audit your Android vitals dashboard today, identify the offending tag, and ship the fix in your next release cycle — do not wait for a sprint.
A clean vitals dashboard is table stakes for recommendation eligibility in 2026. Once you are in the green, optimizing your Play Store listing — screenshots, feature graphic, short description — has full impact on every user who finds you. Check your Play Store screenshot sizes are at the correct dimensions while you are doing the technical cleanup pass; a listing audit tends to surface both issues at once.
Design your Play Store screenshots →
Frequently asked questions
what is the android vitals excessive partial wake lock threshold
Google flags an app when more than 5% of its user sessions in the previous 28 days hold excessive partial wake locks. A session is excessive when the app accumulates more than 2 cumulative hours of non-exempt wake lock time in a single 24-hour period. Both conditions must be met: the per-session threshold is 2 hours, and the bad-session rate threshold is 5% of all sessions over 28 days.
how do i find wake lock issues in play console
Open Play Console and go to Android vitals → Battery → Excessive partial wake locks. The dashboard shows your current bad-session rate and a table listing each wake lock tag name with its average hold duration. Sort by duration descending to identify the biggest offender. The tag name tells you whether the source is your own code or a third-party SDK — most SDKs prefix their tags with their package name.
do foreground services count toward the android vitals battery metric
No. Wake locks held inside a foreground service are exempt from the excessive partial wake lock metric and do not count toward your 5% threshold. Audio playback and user-initiated data transfers are also exempt. The metric targets involuntary background drain, not drain from services the user consented to through a visible notification.
which sdks commonly cause excessive wake lock issues on android
The most common sources are push notification SDKs (older Firebase Cloud Messaging versions during high-volume notification processing), background location services using LocationManager with a raw wake lock, and raw PowerManager.PARTIAL_WAKE_LOCK calls in app code that should be migrated to WorkManager. Search the exact tag string from your Android vitals dashboard on GitHub to identify which library version is responsible.
how long does it take for the battery drain warning to disappear after i fix the issue
The metric uses a 28-day rolling window, so the badge will not disappear until 28 days after your last excessive session. If you ship a fix today and it eliminates all future excessive sessions, the warning will be gone in 28 days. Partial improvements reduce your bad-session rate gradually — every clean day lowers your 28-day average.