Android 17 QPR2 Beta 5 Still Fixes Pixel Reboots

Google shipped Android 17 QPR2 Beta 5 to Pixel testers on September 15, 2026, with fixes for unexpected reboots and Bluetooth audio distortion. The drop uses two builds, CP41.260828.005.A6 and CP41.260828.004.A8, and it arrives 18 days after Google declared QPR2 at Platform Stability.

Platform Stability froze the APIs. Beta 5 is still chasing bugs that reboot a phone, scramble Bluetooth after a call, and freeze the touchscreen when Wallet launches from the power button.

The Beta That Followed Platform Stability

On August 28, 2026, Android 17 QPR2 Beta 4 reached Platform Stability, the point where Google locks the API surface so app makers can stop chasing a moving target. The company published a minor SDK bump to API 37.2 and said the increment has no planned behavior changes, which cuts the need for compatibility testing. The security patch stayed on August 5, 2026, and Google Play services stayed on 26.28.33.

Beta 5 did not move those two numbers. It is a bug-fix drop on the same August 5 patch, sent to phones already in the Android Beta for Pixel program and mirrored the next day in Google’s Beta 5 notice to testers on the Android Beta subreddit. Google told enrolled users it was sending CP41.260828.005.A6 to the Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Fold, and Pixel Tablet, and CP41.260828.004.A8 to every other supported Pixel.

Quarterly Platform Releases land as Pixel Feature Drops. QPR1 was the September drop, so QPR2 is the year-end drop on that same quarterly clock, though Google has not named a public stable date. Beta 5 is the polish pass that is supposed to make that drop feel finished. The changelog still reads like a phone that can fall over in ordinary use.

Eight Bugs Closed After the APIs Froze

Google’s developer notes put eight issues closed in Beta 5 at the top of the page, each with an issue-tracker ID. The list is short, and several items are the kind of fault that ends a workday: a reboot while scrolling, a dead touchscreen, a camera crash, and dirty Bluetooth audio after a call.

BETA 5 FIXES IN GOOGLE’S NOTES

The reboot line is the one that sits least comfortably next to a milestone called Platform Stability. Google wrote it as a system-stability fault, not a rare edge case, and tied it to continuous scrolling in apps packed with media.

A system stability issue that caused unexpected device reboots during continuous UI scrolling in media-heavy applications.

Google, Android 17 QPR2 Beta 5 release notes

Wallet from the power button is a shortcut people actually use at a checkout. A panorama crash is a camera path, not a developer toggle. HDR that ignores its own off switch is a display lie. None of those belong in a build that is meant to be days from a public Feature Drop, and Google still had to ship a dedicated beta to close them.

Bluetooth Keeps Coming Back on Pixel

Pixel Bluetooth has been in the QPR2 notes since the first preview. Beta 5 does not open a new front so much as return to one Google already tried to close. Beta 4 in late August listed a fault where phone-call audio defaulted to the handset speaker instead of a connected Bluetooth device, and it cited four tracker IDs for that single problem (537908014, 541501134, 541772860, 545047074). Three weeks later the Beta 5 notes are back on Bluetooth audio, this time for noise and distortion after a call is completed or answered.

BLUETOOTH BUGS ACROSS QPR2

• Beta 1, July 20: Bluetooth re-pairing failed silently after a remote bond loss (issue 412524057).
• Beta 4, August 28: Call audio defaulted to the phone speaker instead of a paired Bluetooth device.
• Beta 5, September 15: Bluetooth audio picked up noise and distortion after completing or answering a call (issue 541684282).
• Same Beta 5 drop: Changing a Bluetooth device type in Settings still failed to refresh its icon (issue 516071134).

Testers who moved onto QPR2 Beta 1 in early August already described missing notification sounds and flaky Bluetooth playback, including trouble with Pixel Buds and Android Auto, right after QPR1 had closed a separate audio-buffer crash. The public conversation around Beta 5 is quiet, mostly reprint posts, and the objection that remains is simple: August’s stability stamp did not take Bluetooth off the work list for September.

Which Pixels Get QPR2 Beta 5?

Google’s supported Pixel list for QPR2 names 23 devices, from the Pixel 6a through the Pixel 11 Pro Fold. Pixel 6 and Pixel 6 Pro are not on it. Their software window closed with QPR1, so they sit out this entire QPR2 cycle, betas and the later stable drop alike.

THE TWO BETA 5 BUILDS

That split is six older devices on.005.A6 and 17 newer ones on.004.A8. The Pixel 11 family only joined the QPR2 beta on September 1, when Google posted Beta 4 images for those phones after the rest of the lineup had already been on that build for days. Factory images for Beta 5 now include the Pixel 11, Pixel 11 Pro, Pixel 11 Pro XL, and Pixel 11 Pro Fold, even if some owners still talk as if the newest phones are waiting on a separate program.

Enrolling is the supported path for daily testers. Google says you usually do not need a full wipe to move onto the QPR2 beta, but it still wants a backup first. Flashing a factory image is the other door, and that one does require a full reset.

The Reboot That Survived Platform Stability

Reboots are not a one-off in this cycle. Google has now listed an unexpected restart in three straight QPR2 betas, each under a different cause, which is why the August 28 milestone reads oddly against the September 15 notes. The APIs stopped moving. The phones did not.

THE QPR2 BETA CALENDAR

1. July 20, 2026: QPR2 Beta 1 opens (CP41.260701.005) and already lists a silent Bluetooth re-pair failure plus a system crash that rebooted Pixels when invoking Gemini.
2. August 3, 2026: Beta 2 arrives (CP41.260717.006) on the July 5 security patch.
3. August 14, 2026: Beta 3 (CP41.260731.005.A2 /.B1) fixes visual corruption and an unexpected restart when opening the notification shade and Quick Settings.
4. August 28, 2026: Beta 4 hits Platform Stability and closes a thermal-management fault that overheated devices and rebooted them during use, plus the Bluetooth-to-speaker call bug.
5. September 15, 2026: Beta 5 ships on the same August 5 patch as Beta 4 and closes unexpected reboots during continuous scrolling in media-heavy apps.

From Beta 1 to Beta 5 is 57 days. The last two drops share a security patch and a Play services build, so September’s work is concentrated on faults testers kept filing after the API freeze. That is the normal shape of a late QPR, and it is also why “Platform Stability” is a developer milestone, not a promise that the phone will stay up while you scroll Photos.

Call Forwarding Now Needs a Confirmation

The one platform change Google is still explaining to app developers in the QPR2 notes is not a Pixel animation. Android 17 QPR2 adds new limits on app-driven call forwarding, aimed at fraud that uses USSD codes such as *21#. The system now parses those codes when they go out through TelephonyManager.sendUssdRequest(), and it blocks the ones that only held the CALL_PHONE permission.

THE CALL FORWARDING LOCKS

• API block: sendUssdRequest() can no longer fire call-forwarding codes with only CALL_PHONE; blocked apps get a USSD_ERROR_NOT_ALLOWED callback.
• Dialer prompt: People who type a forwarding code in the system dialer now get an OS-level confirmation dialog before the command runs.
• Other USSD: Non-forwarding USSD, including mobile-money transfers and account checks, stays unchanged.
• App workaround: Apps that still need a forwarding setup and do not hold an exempted role are told to switch to ACTION_DIAL so the user can confirm the pre-filled code.

Google frames this as a social-engineering defense, not a Pixel-only tweak, and it ships in the same QPR that is still patching Bluetooth icons and panorama crashes. Developers who already targeted API 37.2 at Beta 4 do not have a new behavior change to retest here beyond that USSD path. Everyone else is looking at a bug-fix image.

CinnamonBun Factory Images and the OTA Path

The emulator image is still named CinnamonBun. Google’s factory-image page for this milestone also points testers to a browser flasher that can flash CinnamonBun QPR2 Beta 5 over USB, with no local toolchain, once USB debugging is on. Manual factory zips sit on the same page, one archive per device, and flashing any of them wipes the phone. OTA zips are posted for recovery cases where a beta install left a device unable to boot.

WAYS ONTO BETA 5

• OTA: Enroll the phone, then take the update in Settings, which is how most testers should move.
• Browser flash: Use Android Flash Tool with the CinnamonBun QPR2 Beta 5 preview link.
• Factory zip: Download the matching image and flash it locally, which resets the device.
• Emulator: Install the CinnamonBun system image in Android Studio’s Device Manager for app work without a physical Pixel.

Testers digging through the build have also flagged items that never made Google’s top-issue list. An Audio streams Quick Settings tile for joining Auracast broadcasts showed up, the older Quick Settings layout customization from earlier QPR2 builds is gone in this one, and Pixel 10 and Pixel 11 units gained a second Proactive Assistance entry in Settings beside the Gemini-branded original. Those are tester notes, not changelog promises, and they can still move before the stable Feature Drop.

Google has not named a day for that stable QPR2 image. Testers who want off the beta train can leave without a data wipe after a stable build lands, and only until they take the next beta. Until then, Beta 5 is the build that has to prove the August API freeze came with a phone that stays up through a long scroll and a Bluetooth call.