4 ms·
I remember many years ago when a few carrier and chipset execs stood up on Google I/O stage and announced a new program to ensure Android devices get updated qu
by madeofpalk 9y ago
I remember many years ago when a few carrier and chipset execs stood up on Google I/O stage and announced a new program to ensure Android devices get updated quicker. Nothing came out of that.
The proof here will be when they ship.
Thankfully, 'Google Play Services' and distributing more and more services through the Play Store is a step in the right direction.
- sangnoir 9y ago> I remember many years ago when a few carrier and chipset execs stood up on Google I/O stage and announced a new program to ensure Android devices get updated quicker. Nothing came out of that Google remembers that too, and this change allows Google to bypass those same execs when pushing out updates. The HAL layer will not change from version to version, meaning no driver support will be required from the OEM for new Android versions.
- keganunderwood 9y agoThey were supposed to not put any user app on the system partition but rather install them using play services when the user logs in. I've only seen one device implement it and it was a low end device so it kind of choked anyway.
- fpgeek 9y agoI've seen plenty of devices implement this. Of course, they were all ones I'd flashed with CyanogenMod...
- kuschku 9y ago> Thankfully, 'Google Play Services' and distributing more and more services through the Play Store is a step in the right direction. A move towards replacing an open OS with an entirely proprietary solution full of tracking by a single vendor is "a step in the right direction"? There's thousands of solutions for how you can update core OS components, none of them require what Google's doing to open source.
- madeofpalk 9y agoLook, the reality of the market is that most people are a lot more concerned about getting timely (security) updates than an 'open source' mobile OS.
- thecrazyone 9y agoGood point. However, that's a short term benefit at the cost of long term is what we should all remember
- fauigerzigerk 9y ago>There's thousands of solutions Yes, but only if you declare the business models of everyone involved a non-goal.
- kuschku 9y agoYou can still have a Google-branded version of the same product that provides additional, Google-only features. An open core business model was always what Android was like, but now the opem core is shrinking with every further commit.
- fauigerzigerk 9y agoAll true, but what does that tell us about any solutions to slow or non-existant updates and fragmentation? What are some of the thousands of solutions? Or are you saying that there never was a problem in the first place?
- kuschku 9y agoThe issue: apps that are only updated with the OS end up outdated. The current solution: Move them out of AOSP, into Google's internal projects, distribute updates via the Play Store. An alternative solution: Move them out of AOSP, onto GitHub, distribute updates via the Play Store. Yes, Google had to decouple them from AOSP. But that’s no reason not to put the code anywhere else in the open. These issues are entirely orthogonal, and Google uses it as a way to force more people onto the proprietary ones.
- calferreira 9y agoAs an Android developer this is a big pain in the arse if you intend to develop apps using google apis. The development is easier, but if you plan to distribute on other stores, google play services are useless and will make your development more time consuming as they are exclusive to devices with google play store.