Pixel Battery Draining After March Update: What Owners Want

Two weeks after unboxing a Pixel 10 Pro, one reviewer opened Settings and found only 96GB usable out of a base 128GB. System files, background processes, and preinstalled apps that can't be disabled had already claimed roughly a quarter of the phone's advertised capacity, according to an Android Police account from nine months ago.

This isn't an argument that Pixel owners reject AI outright. It's about something narrower: who gets to decide how a phone's finite resources, storage chief among them, get spent. That question runs through a detailed storage audit of one device, through polling where Pixel buyers rank battery life and stability above smarter on-device AI, and through a complaint about Pixel battery draining after March update that Google has yet to confirm a fix for, based on the most recent reporting available.

Treat these as three separate problems rather than one bundled grievance. The storage case points to a control-and-transparency gap in how non-optional software uses a phone's capacity. The chip polling points to a mismatch between what Google is building and what owners say they want. The battery complaint points to a reliability regression Google has acknowledged internally but not yet resolved publicly. They reinforce each other without measuring the same thing, and conflating them is where a lot of the online commentary goes wrong.

The storage case: what one Pixel 10 Pro shows about non-optional software

The figures are specific enough to list precisely rather than fold into a single number. On the reviewer's device, one component in the storage breakdown occupies 6.73GB, the Device Intelligence app uses 1.06GB, Pixel Screenshots takes 1.14GB, and Pixel Studio adds 193MB, per Android Police.

That 6.73GB line deserves a caveat: the reviewer doesn't name which package it belongs to in the piece, so it's worth treating separately rather than assuming it belongs entirely to AI features. AICore's own footprint, by contrast, is described only in relative terms, roughly comparable to Tidal, the reviewer's largest self-installed app at just over 9GB, according to the same Android Police report. That's a comparison offered for scale, not a number Google has published itself.

It helps to know what these categories actually measure, because Android's own settings screen blurs distinctions that matter here. App storage covers the installed package plus any files it saves directly, including a downloaded AI model. App cache is temporary data an app can rebuild on demand, the kind Settings lets you clear with no real consequence. System storage covers the operating system and background utilities that never appear as user-facing apps at all. AICore sits in the first category. It doesn't use the cache, per Android Police, which is why clearing an app's cache, the standard fix for a bloated phone, does nothing here.

Clearing AICore's app storage may free space temporarily, but the footprint returns, faster with continued use of AI-powered apps, according to Android Police. Owners can see a total in Settings. They can't necessarily see what's driving it, since the reporting doesn't establish that Pixel's storage menu cleanly separates AI-specific use from ordinary system overhead.

Ordinary overhead is doing real work here too. The gap between 128GB advertised and 96GB usable includes the operating system, temporary files, background utilities like Google Wi-Fi Provisioner, and preinstalled apps broadly, not just AI components, per the same Android Police reporting. The named AI-related apps account for a real but partial slice of that missing quarter.

It's also worth resisting the leap from storage to performance. The reporting documents storage use, not RAM consumption or a measured slowdown. AI features reserve capacity that's been directly observed, but a proven performance penalty is a separate claim the available reporting doesn't make.

The clearest number in the whole account is the price tag attached to avoiding the problem entirely: moving from 128GB to 256GB on a Pixel 10 costs $100 more, per Android Police. That puts a dollar figure on a squeeze partly created by software the owner never chose to install and can't remove.

All of this comes from a single device and a single reviewer, not a controlled study across a Pixel generation. The defensible conclusion is narrow: on this device, Google's current software imposed meaningful, non-removable, hard-to-audit storage costs. That's not evidence of a fleet-wide standard, and it doesn't by itself prove Google's broader AI strategy is failing.

What the chip poll shows: priorities, not a mandate for control

The storage account is one device's experience. Separate polling suggests it isn't an isolated preference. Across three surveys Android Authority ran about the Pixel 10's chip, battery life topped the wish list, performance came second, and reduced heating placed third, while more powerful on-device AI finished last in all three, under 8% of the overall vote and under 6% specifically on the site's own and YouTube polls, according to Android Authority last year.

That result answers a narrower question than it's sometimes given credit for. It doesn't ask whether owners want more control over how their phone allocates storage or processing headroom; it asks what feature they'd most like the next chip to deliver. What it shows is a clear ranking among self-selected readers, not a referendum on AI as a category. Some commenters framed the results as anti-AI outright, but the numbers show on-device AI losing to three specific, concrete priorities, not a rejection of AI features generally.

Read alongside the storage findings, the two pieces of evidence tell a consistent but distinct story. One shows a product-priorities mismatch: readers want the fundamentals nailed down before capability expands. The other shows a control-and-transparency gap: even owners who might welcome AI features have no clean way to opt out of the storage cost or see what's driving it. Neither dataset proves the other's point directly, but together they describe a company that keeps adding capability faster than it's addressing the basics its own audience keeps asking for.

Pixel March update battery drain: what the poll and Issue Tracker show

That same tension shows up more sharply in a specific complaint. Android Authority ran a poll after noticing growing reports of the Google Pixel battery drain issue following a March software update, and the result was lopsided: 75.9% of thousands of respondents said their battery was draining faster since the update, against 15.2% who noticed no change, a margin Android Authority four months ago called hard to dismiss given more than 2,000 confirmation votes.

Google appeared to acknowledge the issue in its public Issue Tracker, where it's listed as assigned with P1 priority, attributed to affected devices failing to enter Deep Doze and staying more active than intended while idle, according to Android Authority. That's a genuine signal Google took the reports seriously, but it's a status update on a tracker entry, not a public statement with a root cause or a release date attached. Readers who tried Battery Saver, or who installed the April update hoping it would help, reported little to no improvement in the same coverage. There was no confirmed Pixel Deep Doze battery drain fix or timeline in Android Authority's reporting as of that April update.

Worth flagging the limits of the poll itself. It's a self-selected reader survey, not a representative sample of every Pixel owner, and people who've noticed a problem are more likely to click a poll about it than people who haven't. Android Authority itself noted that many respondents hadn't checked their battery stats closely before voting. That doesn't undercut the result so much as bound it: what the data shows is a large volume of reported experience among engaged readers, not device-wide telemetry confirming how many Pixels are actually affected.

Even bounded that way, the response volume is what appears to have moved Google. Whether the subject is chip priorities or an update regression, Android Authority's polled readers keep prioritizing stability and predictability over new capability, and Google's own Issue Tracker activity suggests it's registering that signal, even without a public fix in hand yet.

Three separate fixes for three separate problems

It's tempting to treat all of this as one complaint Google could resolve with a single announcement. It isn't. There are at least three distinct problems here, and each needs its own fix.

Software control is the first. Owners should be able to individually enable or disable AI features rather than have them bundled as mandatory, and where technically feasible, Google should offer a choice between processing locally on the device or in the cloud, a solution Android Police proposed nine months ago. This solves the removability problem. It does nothing for the next one.

Transparency is that second problem, and it's a different ask from control. A settings view that clearly separates ordinary system overhead from AI-specific storage would close the audit gap that currently leaves owners staring at a single number with no clear sense of what's driving it, per Android Police.

Hardware pricing is the third, and the costliest. Raising the base storage tier to 256GB would ease the squeeze, but it's a separate lever from control or transparency. It just buys headroom rather than fixing the underlying issue. Android Police's own reviewer hesitated to recommend it outright, expecting Google would simply pass the added manufacturing cost on to buyers.

There's a fourth issue sitting underneath the other three, though it's better described as a recommendation than a proven fact about Google's internal roadmap. The polling gives Google a clear sequencing argument: address battery, performance, and heat before making new on-device AI capability the headline of the next launch. Whether Google is actually sequencing things that way isn't something either dataset can confirm, but the polling makes a strong case that it should.

None of this means every buyer should treat the storage findings as a dealbreaker. The squeeze documented here matters most to heavy photographers, video users, frequent app installers, and anyone planning to keep a device through several years of updates. The 96GB figure is one reviewer's post-setup snapshot, not a standardized capacity benchmark, so it works better as a risk indicator than a universal spec.

For current owners, checking Settings > Storage and periodically clearing AICore's storage, not its cache, are the only levers available right now. Neither offers a durable fix; the footprint returns, especially with continued AI app use, and there's no evidence of a way to remove the underlying components entirely.

The takeaway

Google hasn't published which AI components are mandatory or why, hasn't offered owners a storage-accounting breakdown that separates cause from total, and, as of the most recent reporting, hadn't confirmed a fix timeline for the March battery regression. Those gaps, not any single spec sheet, are what's actually driving the frustration behind both stories.

The narrower conclusion holds up on its own: Google's current AI features can cost owners storage they can't remove or fully audit, and that problem sits alongside, rather than inside, a broader pattern of owners wanting reliability nailed down before capability expands. Whether the next Pixel generation makes AI features optional, gives buyers a genuine storage breakdown, or simply raises the base tier and charges more for the privilege will say more about Google's actual priorities than any chip benchmark or camera spec on the box.