General February 1, 2023 - QPR2 Beta 3 (T2B3.230109.002) - Pixel 6 Pro [Raven] - [thread also for future Major Android Betas]

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member
"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.
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
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

 
Last edited:

roirraW "edor" ehT

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

5t4rC0m1337

Senior Member
Feb 4, 2017
50
18
Hi Guys,

I woke up this morning, my phone was running hot (40 degrees), I just can't anymore with the battery and the hotness, I am going to upgrade from A12 to A13 with the September update.

What is the most straight forward and cleanest way to upgrade please ?
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Hi Guys,

I woke up this morning, my phone was running hot (40 degrees), I just can't anymore with the battery and the hotness, I am going to upgrade from A12 to A13 with the September update.

What is the most straight forward and cleanest way to upgrade please ?
The *only* thing different for updating to Android 13 Stable is that you should start with:
Code:
adb reboot bootloader
fastboot --slot all flash bootloader bootloader.img
to protect yourself from accidentally permanently bricking your phone. Replace "bootloader.img" with the actual name of the bootloader file inside the inner zip in the (full) firmware zip. Not the same thing as the kernel/boot.img.
Then click the yellow How-To-Guide Quick Filter at the top of the list of threads in this section and take your pick as to your preferred way of updating - there are at least 2-3 threads with directions.

I prefer the full factory image method. See those threads for the details. Just know that this thread is about the Android 13 QPR1 Beta 1, not about Android 13 Stable.
 
  • Like
Reactions: roirraW "edor" ehT

yasars

Senior Member
Apr 16, 2010
539
65
Ruhrgebiet
Switch up gesture bug.... Doesnt work ..any fix?
You must use the 3 bottoms to use the phone and UI is laggy


///
Swipe up fix...go to apps> pixel launcher> 3dot menu and deinstall update.... Thats it
If you have not 3dot menu on the right install this and then deinstall it
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Pixel 6 Proraven-t2b2.221216.006-factory-8e0c382f.zip8e0c382f9e55c898c045eb2426798b4a8f4ecd1cd8477212a919278697642aaa

    Pixel 6 Proraven-ota-t2b2.221216.006-e69abcb0.zipe69abcb00f54b2426fdee0850c944ad9fe8c8a0338b3accff389162f33eb43d3

    ARM64+GMSgsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip12a8e1935c6ef46d2d44dea6ea331fa238cb6240bd6df607f6ccb849d619b25c
    ARM64aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zipe508d63f27da01889734d36171dec11f226e2f2bc538526379e2184d51e9ffd3
    x86_64+GMSgsi_gms_x86_64-exp-T2B2.221216.006-9443277-5255002f.zip5255002f0d1249bb08725c06e3a264d8caaf2d84cdb9c40c7a7a8954249d6493
    x86_64aosp_x86_64-exp-T2B2.221216.006-9443277-02d675fb.zip02d675fb15c962fa7e35f494edfbfa2da7b886ef3f6e4709b73b1c57fb96b8ab

    Release notes​

    bookmark
    Beta 2Beta 1
    Release dateJanuary 9, 2023
    BuildT2B2.221216.006
    Security patch levelJanuary 2023
    Google Play services22.41.13

    About Android 13 QPR2​

    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 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.

    How to get QPR2 Beta 2​

    You can install Android 13 QPR2 Beta 2 on any of the following Google Pixel devices:
    • Pixel 4a and 4a (5G)
    • Pixel 5 and 5a
    • Pixel 6 and 6 Pro
    • Pixel 6a
    • Pixel 7 and 7 Pro
    See Get Android 13 QPR beta builds for details on how to get started.

    General advisories​

    Be aware of these general advisories about the release:
    • This release might have various stability, battery, or performance issues.
    • For users with accessibility needs, this release might not be appropriate for daily use.
    • Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
    • Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.

    Get support​

    Two primary support channels are available to you when developing and testing with Android 13 QPR2. 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 QPR2 Beta 2:
    • Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
    • Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.

    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 QPR2. 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.
    • In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
    • An issue with the System UI can sometimes cause it to crash from a null pointer exception.

    Previous beta releases​

    Android 13 QPR1 Beta 1​

    Other known issues​

    Based on our testing, you might encounter the following issues when using Android 13 QPR2. 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.
    • In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
    • An issue with the System UI can sometimes cause the Home screen to become unresponsive.

    Google Apps​

    • After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
    3
    Does root works fine on new beta?
    You have to use the Pixel 7 Pro boot image to patch, like it was with QPR2 Beta 1.
    3
    Wonder if we can just use the p6p boot this time
    Seen a couple users report that using the Pixel 6 Pro boot image to root is now working again on QPR2 Beta 3, for whatever that's worth.
    2
    Anyone faced the problem of disconnected calls after 20.02 mins?
    My calls get disconnected always after this time period.
    Nope. Calls have been pretty great. Maybe whoever you're talking to can't stand talking to you more than that 😂
    2
    Seen a couple users report that using the Pixel 6 Pro boot image to root is now working again on QPR2 Beta 3, for whatever that's worth.
    I can confirm this on a Pixel 6 (non-Pro), it does indeed work as intended again.
  • 11
    February 1, 2023:
    QPR2 Beta 3
    Pixel 6 Proraven-t2b3.230109.002-factory-a8b7d332.zipa8b7d33243440ed011cd037f5ef25fe5b38678c699b33edd8832cc777808e73e

    64-bit-only images​

    Pixel 6 Proraven_64-t2b3.230109.002-factory-64adaa76.zip64adaa76f18899034aa3066d82c3f30a5b6a80de0816a0a50bf6e6e7be971529

    https://developer.android.com/about/versions/13/release-notes#beta3

    Release notes​

    bookmark
    Beta 3Beta 2.1Beta 2Beta 1
    Release dateFebruary 1, 2023
    BuildT2B3.230109.002
    Security patch levelJanuary 2023
    Google Play services23.03.13

    About Android 13 QPR2​

    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 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.

    How to get QPR2 Beta 3​

    You can install Android 13 QPR2 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 QPR2. 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 QPR2 Beta 3:

    Developer-reported and user-reported issues​

    • Fixed an issue where notifications in a notification group were sometimes displayed with straight corners instead of rounded corners. (Issue #264287776, Issue #265529116)
    • Fixed an issue where the message in the notification shade that indicates an active VPN connection overlapped with the message about apps with active foreground services. (Issue #266075977)
    • Fixed an issue where the overflow menu couldn't be accessed when editing Quick Settings tiles. (Issue #263484657)
    • Fixed an issue that sometimes caused a device with vibration enabled to vibrate for too long after it received a notification. (Issue #239676913)

    Other resolved issues​

    • Fixed an issue that sometimes caused messaging apps to crash or fail to send notifications.
    • Fixed a GPU issue that prevented apps from using certain visual effects.
    • Fixed an issue where Quick Settings tiles for a work profile were not added after setting up a new device.
    • Fixed an issue that sometimes caused the Pixel launcher to crash when using the Search bar in the app drawer.
    • Fixed an issue that sometimes prevented a device from being unlocked using a pattern after the Google Assistant was activated.
    • Fixed an issue in the com.android.qns system process that sometimes caused crashes.
    • Fixed an issue with the Pixel launcher that prevented Chinese text input from being recognized when typing in the Search bar in the app drawer.
    • Fixed an issue where when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashed with a "Settings keeps stopping" message and then the system Settings app couldn't be opened.
    • Fixed an issue with the System UI that sometimes caused it to crash from a null pointer exception.
    • Fixed an issue where the connection status of a Bluetooth device sometimes did not match the actual device state.
    • Fixed an issue where the Pixel launcher crashed when a user tapped a web search suggestion for a query term.
    • Fixed an issue that caused status bar icons to overlap with the date text when font and display settings were set to their maximum level on a device.

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

    Previous beta releases​

    Android 13 QPR1 Beta 2​

    Android 13 QPR2 Beta 2.1 (January 2023)
    This minor update to Android 13 QPR2 Beta 2 includes the following fixes:
    • Fixed an issue that sometimes prevented devices from automatically connecting to a 5G network even when it was available. (Issue #265093352)
    • Fixed an issue where devices did not drop or reset an existing, encrypted Bluetooth connection after receiving a command to disable link-layer encryption for that connection.

    Top resolved issues​

    The following issues have been resolved in Android 13 QPR2 Beta 2:
    • Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
    • Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.

    Other known issues​

    Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 2. 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.
    • In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
    • An issue with the System UI can sometimes cause it to crash from a null pointer exception.

    Android 13 QPR1 Beta 1​

    Other known issues​

    Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 1. 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.
    • In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
    • An issue with the System UI can sometimes cause the Home screen to become unresponsive.

    Google Apps​

    • After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
    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