Earlier quoted context omitted.
You should include iPod Touch and how apple forces a charge for updates on that device. This chart is also skewed a bit and should be based on intervals of releases rather than "years since". I don't recall seeing any iOS5 backports to iPhone 2G or 3G.
I don't think Apple charges for iPod touch updates anymore.
Android Orphans: Visualizing a Sad History of Support
141–150 of 235 posts
Re: Android Orphans: Visualizing a Sad History of Support
#142Earlier quoted context omitted.
How does it solve the issue? By making the UI better? But won't OEMs want to "differentiate" by installing their own bloated flashy custom UI? Not to mention the uninstallable adware and junkware installed and always running in the background. Does ICS solve this?
Yes, ICS solves that. Even if the apk is installed in system partition (that means you can't uninstall it), you can mark it hidden and the system will never take it into account at startup, intent broadcast or in other situations. It is as good as removed (except that it physically can't be removed, because you may want to restore the phone to factory settings).
Re: Android Orphans: Visualizing a Sad History of Support
#143Earlier quoted context omitted.
The problem is that you're relying on a third party which does it in their free time. I am not sure they're up to the level of the Linux kernel or Firefox yet. And installing stuff on a PC is ingrained into people's psyche, if they can't do it themselves, they get some other folks to do it for them. Upgrading phones? Not so much. My friend never updated her iPhone 4 once. She once used iTunes to transfer songs to it…
That's why this entire topic is a tempest in the teapot. Only us geeks and computer enthusiasts care about firmware updates. In real life, I know many people who are satisfied with their Android 1.6, 2.1 and iOS 3.x. These people, even if they know that upgrade is available won't bother. The existing device with it's current firmware works for them, so why change it.
Re: Android Orphans: Visualizing a Sad History of Support
#144Re: Android Orphans: Visualizing a Sad History of Support
#145Re: Android Orphans: Visualizing a Sad History of Support
#146There's a major point that can be added to the Why Don’t Android Phones Get Updated? section: Third party skins and interfaces. HTC's Sense, Motorola's Motoblur and co can only introduce an engineering overhead and delays in upgrading. I would much rather they concentrated on making awsome hardware and leaving the UI to Google, rather than attempting to differentiate themselves in this way.
If I were Motorola or Samsung, though, there's no way I'd do that. Without differentiation, you're selling a commodity product. If you're selling a commodity, there are no margins. I agree with you that it would be better for the Android ecosystem if they would, though.
Re: Android Orphans: Visualizing a Sad History of Support
#147- You can't assume what's going to be on the phone, software wise. Each maker evidently messes with it, sometimes even changing the interface itself. I've also read stories of bloatware being added.
- You can't be sure how software updates are going to be handled, because that varies depending on maker and carrier, meaning you might not get updates they same time others do (this is also a problem for Windows 7 Phone).
- Crappy cell provider logo plaques on the hardware (I detest that).
- Multiple/competing app stores.
I believe that Android has a lot of promise, but Google really needs to start exhibiting some control over what's going on.
Re: Android Orphans: Visualizing a Sad History of Support
#148I think that the fact that the chart stopped at June 2010 makes it looks much worse than it is now. Android is newer than iOS and works on a very different environment. Support 4 devices is much easier than 4 thousand. If you extend this chart to 2011 you will notice that the platform is more mature and most of the phones will receive ICS (my wife Galaxy S is a relatively old device and will get it).
Re: Android Orphans: Visualizing a Sad History of Support
#149Earlier quoted context omitted.
How does it solve the issue? By making the UI better? But won't OEMs want to "differentiate" by installing their own bloated flashy custom UI? Not to mention the uninstallable adware and junkware installed and always running in the background. Does ICS solve this?
Yes, ICS solves that. Even if the apk is installed in system partition (that means you can't uninstall it), you can mark it hidden and the system will never take it into account at startup, intent broadcast or in other situations. It is as good as removed (except that it physically can't be removed, because you may want to restore the phone to factory settings).
Is there a UI function in the OS(for example by right clicking on the icon) for that or should it be done via a adb shell?
Re: Android Orphans: Visualizing a Sad History of Support
#150Even though they may have an update available (non-eligable devices excluded) not every user knows how or is able to update their device.
http://blog.brightcove.com/sites/all/uploads/image/brightcov...
[1] http://blog.brightcove.com/en/2011/10/brightcove-unveils-next-generation-video-cloud-smart-player