Lets hope it will arrive soon cuz im excited to see how bad my battery is
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]
- Thread starter roirraW "edor" ehT
- Start date
| Pixel 6 Pro | raven-t1b2.220916.004-factory-b4c16abf.zip | b4c16abfc3a5237ac6412b650705ee255964a7b5b5a9a684eb22bbb678196c1d |
| Pixel 6 Pro | raven-ota-t1b2.220916.004-159ff0cd.zip | 159ff0cd49711b694905d1a297a2b8ee9ac6fde262dbd48b1332b3a9b1367bdc |
Last edited:
Release notes
Beta 2
Release date October 5, 2022 Build T1B2.220916.004 Security patch level October 2022 Google Play services 22.26.15 About Android 13 QPR1
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 QPR1 builds on the updates in the Android 13 release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR1 Beta 2
You can install Android 13 QPR1 Beta 2 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
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 QPR1. 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 open issues
See top open issues for the latest list of top open issues that have been reported.
Previous beta releases
Android 13 QPR1 Beta 1
Top resolved issues
The following issues have been resolved in Android 13 QPR1 Beta 1:
Developer-reported issues
- Fixed an issue for some devices that mistakenly caused a user's emergency contact to be dialed from the lock screen when the device was in their pocket. (Issue #233159557)
Other resolved issues
- Fixed various issues for Pixel 6a devices that made it difficult for users to unlock their device or to set up Fingerprint Unlock.
- Fixed an issue that caused the system UI to crash in certain cases, such as gesturing from the edge of the screen to go back.
- Fixed an issue that sometimes caused the 5G icon to be displayed instead of the 5G UW icon, even when the affected device was already successfully connected to a 5G UW network.
Android 13 QPR1 Beta 2 is here for Google Pixel smartphones
I had issues with the lock screen on beta one, where the screen wouldn't respond when locked, has this been resolved do use no?
fil3s
Senior Member
I can't seem to get root 
I downloaded the factory image and got the boot.img
Tried to boot it, got stuck on the google logo and rebooted. Any ideas?
I downloaded the factory image and got the boot.imgTried to boot it, got stuck on the google logo and rebooted. Any ideas?
Were you on Beta 1 rooted before that? If so, did you disable all Magisk Modules before updating? Try Safe Mode after, if you hadn't disabled all Magisk Modules before? I alwaysI can't seem to get root
Tried to boot it, got stuck on the google logo and rebooted. Any ideas?
fastboot boot (rooted)boot.img and then use Magisk's direct install method to patch the already flashed stock boot.img. I'm not on any Betas, though, so this is just in general.
fil3s
Senior Member
I would dirty flash the Beta 2 factory image, or just flash the stock unrooted boot.img and see if that at least boots, but if it doesn't, then definitely the dirty flash.
fil3s
Senior Member
I just tried to boot the magisk patched boot.img again by deleting the old image and patching a fresh boot.img, then ran
Code:
fastboot boot "magiskboot.img"If the full dirty flash doesn't help, I think I'm out of ideas other than starting completely from scratch, and maybe even start with the Official Google Android Flash Tool and then flash the Beta 2 (assuming the Official Google Android Flash Tool doesn't offer Beta 2 - I don't know if it does or not).
fil3s
Senior Member
Just to be sure, I can downgrade to official 13 right ? I also had problems charging this morning
Yes, absolutely. You definitely want to wipe the phone if you do though, and if you're going to do that anyway, then definitely use the Official Google Android Flash Tool since it fixes weird issues that the factory image doesn't. I used it once to fix my phone when I had the same problem (back on Android 12 Stable, sometime in the last year).
fil3s
Senior Member
I just downgraded to public a13. I was looking in my downloads folder on my PC, checking dates and times, and I think I may have tried to boot the public boot image 
I am lucky I booted the magisk image. Sorry for the confusion.
I am lucky I booted the magisk image. Sorry for the confusion.
I'm glad you figured out the probably why. It happens to everyone from time to time.I just downgraded to public a13. I was looking in my downloads folder on my PC, checking dates and times, and I think I may have tried to boot the public boot image
I am lucky I booted the magisk image. Sorry for the confusion.
caitsith810
Senior Member
Just flashed QPR Beta 2 to see if Wavelet worked. It seems like it's working fine now.
Hopefully the other apps folks had issues with, works as well. Time to try out this beta.
-edit-
Worked for a little while, now its not detecting my headphones again.
Hopefully the other apps folks had issues with, works as well. Time to try out this beta.
-edit-
Worked for a little while, now its not detecting my headphones again.
Anyone having trouble with outgoing calls after QPR2? Can get incoming call but getting immediately call ended with outgoing calls.
I'm in unsupported country so no VOLTE/VOWIFI
I'm in unsupported country so no VOLTE/VOWIFI
Top Liked Posts
-
There are no posts matching your filters.
-
11Pixel 6 Pro [Raven] QPR Betas
QPR stands for "Quarterly Platform Release". Android 13 QPR3 went final in June 2023. See main thread here for final/non-beta releases.
From my Pixel 7 QPR Beta thread (and adjusting the OP with the same information):
You canofficially opt into the Android Beta Program there, oruse 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 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:Get Android 13 | Android Developers
Get an Android 13 on your eligible device.
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.
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 6 Pro. I'll update the information in the OP when necessary. See Post #1 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.10Yet another Beta of 13, Beta 3.3:
Google rolls out Android 13 Beta 3.3 with a bunch of bug fixes
Google is rolling out Android 13 Beta 3.3 to...www.xda-developers.com
8All, this is not a thread for opinions about the Pixel 6/Pro in general, nor is it a thread made for rants. Opinions specifically about Android 13 are fine. I know there have been a few posts that have nothing specific to do with Android 13 and I've let it go. If anyone wants to make posts that don't address anything specifically about Android 13, there are many, many threads in this section where that has taken place.
I know, because I used to read every post in this section but now I avoid the threads that contain those kinds of posts, and I'd like to not see them here in this thread. Any further posts of those types will be deleted as off-topic.6
Good spot. Seeing as how that's now intended behaviour, I guess wiping and disabling verification is all our best moves from here.I think Magisk removed the need to pass the vbmeta disable verity/verification flag with Canary 24303. Here's a quote related to a kernel issue from yujincheng08 (LoveSy):
"Let me clarify the things.
Magisk was used to modify the fstab to inject Magisk components, and in the meantime, Magisk stipped avb_key and avb flags for all partitions. So, that 24300 works is just a side effect and has no insurance.
Now Magisk changed its way of injecting Magisk components, and it will no longer modify the fstab, and the side effect was thus gone together with the refactorization. Some configurations that rely on the fact that Magisk will strip those verification flags will no longer work, and that's expected. Users should disable the verification themselves since they are expected to have unlocked bootloaders."
This all relates to problems with custom kernels and Magisk, but may have further implications for us. Check out more in the issue here..
Some customized kernels are incompatible with Magisk 24303+ that no longer strips verification flags of early mount partitions · Issue #5777 · topjohnwu/Magisk
Device: Pixel 6 Pro Android version: 12.1...
github.com
I'll take this moment to suggest investing in Swift Backup and setting up an automatic backup that runs periodically, so long as you have root it makes wiping pretty much a non-issue.
