Android 11 beta 2.5 released (display hz fix) - Google Pixel 4 XL Guides, News, & Discussion

Google dropped an incremental update to address the whole display flicker issue as well as a few other smaller issues. I'm running it now and can confirm its a night and day difference as far as the display. Using the refresh rate overlay, you can see it stays at 90hz indefinitely while the smooth display option is toggled. They didn't just add back the force 90hz display option like I was hoping but this achieved the same result so I won't complain.
Download link for Android 11 2.5 factory image: https://developer.android.com/preview/download
Download link for Android 11 2.5 OTA:
https://redirect.viglink.com/?forma...with Pixel 4 display fix - 9to5Google&txt=OTA

Magisk Canary on my Pixel 4XL running Android 11 Beta 2.5
All good here. Notifications are functioning.

Any idea if flashing this new version will allow me to have face unlocked back on Android 10? No luck with using the magisk module

chazall1 said:
Magisk Canary on my Pixel 4XL running Android 11 Beta 2.5
All good here. Notifications are functioning.
Click to expand...
Click to collapse
Did you update from Android 11 Beta 2.0, or did you go straight from 10 to 11 2.5?
I did flash-all without the -w, then used magisk canary, updated to the latest, and flashed the patched boot.img, and it still boot loops for me. It says there's no valid boot slot. Which options did you use in Magisk when creating the patched boot img?

matt99017d said:
Any idea if flashing this new version will allow me to have face unlocked back on Android 10? No luck with using the magisk module
Click to expand...
Click to collapse
Hi,
With the july update face unlock works just fine.

1dopewrx05 said:
Google dropped an incremental update to address the whole display flicker issue as well as a few other smaller issues. I'm running it now and can confirm its a night and day difference as far as the display. Using the refresh rate overlay, you can see it stays at 90hz indefinitely while the smooth display option is toggled. They didn't just add back the force 90hz display option like I was hoping but this achieved the same result so I won't complain.
Download link for Android 11 2.5 factory image: https://developer.android.com/preview/download
Download link for Android 11 2.5 OTA:
https://redirect.viglink.com/?forma...with Pixel 4 display fix - 9to5Google&txt=OTA
Click to expand...
Click to collapse
The smooth display setting does not fix the refresh rate at 90Hz in low light conditions.
You can achieve the same result like the force 90Hz from developer options with the following adb command:
adb shell settings put system min_refresh_rate 90.0
After this, toggling the smooth display setting will have no effect. The display refresh rate will always be 90Hz.
To disable it again do the following:
adb shell settings delete system min_refresh_rate
Edit:
First seen in this thread: https://forum.xda-developers.com/pi...force-90hz-refresh-rate-t3994149/post83118135

matt99017d said:
Any idea if flashing this new version will allow me to have face unlocked back on Android 10? No luck with using the magisk module
Click to expand...
Click to collapse
It depends how you "broke" face unlock. If it broke from updating to and older Android 11 beta then going back to Q, then yes it should fix that. If it broke due to corrupting your Persist.img then no, the only way to fix that is to have a backup of your Persist from when it was good and manually restoring the old persist.img.

I flashed the incremental 2.5 update and face lock did not work. I then downloaded Android 10 July and that brought everything back to normal as it should. I tried this numerous times before the incremental update to no avail. I'm so glad that they fixed it!

Update:
SDK Platform-Tools: r30.0.4

Related

GSI images tested with POCO

I've tested 3 GSI images with my phone last weekend, here are the results:
--------------------------------------------------------------------------------------------------------------------------------------------------------------
1. PixelExperience: https://forum.xda-developers.com/poco-f1/how-to/treble-pixel-experience-9-0-t3839681
or here: https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
- Everything work well
- Feel faster than stock, no mi nonsense
- Wifi and data work fine
- Sound: OK
- Camera: work
- Bug: NO DARK MODE, it went black, and never come back.
- Ugly: the notification bar is not so compatible with curve screen, the clock and battery percentage almost got cut-off
- I might do something wrong, but my bank app said the phone is rooted. So, I have to flash stock back.
2. LineageOS: https://forum.xda-developers.com/pr...vice-development/9-0-lineage-os-16-0-t3840801
- There is this "privacy protection" error pop-up all the time
- Booted, run smooth
- Wifi and data work fine
- Sound and camera work.
- LineageOS handles the top and bottom curve better than PixelExp, the notification bar look better
- Some setting features were not working and follow with error, but the phone still work normally after error message
- I really hope the Lineage team get it work really soon. :good:
3. HavocOS: https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
- Bootloop...end
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Step
1. Unlock bootloader
2. Flash TWRP
3. With adb tool, flash system image (I've tried to flash PixelExp system image with TWRP, and got to bootloop, so I've changed to flash with adb command)
4. With TWRP flash decrypt
5. With TWRP wipe cache/dalvick
5. With TWRP format data
6. With TWRP flash decrypt again
Is there any way to flash PixelExperience without root?
PS. When I wrote that the camera work: I mean it works you can take a picture with both front and back cameras, but I didn't compare the picture quality at all.
Just tested Aosp Extended and I'll take the template you posted in the OP so it's easier for you.
AEX post: https://forum.xda-developers.com/pr...device-development/rom-aosp-extended-t3821934
- Rebooted itself a few times during the first boot.
- Felt sluggish during the first minutes, but then everything went smooth as butter.
- Wifi and data work fine
- Sound: OK
- Camera: work, but worse quality than stock
- Bug: NO DARK MODE, it went black, and never come back. In order to fix this you need to reflash the image
- Ugly: the notification bar is not so compatible with curve screen, the clock and battery percentage almost got cut-off. However you can almost fix it changing the display size, not a perfect fix but better than stock.
I'll be going to MIUI stock again, even though I hate it
Thanks for your feedback, you will save us a lot of time!
So, so far, you haven't found any GSI that handle completely properly the notch and curves of our screen?
I dont have any cut off on pixel experience after couple of reboots
Tomatot- said:
Thanks for your feedback, you will save us a lot of time!
So, so far, you haven't found any GSI that handle completely properly the notch and curves of our screen?
Click to expand...
Click to collapse
LineageOS handle the notch almost perfect, however, with other bug.
tomhtg90 said:
I dont have any cut off on pixel experience after couple of reboots
Click to expand...
Click to collapse
It looks nice indeed! Thanks, I'll give it a try.
tomhtg90 said:
I dont have any cut off on pixel experience after couple of reboots
Click to expand...
Click to collapse
For me, the time and battery percentage are closer to the edge than yours.
Also, is it root? Can we flash without root?
Thanks.
kikoarl said:
Just tested Aosp Extended and I'll take the template you posted in the OP so it's easier for you.
AEX post: https://forum.xda-developers.com/pr...device-development/rom-aosp-extended-t3821934
- Rebooted itself a few times during the first boot.
- Felt sluggish during the first minutes, but then everything went smooth as butter.
- Wifi and data work fine
- Sound: OK
- Camera: work, but worse quality than stock
- Bug: NO DARK MODE, it went black, and never come back. In order to fix this you need to reflash the image
- Ugly: the notification bar is not so compatible with curve screen, the clock and battery percentage almost got cut-off. However you can almost fix it changing the display size, not a perfect fix but better than stock.
I'll be going to MIUI stock again, even though I hate it
Click to expand...
Click to collapse
I, personally don't have any preferred template.
It seems as if the AEX is more or less on par with the PixelEx.
Can you manage to flash it without root?
I can live with a bit ugly notification and some minor bug, but I need to use the bank app. So I want to flash it without root.
I tested RR v6.1 GSI and it works with 2 intolerable bugs.
1, 3.5mm headphone not works. Speaker still works when haedphone plug in.
2, since the notch removed by command 'wm size 1080x2074' (result:here), screenshots will add black frame on the top and bottom, and the original contents(1080x2274) are zipped into 1080x1902, so it looks a liitle strange
RR GSI post: gsi-resurrection-remix-o-6-1-0-t3811299
Flashed arm64 a only 0818 version.
- root(magisk 17.1) and xposed v90 beta3 work.
- Wifi and data(CMCC) work
- Sound: both speakers work
- Camera: work
- Bug: headphone not work , screenshot problem
although i hate MIUI , i have to return to it . i need 3.5mm. looking foward to lineage 15.1 or aosp, etc.
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Daruwalla said:
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Click to expand...
Click to collapse
I could answer that...easily...maybe
I hate MIUI.
I hate ads full rom.
I have high hope for the project treble, it's a good starting point for generic device rom.
I don't know about your development of the lineageos, this is the first post I saw this information.
Also, it's fun to try something, even not perfect, it's still fun to mess around.
Daruwalla said:
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Click to expand...
Click to collapse
Thanks for the great news. And do you mind telling that you ve been watching the development where exactly?
Thanks once again.
Tried 9.0 roms
1 Treblized os: very smooth and stable VOLTE problem.
2 Pixel experience: Smooth but thermal throttling is broken hearts up quite bit.
3 lineage os: doens't look as good as PE and yeah no VOLTE is any GSI 9 or 8.1
4 Arrow os: The best of all. Fast snappy.
5 Havoc os: Bootloop tried everything.
Tried 8.1 roms:
1 Arrow os: The best I must say. PUBG experience is great the touch is really snappy and accurate for some reason.
2 RR official: Has some weird issue maybe sound don't remember.
3RR unofficial: there were 2 unofficial builds one booted fine and the other got Bootloop. Sound was good in unofficial and boot animation is better.
4 Aquarius os: Simple and good.
5 Dot os: well I've tried this GSI on my OP5T it was amazing but in Poco it doesn't feel as stable as others.
After trying all these GSI roms the best stable snappy and thermal friendly ROM was 8.1 and 9 Arrow os.
Like if I helped you.
$hivaM Manav said:
Tried 9.0 roms
1 Treblized os: very smooth and stable VOLTE problem.
2 Pixel experience: Smooth but thermal throttling is broken hearts up quite bit.
3 lineage os: doens't look as good as PE and yeah no VOLTE is any GSI 9 or 8.1
4 Arrow os: The best of all. Fast snappy.
5 Havoc os: Bootloop tried everything.
Tried 8.1 roms:
1 Arrow os: The best I must say. PUBG experience is great the touch is really snappy and accurate for some reason.
2 RR official: Has some weird issue maybe sound don't remember.
3RR unofficial: there were 2 unofficial builds one booted fine and the other got Bootloop. Sound was good in unofficial and boot animation is better.
4 Aquarius os: Simple and good.
5 Dot os: well I've tried this GSI on my OP5T it was amazing but in Poco it doesn't feel as stable as others.
After trying all these GSI roms the best stable snappy and thermal friendly ROM was 8.1 and 9 Arrow os.
Like if I helped you.
Click to expand...
Click to collapse
Wow, arrow os was not on my tested list. :good:
Need to try it asap.
Just question: can I flash it without root status?
Adios2nd said:
Wow, arrow os was not on my tested list. :good:
Need to try it asap.
Just question: can I flash it without root status?
Click to expand...
Click to collapse
Well I'm not sure because I flashed root on every GSI because my device feels uncomplete without it but I'm sure you won't have any problem with no root and yeah in some GSI roms we have option to download with gapps/su/ or vanilla
Edit:
I needed root access because I used this universal notch fix
Go to terminal give root access and type
"wm overscan 0,90,0,0" this completely pushes the notification panel below the notch and fits perfectly!
$hivaM Manav said:
Well I'm not sure because I flashed root on every GSI because my device feels uncomplete without it but I'm sure you won't have any problem with no root and yeah in some GSI roms we have option to download with gapps/su/ or vanilla
Edit:
I needed root access because I used this universal notch fix
Go to terminal give root access and type
"wm overscan 0,90,0,0" this completely pushes the notification panel below the notch and fits perfectly!
Click to expand...
Click to collapse
2 Questions
1. I didn't intend to flash root, but when I flashed the "Encryption disabler" (that every guides suggest to flash, see attached), it became root itself. Can I not flash it?
2. Do I need to fix the notch in ArrowOS, is it not detect and adjust by itself?
Adios2nd said:
2 Questions
1. I didn't intend to flash root, but when I flashed the "Encryption disabler" (that every guides suggest to flash, see attached), it became root itself. Can I not flash it?
2. Do I need to fix the notch in ArrowOS, is it not detect and adjust by itself?
Click to expand...
Click to collapse
1. The encryption disabler is only for MIUI roms because it encrypts your data on first boot but GSI roms don't encrypt your data so you can skip flashing that after flashing GSI
2. Only Pie roms have the ability to adjust to notch currently this feature is not available in 8.1 roms so it'll look weird.
The notch situation is a bit better in Lineage 9.0.
In every ROM, ir unlock doesn't work (as expected), and volte doesn't work (expected?!).
All cameras work well.
---------- Post added at 05:14 PM ---------- Previous post was at 05:14 PM ----------
Daruwalla said:
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Click to expand...
Click to collapse
mind posting the link?
$hivaM Manav said:
1. The encryption disabler is only for MIUI roms because it encrypts your data on first boot but GSI roms don't encrypt your data so you can skip flashing that after flashing GSI
2. Only Pie roms have the ability to adjust to notch currently this feature is not available in 8.1 roms so it'll look weird.
Click to expand...
Click to collapse
I'm a very beginner so to flash without root:
0. Unlock bootloader
1. Flash recovery TWRP
2. In TWRP flash encryption disabler
3. Wipe (normal wipe?)
4. Reboot to recovery (Do I need this step?)
5. Flash GSI
6. Then reboot to system
Am I right?
Thanks for your answer.
PS.
If I flash the GSI with adb fastboot, do I need to flash the encryption disabler?
(In fastboot, I do the "fastboot flash system GSI.img")
Adios2nd said:
I'm a very beginner so to flash without root:
0. Unlock bootloader
1. Flash recovery TWRP
2. In TWRP flash encryption disabler
3. Wipe (normal wipe?)
4. Reboot to recovery (Do I need this step?)
5. Flash GSI
6. Then reboot to system
Am I right?
Thanks for your answer.
Click to expand...
Click to collapse
One-time process:
1. UL bootloader.
2. Flash twrp.
3. Format user data for twrp dycript then reboot to recovery again without booting to os.
4. Flash encryption disabler boot once to os.
After this process you don't have to flash the encryption file again and again because it modifies your vendor partition for treble enable. You'll have to flash this file again after flashing any MIUI rom. If you need root in GSI you can flash this file or you can skip.

TIP: love your OP7? Do NOT upgrade to Android 10

EDIT & TL;DR:
(i) Some people on this thread say they have "no problems with the upgrade", but many, many people do. To me that confirms the advice of this post: don't gamble, it's not worth it.
(ii) Also note that some people say that their battery life improved with Android 10… but then it turned out that on Pie, for some reason, they had a battery life of three hours, instead of the awesome times that the rest of us are getting. In short: if someone says that Android 10 is awesome, try to read between the lines.
Original Post:
Long story short.
Upgraded to Android 10.
"Search" stopped working within Settings
Battery life went from Awesome to Awful, Awful, Awful (known issue)
Fought the battery issue for two days (requested help with BBS dump)
Downgraded to Pie using TWRP backup (mistake)
This bricked the phone
Spent a whole day unbricking
Have my phone back but lost local files (photos, documents)
Android Pie ain't broke… Don't be like me, there's nothing to fix, the OP7 on latest Pie is awesome, it's all downhill from there.
Im on android 10 OOS10.0.1, rooted, magisked, viper installed, blu_spark-r57 installed. everything is perfect. search is also working.
but i fully clean flashed the entire android 10 firmware. maybe try that? i backed my stuff up on my PC prior to this.
who ah way said:
Long story short.
Upgraded to Android 10.
"Search" stopped working within Settings
Battery life went from Awesome to Awful, Awful, Awful (known issue)
Fought the battery issue for two days (requested help with BBS dump)
Downgraded to Pie using TWRP backup (mistake)
This bricked the phone
Spent a whole day unbricking
Have my phone back but lost local files (photos, documents)
Android Pie ain't broke… Don't be like me, there's nothing to fix, the OP7 on latest Pie is awesome, it's all downhill from there.
Click to expand...
Click to collapse
But that's not a general recommendation to not update to Android 10
strongst said:
But that's not a general recommendation to not update to Android 10
Click to expand...
Click to collapse
Sure, it's just one person's experience. It caused me a lot of grief, and I don't see the point of taking the risk. For the few days I was on 10 I didn't see any benefits, only drawbacks.
Pie to stable 10 then beta 4, is just keeps getting awesome. But hey maybe its just me. Factory reset and no apps restore
Didit_Anshari said:
just keeps getting awesome
Click to expand...
Click to collapse
What would be one or two specific improvements you've found from Pie to Q?
who ah way said:
What would be one or two specific improvements you've found from Pie to Q?
Click to expand...
Click to collapse
battery life, and animation
I can confirm. Even on a clean install battery backup is significantly less on Android 10. Last Pie update gave me like 10+ hours of SOT.
Saadkhalid786 said:
Im on android 10 OOS10.0.1, rooted, magisked, viper installed, blu_spark-r57 installed. everything is perfect. search is also working.
but i fully clean flashed the entire android 10 firmware. maybe try that? i backed my stuff up on my PC prior to this.
Click to expand...
Click to collapse
Apps to display in full screen not working in 10
Don't know what's the problem with the battery this screenshots from OpenBeta 4 and now i'm on OpenBeta 5 will see how's the battery there :good: for me on every OpenBeta no problem with the battery life :good:
Maybe the reason is that I always to a fresh start from the scratch with every OpenBeta :good:
Sent from my OnePlus7 using XDA Labs
In android 10, Having auto brightness issue getting too low in medium litt conditions...
SherryWadhwa said:
In android 10, Having auto brightness issue getting too low in medium litt conditions...
Click to expand...
Click to collapse
Is not a issues, it's settings to aggressive. For resetting the auto brightness go in settings and tap on the in the screenshots marked points.
That resets the auto brightness and takes some days to learn it new :good:
Sent from my OnePlus7 using XDA Labs
Thanks mate! Tried it but still having a little issue at some point.
anyone can use sip calls with the default phone app and loudspeaker?
GraveDigger176 said:
Don't know what's the problem (...)
Maybe the reason is that I always to a fresh start from the scratch with every OpenBeta :good:
Click to expand...
Click to collapse
That's right, if you're installing from scratch, that doesn't count as an upgrade… And this thread is about warning people about upgrading to Android 10.
Let's cut through the noise for a moment.
Is there ANYONE on this thread who has actually done an UPGRADE as suggested on the guide below, and who is NOT experiencing pain with Android 10?
The Guide (see the section called 2. UPDATE):
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Download the full rom zip file and place it into the root folder of your storage(/storage/emulated/0)
3. Go to Magisk Manager App and uninstall all modules
4. Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, don't reboot yet!
5. Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
6. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit again install -> hit "install to inactive slot"
7. Reboot your device
8. Reinstall your Magisk Modules
Your device is now updated via local upgrade and you keep TWRP and Root
Click to expand...
Click to collapse
who ah way said:
That's right, if you're installing from scratch, that doesn't count as an upgrade… And this thread is about warning people about upgrading to Android 10.
I did also the upgrade from P to Q as I was on stable OOS, but right after upgrade and boot I booted in the stock recovery and do factory reset and the wipe everything wipe and start from the scratch and I never had any mentioned issues. But anyway now i'm on Beta path :good:
Sent from my OnePlus7 using XDA Labs
Click to expand...
Click to collapse
who ah way said:
That's right, if you're installing from scratch, that doesn't count as an upgrade… And this thread is about warning people about upgrading to Android 10.
Let's cut through the noise for a moment.
Is there ANYONE on this thread who has actually done an UPGRADE as suggested on the guide below, and who is NOT experiencing pain with Android 10?
The Guide (see the section called 2. UPDATE):
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
Click to expand...
Click to collapse
Yes, me. I did not face any issues.
I did an upgrade from pie to Q with the same instruction.
3 issues I have.
Autobrightness
Wifi is sometimes disconnecting for a sec and connecting again
Gap below the keyboard
Personally don't have any issues whatsoever with Android 10 - Magisk, kernel, and all. Though its true that if you're on pie there's no point in upgrading. Only added feature that you might enjoy is ever so slightly more customization and android 10 navigation gestures, that's it.
I upgraded to A10 and latest Oxygen and everything is working fine for a month and more, haven't experienced any issues listed above.

Android 11 Upgrade available OTA

Android 11 full release upgrade is available OTA now... downloading as I type this, just check for updates in Settings - System.
Anyone able to get chat bubbles working?
Also screenshot from the apps menu does not work unless full gesture or 3 finger btw..
Upgrade went ok in the end, but after an hr or more I had to reboot a couple of times to get it to complete. Was stuck 3/4 of the way up the progress bar. Stock/unroooted.
You need google Android messaging beta app to get bubble chats working. Currently using it now.
Launcher settings are not sticking with gesture navigation again. Lawnchair is my default launcher, but it is still trying to open Pixel Launcher. This issue went away a while back in 10, but seems to be back in 11. This alone is enough to have me switch back.
Anyone get root working? I tried magisk canary and patching the boot.img from the latest update aka Android 11 final but it wouldn't boot
adm1jtg said:
Anyone get root working? I tried magisk canary and patching the boot.img from the latest update aka Android 11 final but it wouldn't boot
Click to expand...
Click to collapse
No problems here. Used latest Canary to patch 11 boot.img. Flashed 11 full image. Let it boot up once. Rebooted to bootloader, flashed magisk patch boot.img. Booted up fine.
stompysan said:
Launcher settings are not sticking with gesture navigation again. Lawnchair is my default launcher, but it is still trying to open Pixel Launcher. This issue went away a while back in 10, but seems to be back in 11. This alone is enough to have me switch back.
Click to expand...
Click to collapse
I had this issue too, but I was using the traditional 3 button navigation. Every hour or so when I pressed home button it would want me to choose between Nova and Pixel launcher even though I already set Nova as default. Also after clicking the nav bar buttons, they would stay highlighted which was slightly annoying.
On top of these two minor bugs I just don't like Android 11 overall. I went back to AOSiP lol and I won't even bother updating past 10 custom ROMs until some custom ROMs based on 11 are available.
DriveEuro said:
No problems here. Used latest Canary to patch 11 boot.img. Flashed 11 full image. Let it boot up once. Rebooted to bootloader, flashed magisk patch boot.img. Booted up fine.
Click to expand...
Click to collapse
Would you mind uploading your patched boot image? For some reason it's not working for me. either and also did it the same way you described. Says the boot file is corrupted. Can boot with older patched kmages fine just no root though.
Edit* Nevermind I got it working. Took a few reboots and a couple more trys at patching and the patched boot image no longer was read as corrupted.
Still can't get it to work. Boots to Google screen then just goes back to bootloader screen. So far not liking 11 at all wanted to root it to make backups and maybe load aosip
Can someone link me to the canary build your using maybe i have an older one but it says it's for Android 11
Hello guys, I present the following problems: Bubbles WhatsApp does not work, internal audio in screen recording does not work, notification bar or navigation bar does not hide when opening Applications like fb or cod Mobile.
I cant save photos sent to me inside Facebook messenger & any screengrabs I edit vanish when I try to move them to another folder in Gallery, maybe this is more to do with the apps needing updating by developers? stock unrooted

Worth it to upgrade from Android 10 Sept 2020 to Android 11 right now or wait?

Or wait a couple of months for them to tweak it a bit?
I only run Magik and not Xposed, not that it matters!
I'm not rooted, but I've been running R since the first public ßeta.
It's been the smallest update so far in a long time for Android. Very little has changed, compared to previous major version upgrades.
If you can root (and from what I read i think you can with Magisk), make a full backup and try it.
Sent from my Pixel 4 XL using Tapatalk
I don't really know what you'd be waiting for. I don't think a non-rooted person would notice much in terms of drawbacks. Magisk modules level, there were some issues... but I think most things are getting worked out. Xposed technically works, but more than half of my modules broke in a way that probably won't be fixed for a while. I still feel like I'm at a net-negative in terms of phone features. A11 brought little and broke a lot of my QoL tweaks that used Xposed.
I make no claims about SafetyNet as I use no apps that even check it.
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
I tried it and reverted back to 10 - as mentioned didn't gain much but broke a lot. Even in stock form I can't get videos to load a subtitle file because of storage permissions and what not. A tweaked out install of 10 is faaaar nicer imo so that's what I'm running, probably until a new phone comes out sadly.
Kris Chen said:
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
Click to expand...
Click to collapse
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
A11 is not too bad, but as others have said little things here and there that break. Like for me I listen to SiriusXM app on mobile and for some odd reason it will stop playing all of a sudden and close. It's like the aggressive memory management kills the app for no reason. I even have battery optimization turned off and still does it.
Thinking about moving back to A10 from August, not really much I have to have to stick with latest A11 updates.
qman66 said:
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
Click to expand...
Click to collapse
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
You do know the latest version of magisk has a11 support?
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
Ok so I shouldn't install it via the ota? I keep getting the pop up to update every day.
Does using Magisk to dl / install the OTA, then patch the non-live and newly flashed partition, then finally rebooting not work?
When I was rooted that was always the easiest way.
And based upon the post 2 above this one, Magisk now supports A11 without ẞeta, right?
From Coral, with Tapatalk.
kdoggy said:
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
Click to expand...
Click to collapse
How is 11 for you going so far, I am thinking in reverting back to 10, battery is awful on 11

Question Anyone get OxygenOS 12.0.0 to install?

I downloaded it. Went to local upgrade, installed it.
Went to Magisk and did install to inactive slot like normal. And it reboots. Then a small bootloop for a second. Then goes straight back to normal. Like I never installed anything.
Any thoughts?
I tried to root by patching new boot.img but get bootloop which not fixed except after msmdownload tool
All data wiped
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
illusiveairforce said:
I downloaded it. Went to local upgrade, installed it.
Went to Magisk and did install to inactive slot like normal. And it reboots. Then a small bootloop for a second. Then goes straight back to normal. Like I never installed anything.
Any thoughts?
Click to expand...
Click to collapse
Same here. If you dont install magisk to the inactive slot it will go through and you will be in oos12. Problem with mine, it wont read my flaking sim card. Tried it 5x all same problem. Also, every reboot, your dpi goes back to 360 lmao.
I patched boot.img by canary magisk and it is working good, but no option for safetynet passing
sbute said:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
Click to expand...
Click to collapse
I used this guide but patched with magisk 23.0. still have all my modules and passing safety net. Using latest stable magisk 23.0 righteous. Thank you for this. I tried for 3 days killing my device flashing boot img. At least I know my downloaded msm tool works. On latest A12 build out for the global op9
I wouldnt recommend it tbh if its your only phone. Its buggy AH.
mattie_49 said:
I used this guide but patched with magisk 23.0. still have all my modules and passing safety net. Using latest stable magisk 23.0 righteous. Thank you for this. I tried for 3 days killing my device flashing boot img. At least I know my downloaded msm tool works. On latest A12 build out for the global op9
Click to expand...
Click to collapse
Would you or anyone else mind sharing the boot img for the OnePlus 9: OOS/Android 12 ?
I have the Global / NA version.
It would be greatly appreciated!
Zethiel said:
Would you or anyone else mind sharing the boot img for the OnePlus 9: OOS/Android 12 ?
I have the Global / NA version.
It would be greatly appreciated!
Click to expand...
Click to collapse
I have on my PC I will upload soon. Away from it currently. You really need 3 partitions to make work. Boot,vendor_boot,vbmeta
Geesh the battery is so much better on A12 after debloating how I see fit. Passing safety net, all banking apps working and still using old modules !! Score
mattie_49 said:
I have on my PC I will upload soon. Away from it currently. You really need 3 partitions to make work. Boot,vendor_boot,vbmeta
Click to expand...
Click to collapse
That would be greatly appreciated Sir!
0p9 partitions..A 12 - Google Drive
drive.google.com
All three are in here. Make sure to use magisk 23.0 to patch boot and vendor boot so you don't loose modules and magisk hide. Then you disable verity before boot with vb_meta img. You have to do from sdk platform tools folder though. Will not work just putting in a folder on desktop and pulling cmd window from there. Enjoy , follow the above guide to a T
Zethiel said:
That would be greatly appreciated Sir
Click to expand...
Click to collapse
infamousvincci said:
I wouldnt recommend it tbh if its your only phone. Its buggy AH.
Click to expand...
Click to collapse
Only issue I have is no advanced reboot menu what-so-ever. Battery is much better,stable af,modem is better as well. I would recommend .
File above edited. Correct images
mattie_49 said:
File above edited. Correct images
Click to expand...
Click to collapse
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Zethiel said:
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Click to expand...
Click to collapse
I have the correct msm tool for device. This is the forward route for you. Takes you to 11.4. Stock A11
Does anyone else have the issue of their touchscreen not functioning when they install the A12 update? Ive tried installing twice and both times my screen would not register any touches only the volume and power buttons functioned?
EDIT: NVM I MSM'd back to stock and upgraded to OOS 12 before unlocking the bootloader.
Zethiel said:
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Click to expand...
Click to collapse
if you are looking for performance, look into kernels and/or just use a kernel manager.
out of all the Roms I've tried (all but the latest havok release) crDroid is the best performance option I get from a ROM on O09. that piared with optional GApps and frequent OTA updates, its the best thing out so far. the OTA even works perfectly at retaining root without any user input. (but do a backup before reboot, its still technically a dirty flash so play safe)
sbute said:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
Click to expand...
Click to collapse
I don't want to get too off-topic, but figured I'd save a MSM wipe to some people, I can confirm this works, but only using the latest version of Magisk (v24), temporary boot will not work with v23 (the last one with MagiskHide), it caused Qualcomm crashdump and no recovery or fastbootd.
If anyone looks into other root spoofing solutions with the newer version v24, from Magisk settings use Zygisk, select apps using Enforced Denylist, and Universal SafetyNet Fix, there is also Shamiko, which I haven't tested personally.
From my own experience, DenyList+Universal SafetyNet fix+Selinux Switch if you need to switch between permissive and enforced Selinux are enough. Apps won't get to know there is root, safetynet is passed, and selinux checks are passed (that one took me a long while to figure out)

Categories

Resources