Google Pixel Emergency Update (Dec 2025): Second Patch Rolls Out to Fix Battery Drain and Touch Bugs

A surprise second December 2025 Pixel update is rolling out to Pixel 8, Pixel 9, and Pixel 10 phones. Here’s what it fixes, who gets it, and why updating matters on Dec. 19, 2025.

Google is pushing a second, unexpected December 2025 update to select Pixel phones—just weeks after the main December release (Android 16 QPR2). The new patch is small (roughly ~25–27MB), but it targets problems users have been complaining about since the first rollout: faster-than-normal battery drain, intermittent touch failures (especially on Pixel 10), and a bug that can block access to locally cached offline content after upgrading to Android 16. ^[1]

Today’s reporting (Dec. 19) also makes one thing clear: this isn’t a single, uniform build everywhere. While many U.S. users—especially on Verizon—are seeing BP4A.251205.006.E1, other regions are showing different build suffixes (for example, a heise report notes BP4A.251205.006.A4 on a Pixel 10 Pro). ^[2]

Below is what’s known as of December 19, 2025, based on carrier notes, device reports, and Android’s official security bulletins.

What’s new in the second December 2025 Pixel update

Verizon’s release notes (one of the clearest public changelogs available right now) describe the update as System Update released December 17, 2025, still on the December 2025 Android security patch level, and tied to Software Version BP4A.251205.006.E1. ^[3]

Fixes included (carrier notes)

The update addresses three practical issues:

Battery drain: faster-than-normal battery depletion
Touch unresponsive: intermittent touch failures observed specifically on Pixel 10
Cached content access: inability to open locally stored offline content (like offline media/maps) after upgrading from Android 14 (or earlier) directly to Android 16 ^[4]

That lines up with what Pixel owners have been seeing in the wild: a tiny OTA arriving after the larger December update, with the goal of stabilizing day-to-day usability rather than adding features. ^[5]

Which Pixel phones are getting the update

Unlike the main December update—which was broadly available across older supported Pixels—this second December patch appears more limited.

As of today, confirmed eligible models include the Pixel 8, Pixel 9, and Pixel 10 families, including “a” models and foldables. Android Authority lists the currently confirmed devices as: Pixel 8 / 8 Pro / 8a; Pixel 9 / 9 Pro / 9 Pro XL / 9 Pro Fold / 9a; Pixel 10 / 10 Pro / 10 Pro XL / 10 Pro Fold. ^[6]

If you’re on a Pixel 6 or Pixel 7 series device, you may not see this second patch at all—and that alone doesn’t necessarily mean your phone is losing update support. Google has done limited “extra” patches like this before where only certain models get the hotfix. ^[7]

Build numbers and rollout reality: why your update might look different

One reason this story has felt confusing is that Google hasn’t published a single, centralized “here are all the builds” post for this second patch yet—and factory/OTA images weren’t posted at the time outlets first spotted the rollout. ^[8]

What we do know on Dec. 19:

U.S. carrier documentation (Verizon) ties the update to BP4A.251205.006.E1 and a 12/17/2025 release date. ^[9]
Europe: a heise report says its team saw BP4A.251205.006.A4 on a Pixel 10 Pro, while still referencing Verizon’s E1 notes for the fix list. ^[10]
Japan: Jetstream reports a Japan rollout beginning Friday, Dec. 19, with builds including BP4A.251205.006.C2 for some models and BP4A.251205.006.E1 for others—plus extra Japan-specific changes (more on that below). ^[11]

The takeaway: don’t panic if your build suffix isn’t “E1.” The important part is that you’re receiving the December hotfix for your region/carrier.

Why some outlets are calling this an “emergency update”

Two things are happening in parallel—and they’ve blended together in headlines.

1) Pixel owners are getting an out-of-cycle stability hotfix

A second update in the same month is unusual, and when it fixes high-friction issues like battery drain and intermittent touch failures, it feels urgent—especially during the holidays when people travel and rely more on offline maps, boarding passes, and downloaded media. ^[12]

2) Android’s December security context is genuinely serious

Android’s official December 2025 Security Bulletin includes a note that there are indications two Framework vulnerabilities “may be under limited, targeted exploitation”—CVE-2025-48633 and CVE-2025-48572. ^[13]

Separately, CyberScoop reported that Google’s monthly Android update addressed 107 vulnerabilities in total and that the bulletin uses two patch levels (2025-12-01 and 2025-12-05) to help partners roll fixes out faster. ^[14]

And for organizations tracking real-world exploitation risk, the NVD entry for CVE-2025-48633 shows it’s in CISA’s Known Exploited Vulnerabilities process with a 12/23/2025 due date for required action in the federal context (apply mitigations per vendor instructions or discontinue use if mitigations aren’t available). ^[15]

Bottom line: even though the second December Pixel patch reads like a targeted bug-fix, keeping up with Pixel updates matters because the broader December patch window includes security fixes under active concern.

How to get the update right now (and confirm you have it)

Check for the update

Open Settings
Tap System
Tap Software updates
Tap System update ^[16]

Confirm you installed the hotfix

After installing, verify:

Android security patch level: should show December 2025 (per carrier notes) ^[17]
Build number: you may see BP4A.251205.006.E1 (common on Verizon), or another regional variant such as BP4A.251205.006.A4 (reported in Europe) or BP4A.251205.006.C2 (reported for some Japan models). ^[18]

Not seeing the update yet? Here’s why

If your Pixel is eligible but you don’t see the patch today, it’s not unusual.

These updates often roll out in phases, and carrier approvals can stretch timelines. ^[19]
Early reporting indicated the hotfix wasn’t widely available at first and seemed clustered around certain carriers/regions. ^[20]
Google also hadn’t posted downloadable factory/OTA images when the rollout was first noticed, which limits “manual” paths for advanced users. ^[21]

What you can safely do:

Keep your phone on Wi‑Fi, ensure it’s charged, and check again later today.
Restart once and re-check (a surprisingly effective trigger for staged OTAs).

A Japan-only twist on Dec. 19: choice screens tied to a new smartphone competition law

One of the most distinct pieces of news today (Dec. 19) is that Japan’s rollout may not be just bug fixes.

Jetstream reports Google Japan began rolling out an update to multiple Pixel 8/9/10 models to comply with Japan’s “Smartphone Software Competition Promotion Act,” including a choice screen related to the “free choice of browsers and search engines.” ^[22]

This is notable because it suggests the “second December update” can carry different extras by market, even if the core stability fixes (battery/touch/offline cache access) match what Verizon described. ^[23]

(For readers outside Japan: you likely won’t see these specific choice-screen changes.)

What Pixel owners should do today

If you own a Pixel 8/9/10-series phone:

Install the hotfix when it appears—especially if you noticed battery drain after Android 16 QPR2 or any intermittent touch issues.
Don’t ignore December updates: Android’s December 2025 bulletin flags vulnerabilities with signs of targeted exploitation, and Pixel devices typically get patches earlier than much of the Android ecosystem. ^[24]

If you’re on another Android brand:

Watch for your manufacturer’s December/January security rollout, since OEM schedules vary even when Google has published fixes. ^[25]

Quick FAQ (for Discover)

Is this the same as the big Android 16 QPR2 update?
No. The main December release brought Android 16 QPR2 and a larger set of changes; this is a smaller follow-up hotfix aimed at specific post-update problems. ^[26]

Does the hotfix include a new security patch level?
On Verizon’s documentation, it remains December 2025—so think of it as stability fixes layered on top of the month’s security baseline. ^[27]

Why does my friend have BP4A…E1 and I have BP4A…A4/C2?
Build suffixes can vary by region and carrier, even when the underlying fixes are similar. ^[28]

What if my Pixel 7 (or older) doesn’t get this hotfix?
This specific out-of-cycle patch appears focused on Pixel 8/9/10 devices; that doesn’t automatically mean older supported Pixels won’t receive future monthly patches. ^[29]

Android 16 QPR3 Beta 1 Just Dropped – This Changes More Than Expected!