![\"The](\"https:\/\/www.newsbeep.com\/ca\/wp-content\/uploads\/2026\/07\/android-17-logo-hero-6-scaled.jpg\"\/ "\\"android"){kind=logo}
<\/p>\n<\/p>\n
Joe Maring \/ Android Authority<\/p>\n
TL;DR<\/p>\n
Android 17 QPR2 Beta 1 is now available for Pixel testers to install.
\nThe software offers our first look at changes set to arrive with Google\u2019s 2026 Q4 Android release.
\nSupport is available for Pixel 6a and later devices, but not the original Pixel 6 series.<\/p>\n
Lots of Android users are still waiting to get their first taste of Android 17<\/a>, but for Pixel owners who have joined Google\u2019s testing community, we are already looking far out into the future. QPR1 builds like Android 17 QPR1 Beta 7<\/a> from last week have been giving us an early peek at the upcoming September Feature Drop, and now Google is already getting started on what\u2019s next, with the release of Android 17 QPR2 Beta 1<\/a>.<\/p>\n As Google\u2019s Mishaal Rahman confirms<\/a> over on X, this Beta represents the software we\u2019ll ultimately see arrive as Google\u2019s 2026 Q4 Android release. But while QPR1 supported devices from the Pixel 6 on up, QPR2 moves the needle forward and begins its support with the Pixel 6a \u2014 the original Pixel 6 and Pixel 6 Pro are no longer included. Considering both these phones hit their 5-year birthdays<\/a> this October, that\u2019s not unexpected, but still sad to see.<\/p>\n Google starts off with a list of some of the larger bugfixes it\u2019s deploying with this build:<\/p>\n Bluetooth re-pairing fails silently following a remote bond loss. (Issue #412524057<\/a>) If you\u2019re interested in joining Google\u2019s test squad, you can register your Pixel phone at the Android Beta Program<\/a> sign-up page. And if you\u2019re already part of it, you\u2019ll soon be seeing your update notification arrive.<\/p>\n Critically, though, this also marks a point when a tester can make a clean exit from the program if they want to, and not lose their device\u2019s data in the process. If you\u2019ve been testing up to now but wish to get back on the stable track, you can simply choose not to install QPR2 Beta 1, opt out of the Beta Program, and wait for the stable September Feature Drop to arrive in a couple months.<\/p>\n
\nMedia player controls briefly flashed on the lock screen upon waking the device despite the app\u2019s notifications being disabled. (Issue #484607701<\/a>)
\nA system crash causing Pixel devices to unexpectedly reboot when invoking Gemini. (Issue #505750489<\/a>)
\nInitiating a drag-and-drop gesture with multiple fingers caused the source application to stop receiving subsequent touch events. (Issue #516836306<\/a>)
\nNotifications randomly became invisible in the notification shade until a system restart. (Issue #526139207<\/a>,\u00a0Issue #522657034<\/a>)
\nML-DSA key generation fails with an exception when using the \u201cNONE\u201d string digest instead of the class constant. (Issue #525612735<\/a>)
\nAn issue in AccessibilityNodeInfo.toString() where window bounds were incorrectly logged using screen bounds, which caused misleading accessibility debugging data. (Issue #520428442<\/a>)
\nWindow-level UI blur effects failed to render and the \u201cAllow window-level blurs\u201d developer toggle reset after rebooting. (Issue #527376569<\/a>)<\/p>\n