- Google has released the beta OS update “Android 17 QPR2 Beta 3” for Google Pixel devices enrolled in the pre-release Android OS trial program, the “Android Beta Program.”
- The highlight feature of this “Android 17 QPR2 Beta 3” is the hardening of the call forwarding function aimed at preventing fraud.
- It also includes two bug fixes.
On Friday, August 14, 2026 local time, Google released the beta OS update “Android 17 QPR2 Beta 3” for Google Pixel devices enrolled in the pre-release Android OS trial program, the “Android Beta Program.”
“Android 17 QPR2,” which serves as the base for “Android 17 QPR2 Beta 3,” is the second set of updates following the first update group “Android 17 QPR1” for the Quarterly Platform Releases (QPR) rolled out after the official release of “Android 17.” Meanwhile, “Android 17 QPR2 Beta x” serves as the beta OS leading up to the official release.
“Android 17 QPR2 Beta 3” is being distributed via Over the Air (OTA) software updates to a total of 19 Google Pixel models enrolled in the “Android Beta Program”: Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Fold, Pixel Tablet, 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. The new-generation Google Pixel devices releasing on Thursday, August 20, 2026—Pixel 11, Pixel 11 Pro, Pixel 11 Pro XL, and Pixel 11 Pro Fold—are not yet included in the lineup.
Additionally, starting from “Android 17 QPR2 Beta 1,” the “Pixel 6” and “Pixel 6 Pro” remain excluded from the supported devices.
The highlight feature of this “Android 17 QPR2 Beta 3” is the hardening of the call forwarding function designed to prevent fraud. A mechanism has been introduced in which the system analyzes and selectively restricts call forwarding USSD codes such as “*21*” executed via the “TelephonyManager.sendUssdRequest()” API.
Specifically, if an app possessing only the “CALL_PHONE” permission attempts to execute a call forwarding code in the background, the operation will be blocked and a “USSD_ERROR_NOT_ALLOWED” callback will be returned. On the other hand, if a user manually enters a call forwarding code through the system’s dialer app, a new OS-level confirmation dialog will appear before execution, reinforcing defenses against scams exploiting social engineering. Note that USSD requests that do not involve call forwarding, such as mobile remittances or balance inquiries, are not affected by this change.
Developers of call forwarding apps affected by this change will need to properly handle the “USSD_ERROR_NOT_ALLOWED” failure callback. Furthermore, for apps that do not fall under the exempted roles but require call forwarding configuration features, transitioning to a flow where the “ACTION_DIAL” intent is used to pre-fill the number in the dialer and have the user manually confirm the operation is recommended.
In addition, “Android 17 QPR2 Beta 3” includes the following two bug fixes.
| ■ “Android 17 QPR2 Beta 3” Main Bug Fixes and Improvements |
|
After applying the “Android 17 QPR2 Beta 3” update, the build number will be updated to “CP41.260731.005.A2” or “CP41.260731.005.B1,” the Android security patch will be updated to “August 5, 2026,” and the “Google Play services” app will be updated to v26.26.34 or later.
| ■ Build Number |
|
| ■ Android Security Patch |
|
| ■ “Google Play services” App |
|
Source: Google (https://developer.android.com/about/versions/17/qpr2/release-notes#beta3)