General Android 13 QPR1 Beta 1 (September 8, 2022 - t1b1.220819.006 for P6P) is available via Opt-In, OTA zip, or (full) firmware image zip

Search This thread

Ghisy

Senior Member
Mar 27, 2010
1,783
600
Appears so...

Beta 4: radio-raven-g5123b-102852-220704-b-8796503
Beta 4.1: radio-raven-g5123b-102852-220713-b-8828409
Indeed! In case someone needs it, I'm uploading the latest radio from Beta 4.1 (see attached file) for the P6P.
 

Attachments

  • Android_13_beta_4.1_radio-raven-g5123b-102852-220713-b-8828409.img
    80.8 MB · Views: 26

nahsha

Senior Member
May 10, 2007
563
55
The p6p is a good phone but the batt on a12 is pretty bad even with a custom kernel and with the refresh rate set to 60hz! Hope a13 is better..
 
  • Like
Reactions: rester555

Izy

Senior Member
The p6p is a good phone but the batt on a12 is pretty bad even with a custom kernel and with the refresh rate set to 60hz! Hope a13 is better..
if im correct when they tested it the battery was worse at 60hz than at 120hz

Pixel-6-Pro-power-consumption-AnandTech-image-1.jpeg
 

Lughnasadh

Senior Member
Mar 23, 2015
3,905
4,179
Google Nexus 5
Huawei Nexus 6P
The August patch for Android 13? I doubt it. For Android 12, yes, as usual should be first Monday of the month, barring holidays and unforseen (or forseen) circumstances.
I also suspect they will release the August update for Android 12 today and maybe even release the Android 13 source code to AOSP today (or very soon). Would think the Android 13 stable factory images etc. to be available a week or two after they release the source code.

Last year they released the last Android 11 monthly update and the Android 12 source code to AOSP on the first Monday of October, I believe. They released the factory images for Android 12 a couple of weeks later. Would think maybe the same kind of schedule, except in August this time.

We'll see... 🙃
 
  • Like
Reactions: roirraW "edor" ehT

Lughnasadh

Senior Member
Mar 23, 2015
3,905
4,179
Google Nexus 5
Huawei Nexus 6P
I also suspect they will release the August update for Android 12 today and maybe even release the Android 13 source code to AOSP today (or very soon). Would think the Android 13 stable factory images etc. to be available a week or two after they release the source code.

Last year they released the last Android 11 monthly update and the Android 12 source code to AOSP on the first Monday of October, I believe. They released the factory images for Android 12 a couple of weeks later. Would think maybe the same kind of schedule, except in August this time.

We'll see... 🙃
And there's this...

 

Ghisy

Senior Member
Mar 27, 2010
1,783
600
I believe Android 13 stable will be released in September. Android 12 was October last year, probably because of remote work and stuff.

September is the usual time frame for new Android releases.
 

Lughnasadh

Senior Member
Mar 23, 2015
3,905
4,179
Google Nexus 5
Huawei Nexus 6P
Samsung is starting to roll out the August security update to more of its devices so it's possible we get the update soon. But they also originally started pushing the update to some of its device on July 28, so who knows. Lately Samsung has been a few days ahead of Google in rolling out monthly security updates.

May not mean anything...
 
Last edited:
  • Like
Reactions: roirraW "edor" ehT

Lughnasadh

Senior Member
Mar 23, 2015
3,905
4,179
Google Nexus 5
Huawei Nexus 6P
Samsung is starting to roll out the August security update to more of its devices so it's possible we get the update soon. But they also originally started pushing the update to some of its device on July 28, so who knows. Lately Samsung has been a few days ahead of Google in rolling out monthly security updates.

May not mean anything...
" Google did share today that the “August 2022 update for all supported Pixel devices will begin rollout in the coming weeks."

Also...

"Google’s three latest phones are getting a “Fix for GPS location failure under certain conditions.” For the Pixel 6 and 6 Pro, this is still just the July security patch, while the 6a is likely still on the June patch level."

Guess that explains the surprise new July builds, in part at least...

 
Last edited:
  • Like
Reactions: roirraW "edor" ehT

NippleSauce

Senior Member
Jun 23, 2013
461
303
"Google’s three latest phones are getting a “Fix for GPS location failure under certain conditions.” For the Pixel 6 and 6 Pro, this is still just the July security patch, while the 6a is likely still on the June patch level."

Guess that explains the surprise new July builds, in part at least...
Non-important statement incoming - but thank jeebus for that fix, haha. I never had a GPS issue in GMaps on the previous A13Beta builds, however, the app that I use to buy gas couldn't determine my location and wouldn't allow me to make gas purchases. So, this was certainly a beneficial change for me.
 

cd993

Senior Member
May 8, 2009
3,515
1,241
London
Samsung Galaxy S21 Ultra
Haven't seen anyone get it working. JamesDSP does work, however.
Thanks, yeah was curious about that. Could be a good alternative.
Does Wavelet work the same as Viper4android, or is it more just a non-root app that may cause excessive drain processing the audio?

(slight off-topic, but relevant given intentions of finding an efficient audio processing equaliser compatible with A13)
 

Top Liked Posts

  • 2
    How to enable the "battery health" thing in QPR1 that is on twitter?🤔
    This?

    I assume it will come in the next Beta, or one of the next Betas.
    2
    This?

    I assume it will come in the next Beta, or one of the next Betas.
    Lets hope it will arrive soon cuz im excited to see how bad my battery is😂
  • 3
    "Android 13 QPR1 beta is now available and offers Quarterly Platform Releases (QPRs) for the current stable platform that include feature drops, bug fixes, and performance improvements ahead of the public release schedule."

    Don't see downloads for the factory images yet, though.

    @roirraW "edor" ehT Wasn't sure if you were going to create another thread for this (I think you mentioned that you may do that) or use your old thread (I was too lazy to find it 🙃), so I just posted it here.


    What's new?​

    Android 13 QPR1 beta is now available and offers Quarterly Platform Releases (QPRs) for the current stable platform that include feature drops, bug fixes, and performance improvements ahead of the public release schedule.

    Previously enrolled?​

    If you were previously enrolled in the Android 13 Beta Program and have not opted out of the beta program, your eligible device(s) will automatically continue to receive the next Android 13 QPR1 beta updates.

    You only have a short window to opt out of the Android Beta Program now without data loss

    If you have already updated, leaving the program will result in a wipe and your next opportunity to exit without losing data will be in December after the stable launch of Android 13 QPR1.
    3
    Canary Magisk 25203 working fine with QPR1 Beta 1. Also has the October, 2022 Google Play System update. Bootloader and radio have also been updated.
    2
    Factory Image and OTA links are at the bottom of this post.


    The following issues have been addressed:

    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 1 system images are available for the Pixel 4a, Pixel 4a 5G, Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, and Pixel 6a, as well as in the Android Emulator. The Pixel 4 and 4 XL are not supported.

    Most users will be installing Beta 1 (T1B1.220819.006 and T1B1.220819.007 on 6a) with the September security patch from the Android Beta Program website. You can expect an OTA update in the coming hours. If you need help, here’s our full guide on installing Android 13.

    or

    2
    This?

    I assume it will come in the next Beta, or one of the next Betas.
    Lets hope it will arrive soon cuz im excited to see how bad my battery is😂
    2
    September 8, 2022 3:10pm Timi Cantisano

    Google has released Android 13 QPR1 Beta 1​

    Although Google has made Android 13 official and rolled it out to Pixel devices, that doesn’t mean the work stops there. While the release is complete, there could be many different bugs and small issues within the OS that need to be fixed. This is where the Quarterly Platform Release (QPR) comes into play, allowing those in the beta program early access to fixes and improvements. Google has now announced the release of Android 13 QPR1 Beta 1.
    The update is now live and available for supported Pixel devices like the Pixel 4a, Pixel 4a 5G, Pixel 5, Pixel 5a, and Pixel 6 devices. As mentioned before, QPR releases offer improvements or enhancements to Android that are not available to the public yet. For the Android 13 QPR1 Beta 1 release, you can check below for the specific issues that were addressed.

    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.

    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.
    If you want to experience these changes before they roll out in official releases, you can enroll in the beta program for your supported device. If you were previously enrolled in the Android 13 beta, you should still be enrolled to receive QPR updates. By enrolling, you can give feedback to the developers and help identify potential issues that might arrive with the QPR release. You can do this by using the Issue Tracker. If you are not, you can sign up by visiting the Android beta website, which is in the source link.
    When you sign in with your Google account, you will see all eligible devices for the program. If you choose to opt into the program with an eligible device, you will be asked to accept the terms and conditions. You will also have the option of receiving emails about the program and also declaring yourself as a developer. Furthermore, you can join the official Reddit group to share your thoughts or problems with regard to the latest updates. You can also manually download the installation here.
    While discovering new features is exciting, please note that this is a beta, so there could be issues that you encounter while using your device. If the phone is your daily, it might not be the best idea to enroll in the program. While you can revert back to a stable version of Android if you opt out, it will require you to wipe your device and start fresh.

    Source: Android Beta Program

    Release notes​

    bookmark_border
    NotificationsSave this page to your Developer Profile to get notifications on important updates.


    DismissNext

    Beta 1
    Release dateSeptember 8, 2022
    BuildT1B1.220819.006, T1B1.220819.007 (Pixel 6a only)
    Security patch levelSeptember 2022
    Google Play services22.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 1​

    You can install Android 13 QPR1 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
    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 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
    star-issue.svg
    .
    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 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.
  • 11
    Android 13 QPR1 beta 1 discussion starts here.

    "Android 13 QPR1 beta is now available and offers Quarterly Platform Releases (QPRs) for the current stable platform that include feature drops, bug fixes, and performance improvements ahead of the public release schedule."

    Don't see downloads for the factory images yet, though.

    @roirraW "edor" ehT Wasn't sure if you were going to create another thread for this (I think you mentioned that you may do that) or use your old thread (I was too lazy to find it 🙃), so I just posted it here.


    What's new?​

    Android 13 QPR1 beta is now available and offers Quarterly Platform Releases (QPRs) for the current stable platform that include feature drops, bug fixes, and performance improvements ahead of the public release schedule.

    Previously enrolled?​

    If you were previously enrolled in the Android 13 Beta Program and have not opted out of the beta program, your eligible device(s) will automatically continue to receive the next Android 13 QPR1 beta updates.

    You only have a short window to opt out of the Android Beta Program now without data loss

    If you have already updated, leaving the program will result in a wipe and your next opportunity to exit without losing data will be in December after the stable launch of Android 13 QPR1.


    The following issues have been addressed:

    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 1 system images are available for the Pixel 4a, Pixel 4a 5G, Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, and Pixel 6a, as well as in the Android Emulator. The Pixel 4 and 4 XL are not supported.

    Most users will be installing Beta 1 (T1B1.220819.006 and T1B1.220819.007 on 6a) with the September security patch from the Android Beta Program website. You can expect an OTA update in the coming hours. If you need help, here’s our full guide on installing Android 13.

    or
    September 8, 2022 3:10pm Timi Cantisano

    Google has released Android 13 QPR1 Beta 1​

    Although Google has made Android 13 official and rolled it out to Pixel devices, that doesn’t mean the work stops there. While the release is complete, there could be many different bugs and small issues within the OS that need to be fixed. This is where the Quarterly Platform Release (QPR) comes into play, allowing those in the beta program early access to fixes and improvements. Google has now announced the release of Android 13 QPR1 Beta 1.
    The update is now live and available for supported Pixel devices like the Pixel 4a, Pixel 4a 5G, Pixel 5, Pixel 5a, and Pixel 6 devices. As mentioned before, QPR releases offer improvements or enhancements to Android that are not available to the public yet. For the Android 13 QPR1 Beta 1 release, you can check below for the specific issues that were addressed.

    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.

    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.
    If you want to experience these changes before they roll out in official releases, you can enroll in the beta program for your supported device. If you were previously enrolled in the Android 13 beta, you should still be enrolled to receive QPR updates. By enrolling, you can give feedback to the developers and help identify potential issues that might arrive with the QPR release. You can do this by using the Issue Tracker. If you are not, you can sign up by visiting the Android beta website, which is in the source link.
    When you sign in with your Google account, you will see all eligible devices for the program. If you choose to opt into the program with an eligible device, you will be asked to accept the terms and conditions. You will also have the option of receiving emails about the program and also declaring yourself as a developer. Furthermore, you can join the official Reddit group to share your thoughts or problems with regard to the latest updates. You can also manually download the installation here.
    While discovering new features is exciting, please note that this is a beta, so there could be issues that you encounter while using your device. If the phone is your daily, it might not be the best idea to enroll in the program. While you can revert back to a stable version of Android if you opt out, it will require you to wipe your device and start fresh.

    Source: Android Beta Program

    Release notes​

    bookmark_border
    NotificationsSave this page to your Developer Profile to get notifications on important updates.


    DismissNext

    Beta 1
    Release dateSeptember 8, 2022
    BuildT1B1.220819.006, T1B1.220819.007 (Pixel 6a only)
    Security patch levelSeptember 2022
    Google Play services22.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 1​

    You can install Android 13 QPR1 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
    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 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
    star-issue.svg
    .
    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 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.
    10
    Yet another Beta of 13, Beta 3.3:


    Pixel 6 Proraven-tpb3.220617.002-factory-1acb43a3.zip1acb43a3d082b8d2cd16cba834c1b1de25042c5d5122483bbf54ff4a16682186


    Android 13 Beta 3.3 (June 2022)
    Release date: June 27, 2022
    Build: TPB3.220617.002
    Emulator support: x86 (64-bit), ARM (v8-A)
    Security patch level: June 2022
    Google Play services: 22.21.16
    API diff:


    If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 3.3.

    This minor update to Android 13 Beta 3 includes stability and performance improvements as well as the following fixes:

    • Fixed an issue with the Pixel launcher where if the Always show keyboard option was enabled for the app drawer, then when the user closed the app drawer and opened an app folder on the Home screen, the keyboard was erroneously shown as well. (Issue #236584457)
    • Fixed an issue where in some cases, such as gesturing to go back, the system UI crashed. (Issue #236558007)
    • Fixed an issue where devices couldn't connect to a WiFi network in some cases even when the network was available and the signal strength was good. (Issue #236617510)
    • Fixed an issue where the BluetoothManagerService continued to try and bind to the TbsService even when bluetooth.profile.ccp.server.enabled was false, leading to slow performance and cold starts for apps.
    • Fixed an issue where in some cases after a device was plugged in to charge (for example, overnight), the device would become unresponsive until it was rebooted.
    • Fixed a kernel issue with lib/list_debug.c that caused a kernel panic in certain cases on some devices.
    • Fixed an issue with the Connectivity Thermal Power Manager that caused slow UI rendering, unresponsiveness in apps, and poor battery performance in some cases.


    June 27, 2022 2:30pm Comment Skanda Hazarika

    Google rolls out Android 13 Beta 3.3 with a bunch of bug fixes​

    The beta branch of Android 13 just picked up a new bug-squashing update. Following in the footsteps of Android 13 Beta 3’s earlier incremental updates, this new release fixes a whole bunch of issues, including slow UI rendering, inability to connect to a Wi-Fi network, system UI crashes, and a few other problems.
    The build number of Android 13 Beta 3.3 is TPB3.220617.002. There is no change in the security patch level, though, hence it’s still June 2022 on this release. You can find the full list of published fixes in this update below:
    • Fixed an issue with the Pixel launcher where if the Always show keyboard option was enabled for the app drawer, then when the user closed the app drawer and opened an app folder on the Home screen, the keyboard was erroneously shown as well. (Issue #236584457)
    • Fixed an issue where in some cases, such as gesturing to go back, the system UI crashed. (Issue #236558007)
    • Fixed an issue where devices couldn’t connect to a WiFi network in some cases even when the network was available and the signal strength was good. (Issue #236617510)
    • Fixed an issue where the BluetoothManagerService continued to try and bind to the TbsService even when bluetooth.profile.ccp.server.enabled was false, leading to slow performance and cold starts for apps.
    • Fixed an issue where in some cases after a device was plugged in to charge (for example, overnight), the device would become unresponsive until it was rebooted.
    • Fixed a kernel issue with lib/list_debug.c that caused a kernel panic in certain cases on some devices.
    • Fixed an issue with the Connectivity Thermal Power Manager that caused slow UI rendering, unresponsiveness in apps, and poor battery performance in some cases.
    Apart from the aforementioned bug fixes, the update also bumps the Google Play services version from 22.18.19 to 22.21.16.
    In case your Google Pixel device is already enrolled in the Android 13 beta program, you will automatically receive an over-the-air update to Beta 3.3. You can also download the full OTA or the factory image from the link below if you want to manually upgrade to the latest beta release.
    Download Android 13 Beta 3.3

    Source: Android Beta Program on Reddit
    8
    All, 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
    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..

    Good spot. Seeing as how that's now intended behaviour, I guess wiping and disabling verification is all our best moves from here.

    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.
    6
    New Pixel 6 modem included!

    g5123b-102852-220609-b-8701566