General November 7, 2022 Android 13 QPR1 Beta 3.1 (t1b3.221003.008) - Pixel 6 Pro [Raven] - [thread also for future Major Android Betas]

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member

Pixel 6 Proraven-t1b2.220916.004-factory-b4c16abf.zipb4c16abfc3a5237ac6412b650705ee255964a7b5b5a9a684eb22bbb678196c1d

Pixel 6 Proraven-ota-t1b2.220916.004-159ff0cd.zip159ff0cd49711b694905d1a297a2b8ee9ac6fde262dbd48b1332b3a9b1367bdc
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member

Release notes​

Beta 2
Release dateOctober 5, 2022
BuildT1B2.220916.004
Security patch levelOctober 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 2​

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

roirraW "edor" ehT

Forum Moderator
Staff 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?
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 always 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.
 
  • Like
Reactions: Lughnasadh

fil3s

Senior Member
Aug 30, 2014
1,590
443
43
bendigo
mobiledevices11.blogspot.com
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 always 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.

I didn't have any modules installed
 
  • Like
Reactions: roirraW "edor" ehT

fil3s

Senior Member
Aug 30, 2014
1,590
443
43
bendigo
mobiledevices11.blogspot.com
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.

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"
but again it got stuck on Google logo and rebooted
 
  • Wow
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff 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"
but again it got stuck on Google logo and rebooted
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).
 
  • Like
Reactions: fil3s

fil3s

Senior Member
Aug 30, 2014
1,590
443
43
bendigo
mobiledevices11.blogspot.com
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff 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).
 

roirraW "edor" ehT

Forum Moderator
Staff 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'm glad you figured out the probably why. It happens to everyone from time to time.
 
  • Like
Reactions: fil3s

omrij

Senior Member
Mar 5, 2009
627
148
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
 
  • Wow
Reactions: roirraW "edor" ehT

kevin2025

Member
Mar 21, 2022
8
3
how do you rollback to qpr1 beta 1? I'm using qpr1 beta 2 but the factory image has a new bootloader version then qpr1 beta 1 package and when I flashed beta 2 I flashed the new bootloader to both slots. do you just flash the old radio and update zip from beta 1's?
 
  • Wow
Reactions: spinoza23

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    November 7, 2022:
    Pixel 6 Proraven-t1b3.221003.008-factory-6454afed.zip6454afed8f49ed1f08acaf49bd4a86ff28812b5624029c91aa6346d511b7f26c

    Pixel 6 Proraven-ota-t1b3.221003.008-2f799487.zip2f7994875425cbe924afae7da68ae876b7ce0545f831f052f3a27635a8f3f82e

    Release notes​

    Beta 3.1 Beta 3 Beta 2 Beta 1
    Release dateNovember 7, 2022
    BuildT1B3.221003.008
    Security patch levelNovember 2022
    Google Play services22.36.16
    Android 13 QPR1 Beta 3.1 (November 2022)
    This minor update to Android 13 QPR1 Beta 3 includes the following fixes:
    • Fixed a platform issue that caused apps to crash when they were using a MediaSession to handle input from hardware media playback buttons. (Issue #251798994, Issue #252665746, Issue #251381423, Issue #251513135, Issue #255500998)
    • Fixed issues where a device's GPU drivers sometimes caused the system UI to freeze during normal device use.
    • Fixed an issue where Pixel phones sometimes displayed an incorrect "Missed call" notification instead of "Call answered on another device" when the call was answered remotely by Pixel Watch (in untethered mode).
    • Fixed an issue that sometimes caused the Google Camera app to crash.
    • Fixed an issue that prevented Google Assistant from being activated by hotword on some devices.
    • Fixed an issue that prevented motion-based gestures, such as "Lift to check phone" or "Flip to Shhh", from working on some devices.
    • Fixed an issue that sometimes caused artifacts to display when recording or viewing video on some devices.
    • Fixed an issue that sometimes caused the Google Camera app to launch slowly.
    • Fixed an issue for Pixel 6a devices that sometimes caused the CarrierSettings to crash when inserting a SIM card.
    • Fixed that issue that prevented the "Go to browser" option in the notification shade from working while using an instant app.

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

    You can install Android 13 QPR1 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 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 resolved issues​

    The following issues have been resolved in Android 13 QPR1 Beta 3:

    Developer-reported and user-reported issues​

    • Fixed an issue for some devices where the screen unlock UI was displayed over notifications and other lock-screen content. (Issue #254163754)

    Other resolved issues​

    • Fixed an issue that prevented the "Flip camera for selfie" gesture from working on some devices.
    • Fixed an issue that sometimes caused the screen to go blank while attempting to unlock a device.
    • Fixed an issue that sometimes prevented a device from being unlocked using either Face Unlock or Fingerprint Unlock when the device had been idle for multiple hours.
    • Fixed an issue that sometimes caused fullscreen video playback to flicker after enabling always-on-display features and locking the screen.

    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 QPR1. These issues are already known, so there’s no need to file additional reports for similar issues.

    Android Platform​

    • (Fixed in Beta 3.1) In some cases, issues with a device's GPU drivers cause the system UI to freeze during normal device use. To work around this issue, try restarting the device.

    Pixel​

    • (Fixed in Beta 3.1) In some cases, Pixel phones display an incorrect "Missed call" notification instead of "Call answered on another device" when the call is answered remotely by Pixel Watch (in untethered mode).

    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.

    October 26, 2022:
    https://www.reddit.com/r/android_beta/comments/ye15ik
    Posted by u/androidbetaprogram
    Official Google Account
    8 hours ago

    [5 min survey] Tells us what you think about Android 13 QPR1 Beta 3​

    Android 13 QPR1
    Hi Beta users,
    We'd like your feedback on the latest version of Android 13 QPR1 Beta 3 on your Pixel device. This anonymous survey should take about 5 minutes to complete.
    Please only fill out this survey if your device is running Beta 3 (T1B3.221003.003). You can verify this by going to Settings > About Phone.
    If you're experiencing issues/bugs, please also send us feedback using the Android Feedback app on your device or via the public issue tracker https://developer.android.com/about/versions/13/feedback.
    We look forward to your feedback!

    Discussion about Android 13 QPR1 Beta 3 October 20, 2022 - t1b3.221003.003 starts here.

    You can officially opt into the Android Beta Program there, or use the factory image or OTA below.

    Pixel 6 Proraven-t1b3.221003.003-factory-b5d06db1.zipb5d06db19ff712a0d478b9ce664980eb96cbd893a62111ed53b27f6af3b4aa02

    Pixel 6 Proraven-ota-t1b3.221003.003-8b704cc5.zip8b704cc51fd72b0079589ae4088a6dd6122da936882d46b752dfb2ffc25fa5d8

    Release notes​

    bookmark
    Beta 3Beta 2Beta 1
    Release dateOctober 20, 2022
    BuildT1B3.221003.003
    Security patch levelOctober 2022
    Google Play services22.36.16

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

    You can install Android 13 QPR1 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 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 3:

    Developer-reported and user-reported issues​

    • Fixed an issue for some devices where the screen unlock UI was displayed over notifications and other lock-screen content. (Issue #254163754)

    Other resolved issues​

    • Fixed an issue that prevented the "Flip camera for selfie" gesture from working on some devices.
    • Fixed an issue that sometimes caused the screen to go blank while attempting to unlock a device.
    • Fixed an issue that sometimes prevented a device from being unlocked using either Face Unlock or Fingerprint Unlock when the device had been idle for multiple hours.
    • Fixed an issue that sometimes caused fullscreen video playback to flicker after enabling always-on-display features and locking the screen.

    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 QPR1. These issues are already known, so there’s no need to file additional reports for similar issues.

    Android Platform​

    • In some cases, issues with a device's GPU drivers cause the system UI to freeze during normal device use. To work around this issue, try restarting the device.

    Pixel​

    • In some cases, Pixel phones display an incorrect "Missed call" notification instead of "Call answered on another device" when the call is answered remotely by Pixel Watch (in untethered mode).

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