General May 16, 2023 QPR3 Beta 3.2 T3B3.230413.009 - Pixel 7 Pro [Cheetah] - [thread also for future Android QPR Betas]

Search This thread

Lughnasadh

Senior Member
Mar 23, 2015
5,155
6,028
Google Nexus 5
Huawei Nexus 6P
Just to confirm I'm safe to click leave beta today before the release of the final next week will still be able to just install the final when it drops without getting wiped as it says in the below picture below?
As long as you ignore/don’t apply the downgrade OTA update when you receive it. Just make sure you ignore installing it and wait for the stable QPR2 build to reach your phone.
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
Will I be able to sideload QPR 3 beta 1 if I'm currently on 14 DP 2 as long as it has a later build date? I have a Tmo PPro7 with a locked bootloader.
Not without wiping. That would be a technical downgrade. Downgrades of Android OS, especially major version without wiping, can cause unpredictable results. The later build date doesn't matter, since you'd be going from a higher Android version.

However, if you are prepared to wipe and try it anyway, do feel free to let us know your experience. :) But not recommended.
 

dd805bb

Senior Member
Sep 18, 2017
453
257
Google Pixel
Google Pixel XL
I hit the F it button and dirty flashed March official instead of waiting for the official OTA.. Nothing happened. Booted fine. I am rooted so you can't do that on a locked BL. It does rollback from Beta to official so I would guess their official OTA will just have the newer BL.
AGAIN FOR THOSE THAT DONT KNOW, YOU CAN NOT DO THAT UNLESS ROOTED! Just saying. All my modules loading fine, and I am on Magisk 25209 official. FYI.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Can I sideload from beta to stable March if my bootloader is still locked without a wipe ?
This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader.

I hit the F it button and dirty flashed March official instead of waiting for the official OTA.. Nothing happened. Booted fine. I am rooted so you can't do that on a locked BL. It does rollback from Beta to official so I would guess their official OTA will just have the newer BL.
AGAIN FOR THOSE THAT DONT KNOW, YOU CAN NOT DO THAT UNLESS ROOTED! Just saying. All my modules loading fine, and I am on Magisk 25209 official. FYI.
To clarify, all you need is to have the bootloader unlocked - you don't have to actually be rooted. Otherwise, you can also use the OTA method above if your bootloader is locked.
 

dd805bb

Senior Member
Sep 18, 2017
453
257
Google Pixel
Google Pixel XL
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
I have a question. If I put the patched magisk init boot image (same name as original) in the firmware file, would it update correctly it directly via fastboot? Just trying to skip the second step to install the patched init boot image via fastboot.
I don't think it will flash the files if they're modified. You can do it this way, instead, though:
You're right, I forgot all about that, sorry I'm guilty, I don't manually modify the script ;)
@whitewallman
You can't add --slot-all to the update image line

Your can refer to this as template, this one works to flash both slot.
In fact it even allows you to flash the patched file before rebooting to system

Code:
@ECHO OFF

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot.exe --slot all  flash bootloader bootloader-xxx.img
fastboot.exe reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot.exe --slot all  flash radio radio-xxx.img
fastboot.exe reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot.exe  --skip-reboot update image-xxx.zip
echo Switching active slot to the other ...
fastboot.exe --set-active=other
echo rebooting to bootloader ...
fastboot.exe reboot bootloader
ping -n 5 127.0.0.1 >nul
fastboot.exe  --skip-reboot update image-xxx.zip
echo rebooting to bootloader ...
fastboot.exe reboot bootloader
ping -n 5 127.0.0.1 >nul
echo flashing Magisk patched image ...
fastboot.exe --slot all  flash init_boot magisk_patched_xxx.img
echo rebooting to system ...
fastboot.exe reboot

Note that you can remove the stuff having to do with flashing both slots, as it's useless. I re-tested just yesterday with the same firmware flashed to both slots, and once you successfully boot one of the slots, it's impossible to boot the other slot because as @Lughnasadh has pointed out, Google switched to storing some information for your running Android slot on the other slot to save storage space or something like that.

So you can adjust it to:
Code:
@ECHO OFF

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot.exe flash bootloader bootloader-xxx.img
echo rebooting to bootloader #1 of 3...
fastboot.exe reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot.exe flash radio radio-xxx.img
echo rebooting to bootloader #2 of 3...
fastboot.exe reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot.exe  --skip-reboot update image-xxx.zip
echo rebooting to bootloader #3 of 3...
fastboot.exe reboot bootloader
ping -n 5 127.0.0.1 >nul
echo flashing Magisk patched image ...
fastboot.exe flash init_boot magisk_patched_xxx.img
echo rebooting to system ...
fastboot.exe reboot
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
5,155
6,028
Google Nexus 5
Huawei Nexus 6P
I have a question. If I put the patched magisk init boot image (same name as original) in the firmware file, would it update correctly it directly via fastboot? Just trying to skip the second step to install the patched init boot image via fastboot.
I don't think it will flash the files if they're modified. You can do it this way, instead, though:
Doing it this way should be ok, but as The Rode Warrior pointed out, you can also do it the way he suggested. Or, as another option if you are trying to skip manual steps, just use Pixel Flasher.

By the way, one user has reported that that replacing the stock init_boot.img with the patched one in the firmware file does work.
 
  • Like
Reactions: roirraW "edor" ehT

badabing2003

Recognized Contributor
Sep 17, 2012
2,299
3,233
The PATH=%PATH%;"%SYSTEMROOT%\System32" is optional, if that's where you keep your extracted Platform-Tools.
The PATH=%PATH%;"%SYSTEMROOT%\System32" comes from the flash_all.bat script by Google, it is on the first line after the comments.
This is probably due to fastboot.exe having dependencies on windows binaries which are in system32,.
Typically the PATH environment would already have system32 in the path, the script is making sure it has by adding it just in case the user env settings has been modified intentionally or unintentionally.
It's just a safety measure added by Google.
By the way, one user has reported that that replacing the stock init_boot.img with the patched one in the firmware file does work.
Yes, this is how early versions of PF used to do, by repacking the patched boot into the firmware and flashing.
It no longer does that because that is slow and unnecessary.
What it currently does is:
  • it builds a modified flash_all script (called flash-phone.bat)
  • Uses full path to Android platform tools, this assures to pick up the correct fastboot instead of some random one in the system path
  • Specifies the device ID, this assures to apply to the correct device, if multiple devices happen to be connected to the PC
  • Adds / removes options like -w , verity, verification ... depending on what the user has chosen
  • adds --skip-reboot to the last step of image update to make sure the phone does not boot to system
  • Flashes the patch
  • - Reboots to system

Here's what got generated with March update for my p7p
I redacted the device ID
I had chosen to flash to inactive slot.

Code:
chcp 437
@ECHO OFF
:: This is a generated file by PixelFlasher v4.8.0.0

PATH=%PATH%;"%SYSTEMROOT%\System32"
echo Switching active slot to the other ...
"C:\Android\platform-tools\fastboot.exe" -s REDACT --set-active=other
"C:\Android\platform-tools\fastboot.exe" -s REDACT --verbose  flash bootloader bootloader-cheetah-cloudripper-1.0-9618366.img
"C:\Android\platform-tools\fastboot.exe" -s REDACT reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\Android\platform-tools\fastboot.exe" -s REDACT --verbose  flash radio radio-cheetah-g5300g-221229-230210-b-9589366.img
"C:\Android\platform-tools\fastboot.exe" -s REDACT reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\Android\platform-tools\fastboot.exe" -s REDACT --verbose  --skip-reboot update image-cheetah-tq2a.230305.008.c1.zip
echo rebooting to bootloader ...
"C:\Android\platform-tools\fastboot.exe" -s REDACT reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul
echo flashing pf_boot ...
"C:\Android\platform-tools\fastboot.exe" -s REDACT --verbose  flash init_boot pf_boot.img
echo rebooting to system ...
"C:\Android\platform-tools\fastboot.exe" -s REDACT reboot
 

roirraW "edor" ehT

Forum Moderator
Staff member
The PATH=%PATH%;"%SYSTEMROOT%\System32" comes from the flash_all.bat script by Google, it is on the first line after the comments.
This is probably due to fastboot.exe having dependencies on windows binaries which are in system32,.
Typically the PATH environment would already have system32 in the path, the script is making sure it has by adding it just in case the user env settings has been modified intentionally or unintentionally.
It's just a safety measure added by Google.
Ah, thank you! Indeed, I verified in a virtual PC that System32 is already usually in the path, but it makes sense for the script to make sure.

I removed my optional advice from my post.

Yes, this is how early versions of PF used to do, by repacking the patched boot into the firmware and flashing.
It no longer does that because that is slow and unnecessary.
What it currently does is:
  • it builds a modified flash_all script (called flash-phone.bat)
  • Uses full path to Android platform tools, this assures to pick up the correct fastboot instead of some random one in the system path
  • Specifies the device ID, this assures to apply to the correct device, if multiple devices happen to be connected to the PC
  • Adds / removes options like -w , verity, verification ... depending on what the user has chosen
  • adds --skip-reboot to the last step of image update to make sure the phone does not boot to system
  • Flashes the patch
  • - Reboots to system

Here's what got generated with March update for my p7p
I redacted the device ID
I had chosen to flash to inactive slot.

Code:
chcp 437
@ECHO OFF
:: This is a generated file by PixelFlasher v4.8.0.0

PATH=%PATH%;"%SYSTEMROOT%\System32"
echo Switching active slot to the other ...
"C:\Android\platform-tools\fastboot.exe" -s REDACT --set-active=other
"C:\Android\platform-tools\fastboot.exe" -s REDACT --verbose  flash bootloader bootloader-cheetah-cloudripper-1.0-9618366.img
"C:\Android\platform-tools\fastboot.exe" -s REDACT reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\Android\platform-tools\fastboot.exe" -s REDACT --verbose  flash radio radio-cheetah-g5300g-221229-230210-b-9589366.img
"C:\Android\platform-tools\fastboot.exe" -s REDACT reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\Android\platform-tools\fastboot.exe" -s REDACT --verbose  --skip-reboot update image-cheetah-tq2a.230305.008.c1.zip
echo rebooting to bootloader ...
"C:\Android\platform-tools\fastboot.exe" -s REDACT reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul
echo flashing pf_boot ...
"C:\Android\platform-tools\fastboot.exe" -s REDACT --verbose  flash init_boot pf_boot.img
echo rebooting to system ...
"C:\Android\platform-tools\fastboot.exe" -s REDACT reboot
Interesting, and thank you!
 

roirraW "edor" ehT

Forum Moderator
Staff member
LOL, Google can't quite get the https://www.google.com/android/beta page correct. A few minutes ago, they changed it to QPR2 in both places, now they're both QPR3, and they should change only the one on the left to QPR2.

Edit: I was reading it wrong, anyway. Was thinking the left side was for QPR2 Stable. :D

1678903924967.png
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
5,155
6,028
Google Nexus 5
Huawei Nexus 6P

roirraW "edor" ehT

Forum Moderator
Staff member

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.

Pixel 7 Procheetah-t3b1.230224.005-factory-08d6844d.zip08d6844d038fe0f104121c8d5967328d5f12817bd68e9cea80f74a12965f52ee

Pixel 7 Procheetah-ota-t3b1.230224.005-b9ea6269.zipb9ea62698c96f7d66e74c0104410388436ad1df00ac88c5c76c3134610ca82e9

Release notes​

bookmark
Beta 1
Release dateMarch 15, 2023
BuildT3B1.230224.005
Security patch levelMarch 2023
Google Play services23.08.15

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 1​

You can install Android 13 QPR3 Beta 1 on any of the following Google Pixel devices:
  • Pixel 4a and 4a (5G)
  • Pixel 5 and 5a
  • Pixel 6 and 6 Pro
  • Pixel 6a
  • Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.

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.
  • 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.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.

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.

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.
 

kiekan

Senior Member
Feb 10, 2009
355
141
Downers Grove, IL
Just flashed t3b1.230224.005 using the factory image. Successfully rooted and got AOSP mods working.

Does anyone else notice that screen looks significantly darker when using the adaptive display color setting?
 
  • Like
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    QPR 3 Beta 3.1:


    7
    QPR 3 Beta 3.2:


    4
    This build resolved an issue I was having where WIRED ear pods would NOT work properly. 👍
    1
    I still see the proposal to update to android 14 in the update page
    1
    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.

    Yep I can corroborate, we're still in the clear for bypassing. :)

    v2s35bO.png

    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. 😜🤣

    I accidentally wiped my phone last week, and I just set up the Chase app yesterday. I found it very interesting that I was even able to set up the fingerprint reader with the app while rooted (Chase in DenyList, as usual) and on Displax' USNF 2.40 Mod 1.2.
  • 19

    Pixel 7 Pro [Cheetah] QPR Betas


    QPR stands for "Quarterly Platform Release". Android 13 QPR2 went final in March 2023. See main thread here for final/non-beta releases.

    You can officially opt into the Android Beta Program there, or use the factory image or OTA below. You can no longer manually opt into the QPR3 Beta program - only the Android 14 Beta is offered to opt into:
    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:

    and leads to:
    the Enroll in Android 13 Beta for Pixel button there still leads to:
    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.




    I don't plan on testing Betas of any sort, but feel free to use this thread for everything about the QPR Betas or major Android version betas for the Pixel 7 Pro. I'll update the information in the OP when necessary. See Post #2 in my main thread for general information (Unlocking Bootloader / Rooting / Updating | SafetyNet working again | ADB/Fastboot & Windows USB Drivers) but ask questions or make observations about all betas in this thread, please.

    Once a QPR or major Android version goes final, I'll take those discussions to my main thread.
    8
    The Beta also introduces support for some new carriers, some of which are the first ones for some countries (Portugal, Lithuania, Finland, Estonia), this means 5G working out of the box aswell as proper LTE Aggregation combinations (VoLTE depends on another configuration so that could take some time):

    pt_vf​
    pt_meo​
    pt_nos​
    ca_tbaytel​
    uk_tesco​
    lt_telia​
    fi_telia​
    ee_telia​
    uk_sky​
    8
    QPR 3 Beta 3.1:


    7
    QPR2 Beta 3
    Pixel 7 Procheetah-t2b3.230109.002-factory-9b7903db.zip9b7903dbcf23bb41d1e3d86ed16eb5cd4309187c0def3aff148410dc34fcda5d

    https://developer.android.com/about/versions/13/release-notes#beta3

    Release notes​

    bookmark
    Beta 3Beta 2.1Beta 2Beta 1
    Release dateFebruary 1, 2023
    BuildT2B3.230109.002
    Security patch levelJanuary 2023
    Google Play services23.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:
    • Pixel 4a and 4a (5G)
    • Pixel 5 and 5a
    • Pixel 6 and 6 Pro
    • Pixel 6a
    • Pixel 7 and 7 Pro
    See Get Android 13 QPR beta builds for details on how to get started.

    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.
    • 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.
    To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.

    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.
    7
    Beta 2.1:
    Normal system images: Use https://flash.android.com/preview/tm-qpr2-beta2.1
    Pixel 7 Procheetah-t2b2.221216.008-factory-36873c04.zip36873c042e0eacb4fa634afe053444c4885c10c38565bcb01518750dc8030610