Forum Discussion
T-Mobile retroactively removes status updates related to software updates
The company T-mobile has removed the page for tracking Android 12 Development for the OnePlus 7T Pro
I made my purchase decision with the promise that T-mobile would be able to handle updating the phone to the software that the manufacturer has already finished working on.
A year later, and they've taken down the page for the OnePlus 7T Pro, seemingly throwing in the towel on this project and those customers.
Remember, never buy a product based on future promise, because even if T-mobile promises on a website that this phone will get Android 12, they'll just 404 that page when satisfying their customers is inconvenient compared to making money.
They promised, they didn't predict.
I can want my device to perform as advertised, yes, because I spent money on the premise of function that was promised by T-mobile.
You don't know what you're talking about either with this one, stop replying please I'm trying to show that the development page that promised development was removed.
https://www.t-mobile.com/support/devices/software-updates/oneplus-7t-pro-update-to-android-12
In the industry we call this a "dirty delete" and honestly if you can't handle the truth that I've been specifically screwed over by specifically T-mobile, go touch grass. It's the matter of fact and stop trying to tell me my opinion on Android 12 when I never asked you and don't care how buggy you think it is.
This Phone has a Snapdragon 865+ and 12gb of Ram you're gonna come on the forum and try to justify that they can't develop for this phone that's more powerful than plenty of computers. What a joke. It's not that they can't, it's that they won't, because they stopped caring about making good on their software promise and that lack of follow-through should be noted! They could develop this update, but don't want to because people like you, people like you @syaoran who want a job at T-mobile so bad you'll defend them even if they give customers a fat middle finger.
Your replies are unhelpful and irrelevant. Reported numerous times. Don't reply unless you can understand T-mobile's ownership of the issue.
syaoran wrote:
HeavenM wrote:
Hey all.
Gracias @gramps28 for supplying that link for the Android update tracker. I did confirm with our teams that OnePlus is still developing the update for the 7T Pro 5G. There is no launch date for the update and it may be after the Android 13 update starts rolling out so that is why the page was removed at this time.
A few things that I did want to clarify on the update process.
- T-Mobile and other carriers provide requirements to the OEMs that are taken into account during development. The manufacturers build the update and then we test it out before allowing it to be launched to our customers. We can reject an update if it does not meet our standards for quality.
- Starting development on an OS or update does not guarantee that it will be released. There are a ton of factors that can cause the decision to be made not to proceed with testing or deployment and that decision is usually made by the manufacturer unless the carrier tests the final product and say it is not to our standards.
If T-Mobile actually does some testing and I mean, more than just with their bloat and carrier aggregation or a quick 5 seconds of, just to say we did. I have never seen any evidence of that in open or closed beta sides of OnePlus, LG, or Samsung channels and from talking with T-Mobile's Network Engineering Team. If I take your word at face value… T-Mobile clearly needs to do a way better job at this "testing"!
Their testing is against their network not the actual OS itself. It's honestly what Sony has been doing when I worked there with my cousin who also worked at Samsung. Yes all carriers around the world "test" updates. Most cases they'll test the OS it the sense it works, and most of it will have more to do with carrier connectivity, and security. Carriers don't see logs, or code for example to even actually test better than an average joe testing the beta. People are unaware of this. Often when something passes some companies end up updating some of their apps and don't even bother testing them or push out the update. Just small example. Google had a problem with Words With Friends 2 which broke a feature for their Pixel Line. Carriers already tested and approved the update. There are only so much testing that can be done and often there's a deadline often carriers are constrained to. US carriers are under the thumbs of overzealous customers to push out updates unlike the rest of the world.
tidbits wrote:
syaoran wrote:
HeavenM wrote:
Hey all.
Gracias @gramps28 for supplying that link for the Android update tracker. I did confirm with our teams that OnePlus is still developing the update for the 7T Pro 5G. There is no launch date for the update and it may be after the Android 13 update starts rolling out so that is why the page was removed at this time.
A few things that I did want to clarify on the update process.
- T-Mobile and other carriers provide requirements to the OEMs that are taken into account during development. The manufacturers build the update and then we test it out before allowing it to be launched to our customers. We can reject an update if it does not meet our standards for quality.
- Starting development on an OS or update does not guarantee that it will be released. There are a ton of factors that can cause the decision to be made not to proceed with testing or deployment and that decision is usually made by the manufacturer unless the carrier tests the final product and say it is not to our standards.
If T-Mobile actually does some testing and I mean, more than just with their bloat and carrier aggregation or a quick 5 seconds of, just to say we did. I have never seen any evidence of that in open or closed beta sides of OnePlus, LG, or Samsung channels and from talking with T-Mobile's Network Engineering Team. If I take your word at face value… T-Mobile clearly needs to do a way better job at this "testing"!
Their testing is against their network not the actual OS itself. It's honestly what Sony has been doing when I worked there with my cousin who also worked at Samsung. Yes all carriers around the world "test" updates. Most cases they'll test the OS it the sense it works, and most of it will have more to do with carrier connectivity, and security. Carriers don't see logs, or code for example to even actually test better than an average joe testing the beta. People are unaware of this. Often when something passes some companies end up updating some of their apps and don't even bother testing them or push out the update. Just small example. Google had a problem with Words With Friends 2 which broke a feature for their Pixel Line. Carriers already tested and approved the update. There are only so much testing that can be done and often there's a deadline often carriers are constrained to. US carriers are under the thumbs of overzealous customers to push out updates unlike the rest of the world.
Not really overzealous customers, just provide the written, stated, and implied products services and maintenance you (carriers) said you would when you took my money that's now sitting in your pockets providing funds and updates for your infrastructure and other phones updates. Ever heard of "Mr. Magnuson Moss"?
Just to be clear you= T-Mobile
BugPlusWont wrote:
You're wrong. T-mobile makes the updates for the T-mobile Variant, that's why there is a dedicated page for development.
The bootloader for the T-mobile Variant is custom and has to be circumvented to make the phone a true "unlocked" version.
You don't know what you're talking about and very unhelpful, reported.
Don't forget the "T-Mobile 5G chip" that I was told by a T-Mobile worker isn't a 5g phone. 😑
A-carriers dont create the updates..this is all on the OEM…
B-have you seen the train wreck 12 has been across the board for those same OEMs?
C-if they truly did yank it its due to the update not being compatible or way to many issues to try and fix...and even then the carrier doesnt make the decision to pull it..the OEM does..
D-the 8T already received it..and as you can probably guess by reading this..it didnt go well..
your examples of 12 being a train wreck are in this forum..you can see both the OP8 and 9 ran into a crazy amount of issues after 12..as it did for a handful of Samsung devices as well.
OEMs do the updates. Not carriers. Have you noticed Google stopped blaming carriers. This happened almost a decade ago. Google/Sony did an AOSP project and found carriers don't touch code. Carriers "bloatware" is done just like ANY other app you find in the play store. They also found out the longest delay was themselves inadvertently. Android 4.0 and beyond became more modular to allow co-development due to government, licensing, and other consortiums. Since 4.0 Google started releasing kernel sources for testing while they build android. They started to go more and more module with Project Treble. All carriers do is test the finished project and if they find security flaws against their network they send it back. Rinse and Repeat.
FYI - HTC, Sony, Samsung, and LG have admitted to this by releasing their development schedules back then. Rest of the world started to blame OEMs, and only here in the US we still blame carriers. Funny enough Asia markets have way more "bloatware", and by that logic they should always be last to get updates, but surprising they tend to be first in a lot of cases.
According to this website that's updated regularly says the 7T is still in the development stage. Also says carriers tests the os then once approved the manufacturer sends out the update.
https://piunikaweb.com/2022/08/04/t-mobile-verizon-sprint-att-android-12-update-tracker/
HeavenM wrote:
Hey all.
Gracias @gramps28 for supplying that link for the Android update tracker. I did confirm with our teams that OnePlus is still developing the update for the 7T Pro 5G. There is no launch date for the update and it may be after the Android 13 update starts rolling out so that is why the page was removed at this time.
A few things that I did want to clarify on the update process.
- T-Mobile and other carriers provide requirements to the OEMs that are taken into account during development. The manufacturers build the update and then we test it out before allowing it to be launched to our customers. We can reject an update if it does not meet our standards for quality.
- Starting development on an OS or update does not guarantee that it will be released. There are a ton of factors that can cause the decision to be made not to proceed with testing or deployment and that decision is usually made by the manufacturer unless the carrier tests the final product and say it is not to our standards.
If T-Mobile actually does some testing and I mean, more than just with their bloat and carrier aggregation or a quick 5 seconds of, just to say we did. I have never seen any evidence of that in open or closed beta sides of OnePlus, LG, or Samsung channels and from talking with T-Mobile's Network Engineering Team. If I take your word at face value… T-Mobile clearly needs to do a way better job at this "testing"!
