One UI 5.0 Stable Release

@ArkDlk 

You can also use T-Mobile's own "Source of Truth", the tracker for your device! Since this hasn't been shared, I need to let you know that there is a specific page for this exact inquiry. 

Here is the page for the S22:

https://www.t-mobile.com/support/devices/software-updates/samsung-galaxy-s22-series-android-update

The good news is that, it's generally only a matter of time! After a device completes testing, it then goes on to complete the development stage before being published. SO the good news is, it's only an amount of time, in most cases...

The bad news, but other good news, is that there is no real time frame. We have these stages of development, but software is a fickle thing and it's understandable they'd rather side on shipping working software later than bad software sooner if possible. Sometimes, things don't work out, and ideally if your phone ultimately doesn't get the update, the news would be indicated on the same page. All is to say, that web page is the ultimate answer for your question.

I'd recommend using this source of truth for status update as the page will refresh when the update is published. When I updated my OnePlus 8T I knew the update was ready since the webpage refreshed and updated. I also knew something happened when the webpage was later deleted for my OnePlus 7T Plus 5G and I was able to alert users here to the issue.

Just wanted to leave you with this webpage since you are being told the same thing I was told, that the blame is based on your device manufacturer, so instead I wanted to give you T-Mobile's own tools for tracking this update so you have a better truth than the word of a forum user. I hope that helps :) If the page goes down, please let T-Mobile know so you can get an updated time frame for your Android Update. 

Lastly @tidbits Apple does do slow releases, known as "sever delayed requests" so basically this is a strange reply that isn't factually correct. Mostly this reply is trying to tell you it's not T-Mobile's fault. That's why I gave you T-Mobile's own tracker, to show you they have their *own* tracking for their *own* update for their *own* network, as opposed to…. Other carriers which have their own trackers and time-lines for development as well. This is obvious as Android 13 is currently on other devices but not T-Mobile devices. 

That is a very long explanation and I apologize for the amount of detail, but you deserve an honest answer, and I hope that clears things up.

not for hire wrote:

It is odd that phones locked to TMO (S22 series) are able to participate in the One UI 5 beta (unlike AT&T or Verizon), yet somehow, TMO can't get an OS update out in a timely manner? I was in the beta and received the stable version yesterday. IF TMO-locked phones can participate in the beta, then it is clear that the S22 series on TMO is ready for the stable update now.

Can you still get on the beta, thus get the stable?

tidbits wrote:

also want to say the reason T-Mobile doesn't have the "update" even though it has beta is VOLUME.  T-Mobile sells nowhere near amount of volume that ATT and Verizon does.  Also Android always goes through what is called a staggered release.  Not all devices gets it day one.  This is even from Google devices.  It goes something like 1% then 5% then 25%, and so on.  This is because if something hits the fan they can limit the amount of potential broken devices.  Apple on the other hand pushes out the updates all at once and if you see their forums a lot of complaints happen around update time.

Good point. Thanks.

BugPlusWont wrote:

Lastly @tidbits Apple does do slow releases, known as "sever delayed requests" so basically this is a strange reply that isn't factually correct. Mostly this reply is trying to tell you it's not T-Mobile's fault.

That's different than what a Staggered release is.  You can download the update through iTunes, or on WiFi even if you can't OTA it through carrier network which starts at day one for ALL iOS devices.  You need to understand the context of what a server delayed request is used for.  You don't have to wait for anything or anyone for the update.

That's why I gave you T-Mobile's own tracker, to show you they have their *own* tracking for their *own* update for their *own* network, as opposed to…. Other carriers which have their own trackers and time-lines for development as well. This is obvious as Android 13 is currently on other devices but not T-Mobile devices. 

Like I said before my guy…  You don't need the website to tell if you get the update or not.  It's already been known it's just a matter of when.  Samsung for as long as I have worked there has always tended to their biggest customers first.  I don't see that changing any time soon.  Funny thing since it isn't forked did you know if the author of this thread knew where to get the files he can install it and everything will work just fine since the update doesn't touch the carrier partition. It's been this way since the S7 when Samsung finally stopped forking their devices.

That is a very long explanation and I apologize for the amount of detail, but you deserve an honest answer, and I hope that clears things up.

looks like it is rolling out now.  T-Mobile webpage hasn't been update to reflect it.  Like a lot of us have been saying if they say you getting the update.  You getting it.  The site isn't updated quick enough to always give you the most accurate things.  It's only a matter of WHEN not IF you will get it.

https://www.reddit.com/r/tmobile/comments/yggghj/android_13_rolling_out_for_tmobile_for_s22_ultra/