Ok, lately we have seen a lot of roms being posted that do not have kernel source links.
Be advised that XDA requires that you post kernel source when using non-stock kernels.
Stock Kernels
If your kernel is stock and not modified in any way, then you may post the link to the manufactures source (if available). If not, then state the kernel is stock.
If you have re-compiled the stock kernel, then you must have a link to your Git Hub with changes listed.
All others, including CM, AOKP, PA, etc
Link to your Git Hub, or which ever Git Hub or source you used. Along with changes. DO NOT just post a link to CM's site. Be specific which source you used.
All links to source must be links to a compilable kernel that works and matches what you have included in your rom. If you have "Cherry Picked" from other sources, please ensure you have their permission to do so, and, give credits when necessary.
Generally XDA will allow you 5 days maximum to post your kernel source. Please do not abuse this.
Failure to post kernel source will result in the ROM thread either "disapproved" or "Thread Closure" with all download links removed.
Most of you know the rules and GPL, so please abide by them.
Thank You for reading.
MD
Related
Hi there,
this message is target to you that are about to develop a new rom or kernel (veteran must already know that)
These are some special rules that you have to impress in your head before clicking on "Open New Thread" with [ROM][Kernel] in title:
If you are about to post a new Kernel you need to be in compliance to GPL since kernel does contain Linux code, this mean that if you have modified a kernel you MUST provide source code:
(choose what best for you)
- A github link
- packing your kernel and uploading
- a diff .patch files
- Credits to people in case of an already custom kernel
If you are about to post a new Rom, you don't need any source since theu are covered by Apache BUT you must be in compliance with XDA rule and with good sense:
New Roms thread must have:
- Exactly say which base rom do you used : Stock, custom from another developer, CyanogeMod.
- Ask permission to use that rom as your base to the original Developer(s).
- Give credits to Original Developer(s) in your first post:
(eg: Credits and thanks for this Rom goes to XXXXX
- Give credits, if possible, to people that you grabbed: scripts, themes and apps.
- You rom MUST BE free of paid apps, warez is not tollerated here.
- Your first post must have as more info that you can, " this is my rom" and a link is not tollerated.
- Thread Title : " [ROM][date of release]xxxxxxxxxxx[kernel used]
As a user of this thread you must read this (it isn't invisible), so i'll take this as accepted by everyone.
I'm bored of reports on people that don't follow the respect in work of other user and basically, with this thread you don't have other excuses.
Every ROm/Kernel thread found without those (simple) rules will be closed and links deleted without furter notice.
Bonus rules:
- adfly links are not allowed.
- If a Rom and/or Kernel are found by us illegal for XDA, every user is not allowed to have the link of that in your signature.
Feel free to pm me for any clarification.
Thanks for your cooperation.
Today when I was building cm9 rom I got message:
Using prebuilt kernel binary instead of source
THIS IS DEPRECATED, AND WILL BE DISCONTINUED
Please configure your device to download the kernel
sorce repository to kernel/samsung/galaxys2
See http://wiki.cyanogenmod.com/wiki/Integrated_kernel_building
for more information
The instruction on the webiste is not that clear...
Anyone could give advice how to to that?
I answered this in the CM9 thread, but in case anybody looks here and misses that, they are implementing a new feature to build kernels as part of the CM9 build process, at present the SGS2 git changes that would be required for this are in the CM9 gerrit review and have yet to be approved, this will not affect your build in the slightest and once the files are approved this message will disappear. If you want to cherry pick it before it gets approved, you can but doing so may have unintended consequences (thus the need for review).
Ok, lately we have seen a lot of roms being posted that do not have kernel source links.
Be advised that XDA requires that you post kernel source when using non-stock kernels.
Stock Kernels
If your kernel is stock and not modified in any way, then you may post the link to the manufactures source (if available). If not, then state the kernel is stock.
If you have re-compiled the stock kernel, then you must have a link to your Git Hub with changes listed.
All others, including CM, AOKP, PA, etc
Link to your Git Hub, or which ever Git Hub or source you used. Along with changes. DO NOT just post a link to CM's site. Be specific which source you used.
All links to source must be links to a compilable kernel that works and matches what you have included in your rom. If you have "Cherry Picked" from other sources, please ensure you have their permission to do so, and, give credits when necessary.
Generally XDA will allow you 5 days maximum to post your kernel source. Please do not abuse this.
Failure to post kernel source will result in the ROM thread either "disapproved" or "Thread Closure" with all download links removed.
Most of you know the rules and GPL, so please abide by them.
Thank You for reading.
MD
Ok, lately we have seen a lot of roms being posted that do not have kernel source links.
Be advised that XDA requires that you post kernel source when using non-stock kernels.
Stock Kernels
If your kernel is stock and not modified in any way, then you may post the link to the manufactures source (if available). If not, then state the kernel is stock.
If you have re-compiled the stock kernel, then you must have a link to your Git Hub with changes listed.
All others, including CM, AOKP, PA, etc
Link to your Git Hub, or which ever Git Hub or source you used. Along with changes. DO NOT just post a link to CM's site. Be specific which source you used.
All links to source must be links to a compilable kernel that works and matches what you have included in your rom. If you have "Cherry Picked" from other sources, please ensure you have their permission to do so, and, give credits when necessary.
Generally XDA will allow you 5 days maximum to post your kernel source. Please do not abuse this.
Failure to post kernel source will result in the ROM thread either "disapproved" or "Thread Closure" with all download links removed.
Most of you know the rules and GPL, so please abide by them.
Thank You for reading.
MD
We need build instructions in order for people to more easily make custom roms. Currently most roms here only provide a repo or two, hardly describing the build process if anything. Not sure if those repos contain all the sources/blobs you need either.
It's not that hard to build and you can always go on th cheap and hire a cloud vps for a few hours, so don't bother with local building unless you have the powerful hardware.
Anyhow, so far what I know is that some people just replace the kernel and firmware, it seems this is called repacking.
Others are building Lineage from source as per their instructions, which are not descriptive when you're porting to a new device.
We need concrete and concise information about how it's done.
Lineage wiki is pretty accurate and if someone ask here I can try to solve his doubt.
I am not the best developer but I know the basics xD
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
randxor said:
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
Click to expand...
Click to collapse
Thats thanks to codeworkx code. Basically you compile a rom for zl1 and works for zl0.
My workflow is
repo init/sync the rom
Fix libhidl and libbfquio if needed (Dont know why they fix an error creating a bigger one tho)
Take the device tree, vendor and kernel
Adapt the device tree for the rom (Like in cosmic where config is in root not in config folder, boardconfig...)
And just brunch or make or lunch depends on rom xD
Edit: Forgot u need like 200 frameworks/av commits to make zoom work https://github.com/mosimchah/frameworks_av/commits/o8.1 all the january 15th and this one http://gerrit.aicp-rom.com/#/c/54436/
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
randxor said:
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
Click to expand...
Click to collapse
Yout init the rom source you want to compile
You dont need to adapt anything codeworkx already did it for us we just compile zl1 roms with his device tree (Los one) or any of the forked ones (Like Aicp which I recommend).
Libhidl and libbfquio depends on the rom you are building. Libhidl is solved by reverting this changes https://github.com/PixelExperience/system_libhidl/commit/607e961b85eea8969503d8ff8437c014f04f0ca2 and libbfquio by taking this http://gerrit.aicp-rom.com/#/c/56488/
You dont adapt device tree to device you adapt it to the rom you are compiling see how other devs do it in their github (Every rom is different for example in cosmic you rename lineage/aicp.mk to cos.mk and change where to import things)
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
Start by picking up a rom you want to compile that has 8.1 source working and better if a msm8996 device is there (zuk z2, oneplus 3...)
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
randxor said:
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
Click to expand...
Click to collapse
Np
Not sure dont know much about android kernels