Database Info

[Q] Android 3.0 Honeycomb Kernel

can someone explain to me if you were to find the android 3.0-3.2 firmware and or source code files that are used on a tablet (obviously itd be a honeycomb os), with the source code file could work on porting a honeycomb rom be attempted ? or is the firmware/source code im speaking of incorrect of whats needed in rom development. I found an article and have downloaded what was both labeled source code (there were versions used by manufacturer for android 3.0 -3.2) i downloaded the 3.0 version of the "source code" and i also downloaded a matching version of the firmware for android 3.0 used by manufacturer. just looking for more insight before i start posting links or anything, want to make sure I'm giving accurate information .

Jon_Mull said:
can someone explain to me if you were to find the android 3.0-3.2 firmware and or source code files that are used on a tablet (obviously itd be a honeycomb os), with the source code file could work on porting a honeycomb rom be attempted ? or is the firmware/source code im speaking of incorrect of whats needed in rom development. I found an article and have downloaded what was both labeled source code (there were versions used by manufacturer for android 3.0 -3.2) i downloaded the 3.0 version of the "source code" and i also downloaded a matching version of the firmware for android 3.0 used by manufacturer. just looking for more insight before i start posting links or anything, want to make sure I'm giving accurate information .
Click to expand...
Click to collapse
Given that Google has not officially released the source code, you'd be posting warez which is against forum rules. Once Google officially releases source, devs could try to port it to the G2x but with ICS so close to being released/announced, I bet most people would wait for that since it officially supports smaller and lower resolution screens like the ones in phones.

Your correct google has not but other manufactures of tablets using honeycomb have. Following the general public license released the source code which has been made aware of to google by said manufacture. The source code as well as firm ware is readily available without by passing anytype of payment or "pirating" . So how would this be considered warez?

I was under the impression that they only released their specific bits of code and not the entire source code. I may be wrong, this isn't something I've been watching closely.

I don't think Honeycomb has been released yet. All custom roms are stock based. We have OC/UV kernels but the roms are just slight variants of stock.
Sent from my LG-P999 using xda premium

Maybe i misread something , but if you google something along the lines of asus honeycomb source code, you'll find a link to asustek which has said source code for various versions of honeycomb , ie 3.0-3.2 don't quote me on it being 100% being what people are looking for just something i stumbled across

[GPL] [Apache] Crackdown on GPL and Apache Complience

Hello,
It has been brought to our attention that many kernels and/or ROM's (where applicable) posted in this section are not fully compliant with the GNU General Public Licence v2 (GPL v2) and for CyanogenMod ROM's the Apache licence.
This is quite frankly not acceptable so we are initiating a crackdown on this.
For kernel developers: You must provide FULL source code, not just the edits you made (reference here). Your source code must also be up-to-date with any binary releases. If in doubt, update your github first, then release the binary, NOT the other way round.
For CyanogenMod ROM developers: CyanogenMod is OpenSourced under the Apache Licence 2.0 and as such you don't need to upload your source code, though under the "spirit of OpenSource" it would be morally right to do so, however, we will not force you to do this, that is your choice to make.
For ALL ROM developers: If your ROM contains a boot.img file or a zimage file then you must state firstly whether it is your kernel or another user's kernel and secondly you must provide a link to the source code if it is your kernel and a link to the other user's kernel thread if you use another user's kernel.
The full GNU GPL v2 can be read here >>> http://www.gnu.org/licenses/gpl-2.0.html
The FAQ for the GPL v2 can be read here >>> http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html
Why you cannot provide just the edits you made? Read here >>> http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#DistributingSourceIsInconvenient
The Apache Licence 2.0 can be read here >>> http://www.apache.org/licenses/LICENSE-2.0.html
XDA-Developers and the GPL article here >>> http://www.xda-developers.com/android/xda-developers-and-the-gpl/
I have posted notices in many users ROM/kernel threads and those people have 3 days (from the time this post was posted) to provide full kernel source. If you need more time then please contact me via PM. If you are unable to provide source code after the decided time then your thread will be closed and download links removed.
Regards,
Jonny

Ok, the 3 days were up yesterday but due to time constraints I won't start chasing people up on this until much later tonight or tomorrow. If users who were notified by me 4 days ago do not have source code up by tomorrow and have not contacted me, they have no excuse and their threads will be closed so I would suggest uploading it if not already done so.

[Q] A little help

Hey guys,may I know "In order to make a build for your device, you will need a suitably device configuration. Often these are included within the main source download, or are obtained through a method documented by the developers of the ROM." <<<<<where can I get this?

Should be the source code, i guess.

old.splatterhand said:
Should be the source code, i guess.
Click to expand...
Click to collapse
Kernel source code?

I think so.

Where can I find proprietary binaries?

Kernel Source code can be found at www.htcdev.com
After it is released.

old.splatterhand said:
Kernel Source code can be found at www.htcdev.com
After it is released.
Click to expand...
Click to collapse
And the binaries are located in the source code?I'm asking all this questions because I'm in the midst of developing.And to further understand so that it would be easier for me.

I'm no kernel dev, so i can't answer more than this.

It's ok.

Thread Closed

Dear Developers
I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).
You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.
Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:
The used toolchain including its version (linking to your toolchain source is always a good idea)
The used defconfig
The link to your sourcecode (including the used branch, tags,...)
If used, also upload your scripts used for the compilation
If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...
Example:
GPL:
- Used sources (cm-10.1 branch)
- Used defconfig
- Used toolchain
- Used scripts
Click to expand...
Click to collapse
@ROM devs, using a precompiled kernel
As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.
Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.
Example:
GPL:
The kernel included in this ROM is located HERE. I have not altered anything.
Click to expand...
Click to collapse
If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2

Thread Closed

Dear Developers
I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).
You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.
Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:
The used toolchain including its version (linking to your toolchain source is always a good idea)
The used defconfig
The link to your sourcecode (including the used branch, tags,...)
If used, also upload your scripts used for the compilation
If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...
Example:
GPL:
- Used sources (cm-10.1 branch)
- Used defconfig
- Used toolchain
- Used scripts
Click to expand...
Click to collapse
@ROM devs, using a precompiled kernel
As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.
Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.
Example:
GPL:
The kernel included in this ROM is located HERE. I have not altered anything.
Click to expand...
Click to collapse
If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2