Google says it has resolved a severe idle battery-drain problem that has affected Pixel owners since the company’s March and April 2026 software releases. The fix is included in the July update for several newer models, while two A-series phones are scheduled to receive it later.
The problem is that numerous owners say their phones are still losing power rapidly after installing the supposedly corrected software. Some report that the July update produced little or no improvement, while others own Pixel models that Google did not include in its fix announcement.
Google marked the relevant Pixel Issue Tracker report as fixed and said the correction had been merged into July build CP2A.260705.006. The listed devices include the Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL and Pixel 10a. The Pixel 8a and Pixel 9a are expected to receive the fix through a September quarterly update.
This Was More Than Ordinary Post-Update Battery Drain
A Pixel can temporarily use more power after installing a software update. The phone may need to optimise applications, rebuild system data and relearn usage patterns before battery performance returns to normal.
Google’s own battery-drain troubleshooting guide says a modest increase in consumption can be normal for several days after an update. It advises contacting support when unusually high drain continues beyond that adjustment period.
The issue reported throughout 2026 was considerably more severe. Some affected phones reportedly lost large portions of their charge while sitting unused, with the screen off. Others continued draining in airplane mode, suggesting that ordinary mobile-data usage, social-media activity or weak cellular coverage could not fully explain the problem.
Early reports described phones that previously lasted an entire day suddenly requiring two or three charges. In April, one Google Issue Tracker thread attracted nearly 600 comments in less than ten days, while an Android Authority reader poll found that 75.9% of its self-selected respondents had noticed increased drain after a recent update. That poll does not represent every Pixel owner, but it reinforced the scale of the complaints.
The Bug Appears to Have Kept Phones Awake
The technical issue identified in the tracker involved kepler_spi_irq_handler activity and gnss_ipc suspend aborts.
GNSS refers to the satellite-positioning system used for location services. A suspend abort occurs when the phone begins entering a low-power state but is awakened before that process completes. When this happens repeatedly, the processor cannot remain in its deepest idle mode for long enough to conserve energy.
Android normally relies on a power-management system known as Doze. When a phone has been unused for a period, background activity is reduced and the device enters progressively deeper sleep states. These states are essential because a smartphone may spend most of the day with its screen switched off.
Reports associated with the Pixel bug suggested that frequent system-level interrupts were repeatedly waking the processor. That could explain why affected phones remained warm or consumed substantial power even when no ordinary application appeared responsible in the battery-usage screen. Google’s decision to name those specific suspend failures in its fix statement supports the conclusion that the company addressed at least one system-level cause of the drain.
Why Some Owners Say the Fix Has Not Worked
There are several possible explanations for the disagreement between Google’s status update and user reports.
The first is that “fixed” in an issue tracker can mean that engineers have merged a correction into a particular software branch. It does not necessarily prove that the change resolves every similar battery complaint across every phone, mobile network and usage pattern.
Some phones may also be suffering from different problems that produce the same visible symptom. A malfunctioning application, poor cellular signal, damaged battery, aggressive background synchronisation or another Android service can all cause rapid battery loss. Fixing the GNSS-related suspend bug would not correct those unrelated causes.
However, the response cannot be dismissed entirely as confusion. Current comments from Pixel 9 and Pixel 10 owners indicate that at least some phones running the specified July build are still experiencing severe idle drain. Reports gathered after Google closed the issue include complaints that battery life remains unchanged or that the phone still fails to sleep properly.
It is also possible that the correction works only under certain combinations of modem firmware, carrier settings, Google Play services versions or location usage. Software bugs involving power management can be difficult to reproduce because they may depend on network conditions and background events that do not occur consistently.
Pixel 7 and Pixel 8 Owners Have Been Left Uncertain
One of the strongest objections concerns the phones Google did not mention.
Reports of excessive drain have appeared across several Pixel generations, including the Pixel 7 and Pixel 8 families. Yet Google’s fix statement names the Pixel 9 and Pixel 10 series, followed by the Pixel 8a and Pixel 9a for September. It does not explain whether the regular Pixel 8, Pixel 8 Pro, Pixel 7 or Pixel 7 Pro share the same underlying fault.
That omission does not necessarily prove that those phones will never receive a correction. Older models may use different hardware, require separate firmware changes or have battery problems unrelated to the specific tracker issue.
For affected owners, however, the distinction provides little comfort. A phone that still loses half its battery while idle remains difficult to use regardless of whether its failure technically belongs to a different bug report. Several current reports have criticised Google for closing the issue without clearly addressing the older models that participated in the original discussion.
Pixel 8a and Pixel 9a Owners Must Wait Until September
The fix is not yet available for the Pixel 8a and Pixel 9a, according to Google’s statement.
Those models are expected to receive it through the September QPR, meaning quarterly platform release. A QPR is a larger Android update that can contain platform changes and broader fixes in addition to ordinary monthly security patches.
Owners of these models should therefore not assume that the July update was supposed to resolve their idle drain. Their results can only be assessed properly after the September software arrives.
The delay may reflect differences in hardware, modem firmware or the software branches used by the A-series phones. Google has not publicly explained why these models require additional time while the Pixel 9, Pixel 10 and Pixel 10a received the change in July.
Owners Can Check Whether Another App Is Responsible
A Pixel owner still experiencing poor battery life should first confirm that the latest system and application updates are installed.
Google recommends opening Settings, selecting System and then Software update. Application updates can be checked through the Play Store under Manage apps and devices. The phone should also be restarted after the update has finished installing.
Battery Diagnostics is available on the Pixel 6 and newer. It can be found under Settings, Battery, Battery diagnostics and Battery draining too quickly. The Battery usage section can also show whether one application has consumed an unusually large share of the charge.
A clearly identified third-party application can be restricted, updated or temporarily removed. Google recommends leaving ordinary apps on the Optimised background setting rather than aggressively disabling every service, since essential applications may stop delivering notifications or functioning correctly.
Battery Saver can reduce consumption temporarily, but it is not a real solution to a system process that prevents deep sleep. Similarly, disabling location completely may hide a GNSS-related problem while removing navigation, weather and safety functions that the phone is expected to provide.
A Factory Reset Should Be a Last Resort
Some affected users have attempted factory resets, but a reset is not guaranteed to eliminate a bug contained in the operating system or firmware.
It can help when corrupted settings, restored applications or accumulated software conflicts are responsible. It can also create a misleading temporary improvement because background accounts and services have not yet been fully restored.
Google lists a factory reset as an advanced troubleshooting step and warns that it erases applications and local data. A complete backup should therefore be created before considering it. Persistent drain after the correct update and several days of normal use should be reported to Pixel Support rather than immediately assuming the battery itself needs replacement.
Google’s Fix May Be Real but Incomplete
Google appears to have corrected a specific defect involving location-related system interrupts and failed low-power transitions. That is meaningful progress for users whose phones were affected by exactly that fault.
The continuing complaints suggest that the broader Pixel battery-drain story is not finished. Some covered phones may not have responded to the July update, while several older models were excluded from Google’s announcement despite similar reports.
The most accurate conclusion is therefore not that Google’s fix is false. It is that the company may have fixed one identified cause without resolving every case that users have grouped under the same battery-drain problem.
Owners of supported Pixel 9 and Pixel 10 models should install the July build, allow several days for post-update optimisation and compare overnight idle loss under similar conditions. When severe drain continues, battery diagnostics and a support report will provide more useful evidence than another round of random setting changes.
