What is a kang?
A kang is a rom who uses its source from another project and build upon it. Most the time to personalize it (only add to the original code) and other times to eventually improve (go back and change code) on the original work like CyanogenMod does.
Example.
Google made Android Open Source Project.
CyanogenMod is a Kang of Original Android.
MIUI is a Kang of CyanogenMod.
Thanks.
So how do I kang? (Without knowledge of android development)
setup build env
get a coffee
pull source by syncing with sbloods tree
make ur changes to the source
get a coffee, build. enjoy coffee
read sbloods rom/source thread.
Sent from my HTC Glacier using xda premium
smirkis said:
setup build env
get a coffee
pull source by syncing with sbloods tree
make ur changes to the source
get a coffee, build. enjoy coffee
read sbloods rom/source thread.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
But doing all of that requires knowledge of Android Development... (except the coffee part)
you need at least basic knowledge.
well another option is downloading the Rom and just removing and adding files. read so you don't delete something important though
--sent from my glacier.
Or just use Cyanogen Compiler...
Easy way to make a CM Kang
Related
I find that many developers are working on porting android 2.1 or 1.6 vanila and it result in much duplicated work.
I was thinking of maybe setting up 2 git repositories one for 1.6 AOSP and 2.1 AOSP on which everyone can work on, improve and fix bugs.
lgstoian said:
I find that many developers are working on porting android 2.1 or 1.6 vanila and it result in much duplicated work.
I was thinking of maybe setting up 2 git repositories one for 1.6 AOSP and 2.1 AOSP on which everyone can work on, improve and fix bugs.
Click to expand...
Click to collapse
That's a nice idea, im begging to look after a site to host the repositories...
We can use github for hosting or any other site. I'm interested in looking after the repositories too.
A centralized effort will always be better then a fragmented one.
lgstoian said:
We can use github for hosting or any other site. I'm interested in looking after the repositories too.
A centralized effort will always be better then a fragmented one.
Click to expand...
Click to collapse
If you have alot of money, then Github would be ok... But it costs $50/month for the package that is minimum for two sets of android source code...
Know any places where we can host the code?
Mod. edit: not dev related, moved to general
Gitorious and Github are both free and unlimited for open source projects.
We can use sourcefordge too. The offer svn and git repositories. So what about it folks, who would be interested?
I would be interested in this...
I think we should open a project on sourcefordge for android 2.2 with the first task being to get the new kernel (2.6.32) working on the tattoo.
It could host the long awaited universal froyo upgrade
-------------------------------------
Sent via the XDA Tapatalk App
lgstoian said:
I think we should open a project on sourcefordge for android 2.2 with the first task being to get the new kernel (2.6.32) working on the tattoo.
Click to expand...
Click to collapse
That will be hard becuase the new kernel (2.6.32) is very big so we would need something like GRUB to boot it, from another partition than the boot partition...
If we disable enough modules the size should go down but that would mean it won't be universal any more.
There could be a regular version and a 'lite' version for Tattoo and older phones.
Wait wait wait.
I can play full divx movies smoothly so some seldom used modules could be stored on sd with no prob.
-------------------------------------
Sent via the XDA Tapatalk App
I want to try compiling my own kernel for 2.2. Where can I find the source code?
For the incredible its not out yet i dont think. I could be wrong though.
Sent from my Incredible using XDA App
Warning!
Please start threads asking questions in General sub-forum. Thanks
veli69 said:
I want to try compiling my own kernel for 2.2. Where can I find the source code?
Click to expand...
Click to collapse
when its available it will be here http://developer.htc.com/
otherwise go here for android source http://android.git.kernel.org/
ghostrida said:
when its available it will be here http://developer.htc.com/
otherwise go here for android source http://android.git.kernel.org/
Click to expand...
Click to collapse
I will try git
It's not there. And they won't release it.
Since when was HTC obligated to release kernel source if they didn't release the binary?
Well regardless I want to try making kernels how do you know the version of the kernel you downloaded ?
You don't understand. The aosp kernel source does not contain board support for the Dinc.
Sent from my ADR6300 using XDA App
Hi,
i know that the build would be slow as hell but has anyone compiled ICS for the G1? just for trying it ?
i would like to try it myself but i have no clue on how and from hat i`ve heard my computer would take ages to build it
It's done for droid eris, it can be ported to G1.
http://forum.xda-developers.com/showthread.php?t=1352170
Porting would be inefficient when it can be built from source.
Unfortunately I can't do neither
Sent from my GT-I9100 using XDA App
Ice Cream Sandwich Build Help
As soon as the source was released I was thinking about trying to build it for "old reliable" (my nickname for my old G1). I know it would be slow as mud but I still want to give it a try. Problem is I've never compiled the source of Android before so I would be going in blind. I've read the info at source.android.com so I have somewhere to start. If anyone has any other guides/tutorials on how to build Android for a device then I would be really appreciative. I'm a Computer Science major so don't be afraid to throw a little code at me either. I'll include the details of my phone below in case anyone needs it.
HTC Dream
SPL: HBOOT-1.33.2005 (DangerSPL)
Radio: 2.22.19.261
OS: CyanogenMod 6.1 (Android 2.2.1)
You can have a look at Terry' ezGingerbread thread. Here he explains what to do to compile his ezGingerbread from the sources. Principally compiling ICS is the same, but you need to exchange / modify the manifest to your needs.
Sent from my Gingerbread on Dream using XDA App
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
hyperspace290 said:
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
It's almost stock, but there are some projects from CM included and some he cloned from CM or from other sites and manages them by himself. Details you can see it in his manifest.xml located in the .repo directory. The manifest defines, what projects are to be included and what branch you want to use for these projects.
You will not want my manifest for ICS (at least unless I make an ICS branch myself)
The reason is you will want to use the ICS git repos and not the GB git repos (original or cloned by me)
That said if you are new to building an android rom look at the structure using ezgb some, and build ezgb, then when you understand the structure clone ICS from aosp (see info on source.android.com) and create your own manifest from that including cloned git repos you need from ezgb with any addtl modifications required.
The first thing is:
* Git is the source control for all parts of android, however many (well over 200) git repos are used in ICS
* Repo is a tool (python script with plugins pulled from its own git repo) for maintaining all of the git repos used in an android build, and creating the true tree of repos needed for the work directoy.
* Manifest is a special git repository with default.xml (and sometimes other manifest xmls) used by the repo script to find all the projects other git repositories, as well as what branch/commit to checkout to the work directory.
Thanks for the advice guys. Glad to see the little G1 is still getting some love. I think I'll start by building ezGingerbread to get the handle on the build process for Android and at least get up to 2.3.
If anyone knows what kinds of modifications are normally needed for a port like this then I would appreciate the help. Is it normally just editing some config files or would I have to dive into the code? Thanks again.
Sent from my DROID3 using XDA App
Looks like someone has beaten me to the punch. Anyone interested shout go have a look at this thread: http://forum.xda-developers.com/showthread.php?p=19648827
not exactly.
that is a port from a source-build for the hero
but very close
looks like the dev is trying to make a source build for the dream.
you could contact him so you can work together
Really get the cm9 source, pull forward the dream/sapphire device trees from cm7 (or firerats port of that) and it ought to be alright.
There seems little in the way of true cm bits at current (sure to change soon) but most of the hardware backwards compatibility patches are alredy in cm9 from the looks of it.. for all I know this is a cm9 build since aosp has no hero device tree out of box.
I was going to reply to that thread but since I'm still considered new I can't post to development threads. I guess I will PM the dev later to let him know I'm interested in helping him out.
Why would you build for another device if the dream has built into AOSP? Doesn't make a whole lot of sense to me unless they flat out took out the board file in ICS but you could easily put it back by pulling it from an earlier revision.
Sent from my DROID3 using XDA App
Hi,
Is there any ICS rom for Vibrant which is open source?
I have looked the passion and other ROM, I dont' think they are open source.
Is there one which I can download and built the ROM myself?
Thank you.
Not sure but all of them should be open source. just give credit where it's due and that should be good
Sent from my SGH-T959 using xda premium
When CM9 is out, it will all be on github, so you can pull and build it.
ICSSGS and Passion both (I think) claim to be open, but the proof is in looking for their sources and trying to build.
test.im.09 said:
Hi,
Is there any ICS rom for Vibrant which is open source?
I have looked the passion and other ROM, I dont' think they are open source.
Is there one which I can download and built the ROM myself?
Thank you.
Click to expand...
Click to collapse
Code Name Android is open source and currently has device trees for the Galaxy Nexus and Nexus S. There is no Vibrant device tree yet. Whenever I can get back to civilization my goal is to build one then to compile all from CNA source.
Onecosmics is open in the sense that they give you all the files that you need to build from the aosp device tree, AOKP and cm9 are also open.
Any of Neo's roms are not open source, nor does he even bother to respond to a PM about the device tree
https://github.com/TeamRegular
I have decide to create an organization open to commits from any one who wants to help out.
We are making modifications to the kernel ,device, and the recovery.
Please only commit things that have been tested.
We take no credit for our forked repositories.
Re: [Guide] Building from source Any ROM
Nice name..
seems the name is from regular show on CN
Sent from my SPH-D700 using xda premium
Many updates have been commited since our first notice. Please check out our github to view our newest commits.
XYLON ROM
Effsi from Team Regular has released XYLON for our OG Epic4G
:good: >>>>> http://forum.xda-developers.com/showpost.php?p=40227044&postcount=2513 <<<<< :good: