In the United States at least, mobile firmware updates are subject to the approval of mobile carriers. Most phones that are released in both the United States and Europe are updated in the latter region before the former. American carriers are also a primary reason why most phones do not run stock Android [1].
Since some revenue sharing is already in place [2], and carriers make money regardless of what Android version their customers are on, I do not think it is the answer. Unless Google can find a way to reduce the control that carriers have (by weaning Americans off of subsidized phones, or by restricting Android software customization similar to iOS or Windows Phone), I am not sure things will change for the better.
[1]: http://www.theverge.com/2012/1/10/2697939/motorolas-sanjay-j...
[2]: http://articles.businessinsider.com/2010-03-25/tech/30041935...
On Android devices, the best analog to the BIOS would be the bootloader. Since most Android bootloaders are locked to prevent unsigned kernels from running, they are updated during OS updates. See http://www.extremetech.com/computing/120771-what-is-a-bootlo... .
but i agree with your points. just saying that there's probably a third issue as well.
I also think Google made this a lot worse by not being more open with ICS development. If Google had been more open with the kernel and drivers along the way, I think ICS upgrades could have been much easier and could be moving much faster as well.
Put in perspective - it took about 12 minutes after finding out about a new iOS release and having it on my device, and 12 months for the Android device.
FWIW, Apple don't exactly have an unblemished record in treating owners of existing iPhones properly, as anyone who suffered through the first few iOS upgrades on iPhone3G's after the 3GS came out. For a while even Apple native apps like Messages (the SMS app) were all but unusable on a fully updated 3G…
Having said that, I'm still overall much happier with the OS upgrade path my original iPhone -> iPhone 3G -> iPhone 4S has had, compared to the long delays in getting _any_ OS upgrades for my Galaxy S II (largely due to the carriers here in .au rather than Google's fault, but that doesn't make the feeling of lack of support any easier to stomach…)
when i first bought my dreadful nexus one, the only newly launched keyboard option i had was the backflip! a brick was faster. it was already announced to be relegated to 1.5 forever, and 1.6 was launched before it was out. or something like that. older keyboard availables, G1, too slow, no support. droid. slow, no memory, no GSM.
The Desire Z is still sold though it is getting harder to find (e.g. retailers like expansys don't seem to have it any more). On the other hand, T-Mobile also recently had a surprise revival sale (now over, I believe) on its twin (the G2).
There are also a fair number of lower-end QWERTY devices (both Blackberry-style and sliders), but there is absolutely room for a high-end QWERTY "hero". Personally, I'm rooting for an HTC One Z (with a T-Mobile G3 twin?), but we'll see.
will do take a second look at them
http://allthingsd.com/20110420/the-most-successful-store-no-...
$1.4b/quarter as of last year. Their margins are a lot tighter on media sales, but even so, that's probably a good chunk of change.
That being said, it is interesting how Apple's support of old hardware is the dual of Google's.
Google does a bad job of getting OS updates to older hardware, but they do an impressively good job of supporting their applications on older hardware and OSes. Outside of the deliberate exception of the Chrome Beta, I can't think of an official Google app for Android that doesn't support at least Froyo and many go back further. My G1 (running Donut) was still getting Google app updates for a good chunk of last year. I happen to know that because I picked it up for a memorial tweet on the G1's third anniversary and was surprised with all the update notifications I got.
Meanwhile, Apple is very good about getting OS updates to older devices. But when you look at their app support, it doesn't look nearly so good. Everyone talks about Siri, but did you also know that the original iPad doesn't support iPhoto or iMovie (see: http://www.theverge.com/2012/3/9/2856499/iphoto-ios-app-ipad... )? iMovie is particularly damning because the first iOS version (for the iPhone 4) was released less than 3 months after the original iPad.
I understand why Android geeks are desperate to have the very latest OS version running on their device (as a weird point of OCD-geek pride). I have no idea why Apple fans should care so much about what version number Android phones have when Google is near constantly updating the software that runs of them. Seems to run counter to their stance on the features vs. specs debate on hardware, where user experience is more important than the number attached to something.
"Normal people" on the other hand, clearly don't give a damn, if they are even aware of this "issue", and have no reason to.
And those contracts are still giving them money, otherwise they wouldn't think twice about breaking it. All apple actions can be directly translated to immediate profit goal.
However, that diversity in hardware is also the biggest problem with the platform. Handset manufacturers seem to look at a device as a "sell and forget" sort of item. They make it, sell it, and then move on to the next project.
It's too expensive, in their minds, to support a handset that they've already sold. They make money by selling more handsets, not by putting large amounts of effort into supporting and updating old hardware from which there is no revenue stream.
Apple, on the other hand, actually has a significant revenue stream from existing hardware through the sales of apps, music, and books. So, by providing updates for older versions of the hardware they are improving their ability to collect additional revenue. For example, when they added in-app payments, those APIs were available to all existing iPhone users, not just the newest users and thus were able to extract more profits from those existing users.
In the Android world, a manufacturer only makes money from the original sale. So, it seems that in order for Google to encourage on-going support, they should:
1. Participate in a revenue sharing program from app sales from the manufacturers phones that are running the most current release of the OS.
2. Improve the situation with drivers the large variety of hardware. If the Google distribution supported a large amount of hardware (CPUs, GPUs, sensors, etc) "out of the box", perhaps it would be easier for manufacturers to get the OS running on their devices and thus take less time to get updates to market. Or perhaps I'm being naive and there's something else that's holding up updates other than technical issues with drivers/hardware compatibility.