Skip to main content

Here’s everything new in Android 17 QPR2 Beta 3 [Gallery]

The preview for the December release continues today with a surprising Friday launch of Android 17 QPR2 Beta 3.

Over the coming hours, we’ll dive into all of Android 17 QPR2 Beta 3’s new features and every single change. (The newest updates will be at the top of this list. Be sure to check back often and tell us what you find in the comments below.) Android 17 QPR2 Beta 2 screenshots appear on the left and Android 17 QPR2 Beta 3 on the right.

If you want to quickly install Android 17 QPR2 Beta 3 on your compatible 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, be sure to check out our step-by-step guide.

Updating…

Advertisement - scroll for more content

More blur to system UI

Customize Pixel Quick Settings layout

  • From Android Canary. More

Expanded Dynamic Color theming

Hardening against call forwarding fraud


Android 17 QPR2 Beta 3 introduces new security restrictions on programmatic call forwarding to protect users from fraud. The system now parses and selectively restricts call-forwarding USSD codes (such as *21*) executed via the TelephonyManager.sendUssdRequest() API.

  • API Restriction: The sendUssdRequest() API is no longer accessible for call-forwarding codes using only the CALL_PHONE permission. Standard apps attempting to execute these codes in the background will be blocked and receive a USSD_ERROR_NOT_ALLOWED callback.
  • System Confirmation: To combat social engineering scams, users manually dialing call-forwarding codes in the system dialer will now see a new OS-level confirmation dialog before the command is executed.
  • Non-Call Forwarding USSD: Non-call forwarding enabling USSD requests (such as mobile money transfers and account checks) are unaffected by this change.
  • Mitigation: If your app is affected, verify that it handles the USSD_ERROR_NOT_ALLOWED failure callback gracefully. For apps requiring call-forwarding setup that do not qualify for an exempted role, migrate your flow to use the ACTION_DIAL intent to pre-fill the dialer, allowing the user to manually confirm the action.

Fixes

FTC: We use income earning auto affiliate links. More.

You’re reading 9to5Google — experts who break news about Google and its surrounding ecosystem, day after day. Be sure to check out our homepage for all the latest news, and follow 9to5Google on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our exclusive stories, reviews, how-tos, and subscribe to our YouTube channel

Comments

Author

Avatar for Abner Li Abner Li

Editor-in-chief. Interested in the minutiae of Google and Alphabet. Tips/talk: abner@9to5g.com