Google has marked the Pixel idle battery drain bug as Fixed on its public Issue Tracker, closing out a complaint that has run since the March 2026 Pixel Drop. The entry, issue 525509065, is titled “Pixel 9 Pro XL Severe Idle Drain: kepler_spi_irq_handler & gnss_ipc Suspend Aborts (March/April 2026)” and now carries a Fixed status. Owners replying to the same thread say their phones are still draining.
What the Pixel idle battery drain bug actually does
The symptom is a phone that burns through its battery while doing nothing at all — screen off, in a pocket, overnight. The cause named in the tracker title is a set of suspend aborts tied to the GNSS (satellite positioning) subsystem and an SPI interrupt handler. In plain terms, a piece of the hardware keeps waking the system up, so the phone never settles into Deep Doze, the deepest idle state Android has. Nothing on screen tells you this is happening; you just wake up to a battery figure that does not add up.
The report is big enough that it is not even the original thread. Google’s own first comment on the current entry reads: “Thank you for reporting the issue. As a bug https://issuetracker.google.com/issues/502262230 has reached its comment limit, we have created this new issue. Please provide your comments here.” An earlier bug filed on the same problem hit the tracker’s comment ceiling and had to be replaced.
Which Pixels get the fix, and when
The fix is attached to the July 2026 Pixel update, build CP2A.260705.006. Per Android Authority’s reading of the tracker, it covers the Pixel 9, 9 Pro and 9 Pro XL and the Pixel 10, 10 Pro, 10 Pro XL and 10a, with the Pixel 8a and Pixel 9a scheduled for September. Android Police, reading the same tracker, notes that Pixel 8 and Pixel 7 owners who reported the same behaviour are not named in that list at all.
- Fixed now (July build): Pixel 9, 9 Pro, 9 Pro XL, Pixel 10, 10 Pro, 10 Pro XL, 10a
- Scheduled for September: Pixel 8a, Pixel 9a
- Not named: Pixel 8 and Pixel 7 series
- Status: Fixed on Issue Tracker 525509065, last updated 30 July 2026
Why owners are not convinced
Two things are working against Google here. The first is that its own July changelog never mentioned this. The published release notes for CP2A.260705.006 list five fixes — app crashes, widget colour and contrast, a boot loop, wallpaper shape effects, and navigation button alignment on the Pixel 10 Pro Fold — and battery is not among them. If you installed the July patch three weeks ago, you had no way of knowing it was supposed to have solved your battery problem.
The second is that the reports have not stopped. Android Police and Android Authority both report owners on the July build still describing the same overnight drain, and the tracker entry was still being updated today. A status flag is Google’s assessment of its own code, not a measurement of your phone.
This is the second Pixel bug this month where the fix reached users before any acknowledgement did — the Pixel 4a boot loop was resolved the same way, quietly, with owners confirming it before Google documented anything. Shipping a fix silently and then closing the ticket costs Google nothing and leaves owners to work out on their own whether the problem they have been living with since March is actually over.
What to do if your Pixel is still draining
Check Settings > About phone > Android version > Build number and confirm you are on CP2A.260705.006 or later; carrier variants in Australia and on Rogers carry a .A1 suffix on the same build. If you are on that build and the drain persists, add your report to issue 525509065 with your model, build and a battery-usage screenshot. Reports on the existing entry are more useful than a fresh duplicate, and the thread is the channel Google has been using to communicate on this bug.
Sources: Google Issue Tracker, Android Authority, Android Police
