Linked by Thom Holwerda on Thu 21st Aug 2014 15:13 UTC
PDAs, Cellphones, Wireless

For every Android update, Google's release of code to OEMs starts an industry-wide race to get the new enhancements out to customers. So how did everyone do this year? Who was the first with KitKat, and who was the last? What effect does your carrier have on updates? How has the speed of Android updates changed compared to earlier years?

Nice overview that may help during your next purchasing decision, and which neatly illustrates Android's biggest weakness. Interestingly enough, it doesn't include non-stock ROMs.

Permalink for comment 594621
To read all comments associated with this story, please click here.
They need to fix this
by WereCatf on Thu 21st Aug 2014 16:10 UTC
Member since:

For one, drivers for the various components should be officially maintained on Google's servers and ROM-makers should explicitly be given the permission to use them in their creations.

Secondly, manufacturers should provide a simple, easy-to-use tool for people to switch over to the latest Google-maintained Android-version for which up-to-date drivers exist. This could be coupled with a system where, if your hardware matches certain ID, you're given access to various apps and tools in Play Market that were provided by the manufacturer, but which aren't available to anyone else -- this way manufacturers could still offer "value add" on their products even for stock-Android-users.

These two changes wouldn't fix the situation, but they'd at least improve things. A proper fix would likely require a complete revamp of how Android is used and distributed and would simply be too disruptive an act to anyone willing to commit to such. Of course, neither of these will be done either, manufacturers don't want their old devices to hang about longer than the minimum necessary.

Reply Score: 4