Forum Discussion
OnePlus 8 Android 12
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!
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.
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.not overly sure how they are prioritizing one device over the other..whichever team that is working on said devices issue filled update that finds a fix will kick it out the soonest..thats it..
LG had its own issues with the screen burn-in...which I feel never got resolved no matter what people did. That was probably one of many downfall of LG in the smartphone world. I used to LOVE LG...but G5 was my last phone and after that, I was done with them.
Unfortunately I have only 5bmore payments left on my OnePlus 8 but I've got all the latest with my new addition to monthly payments lol my Pixel 6 Pro. I just want to play around band use my OnePlus for awhile but not on Android 11, I'm too used to 12 to want to go back lol. Do you know if they've even mentioned a date when it might be pushed for T-Mobile?
I can say that the wait for Android 12 on the OnePlus 8 was disappointing. It's a mess, full of bugs, and what does work, doesn't even work well. As a lot of other people have learned with other manufacturers and other devices. Android 12 is still pretty much a mess that is going to take a while to fix.
Really? I hadn't heard much about the 8 and bugs, probably because I'm using my pixel 6 right now and as I'm sure you know there was a ton of bugs for the 6 and 6 pro but I must have been extremely lucky because my experience with the pixel 6 was bug free and just great pretty much all around, I have no complaints. Hopefully by the time Android 12 reaches my T-Mobile variant of my OnePlus 8 most the bugs will be resolved hahaha! That made me laugh just typing it. When will a company, , clears throat, Google, just to name one lol stop pushing updates that clearly haven't been tested enough especially when they leave the final beta phase still completely broken and yet after basically no repairs they release the so called stable version which anyone that knows smartphones at all knows that's just the first wide open public beta, it's never stable enough for me to consider the messes they've released to be called stable, but the faster it's out the more other items, get pushed, also too early so they never lose site of that bottom line. Oh it's just sad really. But oh so true.
BTW thanks for the info on carriers not holding up the releases, I've always thought they had to add their own bloatware and whatever else they want to do with it to keep their feet in the pool at all times then release to their customers as they see fit. What you said made a lot of sense after I thought about it a little. Especially after a purchasing my pixel 6 because it's a T-Mobile variant, but being a pixel I get the new releases right away. The same time the unlocked versions get their updates so I totally believe you. I just wish Android 12 would be released for my OnePlus 8 so I can use that as my daily driver for a while again. But I went and ordered a pixel 6 Pro. So I really don't mind waiting longer for the one plus eight to update now since I'll be preoccupied with the pixel 6 Pro, hopefully without issue like it was with my original six, fingers crossed.
this is from a manufacturer that is no longer around...however how the updates are handled are still handled like this for every carrier..HTC just happened to be the only one to put it out for everyone to see how its handled..
Carriers definitely play a role in delays.
Carriers have little to no direct control in the development of the updates. However, they're the ones that put the requirements in place of which customizations/settings, extra apps, telemetry, restrictions, testing, etc, that the oems have to develop and implement, and the more they add or require, the longer you can expect the updates to take. If they didn't have additional requirements, it'd just be the unlocked version and there's be little delay (save time for testing/verification). So while they have little control, their extra requirements can still be a significant source of delays imo.
As examples of extra value that carriers require oems implement - potentially contributing to delays, look at things like Digital Turbine Ignite and SingleTap that allow bloatware and apps to be installed bypassing Google Play.
foobar wrote:
Carriers definitely play a role in delays.
Carriers have little to no direct control in the development of the updates. However, they're the ones that put the requirements in place of which customizations/settings, extra apps, telemetry, restrictions, testing, etc, that the oems have to develop and implement, and the more they add or require, the longer you can expect the updates to take. If they didn't have additional requirements, it'd just be the unlocked version and there's be little delay (save time for testing/verification). So while they have little control, their extra requirements can still be a significant source of delays imo.
As examples of extra value that carriers require oems implement - potentially contributing to delays, look at things like Digital Turbine Ignite and SingleTap that allow bloatware and apps to be installed bypassing Google Play.
It's already been pointed out since early life of Android. Even Google believed it UNTIL they actually did their own case study with Sony during an AOSP project. They found out carriers has very little to do with delays if any at all. HTC, Sony, Motorola, and Samsung rolled out timelines of how things are done, and quite a few of their development team managers have pointed this out as well. It's one of the reasons why if you go to other carrier forums in other countries they blame OEM's yet we blame carriers. Try buying a Samsung phone directly from Korea, and talk about bloat and carrier customizations and how does Samsung release that version first before US carriers? Oh I used to work for Samsung Korea for reference. Currently working for the DoD doing software.
Customization being a delay is the BIGGEST lie ever told. All carriers AROUND the world has these "customizations". Explain how carriers here are delaying months to years, but the rest of the developed world don't? They are all the same telemetry companies and ran by the same development companies around the world. custom apps for example are done in house and are updated through the app store and very little testing is needed as it can be done in house, and not part of the development process. See Google/Sony AOSP project. To make it FURTHER easier for this they made a carrier partition with specific APIs and can run on older software without carrier intervention. How can Apple do this worldwide and release 1 OS for every carrier if they need all these customizations? I have yet to see an app from any carrier that requires development with OS development to cause a delay.
Examples of SingleTap and Digital Turbine is a very poor example. If they are going to sideload the software only needs to be tested on a VM than actually through development. As a developer standpoint it make 0 sense to develop something you are going to sideload after the fact. As pointed they could just not develop at all and leave it in the carrier partition and it'll run correctly and has the permissions to do so. If Google changed the permissions it's a couple lines of code and viola still doesn't need testing. The only time this wouldn't work is IF OEM's changed how the carrier partitions works, but this could break project treble which is a violation of using Android with Google services.
There's a reason why Google releases a fully developed Kernel months in advance unless like previous versions of Android. Governmental involved has always been the largest delay for software updates. FCC, WiFi, Bluetooth, USB, Qualcomm(especially with CDMA), and a slew of other consortiums, All of these have varying laws and regulations which is the reason why OS versions were all over the place especially during Android infancy. Now you can finish the kernel test it out and see if everything works. You can then develop the OS around that without tweaking the kernel from that point. This is leagues better waiting for the kernel and OS to come and then do the kernel and OS at the same time. More things to go wrong with testing as OS and kernel will have to rewritten.
