Linked by Thom Holwerda on Thu 13th Feb 2014 23:38 UTC

Another day, another fear-mongering 'Android is closed!'-article at Ars Technica. After Peter Bright's article last week (sharply torn to shreds by Dianne Hackborn), we now have an article with the scary title "New Android OEM licensing terms leak; 'open' comes with a lot of restrictions".

The title itself is already highly misleading, since one, the licensing terms aren't new (they're from early 2011 - that's three years old), and two, they're not licensing terms for Android, but for the suite of Google applications that run atop Android.

This article makes the classic mistake about the nature of Android. It conflates the Android Open Source Project with the suite of optional proprietary Google applications, the GMS. These old, most likely outdated licensing terms cover the Google applications, and not the open source Android platform, which anyone can download, alter, build and ship. Everyone can build a smartphone business based on the Android Open Source Project, which is a complete smartphone operating system.

Thread beginning with comment 582923
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: This is a significant leak
by l3v1 on Fri 14th Feb 2014 06:34 UTC in reply to "This is a significant leak"
Member since:

Thirdly, it is important to reiterate that AOSP is not a very community driven project. If Google don't want your patches, AOSP won't ever have those patches. If Amazon wanted to contribute patches back to AOSP, I don't expect that they would be successful.

How is that relevant (community-driven or not)? The point is that you can take the AOSP, drop in whatever you want and put it on your devices without the need to 'sell your soul' to Google.

Reply Parent Score: 4

moondevil Member since:

Except many of the new APIs are only available via the Google services, so you also loose on the available applications.

Reply Parent Score: 3

kwan_e Member since:

Yes, but the point is how many of these "many APIs" are for proprietary Google services?

Reply Parent Score: 3