Android 17 QPR3 Beta 2: Release Date, Fixes, and Pixel Devices

Google released Android 17 QPR3 Beta 2 on October 20, 2026, the second test build in the run-up to the next Quarterly Platform Release. The build (DP11.261002.005) carries the October 5, 2026 security patch level and Google Play services 26.36.33, and it closes out roughly 21 bugs reported against Beta 1 — including random reboots, Wi-Fi Aware connection failures, Bluetooth pairing timeouts, and a black-screen bug after phone calls. There are no new user-facing features or API changes in this build; it's a stability pass ahead of the eventual stable QPR3 Feature Drop.

What's new in Android 17 QPR3 Beta 2

Beta 2 is explicitly a bug-fix release. Google's own release notes for the build don't list a single new feature, UI change, or developer-facing API change — a pattern that's typical for a second beta in a QPR cycle, when the focus shifts from adding functionality to stabilizing what shipped in Beta 1 and the Android 17 base release that launched back in June. If you're hoping for new Pixel software tricks, this isn't that update; if you installed Beta 1 and have been annoyed by freezes, dropped calls, or flaky Bluetooth, this is the build that's supposed to fix it.

That doesn't mean the update is trivial. The fix list touches core reliability issues that affect daily use far more than a cosmetic feature would, including several separate reports of devices crashing and rebooting during normal use, and a battery-drain bug tied to motion sensors.

Android 17 QPR3 Beta 2 release date and build details

Beta 2 shipped on October 20, 2026, 18 days after Beta 1 arrived on October 2. Google's official QPR3 Beta release notes list the following build details:

The jump from security patch level 2026-08-05 to 2026-10-05, and the Play services bump to 26.36.33, both suggest Beta 2 is built from a more current source tree than Beta 1 rather than being a narrow hotfix. For context on the baseline this beta builds on, see our earlier coverage of the Android 17 release date and feature rundown and the October 2026 Pixel stable update.

Everything fixed in Android 17 QPR3 Beta 2

Google groups the roughly 21 fixes in Beta 2 into a few buckets. The system-stability fixes are the headline: eight separate tracked issues covering intermittent crashes and reboots during normal use, plus a fix for devices unexpectedly shutting down during WhatsApp video calls. Two more notable stability fixes:

• Black screen after calls — the display could turn black and become unresponsive after ending a phone call.
• Battery drain from motion sensors — motion sensors could stay active (and drain battery) after being used for Face Unlock or the camera, even once you stopped using either.

Connectivity and telephony got a substantial pass, too:

• Wi-Fi Aware failing to establish a new data path after releasing an accept-any responder request
• Bluetooth pairing failing due to a connection timeout
• Cellular data, MMS, and hotspot failures on Dish Network
• VoLTE, VoNR, and Wi-Fi Calling unavailable on carrier IT&E
• Wi-Fi Calling unavailable on carrier OXIO
• The Internet Quick Settings tile showing persistent/incorrect text when mobile data is active without Wi-Fi

On the UI side, Beta 2 fixes a bug where screen recording freezes after rotating the screen, a misaligned Bluetooth subtitle in Quick Settings, a misplaced pin icon in the share sheet, system-wide text and icons rendering abnormally small regardless of display size settings, and the app drawer closing unexpectedly when switching keyboard languages. A handful of app-specific reports were also resolved, including the Terminal app failing to launch its Linux VM after installation, a paired watch continuing to ring after a call was answered on the phone, and the Airbnb app failing to connect when sending messages.

What Android 17 QPR3 Beta 1 fixed, for comparison

Beta 1, released October 2, 2026, addressed a different set of roughly 20 issues — many of them more disruptive than Beta 2's list. The headliners were devices freezing when unlocking with a fingerprint, the device crashing when "require eyes to be open" was selected in Face Unlock settings, and the NFC service crashing with a DeadObjectException after the initial scan on devices coming from Android 16. Beta 1 also fixed a crash loop in the phone app (and loss of cellular service) triggered when a modem reported unexpected SIM slot indices, a MediaPlayer crash on non-ASCII audio attribute tags, and excessive idle battery drain when Flip to Shhh was enabled.

Taken together, Beta 1 and Beta 2 read as a standard two-beta stabilization cycle: Beta 1 cleared out the more severe crash and freeze reports that surfaced after the initial QPR3 code drop, and Beta 2 is mopping up a second wave of issues — including some, like the Wi-Fi Aware and carrier-calling bugs, that are more niche but still worth fixing before a wider rollout.

Which devices get Android 17 QPR3 Beta 2

Google's official QPR3 beta enrollment page lists the following supported Pixel devices for the Android 17 QPR3 Beta program:

• Pixel 6a
• Pixel 7, Pixel 7 Pro, Pixel 7a
• Pixel Tablet, Pixel Fold
• Pixel 8, Pixel 8 Pro, Pixel 8a
• Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a
• Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, Pixel 10a
• Pixel 11, Pixel 11 Pro, Pixel 11 Pro XL, Pixel 11 Pro Fold

Any device already enrolled in the Android Beta for Pixel program and running Beta 1 will receive Beta 2 as a straightforward over-the-air update. Google's release notes also note the build supports the Android Emulator (x86 64-bit and ARM v8-A) and Generic System Images on Treble-compliant devices, which is mainly relevant to developers testing app compatibility rather than everyday users.

One detail worth flagging: the oldest device on the QPR3 beta list is the Pixel 6a, not the original Pixel 6 or Pixel 6 Pro. Those two phones reached the end of their guaranteed update window around the October 2026 security patch, so their absence from the QPR3 beta roster lines up with that timeline rather than being an oversight.

How to install Android 17 QPR3 Beta 2

There are two practical ways to get the update, per Google's official instructions:

1. Enroll in the Android Beta for Pixel program (OTA). Sign up at g.co/androidbeta. Google says enrollment is fast and usually doesn't require a full data reset, though it recommends backing up your device first. Once enrolled, your device keeps receiving OTA beta updates — including future QPRs — for the rest of the release cycle unless you opt out. You can only opt out without a data wipe after a stable release has landed and before the next beta build is applied.
2. Flash a system image manually. Google recommends the Android Flash Tool for a guided install, or downloading the QPR3 system image directly from the Pixel downloads page for manual flashing (useful for automated or regression testing setups). Flashing a beta build this way automatically enrolls the device in OTA updates for subsequent beta builds through the final stable release.

If your device is currently on Beta 1, you don't need to do anything beyond checking for a system update in Settings; the OTA to Beta 2 should arrive automatically through the beta channel.

What Beta 2 means for the stable QPR3 release timing

Google's developer documentation describes QPRs as shipping "on a quarterly cadence" and being delivered to AOSP and Pixel devices as part of Feature Drops, but the official release notes and the QPR3 program page do not list a firm stable release date. Based on the cadence of Android's prior QPR cycles — which have typically run two to three betas before a stable rollout — Beta 2's focus on cleaning up a long tail of fixes (rather than introducing anything new) is consistent with a program that's maturing toward a stable release, but Pandromeda has not found an official date from Google and isn't going to guess one. Anyone expecting a specific month for stable QPR3 should treat that as unconfirmed until Google's own channels say otherwise.

It's also worth noting what Beta 2 doesn't change: Google's release notes for the beta cycle state these QPR updates "don't include app-impacting API changes," but developers are still encouraged to test their apps against the beta builds in case upcoming behavior changes affect user experience once the Feature Drop goes stable.

Frequently asked questions

Is Android 17 QPR3 Beta 2 safe to install on a daily driver?

It's a beta build, so Google's own guidance is to back up your data first. Beta 2 specifically targets stability bugs reported against Beta 1, so for people already running Beta 1, it should reduce rather than introduce crash-related issues, but any pre-release software carries some risk.

Can I go back to stable Android 17 after installing the beta?

Per Google's enrollment terms, once you've applied a beta update you can only return to the stable channel without a data wipe after a new stable release lands, and only before you accept the next beta build.

Does Android 17 QPR3 Beta 2 add any new features?

No. Google's official release notes for this build don't list any new user-facing features or developer-facing API changes. Every item in the published fix list is a bug fix carried over from issues reported against Beta 1.

How many bugs does Beta 2 fix compared to Beta 1?

Google's release notes credit Beta 2 with roughly 21 fixed issues, close to the roughly 20 fixes shipped in Beta 1. The two lists don't overlap — Beta 1 targeted crash-heavy reports like fingerprint-unlock freezes and NFC crashes, while Beta 2 cleared a second wave covering Wi-Fi Aware, Bluetooth pairing, and carrier-specific calling problems.

What's next for Android 17 QPR3

With Beta 2 focused entirely on bug fixes and carrying a fresh October security patch level, the most likely next step is either a Beta 3 refinement build or a move to a release candidate as Google closes out the remaining tracked issues. For now, anyone who wants the fixes in Beta 2 should either update from within the Android Beta for Pixel program or flash the build directly; everyone else can wait for the stable Feature Drop, whenever Google formally sets that date. Pandromeda will cover the stable QPR3 rollout, along with any further beta builds, as Google's release notes update. For the bigger picture on what else changed around Android 17 this cycle, see our report on October's Android update and its scam-call protections.

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