Google Pixel users are dealing with frustrating battery problems again, and this time the September patch seems to be the main culprit. The Android 16 QPR1 update has left many owners watching their battery percentages drop faster than usual, turning what should be all-day devices into phones that need midday charging sessions.

The complaints started flooding in shortly after the September update rolled out. Over on Reddit’s r/GooglePixel megathread, users with different models are sharing similar stories.

One Pixel 9 Pro owner mentioned their phone sits idle on a desk most of the day yet loses 50% or more of its charge.

pixel-9-pro-battery-drain-september-update-android-16-qpr-1

Another Pixel 7 user reported regularly hitting 50% battery by midday despite barely touching their device during work hours.

pixel-7-battery-drain-september-update-android-16-qpr-1

The Pixel 8 Pro crowd isn’t having any better luck either, with reports of roughly 30% shorter battery life compared to before the update.

pixel-8-pro-battery-drain-september-update-android-16-qpr-1

Google’s support forums tell the same story. Multiple Pixel 9, Pixel 8, and Pixel 8 Pro users have shared their frustrations about the issue, with some noting their batteries drain 20-25% overnight when the phone should be idle. System apps appear to be running the CPU for extended periods even when the device isn’t being used, which obviously tanks battery life pretty quickly.

android-16-battery-drain-report-pixel-9

This isn’t Google’s first rodeo with battery problems in Android 16. During the initial beta testing phase, users reported major battery drain issues as well. Android Authority covered those early complaints back when Android 16 was still in beta. Then, even when Android 16 rolled out for everyone on the stable channel, there was a surge in reports about battery drain. Things quietened down for a couple of months, but with reports once again resurfacing, it’s clear that something is amiss.

Some users have tried factory resetting their phones, though results seem mixed. One person mentioned a factory reset helped them out, while another said it made no difference at all. The usual troubleshooting steps like checking for rogue apps, turning off Adaptive Audio, or disabling Wi-Fi and Bluetooth scanning have helped a few people squeeze out better battery life, but many are still struggling.

For what it’s worth, I haven’t noticed any drastic decrease in battery life on my Pixel 7a after updating. It’s holding up reasonably well through a typical day. But enough people across enough different Pixel models are reporting issues, which suggests it’s not just a few isolated cases.

Google hasn’t yet acknowledged the problem, so it’s unclear if we’ll see a fix with the October update that will be going live in a week or so.

That said, feel free to share your battery life experience following the Android 16 update and/or the latest Android 16 QPR1 update, which many seem to blame for poor battery performance.

Has the Android 16 QPR1 update impacted battery life on your Pixel?

View Results

Loading ... Loading ...
We stand out from the tech-media crowd because we break news stories; we mainly bring you stuff that you won’t find anywhere in the mainstream tech media. Our stories have been picked up by some of the world’s most popular websites and media outlets—more info is available here.

Dwayne Cubbins
2715 Posts

I cover fast-moving stories across apps, online platforms, and everyday tech — phones, wearables, consoles, and whatever else people are fighting with this week. Bugs, rollouts, scams, policy enforcement, and the occasional internet-culture rabbit hole are all fair game. My goal is simple — make confusing tech news readable. When I'm not working, I'm working out or chilling with my dog. Got a tip? You can find me on X @dcubbins.

Next article View Article

YouTube background play not working on Brave Browser app? Try these potential workarounds

Update 31/01/26 - 09:22 am (IST): Brave's support team has confirmed that the company is aware and investigating the issue. They've also provided the same workaround...
Jan 12, 2026 3 Min Read