Android 17 QPR3 Beta 4 Fixes Pixel Lag, Battery Drain Bugs

Google has started rolling out Android 17 QPR3 Beta 4 to eligible Pixel phones and tablets, pushing out build DP11.261030.003 on November 12, 2026. The update is the fourth beta in the QPR3 cycle and targets four specific bugs: memory leaks in system_server that cause severe UI lag and Pixel Launcher crashes, a confusing Conscrypt error when old TLS connections are rejected, a visually clipped on-screen keyboard, and background Bluetooth activity that was draining batteries faster than normal.

What's new in Android 17 QPR3 Beta 4

Beta 4 is a maintenance build rather than a feature release. According to Google's official QPR3 release notes, the update doesn't introduce app-facing API changes. Instead, it's aimed squarely at stability problems that testers flagged after Beta 3 went out on October 29. Google ships these quarterly platform release (QPR) betas to Pixel devices ahead of the broader Feature Drops, giving developers and testers a chance to catch issues before a build reaches general availability.

9to5Google, which reported on the rollout the same afternoon it went live, noted that Beta 4 arrived a little over two weeks after Beta 3 and that Google is continuing to push bug-fix updates to the full Pixel 6a-through-11 lineup rather than narrowing the pool of eligible devices as the cycle progresses.

The security patch level stays at 2026-10-05, the same level Beta 3 shipped with, and Google Play services moves up to version 26.41.31 — a jump from the 26.36.33 build that shipped with Beta 2 and Beta 3.

The QPR3 beta cycle so far

Beta 4 is the fourth build in a cycle that began October 2, 2026. Google has kept a roughly two-to-three-week cadence between releases, alternating between larger feature-and-fix updates and tighter, more targeted patches like this one.

Each beta has shipped with its own "top issues fixed" list on Google's release notes page. Beta 1 cleared 20 issues inherited from early QPR3 testing, Beta 2 closed 21 more, and Beta 3 fixed 26 — including a black inner display on unfolding and flickering Recents transitions. Beta 4's list is shorter at four issues, but each one was significant enough on its own to warrant a dedicated fix rather than waiting for a larger batch.

The four bugs this beta fixes

Google's release notes list four "top issues fixed" for Beta 4, each tied to a public Issue Tracker report. Unlike Beta 3's refresh — which closed out 26 separate issues ranging from flickering Recents animations to a black inner display on foldables — Beta 4's fix list is narrower but addresses some of the more disruptive bugs testers had been hitting.

The system_server leak is the most consequential of the four. It's tied to five separate Issue Tracker reports, suggesting Google was chasing the same root cause across multiple symptom reports — lag, launcher crashes, and spontaneous restarts can all trace back to the same process leaking memory over time. system_server is one of Android's core processes, handling window management, activity lifecycles, and most system services; when it leaks memory, the whole device slows down rather than just one app, which is why testers described everything from a sluggish Pixel Launcher to unprompted reboots.

The Conscrypt fix is more of a developer-facing cleanup than a user-facing one. Conscrypt is the security provider Android uses for TLS/SSL connections, and TLSv1 and TLSv1.1 have been considered insecure and deprecated across the industry for years. Apps that target API level 36 and still try to negotiate those older protocols were getting rejected, which is expected behavior — but the error message thrown back was an opaque IllegalArgumentException that didn't clearly explain why the connection failed. Beta 4 doesn't change the underlying rejection policy; it just makes the resulting error message easier for developers to diagnose.

The Bluetooth battery drain fix is also notable since it's the kind of bug that quietly erodes a beta tester's patience; a phone burning through charge in the background is often the first thing people notice, even before they can pin down why. And the clipped on-screen keyboard bug, while visually minor, directly affects something nearly every user interacts with dozens of times a day — Google flagging it as a top issue for a beta this late in the cycle suggests it was reported frequently enough to prioritize over less visible bugs.

Build number, security patch and Play services

Beta 4 carries the build number DP11.261030.003 across all eligible Pixel hardware — unlike Beta 3, which shipped two build variants (DP11.261016.003 for most devices and DP11.261016.004 for the Pixel 11 line), Beta 4 unifies everything under a single build string. The security patch level holds at 2026-10-05, carried over unchanged from Beta 2 and Beta 3, while Google Play services advances to 26.41.31.

Which Pixel devices are eligible

Android 17 QPR3 Beta 4 is available to the same device roster that's been eligible since QPR3 Beta 1, stretching from the Pixel 6a up through the newest Pixel 11 family, plus the Android Emulator for app testing.

That's 22 phone and tablet models in total, matching the lineup Google has supported since QPR3 testing began in October. Owners of a Pixel 11 can join this beta track even though QPR1 arrived late for that lineup — QPR3 testing has run on schedule across the current Pixel family regardless.

How to install Beta 4

Testers already enrolled in the Android Beta Program on an eligible Pixel should receive Beta 4 as an over-the-air update automatically; it can also be checked for manually under Settings > System > System update. Anyone not yet enrolled can sign up for the beta program on a supported device to start receiving QPR3 builds, including this one — enrollment is free and tied to a Google account, and opting out later rolls the device back to the latest stable release (with a data wipe, since Android downgrades aren't supported in place).

Developers who prefer a clean flash rather than an OTA can instead download factory or OTA system images directly from the Android developer site and flash them with platform tools. That route is generally recommended for anyone testing app compatibility rather than just using a phone day to day, since it guarantees a known-clean starting state rather than an incremental update layered on top of whatever build the device was already running.

Bugs should be reported through the Android Beta Feedback app, which is preinstalled on beta builds and accessible from the app drawer or Quick Settings — that's the same channel Google used to collect the reports that led to Beta 4's four fixes. Feedback submitted there can include a bug report attachment, screenshots, and reproduction steps, all of which feed into the same Issue Tracker reports linked throughout this article.

How Beta 4 compares to Beta 3

Beta 4 is a much smaller patch than its predecessor. Android 17 QPR3 Beta 3, released October 29, closed out 26 separate issues, including a black inner display on foldables when unfolding, flickering Recents transitions, and a broken Force Stop button in app settings. Beta 4's four fixes are more narrowly scoped, but they target problems with a more direct, everyday impact: system-wide lag, a UI element that's hard to type into, and battery life — the kind of bugs that show up in day-to-day use rather than edge-case scenarios.

The security patch level hasn't moved between Beta 3 and Beta 4, both sitting at 2026-10-05, but Google Play services has advanced from 26.36.33 to 26.41.31, a sign Google is continuing to update the Play services layer independently of the OS patch cadence.

When QPR3 goes stable

Google has not published a stable release date for QPR3 in its official release notes. Quarterly Platform Releases typically spend several months in beta before reaching general availability as part of a Pixel Feature Drop, following the pattern set by Android 17's original rollout and its QPR1 and QPR2 predecessors. Based on that cadence, a stable QPR3 release in early 2027 would be consistent with how Google has shipped prior quarterly updates, though Google itself has not confirmed a date.

Platform stability — the point at which Google freezes app-facing APIs for the release — is usually reached a few betas before the final stable build ships, giving developers a window to finish compatibility testing without worrying about further API changes landing underneath them. Google's QPR3 release notes don't yet flag Beta 4 as having reached that milestone, which suggests at least one more beta is likely before the cycle wraps up.

What happens next

Expect at least one more QPR3 beta before Google locks in platform stability and moves toward a stable release. Testers who hit new bugs on Beta 4 should file them through the Android Beta Feedback app so they can be triaged for the next build. Anyone relying on a Pixel as a daily driver, rather than a dedicated test device, may want to wait for platform stability before installing — beta builds, even late-cycle ones like Beta 4, can still carry regressions that haven't surfaced yet.

For now, Beta 4 is live for the full eligible Pixel lineup, and it's a safe bet Google will keep iterating on QPR3 with further bug-fix betas before the quarter is out.

Written byNadia Osei

Nadia Osei covers mobile and consumer gadgets for Pandromeda: smartphones, tablets, smartwatches, earbuds and smart-home devices. She tracks launches, software updates and pricing across Apple, Google, Samsung and the rest, and builds comparisons from the manufacturers' published specifications.

More from Nadia OseiAll Mobile & Gadgets coverage