Hacker News new | ask | show | jobs
by vardump 4033 days ago
> Can Google not poach one or two of Apple's negotiators to go to the right meetings at Motorola, Verizon, etc to talk about updates?

I don't understand why things like these are necessary in the USA. Why should network operator have control to which version you're running? Most other places you can just get new firmware directly from manufacturer.

2 comments

I don't understand it either. How should the carrier have any say/input into when the firmware on these phones is updated?
Because they also do firmware customizations with their own apps, services and UI according to their marketing material.
The thing that's confusing to me is that the carriers don't automatically default to the newest version of the OS.

Even if it weren't a contractual obligation, I can't imagine, say, the AT&T store loading a phone right now with iOS 7

So, you'd be fine with your ISP being the gatekeeper for which operating system(s) and version(s) you can run on your computer?

The U.S. system where operators are such gatekeepers for mobile devices is an anomaly. It doesn't need to be so, and it is not so elsewhere.

I don't understand the overall picture of the U.S. telecom industry in the first place. Slow speeds, data caps, bad coverage, high prices and control freak carriers.

I didn't say anything about them "controlling" what I can run on my computer/phone.

They load it with a default that you can change. That doesn't inhibit my choice in the slightest.

But a large number of people don't care to change their OS from the default, so the ecosystem gets loaded with a large number of those phones.

I just don't understand why the telecoms wouldn't use the newest OS as the default.

> I just don't understand why the telecoms wouldn't use the newest OS as the default.

Why would they allow you to upgrade the OS when they can sell you a new phone and a new multi year contract. It's a pretty basic strategy.

Uh carriers across Europe and Australia don't restrict OS updates afaik
Kinda. My Xperia Z didn't update to Kitkat when it was available. I bought it at JB-HIFI and therefore it came with Telstra junk on it. In /system/build.prop there's a setting called Customisation Number. So I used towel root and changed it to a stock number and the system updated to Kitkat and removed the non-uninstallable Telstra junk.

Telstra didn't update because of a battery issue. Which was true... the battery died quickly if you left the GPS on. I didn't use the GPS much so I left it off. (This issue has since been resolved, then telstra enabled the update)

Considering I didn't even have Telstra as a carrier. it was because JB-HIFI is a Telstra reseller that this happened.

It's because the Manufacturer agreed to only update when Telstra updated. It's all through the Sony update software.

I don't think carriers do anywhere. I'm confused.
a big reason is that you actually need to test whether the newest version works well. Even the jump from 4.4 to 5 has some performance hits. Not to mention when we get beyond vanilla android, custom home screens and stuff are extremely sensitive to base OS changes.

Also, the phone companies themselves need to put out the updates, which isn't happening a lot of the time (or with 6 month+ delays).