Develop Bugs

OnePlus 3 and Miracast

Hi guys,
In the last year I was using a dongle, Wireless Display Microsoft Adapter version 3.0.124.0, with good results with a Samsung Galaxy S4 and a notebook, Toshiba P50-A-14L.
I cannot say the same for OP3.
With OOS 3.2.4 the video lags and the sound is metallic, with others roms, like cm 13 arter kernel pacman op3lite, it doesn't even connect, while the PC and the s4 continue to perform well.
Is there anyone with the same issue or somebody with a solution?

Go to the source code
You are an advanced user. I used to fix Miracast issues at source code level, it seems a good opportunity for you to jump into Kernel driver, wpa_supplicant, android Miracast/WiFi Java framework, and using gdb_client to debug ...

xbing6 said:
You are an advanced user. I used to fix Miracast issues at source code level, it seems a good opportunity for you to jump into Kernel driver, wpa_supplicant, android Miracast/WiFi Java framework, and using gdb_client to debug ...
Click to expand...
Click to collapse
I've never done this before but there is always a first time! I'll try as soon as possibile!! Thank You!

Cm 14 nexus 5x

Hey is there any rom for nexus 5x with android version 7.0
Here are some of the features we expect from CM14 or Cyanogenmod 14
1. CM14 Multi-window Mode
Well, multitasking is the key feature that every user is looking for nowadays. And, CM14 is all set to enhance this feature by multi-window mode that will allow the users to run multiple apps at the same time on the screen. With this split screen feature, you can also drag and drop text in between apps, when required instead of typing the content all over again or copy/pasting either.
Multi-window mode CM14
The app developers have to add support for the split screen mode to make their apps compatible to use this feature on the all-new upcoming CM14 ROM. Users can open apps side by side and resize the app window using a slider and adjust it according to their preferences.
2. New System UI in CM14
Cyanogenmod 14 may follow Android N as it would introduce a completely new User Interface that will not include the famous app drawer. If not, then the latest ROM from Cyanogenmod may allow the option to switch between the two different UIs, one containing the app drawer and the other without it. Such UI are highly favoured and seen on iOS and MIUI devices.
3. CM14 will have a Better Optimized Battery Management
Battery optimization has been the concern for Android developers as well as the community at Cyanogenmod as Android devices are highly criticized for low battery life compared to iOS devices. However, CM14 is expected to enhance its battery optimization feature that would boost the battery life up to 20% with the Doze mode as seen on Android 6.0 Marshmallow.

Cynogenmod is already developing rom for nexus 5x

is there any news about this topic...... if you have plz comment

CM 14 is coming....
I'm going to start making CM 14 UNOFFICIAL for BULLHEAD expect it to be up very soon.. :fingers-crossed: :fingers-crossed:

So which is better with a Rockchip PX5 A53 octa-core, Android 8.0 or 6.0?

Even after reading the mega-threads on the two setups it's hard to decide which is the better way to go, if you have the choice. You can see the new PX5 octa-core units running either 8.0 or 6.0, so which to buy? The issues I see from the posts include:
- 8.0 hasn't been fully rooted, and rooting might be turn out to be difficult
- while 8.0 looks somewhat "fresh" with the not quite so fresh anymore tile styling, it has that ugly sidebar, which will require rooting to get rid of
- it seems to be hard to autorun apps on 8.0, so you can't just start up into a custom launcher
- does 8.0 really have less problems interfacing with hardware? With the variety of WiFi, Bluetooth, volume control, microphone etc. problems described in these threads, is the old establish 6.0 better at handling them, or does it lack drivers for newer versions of things like CAN bus interfaces or Torque BT adaptors?
- seems you need 8.0 for 4GB ram, does that make 8.0 worth it on its own?
It seems an even split for which version manufacturers are putting on these units. And it seems an equal number of people with 6.0 want to upgrade to 8.0 as people with 8.0 who want to downgrade to 6.0.
So to a new buyer, would you say get 8.0 or 6.0? I don't think there are many PX5's with 7.1 for some reason, which is why I left that out.
Thanks!

I thought there would be lots of people with views on this - no strong opinions? I thought this would be the first thing to consider when choosing a unit...no?

Same questions here as well.

I've a Dasaita px5 2gb 6.0 and now, about a month I've upgraded to malaysk 8.0 rom.
So, talking about 8.0:
-Fully rooted, everything works perfectly with supersu in 8.0 too
- Google maps works with 8.0, with 6.0 it doesn't
-Smooth performance even with 2gb ram.
-Spotify doesn't pop up
-Working custom launchers
-Working torque
-Autostart working with malaysk rom
-CANBUS working normally
-Bluetooth quality a2dp better than 6.0 (sd-968 module)
Problems with 8.0:
-some users that use md725 Bluetooth module related that is not working due to missing drivers, but a few users says it's working.
-apps force close when you do fast boot. It's difficult to decompile mtcmanager.apk and write the whitelist to keep apps in memory.
-Google contacts not syncing properly to work with voice command. There are some methods at xda to try to use mtcdialer, but it's not working for everyone. You can use manually touching the contact, but not working properly for voice command.
-EQ is working, but fader and balance not working for me (this issue I don't know if is happening with other users too)
In general, I think that Android 8.0 even with 2gb ram worth it.

Thanks megatm! Exactly the info that will help a lot of people who are trying to decide.
Much appreciated!

[Q] Anyone tried building/compiling Android for Windows RT devices?

Recently I installed Windows 10 RT on my Surface RT.
I think it's better than the Windows 8 RT and most people can agree on that.
Even after having W10 OA, there are not many apps available for this device.
I was wondering if anyone successfully built a version of android that ran on ARM Windows devices. I would like to build one compatible for the Surface RT but there are no kernel sources or device trees available. Also, there is no way to flash it with a conventional flash tool. Therefore, it cannot be built this way. But has anyone tried compiling android x86 but for ARM?
If yes, in which way did you build it?
Or if you built it in another way, in which way did you build it?
I am very interested in building a version for our Surface RT so we can finally get somewhere and get support for almost all of the apps in the android world

alexenferman said:
Recently I installed Windows 10 RT on my Surface RT.
I think it's better than the Windows 8 RT and most people can agree on that.
Even after having W10 OA, there are not many apps available for this device.
I was wondering if anyone successfully built a version of android that ran on ARM Windows devices. I would like to build one compatible for the Surface RT but there are no kernel sources or device trees available. Also, there is no way to flash it with a conventional flash tool. Therefore, it cannot be built this way. But has anyone tried compiling android x86 but for ARM?
If yes, in which way did you build it?
Or if you built it in another way, in which way did you build it?
I am very interested in building a version for our Surface RT so we can finally get somewhere and get support for almost all of the apps in the android world
Click to expand...
Click to collapse
Sounds like a good idea, another option would be to look into the Linux4Tegra side of things, I'm not sure if it supports the Tegra 4 in the Surface2 but if it does we might have some interesting things to draw out of it...

AlGaib said:
Sounds like a good idea, another option would be to look into the Linux4Tegra side of things, I'm not sure if it supports the Tegra 4 in the Surface2 but if it does we might have some interesting things to draw out of it...
Click to expand...
Click to collapse
Actually, there are suprisingly still people working on linux: https://forum.xda-developers.com/wi...-secure-boot-linux-surface-rt-t3653848/page12
First we have to get linux and then we can adapt the kernel and drivers to run android. There are very similar tablets running android like the ASUS Transformer Pad TF502T. If we use this kernel tree and build a device tree, we should get it working. I would try Lineage OS and TWRP. I think we can get maximum android Nougat for this tablet, after that, because of big kernel changes on android oreo+, we have to modify it even more. Forget about android X86. It's not a great idea.
I have compiled android custom roms before, but with all of the sources ready. In this case, we have to build a lot.
CrackTheSurface said:
Android is only a colorful touchy surface which is based on Linux, so at very first we must get Linux running.
The SoC(System on Chip) Tegra3 has Linux kernel mainline support so driver support shouldn't be that much of a problem (I am an optimist :fingers-crossed. Display output should also be possible as far as i know it uses Display Serial Interface (DSI) and is directly connected to the SoC.
The attachable keyboard is connected via i2c HID, which has also Linux kernel suppport. HDMI should also be supported out of box by the kernel. Touchscreen, WiFi, Audio, Bluetooth are the main problem points.
But now must start getting the kernel to run with an command line interface (CLI).
And installing the nvidia graphics drivers and multimedia codecs
Click to expand...
Click to collapse
If anyone wants to help with linux, please do it.

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]

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:
Spoiler: Details:
xinseo said:
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?
Click to expand...
Click to collapse
roirraW edor ehT said:
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:
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
which has a link:
and leads to:
Get Android 13 | Android Developers
Get an Android 13 on your eligible device.
developer.android.com
the Enroll in Android 13 Beta for Pixel button there still leads to:
Android Beta Program
Android Beta Program allows you to enroll your Android device for beta releases.
www.google.com
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.
Click to expand...
Click to collapse
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
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.

Spoiler: OLD News
April 6, 2023:
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.
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 2.1Beta 2Beta 1
Release dateApril 6, 2023BuildT3B2.230316.005Security patch levelMarch 2023Google 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.
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-t3b2.230316.005-factory-3923dd64.zip3923dd6452862974f235d6acbe215773e379351ee7296ffa026f2748fa7056d5
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-ota-t3b2.230316.005-811d7863.zip811d78635bafeaa3d02b3b69ab2dc28109b574c3c511d1df80db32716745f17f
64-bit-only images​
Pixel 6 Proraven_64-t3b2.230316.005-factory-41c2639d.zip41c2639ddcdaddad9cb0b59ba07ff68f9a9767cd4b774bc78ceb866dca8e6597
March 29, 2023:
Android 13 QPR3 Beta 2
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 2Beta 1
Release dateMarch 29, 2023BuildT3B2.230316.003Security patch levelMarch 2023Google Play services23.08.15
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​You can install Android 13 QPR3 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 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.
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-t3b2.230316.003-factory-f0292a27.zipf0292a27135f660dc20f091b044a8ec997a47758e0365ff7721edbec2cb3c82e
64-bit-only images​
Pixel 6 Proraven_64-t3b2.230316.003-factory-fbfbb3b5.zipfbfbb3b515a957dbc77a723b6e66fef17a694cc5fc8ad3506674ade60783f017
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-ota-t3b2.230316.003-2f73a8ea.zip2f73a8eaae652c70af4fc16ac5d414847b6041d68ff1a19cff0cd74ef6da956f
March 15, 2023:
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.
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-t3b1.230224.005-factory-f1dca87c.zipf1dca87c6b2b072a022800edfadad781c066543ffcdd891a2aff36c8cf4ccd1d
64-bit-only images​
Pixel 6 Proraven_64-t3b1.230224.005-factory-fc005de5.zipfc005de5f615dbe4fb9f0a176a6fbd19d182830061294a54ba69379566e99a27
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-ota-t3b1.230224.005-21358b57.zip21358b571506d3a9e3af7e3c63ee9736265dd91b125dc656f4a3cc6869abdcb4
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 1
Release dateMarch 15, 2023BuildT3B1.230224.005Security patch levelMarch 2023Google Play services23.08.15
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 1​You can install Android 13 QPR3 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
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 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.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
Lughnasadh said:
https://twitter.com/i/web/status/1634291746598207488
Click to expand...
Click to collapse
Note @Lughnasadh's post from the Pixel 7 Pro QPR thread, and XDA's article below:
Android 13 QPR3 Beta 1 set to arrive next week
It looks like Google is ready to start its next stage of testing, as it is set to release Android 13 QPR3 Beta 1 next week.
www.xda-developers.com
Android 13 QPR3 Beta 1 set to arrive next week​BYTIMI CANTISANO
PUBLISHED 20 HOURS AGO
It looks like Google is ready to start its next stage of testing, as it is set to release Android 13 QPR3 Beta 1 next week.
Pixel 7 Pro in Snow
Readers like you help support XDA Developers. When you make a purchase using links on our site, we may earn an affiliate commission. Read More.
Well, it looks like Google is ready to move onto the next step of its QPR (Quarterly Platform Release) beta program, announcing that Android 13 QPR3 Beta 1 will be arriving next week. This beta will allow users to get an early look at the Android 13 QPR3 release set to make its debut sometime in June.
The company announced the news through Reddit, giving users an early heads up of what to expect. While it didn't get into the details of what might show up in the beta release, it did state that those enrolled in the current Beta Program would automatically get the latest update when it's released.
Now, one thing to note, and something Google does state, is that in order to be eligible for the stable release of Android 13 QPR2, users will need to manually opt out. Previously, this update was rolled out to those in the Beta Program, but going forward, it looks like if you're enrolled in the beta, you'll just keep receiving beta releases, skipping over the general release of the OS.
While this isn't a big deal, sometimes betas aren't all that stable, so if you are using this on your main device, now might be a perfect time to opt out. Of course, you can always choose to opt out at any time, but by doing so in a beta release cycle you'll be forced to wipe out your device and start fresh. So, if you're having any second thoughts, now's the time to make the change.
Google does have some tips for users ahead of the Android 13 QPR3 Beta 1 release, stating that if you've opted out, just wait until the stable release and apply that update instead of downgrading. The main reason to go this route, and as stated above, is to avoid wiping your device. Now, for the most part, this and any other beta from Google will be released through its Beta Program or you can download and install the beta updates manually too.
Source: Reddit
Click to expand...
Click to collapse
For anyone who doesn't notice Google's official announcement in those above, and what to do if you're on the QPR2 Beta 3.x and want to be on stable:
https://www.reddit.com/r/android_beta/comments/11nz32q
Hi Beta users,
With the release of our final Android 13 QPR2 Beta update a few weeks ago, we are now preparing for our next Beta Program cycle that covers our Android 13 June release (QPR3). Android 13 QPR3 Beta 1 will kick off the week of March 13th. If you take no action and remain enrolled in the Beta Program, you will automatically receive Android 13 QPR3 Beta 1 starting next week.
We are changing our beta release process - to receive the upcoming March QPR2 public stable release, devices currently enrolled in Beta will need to first opt out of the program. Devices that remain enrolled in the Beta Program will receive Android 13 QPR3 Beta 1.
If you prefer to exit the Beta Program and receive the final public March QPR2 update without the need to wipe your data, please do one of the following:
Opt out of the program before March 13th, ignore/don’t apply the downgrade OTA update, and wait for the final public stable release of the March Feature Drop (QPR2) releasing this month. Opting out will not cause a data wipe as long as you don’t apply the downgrade OTA. Note: If you want to immediately return to the latest public version, you can apply the downgrade OTA which will require a data wipe per usual program guidelines.
If you receive the Android 13 QPR3 Beta 1 update, don’t install the update. Instead, first opt out of the program, ignore/don’t apply the downgrade OTA update, and wait for the official March public release. Note: If you opt-out of the program after installing the QPR3 beta 1 update, all user data on the device will get wiped per usual program guidelines.
We will continue to post updates and information on the upcoming Android 13 QPR3 Beta here in this community.
Click to expand...
Click to collapse
February 22, 2023:
QPR2 Beta 3.2:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-t2b3.230109.009-factory-41828679.zip418286794c52deb030bdfa141b4b74036c0334d640f10fdcfca59a50ae8e1258
64-bit-only images​
Pixel 6 Proraven_64-t2b3.230109.009-factory-b87438c1.zipb87438c11839a9ed9ea49e0d44e467d4e7ca381aaf1452063a2b833fac3eeb5c
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-ota-t2b3.230109.009-aa68086b.zipaa68086bea2775f126dee8367f90132bba111361456afc57421eb713737c3e5d
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Beta 3.2Beta 3.1Beta 3Beta 2.1Beta 2Beta 1
Release dateFebruary 22, 2023BuildT2B3.230109.009, T2B3.230109.006.A1 (Pixel 7 Pro only)Security patch levelFebruary 2023Google Play services23.03.13
Android 13 QPR2 Beta 3.2 (February 2023)
This minor update to Android 13 QPR2 Beta 3 includes the following fixes:
Fixed issues that sometimes caused the screen on some devices to flash green or display other visual artifacts. (Issue #260941279, Issue #256052135)
Jio 5G network is now enabled for Pixel 6 and 7 series devices.
If you're already running a beta build, you'll automatically receive an over-the-air (OTA) update to Beta 3.2.
Note: Other known issues listed for the Beta 3 release still apply to Beta 3.2.
Android 13 QPR2 Beta 3.1 (February 2023)
This minor update to Android 13 QPR2 Beta 3 includes the following fixes:
Fixed an issue in the system Bluetooth module that could have allowed for possible out-of-bounds writes due to memory corruption. (Issue #259630761)
Fixed an issue where some Romanian translations were missing from the system image.
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.2​You can install Android 13 QPR2 Beta 3.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 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.
Click to expand...
Click to collapse
February 9, 2023:
Android 13 QPR2 Beta 3.1 (February 2023)
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Android Developers
Platform
Releases
Release notes​bookmark
Beta 3.1Beta 3Beta 2.1Beta 2Beta 1
Release dateFebruary 9, 2023BuildT2B3.230109.004Security patch levelFebruary 2023Google Play services23.03.13
Android 13 QPR2 Beta 3.1 (February 2023)
This minor update to Android 13 QPR2 Beta 3 includes the following fixes:
Fixed an issue in the system Bluetooth module that could have allowed for possible out-of-bounds writes due to memory corruption. (Issue #259630761)
Fixed an issue where some Romanian translations were missing from the system image.
If you're already running a beta build, you'll automatically receive an over-the-air (OTA) update to Beta 3.1.
Note: Other known issues listed for the Beta 3 release still apply to Beta 3.1.
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.1​You can install Android 13 QPR2 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 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.
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-t2b3.230109.004-factory-ac78f322.zipac78f322fd6e21e0651153c59a68eeb0f47c0c36597238bcfaae96da1dfcca9e
64-bit-only images​
Pixel 6 Proraven_64-t2b3.230109.004-factory-5b63aa97.zip5b63aa974cd88c595faa30f03b7bf7fc33ea82e4de003cd26fcfcdbfcc6aae64
OTA:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-ota-t2b3.230109.004-b9e91f27.zipb9e91f278c8e7c775f05fdd822909f70e579714db2e0d9fc880add11ef254ae7
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, 2023BuildT2B3.230109.002Security patch levelJanuary 2023Google 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.
Click to expand...
Click to collapse
January 20, 2023:
Beta 2.1:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Normal system images: Use https://flash.android.com/preview/tm-qpr2-beta2.1
Pixel 6 Proraven-t2b2.221216.008-factory-c3e9aa09.zipc3e9aa097e50614c320df2a81994bb201efc2dba1ef1a07d98fe503be5549c93
64-bit-only images​
Pixel 6 Proraven_64-t2b2.221216.008-factory-7ded64d0.zip7ded64d04ba54f2d08dcfc1fafb5d7992e6d959be137a6a4eec80da4c5275406
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 2.1Beta 2Beta 1
Release dateJanuary 20, 2023BuildT2B2.221216.008Security patch levelJanuary 2023Google Play services22.41.13
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.
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.1​You can install Android 13 QPR2 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 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.
Click to expand...
Click to collapse
January 9, 2023:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-t2b2.221216.006-factory-8e0c382f.zip8e0c382f9e55c898c045eb2426798b4a8f4ecd1cd8477212a919278697642aaa
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-ota-t2b2.221216.006-e69abcb0.zipe69abcb00f54b2426fdee0850c944ad9fe8c8a0338b3accff389162f33eb43d3
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
ARM64+GMSgsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip12a8e1935c6ef46d2d44dea6ea331fa238cb6240bd6df607f6ccb849d619b25cARM64aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zipe508d63f27da01889734d36171dec11f226e2f2bc538526379e2184d51e9ffd3x86_64+GMSgsi_gms_x86_64-exp-T2B2.221216.006-9443277-5255002f.zip5255002f0d1249bb08725c06e3a264d8caaf2d84cdb9c40c7a7a8954249d6493x86_64aosp_x86_64-exp-T2B2.221216.006-9443277-02d675fb.zip02d675fb15c962fa7e35f494edfbfa2da7b886ef3f6e4709b73b1c57fb96b8ab
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 2Beta 1
Release dateJanuary 9, 2023BuildT2B2.221216.006Security patch levelJanuary 2023Google 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.
Click to expand...
Click to collapse
December 12, 2022:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-t2b1.221118.006-factory-58c7ef5d.zip58c7ef5d1046627cfedf6fe53e7dca554001893d4c5f27a685a50e77c635a8ec
64-bit-only image:
Pixel 6 Proraven_64-t2b1.221118.006-factory-1a296844.zip1a2968448da3484cdde71faa66bd71ba2fdd051cc88e02cbae548c32e8d658e7
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 1
Release dateDecember 12, 2022BuildT2B1.221118.006Security patch levelDecember 2022Google Play services22.39.10
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 1​You can install Android 13 QPR2 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
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 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 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 the 1/8x and 1/4x while in Slow Motion mode.
Click to expand...
Click to collapse

For historical reference:
Spoiler: Really old news from OP
Spoiler: OLD (November 7, 2022)
November 7, 2022:
Factory images for Google Pixel | Android Developers
Instructions for downloading and installing QPR Beta system images for Pixel devices
developer.android.com
Pixel 6 Proraven-t1b3.221003.008-factory-6454afed.zip6454afed8f49ed1f08acaf49bd4a86ff28812b5624029c91aa6346d511b7f26c
OTA images for Google Pixel | Android Developers
Instructions for downloading and installing QPR beta system images for Pixel devices
developer.android.com
Pixel 6 Proraven-ota-t1b3.221003.008-2f799487.zip2f7994875425cbe924afae7da68ae876b7ce0545f831f052f3a27635a8f3f82e
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​Beta 3.1 Beta 3 Beta 2 Beta 1
Release dateNovember 7, 2022BuildT1B3.221003.008Security patch levelNovember 2022Google 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.
Click to expand...
Click to collapse
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!
Click to expand...
Click to collapse
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.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-t1b3.221003.003-factory-b5d06db1.zipb5d06db19ff712a0d478b9ce664980eb96cbd893a62111ed53b27f6af3b4aa02
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-ota-t1b3.221003.003-8b704cc5.zip8b704cc51fd72b0079589ae4088a6dd6122da936882d46b752dfb2ffc25fa5d8
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 3Beta 2Beta 1
Release dateOctober 20, 2022BuildT1B3.221003.003Security patch levelOctober 2022Google 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 .
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.
Click to expand...
Click to collapse
Android 13 QPR1 beta 2 discussion starts here.
Spoiler: OLD (October 5 2022)
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-t1b2.220916.004-factory-b4c16abf.zipb4c16abfc3a5237ac6412b650705ee255964a7b5b5a9a684eb22bbb678196c1d
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-ota-t1b2.220916.004-159ff0cd.zip159ff0cd49711b694905d1a297a2b8ee9ac6fde262dbd48b1332b3a9b1367bdc
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark_border
Beta 2Beta 1
Release dateOctober 5, 2022BuildT1B2.220916.004Security patch levelOctober 2022Google 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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
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.
Click to expand...
Click to collapse
Android 13 QPR1 beta 1 discussion starts here.
Spoiler: "Old" Android 13 QPR1 Beta 1 stuff
Lughnasadh said:
"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.
Android Beta Program
Android Beta Program allows you to enroll your Android device for beta releases.
www.google.com
Click to expand...
Click to collapse
Android Beta Program
Android Beta Program allows you to enroll your Android device for beta releases.
www.google.com
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.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
You only have a short window to opt out of the Android Beta Program now without data loss
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
Android 13 QPR1 Beta 1 rolling out to Pixel phones
Like last year, Google is continuing the Android 13 Beta Program with Quarterly Platform Releases, starting with QPR1 this September.
9to5google.com
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.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
or
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6a: Factory Image — OTA
Pixel 6 Pro: Factory Image — OTA
Pixel 6: Factory Image — OTA
Pixel 5a: Factory Image — OTA
Pixel 5: Factory Image — OTA
Pixel 4a (5G): Factory Image — OTA
Pixel 4a: Factory Image — OTA
Google has released Android 13 QPR1 Beta 1
Google has released Android 13 QPR1 Beta 1 for supported Pixel Devices, bringing improvements and fixes to Android 13.
www.xda-developers.com
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
Click to expand...
Click to collapse
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark_border
NotificationsSave this page to your Developer Profile to get notifications on important updates.
DismissNext
Beta 1
Release dateSeptember 8, 2022BuildT1B1.220819.006, T1B1.220819.007 (Pixel 6a only)Security patch levelSeptember 2022Google 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
.
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.
Click to expand...
Click to collapse
Android 13 Final looks to be OUT!
Spoiler: OLD (August 15, 2022)
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TP1A.220624.021, Aug 2022)FlashLinkd8ddfdca3af0b97b3b99460afdab3cf95a741f988dccd5122564c855a64baa36
Click to expand...
Click to collapse
Please take discussion of this to my other thread now that it appears to be Final.
I've consolidated the still working (as of August 24, 2022) download links here for convenience:
Spoiler: All Beta version download links
13 Beta 4.1:
Pixel 6 Proraven-tpb4.220624.008-factory-eecbcf50.zip
eecbcf5012785c409433fe2dc2cbac31431751af7414c47f3beb6381035c37d6
Beta 4:
Pixel 6 Proraven-tpb4.220624.005-factory-e06d65e2.zipe06d65e242faaad12f3bcc0a70441afda192475bfb9e699e944e757d80f820ad
Beta 3.3:
Pixel 6 Proraven-tpb3.220617.002-factory-1acb43a3.zip1acb43a3d082b8d2cd16cba834c1b1de25042c5d5122483bbf54ff4a16682186
Click to expand...
Click to collapse
Beta 3.2:
Pixel 6 Proraven-tpb3.220610.004-factory-f1c00e48.zipf1c00e4815ea7db4575f7e3e20a45d3ee867672ac628e5a031e3e0979a3a2d18
Beta 3.1:
Pixel 6 Proraven-tpb3.220513.017.b1-factory-92adb5f3.zip92adb5f3a252a4f58bb682a3f1a24c66fd353ade948eb3a72355b3f8822ef941
Click to expand...
Click to collapse
Beta 3:
Pixel 6 Proraven-tpb3.220513.017-factory-0300106f.zip0300106f81437076be26b670b32b1ab8099eaf4ab9a9bb871c2049f1213a547a
Click to expand...
Click to collapse
Beta 2:
DeviceOTAFactory Image
Google Pixel 6 ProDownload LinkDownload Link
Click to expand...
Click to collapse
Beta 1:
Google Pixel 6 ProOTA Download LinkFactory Image Download Link
Spoiler: Old stuff
You can easily download Android Developer Beta 3, and be sure to check out our guide on how to install Android 13 if you’re unsure of how to do so.
Click to expand...
Click to collapse
Android 13 Beta 4!
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-tpb4.220624.005-factory-e06d65e2.zipe06d65e242faaad12f3bcc0a70441afda192475bfb9e699e944e757d80f820ad
Android 13 inches closer to public release as final beta rolls out for Pixels
Android 13 is inching closer to its public release, as the final beta has rolled out for Google Pixel smartphones now.
www.xda-developers.com
July 13, 2022 1:00pm Comment Adam Conway
Android 13 inches closer to public release as final beta rolls out for Pixels​Android 13 is just around the corner, as Google has just announced that the final beta version of the next major Android platform is finally here. There aren’t any new features that Google has highlighted, but this build is particularly special — Android 13 Beta 4 is the release candidate build for both Google Pixel devices and the Android Emulator. That means it primarily packs bug fixes and other polishes, though we imagine there’ll be some changes under the hood that haven’t been highlighted.
When will Android 13 release?​
For Android updates, Google typically reveals a “platform stability” milestone so that developers can know when Google intends on delivering the final SDK/NDK APIs, along with final internal APIs and app-facing system behaviors. Android 13 Beta 3 brought us to platform stability, bringing us on track for a stable public release very soon. For context, Android 12 hit platform stability in August of 2021, and the final version was released in October of that year. This release is a release candidate build, meaning that it should be fairly stable if you can’t wait to try it out.
What’s new in Android 13 Beta 4?​To be honest, there’s nothing surface level that Google has highlighted. The company says that this build gives developers “everything you need to complete your testing”. It’s primarily for bug fixing and software polishing, and while you may notice stability improvements, it’s unlikely that there’s any major that will have changed. Google says developers should, in particular, prepare for the following changes:
Runtime permission for notifications: The latest version of Android introduces a new runtime permission for sending notifications from an app. Make sure you understand how the new permission works, and plan on targeting Android 13 (API 33) as soon as possible. More here.
Clipboard preview: Make sure your app hides sensitive data in Android 13’s new clipboard preview, such as passwords or credit card information. More here.
JobScheduler prefetch: JobScheduler now tries to anticipate the next time your app will be launched and will run any associated prefetch jobs ahead of that time. If you use prefetch jobs, test that they are working as expected. More here.
Google also announced that information about the final release of Android 13 will be available “in the weeks ahead”.
How to download and install Android 13 Beta 4 on your Google Pixel device​You can easily download Android 13 Beta 4 for your Pixel devices and follow our guide on how to install Android 13 to set it up. Google is officially releasing this beta update for the Pixel 6 Pro, Pixel 6, Pixel 5a 5G, Pixel 5, Pixel 4a (5G), Pixel 4a, Pixel 4 XL, or Pixel 4. You can use the 64-bit system images with the Android Emulator in Android Studio, and you can also use a GSI too.
To learn more about the fourth and final beta release, head over to the official blog post on the Android Developers blog.
Click to expand...
Click to collapse
Yet another Beta of 13, Beta 3.3:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 6 Proraven-tpb3.220617.002-factory-1acb43a3.zip1acb43a3d082b8d2cd16cba834c1b1de25042c5d5122483bbf54ff4a16682186
Click to expand...
Click to collapse
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
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:
API 32 → API 33
Beta 2 → API 33
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.
Click to expand...
Click to collapse
Google rolls out Android 13 Beta 3.3 with a bunch of bug fixes
Google is rolling out Android 13 Beta 3.3 to address a few bugs that were present in the previous beta release. Check out the changelog!
www.xda-developers.com
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
Click to expand...
Click to collapse
Android 13 Beta 3.3 brings the new Android 13 easter egg
Along with a host of bug fixes, Android 13 Beta 3.3 also brings the new Android 13 easter egg. Here's how you can access it on your Pixel device.
www.xda-developers.com
June 28, 2022 10:50am Comment Pranob Mehrotra
Android 13 Beta 3.3 brings the new Android 13 easter egg​After releasing Android 13 Beta 3.2 earlier this month, Google rolled out another beta build to the Pixel lineup this week. The latest release, Android 13 Beta 3.3, addressed several bugs, including slow UI rendering, inability to connect to a Wi-Fi network, system UI crashes, and more. While Google’s official changelog did not highlight any other changes, recent reports suggest that the update also includes the Android 13 easter egg.
If you’ve just updated your Pixel device to Android 13 Beta 3.3, you can now access the Android 13 easter egg on your phone. To do so, head over to the About Phone section in the device settings and tap on the Android version repeatedly. This should open up the same UI that you got with the Android 12 easter egg. If you move the clock hands to the 1 o’clock position, the Android 13 logo will pop up on the clock face with the Material You Dynamic Color bubbles in the background. But that’s not all.
If you tap and hold the bubbles, they’ll change into emoji. You can then long-press the emoji to cycle through fourteen thematic sets. These include: Fruit, Cat faces, Regular faces, Expressive (eye) faces, Melting face, Hearts/love, Outer space, Moon, Aquatic life, Monkeys, Zodiac, Clocks, Flowers, and Turtle king.
At the moment, it isn’t clear whether Google plans to a new easter egg widget as it did with Android 12. We’ll make sure to let you know as soon as we have more details.
What do you think of the new Android 13 easter egg? Which one of the fourteen emoji sets is your favorite? Let us know in the comments section below.
Via: 9to5Google
Click to expand...
Click to collapse
New Android 13 Beta 3.2:
Pixel 6 Proraven-tpb3.220610.004-factory-f1c00e48.zipf1c00e4815ea7db4575f7e3e20a45d3ee867672ac628e5a031e3e0979a3a2d18
https://developer.android.com/about/versions/13/release-notes
Release notes​
Beta 3.2Beta 3.1Beta 3
Release date: June 16, 2022
Build: TPB3.220610.004
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: June 2022
Google Play services: 22.18.19
API diff:
API 32 → API 33
Beta 2 → API 33
Android 13 Beta 3.2 (June 2022)
If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 3.2.
This minor update to Android 13 Beta 3 includes stability improvements as well as the following fixes:
Fixed an issue where the back gesture wasn't working in some apps.
Fixed an issue where the At a glance settings page would collapse inconsistently when scrolling.
Fixed an issue where some apps would crash instantly on opening.
Fixed an issue where the microphone would turn on and off unexpectedly during unrelated use of the device.
Fixed an issue where the Google Photos app would crash frequently.
Click to expand...
Click to collapse
Android 13 Beta 3.2 arrives with important bug fixes
Android 13 Beta 3.2 has arrived with a bunch of important bug fixes that improve the stability of your smartphone. Check it out!
www.xda-developers.com
June 16, 2022 6:54pm Comment Adam Conway
Android 13 Beta 3.2 arrives with important bug fixes​Android 13 is almost here, and the most recent beta update, Beta 3, arrived bringing finalized APIs. We’ve already had one hotfix update arrive since then, and now Google is in with a second one for you to download and install on your Google Pixel. This update packs a ton of major bug fixes that you might want to install as soon as you can!
When will Android 13 release?​
For Android updates, Google typically reveals a “platform stability” milestone so that developers can know when Google intends on delivering the final SDK/NDK APIs, along with final internal APIs and app-facing system behaviors. Google reached platform stability with the Beta 3 update, and there are several weeks at minimum planned before the official release. Android 12 hit platform stability in August of 2021 and the final version was released in October of that year. Google has released more details about the release timeline that you can check out.
What’s changed in Android 13 Beta 3.2?​The fixes are as follows:
Fixed an issue where the back gesture wasn’t working in some apps.
Fixed an issue where the At a glance settings page would collapse inconsistently when scrolling.
Fixed an issue where some apps would crash instantly on opening.
Fixed an issue where the microphone would turn on and off unexpectedly during unrelated use of the device.
Fixed an issue where the Google Photos app would crash frequently.
Note that the other known issues listed for the Beta 3 release still apply to Beta 3.2, and it just seems to be the case that Google deemed these ones to be a higher priority and fixed them in between beta releases.
This is very much a minor release, but it’s good that Google is focusing on improving the beta experience for users that have opted to use it. These builds are designed to be used by users who want to try out the next version of Android, so while you shouldn’t use it on your daily driver, I’m sure plenty of users do. As a result, some of these are pretty problematic bugs that could have caused issues for people.
How to download and install Android 13 Beta 3.2 on your Google Pixel device​You can easily download Android Developer Beta 2.1, and be sure to check out our guide on how to install Android 13 if you’re unsure of how to do so. If you already have a previous beta, then you will receive the update via OTA.
Google is officially releasing this beta update for the Pixel 6 Pro, Pixel 6, Pixel 5a 5G, Pixel 5, Pixel 4a (5G), Pixel 4a, Pixel 4 XL, or Pixel 4. You can use the 64-bit system images with the Android Emulator in Android Studio too.
Source: /r/android_beta
Click to expand...
Click to collapse
Beta 3.1:
The filename and hash of the latest Android 13 beta 3 for all devices just changed (only slightly for the filename). I confirm that the new zip file and the old one for Beta 3 have a different hash (I won't be flashing it):
Factory images for Google Pixel | Android Developers
Instructions for downloading and installing QPR Beta system images for Pixel devices
developer.android.com
Pixel 6 Proraven-tpb3.220513.017.b1-factory-92adb5f3.zip92adb5f3a252a4f58bb682a3f1a24c66fd353ade948eb3a72355b3f8822ef941
Click to expand...
Click to collapse
OLD Beta 3.0:
Pixel 6 Proraven-tpb3.220513.017-factory-0300106f.zip0300106f81437076be26b670b32b1ab8099eaf4ab9a9bb871c2049f1213a547a
Click to expand...
Click to collapse
Google Pixel 6 ProDownload LinkDownload Link
Click to expand...
Click to collapse
Android 13 reaches Platform Stability milestone with Beta 3 release
Google today released the third beta build of Android 13. With Android 13 Beta 3, the new release had finally hit the Platform Stability milestone.
www.xda-developers.com
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Beta 2:
https://www.xda-developers.com/how-to-download-android-13/#beta2
Android 13 Beta 2 (TPBB.220414.015)For eligible Google Pixel devices, you can download the second beta build of Android 13 from the index below:
DeviceOTAFactory Image
Google Pixel 6 ProDownload LinkDownload Link
Click to expand...
Click to collapse
You can also download the official Generic System Image (GSI) packages from the index below:
GSI Downloads​
ArchitectureGSI Packagex86_64+GMSDownload LinkARM64+GMSDownload Linkx86_64Download LinkARM64Download Link
Click to expand...
Click to collapse
Android 13 Beta 2 is here with a new predictive back gesture
Android 13 Beta 2 is now here for Google Pixel devices, and it introduces a predictive back gesture for developers to implement.
www.xda-developers.com
OLD:
Android 13 Beta 1 (TPB1.220310.029)​
Google Pixel 6 ProOTA Download LinkFactory Image Download Link
GSI Downloads​
ArchitectureGSI Packagex86_64+GMSDownload LinkARM64+GMSDownload Linkx86_64Download LinkARM64Download Link
Android 13 Beta 1 is here with better media file permissions
Android 13 Beta 1 is here, and it brings more granular access to media files, better error reporting, and anticipatory audio routing.
www.xda-developers.com
Android 13 'Tiramisu': Everything you need to know about Google’s big 2022 update
Android 13 was unleashed upon the world last year, but it's still rolling out to devices, along with betas and bug fixes.
www.xda-developers.com

Luv the name have enjoyed as a great dessert especially with Expresso traveling in Italy!

galaxys said:
Luv the name have enjoyed as a great dessert especially with Expresso traveling in Italy!
Click to expand...
Click to collapse
I didn't even know that Google was still using dessert names internally only, although the internal names didn't always match the officially released names when they had them. I had to Google to see if Tiramisu was official or not.
Android 12 Brings Back Dessert Names For Google OS; Will Be Called "Snow Cone"

roirraW "edor" ehT said:
I didn't even know that Google was still using dessert names internally only, although the internal names didn't always match the officially released names when they had them. I had to Google to see if Tiramisu was official or not.
Android 12 Brings Back Dessert Names For Google OS; Will Be Called "Snow Cone"
Click to expand...
Click to collapse
Yeh, it looks like Google had to submit to the public pressure to bring back the yummy name's.... for now! Stay tuned Cheers

Anyone have Feature Flags blank?

They left out the coolest, though not really useful feature. You can run full VMs of Windows and Linux on it.

TonikJDK said:
They left out the coolest, though not really useful feature. You can run full VMs of Windows and Linux on it.
Click to expand...
Click to collapse
It was a separate article.

Factory images for Google Pixel | Android Developers
Instructions for downloading and installing QPR Beta system images for Pixel devices
developer.android.com
raven-tpp2.220218.010-factory-79bf5fe3.zip
SHA-256 hash: 79bf5fe3c1b169c52de4e0bd212a2693c89b4f5d0a263c17d34dfcaaec4bd841
Android 13 Developer Preview 2 arrives with notification permission requests and other changes
Android 13 Developer Preview 2 is here, and it packs notification permission requests and developer productivity improvements. Check it out.
www.xda-developers.com
March 17, 2022 1:00pm Comment Adam Conway
Android 13 Developer Preview 2 arrives with notification permission requests and other changes​
February saw the release of the first Android 13 Developer Preview, and with it came the groundwork for the next iteration of the world’s biggest operating system. It brought along a number of changes that benefit developers and made improvements to privacy, Material You, language controls, and more. Now the company has announced the second developer preview, and it has some additional features and lots of improvements over the previous developer preview.
As the title “Developer Preview” implies, these releases are intended for usage by developers only. It’s for testing out new features and making sure that their apps work on updated devices as they’re supposed to. There are going to be bugs, there are going to be other problems, and Google will be pushing for feedback from developers over the coming months. If you don’t mind running into problems, then, by all means, give Android 13 a try. However, if you rely on your smartphone being consistently stable, then it might be worth waiting for the full Android 13 release that’s expected to launch in the latter half of the year.
The most notable features of Android 13 developer preview 2 include:
Notification permission requests
Developers can now downgrade their permissions
A ton of developer productivity improvements
When will Android 13 release?​
For Android updates, Google typically reveals a “platform stability” milestone so that developers can know when Google intends on delivering the final SDK/NDK APIs, along with final internal APIs and app-facing system behaviors. Google intends on reaching platform stability in June 2022, with several weeks at minimum planned before the official release. Android 12 hit platform stability in August of 2021 and the final version was released in October of that year. Google has released more details about the release timeline that you can check out.
Privacy and security​Google knows that users want an operating system that they can trust with their data. After all, smartphones have reached the point where they are effectively an extension of ourselves and our own lives in a lot of ways. We use them for storing important photos, having private conversations with friends and family, and carrying them with us day to day with the trust that microphones or cameras aren’t recording every interaction. We’ve seen changes for Android 13’s permissions system (amongst other changes) introduced in Android 13 Developer Preview 1, and Developer Preview 2 expands on that.
Notification permission​Android 13 introduces a new runtime permission for sending notifications from an app: POST_NOTIFICATIONS. Apps that target Android 13 will now need to request permission from the user in order to push notifications. For apps that target Android 12 or lower, the system will handle the upgrade flow, but users will still see a system dialog that they need to accept or decline to allow for an app to push notifications. Google is encouraging developers to target Android 13 as early as possible and request the notification permission in their apps.
Developer downgrade permissions​Sometimes when apps are updated, they don’t need older permissions that were once previously granted. Android 13 is introducing a new API that will allow developers to downgrade previously granted runtime permissions.
Safer exporting of context-registered receivers​Android 12 introduced and required developers to declare the exportability of Intent receivers declared in the Android Manifest. Google is now asking developers to do the same for context-registered receivers by adding either the RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED flag when registering receivers for non-system sources. These won’t be required in Android 13 but are highly recommended for developers to enable.
Developer productivity​Android wouldn’t be what it is without developers, and every platform update usually brings updates that make the lives of developers easier. Some updates definitely make it more difficult, but Google generally tries to streamline the development process of apps with every iteration.
Improved Japanese text wrapping​Android 13 DP1 introduced improvements to TextView text wrapping, and now some improvements are being introduced specifically for Japanese text. This time around, TextViews can now wrap text by Bunsetsu (the smallest unit of words that sounds natural) or phrases — instead of by character — for more polished and readable Japanese applications. You’ll just need to enable android:lineBreakWordStyle=”phrase” with TextViews.
Japanese text wrapping with phrase style enabled (below) and without (above)
Improved line heights for non-Latin scripts​In, Android 13 non-Latin scripts (such as Tamil, Burmese, Telugu, and Tibetan) are displayed by using a line height that’s adapted for each language. This prevents clipping and improves text positioning, and all an app needs to do to implement these improvements is target Android 13.
Text Conversion APIs​People who speak languages like Japanese and Chinese use phonetic lettering input methods, which can slow down searching and features like auto-completion. In Android 13, apps can call the new text conversion API so users can find what they’re looking for faster and easier. Previously, searching in Japanese required the user to do the following:
Input Hiragana as the phonetic pronunciation of their search term (i.e. a place or an app name)
Use the keyboard to convert the Hiragana characters to Kanji,
Re-search using the Kanji characters
Get their search results.
With the new text conversion API, Japanese users can type in Hiragana and immediately see Kanji search results live, skipping the middle two steps.
Color vector fonts​Android 13 adds rendering support for COLR version 1 fonts and updates the system emoji to the COLRv1 format. COLRv1 is a new and highly-compact font format that renders quickly and crisply at any size. For most apps, the system handles everything and COLRv1 just works. Google recommends testing emoji rendering if your app implements its own text rendering and uses the system fonts. You can read more about COLRv1 in the Chrome announcement when it was announced with Chrome OS 98.
Bluetooth LE Audio​Bluetooth Low Energy Audio is, as the name suggests, a low-energy way to transmit audio over Bluetooth. Android 13 brings official support for it.
MIDI 2.0​Android 13 also adds support for the new MIDI 2.0 standard, including the ability to connect MIDI 2.0 hardware through USB. MIDI 2.0 offers improvements such as increased resolution for controllers, better support for non-Western intonation, and more expressive performance using per-note controllers.
How to download and install Android 13 Developer Preview 2 on your Google Pixel device​You can easily download Android Developer Preview 2, and be sure to check out our guide on how to install Android 13 if you’re unsure of how to do so.
Google is officially releasing this developer preview update for the Pixel 6 Pro, Pixel 6, Pixel 5a 5G, Pixel 5, Pixel 4a (5G), Pixel 4a, Pixel 4 XL, or Pixel 4. You can use the 64-bit system images with the Android Emulator in Android Studio, and you can also use a GSI too.
Click to expand...
Click to collapse
Android 13 Developer Preview 2 brings the app drawer to the taskbar
Android 13 updates the taskbar on large-screen devices with a new button to open the app drawer without going to the home screen.
www.xda-developers.com
March 17, 2022 2:18pm Comment Corbin Davenport
Android 13 Developer Preview 2 brings the app drawer to the taskbar​
Android 13 Developer Preview 2 was just released on Thursday, with another round of new features and changes leading up to the final release of Android 13 later this year. Google highlighted some of the changes in the new build when it arrived, but it seems there’s another helpful improvement: an app drawer in the taskbar on large screen devices.
The recent Android 12L update (also known as Android 12.1) adds a taskbar to the bottom of some large-screen devices, including some tablets and foldable phones, which is still present in Android 13. However, as Esper’s Mishaal Rahman pointed out in a tweet, there’s now an additional icon in the taskbar that opens the app drawer.
Credit: Mishaal Rahman
The taskbar opened from the app drawer might not be as full-featured as the the drawer in your home screen launcher of choice — for example, there doesn’t appear to be a search bar right now. Still, it will give you the option of opening another new application without going back to the home screen or asking Google Assistant, similar to the Edge panel on Galaxy phones and other similar custom features. This also brings taskbar-equipped Android closer in functionality to Windows or Chrome OS, both of which organize all your apps in a button accessible from the taskbar.
Android 13 Developer Preview 2 also adds runtime permissions for app notifications, improved Japanese text wrapping, a new Text Conversion API for languages like Japanese, COLR fonts, MIDI 2.0, Bluetooth LE Audio, and other changes. Check out our main Android 13 Developer Preview 2 coverage for more information and the download links for Pixel devices.
Google is expected to release the first Android 13 Beta sometime in April, with a stable release arriving sometime after July. Android 12 arrived in October of last year, and Android 11 was released in September 2020, so the schedule for Android 13 will likely follow the same pattern.
Click to expand...
Click to collapse

roirraW edor ehT said:
Android 13 Developer Preview 2 arrives with notification permission requests and other changes
Android 13 Developer Preview 2 is here, and it packs notification permission requests and developer productivity improvements. Check it out.
www.xda-developers.com
Click to expand...
Click to collapse
Anyone give this a go yet?

scott.hart.bti said:
Anyone give this a go yet?
Click to expand...
Click to collapse
Yes, and rooted. Seems to be working fine so far, but I've only been on it for about a half hour. Don't see any major issues yet. Only thing is that I can't access recents with Nova Launcher from the home screen, I have to be in settings or an app. Pixel launcher works fine.

Just clarifying.. I think I read someone ota'd dp1 on their phone , but many others bricked theirs due to not having unlocked bootloader. This is still not loadable if you are carrier/bootloader locked, right?

This includes the 12L/QPR modem but I need to poke around. Would go a long way to helping me confirm that even if a modem has the same major version, different branches can have different functionality and minor versions.

Anybody know if I can flash full 13 DP2 image if I’m on 12L B3 locked boot loader via flash tool seeing as I can’t opt out of the 12L beta as won’t roll back to stable Feb and who knows when stable march update will drop ,thanks

DoobyDroid said:
Anybody know if I can flash full 13 DP2 image if I’m on 12L B3 locked boot loader via flash tool seeing as I can’t opt out of the 12L beta as won’t roll back to stable Feb and who knows when stable march update will drop ,thanks
Click to expand...
Click to collapse
I keep hearing its possible, but I heard horror stories last month of bricked bootloaders. Can anyone respond? I have heard it is because some people used fastboot?

Doug8796 said:
I keep hearing its possible, but I heard horror stories last month of bricked bootloaders. Can anyone respond?
Click to expand...
Click to collapse
Yes I’ve previously opted out of 12L beta and had the message no OS installed as it can’t roll back to stable feb you need to wait for the delayed stable march but after turning off and leaving when it rebooted it just booted back into 12L B3 just wondered if poss to flash 13 DP2 via the flash tool without going back to stable 12 and if I need to unlock boot loader first etc

As far as I know if you flash like normal ota it works. ryenreid got his working on the discord.

Doug8796 said:
Just clarifying.. I think I read someone ota'd dp1 on their phone , but many others bricked theirs due to not having unlocked bootloader. This is still not loadable if you are carrier/bootloader locked, right?
Click to expand...
Click to collapse
If you have an unlocked bootloader but actually Opt into the Beta through Google's site at https://www.google.com/android/beta then I believe any phone should be able to get it.
Big However, though - not recommended to do that with a locked bootloader since if it doesn't work for you, there's no way to flash back to Stable. You have to stick with the DP/Beta ride until it's Stable.
You can opt-out of the Beta, but that would normally either factory reset your device when it flashes your device back to Stable, but I seem to recall for those with a locked bootloader that they couldn't find a way back to Stable even considering that caveat.
What @DoobyDroid says below:
DoobyDroid said:
Yes I’ve previously opted out of 12L beta and had the message no OS installed as it can’t roll back to stable feb you need to wait for the delayed stable march but after turning off and leaving when it rebooted it just booted back into 12L B3 just wondered if poss to flash 13 DP2 via the flash tool without going back to stable 12 and if I need to unlock boot loader first etc
Click to expand...
Click to collapse
DoobyDroid said:
Anybody know if I can flash full 13 DP2 image if I’m on 12L B3 locked boot loader via flash tool seeing as I can’t opt out of the 12L beta as won’t roll back to stable Feb and who knows when stable march update will drop ,thanks
Click to expand...
Click to collapse
Doug8796 said:
I keep hearing its possible, but I heard horror stories last month of bricked bootloaders. Can anyone respond? I have heard it is because some people used fastboot?
Click to expand...
Click to collapse
No, see above.

I'm gonna ride or die with it , not going to opt out. I hear there is a custom dp1 that I need with unlocked bootloader? I hear different things.. Can I not just install ota like normal?