Android 17 QPR 2 Beta 1 Fixes Bluetooth, Gemini Crashes, and Notifications
Google released Android 17 QPR 2 Beta 1 on July 20, 2026, build CP41.260701.005, and the entire release is structured around repairs. The three headline fixes address Bluetooth accessories silently failing to reconnect after a disconnect, Pixel devices rebooting when invoking Gemini, and notifications randomly going invisible, per Google's official release notes. One notable gap: the Pixel 6 and Pixel 6 Pro are absent from the supported device list, despite both receiving the stable July Android 17 update earlier this month and being supported in the prior beta track.
Bluetooth failures affect headphones, car audio, and speakers. A Gemini-triggered reboot is a system crash tied to one of Google's most prominently marketed Pixel features. Invisible notifications mean users can't know what they've missed.
The three fixes in Android 17 QPR 2 Beta 1
The Pixel Bluetooth re-pairing fix targets Issue #412524057, documented in Google's release notes. The underlying problem is a remote bond loss scenario: when the connection between a Pixel and a Bluetooth device drops at the remote end, the two fail to re-pair when both come back online. The failure is silent. No error message, no pairing prompt. A user would simply find their audio disconnected with no immediate indication why, short of opening Bluetooth settings to pair manually.
The Gemini crash fix on Pixel addresses Issue #505750489, also in Google's release notes. Invoking Gemini on affected devices could trigger a full system reboot. Google has tied the fix to a tracked issue ID, which signals a targeted repair rather than a speculative patch. QPR 2 Beta 1 is still pre-release software, though, and beta testing will show how the fix holds across different device configurations and Gemini usage patterns.
The notification fix is less formally documented in Google's official notes but was highlighted by Android Police as one of the major changes in the release: notifications rendering invisibly, present in the system but blank or absent from the screen. Unlike the Bluetooth and Gemini issues, no public issue ID has been assigned in sources reviewed for this article. The specific conditions that triggered the problem are not detailed in available reporting.
All three fixes share a structural characteristic worth noting: they're repairs to things users interact with constantly. Bluetooth connections, AI assistant invocations, notification awareness. These aren't buried in settings menus.
Where QPR 2 Beta 1 fits in the current Android 17 beta cycle
QPR 2 Beta 1 arrived six days after QPR1 Beta 7 shipped on July 15. Google is running both QPR tracks in parallel: QPR1 is in its final stretch toward a public stable release while QPR2 testing is already being seeded to enrolled testers.
The QPR1 cleanup cycle has been dense. QPR1 Beta 6, released three weeks ago, delivered platform stability, locking the API surface so developers could ship final apps without risk of further breakage, 9to5Google documented. That same release also resolved a WindowManagerGlobal bug causing app crashes, a hotspot issue where custom network names reverted to generic defaults, and Quick Settings carousel glitches triggered by fast swiping.
QPR1 Beta 7 then addressed three more Quick Settings problems, 9to5Google reported. Battery Share was failing to activate from its Quick Settings tile on some devices, with the charging animation looping endlessly on others. Google tracked the behavior across seven distinct issue reports. Toggling Wi-Fi off created an empty gap between the battery and mobile data icons in the status bar (Issue #517178332). The font size controller in Quick Settings was crashing outright when tapped, leaving users unable to adjust text size without restarting the phone or avoiding the panel entirely. QPR1 Beta 7 also included no major regressions in its release notes, WebProNews noted, which is a meaningful signal at this stage of a release cycle.
Those QPR1 changes are expected to reach all eligible Pixel users through the September Feature Drop, WebProNews reported. QPR 2 Beta 1 is now the first step in the next round of Android 17 beta bug fixes.
Android 17 QPR 2 Beta 1 supported devices and the Pixel 6 gap
Eligible devices for QPR 2 Beta 1 are the Pixel 6a and Pixel 7 or newer, including foldables, Android Police confirmed. Enrolled users receive the update over the air automatically; system images are also available for manual flashing.
The Pixel 6 and Pixel 6 Pro are not on that list. Both received the stable July 2026 Android 17 update, which shipped July 7, and were supported in the prior beta track, 9to5Google reported. Their absence from QPR 2 Beta 1 draws a line through the middle of the same device generation, with the Pixel 6a eligible while its siblings are not.
Google has not publicly explained the exclusion. It could reflect a technical issue specific to those devices, a staged narrowing of pre-release access as those models age, or something else. The available reporting doesn't resolve it, and speculating beyond that isn't useful.
Pixel 6 and 6 Pro owners remain on stable Android 17 and continue to receive security updates. What their QPR2 beta exclusion means beyond the current cycle is an open question.
What beta users should do next
QPR 2 Beta 1 carries a security patch level of 2026-07-05, per Google's release notes. The Bluetooth re-pairing and Gemini crash fixes are each tied to specific tracked issue IDs, which gives reasonable confidence that the repairs are targeted. The notification fix doesn't carry a public issue ID in available sources, but Android Police flagged it as a major change in the release.
For beta users on supported devices experiencing Bluetooth re-pairing failures or Gemini-triggered reboots, this is the fix cycle to be on. If neither problem has surfaced, the update is still worth taking: broader testing coverage helps surface edge cases that internal testing may not catch, and the notification fix applies to any enrolled user.
Bugs can be filed through the Android Beta Feedback app, accessible from the app drawer or Quick Settings, or directly via Google's public issue tracker, 9to5Google noted.
For Pixel 6 and 6 Pro owners, the stable channel is where things stand for now. The QPR1 fixes moving toward the September Feature Drop are the ones to expect first. Whether QPR 2 Beta 1's repairs eventually reach those devices through a future monthly update, Google hasn't confirmed.
Comments
Be the first, drop a comment!