OnePlus 8 Android 12

tidbits wrote:

Makulund wrote:

Ok I'm about done hearing that the Unlocked variants OnePlus 8 and 8 Pro are on Stable versions of android 12 while being stuck with the carrier variant means we probably won't see Android 12 on T-Mobiles OnePlus 8 or 8 Pro until Android 13 drops this is ridiculous thanks T-Mobile! 

unlike popular belief… Carriers have little control, and don't touch the code like people think they do.  Multiple times OEM(manufacturers) have admitted it, but here in the states we still blame carriers.  Ever noticed Google doesn't blame carriers anymore after about a year of them complaining?  Why?  They did an AOSP project with Sony and found out that carriers DON'T actually delay updates no more than a month in 90% of cases.  They only time there is any lengthy delay is where a security flaw was found.

Other OEM's have pushed out their updates on T-Mobile except OnePlus.  They chose to update process for T-Mobile.  Why would T-Mobile delay 1 manufacturer over all the others they have?  Think about it for a second.  IF you device is paid off you can actually load the OnePlus version and run it instead of waiting for a T-Mobile version coming out.  OnePlus forums will show you how to do it.

So what if i decide to load OnePlus 8 Android 12 on my TMO version since its paid off. Will it still work well for like text messages, 5G, WiFi, all that as if i had the TMO version?

Everything works fine if you use the MSM Tool to load the Global/NA firmware on the T-Mobile variant.  The hardware is the same.  WiFi Calling works, VoLTE works, RCS works, etc.  It is recommended you request T-Mobile SIM unlock your device first though.  The device can only be SIM unlocked on the T-Mobile firmware.  

syaoran wrote:

Everything works fine if you use the MSM Tool to load the Global/NA firmware on the T-Mobile variant.  The hardware is the same.  WiFi Calling works, VoLTE works, RCS works, etc.  It is recommended you request T-Mobile SIM unlock your device first though.  The device can only be SIM unlocked on the T-Mobile firmware.  

This is probably the best thing to do but a lot of people don't feel comfortable doing something like this.  The entire android update process is still a major problem.  It seems like carriers claim that the manufacturer is holding up the update and manufacturers like OnePlus claim it's the carrier.  It's also rather strange that a low-end phone like the Nord N200 gets the Android 12 update before a "flagship" at the time of it's release does.  I know the 8 is old in today's cell phone world, but it's still a very capable device, much more so that the N200.  To me this show's it's not about the hardware but how many phones were sold.  It's obvious that the OnePlus 8 was not a big seller for T-Mobile.

The blame game is just to shut.the.consumer up but it is 95% on the device manufacturer.  As a person who has tested builds for just about every manufacturer that sells their devices through a carrier in the US and Canada.  It has been over a decade since carriers have had any meaningful impact on an update, especially a major one.  

syaoran wrote:

The blame game is just to shut.the.consumer up but it is 95% on the device manufacturer.  As a person who has tested builds for just about every manufacturer that sells their devices through a carrier in the US and Canada.  It has been over a decade since carriers have had any meaningful impact on an update, especially a major one.  

I get it. OnePlus just gave a big middle finger to the T-Mobile community. Well, the few people that fell for the OnePlus 8 hype that is.

wbknudsen wrote:

syaoran wrote:

The blame game is just to shut.the.consumer up but it is 95% on the device manufacturer.  As a person who has tested builds for just about every manufacturer that sells their devices through a carrier in the US and Canada.  It has been over a decade since carriers have had any meaningful impact on an update, especially a major one.  

I get it. OnePlus just gave a big middle finger to the T-Mobile community. Well, the few people that fell for the OnePlus 8 hype that is.

the majority of their devices that received 12 are in the same boat..its by far not just the 8 running into this..heck a nice chunk of other manufacturers devices that received 12 ran into issues as well..

wbknudsen wrote:

syaoran wrote:

The blame game is just to shut.the.consumer up but it is 95% on the device manufacturer.  As a person who has tested builds for just about every manufacturer that sells their devices through a carrier in the US and Canada.  It has been over a decade since carriers have had any meaningful impact on an update, especially a major one.  

I get it. OnePlus just gave a big middle finger to the T-Mobile community. Well, the few people that fell for the OnePlus 8 hype that is.

It's how devices are developed for.  You take two teams.  They alternate between devices release.  So the team that works on the firmware for the 9's and everything released then, is a different team than the team that works on the 10's and everything that came out then from OnePlus.  The older the device, the rougher the code merge between Oxygen OS and Color OS seems to have been.  

This isn't saying much, but I haven't read about many issues with the N200 and the update to 12. I saw a few reddit posts about what seems to be typical update issues across the board with all manufacturers.

I just find it rather odd that the N200, a $199 dollar phone, gets priority over this phone.  It tells me that T-Mobile has some say in the priority of a manufacturer's updates.  Just guessing though, I'm clearly in over my head on this one.

You don't want Android 12 anyway...it's a nightmare of an OS with my Oneplus 9 Pro going all over the place. Things like this is worthy of getting sued and getting money back as the phone becomes unusable during the day and need to constantly reboot.

LG might be gone but they did a pretty good job and getting 12 ready for their V60...i havent ran into any issues since it received 12.

knock on wood i didnt just jinx myself.