Android 17 QPR2 Beta 3 Adds New Security Protection

Android 17 QPR2 Beta 3: What Has Changed

Google’s latest Android 17 QPR2 Beta 3 update is more interesting than a routine bug-fix release. The August 14 beta adds a new protection against call-forwarding fraud while also fixing several Pixel system problems. Google’s official release notes confirm that the build includes changes aimed at both users and developers.

The timing makes the update worth watching because Android 17 QPR2 is moving toward a more polished release, while Google continues testing changes that can affect everyday phone security and usability.

The Biggest Change Is Protection Against Call-Forwarding Scams

The most significant change in Beta 3 is a new restriction designed to make call-forwarding fraud harder to exploit.

Android can now identify certain call-forwarding USSD codes and restrict apps from executing them programmatically. Google specifically says that the TelephonyManager.sendUssdRequest() API can no longer be used by standard apps to execute call-forwarding codes with only the CALL_PHONE permission. Blocked requests can return a USSD_ERROR_NOT_ALLOWED result. 

This matters because call-forwarding scams can be used as part of social-engineering attacks. A victim may be persuaded to enter a special dialing code, potentially changing where incoming calls are routed. Android 17 QPR2 Beta 3 adds another layer of protection before such commands can take effect.

Users Get an Extra Confirmation Step

The protection is not limited to apps. When a user manually enters a call-forwarding code through the system dialer, Android now shows an OS-level confirmation dialog before executing the command.

That extra step is simple, but it addresses an important weakness in scam scenarios: users may follow instructions without understanding what a USSD code actually does. A confirmation prompt gives the operating system an opportunity to make the action more visible.

Normal USSD Services Are Not Being Blocked

Google also makes an important distinction. Non-call-forwarding USSD requests, including functions such as mobile-money transfers and account checks, are not affected by this particular restriction. 

For developers whose apps legitimately need to configure call forwarding, Google recommends changing the flow rather than attempting to bypass the restriction. Apps that do not qualify for an exempted role can use the dialer intent to pre-fill the relevant action and let the user confirm it manually.

Android 17 QPR2 Beta 3 Also Fixes Pixel Problems

The security change is the headline feature, but Beta 3 also addresses several problems reported during earlier testing.

Google says the update fixes an issue where opening the notification shade or Quick Settings could cause visual corruption and an unexpected device restart. It also fixes incorrect battery-health warnings that could make users believe their device's battery capacity had degraded when it had not. 

These may sound like small fixes, but they are exactly the type of problems that matter during beta testing. A system interface that can trigger a restart is much more disruptive than a minor visual glitch, while inaccurate battery warnings can lead users to make unnecessary hardware or replacement decisions.

Which Devices Can Test Android 17 QPR2?

Google provides Android 17 QPR2 beta builds for a broad range of supported Pixel devices. The current supported list includes Pixel 6a, Pixel 7 series, Pixel Tablet, Pixel Fold, Pixel 8 series, Pixel 9 series, Pixel 10 series and Pixel 10a. 

Developers can also use the Android Emulator to test their applications. Generic System Images are available for development and compatibility testing, although Google describes GSI builds as experimental tools intended for developers rather than normal everyday use. 

What Android 17 QPR2 Means for App Developers

For most developers, the call-forwarding change is the part that deserves the closest attention. Apps that rely on programmatic USSD behavior should test their flows against the new restrictions instead of assuming previous behavior will continue.

Google says Android 17 QPR2 includes a minor SDK release and does not have planned behavior changes that broadly require compatibility testing. However, the release notes specifically document the new call-forwarding restrictions and recommend handling the blocked-request callback correctly where applicable. 

This is a useful reminder that platform updates are not always about new visual features. A relatively small API behavior change can matter more to an app developer than a redesigned interface because it can affect an existing workflow or automation.

Is Android 17 QPR2 Beta 3 Ready for Everyone?

It depends on what you use your phone for. Google makes Android 17 QPR2 available through the Android Beta for Pixel program, but it remains a beta release rather than the normal stable software channel. Google recommends backing up a device before enrolling. 

For developers and enthusiasts who want early access, the beta can be useful for testing compatibility and exploring upcoming changes. For someone who depends on their phone for banking, work, navigation or other critical tasks, waiting for the stable release is the safer choice.

Why This Update Matters

Android 17 QPR2 Beta 3 shows a useful direction for Google's mobile platform: security improvements are being built into everyday interactions rather than relying entirely on users to recognize scams themselves.

The call-forwarding protection is especially notable because it targets a real-world abuse pattern while still leaving ordinary USSD functionality available. Combined with the stability fixes, it makes Beta 3 less about flashy new features and more about making Android harder to misuse.

For users, the practical takeaway is simple: if you're running the Android beta, this is an update worth installing for the fixes and security changes. If you're on stable Android, there is no need to chase the beta just for these features. The more important story is what eventually makes its way into the stable Android 17 QPR2 release.

FAQ

What is Android 17 QPR2 Beta 3?

It is the third beta release of Android 17's second Quarterly Platform Release. Google released Beta 3 on August 14, 2026, with security, stability and platform improvements. 

What is the biggest new Android 17 QPR2 feature?

The most notable change in Beta 3 is protection against call-forwarding fraud, including restrictions on programmatic call-forwarding USSD requests and an additional confirmation step in the system dialer. 

Does Android 17 QPR2 block all USSD codes?

No. Google specifically says non-call-forwarding USSD requests, such as mobile-money transfers and account checks, are unaffected by this change.

Should normal users install the Android 17 QPR2 beta?

Only if they are comfortable using beta software. Developers and enthusiasts can benefit from early testing, while users who depend on maximum stability may prefer to remain on the stable release.