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).
Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices.
Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", "
android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build".
How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help!
Ain't nobody is going to help you ^^ I am looking for that kind of knowledge too. I would like to start building roms from source and make some modifications to CM10's kernel
check out Legion modz team thread
it has a little info on it
http://forum.xda-developers.com/showthread.php?t=2314836
and make google your best friend
so much way to take...
theabnormalguy said:
Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices.
Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", "
android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build".
My github account is MaxusPrimus
How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help!
Click to expand...
Click to collapse
Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to.
---------- Post added at 08:51 PM ---------- Previous post was at 08:09 PM ----------
flipinfin said:
Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to.
Click to expand...
Click to collapse
Heres some starting links that im using starting to build from source. the samsung open source page look for your model number http://opensource.samsung.com. Obviously. you can build your own kernel.
how to unpack repack img http://forum.xda-developers.com/showthread.php?t=1081239
http://www.kandroid.org/online-pdk/guide/index.html very useful link aswell as this one http://source.android.com/source/initializing.html.
heres a link to identify partition tables http://forum.xda-developers.com/showthread.php?t=1959445. . Heres another link that you prolly can pull files from if needed http://www.teamandroid.com/2013/04/...kp-build-6-android-422-jelly-bean-custom-rom/
Dont take this the wrong way but i think your getting confused how roms kernels etc r built its all open source. That rom is based off of jelly bean and alls they did was change the name. Though its open source so i would assume you can repo the rom at https://github.com/. In addition if i was you i would download the rom "which you prolly already have and do some investigating.. heres another useful link http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code. Never forget google is your best friend. Fogot to mention if you aint on linux i would switch os real soon. I think this link will be ver ver very helpful https://bitbucket.org/bigwillyg/buttered_toast_shooter
Is that Vibrant T-Mobile ? cuz if it is http://aokp.co/devices/vibrantmtd theres your starting point
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