Hmmm, interesting why google released second beta in one month (not 1.1
).... I was expecting second build next week (april)

It's fixedanyone install this yet and see if the adaptive colour is fixed? or is it still horrible?
nice, I'll install it now then
It's there for me.Clear calling is missing from settings for me. Anyone else have the same issue?
Weird. On Verizon and had it in QPR3 Beta 1.
Android 14 will make it easier to hide your phone’s PIN from shoulder surfers
BYMISHAAL RAHMAN
Android is adding a new "enhanced PIN privacy" setting that will make it safer for you to enter your phone's PIN in public.
Readers like you help support XDA Developers. When you make a purchase using links on our site, we may earn an affiliate commission. Read More.
Google just released the second beta for the upcoming Android 13 QPR3 release this June, but the new release doesn’t offer a whole lot in terms of new features and improvements. Since QPR3 will be Android 13’s final maintenance release, it mainly focuses on stability and bug fixing changes. However, some minor quality-of-life improvements do make their way into QPRs, and Android 13 QPR3 is no different. Given that few OEMs outside of Pixel ever merge QPRs, these quality-of-life improvements will become available on devices from other brands in the next major Android release, ie. Android 14. And in Android 13 QPR3 Beta 2, we spotted a new feature that’ll make its way to other devices on Android 14: Enhanced PIN privacy.
After booting up Android 13 QPR3 Beta 2 on a Pixel 6, we spotted a new “enhanced PIN privacy” toggle under Settings > Security & privacy > Device lock. The description for this toggle reads “disable animations while entering the PIN”, meaning that the animation that normally plays when you tap any number on the keyguard won’t be shown. This will make it harder for shoulder surfers to watch you enter your PIN, because the Android lock screen won’t show an obvious visual cue for each number you tap.
Here’s a video demonstrating this new enhanced PIN privacy feature. This video was recorded from another device because Android applies FLAG_SECURE to the keyguard window, preventing screenshots and screen recordings from being taken. Special thanks to Nail Sadykov for sharing this video with us!
Shoulder surfing is a common social engineering attack used to obtain access to users’ devices, as many people enter their PIN while in public places. A recent report from The Wall Street Journal showed how shoulder surfers could gain nearly full access to a user’s Apple or Google Account simply by observing their phone’s unlock code and then swiping their device. Making it harder for shoulder surfers to observe PIN entry will make it harder for them to subsequently access a user’s Apple or Google Account, hopefully.
Enhanced PIN privacy isn’t the only new lock screen-related improvement coming in Android 14. We previously spotted a new feature called “auto-confirm correct PIN” that allows you to bypass tapping Enter in order to unlock your phone. That feature is not available to users yet, unlike the new enhanced PIN privacy toggle we spotted in Android 13 QPR3 Beta 2. Speaking of which, it’s likely that this new enhanced PIN privacy toggle will appear in the next Android 14 preview release, which is expected to be Android 14 Beta 1. Android 14 Beta 1 will likely land in early April, and when it does, we’ll be covering the new features and changes extensively.
No problem here.Is anyone else having issues with the quick settings/ drop-down status bar
Mine gets stuck if I swipe down to see a notification have to restart the phone
banking apps are working totally fine for me, same with Google pay.Can anyone confirm that Banking apps din't work on the QPR Beta?? And what about google pay?
In other boards it says banking apps work perfect with beta and nothing won't work.
I am not having this issue either.Is anyone else having issues with the quick settings/ drop-down status bar
Mine gets stuck if I swipe down to see a notification have to restart the phone
Devices must be on a non-Developer Preview public stable build to enroll in the beta program.
I guess Night Light is enabled. Check your settings.The screen saturation went way up and looks great on Light mode but looks terrible on dark mode. Everything looks brown or reddish. Wallpaper and Themes are completely broken, as are Material You themes.
Release notes
bookmark
Beta 2.1Beta 2Beta 1
Android 13 QPR3 Beta 2.1 (April 2023)
Release date April 6, 2023 Build T3B2.230316.005 Security patch level March 2023 Google Play services 23.11.15
This minor update to Android 13 QPR3 Beta 2 includes the following improvements:
If you're already running Beta 2, you'll automatically receive an over-the-air (OTA) update to Beta 2.1.
- Modem updates
Note: Other known issues listed for the Beta 2 release still apply to Beta 2.1.
About Android 13 QPR3
Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR3 builds on the updates in Android 13 QPR2 and the initial Android 13 release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR3 Beta 2.1
You can install Android 13 QPR3 Beta 2.1 on any of the following Google Pixel devices:
See Get Android 13 QPR beta builds for details on how to get started.
- Pixel 4a and 4a (5G)
- Pixel 5 and 5a
- Pixel 6 and 6 Pro
- Pixel 6a
- Pixel 7 and 7 Pro
General advisories
Be aware of these general advisories about the release:
- This release might have various stability, battery, or performance issues.
- For users with accessibility needs, this release might not be appropriate for daily use.
- Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
- Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support
Two primary support channels are available to you when developing and testing with Android 13 QPR3. The channel you should use to get support depends on where you are encountering your issue.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
- Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.- Support for issues with other apps: Contact the app developer directly.
Feature updates
- Improvements for Adaptive Charging that can automatically adjust to your charging needs using on-device signals.
Top resolved issues
The following issues have been resolved in Android 13 QPR3 Beta 2:
- Fixed an issue that caused the volume panel to flicker when adjusting the volume using the volume buttons.
- Fixed an issue that caused the system UI to get stuck in a blurry state in some cases, such as unlocking the device or finishing a phone call.
- Fixed an issue where the notification shade was closing immediately after a user opened it.
- Fixed an issue where the always-on display was displayed over apps and other content after unlocking the device.
- Fixed an issue where a device couldn't copy apps and data wirelessly during first-time setup.
Top open issues
See top open issues for the latest list of top open issues that have been reported.
Other known issues
Based on our testing, you might encounter the following issues when using Android 13 QPR3. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform
- If the user tries to open the camera by pressing the power button twice, the camera displays a black screen instead.
- In some cases when a work profile is switched on or off, the device reboots instead.
- The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Previous beta releases
Android 13 QPR3 Beta 1
Top resolved issues
The following issues have been resolved in Android 13 QPR3 Beta 1:
- Fixed an issue where the clock text on the lockscreen was the wrong color.
- Fixed an issue where Bluetooth audio wasn't working on some devices.
- Fixed an issue where the fingerprint icon that is normally displayed on screen to indicate the position of the fingerprint sensor erroneously changed to an exclamation point (!).
- Fixed an issue where live wallpapers could not be selected or used.
- Fixed an issue where widgets, app icon positions, and other configurable options on the home screen were reset after installing an OTA update.
- Fixed an issue that caused a device to be unenrolled from Face Unlock after installing an OTA update.
Other known issues
Based on our testing, you might encounter the following issues when using Android 13 QPR3 Beta 1. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform
- If the user tries to open the camera by pressing the power button twice, the camera displays a black screen instead.
- In some cases when a work profile is switched on or off, the device reboots instead.
- The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Pixel 7 Pro | cheetah-t3b2.230316.005-factory-76ae442e.zip | 76ae442e77265d0011a192103402f210aee49e76a49b3bce405af7342cd1fb3b |
Pixel 7 Pro | cheetah-ota-t3b2.230316.005-b9c1f956.zip | b9c1f9568f22b3896ba962f090556e74a60bd83bb3bb94240af7acb7c687ea7e |
For Chase, here's how I got it to work on my P6 previously. There's an old thread where someone installed a downgraded version, but I didn't need to do that:
I force stopped the app and cleared cache/data. I then enabled airplane mode, went into the Chase app and entered my credentials. I hit the fingerprint option and hit "sign on." I got the error saying no data connection available. I reenabled data and signed on.
This unfortunately did not work for me. I pass safetynet and have magisk hidden as well as Chase on the deny list with all the ticks selected.
On my pristine (bootloader hasn't been touched) 7 Pro, I pass basic integrity and CTS and on the Play Integrity API Checker, I pass MEETS_DEVICE_INTEGRITY as well as MEETS_BASIC_INTEGRITY but fail MEETS_STRONG_INTEGRITY.
My Google Pay still works and that's all I cared about.
I also checked and the Chase app is allowing me to use my credit card rewards so it's not detecting any issues it cares about either.
The only thing that the Chase app won't do while rooted (and methods to fool it are implemented) is allow you to set up using a fingerprint in the app, but you can do so while temporarily not rooted (which I plan to do when the next Stable update drops if I remember), and it'll stick when you re-root. Yes, it's in my DenyList with no help for that.![]()
Force stop the phone app through app info a couple times. "Force Stop" button on right will be bright, repeat force stop until the button discontinues being bright.I just realized that I no longer have 'screen my call' option in the phone app. I'm on qpr3 beta 3.2 my carrier is Tmo. Anyone with similar issue?
I'm only being allowed to Opt into the Android 14 beta program. I want to enroll in the Android 13 QPR Beta program instead. Any idea how?
I don't know for sure, but I suspect that no one can opt into the QPR3 Beta program any longer.
Even Google's QPR3 Beta release page:
which has a link:Release notes | Android Developers
Release notes and known issues for the latest...developer.android.com
and leads to:
the Enroll in Android 13 Beta for Pixel button there still leads to:Get Android 13 QPR beta builds | Android Developers
Get Android 13 QPR beta builds on an eligible...developer.android.com
which only mentions Android 14 Beta.
So I think your only choice if you want to try QPR3 Beta is to have an unlocked bootloader and flash the factory image, or I think it's possible to sideload the OTA without unlocking the bootloader - but it's highly discouraged to try a Beta with a locked bootloader, as you'll be locked into the Beta program (via manual OTA sideloads) until it goes final, and you'll have no choice but to deal with the issues.
pt_vf |
pt_meo |
pt_nos |
ca_tbaytel |
uk_tesco |
lt_telia |
fi_telia |
ee_telia |
uk_sky |
Pixel 7 Pro | cheetah-t2b3.230109.002-factory-9b7903db.zip | 9b7903dbcf23bb41d1e3d86ed16eb5cd4309187c0def3aff148410dc34fcda5d |
Release notes
bookmark
Beta 3Beta 2.1Beta 2Beta 1
Release date February 1, 2023 Build T2B3.230109.002 Security patch level January 2023 Google Play services 23.03.13 About Android 13 QPR2
Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR2 Beta 3
You can install Android 13 QPR2 Beta 3 on any of the following Google Pixel devices:
See Get Android 13 QPR beta builds for details on how to get started.
- Pixel 4a and 4a (5G)
- Pixel 5 and 5a
- Pixel 6 and 6 Pro
- Pixel 6a
- Pixel 7 and 7 Pro
General advisories
Be aware of these general advisories about the release:
- This release might have various stability, battery, or performance issues.
- For users with accessibility needs, this release might not be appropriate for daily use.
- Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
- Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support
Two primary support channels are available to you when developing and testing with Android 13 QPR2. The channel you should use to get support depends on where you are encountering your issue.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
- Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.- Support for issues with other apps: Contact the app developer directly.
Top resolved issues
The following issues have been resolved in Android 13 QPR2 Beta 3:
Developer-reported and user-reported issues
- Fixed an issue where notifications in a notification group were sometimes displayed with straight corners instead of rounded corners. (Issue #264287776, Issue #265529116)
- Fixed an issue where the message in the notification shade that indicates an active VPN connection overlapped with the message about apps with active foreground services. (Issue #266075977)
- Fixed an issue where the overflow menu couldn't be accessed when editing Quick Settings tiles. (Issue #263484657)
- Fixed an issue that sometimes caused a device with vibration enabled to vibrate for too long after it received a notification. (Issue #239676913)
Other resolved issues
- Fixed an issue that sometimes caused messaging apps to crash or fail to send notifications.
- Fixed a GPU issue that prevented apps from using certain visual effects.
- Fixed an issue where Quick Settings tiles for a work profile were not added after setting up a new device.
- Fixed an issue that sometimes caused the Pixel launcher to crash when using the Search bar in the app drawer.
- Fixed an issue that sometimes prevented a device from being unlocked using a pattern after the Google Assistant was activated.
- Fixed an issue in the com.android.qns system process that sometimes caused crashes.
- Fixed an issue with the Pixel launcher that prevented Chinese text input from being recognized when typing in the Search bar in the app drawer.
- Fixed an issue where when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashed with a "Settings keeps stopping" message and then the system Settings app couldn't be opened.
- Fixed an issue with the System UI that sometimes caused it to crash from a null pointer exception.
- Fixed an issue where the connection status of a Bluetooth device sometimes did not match the actual device state.
- Fixed an issue where the Pixel launcher crashed when a user tapped a web search suggestion for a query term.
- Fixed an issue that caused status bar icons to overlap with the date text when font and display settings were set to their maximum level on a device.
Top open issues
See top open issues for the latest list of top open issues that have been reported.
Other known issues
Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform
- The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Previous beta releases
Android 13 QPR1 Beta 2
Android 13 QPR2 Beta 2.1 (January 2023)
This minor update to Android 13 QPR2 Beta 2 includes the following fixes:
- Fixed an issue that sometimes prevented devices from automatically connecting to a 5G network even when it was available. (Issue #265093352)
- Fixed an issue where devices did not drop or reset an existing, encrypted Bluetooth connection after receiving a command to disable link-layer encryption for that connection.
Top resolved issues
The following issues have been resolved in Android 13 QPR2 Beta 2:
- Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
- Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Other known issues
Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform
- The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
- In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
- An issue with the System UI can sometimes cause it to crash from a null pointer exception.
Android 13 QPR1 Beta 1
Other known issues
Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 1. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform
- The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
- In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
- An issue with the System UI can sometimes cause the Home screen to become unresponsive.
Google Apps
- After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Pixel 7 Pro | cheetah-t2b2.221216.008-factory-36873c04.zip | 36873c042e0eacb4fa634afe053444c4885c10c38565bcb01518750dc8030610 |