Android 17 QPR2 Beta 3: Security Hardening and Bug Fixes for Pixel

Google has released Android 17 QPR2 Beta 3, bringing targeted security hardening for call-forwarding protocols and critical stability patches to Pixel devices ranging from the 6a through the 10 series. As of August 14, 2026, the update (builds CP41.260731.005.A2 and CP41.260731.005.B1) is available for deployment via the Android Beta Program and OTA image flashing, following the August 5, 2026, security patch level.

The Tech TL;DR:

• Security Hardening: Google has restricted the sendUssdRequest() API to block unauthorized background call-forwarding, mitigating programmatic fraud.
• System Stability: The update resolves critical UI regressions involving the notification shade and Quick Settings, alongside false-positive battery degradation reporting.
• Deployment Scope: Supported hardware includes the Pixel 6a through the Pixel 10 series; Pixel 11 devices remain excluded from this specific beta cycle.

Architectural Security: The USSD Call-Forwarding Patch

The core of this release focuses on the misuse of Unstructured Supplementary Service Data (USSD) protocols. Android 17 QPR2 Beta 3 enforces a strict permission model: apps attempting to execute call-forwarding codes via the CALL_PHONE permission will now trigger a USSD_ERROR_NOT_ALLOWED callback.

For developers currently maintaining telephony-integrated applications, the migration path requires a shift toward the ACTION_DIAL intent. This forces the system dialer to open, ensuring the user must manually confirm the USSD command. This architectural shift prioritizes user-in-the-loop security over background automation for sensitive network requests.

// Implementation example for handling the new API restriction
Intent intent = new Intent(Intent.ACTION_DIAL);
intent.setData(Uri.parse("tel:*21*1234567890%23"));
startActivity(intent);

Stability and Performance Remediation

Beyond security, this beta addresses two high-priority regressions that impacted system reliability. Issue #535249652 and #543124160 identified a visual corruption bug triggered when accessing the notification shade and Quick Settings, which resulted in unexpected system restarts.

Additionally, the Device Health and Support tool has been patched to stop reporting erroneous battery capacity degradation. This bug, tracked under issues #535421490, #538943170, and #535504630, caused unnecessary friction for users and potential churn for support departments.

Comparative Context: QPR2 Iterations

This release follows the trajectory established in previous QPR2 builds. While earlier iterations focused on Bluetooth pairing reliability and resolving system crashes triggered by the Gemini assistant, this current build shifts toward granular permission management. According to reporting from digimanie.cz, the preceding Beta 2 focused on bug fixes and higher stability, whereas Beta 3 represents a more aggressive security posture. The transition to this build is recommended for developers testing their applications against the latest Android 17 runtime environment, particularly those utilizing telephony APIs.

Disclaimer: The technical analyses and security protocols detailed in this article are for informational purposes only. Always consult with certified IT and cybersecurity professionals before altering enterprise networks or handling sensitive data.