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]

[acwcanada]

New magisk canary 24.312 doesn't seem to boot for me. Anyone else having problems?

Same as you, I got into bootloops. But then I flash the A13B2 factory image without wipe to make it booting normally, then I flash the boot.img which patched with 24312 to retain the root. Tried rebooting a few time afterwards, now it seems running fine. No idea why it got into boot loops when it was updated from 24310 to 24312 in the first reboot.

 

[Gordietm]

Same as you, I got into bootloops. But then I flash the A13B2 factory image without wipe to make it booting normally, then I flash the boot.img which patched with 24312 to retain the root. Tried rebooting a few time afterwards, now it seems running fine. No idea why it got into boot loops when it was updated from 24310 to 24312 in the first reboot.

How did you patch the boot image with 24312 if you couldn't get it to boot. I haven't been able to do that.

 

[acwcanada]

How did you patch the boot image with 24312 if you couldn't get it to boot. I haven't been able to do that.

Like I told you I flash the full factory image without wipe to keep my data, then it reboot into the system without root, then just extract and patch the factory boot.img with 24312, then adb flash the patched boot.img

 

[Gordietm]

Like I told you I flash the full factory image without wipe to keep my data, then it reboot into the system without root, then just extract and patch the factory boot.img with 24312, then adb flash the patched boot.img

Yes, I had to flash the factory image without wiping to get my phone to boot after it was bootlooping with 24312. But magisk reverts back to 24310 ant then asks me to update to 24312 again. So I would be patching the boot image to the same patched image I already have.

 

[acwcanada]

Yes, I had to flash the factory image without wiping to get my phone to boot after it was bootlooping with 24312. But magisk reverts back to 24310 ant then asks me to update to 24312 again. So I would be patching the boot image to the same patched image I already have.

A little bit differ compare with yours, after flash the factory image and then reboot, I found that my Magisk is on version 24312. Seems I am luckier than you when it was updating from 24310 to 24312, mine is completed the update then some problems caused it boot loops, you update properly was not fully completed. I would suggest that you download 24312 and manually install it instead of use the auto update.

 

[Gordietm]

A little bit differ compare with yours, after flash the factory image and then reboot, I found that my Magisk is on version 24312. Seems I am luckier than you when it was updating from 24310 to 24312, mine is completed the update then some problems caused it boot loops, you update properly was not fully completed. I would suggest that you download 24312 and manually install it instead of use the auto update.

Nevermind, I got it. Thanks for your help.

 

[cultofluna]

I can confirm patching stock boot with latest canary and flashing on fastboot working ..
Updating through the magisk app( direct install)... leading to bootloop....

 

[wera750]

I thought beta 2 brought in predictive back? Why can't we find it?

 

[Lughnasadh]

No problem updating from Canary 24310 to 24312 using the direct install method on A13B2.

 

[exocetdj]

Hi - sorry, probably wrong place but we are discussing 24312 and a13

I was trying to get v4a working today but obviously that's no go it seems but coincidentally i noticed that 24312 has a new sepolicy injection mechanism - will that help in anyway with v4a?

I'm just brainstorming really as don't want to spend more than the time it takes to do a wet fart on this tbh

Other than lack of v4a - im finding a13 pretty decent and have been using it for a few days solidly now

 

[Lughnasadh]

Hi - sorry, probably wrong place but we are discussing 24312 and a13

I was trying to get v4a working today but obviously that's no go it seems but coincidentally i noticed that 24312 has a new sepolicy injection mechanism - will that help in anyway with v4a?

I'm just brainstorming really as don't want to spend more than the time it takes to do a wet fart on this tbh

Other than lack of v4a - im finding a13 pretty decent and have been using it for a few days solidly now

I haven't seen anyone who has gotten V4A working on A13 yet. The only change from 24310 to 24312 aside from adding the debug channels is the "Extract vbmeta from footer" commit as far as I can tell.

The new sepolicy injection methods occurred earlier and didn't make a difference in getting V4A working, for me at least.

 

[exocetdj]

I haven't seen anyone who has gotten V4A working on A13 yet. The only change from 24310 to 24312 aside from adding the debug channels is the "Extract vbmeta from footer" commit as far as I can tell.

The new sepolicy injection methods occurred earlier and didn't make a difference in getting V4A working, for me at least.

thanks for the reply man - my eyes skipped the relevant log for 24312 it seems haha

yep it was on 24310

Im glad im not the only one trying and will keep my ears to the floor

 

[exocetdj]

direct install from 24310-12 worked flawlessly here

 

[LLStarks]

App/universal searching is bugged?

The fingerprint reader is much better now. But I wonder if it's just the new and far more deliberate enrollment procedure.

 

[Bwyan Benton]

I thought beta 2 brought in predictive back? Why can't we find it?

You won't see that until the final release of android 13

 

[roirraW "edor" ehT]

Android 13 Beta 3 will bring native support for braille displays

The upcoming Android 13 beta will bring native support for braille displays, allowing deafblind users to more easily access their smartphones.

www.xda-developers.com

May 20, 2022 6:29am Comment Kishan Vyas

Android 13 Beta 3 will bring native support for braille displays​

Over the years, Google has added many features to Android to make the operating system more accessible to people with special needs. For instance, Andriod 10 brought Live Caption and Live Transcribe, while Android 12 added a new feature called Camera Switches, allowing users to control their phones with facial expressions. As part of this continued push, Google will be adding native support for braille displays in Android 13.
In a blog post on Thursday, Google announced that the upcoming Android 13 beta release would bring out-of-the-box support for braille display. For the unaware, a refreshable braille display is an electro-mechanic device that surfaces information by raising round-tipped pins through holes in a flat surface. It enables blind and deafblind users (who can’t use a screen reader) to access smartphones or computers. It has always been possible to use a braille display on Andriod using the Talkback app. But now, Google is baking the Talkback features right into Android so users won’t need to download a separate app.
“With this new update, there are no additional downloads necessary to use most braille displays. People can use braille displays to access many of the same features available with Talkback. For instance, you can use display buttons to navigate your screen and then do activities like compose an email, make a phone call, send a text message or read a book,” wrote Nimber Jaber, Accessitliy Analyst at Google, in a blog post.
Users will have access to all the usual Talkback features, including the ability to composite an email, make a phone call, read a book, and so on. In addition to these features, Google has also added some new shortcuts in Talkback. For example, you can use new navigation shortcuts to scroll and move to the next character, word, or line. And then, there are shortcuts for settings and editing documents, like selecting, copying, pasting, etc.

Source: Google Blog

 

[dmarden]

Sorry to ask for the handholding/reassurance. I did read.

So I am on QPR Beta 3 right now... sounds like I should be able to:

1. Switch to Magisk Canary and then update to the latest
2. Download and unpack A13 B2, and patch the boot.img from it
3. Flash A13 B2 removing the -w (no need to do any of the vbmeta verity whatever)
4. Flash the patched boot.img

Success, right? Rooted A13 without wiping?

 

[whatsisnametake2]

Sorry to ask for the handholding/reassurance. I did read.

So I am on QPR Beta 3 right now... sounds like I should be able to:

1. Switch to Magisk Canary and then update to the latest
2. Download and unpack A13 B2, and patch the boot.img from it
3. Flash A13 B2 removing the -w (no need to do any of the vbmeta verity whatever)
4. Flash the patched boot.img

Success, right? Rooted A13 without wiping?

this is exactly what I'm about to do. that's my understanding as well.

 

[dmarden]

this is exactly what I'm about to do. that's my understanding as well.

Please report back lol

 

[whatsisnametake2]

in terms of going backwards from A13, if using the full factory images to flash with flash-all.bat, presumably there's no reason I can't go A13 beta 2 -> A12L main? and also even without wipe if wanted? (removing -w)