General May 16, 2023 QPR3 Beta 3.2 T3B3.230413.009 - Global / T3B3.230413.009.A1 Verizon - Pixel 6 Pro [Raven] - [thread also for future Android QPR Betas]

Search This thread

shadyrexman

Member
Mar 29, 2023
13
12
@shadyrexman I haven't read everything, but is it possible that you're fastboot booting the Magisk'd Pixel 7 Pro boot.img, but that you're direct installing to the stock Pixel 6 Pro boot.img that's on your phone after you updated?

Recommendations: Either...
  • Don't fastboot boot the Magisk'd Pixel 7 Pro boot.img. Instead do:
    • Code:
      fastboot flash boot Magik'dPixel7ProBoot.img
or
  • Flash the stock unroot Pixel 7 Pro boot.img to your Pixel 6 Pro, and then boot the Magisk'd Pixel 7 Pro boot.img and direct install, but if you're going to do it this way, you might as well do the first way and just flash the Magisk'd Pixel 7 Pro boot.img.
You made my day, I just rooted my p6p, I used to follow the OTA instructions and use fastboot boot, instead of fastboot flash boot. And now I'm ok :) thank you again for everyone's helping!
 

roirraW "edor" ehT

Forum Moderator
Staff member
You made my day, I just rooted my p6p, I used to follow the OTA instructions and use fastboot boot, instead of fastboot flash boot. And now I'm ok :) thank you again for everyone's helping!
You're welcome! I'm glad you found your solution, and thanks for letting us know.
 
  • Love
Reactions: shadyrexman

roirraW "edor" ehT

Forum Moderator
Staff member
Aignes Website-Watcher is telling me this (bolded) part at the end is new in the "Which devices are eligible?" FAQ at:
Devices must be on a non-Developer Preview public stable build to enroll in the beta program.
 
  • Like
Reactions: Lughnasadh

roirraW "edor" ehT

Forum Moderator
Staff member
QPR 3 Beta 2.1
This minor update to Android 13 QPR3 Beta 2 includes the following improvements:
  • Modem updates

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.

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.

Release notes​

bookmark
Beta 2.1Beta 2Beta 1
Release dateApril 6, 2023
BuildT3B2.230316.005
Security patch levelMarch 2023
Google Play services23.11.15
Android 13 QPR3 Beta 2.1 (April 2023)
This minor update to Android 13 QPR3 Beta 2 includes the following improvements:
  • Modem updates
If you're already running Beta 2, you'll automatically receive an over-the-air (OTA) update to Beta 2.1.
Note: Other known issues listed for the Beta 2 release still apply to Beta 2.1.

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

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

Pixel 6 Proraven-t3b2.230316.005-factory-3923dd64.zip3923dd6452862974f235d6acbe215773e379351ee7296ffa026f2748fa7056d5

Pixel 6 Proraven-ota-t3b2.230316.005-811d7863.zip811d78635bafeaa3d02b3b69ab2dc28109b574c3c511d1df80db32716745f17f

64-bit-only images​

Pixel 6 Proraven_64-t3b2.230316.005-factory-41c2639d.zip41c2639ddcdaddad9cb0b59ba07ff68f9a9767cd4b774bc78ceb866dca8e6597
 
Last edited:
  • Like
Reactions: Lughnasadh

Lughnasadh

Senior Member
Mar 23, 2015
5,176
6,068
Google Nexus 5
Huawei Nexus 6P
I lost root and cant patch P7P bootloader with Magisk. Any idea what to do?
P6P
First of all, you don't patch the bootloader, you patch the boot image.

Second, use Canary Magisk 26001 or Beta Magisk 26.0 to patch the Pixel 6 Pro boot image. Patching the Pixel 7 Pro boot image is no longer needed with these new Magisk versions.
 

BROKEN1981

Senior Member
Dec 27, 2013
1,922
874
ASUS ROG Phone 3
Google Pixel 6 Pro
First of all, you don't patch the bootloader, you patch the boot image.

Second, use Canary Magisk 26001 or Beta Magisk 26.0 to patch the Pixel 6 Pro boot image. Patching the Pixel 7 Pro boot image is no longer needed with these new Magisk versions.
Yeah, not sure why I didn't type out boot image. ( I am very tired.) Figured it out before I seen your reply.
 
  • Like
Reactions: roirraW "edor" ehT

onesolo

Senior Member
Apr 18, 2006
2,575
225
Nexus 7 (2013)
Google Nexus 5
Guys, need help!!! I'm on beta 2 and tried to flash factory image of 2.1 and got this error:
Checking 'product' OKAY [ 0.002s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' FAILED

Device version-baseband is 'g5123b-116199-230317-B-9765545'.
Update requires 'g5123b-116954-230330-B-9849771'.

fastboot: error: requirements not met!
Press any key to exit...
Any ideas?!?! I'm flashing all the time the factory images on the beta with no problems from the baseband...
Going to flash the ota on the recovery ...
 
  • Wow
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Guys, need help!!! I'm on beta 2 and tried to flash factory image of 2.1 and got this error:

Any ideas?!?! I'm flashing all the time the factory images on the beta with no problems from the baseband...
Going to flash the ota on the recovery ...
Are you using Platform-Tools v33.0.3, or one of the bad 34.x versions? You've got the correct Beta 2.1 firmware downloaded, not for the wrong device, by mistake? It says "Raven"?

Maybe try dirty flashing Beta 2.0 and then 2.1 after. You can find the 2.0 downloads in the second post in the Old News section.
 
  • Like
Reactions: Lughnasadh

roirraW "edor" ehT

Forum Moderator
Staff member
Guys, need help!!! I'm on beta 2 and tried to flash factory image of 2.1 and got this error:

Any ideas?!?! I'm flashing all the time the factory images on the beta with no problems from the baseband...
Going to flash the ota on the recovery ...
Another idea I have is that you downloaded the OTA instead of the factory image. The factory image shouldn't care what version of anything is on your phone - it'll just overwrite everything.
 
  • Like
Reactions: Lughnasadh

onesolo

Senior Member
Apr 18, 2006
2,575
225
Nexus 7 (2013)
Google Nexus 5
Are you using Platform-Tools v33.0.3, or one of the bad 34.x versions? You've got the correct Beta 2.1 firmware downloaded, not for the wrong device, by mistake? It says "Raven"?

Maybe try dirty flashing Beta 2.0 and then 2.1 after. You can find the 2.0 downloads in the second post in the Old News section.
I'm using 34.0.1-9680074. I didn't download for the wrong device. After that I flashed the ota file with success.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
I'm using 34.0.1-9680074. I didn't download for the wrong device. After that I flashed the ota file with success.

Ah, that's the issue. Platform-Tools 34.0.0 and 34.0.1 have a serious bug that prevents successfully flashing the firmware image. Google knows about it but has not fixed it yet, and they still offer 34.0.1 as the latest Platform-Tools despite the bug. You have to use 33.0.3 with the whole image. I'm glad to hear that they worked fine with the OTA, and therefore solved the issue.

 

roirraW "edor" ehT

Forum Moderator
Staff member
From my Pixel 7 QPR Beta thread (and adjusting the OP with the same information):
You can officially opt into the Android Beta Program there, or use 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'm only being allowed to Opt into the Android 14 beta program. I want to enroll in the Android 13 QPR Beta program instead. Any idea how?
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:
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.
 
  • Like
Reactions: Lughnasadh

roirraW "edor" ehT

Forum Moderator
Staff member
QPR3 Beta 3:

Release notes​

bookmark
Beta 3Beta 2.1Beta 2Beta 1
Release dateApril 20, 2023
BuildPixel 6, Pixel 6 Pro, and Pixel 6a devices that use Verizon as their carrier: T3B3.230413.003.A1

All other devices: T3B3.230413.003
Emulator supportx86 (64-bit), ARM (v8-A)
Security patch levelPixel 6, Pixel 6 Pro, and Pixel 6a devices that use Verizon as their carrier: March 2023

All other devices: April 2023
Google Play services23.09.12

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

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

Top resolved issues​

The following issues have been resolved in Android 13 QPR3 Beta 3:
  • Fixed issues that could cause Wi-Fi calling to stop working.
  • Fixed an issue that could sometimes cause the system to get stuck on the home screen with no app icons and either the normal background or a blank, black background.
  • Fixed an issue where the system UI crashed when trying to access the Wallpaper & style screen both in the system settings app or by long-pressing from the home screen.
  • Fixed an issue that could cause the screen on some devices to flash green when toggled if the phone was in a high temperature environment.
  • Fixed an issue where the camera displayed a black screen if the user tried to open the camera by pressing the power button twice.
  • Fixed an issue where in some cases when a work profile is switched on or off, the device rebooted instead.

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​

  • The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.

Pixel 6 Proraven-t3b3.230413.003-factory-9ff78833.zip9ff78833dedc5e289562658e80ed109f98d959b17d2c7b44734edcdc64e3b944
Pixel 6 Pro (Verizon only)raven-t3b3.230413.003.a1-factory-98736a77.zip98736a777fd4f528257cdd89e730c2f262dfa13c24a5bc2babfda5f17602d8c0

64-bit-only images​

Pixel 6 Proraven_64-t3b3.230413.003-factory-d071aaf4.zipd071aaf40cdcdb53888a92f7242105ec55421ce50737cefddc5f630b2405dcfd

Pixel 6 Proraven-ota-t3b3.230413.003-739cd6ac.zip739cd6ac6a4acf4dea863e1fafbb088aecd2afc2067000985db0c010d69039c7
Pixel 6 Pro (Verizon only)raven-ota-t3b3.230413.003.a1-7d0c2664.zip7d0c266477416dcdeae02c82a02440fe4e66fc6af0bc83f4ca1f384ffb2e9c36

 
  • Like
Reactions: Lughnasadh

BROKEN1981

Senior Member
Dec 27, 2013
1,922
874
ASUS ROG Phone 3
Google Pixel 6 Pro
QPR3 Beta 3:


Pixel 6 Proraven-t3b3.230413.003-factory-9ff78833.zip9ff78833dedc5e289562658e80ed109f98d959b17d2c7b44734edcdc64e3b944
Pixel 6 Pro (Verizon only)raven-t3b3.230413.003.a1-factory-98736a77.zip98736a777fd4f528257cdd89e730c2f262dfa13c24a5bc2babfda5f17602d8c0

64-bit-only images​

Pixel 6 Proraven_64-t3b3.230413.003-factory-d071aaf4.zipd071aaf40cdcdb53888a92f7242105ec55421ce50737cefddc5f630b2405dcfd

Pixel 6 Proraven-ota-t3b3.230413.003-739cd6ac.zip739cd6ac6a4acf4dea863e1fafbb088aecd2afc2067000985db0c010d69039c7
Pixel 6 Pro (Verizon only)raven-ota-t3b3.230413.003.a1-7d0c2664.zip7d0c266477416dcdeae02c82a02440fe4e66fc6af0bc83f4ca1f384ffb2e9c36

First, thank you for always letting us know about the newest updates! Secondly, can you please delete the spam?
Screenshot_20230420-184339.png
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
First, thank you for always letting us know about the newest updates!
You're welcome!

Secondly, can you please delete the spam?
The quickest way to get the first available moderator to act on SPAM (or anything else) is to use the Report button in the lower-right corner of the post, but as you can see, another moderator has already deleted that SPAM. :) Actually, according to the forum whether it's correct or not, another moderator deleted it three minutes before you posted this. You might've been in the process of making the post while they were deleting the SPAM. 🤷‍♂️

Thank you, anyway!
 
  • Like
Reactions: BROKEN1981

BROKEN1981

Senior Member
Dec 27, 2013
1,922
874
ASUS ROG Phone 3
Google Pixel 6 Pro
Has the last update been buggy for anyone? I get random app crashes, phone froze about 4 times. This is after I had reflashed in Pixel Flasher erasing user data.

It was worse than that before. Android Auto would disconnect. Couldn't type in the Google search for an app. Google Files was missing a few things. Couldn't upload files to Google Drive.

Only running 2 mods. One mod is to get the recording fiction in Google dialer app. The other is to hide NavBar. So nothing major.
 

onesolo

Senior Member
Apr 18, 2006
2,575
225
Nexus 7 (2013)
Google Nexus 5
Has the last update been buggy for anyone? I get random app crashes, phone froze about 4 times. This is after I had reflashed in Pixel Flasher erasing user data.

It was worse than that before. Android Auto would disconnect. Couldn't type in the Google search for an app. Google Files was missing a few things. Couldn't upload files to Google Drive.

Only running 2 mods. One mod is to get the recording fiction in Google dialer app. The other is to hide NavBar. So nothing major.
the same for me after applied OTA and root on the regular 6...

What mod is that for the google dialer??
 
  • Wow
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    It's interesting that the Verizon builds are always one month behind on security patch level with the QPR 3 Beta 3 builds: first March when Global was April, now April when Global is May.
    1
    😈
    QPR 3 Beta 3.2:


  • 11

    Pixel 6 Pro [Raven] QPR Betas


    QPR stands for "Quarterly Platform Release". Android 13 QPR2 went final in March 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 can officially opt into the Android Beta Program there, or use 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'm only being allowed to Opt into the Android 14 beta program. I want to enroll in the Android 13 QPR Beta program instead. Any idea how?
    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:
    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.
    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