Skip to main content

ANDROID TRADEMARKS & LICENSING

Trademarks
In order to use the Android trademark, device manufacturers must ensure that the device complies with the Compatibility Definition Document (CDD) and then get permission from Google. Devices must also meet this definition to be eligible to license Google's closed-source applications, including the Android Market. Participation in the compatibility program is free of charge.
In September 2010, Skyhook Wireless filed a lawsuit against Google in which they alleged that Google had used the compatibility document to block Skyhook's mobile positioning service (XPS) from Motorola's Android mobile devices. In December 2010 a judge denied Skyhook's motion for preliminary injunction, saying that Google had not closed off the possibility of accepting a revised version of Skyhook's XPS service, and that Motorola had terminated their contract with Skyhook because Skyhook wanted to disable Google's location data collection functions on Motorola's devices, which would have violated Motorola's obligations to Google and its carriers.

Licensing

The source code for Android is available under free and open source software licenses. Google published their Linux kernel changes under the GNU General Public License version 2, and the rest of the code (including network and telephony stacks) under the Apache License version 2.0. Google also keeps the reviewed issues list publicly open for anyone to see and comment.
The Open Handset Alliance develops the GPL-licensed part of Android, that is their changes to the Linux kernel, in public, with source code publicly available at all times. The rest of Android is developed in private, with source code released publicly when a major new version is released. Typically Google collaborates with a hardware manufacturer to produce a flagship device (part of the Google Nexus series) featuring the new version of Android, then makes the source code available after that device has been released.
In early 2011, Google chose to temporarily withhold the Android source code to the tablet-only Honeycomb release, creating doubts over Google's commitment to open source with Android. The reason, according to Andy Rubin in an official Android blog post, was because Honeycomb was rushed for production of the Motorola Xoom, and they did not want third parties creating a "really bad user experience" by attempting to put onto smartphones a version of Android intended for tablets.The source code was once again made available in November 2011 with the release of Android 4.0.

Comments

Popular posts from this blog

One-Click Root for Stock Gingerbread (Droid X, Droid 3, Droid X2, Cliq and Cliq 2) [From the Forums]

Earlier today we reported XDA forum member  dirbliss had successfully rooted the Motorola DROID 3. Now, thanks to  Framework43, krazykrivda, and  psouza4 over at rootzwiki, we have an uber simple one-click root method for stock Gingerbread. I have tested this out on my Droid X running 4.5.602 and everything went flawlessly. As per P3Droid , this method should work on the Droid 3, Droid X, Droid X2, Cliq and Cliq 2. Here’s how it goes down, but proceed at your own risk: Motorola drivers need to be installed – 32bit here and 64bit here Download and unzip ‘Droid 3 easy root script v7′ to your PC  from here Turn on USB debugging on your phone by going to Settings > Applications > Development > USB debugging(check box) Plug phone into your computer and select “Charge Only” mode from your phone’s notification drop down (pull down your notification bar and tap USB connection to change). Navigate to ‘Droid 3 easy root’ folder you unzipped to...

SATA based Android – Convert any laptop with this drop in PCB board

Android runs on everything! Though, it’s admittedly tougher to run on some things, of which the most common target are PCs. Those of us wanting to experiment in that department have typically found our way to projects like Android x86, which by the way has ICS development builds underway (Yes, I’m one of the experimenters). However, here’s another solution I hadn’t known about until today. It’s so far called “PunkThis” from CUPP Computing. Essentially what we have here is a PCB board attached through either SATA or PCI express. So yeah, stick this thing in your laptop’s hard drive bay and you’ll be running Android. The board is a great improvement over Android x86 in terms of compatibility. Most of the typical phone guts are part of the board, including a 1GHz TI OMAP processor, 512MB of RAM, MicroSD card, and even a WiFi chip. This should pretty much guarantee that any app should run unless its simply too taxing for the allotted processor speed and RAM. As for the rest of wha...

Does RIM Have What It Takes To Catch Up To Android, iOS and Windows Phone?

As many know by now, the mighty duo of CEO’s at RIM, Jim Balsillie and Mike Lazaridis have stepped down only to promote one from within.  Taking over as single and only CEO of Research in Motion is Thorsten Heins, a four year COO who worked closely under Jim and Mike.  In recent news, he’s been given the cold stare thanks to making such statements as  “I don’t think there is some drastic change needed,” and   “We are evolving. We’re evolving our strategy, we’re evolving our tactics, our processes.”   As one standing from the outside looking in, I’d argue in favor of a drastic change, personally.  But hey, RIM’s the competition so I’m not pressing the issue.  However, the question does arise, should Google’s Android be afraid?  As much as I would love to shout from the roof top “ hell no! “, I”ll try to keep it professional here.   With RIM falling drastically behind every quarter, Android, iOS and Windows Phone pretty much occupy the...