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
Related
So updated to the. 8 was fine, Google did restore as I wiped everything(fresh install) twrp and magisk installed. First problem I noticed is I flash install oreo remix boot animation via magisk or twrp but it refuses to change the boot animation of the no limit rom. I thought ok w.e, then I did the battery extend life by adb shell disabling what was listed and I download the jtool to set force 90hz. Now when I try to open these 2 apps this happens https://youtu.be/bCBSCmg2Gb4
So I did clean install back to stock. 7 and on no limit Tom, surprise had same issue again, by installing the June 18th smurf rom. Then I did local upgrade to.8 the issue went away, but came back as soon as I applied the no limit rom. Conclusion bad kernal version on.7 and the rom isn't supported on. 8?
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
So this morning I went to check on lineage OS news oh, and I found out that they released today for all pixels. I am running it with no issues although I would recommend to download the micro gapps package cuz if you do the Nano or anything below it will give you issues with your phone reading SIM card. Aside from that I had successfully running the rom with magisk installed.
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
i42o said:
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
i42o said:
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
Click to expand...
Click to collapse
Is 90hz working??
ahoslc said:
Is 90hz working??
Click to expand...
Click to collapse
Read just one or two more posts above the one you quoted to find your answer.
bradical711 said:
Read just one or two more posts above the one you quoted to find your answer.
Click to expand...
Click to collapse
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
i42o said:
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
90hz works, 70% plus brightness on coral gives 90hz, below is 60hz. flame has some different tunings percentage wise, but same concept.
RefreshRate will work as soon as we have an official R image I can steal a single APK from.
We won't be implementing Squeeze or Soli most likely - it's RE, and given scrutiy over large projects and reverse engineered code, we likely won't see it unless it's reimplemented OSS (DU reverse-engineered it, but didn't clean room re-implement).
ahoslc said:
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
Click to expand...
Click to collapse
It works.
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Madjax2020 said:
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Click to expand...
Click to collapse
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
i42o said:
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
Click to expand...
Click to collapse
thank you sir for the reply. However i could not get it to be stable. The initial setup failed no matter what i tried. The error of data tansfer tool would fail. I want to run this as it seemed very smooth, however i think i need to wait for another update or something. i followed the OP to the t and nothing seemed to work properly for me.
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
I'll try again thanks for the info
Seems the wiki says you can sideload gapps right after sideloading the OS, the OP said doing that causes issues lol. But he'll I'll try it anyway
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
Got this running great, with gapps. Was wondering if you're getting the issue I am with google assistant. It seems to freeze up and not be usable.
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Madjax2020 said:
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Click to expand...
Click to collapse
You do remember I said micro right? I specifically explained that by using nano you would have no cell phone connectivity and upon transfer tool just put no transfer
XMayhem2099 said:
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Click to expand...
Click to collapse
Yes it is still there but much less now
Face unlock working?
Dear all,
Hope you are doing great, I was downloading and installing automatic updates just fine and the other week got a notification about a new update of over 1.4 gbs and the automatic installer was not possible to do and requested me to download it and installing it manually. I downloaded the Rar and everything was going smooth and when I enter TWRP I installed at first shoot without doing any wipe or clear cache or data.
All was installed and it told me to restart the phone, I did that and vroom a vibrating sound happen and got me back to the main screen of Poco and then to TWRP and show me 3 workarounds to clear data and cache and the last resort do a clean flash rom.
I had to end with the last option since I was unable to install the update. What could be gone wrong here? I am back at stock now and I am very sad that this fricking update break all the custom firmware and got me bootlooped
I look for your inputs and maybe I can try again.
Thank you!
You must install Android 11 firmware for newer versions of Arrow as it has switched to OSS vendor.
I was on arrow os 11 so Android 11 was on there, the issue was when I was installing the new update from surija I believe si called the developer.
Do you guys have an idea what did I did wrong? Should You recommend staying vainilla stock miui 12 with root privileges or arrow 11?
Thank you!
I was able to flash the latest version update but I am having a System UI is not responding and got WIFI broken so if anyone is installing this update be careful, does anyone installed the last arrow OS update?
I am currently having issues with the last update, I think I will stick with no updates on the firmware
Sorry I am posting multiple updates on my thread, but I tested it and definetly the last update from Surya break the OS when you login you do not have WIFI and is showing the error I mentioned UI system unresponsive. I installed the version from April from Arrow OS and all works like a charm.
So if anyone reads this be careful with latest release from Surya 5/14 version
Yes, i can confirm. The version I used initially was from april 30. The update from may caused bootloop. I'll be turning off updates when I restore it with miflash.
The main reason I went with arrow is that it is selinux enforcing and supports safety net. But this really makes me think..
@SebixWolf The problem may have been that you flashed arrowos from the wrong miui version. I just miflashed back to the original regional version, flashed twrp again and flashed the R firmware. See https://forum.xda-developers.com/t/...ng-flashing-custom-rom.4274891/#post-85002889
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)