On the heels of Microsoft bashing Google's hands-off Android update policy at Ignite 2015, Lucian Armasu at Tom's Hardware has an editorial reaffirming Android's update woes:
Android 5.0 and Android 5.1 (Lollipop) [...] currently represent 9.0 percent and 0.7 percent of the Android market, respectively, for a combined total of 9.7 percent. That's definitely nothing to be proud about, because it could be years by the time the vast majority of users are on the Android 5+ platforms. By then, 10 percent of users could be on Android 8.0.
Because Android is open source and because so many (essentially) OEM-tweaked "forks" of it exist, a "clean" upgrade path is almost impossible. To have a clean standardized update system would mean all the OEMs would have to agree to abide strictly by Google's guidelines for what they can and cannot modify on the platform. However, as soon as Google tries to do something like that, the OEMs usually cry foul that Google is making Android more proprietary and restricting what they can do with it. Google may also not want to upset the OEMs too much by forcing a unified update system on them either, because of the fear that those OEMs could take their business elsewhere, as it were.
When we look at the matter practically, though, we see that some have already tried that (Samsung with Tizen), and it hasn't worked very well. The reality is that Android and iOS are so entrenched in the market right now that it's hard to believe a significant third platform could arise on mobile when it comes to apps. Even Microsoft, after spending billions upon billions trying to make Windows Phone popular, has essentially admitted failure on the app store front, and is now trying to make Android and iOS apps work with Windows instead.
Google also can't and shouldn't leave the responsibility to OEMs and carriers anymore, because so far they've proven themselves to be quite irresponsible from this point of view. At best, we see flagship smartphones being updated for a year and a half, and even that is less than the time most people keep their phones. Even worse, the highest volume phones (lower-end handsets) usually never get an update. If they do it's only one update, and it comes about a year after Google released that update to other phones, giving malicious attackers plenty of time to take advantage of those users.
This update "system," if you can call it that, ends up leaving the vast majority of Android users with security holes in their phones and without the ability to experience new features until they buy new phones (which is sadly a kind of planned obsolescence as well). This can't be an acceptable state of affairs for Google, and it shouldn't be. Google already has a great six-week update system for Chromebooks, and it's time to have Android catch up to that, as well.
(Score: 2) by jasassin on Wednesday May 06 2015, @08:41PM
I'm using an original kindle fire with a newest nightly build of CyanogenMod now (4.4.4). In a case like this, because of the terribly slow (but supposed to be faster) "silk browser" this unit is much faster. I've noticed CyanogenMod has only released nightly builds since milestone12 dated 2014-11-12. Milestone12 would not work with the full blown gapps package. I had to use their small googleapps package to get play store working. The only bug I've found (this has happened on the milestone releases so this is an old bug) is sometimes the kindle won't wake on power button from sleep, requiring a hard reset. It occurs enough to be a nuisance, but still a better experience than factory.
I'd sure put 5.1 on here to try it (if they ever make it), but I'm not sure it would fit... even with the smaller gapps package.
jasassin@gmail.com GPG Key ID: 0xE6462C68A9A3DB5A