Comments on: Android ‘open source’ heritage will soon be but a memory… https://blog.p2pfoundation.net/androids-open-source-heritage-a-memory/2013/11/04 Researching, documenting and promoting peer to peer practices Fri, 03 Jan 2014 13:36:21 +0000 hourly 1 https://wordpress.org/?v=5.5.15 By: technology|dict|android|latest technology https://blog.p2pfoundation.net/androids-open-source-heritage-a-memory/2013/11/04/comment-page-1#comment-567294 Thu, 28 Nov 2013 07:30:02 +0000 http://blog.p2pfoundation.net/?p=33833#comment-567294 technology|dict|android|latest technology

[…]P2P Foundation's blog » Blog Archive » Android ‘open source’ heritage will soon be but a memory…[…]

]]>
By: Sepp Hasslberger https://blog.p2pfoundation.net/androids-open-source-heritage-a-memory/2013/11/04/comment-page-1#comment-561217 Thu, 07 Nov 2013 13:53:49 +0000 http://blog.p2pfoundation.net/?p=33833#comment-561217 Another one of Google’s tricks is

Locking-in manufacturers

While Google is out to devalue the open source codebase as much as possible, controlling the app side of the equation isn’t the company’s only power play.

If a company does ever manage to fork AOSP, clone the Google apps, and create a viable competitor to Google’s Android, it’s going to have a hard time getting anyone to build a device for it. In an open market, it would be as easy as calling up an Android OEM and convincing them to switch, but Google is out to make life a little more difficult than that. Google’s real power in mobile comes from control of the Google apps—mainly Gmail, Maps, Google Now, Hangouts, YouTube, and the Play Store. These are Android’s killer apps, and the big (and small) manufacturers want these apps on their phones. Since these apps are not open source, they need to be licensed from Google. It is at this point that you start picturing a scene out of The Godfather, because these apps aren’t going to come without some requirements attached.

While it might not be an official requirement, being granted a Google apps license will go a whole lot easier if you join the Open Handset Alliance. The OHA is a group of companies committed to Android—Google’s Android—and members are contractually prohibited from building non-Google approved devices. That’s right, joining the OHA requires a company to sign its life away and promise to not build a device that runs a competing Android fork.

]]>
By: Sepp Hasslberger https://blog.p2pfoundation.net/androids-open-source-heritage-a-memory/2013/11/04/comment-page-1#comment-561215 Thu, 07 Nov 2013 13:45:48 +0000 http://blog.p2pfoundation.net/?p=33833#comment-561215 Yes Paul, ideally that is what should happen.

Google keeps their closed version and everyone else moves on.

But as the article also explains, there is a strategy to what Google does, which involves making it as difficult as possible to go back to the old version as they can. The old version is gradually being emptied of content by switching parts of it to proprietary (by using a proprietary plug-in instead of the equivalent contained in the original.

As time passes, the open source version gets smaller and smaller and more and more outdated, to where it will be exceedingly expensive to revert as you’d have to update all that parts that have been abandoned for years…

]]>
By: Paul Hughes https://blog.p2pfoundation.net/androids-open-source-heritage-a-memory/2013/11/04/comment-page-1#comment-560799 Tue, 05 Nov 2013 19:50:08 +0000 http://blog.p2pfoundation.net/?p=33833#comment-560799 Sepp, won’t Google closing it up, simply represent a closed fork to the Android OS? What’s to keep the rest of the Android community from continuing to evolve it in their own open fork? I’m guessing there are a lot of cell phone manufacturer’s who do not want to pay licensing fees or risk getting closed off by Google using one means or another. It seems to me that the most logical move is for all the developers and manufacturers is to move on using the open source version, with all of it’s amazing features (after all it is that way precisely because of the open-source community), and let Google close itself off into a proprietary rabbit hole.

]]>