decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
I Call FUD! And a request of someone who knows better! | 142 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Needs to be licensed from Google?
Authored by: Wol on Wednesday, September 12 2012 @ 05:57 AM EDT
And - in order to provide a decent experience - OEMs have *always* had to
customise the base OS. It was true in the Win3.1 days and when MS stopped it
with 95 it was very damaging to the industry.

Google can't be expected to provide a system that will work well on all
hardware. MS try, and fail pretty badly. Google lets OEMs tweak Android to fit,
so if it doesn't work it's the OEM's fault. MS won't let OEMs tweak it, so all
OEMs are much of a muchness.

So you're basically moaning about what actually boils down to *good* engineering
practice (which is, of course, why MS won't let you do it :-)

Cheers,
Wol

[ Reply to This | Parent | # ]

Needs to be licensed from Google - license to API's?
Authored by: Anonymous on Wednesday, September 12 2012 @ 06:16 AM EDT
There is no license needed to use or reimplement API's. See Oracle v.s. Google
for that.
You may need a license to use Google services though, when using these API's. If
Amazon were to implement the same API's and you access those, you might need a
license with Amazon.

[ Reply to This | Parent | # ]

I Call FUD! And a request of someone who knows better!
Authored by: Anonymous on Thursday, September 13 2012 @ 10:07 AM EDT

The request to someone who knows better: Please provide a link to a source outlining the functionality of a phone that has nothing but the stock Android base that Google provides! I can't find a good example at the moment. I'd specifically like an example of a Stock Android phone that is not locked down, nor has extra apps locked in by the manufacturer as an example to blow away the FUD inherent in the post I'm responding to.

The the parent poster:

You state a lot of obvious things, but I think your intent is clear in your final statement. A conclusion that can not be logically formed from your previous statements.

IANAL, but to cover your points from my knowledge base:

    A: Yes, the source code for the kernel is GPL protected, as a result "Google has been faithful in always making their linux kernel changes publicly available" - in other words, Google actually complies with the license terms of software they make use of... unlike Microsoft who has to be forced to.
    B: Google choose to protect the Android code using the Apache license. That's a permissive license along the lines of the BSD license. The Copyright owner has the right to license their work under any license they want including multiple licenses if they so choose. What they can't do is revoke the license from someone who has not breached the license.
    C: Yes, in order to make use of Android, the manufacturers are required to meet the terms of the Apache license. Those obligations don't meet the sharing obligations required of the GPL.
And now for the Fear Uncertainty and Doubt you have been trying to build:
the manufacturers will almost always be forced to add on to it
I call FUD. Please provide proof via links to other licensing or agreements where the manufacturers - like Samsung - are forced to add on to Android - like the Samsung Apps.

Your conclusion that the Apache license "forces" someone to "add on to the product or locking it down1" is totally without a basis in logic let alone fact. A person can make use of Apache/BSD protected code and release that code (The Free Software Foundation with authoring GNU code) or said person can choose to use such protected code and lock it down entirely (Microsoft).

Microsoft wasn't "forced" to use the GNU network stack and lock it down anymore then phone manufacturer's are "forced" to lock down Android.

As a result, your conclusion is: FUD!

1: You didn't come straight out and say Google is forcing manufacturers to lock down Android phones, but that's inherent in all else you say combined with your conclusion. As evidence of the Manufacturers - Not Google's - desire to lock down phones I present Motorola (now Owned by Google) starting to provide a means of Motorola Phone Owners a method to unlock their phones.

RAS

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )