Android's GPL violations

[TomCooksey]

Now we know a bit more, I'd like to start this thread to list possible/
probable GPL violations within Android.

1) The Linux kernel: There's no config for the qemu kernel, only the
halibut dev kit kernel. I'm pretty sure the config is a requirement of
the GPL.

2) OpenBinder, which seems to form the basis of Android is released
under the Mozilla Public Licence. I think this means Google must
provide access (or instructions to access) the original source and
describe what modifications they have made to that source. Anything
using that source needs to be released under the MPL.


I'm not too familiar with the MPL, but the .config bit I'm certain
about. BT got into a bit of bother about not releasing the .config
file for the HomeHub.

[dasGrunge]

Standard IANAL applies.

The config I believe is available in the emulator in /proc/config.gz.
You can get it from there.

Having said that, I'm sure there are other open source licensing
infringements, e.g. whichever libc library they're using. The promise
to release the source at a future date not too far away might suffice
for them to get by unless someone really pushes the issue, i.e. sues.

[TomCooksey]

Well, I've been reliably informed that many of the people who
developed OpenBinder while working at PalmSource (Diane
Hackborn, Trey Boudreau, Jason Parks) now work for Google on the
Android project. So I guess if they wrote the code, they own it and
can licence it anyway they choose. Although perhaps Access might have
something to say.

I also hadn't realised the config was avaliable in /proc.

Looks like Google are GPL clear so far! Fantastic, well done Google!

[gaz]

Have you looked inside /proc/config.gz? ;)

[omattos]

looking at the length of the legal notices file I'm guessing googles
lawyers have looked at the sdk pretty hard.

> Looks like Google are GPL clear so far! Fantastic, well done Google!- Hide quoted text -
>
> - Show quoted text -

[Brian Swetland]

I assume you're referring to this language in the GPL (kernel/
COPYING):
> For an executable work, complete source
> code means all the source code for all modules it contains, plus any
> associated interface definition files, plus the scripts used to
> control compilation and installation of the executable.

As I pointed out in a previous thread, there is a provided
goldfish_defconfig (in kernel/arch/arm/configs) which can be used to
synthesize the exact .config used to compile this kernel. We build
the release kernel as follows:

1. check out fresh kernel source
2. make goldfish_defconfig
3. make

You will find the Binder Driver kernel driver sources in kernel/
drivers/binder in the kernel source distribution. The Android
userspace Binder code is not derived from the OpenBinder version.

Brian

On Nov 19, 2:44 pm, TomCooksey <TomCook...@googlemail.com> wrote:

[Rod Whitby]

Brian Swetland wrote:
> You will find the Binder Driver kernel driver sources in kernel/
> drivers/binder in the kernel source distribution. The Android
> userspace Binder code is not derived from the OpenBinder version.

Thanks for the clarification, Brian.

Can you say whether the Android userspace Binder source code will be
open sourced along with the source code for the SDK, or will it remain
closed source.

[Since it is not derived from the OpenBinder version, then it is
Google's perogative whether to open source that userspace code or not
(since userspace executables fall under the "mere aggregation" clause of
the GPL and are not considered derivative works). Hence the question.]

-- Rod

[Brian Swetland]

Regarding userspace source code issues, I will refer you to this post
by Dan Morrill. I think this is the clearest statement about it:
http://groups.google.com/group/android-developers/msg/ce848a736913e04b

> When the source code is released, it will include the entire system. Most
> of it will be licensed under Apache 2.0, and the rest will be licensed under
> a few other open source licenses such as GPL. (For instance, the Linux
> kernel itself is GPL, so the kernel related changes are already available
> under the terms of the GPL.)
>
> Source will be available for the system C library, the Dalvik VM, the core
> API libraries, etc.

[Rod Whitby]

Brian Swetland wrote:
> On Nov 22, 2:38 am, Rod Whitby <rod.whi...@gmail.com> wrote:
>> Can you say whether the Android userspace Binder source code will be
>> open sourced along with the source code for the SDK, or will it remain
>> closed source.
>

> Regarding userspace source code issues, I will refer you to this post
> by Dan Morrill. I think this is the clearest statement about it:
> http://groups.google.com/group/android-developers/msg/ce848a736913e04b
>
>> When the source code is released, it will include the entire system. Most
>> of it will be licensed under Apache 2.0, and the rest will be licensed under
>> a few other open source licenses such as GPL. (For instance, the Linux
>> kernel itself is GPL, so the kernel related changes are already available
>> under the terms of the GPL.)
>>
>> Source will be available for the system C library, the Dalvik VM, the core
>> API libraries, etc.

So that's a "Yes, the Binder userspace code will be open sourced."

Excellent.

Now all we need to know is when ;-)

-- Rod

[Dan Morrill]

Specifically regarding the libc implementation:  Android uses a libc derived from a heavily-modified BSD libc.  The original source is thus BSD-licensed, and will be compatible with the Apache 2.0 license when it is open-sourced.  Notably, it's not GPL or LGPL.

- Dan