General Android 13 QPR3 went final in June 2023-opt-out now to get the OTA without wiping - Pixel 6 Pro [Raven] - [thread also for future Android QPR Betas]

[acwcanada]

Does QPR3 Beta fix the VoLTE vulnerability for P6Pro?

It contains the March Security Update, so yes it should fix those.

 

[roirraW "edor" ehT]

Android 13 QPR3 Beta software survey

Hi Beta users, We'd like your feedback on the latest Beta version of Android 13 on your Pixel device. This *anonymous* survey should take you about 5-10 minutes to complete. Please only fill out this survey if your Pixel device is running Android 13 QPR3 Beta build. You can verify this by...

docs.google.com

 

[Sui77]

Just updated to QPR3 and rooted with latest Canary...

Sadly I have ROOT, but Magisk does not execute any modules.

Any idea?

 

[furkanosman]

Just updated to QPR3 and rooted with latest Canary...

Sadly I have ROOT, but Magisk does not execute any modules.

Any idea?

Same for me

 

[Sui77]

Shiiiit, so it was not just bad luck for me.
Hopefully there will be a fix soon

 

[Lughnasadh]

Just updated to QPR3 and rooted with latest Canary...

Sadly I have ROOT, but Magisk does not execute any modules.

Any idea?

You should be using either Stable 25.2 or Canary 25206. Canary 25210 broke module loading.

 

[ctankep]

Just updated to QPR3 and rooted with latest Canary...

Sadly I have ROOT, but Magisk does not execute any modules.

Any idea?

You should be using either Stable 25.2 or Canary 25206. Canary 25210 broke module loading.

Can confirm this FWIW!
Running QPR3 Beta 1 with Magisk 25.2 and have root with AOSP Mods, LSPosed running no problems.

 

[Sui77]

Thx, I'm on 25206 now add all is working

 

[Lughnasadh]

Looks like the problems with patching the boot image on the Pixel 6 series when on the QPR3 beta(s) (and other betas) and A14 DPs may have been fixed. Patching the Pixel 7 boot.img may no longer be needed when the next Canary is released.

Force ramdisk format to lz4_legacy for v4 by vvb2060 · Pull Request #6775 · topjohnwu/Magisk

Seems like Google doesn't want to fix this.

github.com

 

[roirraW "edor" ehT]

March 29, 2023:
Android 13 QPR3 Beta 2

Android 13 | Android Developers

<!-- hide description -->

developer.android.com

Release notes​

bookmark
Beta 2Beta 1

Release date	March 29, 2023
Build	T3B2.230316.003
Security patch level	March 2023
Google Play services	23.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 2​

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

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.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developer.android.com

Pixel 6 Pro

raven-t3b2.230316.003-factory-f0292a27.zip

f0292a27135f660dc20f091b044a8ec997a47758e0365ff7721edbec2cb3c82e

64-bit-only images​

Pixel 6 Pro

raven_64-t3b2.230316.003-factory-fbfbb3b5.zip

fbfbb3b515a957dbc77a723b6e66fef17a694cc5fc8ad3506674ade60783f017

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developer.android.com

Pixel 6 Pro

raven-ota-t3b2.230316.003-2f73a8ea.zip

2f73a8eaae652c70af4fc16ac5d414847b6041d68ff1a19cff0cd74ef6da956f

 

[acwcanada]

March 29, 2023:
Android 13 QPR3 Beta 2

Android 13 | Android Developers

<!-- hide description -->

developer.android.com

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developer.android.com

Pixel 6 Pro

raven-t3b2.230316.003-factory-f0292a27.zip

f0292a27135f660dc20f091b044a8ec997a47758e0365ff7721edbec2cb3c82e

64-bit-only images​

Pixel 6 Pro

raven_64-t3b2.230316.003-factory-fbfbb3b5.zip

fbfbb3b515a957dbc77a723b6e66fef17a694cc5fc8ad3506674ade60783f017

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developer.android.com

Pixel 6 Pro

raven-ota-t3b2.230316.003-2f73a8ea.zip

2f73a8eaae652c70af4fc16ac5d414847b6041d68ff1a19cff0cd74ef6da956f

Any idea if we still have to use the P7P boot.image to root?

 

[roirraW "edor" ehT]

Any idea if we still have to use the P7P boot.image to root?

That is the million-dollar question. Well, okay, maybe $1 question. I don't have time to chance betas myself these days, but hopefully someone else will answer. If you or anyone find out for sure, please let us know.

@Lughnasadh's post quoted below is the best answer so far:

Looks like the problems with patching the boot image on the Pixel 6 series when on the QPR3 beta(s) (and other betas) and A14 DPs may have been fixed. Patching the Pixel 7 boot.img may no longer be needed when the next Canary is released.

Force ramdisk format to lz4_legacy for v4 by vvb2060 · Pull Request #6775 · topjohnwu/Magisk

Seems like Google doesn't want to fix this.

github.com

 

[BROKEN1981]

Any idea if we still have to use the P7P boot.image to root?

seems like it. using pixel Flasher and no root.
edit, used pixel 7 pro boot image. got root

 

[acwcanada]

That is the million-dollar question. Well, okay, maybe $1 question. I don't have time to chance betas myself these days, but hopefully someone else will answer. If you or anyone find out for sure, please let us know.

@Lughnasadh's post quoted below is the best answer so far:

The Magisk Canary 25210 has not been updated for quite sometime so it seems fix still not yet be included, we might still have to patch the P7 boot images to root the P6 series.

 

[acwcanada]

seems like it. using pixel Flasher and no root.
edit, used pixel 7 pro boot image. got root

Thanks for the info.

 

[acwcanada]

Just update it with the patched P7P boot image, got root and everything seems run smoothly. The only thing which is a little bit strange is that it is still have the March 5 Security, I don't think beta 3 will be available in April or at least has to wait till end of April, so the beta 2 wouldn't have the April Security Update for most part of April.

 

[shadyrexman]

Hey guys, I used both p6p and p7p boot.img and fastboot boot and can't root it in T3B2 with Canary 25210 on my p6p. any suggestions? Thank you

 

[Lughnasadh]

Just update it with the patched P7P boot image, got root and everything seems run smoothly. The only thing which is a little bit strange is that it is still have the March 5 Security, I don't think beta 3 will be available in April or at least has to wait till end of April, so the beta 2 wouldn't have the April Security Update for most part of April.

The April security bulletin hasn't been released yet so it's normal for it to be on the March security update. If they continue to release QPR Beta builds (originally they said only through March, but now that seems to have changed with the new process of releasing the QPR Beta builds and I think they removed reference to "through March" in the F.A.Q. section), QPR3 Beta 3 should be released early to mid April with the April security patch.

EDIT: Seems as if the QPR Beta program will end when the first A14 Betas are released as originally scheduled. See my reply to myself below.

 

[acwcanada]

Hey guys, I used both p6p and p7p boot.img and fastboot boot and can't root it in T3B2 with Canary 25210, any suggestions? Thank you

Go back to 25206 or use Magisk Delta 25210

 

[Lughnasadh]

The April security bulletin hasn't been released yet so it's normal for it to be on the March security update. If they continue to release QPR Beta builds (originally they said only through March, but now that seems to have changed with the new process of releasing the QPR Beta builds and I think they removed reference to "through March" in the F.A.Q. section), QPR3 Beta 3 should be released early to mid April with the April security patch.

Although maybe the "through March" still holds as they have said this:

Android 13 QPR3 Beta will continue until Android 14 Beta kicks off. If you’re participating in QPR3 beta, you will automatically receive an over-the-air (OTA) update to Android 14 Beta 1 when it becomes available. No separate program opt-in is required. We’ll provide more information as we get closer to the Android 14 beta release.

Since the first A14 Beta is scheduled to be released in April, it does sound like the A13 QPR Beta program may end this month as they originally stated.