Pixel 9 and Pixel 10 battery drain issue: what's fixed
On July 30, Google marked a months-old bug "Fixed" in its public Issue Tracker. The bug is the Pixel 9 and Pixel 10 battery drain issue that's dogged owners since spring, and the closure didn't sit well with everyone: more than 50 comments piled up underneath, largely from users saying their phones still drain overnight (9to5Google, yesterday).
The fix is bundled into build CP2A.260705.006, covering the Pixel 9, 9 Pro, 9 Pro XL, 10, 10 Pro, 10 Pro XL, and 10a, according to Google's own comment marking the issue "Fixed" on its Issue Tracker. The bug's official title, "Severe Idle Drain: kepler_spi_irq_handler & gnss_ipc Suspend Aborts," names a specific failure mode, not a catch-all battery complaint (9to5Google, yesterday).
The evidence doesn't show Google's fix failed. It shows Google closed a narrowly defined bug without clearly explaining which devices, and which drain symptoms, that closure actually covers. Some post-update complaints may be the same GNSS suspend-abort bug slipping through despite the patch; others may be unrelated drain getting lumped in because Google never described the fix in terms anyone outside its engineering team could verify.
Sorting those two possibilities apart, rather than declaring the whole rollout broken, is the fairer read of what's happened this week. Drawing that line is Google's job, not something frustrated owners should have to work out in a comment thread.
What's fixed, what's promised, and what's still unaddressed
Before arguing about whether the fix works, it helps to know who it was ever meant to help. Google's coverage breaks into three tiers, and the gaps between them explain much of the frustration in the comments.
Fixed now, in the July update: Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, and Pixel 10a, according to Google's own comment marking the bug "Fixed" on its Issue Tracker.
Promised later, in the September QPR: Pixel 8a and Pixel 9a, which Google says will get the same fix roughly two months after the flagship rollout (Engadget, yesterday).
Not mentioned at all: Pixel 7 and standard Pixel 8 models, even though users reported similar idle-drain symptoms on those devices in the same Issue Tracker thread (9to5Google, yesterday).
That last gap is Google's first communication failure, separate from whether the July patch does what it claims for the phones it covers. Google hasn't said whether Pixel 7 and base Pixel 8 owners are covered by anything, which leaves those users watching their battery drain overnight with no sign that help is coming.
The Pixel idle battery drain fix: what Google says caused it
The reported mechanism is specific enough to describe in plain terms. Pixel phones are supposed to enter "Deep Doze" when locked, dropping the Tensor chip to its lowest power state. But the GNSS subsystem, the component that handles satellite positioning, reportedly kept failing to enter its own low-power state, generating continuous hardware interrupts that blocked Deep Doze from engaging at all (Android Authority, yesterday).
That pattern showed up even when it shouldn't have: some users saw the same drain with Airplane Mode on and every wireless radio switched off (Android Authority, yesterday). That's consistent with the GNSS suspend failure described in the report, rather than ordinary app activity or poor cellular reception.
Real-world reports illustrate how severe the problem could get. Some users said their battery offered only a few hours of use before needing a recharge (Engadget, yesterday).
Exactly when this started is less settled than the fix announcement suggests. Most reporting ties the bug's emergence to the March 2026 Pixel Drop, when a Pixel 9 Pro XL owner reported severe drain while the phone remained idle (Android Authority, yesterday). Engadget's account instead points to Google's April update as the trigger, describing a CPU that appeared to keep running in the background even while the phone sat unused (Engadget, yesterday). The two accounts may simply reflect first reports versus wider visibility of the same underlying problem, but the public record doesn't resolve which is accurate, so the exact origin date is worth treating as unsettled.
What post-update reports can and can't tell us
Google's public technical account, as far as the record shows, sits in a single Issue Tracker comment describing a fix merged into the July build for seven specific models. The July update's own changelog never mentions an idle-drain fix at all, leaving no public technical record of what actually changed (Tech Advisor, yesterday).
Three things can be said with confidence here, and keeping them separate matters more than picking a side:
- Established: Google marked the named bug "Fixed" and listed seven covered models (Android Authority, yesterday).
- Reported: dozens of commenters, including fresh reports from Pixel 10 owners, say drain persists on phones already running the July build (9to5Google, yesterday), and additional users describe the same excessive drain after installing the update (Tech Advisor, yesterday).
- Unresolved: nothing in the public record confirms whether those complaints trace back to the same kepler_spi_irq_handler and gnss_ipc failure Google diagnosed, or to something else entirely.
These are self-selected posts from people motivated enough to write in a bug thread, not standardized before-and-after battery measurements. A phone still losing charge faster than expected could be hitting a different trigger, running into a separate bug, or working through ordinary post-update reindexing, a temporary process that can resemble a battery bug before it settles down. Telling those apart would take battery statistics or the kind of internal telemetry Google already has, not another round of anecdotes.
A handful of users also report similar idle drain on Samsung Galaxy phones (Android Authority, yesterday), a data point worth watching but too thin to call this an Android-wide problem, and beside the point of whether Google's Pixel-specific patch worked. Persistent complaints mean something still needs explaining. They aren't, by themselves, evidence the July fix failed on the phones it targeted.
Where this leaves Pixel owners
Google's Issue Tracker status, the silent changelog, and user reports point in different directions, and untangling why matters more than picking one to believe. The most consistent reading: the July patch closed the GNSS suspend-abort bug for the phones Google named, while other causes of overnight drain, on covered and uncovered devices alike, remain open. That's a scope and communication failure, not proof the patch itself doesn't work.
Anyone with an affected device should check where their phone actually sits: covered now if it's a Pixel 9 or 10 model, covered in September if it's an 8a or 9a, and not included in the models Google named if it's a Pixel 7 or standard Pixel 8 (Android Authority, yesterday). That distinction explains why model coverage is part of the confusion driving the backlash in the comments.
What happens next matters more than the label on a ticket. Google could publish an actual technical account of what the July patch changed, name the failure mode in a public changelog instead of a buried comment, and say plainly whether Pixel 7 and Pixel 8 owners reporting the same symptom are hitting a diagnosed bug or something else. Until then, take Google's claim on its own terms: resolved, according to Google, for the failure mode it named, on the phones it named, unverified everywhere else.
Comments
Be the first, drop a comment!