Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS 10 Carrier Updates Causing Issues for T-Mobile Users in U.S., Telstra Users in Australia

I did the carrier update and iOS update using iTunes as I got promoted for both when I plugged my 6S in and worked fine. Over air seems to be slower and have a higher proficiency for an issue
 
Luckly i have had no issues so far and im not in a great coverage location. I have one bar and just playing with the speed test everything seems fine maybe even a little bit faster.
 
BeauGiles said:
A Telstra employee replied in that Whirlpool thread, confirming they are aware of it, and it's not limited to iOS 10.

Just a update – we've narrowed the issue down and it is not specific to iOS 10, we've found it on users with iOS 9 as well. Still working to address it.​
Click to expand...
I have no issue ... updates to iOS 10 TMobile

With no issue .....
 
emm386 said:
Now who's to blame here?

Apple is probably already "investigating". As usual. Something they prefer over testing prior to rollout.

And they will claim that only a tiny insignificant amount of users were affected. As usual.
Click to expand...
Many issues usually do only affect a small amount of users, but either way- it's all Apple's fault. Because everything bad that's ever happened anywhere is Apple's fault.
 
  • Like
Reactions: saxon48
sbailey4 said:
Reverting to 9.3.5 will not resolve it. Its a carrier update not iOS.
Click to expand...

I had problem in Irvine. Spotty coverage. When upgrade to IOS 10. Nothing work as soon as i leave my house. Require a reboot. But Downgrade back to IOS 9.3.5 (carrier setting is back to: 24.2). Did not have problem after that. SO downgrade helped.
 
Have had problems since upgrade yesterday. Just called T-Mobile. They claimed to have done something. Will see!
 
talmy said:
Have had problems since upgrade yesterday. Just called T-Mobile. They claimed to have done something. Will see!
Click to expand...

thanks for sharing..... it was very painful yesterday, upgrade... restore... downgrade... start all from scratch... I will wait for confirmation from more people before going back to 1OS 10
 
ATT is screwed up also. Too many times it gets stuck on "E". You have to Airplane mode then out to get back to LTE or 4G.
 
TMRJIJ said:
Carrier update not Apple update. It's T-mobile's burden to fix.
Click to expand...

It could be Apple's problem, if iOS 10 is not handling carrier updates correctly, which is probably why they are looking into it. Seems like it would be T-Mobile's problem, but how confused would you have to be to screw up that basic config?
 
emm386 said:
Now who's to blame here?

Apple is probably already "investigating". As usual. Something they prefer over testing prior to rollout.
Click to expand...
T-Mobile is to blame.

Of all the things on an iPhone, the only part that Apple doesn't have control of is the carrier. If T-Mobile pushes out bad settings and there's something wrong with them, that's no more Apple's fault than an app in the app store being buggy. Less than even most there, in fact, since the bug only appears when interacting with an external piece of hardware (the cell tower), at that.

That said, it certainly isn't everyone--I'm on T-Mobile and both of the phones in my house seem fine.
 
  • Like
Reactions: ILikeAllOS and Lancetx
Makosuke said:
T-Mobile is to blame.

Of all the things on an iPhone, the only part that Apple doesn't have control of is the carrier. If T-Mobile pushes out bad settings and there's something wrong with them, that's no more Apple's fault than an app in the app store being buggy. Less than even most there, in fact, since the bug only appears when interacting with an external piece of hardware (the cell tower), at that.

That said, it certainly isn't everyone--I'm on T-Mobile and both of the phones in my house seem fine.
Click to expand...

Did you stop to think that iOS10 may not be handling new carrier settings correctly? Not sure if any other carrier has pushed new settings since iOS10 or if T-Mobile is the first to do so. But please, continue with your absolute statement.
 
drewyboy said:
Did you stop to think that iOS10 may not be handling new carrier settings correctly? Not sure if any other carrier has pushed new settings since iOS10 or if T-Mobile is the first to do so. But please, continue with your absolute statement.
Click to expand...

iOS 10 on our 6S was working fine with 25.0 and following the update to 25.1 is when the issues started. I've kept my 6+ on 25.0 and had no issues other then it bugging me to update my carrier settings. You'd think there would be a way for T-Mobile to stop pushing the carrier update if they know it's causing issues.
 
drewyboy said:
Did you stop to think that iOS10 may not be handling new carrier settings correctly? Not sure if any other carrier has pushed new settings since iOS10 or if T-Mobile is the first to do so. But please, continue with your absolute statement.
Click to expand...
It's certainly possible, but seems unlikely, since it would mean that iOS10 was able to read and apply the new carrier settings, but somehow goofed them up during installation such that they still function but have bugs.

More to the point, I would hope that T-Mobile actually tests new carrier setting rollout before making them live, so even if that were true I would expect them to have caught this and reported it to Apple while testing these new setting pushed out to iOS10 during the GM period, and held off making it live to everyone in their customer base until the bug was fixed.

It doesn't matter whether the actual bug is in iOS or the settings, T-Mobile is responsible for making sure those settings are going to work with whatever OSes they're pushing them to.

Now, maybe I'm wrong and Apple doesn't let major carriers test OTA settings rollout until they're pushing them live to several million customers, but that would kind of surprise me.

Or maybe they don't let carriers test OTA settings rollout on beta OSes, but in that case I don't see why T-Mobile wouldn't have waited until the OS was released and they could test it properly before pushing it to all customers.

Or, heck, maybe the carrier settings are entirely done in-house by Apple. That would make it Apple's fault, not T-Mobile's, although again, it would surprise me.

And I say this as a T-Mobile customer. If it's an uncommon bug maybe they just didn't stumble upon whatever combination of local and cell tower hardware and software triggers it, and I'm not going to get too worked up if they resolve it quickly, but it's their responsibility to make sure it works.

[Edit: Although T-Mobile seems to be claiming that the problem is universally with iOS10 and has nothing to do with the carrier update, which would be a different situation. Still a weird situation, though--why wouldn't they have caught this bug with the GM unless it's extremely rare, and why would Telstra be claiming that it's universally a problem with the settings, not the OS, unless their problem is completely different and just has coincidental timing?]
 
Last edited:
  • Like
Reactions: coolfactor
BeauGiles said:
A Telstra employee replied in that Whirlpool thread, confirming they are aware of it, and it's not limited to iOS 10.

Just a update – we've narrowed the issue down and it is not specific to iOS 10, we've found it on users with iOS 9 as well. Still working to address it.​
Click to expand...

Sounds familiar. Here in the Netherlands something similar happens with the local KPN network.
The internet connection simply breaks, without losing the 4G status sign on screen. This happens when the phone is switching over to another cell tower while the network is very busy with other connections.
Only a single toggle between 4G and 3G (or 2G) mode helps reconnecting.
When iOS 9.3.5 came out, that problem seems solved. At least on a iPhone 6S and SE.

I'll stay on iOS9 for a while.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back