Android 17 QPR3 Beta 3 Rolls Out to Pixel Phones With 26 Fixes

Google has rolled out Android 17 QPR3 Beta 3 to eligible Pixel phones, the third test build in the current Quarterly Platform Release cycle. The update arrived on October 29, 2026 as builds DP11.261016.003 and DP11.261016.004, carries the October 5, 2026 security patch level, and bundles Google Play services 26.36.33. According to Google's own release notes, Beta 3 resolves 26 issues reported against earlier QPR3 builds, with no app-impacting API changes for developers to worry about.

What's actually new in Beta 3

Beta 3 is squarely a stability pass rather than a features drop. Google's official QPR3 release notes list the build as fixing 26 separate issues that had been reported in earlier Android 17 QPR3 betas or carried over from Android 16. There's no new user-facing feature spotlighted in the changelog, which fits the pattern of this phone's QPR3 Beta 2 release a week earlier: Google tends to front-load bigger changes into Beta 1 and spend the following rounds squashing the bugs that beta testers flag.

Several of the fixes target things that are easy to notice in daily use rather than obscure edge cases. Google's notes call out:

• Images rendering with incorrect transparency when using the Multiply blend mode
• The Recents overview flickering during a home-gesture quick-switch
• The inner display staying black when unfolding a foldable Pixel
• Poor video quality when using the phone as a webcam
• Toast notifications intermittently failing to appear under high memory pressure
• Home-screen wallpaper briefly showing on the lock screen when the device wakes from an open app
• UI buttons rendering as blank white squares in dark mode
• The Mobile Data Quick Settings icon rendering at the wrong size with visual artifacts
• WPA-Enterprise Wi-Fi connections failing to authenticate with PEAP

The rest of the list skews toward smaller polish items: grayed-out grouped notification icons, a navigation-bar animation glitch when swiping up to Recents, bubbles getting stuck in a miniaturized state, and a SettingsDumpService memory leak after opening SIM settings. None of it is flashy, but it's the kind of cleanup that matters more the closer a QPR gets to its stable release.

The 26 fixes, grouped

Scanning through Google's full changelog, the Beta 3 fixes cluster into a few recognizable buckets rather than being a random grab bag:

• Display and rendering: the Multiply blend-mode transparency bug, the font-size slider rendering glitch, blank white UI buttons in dark mode, and the inner-display black screen on unfolding foldables.
• System UI and navigation: the Recents overview flicker during quick-switching, the navigation-bar animation glitch when swiping to Recents, inconsistent status-bar icon spacing, and bubbles getting stuck in a miniaturized state.
• Connectivity: WPA-Enterprise Wi-Fi connections failing PEAP authentication, and the Mobile Data Quick Settings tile rendering at the wrong size with visual artifacts.
• Stability and crashes: intermittent crashes on the lock screen or shortly after startup, the Twitter app crashing when viewing thread mentions, and app crashes when calling BluetoothLeScanner.stopScan() with a null callback.
• Notifications and settings: grouped notification icons and titles appearing grayed out, a persistent UI message that couldn't be dismissed, and a SettingsDumpService memory leak after opening SIM settings.
• Media and camera: poor video quality when using the phone as a webcam, and toast notifications intermittently failing to display under memory pressure.

Several of these — the grouped-notification issue and the Mobile Data tile sizing bug in particular — carry multiple linked issue-tracker numbers, suggesting they were widely reported by beta testers rather than isolated reports, which is likely why Google prioritized them for Beta 3 rather than holding them for a later build.

Security patch level holds steady

Beta 3 ships with the same October 5, 2026 security patch level as Beta 2, rather than bumping it forward. That's not unusual for a mid-cycle beta build — Google typically aligns the security patch level with the most recent monthly release and focuses QPR betas on platform stability rather than shipping a new patch batch with every build.

Which Pixel phones can install it

Per Google's Get Android 17 QPR3 page, OTA updates and downloads for this cycle are available on 23 Pixel devices, spanning five generations:

Older Pixel 6 and Pixel 6 Pro units, which have aged out of platform updates, are not on the list. Anyone weighing a newer Pixel against what's currently available should see our Pixel 11 vs. Pixel 11 Pro comparison for how the current flagship lineup differs on paper.

How to enroll — and how to get out

Enrollment runs through Google's Android Beta program rather than a side-loaded file. Google's own instructions say to visit g.co/androidbeta, sign in with the Google account tied to an eligible Pixel, and opt the device in; the update then arrives as a normal OTA. Google notes that "in most cases you don't need to do a full reset of your data to move to the Android 17 QPR 3 Beta," though it still recommends backing up first.

Devices can also be moved onto the beta by flashing a system image directly. Google warns that once a device has been flashed with a beta build, it's automatically enrolled in OTA updates for every subsequent beta through the final stable release.

Getting out is more limited than getting in. Per Google's documentation, a beta device can only drop out of the program without a data wipe at the point a stable update is applied — and only until the next beta build is installed, at which point that opt-out window closes again. Trying to leave the beta program at any other time triggers a data-wiping downgrade, so anyone who enrolled in QPR2 or QPR3 beta for testing purposes and wants off should do it as soon as a stable build becomes available to them, not later.

When does this reach everyone else?

Google hasn't published a firm date for when Android 17 QPR3 goes stable. Its official documentation describes QPRs as part of a recurring cycle — "there are four stable releases to the public" across a given Android version's life, counting the initial platform release plus three Quarterly Platform Releases — but neither the QPR3 overview page nor the release notes commit to a calendar date for this particular cycle's stable rollout. Beta programs for past Android releases have generally run for a handful of monthly builds before the corresponding QPR goes stable, and Beta 3 landing in late October suggests Google is still working through its usual pre-stable testing rhythm rather than closing in on a final build. Anyone who wants a hard date will need to wait for Google to confirm one rather than go by outside guesses. Android's broader version history, including how past Quarterly Platform Releases have tracked to stable builds, is cataloged on Wikipedia's Android version history page for anyone comparing this cycle to previous ones.

Why a bug-fix beta is still worth watching

It's easy to dismiss a beta that's "just" 26 fixes, but QPR betas are where Google works out the issues that will otherwise ship to everyone on the stable channel. A number of the Beta 3 fixes — the inner-display black screen on folding Pixels, the webcam quality issue, the Wi-Fi PEAP authentication failure — are the sort of thing that would generate real support complaints if they reached general availability untouched. For anyone running the beta on a primary phone, this build is a meaningfully safer place to land than Beta 1 or Beta 2 were.

It's also a reminder of how platform-level polish items tend to show up well before marquee features. Readers tracking related platform UI changes, like how always-on elements behave across ecosystems, may find our rundown of always-on display behavior on iPhone, Android, and Apple Watch useful context, since lock-screen and display bugs are a recurring theme across these quarterly betas.

Should you install Beta 3?

For developers testing app compatibility, yes — Google's notes confirm there are no app-impacting API changes in this cycle, so the risk of Beta 3 breaking an app that worked on Beta 2 is low. For everyday users on a primary phone, the calculus is less clear-cut: beta software, even a stability-focused build like this one, can still introduce new regressions, and the opt-out mechanics mean leaving the program isn't as simple as toggling a switch. Users who already run earlier QPR3 betas should take the OTA, since it's explicitly fixing bugs reported against the builds they're currently on. Those still on stable Android 17 or on the QPR2 track should weigh whether they want to be in a pre-release program at all, independent of Samsung or other manufacturers' own update cadence — for comparison, see how that plays out on the other side of Android in our One UI 9 rollout tracker.

What to watch next

With Beta 3 focused entirely on cleanup, the next milestones to watch are whether Google ships a Beta 4 with another round of fixes, or whether the program moves toward a release candidate ahead of stable. Pandromeda will update this story, or publish a follow-up, once Google's release notes or the Android Beta program page show a confirmed stable date or a new build for Android 17 QPR3.

Frequently asked questions

What is Android 17 QPR3 Beta 3?
It's the third beta build in the Android 17 QPR3 (Quarterly Platform Release 3) test cycle for Pixel phones, released October 29, 2026 as builds DP11.261016.003 and DP11.261016.004. Google's release notes describe it as fixing 26 issues carried over from earlier betas.

Which Pixel phones can install Beta 3?
Google lists 23 eligible devices: Pixel 6a, the Pixel 7 series, Pixel 8 series plus Pixel Tablet and Pixel Fold, the Pixel 9 series, the Pixel 10 series, and the Pixel 11 series. Pixel 6 and 6 Pro are not included.

How do I install Android 17 QPR3 Beta 3?
Enroll an eligible Pixel at g.co/androidbeta and the update arrives as a standard OTA. Devices already enrolled in the QPR3 beta receive Beta 3 automatically.

Can I go back to stable Android without losing my data?
Only at a specific point: Google says you can opt out of future beta updates without a data wipe once you apply a stable release update, and only until you install the next beta. Opting out at any other time triggers a data-wiping downgrade.

When will Android 17 QPR3 become stable?
Google hasn't published a firm date. Its documentation only confirms that QPRs ship on a recurring quarterly cycle, without committing to a calendar date for this cycle's stable release.

Does Beta 3 add new features?
No. Based on Google's release notes, Beta 3 is a bug-fix build with no new user-facing features and no app-impacting API changes for developers.

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