Or is it that Apple give you the Henry Ford - any colour as long as it is black methodology and Android based HW manufacturers offer a more custom solution, (i.e. specific modems and apps etc for specific carriers?)

Personally, the approach I have taken is to load a debranded rom on my phone that by history has always got any OTA updates soon after Samsung releases them cutting out the whole carrier approval delay

Sure your OS gets updated, but what happens when Apple release new software and is bricks mobile networks around the world? This has happened in the past, and I'm sure will continue to do so with Apple's poor track record of their handling of network signalling in iOS and full 3GPP compliance. When this happens networks are hamstrung - they can't go and dump every iOS device off their network, although I'm sure in several instances in the past they would have loved to have done so.

I guess Telecom like to keep there Network working well and if there is an update that is complex or doesn't work well for the dumbest users then nobody gets it. I think Telecom like to keep things simple for the helpdesk and so limiting the number of updates helps there as there staff doesn't need updated training.

A bit like, you have a hammer and nail that does the job, why would you want a screw driver and screws.

Like Wade says, get the updates from the phones provider if you can, they are the ones that build it after all, Telecom is just the standard network it runs on.

hellonearthisman: I guess Telecom like to keep there Network working well and if there is an update that is complex or doesn't work well for the dumbest users then nobody gets it. I think Telecom like to keep things simple for the helpdesk and so limiting the number of updates helps there as there staff doesn't need updated training.

A bit like, you have a hammer and nail that does the job, why would you want a screw driver and screws.

Like Wade says, get the updates from the phones provider if you can, they are the ones that build it after all, Telecom is just the standard network it runs on.

I would love to get my updates directly from HTC. If Telecom could arrange to release my imei so I could do that without having to unlock, root, install a custom recovery and load a ROM that would be great.

Edit: And as for their helpdesk, they can't cope now and are worse than useless, I can't see how multiple updates could make them any worse than they already are!

hellonearthisman: Like Wade says, get the updates from the phones provider if you can, they are the ones that build it after all, Telecom is just the standard network it runs on.

Then you have settings like Dormancy, which is used by one network in New Zealand but not the other one. You install a non-branded ROM, or a third-party ROM with the wrong settings, and your battery goes the way of the dodo. Are you going to blame the operator, the manufacturer or yourself who decided to install something without knowing exactly is happening behind the scenes?

hellonearthisman:?Like Wade says, get the updates from the phones provider if you can, they are the ones that build it after all, Telecom is just the standard network it runs on.

Then you have settings like Dormancy, which is used by one network in New Zealand but not the other one. You install a non-branded ROM, or a third-party ROM with the wrong settings, and your battery goes the way of the dodo. Are you going to blame the operator, the manufacturer or yourself who decided to install something without knowing exactly is happening behind the scenes?

Yep, I agree with the fast dormancy argument, but ROM cooks are able to put a toggle in their ROMs, so how long does it take for TNZ to do the same. Or edit one line in the modem software to change the =1 to an =0. And are there any other networks in the world that don't use fast dormancy that have the same abysmally tardy update history as TNZ?

hellonearthisman:?Like Wade says, get the updates from the phones provider if you can, they are the ones that build it after all, Telecom is just the standard network it runs on.

Then you have settings like Dormancy, which is used by one network in New Zealand but not the other one. You install a non-branded ROM, or a third-party ROM with the wrong settings, and your battery goes the way of the dodo. Are you going to blame the operator, the manufacturer or yourself who decided to install something without knowing exactly is happening behind the scenes?

Yep, I agree with the fast dormancy argument, but ROM cooks are able to put a toggle in their ROMs, so how long does it take for TNZ to do the same. Or edit one line in the modem software to change the =1 to an =0. And are there any other networks in the world that don't use fast dormancy that have the same abysmally tardy update history as TNZ?

It would be great if it was supported, but at the end of the day the number of people who install ROMs is small compared to those who just want a phone to check email, Twitter. And the number of people who install ROMs and know that there are settings to be adjusted is even smaller.

Wade: Or is it that Apple give you the Henry Ford - any colour as long as it is black methodology and Android based HW manufacturers offer a more custom solution, (i.e. specific modems and apps etc for specific carriers?)

Actually the way I see it, Apple makes a "Rolls-Royce" and the rest are the "mass-market" options. Sure you can get cars with better features than a "Rolls Royce", faster (Audi), better engines (Mercedes), better transmissions (Lexus), better, this and that (others). But with a Rolls-Royce, you just know it has "quality", which is very hard to define, but you know it is there. It just does what it does very well.

Plus the fact the Android handset manufacturers stop giving software updates, after about a year or so after the phone is released. However, just like cars (after the recalls have stopped, and warranty has expired), you can still custROMize it.

hellonearthisman:?Like Wade says, get the updates from the phones provider if you can, they are the ones that build it after all, Telecom is just the standard network it runs on.

Then you have settings like Dormancy, which is used by one network in New Zealand but not the other one. You install a non-branded ROM, or a third-party ROM with the wrong settings, and your battery goes the way of the dodo. Are you going to blame the operator, the manufacturer or yourself who decided to install something without knowing exactly is happening behind the scenes?

Yep, I agree with the fast dormancy argument, but ROM cooks are able to put a toggle in their ROMs, so how long does it take for TNZ to do the same. Or edit one line in the modem software to change the =1 to an =0. And are there any other networks in the world that don't use fast dormancy that have the same abysmally tardy update history as TNZ?

It would be great if it was supported, but at the end of the day the number of people who install ROMs is small compared to those who just want a phone to check email, Twitter. And the number of people who install ROMs and know that there are settings to be adjusted is even smaller.

If you know how to do it, go for it.

I don't want to have to do it. I want TNZ to do it. My point is if ROM cooks can change one line of code why does it take TNZ months to do it and test it. The two firmware updates that my One X is missing have reportedly reduced force closes, stopped screen flicker and improved battery life. I am sure that even the people who only have their smartphones to check email and do facebook and twitter would appreciate a battery that can last a whole day.

I don't want to have to do it. I want TNZ to do it. My point is if ROM cooks can change one line of code why does it take TNZ months to do it and test it. The two firmware updates that my One X is missing have reportedly reduced force closes, stopped screen flicker and improved battery life. I am sure that even the people who only have their smartphones to check email and do facebook and twitter would appreciate a battery that can last a whole day.

Please ignore the fact I work for Telecom. I work in the fixed space, not mobile so I'm only going from my experience as a user in this case...

ROM cooks can do it quick because they have exactly zero responsibility. I have personal experience with several ROMs (from xda etc) on an old HTC Desire that broke many features including SMS and MMS.

I now have a personal SGS3 (purchased from Harvey Norman) and while I have rooted it so I can continue to use Titanium backup, I have left the default ROM image on it.

I don't want to have to do it. I want TNZ to do it. My point is if ROM cooks can change one line of code why does it take TNZ months to do it and test it. The two firmware updates that my One X is missing have reportedly reduced force closes, stopped screen flicker and improved battery life. I am sure that even the people who only have their smartphones to check email and do facebook and twitter would appreciate a battery that can last a whole day.

Please ignore the fact I work for Telecom. I work in the fixed space, not mobile so I'm only going from my experience as a user in this case...

ROM cooks can do it quick because they have exactly zero responsibility. I have personal experience with several ROMs (from xda etc) on an old HTC Desire that broke many features including SMS and MMS.

I now have a personal SGS3 (purchased from Harvey Norman) and while I have rooted it so I can continue to use Titanium backup, I have left the default ROM image on it.

Cheers? N

I appreciate what you are saying. And envy the fact that you can simply root your S3 without putting your hand up to say "please void my warranty" by having to go through htcdev. My gripe is it shouldn't take 100 days to modify (to suit the network) and test firmware used around the world that essentially just contains bug-fixes.I am glad you bring up the subject of responsibilty though. My phone is a high end handset, the latest generation in fact, I believe Telecom has a responsibility to me as user to keep my phone up to date. Or at the very least communicate that the later versions of the firmware are not stable on their network.The ultimate denial is contacting Telecom's helpline to be told it is HTC's fault.....

1. What makes you/people think Telecom/insert network provider has the responsibility to upgrade your software after purchase? Given their track record I certainly wouldn't expect updates to be free flowing when purchasing from Telecom directly.

2. In the blog post they state " We have never held back an available update for any other reason than the release failed our testing programme and the manufacturer was unable to resolve this. This would have translated into a substandard customer experience." However it wouldn't really be appropriate commercially for them to say publicly what is or isn't working, that's really between them and the OEM / Google. But if you're wondering why any particular update is taking a while then reading between the lines of the above excerpt makes it pretty clear to me.

One thing that a lot of you are forgetting is that the Android model of mobile carriers approving software before it's released is nothing new - it is the same model that's been in use since the late 90's. I recall BellSouth even launching an Ericsson phone one weekend that didn't work with their network and resulted in them having to recall 5000 odd phones in the weeks following.

Ever since manufacturers started making software updates available to end users it's always required carriers to approve this first. With Nokia phones for example you'd often find it could take months for updates to appear in some markets, hence the popularity of changing product codes. Even before OTA and downloadable end users updates were available software testing was done before new software was even made available to service agents.