General Android 13 QPR3 went final in June 2023-opt-out now to get the OTA without wiping - Pixel 6 Pro [Raven] - [thread also for future Android QPR Betas]

Search This thread

lssong99

Senior Member
Jul 15, 2005
414
279
Can somebody provide me Pixel 7 Pro's magisk patched boot img from the latest QPR2 Beta 1 update?
The one which succesfully roots the Pixel 6 Pro
Here you are:

 

roirraW "edor" ehT

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

Bzaina

Senior Member
Mar 28, 2013
55
9
Can someone confirm if this Beta 2 intruduced new carriers in Pixel 6 Series?
I have VoLTE now with this Beta 2 (Pixel 6) but no 5G.

I'm asking for something like this:
pt_vf
pt_meo
pt_nos

I know Pixel 7 already have this since beta 1.

You may check this in:
/system/vendor/firmware/carrierconfig/cfg.db

That database (refer to the "confnames" table inside it for carrier names) defines confseq files that are loaded into the nv memory of the modem. e.g. modem config. on ee_telia 5G got enabled and 5CA LTE appeared.

 
Last edited:

Bzaina

Senior Member
Mar 28, 2013
55
9
Pixel 7 and 6 have the same carriers supported. That includes the new portuguese ones from Beta 1

So sad to know this. Pixel 7 users have 5G since beta 1 in Portugal but I'm guessing Google is intending to leave Pixel 6 behind... no 5G for us but we already have VoLTE since beta 2.
 

roirraW "edor" ehT

Forum Moderator
Staff member

Android 13 QPR2 Beta readies a way to record a specific app instead of your whole screen

Kyle Bradshaw
Jan. 10th 2023 1:45 pm PT
@SkylledDev
Android 13 logo

Android 13 is preparing a new way to record the contents of a single app instead of recording the entirety of your screen.

When screen recording today on Android, you’re capturing the entirety of your phone’s visible contents, including any incoming notifications, apps in your Recent list, and more. This can be a bit of a privacy nightmare, which leads to screen recordings needing to be carefully staged.
Google is looking at a potential solution to this problem in Android 13’s second quarterly update — currently in Beta testing. As uncovered by my colleague Dylan Roussel, Android 13 QPR2 Beta 2 has some experimental new UI for selecting one specific app to be recorded, instead of recording your full screen.
As seen in the example video below, a live feed of a few recent apps are shown in a dialog similar to Android’s share sheet. Beneath those options, a larger list of apps is also available to choose from, allowing you the freedom to record any one particular app you wish.


From the dialog’s phrasing — “Share or record an app” — we believe this same design will also be used for casting your phone’s screen to another device. If so, this would certainly afford more privacy to someone casting their screen, such as a teacher showing something to their class.
The ability to record a single Android app should also be particularly helpful for those on tablets or foldables who can have multiple apps open, but probably only want to record one of them. This should help keep video sizes down, at least somewhat.
For now, though, this feature doesn’t seem to work correctly, which is no surprise considering it’s still a work-in-progress. It’s possible Google may have it completed in time for the full Android 13 QPR2 launch — expected to be in March — or this may be a preview of something even further on the horizon.
Dylan Roussel contributed to this article.
 

MartinN6

Senior Member
Jul 6, 2015
695
416
Kassel
Themed icons
In this xda article (https://www.xda-developers.com/google-testing-automatic-themed-icons-pixel-launcher/) it is written: "The feature comes in the form of a new developer flag called ENABLE_FORCED_MONO_ICON .The description states that flipping the toggle will "enable the ability to generate monochromatic icons, if it is not provided by the app."
Unfortunately I can't find this switch (it's not in developer options in settings) Can anyone help me? Thanks a lot for this
 

roirraW "edor" ehT

Forum Moderator
Staff member

Android 13 QPR2 Beta 2 feedback survey live for Pixel
Abner Li
- Jan. 12th 2023 9:37 am PT
@technacity

Android 13 QPR2 Beta 2 rolled out on Monday with only a handful of tweaks, and Google is now taking feedback from Pixel owners.

The feedback survey starts by having you confirm the Android 13 QPR2 Beta 2 version (T2B2.221216.006) you’re running and the phone: Pixel 4a to 7 Pro.
You’re asked to rate satisfaction across 13 areas: stability, performance, battery, device temperature, camera, Bluetooth, call quality, messaging, Wi-Fi connectivity, data connectivity, app experience, authentication (face/fingerprint), and charging (wired charging, wireless charging).
That’s then followed by a feedback survey question on whether you’d recommend Android 13 QPR2 Beta 2 in its “current state” to others and “how satisfied are you overall with the software experience on this version of Android” from 1-5, as well as how it compares to the “previous build on your device.”
You’re then asked to identify a “top issue area” with the ability to leave more details on the problem and note how it impacts the overall experience. An “additional feedback on your experience” field closes the survey, where you can share other thoughts.
Google should release one more beta next month, with the following issues remaining:
  • 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.
 

roirraW "edor" ehT

Forum Moderator
Staff member
  • Like
Reactions: Lughnasadh

Top Liked Posts

  • There are no posts matching your filters.
  • 11

    Pixel 6 Pro [Raven] QPR Betas


    QPR stands for "Quarterly Platform Release". Android 13 QPR3 went final in June 2023. See main thread here for final/non-beta releases.

    From my Pixel 7 QPR Beta thread (and adjusting the OP with the same information):
    You 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