Android 17 QPR2 Beta 3 is a surprisingly feature-packed update

The update also introduces a security feature designed to protect users from phone scams that trick victims into enabling call forwarding.

Who’s getting Android 17 QPR2 Beta 3?

Google says QPR2 Beta 3 is rolling out as build CP41.260731.005.A2 for the Pixel 6a, Pixel 7 series, Pixel 7a, Pixel Fold, and Pixel Tablet, while other eligible devices get build CP41.260731.005.B1.

As with QPR2 Beta 1 and Beta 2, the Pixel 6 and Pixel 6 Pro aren’t supported by this release. Both phones will reach five years old before Android 17 QPR2 is expected to reach its stable release, marking the end of Google’s software support for the two devices.

Owners of a Pixel 6a or newer can still join the Android Beta Program and install QPR2 Beta 3. Eligible devices include the Pixel 6a, Pixel 7 series, Pixel 8 series, Pixel 9 series, Pixel 10 series, Pixel 10a, Pixel 10 Pro Fold, and Pixel Tablet.

If you’re already enrolled in the Android 17 beta, Google says QPR2 Beta 3 will arrive automatically as an over-the-air update unless you’ve opted out.

Google is also expanding the system’s theming controls with a new hue slider alongside four main color styles.

Google is continuing to lean into blur effects across Android’s system UI. In Android 17 QPR2 Beta 3, the effect has been expanded to more parts of the interface, including lock screen shortcuts, the fingerprint button, and notifications.

Android 17 QPR2 Beta 3 also brings a handy change for foldable phones. Apps running in windows now get an app handle that can be dragged to transition between full-screen and split-screen modes.

There’s also a new shortcut for opening a bubble in full-screen mode. Rahman notes that compared with the Canary build, the main difference is that the “Move to fullscreen” shortcut has been moved to the top of the context menu.

Google is making call-forwarding scams harder to pull off

Another big change in Android 17 QPR2 Beta 3 is that Google is adding new restrictions designed to protect users from call-forwarding fraud.

Android 17 will now parse and selectively restrict call-forwarding USSD codes, including codes such as 21, when they’re executed through the TelephonyManager.sendUssdRequest() API.

Under the new rules, regular apps can no longer use the sendUssdRequest() API to execute call-forwarding codes in the background simply with the CALL_PHONE permission. Attempts will be blocked and return a USSD_ERROR_NOT_ALLOWED callback.

In simple terms, Android 17 will now stop apps from secretly using call-forwarding codes to redirect your calls, adding an extra layer of protection against phone scams.

Google is also adding an OS-level confirmation dialog when users manually enter call-forwarding codes through the system dialer. The additional confirmation is intended to make scams harder to execute, particularly those where scammers convince victims to enter a code that silently redirects incoming calls.

Importantly, Google says this change does not affect other types of USSD requests, such as mobile-money transfers and account checks.

Android 17 QPR2 Beta 3 also fixes some major bugs

In addition to the major user-facing features, Google is also fixing several bugs in the latest build. One addresses an issue in which opening the notification shade or Quick Settings can cause visual corruption, followed by an unexpected device restart.

The update also fixes the Device Health and Support tool, which could incorrectly warn users that their battery capacity had degraded.

Moreover, the update adds an option in the Terminal app to control how links opened inside a virtual machine are handled. Users can choose to automatically forward web URLs from the VM to the host’s browser or open them inside a browser running within the VM, if one is installed.