Android 17 QPR 2 Beta 2 is now available

2 months ago 9

Technically, Google lone releases 1 large Android mentation per twelvemonth – this twelvemonth it was Android 17. However, the institution besides works connected Quarterly Platform Releases (also known arsenic QPRs), which it serves up to Pixel devices arsenic good arsenic successful the signifier of AOSP images. Yesterday, Google rolled retired Android 17 QPR 1 Beta 8 to Pixels and present Android QPR 2 Beta 2.

Strangely, the merchandise notes marque nary notation of what has changed since QPR 2 Beta 1. Below you tin find the changelog for QPR 2 Beta 1.

If you privation to effort retired Beta 2 connected your phone, you tin articulation the Android Beta Program. OTA updates are disposable for the pursuing models:

Pixel 6a
Pixel 7
Pixel 7 Pro
Pixel 7a
Pixel Tablet
Pixel Fold
Pixel 8
Pixel 8 Pro
Pixel 8a
Pixel 9
Pixel 9 Pro
Pixel 9 Pro XL
Pixel 9 Pro Fold
Pixel 9a
Pixel 10
Pixel 10 Pro
Pixel 10 Pro XL
Pixel 10 Pro Fold
Pixel 10a

As promised, present is the changelog for the erstwhile Android 17 QPR 2 Beta 1:

Bluetooth re-pairing fails silently pursuing a distant enslaved loss. (Issue #412524057)
Media subordinate controls concisely flashed connected the fastener surface upon waking the instrumentality contempt the app's notifications being disabled. (Issue #484607701)
A strategy clang causing Pixel devices to unexpectedly reboot erstwhile invoking Gemini. (Issue #505750489)
Initiating a drag-and-drop motion with aggregate fingers caused the root exertion to halt receiving consequent interaction events. (Issue #516836306)
Notifications randomly became invisible successful the notification shadiness until a strategy restart. (Issue #526139207, Issue #522657034)
ML-DSA cardinal procreation fails with an objection erstwhile utilizing the "NONE" drawstring digest alternatively of the people constant. (Issue #525612735)
An contented successful AccessibilityNodeInfo.toString() wherever model bounds were incorrectly logged utilizing surface bounds, which caused misleading accessibility debugging data. (Issue #520428442)
Window-level UI blur effects failed to render and the "Allow window-level blurs" developer toggle reset aft rebooting. (Issue #527376569)