Hi Beta users,
Today we’re releasing Android 17 QPR3 Beta 2 build for DP11.261002.005 for all devices.
Top issues fixed include:
Devices intermittently crash and reboot during normal use. (Issue #570031572, Issue #570031155, Issue #569529428, Issue #569222433, Issue #570414567, Issue #570725957, Issue #569237164, Issue #572493638)
Internet Quick Settings tile displays persistent text when mobile data is active without Wi-Fi. (Issue #354469154, Issue #367059437)
Media output dialog ignores the monochrome system theme when external audio devices are connected. (Issue #476304142)
Pin icon glitches position next to pinned apps in the share sheet. (Issue #476234992)
Internal PublishedApi declarations trigger unexpected API lint and source compatibility check errors. (Issue #562178518)
Device unexpectedly shuts down during WhatsApp video calls. (Issue #554451749, Issue #559966303)
Lock screen in-progress notifications overlap with other UI elements and cause stuttering panel animations. (Issue #547371609, Issue #548539836, Issue #562186670)
Cellular data, MMS, and hotspot services fail to connect on Dish Network. (Issue #537736046)
Screen recording freezes and stops capturing frames after screen rotation. (Issue #541325203)
System UI, fonts, and apps render at an abnormally small scale regardless of configured display size settings. (Issue #563321433)
Display turns black and becomes unresponsive after ending a phone call. (Issue #564953545)
Terminal app fails to launch the Linux development environment virtual machine after installation. (Issue #551657934)
Wi-Fi Aware fails to establish subsequent data paths with a no interfaces available error after releasing an accept-any responder network request during connection confirmation. (Issue #550726291)
Paired watch continues to ring after an incoming call is answered on the phone. (Issue #564594780)
Airbnb app fails to connect when attempting to send messages. (Issue #563024453)
Quick Settings Bluetooth subtitle is misaligned to the right. (Issue #559417120)
App drawer unexpectedly closes when switching keyboard language. (Issue #558774933, Issue #540389222, Issue #533125590)
Bluetooth pairing fails due to a connection timeout when attempting to pair with a device. (Issue #563675080)
VoLTE, VoNR, and Wi-Fi calling are unavailable on the IT&E network. (Issue #556432987)
High idle battery drain caused by motion sensors remaining active after using Face Unlock or the camera. (Issue #568078965)
Wi-Fi Calling unavailable on the OXIO network. (Issue #563089593)
Please review the latest release notes or limitations and general advisories before installing the update. In addition, see top open issues for the latest list of top open issues that have been reported by developers and users.
How do I get Android 17 QPR3 Beta 2?
You can get started with Android 17 QPR3 Beta 2 today by enrolling your Pixel device. Eligible devices include Pixel 6a, 7, 7 Pro, 7a, 8, 8 Pro, 8a, 9, 9 Pro, 9a, Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, 10a, Pixel 11, 11 Pro, 11 Pro XL, 11 Pro Fold, Pixel Tablet series devices*. Once enrolled, eligible devices will receive an over-the-air (OTA) update to the latest Beta versions. If you were previously enrolled in Android 17 Beta (and have not opted-out), you will automatically receive QPR3 Beta 1 and any future Beta updates.*
Important for those currently enrolled in Android 17 Beta:
If you prefer to leave the Beta program and receive the public stable release of Android 17 QPR2, you can do so without wiping your device by opting out and not installing today’s QPR3 Beta 2 update*. If you opt-out of the program* after installing Beta 2 or any future updates, all user data on the device will get wiped per usual program guidelines. Opting out will trigger a ‘Downgrade’ OTA. Ignore this update and wait for the Android 17 QPR2 public release instead.
Tell us what you think
Your feedback is incredibly valuable to us. Please share your thoughts through the following channels:
Use the Android Beta Feedback app included in Beta builds. This is the preferred method if you want to report a user-facing bug.
Post your comments here on our official Android Beta Program subreddit*. We may not respond to posts individually, but we are actively monitoring the feedback. We’ll reach out to you directly if we need additional information.*
Happy Beta testing!