![\"The](\"https:\/\/www.newsbeep.com\/us\/wp-content\/uploads\/2026\/04\/android-17-logo-hero-1-scaled.jpg\"\/ "\\"android"){kind=logo}
<\/p>\n<\/p>\n
Joe Maring \/ Android Authority<\/p>\n
TL;DR<\/p>\n
Android 17 QPR1 Beta 3 is now available for Pixel testers to install.
\nToday\u2019s release arrives just two weeks after Beta 2.
\nGoogle says this update includes \u201ca minor SDK release.\u201d<\/p>\n
Don\u2019t want to miss the best from Android Authority?<\/p>\n
Google got the ball rolling on Android 17 QPR1 Beta 1<\/a> in late April, before following up with Beta 2<\/a> a couple weeks later. Now, two more weeks down the line, it\u2019s time for Beta 3 to arrive. We first heard it was on the way a few hours back, when Google shared on the Android Developers Blog<\/a> that Beta 3 was landing with \u201ca minor SDK release to support a few features that just couldn\u2019t wait for QPR2.\u201d While we didn\u2019t see it at first, the release is now finally available for testers to install.<\/p>\n There are two revisions out today: CP31.260508.005.A1 for Pixel 6 and 7 models, and CP31.260508.005 for more recent hardware. If you\u2019re already on the testing track, you should be getting a notification about your update when it\u2019s ready to install. If you\u2019re just looking to get started now, the easiest way is to register your device with the Android Beta Program<\/a>.<\/p>\n Google\u2019s Mishaal Rahman<\/a> notes over on X that today\u2019s build includes a springy new notification animation, modified screen recorder behavior, and just a whole, whole lot of that definitely-not-Liquid-Glass blur across the UI.<\/p>\n Here are some of the fixes Google says are present in this release:<\/p>\n A recurring system error in ContextHubClientManager that caused excessive logcat noise when attempting to send messages to unregistered clients. (Issue #289721806<\/a>)<\/p>\n Clicking on the\u00a0date on at a glance prompts to open the terminal\u00a0(Issue #506101970<\/a>)<\/p>\n Wi-Fi unexpectedly disconnects due to erroneous low-quality detection despite strong signal strength. (Issue #494670350<\/a>)<\/p>\n Users experienced frequent crackling or distorted audio during media playback from any source. (Issue #482749744<\/a>,\u00a0Issue #471865281<\/a>,\u00a0Issue #485701794<\/a>,\u00a0Issue #489062503<\/a>,\u00a0Issue #494050912<\/a>,\u00a0Issue #494901502<\/a>,\u00a0Issue #493915745<\/a>,\u00a0Issue #458363923<\/a>)<\/p>\n UI elements are partially cut off or positioned off-screen when apps are expanded to full-screen mode. (Issue #476830614<\/a>,\u00a0Issue #489452085<\/a>)<\/p>\n Home screen widgets would disappear or become unavailable in the widget picker after a device reboot. (Issue #488125748<\/a>,\u00a0Issue #505117543<\/a>,\u00a0Issue #505671079<\/a>,\u00a0Issue #497140330<\/a>,\u00a0Issue #506685943<\/a>,\u00a0Issue #510967059<\/a>)<\/p>\n The mobile data icon incorrectly remains active in the Quick Settings panel after Airplane Mode is enabled. (Issue #501368569<\/a>,\u00a0Issue #505757076<\/a>)<\/p>\n![\"google](\"https:\/\/www.newsbeep.com\/us\/wp-content\/uploads\/2026\/05\/google_preferred_source_badge_light@2x.png\"\/ "\\"google"){kind=icon}
![\"google](\"https:\/\/www.newsbeep.com\/us\/wp-content\/uploads\/2026\/05\/google_preferred_source_badge_dark@2x.png\"\/ "\\"google"){kind=icon}
<\/a><\/p>\n