Joe Maring / Android Authority
TL;DR
- Android 17 QPR2 Beta 1 is now available for Pixel testers to install.
- The software offers our first look at the changes coming with Google’s Q4 2026 release of Android.
- Compatibility is available for Pixel 6a and later devices, but not for the original Pixel 6 series.
Many Android users are still waiting to try it for the first time. Android 17But for Pixel owners who have joined Google’s testing community, we’re already looking to the future. QPR1 is constructed as Android 17 QPR1 Beta 7 last week gave us an early look at the upcoming September feature drop, and now Google is already getting started on what’s next, with the release of Android 17 QPR2 Beta 1.
Like Google’s Mishaal Rahman confirm In X, this Beta represents the software we will finally see arrive as Google’s Q4 2026 version of Android. But while QPR1 supports devices from Pixel 6 onwards, QPR2 moves the needle forward and starts supporting devices with Pixel 6a – the original Pixel 6 and Pixel 6 Pro are no longer included. Considering both phones they turned 5 years old this October, that’s not unexpected, but it’s still sad to see.
Google starts off with a list of some of the most important bug fixes it’s rolling out with this build:
- Bluetooth pairing fails silently after remote connection loss. (Number 412524057)
- The media player controls briefly flashed on the lock screen when waking up the device even though app notifications were disabled. (Number 484607701)
- A system crash causes Pixel devices to reboot unexpectedly when invoking Gemini. (Number 505750489)
- Initiating a multi-finger drag and drop gesture caused the source app to stop receiving subsequent touch events. (Number 516836306)
- Notifications randomly became invisible in notification shade until system reboot. (Number 526139207, Number 522657034)
- ML-DSA key generation fails with an exception when the string digest “NONE” is used instead of the class constant. (Number 525612735)
- An issue in AccessibilityNodeInfo.toString() where window boundaries were incorrectly registered using screen boundaries, causing misleading accessibility debug data. (Number 520428442)
- Window-level UI blur effects could not be rendered and the developer’s “Allow window-level blurs” was reset after reboot. (Number 527376569)
Development…
Thank you for being part of our community. Read our Comment Policy before publishing.
