Develop Bugs

Why is Oreo taking so long?

I'm not asking for an ETA, as I know that's against the rules on xda.
However, I'm unable to find any info anywhere about the reasons why Oreo hasn't arrived. It was released in August, and over three months is a long time in custom ROM world.
I'm guessing it's being worked on but there are complications, but with the lack of updates being posted by the powers that be, it's hard to know. Can someone in the know tell me?

As far as i know it was the quick succession of Android 8.1 which let several custom rom developers drop Android 8 developement and jump directly onto the 8.1 train.

Schwarzie2k said:
As far as i know it was the quick succession of Android 8.1 which let several custom rom developers drop Android 8 developement and jump directly onto the 8.1 train.
Click to expand...
Click to collapse
Let's hope 8.2 isn't released soon then.
I think many people would appreciate a blog post on the LineageOS website advising how things are progressing and what the challenges have been.

the blog post from December touched on the progress of Oreo and on skipping 8.0 to go straight to 8.1. (it's below the changelog text):
https://www.lineageos.org/Changelog-15/
However now that Android 8.1 has been released, we’re anticipating moving straight to the 15.1 branch where we’ll merge all our work done for 15.0 and finish the porting effort.
Click to expand...
Click to collapse
Also, a very recent news (January 1) here on XDA talks about an alpha build being available for the OnePlus 5:
https://www.xda-developers.com/lineageos-15-1-android-8-1-oneplus-5/
(I'm assuming that's from the official maintainer to have been worthy of a news).
So things seem to move into place.

Any OFFICIAL LineageOS 14.1 users?

Long story short, I'm looking for the most stable and refined custom ROM for the MZP. I'm currently using Alberto97's AOSP 8.1 and while everything is working fine, it isn't really that refined. As it is ported from what I guess is the Google Pixel, the OS thinks that the device is a Google Pixel. For example, when I set up the device, it shows the banner "Finish setting up your Pixel". Also, when I register my fingerprint to unlock the device, the setup shows to use the index finger and touch the sensor located on the rear of the device (like the Pixel's). Charging with the phone powered off is also bugged, as it shows nothing but "Charging ??/100". I know these may seem like small things, but I'm a person with extreme attention to detail (almost borderline OCD) and things like these just bug the hell out of me, even though it isn't the devs fault at all (mad respect to Alberto).
Basically, I want a custom ROM that is MADE for the device, not ported. If you guys get what I mean. Polished is the word, I guess.
Seeing as LineageOS 14.1 is officially supported, do these cosmetic flaws exist? Can any LOS users confirm this? I apologize for bugging this sub with my stupid questions, I just want to settle with my phone once and for all.
Thank you to all for your help!

djdelarosa25 said:
Long story short, I'm looking for the most stable and refined custom ROM for the MZP. I'm currently using Alberto97's AOSP 8.1 and while everything is working fine, it isn't really that refined. As it is ported from what I guess is the Google Pixel, the OS thinks that the device is a Google Pixel. For example, when I set up the device, it shows the banner "Finish setting up your Pixel". Also, when I register my fingerprint to unlock the device, the setup shows to use the index finger and touch the sensor located on the rear of the device (like the Pixel's). Charging with the phone powered off is also bugged, as it shows nothing but "Charging ??/100". I know these may seem like small things, but I'm a person with extreme attention to detail (almost borderline OCD) and things like these just bug the hell out of me, even though it isn't the devs fault at all (mad respect to Alberto).
Basically, I want a custom ROM that is MADE for the device, not ported. If you guys get what I mean. Polished is the word, I guess.
Seeing as LineageOS 14.1 is officially supported, do these cosmetic flaws exist? Can any LOS users confirm this? I apologize for bugging this sub with my stupid questions, I just want to settle with my phone once and for all.
Thank you to all for your help!
Click to expand...
Click to collapse
Hi there,
None of the cosmetic flaws you said exist on the official LineageOS 14.1 ROM. I'm using it for several months now and it is certainly the most polished ROM created for this device.
By the way, I've tested weeks ago Alberto97's AOSP 8.1 and it was a weak experience. It wasn't optimized as I expected, some of the animations were jerky and I noticed multiple bugs.
I definitely recommend using LineageOS 14.1 ROM if you want a good experience. Also, I recommend using 7.1 ROMs instead of 8.0's/8.1's. They are way more stable and optimized.
If you have any question, feel free to ask.

Systemlessly said:
Hi there,
None of the cosmetic flaws you said exist on the official LineageOS 14.1 ROM. I'm using it for several months now and it is certainly the most polished ROM created for this device.
By the way, I've tested weeks ago Alberto97's AOSP 8.1 and it was a weak experience. It wasn't optimized as I expected, some of the animations were jerky and I noticed multiple bugs.
I definitely recommend using LineageOS 14.1 ROM if you want a good experience. Also, I recommend using 7.1 ROMs instead of 8.0's/8.1's. They are way more stable and optimized.
If you have any question, feel free to ask.
Click to expand...
Click to collapse
Sweet, thanks a lot man! I'm going to flash it right now.

Sadly, the flash failed It appears that it doesn't support the Oreo bootloader

djdelarosa25 said:
Sadly, the flash failed It appears that it doesn't the Oreo bootloader
Click to expand...
Click to collapse
What is the error?
Did you flash the official or soak test 8.0 rom before?

Systemlessly said:
What is the error?
Did you flash the official or soak test 8.0 rom before?
Click to expand...
Click to collapse
ERROR 7, my bootloader is not supported
I updated to official 8.0.0 Oreo by sideloading the OTA

djdelarosa25 said:
ERROR 7, my bootloader is not supported
I updated to official 8.0.0 Oreo by sideloading the OTA
Click to expand...
Click to collapse
Oh yeah, that's bad.
You should post a message regarding this issue on the Official Lineage 14.1 topic to make the developper aware. I think that's not hard to make the bootloader compatible, it should be some parameters to change

Systemlessly said:
Oh yeah, that's bad.
You should post a message regarding this issue on the Official Lineage 14.1 topic to make the developper aware. I think that's not hard to make the bootloader compatible, it should be some parameters to change
Click to expand...
Click to collapse
I've been trying to Google ways on how to contact the maintainer but I can't seem to find out how. Can you help me by sending a link on how to message the dev?

djdelarosa25 said:
I've been trying to Google ways on how to contact the maintainer but I can't seem to find out how. Can you help me by sending a link on how to message the dev?
Click to expand...
Click to collapse
According to this link: https://wiki.lineageos.org/devices/addison
It is said that it is mccreary the maintainer.
Here is his mail:
Sean McCreary: [email protected]
https://review.lineageos.org/#/q/owner:mccreary%40mcwest.org+status:merged

Systemlessly said:
According to this link: https://wiki.lineageos.org/devices/addison
It is said that it is mccreary the maintainer.
Here is his mail:
Sean McCreary: [email protected]
https://review.lineageos.org/#/q/owner:mccreary%40mcwest.org+status:merged
Click to expand...
Click to collapse
Holy cr*p, thanks so much, man! :laugh:

am also looking like dis , how smooth los 14.1? what is the present bug? in bootloader case, we can edit build prop instead zip folder

talktosam said:
am also looking like dis , how smooth los 14.1? what is the present bug? in bootloader case, we can edit build prop instead zip folder
Click to expand...
Click to collapse
I contacted the maintainer and he said it's not as simple as that, as there may be incompatibilities with a bootloader from a different Android version. We're messaging each other for the past few days and he sent me a test build. The flash succeeded, though we are unable to make it boot up.

djdelarosa25 said:
I contacted the maintainer and he said it's not as simple as that, as there may be incompatibilities with a bootloader from a different Android version. We're messaging each other for the past few days and he sent me a test build. The flash succeeded, though we are unable to make it boot up.
Click to expand...
Click to collapse
u ask any way to get LOS 15.1? any hope? how can i contact him?

talktosam said:
u ask any way to get LOS 15.1? any hope? how can i contact him?
Click to expand...
Click to collapse
I asked him yesterday but he said that it's against rules to ask for ETAs (even when I only asked him if it would come out, I didn't ask when :/)
Read the thread, one user already posted his email address here, though don't even try to ask him stuff like that again as surely he will link that to me.

djdelarosa25 said:
I asked him yesterday but he said that it's against rules to ask for ETAs (even when I only asked him if it would come out, I didn't ask when :/)
Read the thread, one user already posted his email address here, though don't even try to ask him stuff like that again as surely he will link that to me.
Click to expand...
Click to collapse

The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).

I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?

vbdss said:
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
Click to expand...
Click to collapse
Please see the post above you.
https://forum.xda-developers.com/showpost.php?p=76379057&postcount=16
---------- Post added at 07:06 PM ---------- Previous post was at 07:04 PM ----------
Happy to know that the developer fixed the issue @djdelarosa25. Well, it was a great idea to send him an e-mail.

vbdss said:
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
Click to expand...
Click to collapse
Lineage 14.1 is Nougat based and it will not flash as it will display bootloader error while flashing in twrp. Wait for Lineage 15 or as djdelarosa25 said [/COLOR]
djdelarosa25 said:
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
Click to expand...
Click to collapse
wait till 2nd may
---------- Post added at 05:47 PM ---------- Previous post was at 05:32 PM ----------
djdelarosa25 said:
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
Click to expand...
Click to collapse
Is there any news for Lineage 15? I am kinda use to Oreo so I am looking for an Oreo ROM. I like AOSP no doubt but I'd also like to try a ROM that is build from scratch for MZP only.

Systemlessly said:
Happy to know that the developer fixed the issue @djdelarosa25. Well, it was a great idea to send him an e-mail.
Click to expand...
Click to collapse
Yeah, thanks for helping me, man! The dev was really cool - replies, debugs, and compiles really quickly as well. Talk about pro.
Manish355 said:
Is there any news for Lineage 15? I am kinda use to Oreo so I am looking for an Oreo ROM. I like AOSP no doubt but I'd also like to try a ROM that is build from scratch for MZP only.
Click to expand...
Click to collapse
I already asked him if it was in the works and he said don't ask for ETAs. I asked him again today and told him I wasn't asking for a date, just a confirmation if LOS 15 is in the works. We'll see what he says.
EDIT: So it counts as an ETA then. He said we'll just see it come out (so I guess it is in the works). But I wouldn't worry that much, the dev works really fast.
and yeah, I like a ROM that was made for the MZP as well. As much as I like Alberto's ROM, a ROM built from scratch > a port (though LOS 14.1 is Alberto's work as well). It's a pity he quit development of it.

Android 10 Stable Update are available ?

Now Android 10 Stable Update are available ?
I have brick the phone twice with updates.

A.saeed said:
Now Android 10 Stable Update are available ?
I have brick the phone twice with updates.
Click to expand...
Click to collapse
Not seen any updates here so far have they released a new one?

I never received the previous update, so I guess I am lucky in this sense!
My understanding is that the first release was a beta test!
Not sure what the approach will be for releasing a new update: give it to the same people as the first or to everyone?
I do hope you all got your phones up and running again! And let's hope the next update will be better!

No new upadte in serbia,just checked and no update?

saggel said:
I never received the previous update, so I guess I am lucky in this sense!
My understanding is that the first release was a beta test!
Not sure what the approach will be for releasing a new update: give it to the same people as the first or to everyone?
I do hope you all got your phones up and running again! And let's hope the next update will be better!
Click to expand...
Click to collapse
Even if it were as you say, I don't think Xiaomi has made a good impression, the "Beta testers" cannot be the unsuspecting and unfortunate users

saggel said:
I never received the previous update, so I guess I am lucky in this sense!
My understanding is that the first release was a beta test!
Not sure what the approach will be for releasing a new update: give it to the same people as the first or to everyone?
I do hope you all got your phones up and running again! And let's hope the next update will be better!
Click to expand...
Click to collapse
It was a beta test. It was for everyone. It being buggy doesn't mean it's a beta..

If it bricks your phone its a ****ing alpha test...beta rofl

Arkon1337 said:
If it bricks your phone its a ****ing alpha test...beta rofl
Click to expand...
Click to collapse
I'm beginning to believe that they did it on purpose to get rid of "Android One" ...

IlSaro said:
I'm beginning to believe that they did it on purpose to get rid of "Android One" ...
Click to expand...
Click to collapse
Nah, Xiaomi just bad at system updates... Even most of their flagship phones running on Android 9.

andraslate said:
Nah, Xiaomi just bad at system updates... Even most of their flagship phones running on Android 9.
Click to expand...
Click to collapse
It is normal to be wrong, not to persevere ...

"Xiaomi is aware of the Android 10 update issues in Mi A2 Lite and the launch to users of that device has now been suspended . Our teams are now working to solve the problem and our goal is to implement an update via OTA throughout March. Affected users are recommended to take their devices to authorized Xiaomi service centers for post-sale assistance."
Source
So theyre gonna release new version of the Android 10 in March 2020.
First Android 10 Release - 9 March 2020
Second - 16/23/30 March 2020

IlSaro said:
I'm beginning to believe that they did it on purpose to get rid of "Android One" ...
Click to expand...
Click to collapse
It's working here. I've bought a Pixel 3a

Question Android 13 - Developer Preview 1

There are OTA's available as well.
Is anyone brave enough to try it? Is anyone on it? I am considering side loading it.
https://www.xda-developers.com/how-to-download-android-13/

If they are planning on it being beta by April it shouldn't be all that bad but I'm probably gonna wait until at least the next build. 12 to 13 isn't as huge a leap as it was from 11 to 12 so I'm guessing/hoping it won't be as buggy as early 12 builds. I'm sure someone will take the plunge to determine if it can be rooted or not.

oh my god xD google is trolling us....android 12,android 12 L,now android 13...what the ****! xDDDDD

Well 12L comes out next month officially. No more Android 12 updates.
Hopefully someone takes the plunge. I don't mind doing installing it to do bug reports to ensure the beta is a fun experience.
I want to know if the OTA works, scared to be the first to try as google doesnt even offer the ota on their website. Who will be the brave soul?

I am going to do a factory reset to A13,give a few minutes

Ivixmax said:
oh my god xD google is trolling us....android 12,android 12 L,now android 13...what the ****! xDDDDD
Click to expand...
Click to collapse
According to some people, A12L has the best modem update, A13 has the newest kernel.
Maybe in the future we best just mix all three branches together, creating the best Android.

Morgrain said:
According to some people, A12L has the best modem update, A13 has the newest kernel.
Maybe in the future we best just mix all three branches together, creating the best Android.
Click to expand...
Click to collapse
It was already making me think of Windows 98 Millenium edition - the notorious user mix and match of the horrible Windows ME and the less horrible Windows 98.

ok root is working fine on A13, no problem. This is the kernel and baseband versions

Looking at the dates 220205 - Android 12L and 220114 - Android 13, it appears that this build of Android 13 is older than the 12L update. February 5th vs January 14th.. Thoughts? Anyone see how the modem works?

Doug8796 said:
Looking at the dates 220205 - Android 12L and 220114 - Android 13, it appears that this build of Android 13 is older than the 12L update. February 5th vs January 14th.. Thoughts? Anyone see how the modem works?
Click to expand...
Click to collapse
LLStarks said:
Modem is newer than Feb but older than 12L. Bootloader is version 1.2 compared to 1.1 in 12L and 1.0 in Feb.
Mixed bag. Need to see what 13 modem is capable of (i.e. VoNR, C-Band, etc).
Click to expand...
Click to collapse
LLStarks said:
VoNR and C-Band are present. Rooting works as expected.
Edit: This update adds 3 carrier 5G aggregation?!?! n41-n71-n71 and n41-n41 looks to be present with the latter also appearing in 12L.
Click to expand...
Click to collapse

Is the modem decent? More capable than all but Android 12L? Can non root flash the newer modem you think?

Doug8796 said:
How is the modem working? did you do a speed test?
Click to expand...
Click to collapse
@LLStarks , just tagging you in this thread to see if you have any answer for @Doug8796.

Doug8796 said:
Can non root flash the newer modem you think?
Click to expand...
Click to collapse
With the bootloader unlocked you can flash anything you like. What happens when you do, no one call tell, though. Might work, might not, the possibility of boot loop...

ATENTION!
ok dont install this ****....y only can rich 4 mbps on 4g and 5g what the ****! jajajajjaja

Cant unlock the ole bootloader until I pay it off - on contract.

time to return to A12 L

Ivixmax said:
ATENTION!
ok dont install this ****....y only can rich 4 mbps on 4g and 5g what the ****! jajajajjaja
Click to expand...
Click to collapse
You sure it's build/A13 related? Have you tried out another phone at the same location where your A13 device is?
I've had a mountain of NordVPN connection problems in the most recent months and have troubleshooted so much, even though in the end it was just caused by bad/weak servers, meaning after connecting to new ones it was "solved" - so if you use a VPN, mind that.

Ivixmax said:
ATENTION!
ok dont install this ****....y only can rich 4 mbps on 4g and 5g what the ****! jajajajjaja
Click to expand...
Click to collapse
what was it before in the same spot on 12L?

Doug8796 said:
what was it before in the same spot on 12L?
Click to expand...
Click to collapse
40 or 60 mate xD

Patetic modem on A13.
Time to reflash A12 L

Question Pixel 6 pro android 13 Beta 2.1.

How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?

Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.

NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..

There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here

biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!

Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)

Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.

Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)

NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.

Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(

NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com

uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.

Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro

NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir

notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...

NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.

Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)

I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.

Does anyone know When would be next Beta update?
Thanks...