Forum Discussion
Android 12 Oxygen 12 updated for OnePlus 9 Pro has MAJOR BUGS & ISSUES!!!!!!
I recently received a new update for android 12 & oxygen 12 for my oneplus 9 pro. Now I have a list of bugs and issues happening. I have read a lot of the same complaints here on the forum and other sites from oneplus 9 pro/ t mobile users experiencing the same thing. Just to list a few…… screen brightness changes for no reason, operational and navigational lag, refresh rate (120) slows down periodically, finger print reader and face unlock will randomly stop working. What is the game plan for t mobile to send out fixes to an update I didn't need? This is ridiculous.
Hey guys:
The long and the short is I've been experiencing all the aforementioned issues with my branded TMobile OnePlus 9 Pro just like everyone else on this thread - and I went so far as to perform a hard reset of my phone. But…
I just downloaded and installed the July security patch (version:LE2127_11_C.19) and it seems to have resolved all issues. Granted it's only been 15 minutes so far so fingers crossed.
syaoran wrote:
magenta6723572 wrote:
So who is to blame for this Android 12 fiasco 🤣 My fingers are ready!!!
In this case, it's Google and OnePlus. Android 12 wasn't great when it was released but is slowly being fixed. However, then you throw the mess of the Oxygen OS base being merged with OPPO's Color OS that has caused problems on top of problems. So much so, Android 13 will revert to a straight Oxygen OS feeling with no code from Color OS at all.
I just hope they don’t eff it up further in the future...just have a really bad taste with Android even though I don’t think I can ever switch to Apple.
I miss LG, HTC, and wish these cell companies would offer more brands. Xiaomi for example. But I'm sure there's all sorts of red flag, gov, Chinese this, and who knows what sort of deals these companies offer T-Mo to keep their brands *cough*
magenta6723572 wrote:
So who is to blame for this Android 12 fiasco 🤣 My fingers are ready!!!
12 itself has borked up numerous devices across the manufacturers..heck the smoothest 12 update i have seen so far was to my V60..only a few small issues that you dont even really notice much..by far not issue free but at least its still working lol
sorry..did some add on edits to my last post instead of just doing a new one lol.
magenta6723572 wrote:
So who is to blame for this Android 12 fiasco 🤣 My fingers are ready!!!
In this case, it's Google and OnePlus. Android 12 wasn't great when it was released but is slowly being fixed. However, then you throw the mess of the Oxygen OS base being merged with OPPO's Color OS that has caused problems on top of problems. So much so, Android 13 will revert to a straight Oxygen OS feeling with no code from Color OS at all.
So who is to blame for this Android 12 fiasco 🤣 My fingers are ready!!!
Google kicks updates to manufacturers..manufacturers mess with it to make them compatible with their devices..been this way since day one pretty much...carriers dont want anything to do with security patches because..
A-they cover the reception side of things..
B-they dont want to be the reason the security patch doesnt work
C-they’ll test them but anything ran into reception wise they’ll kick feedback to the manufacturer and then the wash/rinse/repeat fixing then testing then either giving the ok to kick it out or hold off and fix the remaining issues.
heck its the same for OS updates as well..the carrier will test them but the mass majority of any fixes or adjustments is on the manufacturers side. same goes for the other carriers...so figure each OEM must make a carrier variant for each carrier out there.
HTC has been gone in the wind however this still gives the run down that every manufacturer does when it comes to OS updates start to finish..
so when people are saying “ (insert carrier here) kicked out the update..why hasnt TMO? whelp...that carrier was able to finish theirs with less issues to fix before the TMO variant did..or vise versa..whomever gets a working variant first gets to kick it out first. if in this case OP kept running into issues with Verizons variants but things went semi smoothly for TMOs..then they’ll kick out TMOs first..
carriers will have things they want added in though..which is usually where said delays come in due to trying to make it compatible without screwing anything up.
i can say the issue yall were having was due to a compatibility issue between 12 and from what i was told one specific ability on the OP devices..im unable to say what said ability was however if this security patch actually fixed it then im wondering if they either turned said ability off to correct this or if they actually fixed it fixed it..
magenta6723572 wrote:
fireguy_6364 wrote:
TMO has very little to do with updates..especially security patches..
Are you sure? I thought they built their own ROM’s based on Android...the reason why it’s also difficult to patch & update anything with T-Mo’s version.
Carriers to not employ development teams for Android or iOS. All updates for all devices are developed and tested in-house by the OEM before the OEM pushes that update.
fireguy_6364 wrote:
TMO has very little to do with updates..especially security patches..
Are you sure? I thought they built their own ROM’s based on Android...the reason why it’s also difficult to patch & update anything with T-Mo’s version.
Did the Update about 24 hours ago. Definitely an improvement, but still not fixed. Had my fingerprint reader break a few times and the screen stay max brightness. I think I restarted my phone twice yesterday.
TMO has very little to do with updates..especially security patches..
