Android 17 QPR2 Beta 3 Rolling Out to Pixel Devices

Following last week’s release, Google has issued Android 17 QPR2 Beta 3 for Pixel devices in an uncommon Friday rollout. This build is the largest update of the current cycle and includes several important bug fixes and a notable security change to protect users from call-forwarding fraud.


Android 17 QPR2 greatly expands Dynamic Color theming on Pixel

Android 17 QPR2 lets you customize Pixel Quick Settings layout

Android 17 QPR2 brings system blur to the Pixel lockscreen

Android 17 QPR2 adds App lock to Pixel


This Beta 3 release includes a concise changelog addressing a couple of significant issues:

  • Fix for notification shade and Quick Settings instability: Opening the notification shade and Quick Settings could cause visual corruption and, in some cases, an unexpected device restart. The update corrects the root causes identified in tracking reports. (Issue #535249652, Issue #543124160)
  • Correction for Device Health and Support battery warnings: The Device Health and Support tool was generating false battery capacity degradation alerts for some users. This release fixes the erroneous messaging so that battery capacity is reported accurately. (Issue #535421490, Issue #538943170, Issue #535504630)

In addition to those bug fixes, Beta 3 introduces a security enhancement described as “Hardening against call forwarding fraud.” This change tightens how apps can programmatically trigger call-forwarding commands to prevent misuse and social engineering attacks.

Android 17 QPR2 Beta 3 introduces new security restrictions on programmatic call forwarding to protect users from fraud.

  • API restriction: The sendUssdRequest() API can no longer be used to execute call-forwarding codes with only the CALL_PHONE permission. Standard apps that try to run such codes in the background will be blocked and receive a USSD_ERROR_NOT_ALLOWED callback. This prevents silent or automated changes to call-forwarding settings by untrusted apps.
  • System confirmation for manual dialing: When a user dials a call-forwarding code directly in the system dialer, the OS will display a new, built-in confirmation dialog before executing the command. This extra step helps protect users from social engineering scams that rely on convincing a person to dial a forwarding code.
  • Non-call-forwarding USSD unaffected: USSD requests that do not enable call forwarding—such as balance checks, mobile money transactions, and other carrier services—are not impacted by this restriction and should continue to work normally.
  • Developer guidance and mitigation: Apps affected by this change should gracefully handle the USSD_ERROR_NOT_ALLOWED callback. For legitimate use cases that require user-initiated call forwarding, developers can migrate to the ACTION_DIAL intent to pre-fill the dialer with the appropriate code so the user can confirm and execute the action manually. Apps that qualify for specific exempted roles should ensure they meet the necessary criteria to retain access.

If you encounter issues while testing Beta 3, report them using the Android Beta Feedback app available on Pixel devices. Open the app from the application drawer or Quick Settings to file bugs directly to Google’s issue tracker. You can also participate in community discussions through the Android Beta community on Reddit for additional help and shared experiences.

  • Builds included in this release:
    CP41.260731.005.A2
    CP41.260731.005.B1

Android 17 QPR2 Beta 3 system images are available for a broad range of Pixel hardware, including 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, and Pixel 10a, as well as for the Android Emulator. Developers and enthusiasts can use these images for testing and validation on supported devices.

If you prefer to receive the update over the air, you can enroll your device in the Android Beta Program to get the OTA when it becomes available. Enrolling makes it easier to test the update on-device and provide timely feedback to Google.