Just got the tmobile android 12 update on my Oneplus 9pro global version and its causing issues

Ugh, I'm glad I'm not the only one. I'm rolling back now.  Do these devs not test all the phones before rolling these out?  It's really unacceptable to push these updates when there are SO many issues.

If you use Tasker, forget it. It's been so glitchy. It won't recognize a lot of of auto-rotate and basic commands.

Overall interface is slow; disabling animation through developer’s option enabled didn’t do much.

Phone freezes (9 Pro also) and would auto restart but everything is just too slow to do anything.

I don't know if this is OnePlus's fault or T-Mobile. The quality control of these rollouts are beyond unprofessional.

Rolling back solved all of my issues.  It's a pain and it sucks, but my device works normally again.

Hi there, would you be able to elaborate or provide a reliable link for this:

Use the MSM Tool for your device to roll it back.  This isn't an easy process but excellent walk-throughs can be found on the XDA-Developers forums for this.  Once you roll back, which will completely wipe your device, so back it up if you value anything on it.  Enable Developer Options and turn off Automatically Install System Updates.  You will still get the annoying prompt for the update, which you can force close the system update app to get rid of until you reboot your device.  

Also, did the roll back completely resolve the issues you were having?  Right now my biggest issues are:

• the silent / vibrate slider no longer works - the notification that it is working comes up but when the phone rings it is always out loud.
• the direct dial and direct message shortcuts are gone and I am not finding a way to re-create them
• calls disconnect as soon as I answer (sometimes two or three times in a row)
• my WiFi seems super slow

figure it like this..TMO wont give the go ahead to release an update to the OEM until most of the bugs are fixed/taken care of..with how 12 has been rolling out im taking a guess that the previous versions of it were horrible and not deemed worthy of being kicked out...the shocking part would be that THIS variant was the one they gave the ok to kick out lol.

Yeah my bootloader is relocked. And everything working great on 11. Used MSM since my recovery was destroyed when I turned on dynamic updates. Just want to state that everything was stock on my phone other then having an unlocked bootloader. I was kind of hoping that there would be a way to flash the tmobile 12 firmware and modem files onto my global version without losing wifi calling and 5g. But if wifi calling doesn't even work on the tmobile variant ill wait and see if someone comes up with a fix. I'm Kind of a shocked that 12 is so bad with the long wait that tmobile put us through for the release. 

WiFi Calling for T-Mobile on Android 12, regardless of whether you use the Global/NA, EU, or T-Mobile firmware, does not work.  A number of devices, including Pixels are experiencing the same issues with WiFi Calling with Android 12.  It is one of the many Android 12 issues that are going to be a problem well into the Android 13 release cycle.  

If you need WiFi Calling, like I do or just want your device to remain on a reliable firmware.  Use the MSM Tool for your device to roll it back.  This isn't an easy process but excellent walk-throughs can be found on the XDA-Developers forums for this.  Once you roll back, which will completely wipe your device, so back it up if you value anything on it.  Enable Developer Options and turn off Automatically Install System Updates.  You will still get the annoying prompt for the update, which you can force close the system update app to get rid of until you reboot your device.  

12 itself for the carrier variants has been a bit of a nightmare across the board..

I just updated my global version too thank got most things are fine but I lost the wifi calling option. Any help?

I've had nothing but issues since the update to 12.  My phone doesn't always charge fully overnight, I have to call people twice since the first call always drops/won't connect, general slowing down of the system overall, and now I can't receive phone calls?  This really isn't making me interested in the OnePlus 10 at all.  I might have to go back to Sony or see if the Nothing phone is going to be any good.  There's no point in having a phone that can't receive any phone calls.  

*edit* also, the battery drains much faster than it used to with normal usage.

syaoran wrote:

Personally, using dynamic updates is a bad idea.  It just fragments the OS even more with the potential for way more issues.  Why is your bootloader unlocked?  You really should relock it and leave it locked.  If you used TWRP to convert it, then you should have done it the right way, using the MSM Tool method.  Most users running Android 12 have factory reset their device to eliminate a lot of issues.  This is always recommended with a major OS version update.  

agreed. keep in mind that when these updates are being worked on and tested its on a fully stock device..no additional apps etc ..so taking it back to being as close to stock as possible tends to help..not everyones cup of tea..and wont help you avoid bugs..but its usually a smoother download.