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

[nitin_ko]

With Latest beta update in Feb, mobile data connection has become a big pain. I use dual Sims and both don't connect to data. Started facing this issue after latest beta update. Anyone else facing this issue? Any fix ? reverting to stock is not possible since i will have to wipe my device and i can't afford to delete entire storage.

 

[roirraW "edor" ehT]

February 9, 2023:
Android 13 QPR2 Beta 3.1 (February 2023)

Release notes | Android Developers

Release notes and known issues for the latest Android 13 builds.

developer.android.com

• Android Developers
• Platform
• Releases

Release notes​

bookmark
Beta 3.1Beta 3Beta 2.1Beta 2Beta 1

Release date	February 9, 2023
Build	T2B3.230109.004
Security patch level	February 2023
Google Play services	23.03.13

Android 13 QPR2 Beta 3.1 (February 2023)
This minor update to Android 13 QPR2 Beta 3 includes the following fixes:

• Fixed an issue in the system Bluetooth module that could have allowed for possible out-of-bounds writes due to memory corruption. (Issue #259630761)
• Fixed an issue where some Romanian translations were missing from the system image.

If you're already running a beta build, you'll automatically receive an over-the-air (OTA) update to Beta 3.1.
Note: Other known issues listed for the Beta 3 release still apply to Beta 3.1.

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

You can install Android 13 QPR2 Beta 3.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 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.

Factory images for Google Pixel | Android Developers

Instructions for downloading and installing QPR Beta system images for Pixel devices

developer.android.com

Pixel 7 Pro

cheetah-t2b3.230109.004-factory-004d470e.zip

004d470e960d6240ebcf48d713f2b9a2c0b63bc307532216c85c9e48a92fce19

OTA images for Google Pixel | Android Developers

Instructions for downloading and installing QPR beta system images for Pixel devices

developer.android.com

Pixel 7 Pro

cheetah-ota-t2b3.230109.004-1fc7be52.zip

1fc7be522cf1f0757f6bd4f2b9b5fbc2ab827580aad62502870d063795adf507

 

[Lughnasadh]

Yes, it has the February security update.

 

[Dave_247]

Google seem to have done something funky with the new version 34 of platform tools, as it seems to miss booting into fastbootd for the final flashing step and instead try to flash it without it, but will fail and cause bootloops due to missing the critical files. It was driving me nuts trying to figure out why it was failing as I've just been using the Android Flash Tool website, but for some reason that only has 3.0 and not the slightly newer 3.1

extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.000s]
Checking 'version-bootloader'                      OKAY [  0.000s]
Checking 'version-baseband'                        OKAY [  0.000s]
Setting current slot to 'b'                        OKAY [  0.120s]
extracting boot.img (64 MB) to disk... took 0.191s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB)                        OKAY [  1.465s]
Writing 'boot_b'                                   OKAY [  0.257s]
extracting init_boot.img (8 MB) to disk... took 0.025s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB)                    OKAY [  0.180s]
Writing 'init_boot_b'                              OKAY [  0.032s]
extracting dtbo.img (16 MB) to disk... took 0.095s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB)                        OKAY [  0.364s]
Writing 'dtbo_b'                                   OKAY [  0.057s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.011s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB)                        OKAY [  0.024s]
Writing 'pvmfw_b'                                  OKAY [  0.007s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB)                         OKAY [  0.001s]
Writing 'vbmeta_b'                                 OKAY [  0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.003s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.001s]
Writing 'vbmeta_system_b'                          OKAY [  0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB)                   OKAY [  0.001s]
Writing 'vbmeta_vendor_b'                          OKAY [  0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.255s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB)                 OKAY [  1.466s]
Writing 'vendor_boot_b'                            OKAY [  0.247s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.169s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB)          OKAY [  1.491s]
Writing 'vendor_kernel_boot_b'                     OKAY [  0.269s]
extracting super_empty.img (0 MB) to disk... took 0.002s
extracting product.img (2870 MB) to disk... took 15.960s
extracting system.img (827 MB) to disk... took 4.945s
extracting system_dlkm.img (0 MB) to disk... took 0.001s
extracting system_ext.img (361 MB) to disk... took 2.279s
extracting system_other.img (25 MB) to disk... took 0.181s
extracting vendor.img (644 MB) to disk... took 5.272s
extracting vendor_dlkm.img (41 MB) to disk... took 0.122s
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB)            FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed

 

[sh0nda]

Updated pixel 7 pro (unlocked) to latest beta and dual esim is still not working. Any advice, thank you.

 

[EtherealRemnant]

Updated pixel 7 pro (unlocked) to latest beta and dual esim is still not working. Any advice, thank you.

Google hasn't enabled it yet.

 

[gogoffm]

With Latest beta update in Feb, mobile data connection has become a big pain. I use dual Sims and both don't connect to data. Started facing this issue after latest beta update. Anyone else facing this issue? Any fix ? reverting to stock is not possible since i will have to wipe my device and i can't afford to delete entire storage.

Same here. Using it in Germany with T-mobile (Esim) and Vodafone (physical sim) , it's a mess.

 

[anqry]

Same here. Using it in Germany with T-mobile (Esim) and Vodafone (physical sim) , it's a mess.

Installs beta software on a daily driver, turns out some functions are broken.

 

[Josh]

Same here. Using it in Germany with T-mobile (Esim) and Vodafone (physical sim) , it's a mess.

Do you have 5g connection on T mobile?
I'm also on T mobile but dont have 5G connection (Croatia) unlocked phone with root.
Dirty flashed global February build over T mobile build .
I know that I can flash some magisk modules and install some app to make it possible to have 5G but has some network issues as I'm not available when someone call me(got sms that someone called me)
.After reset network settings seems issues gone and lost 5G connection.

 

[gogoffm]

Do you have 5g connection on T mobile?
I'm also on T mobile but dont have 5G connection (Croatia) unlocked phone with root.
Dirty flashed global February build over T mobile build .
I know that I can flash some magisk modules and install some app to make it possible to have 5G but has some network issues as I'm not available when someone call me(got sms that someone called me)
.After reset network settings seems issues gone and lost 5G connection.

Yes, 5G on both sims. Is it possible to flash the Stock built over the beta built through android flash?

 

[WillyRy]

Is anyone have Google messenger issues. It constantly saying message not delivered. Any help would be greatly appreciated.

Yes, I have had that, too.
I did a support bug report with a log to them as well.
VZW: sim & eSIM

 

[EtherealRemnant]

Gotta say... The battery has been quite good on this build.

 

[letmedanz]

Anyone facing issue with gpay on beta?
App opens fine, all functions seem to be working ok, however payments don't go through 4 out of 5 times.
It just says 'oops something went wrong'.
Seen these issues with QR merchant payments and saved utilities, both on debit and credit

 

[Lughnasadh]

QPR2 Beta 3.2 is out. Very minor update unless you are on Jio.

• Fixed issues that sometimes caused the screen on some devices to flash green or display other visual artifacts. (Issue #260941279, Issue #256052135)
• Jio 5G network is now enabled for Pixel 6 and 7 series devices

 

[roirraW "edor" ehT]

QPR2 Beta 3.2:

Factory images for Google Pixel | Android Developers

Instructions for downloading and installing QPR Beta system images for Pixel devices

developer.android.com

Pixel 7 Pro

cheetah-t2b3.230109.006.a1-factory-117742bc.zip

117742bc5147f87f1b99337b4ba43fb5fcdbfd1277a80c87d0d0b17d71baa8d7

OTA images for Google Pixel | Android Developers

Instructions for downloading and installing QPR beta system images for Pixel devices

developer.android.com

Pixel 7 Pro

cheetah-ota-t2b3.230109.006.a1-e7cf02d7.zip

e7cf02d73032f7e96dec3893e2a54ea89d460a2257abd3680a6ab443be2a2c05

Release notes | Android Developers

Release notes and known issues for the latest Android 13 builds.

developer.android.com

Beta 3.2Beta 3.1Beta 3Beta 2.1Beta 2Beta 1

Release date	February 22, 2023
Build	T2B3.230109.009, T2B3.230109.006.A1 (Pixel 7 Pro only)
Security patch level	February 2023
Google Play services	23.03.13

Android 13 QPR2 Beta 3.2 (February 2023)
This minor update to Android 13 QPR2 Beta 3 includes the following fixes:

• Fixed issues that sometimes caused the screen on some devices to flash green or display other visual artifacts. (Issue #260941279, Issue #256052135)
• Jio 5G network is now enabled for Pixel 6 and 7 series devices.

If you're already running a beta build, you'll automatically receive an over-the-air (OTA) update to Beta 3.2.
Note: Other known issues listed for the Beta 3 release still apply to Beta 3.2.
Android 13 QPR2 Beta 3.1 (February 2023)
This minor update to Android 13 QPR2 Beta 3 includes the following fixes:

• Fixed an issue in the system Bluetooth module that could have allowed for possible out-of-bounds writes due to memory corruption. (Issue #259630761)
• Fixed an issue where some Romanian translations were missing from the system image.

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.2​

You can install Android 13 QPR2 Beta 3.2 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.

 

[Lughnasadh]

https://twitter.com/i/web/status/1634291746598207488

 

[LLStarks]

QPR3 wasn't supposed to happen. I wonder what changed.

 

[Lughnasadh]

https://twitter.com/i/web/status/1634291746598207488

Now I'm wondering if the change in the beta release process is the reason why the stable March build was delayed.

 

[roirraW "edor" ehT]

For anyone who doesn't notice Google's official announcement in those above, and what to do if you're on the QPR2 Beta 3.x and want to be on stable:
https://www.reddit.com/r/android_beta/comments/11nz32q

Hi Beta users,

With the release of our final Android 13 QPR2 Beta update a few weeks ago, we are now preparing for our next Beta Program cycle that covers our Android 13 June release (QPR3). Android 13 QPR3 Beta 1 will kick off the week of March 13th. If you take no action and remain enrolled in the Beta Program, you will automatically receive Android 13 QPR3 Beta 1 starting next week.

We are changing our beta release process - to receive the upcoming March QPR2 public stable release, devices currently enrolled in Beta will need to first opt out of the program. Devices that remain enrolled in the Beta Program will receive Android 13 QPR3 Beta 1.

If you prefer to exit the Beta Program and receive the final public March QPR2 update without the need to wipe your data, please do one of the following:

• Opt out of the program before March 13th, ignore/don’t apply the downgrade OTA update, and wait for the final public stable release of the March Feature Drop (QPR2) releasing this month. Opting out will not cause a data wipe as long as you don’t apply the downgrade OTA. Note: If you want to immediately return to the latest public version, you can apply the downgrade OTA which will require a data wipe per usual program guidelines.
• If you receive the Android 13 QPR3 Beta 1 update, don’t install the update. Instead, first opt out of the program, ignore/don’t apply the downgrade OTA update, and wait for the official March public release. Note: If you opt-out of the program after installing the QPR3 beta 1 update, all user data on the device will get wiped per usual program guidelines.

We will continue to post updates and information on the upcoming Android 13 QPR3 Beta here in this community.

 

[Markeee]

Just to confirm, I'm safe to click leave beta today before the release of the final next week and will still be able to install the final when it drops without getting wiped as it says in the below picture below?