Wireless providers like to brag about two things: their network and their offerings. Something you do not often hear about is software updates. They should be easier than ever for Android device manufacturers to implement thanks to the Project Treble framework, but when the phone is a model specific to a US operator, it must be sent to the operator for additional control before being passed on to the consumer. . But sometimes you get the feeling that the telecommunications companies just don’t care, especially when major security updates from January only reach your device in May. So what gives?
Let’s start with the current state of how updates are revealed in the US, specifically with the big three.
AT&T is the most opaque about software updates. Users should navigate to the company’s wireless support pages, select their device, and then scroll down the list of items to “System” and then click “Software Version”. The company reveals the latest OS version applicable to the device but does not provide any details about security fixes. Navigating to att.com/softwareupdates redirects to a page that happily tells you that your device is up to date. Not very useful.
Ma Bell used to detail software update stories for each device, but has stopped doing so at some point, it seems.
Verizon is (a) second best in this pool. Each device on the rollers has its own dedicated software update log. If you are particularly confident and know the model name your company uses, you can crack a direct URL input formatted as such: https://verizon.com/support/device-name-update/. Otherwise, go to Support> Mobile> Device Setup & Support, select a device, then swipe down to Operating System and Software and tap “Device Name Software Update.” Yes, it’s a bit confusing, but you get a list of the latest software updates, including when they were released, the build number, the patch level, and the OS version.
Bound for the second – because none of them deserve merit in my opinion – is T-Mobile, which hosts a site dedicated to tracking devices while they go through the update process. Devices in the development stage indicate that the carrier and OEM have agreed to distribute a new update to the device and that the work has started at the end of the manufacturer. The test phase moves the ball onto T-Mobile’s court and immediately precedes the roll-out. Right now, the company’s benchmark lies with the Android 12 upgrade. The company also used to have update stories, but it has since dropped them.
Things are bad. We know it. And we know it can get so much better. In Canada, Telus carefully maintains a list of devices, what the company is working on for each one, whether it’s a security update or a full OS bump, and a target date for when things go live. Rogers, also up north, is another brand putting its name on the line. Fido and Koodo too. And if you want to go down under, Vodafone has you covered in Australia, and states what you can look forward to with the next big updates. How each operator handles the schedule will vary and whether they reach the target dates they say they need to, yes, it is up to the customers to hold the company accountable. And they do.
Of course, we think it’s important to have the whole picture – going forward and backwards – to help inform consumers and let them put together what they need to do to protect themselves from unaddressed security threats that could affect their phone use.
We have asked AT&T, T-Mobile and Verizon whether they will consider putting stories and schedules in place. We’ll update this story if we hear back.
Read Next
About the author
