Hello all,
I've forked a CM9 repo for the HTC One X and am able to successfully compile and build but I'd like to add my own repo to the build process. I'm not quite sure how everything works together yet but it seems that the default.xml may be the place where I need to make the change. Is that true? If not, how can I go about adding my own source to my CM9 workspace in order to compile and build a ROM based on my source changes.
Thanks!
Related
Hi everyone,
To learn more on Android and to have fun, I'm creating a Kang based on
Cyanogenmod 7.2 for the HTC Glacier.
I got the source using repo and I was able to build a "vanilla" CM7.2 without issue.
Now I want to make some modification but I'm not sure
how you guys / gals are managing the source code.
I see 3 ways to organize my work :
1- Fork each part I want to work on and change the default manifest to fetch update from my github instead of cyanogenmod.
Pros : easy, can track my change using git
Cons : to fork every part just to change a text file is beurk...
2- Create local branch with git in every project I want to change.
Pros : easy
Cons : My commit are only local. Need to merge each project with CM branch.
3- Work outside cyanogenmod source folder and applied my change before building my kang.
Rollback everything (git reset) once my build is done.
Pros : no effort to stay in sync with CM sources. Can create a project on github with all my changes.
Cons : Need to use a kind of script to apply my mod every time I want to build.
Any opinions ? How are you managing your sources ?
I'm quite new with Android development, so feel free to suggest tutorial or better working technique.
Regards.
Hello,
Bump! :-D
I will try solution 3 but I am still interested to get opinions.
Regards
Sent from my HTC Panache / Darkside CM7.2 using xda premium.
Hi I'm interested in building ROMs for our tf300. I've tried building ROMs before both on my desire HD and this last weekend for the tf300t, but I've always run into problems: especially when I wanna build a ROM for a device that isn't officially supported.
For instance, I would like to unofficially build carbon ROM for the tf300t.
I know how to setup the computer in Linux and its all setup. I know how to repo init. I know how to repo sync.
Now for the hard part. Correct me if I'm wrong. In order to build an unofficial ROM I would need to pull the device tree and vendor tree, right, and put them into the repo that I repo synced earlier? Then I would need to update the local manifest to include those device and vendor trees?
I have several questions about it.
First, where can I get the device and vendor trees? It seems as if drgravy has some good trees, maybe I can use those?
Second, would those device and vendor trees have the 4.2 BL support or is that a different change?
Third, would I need to change the repo to build a proper kernel for the tf300t or would the device tree or vendor tree include the kernel source? Any help would be awesome.
Also in replying to this please don't just post a link. I've read a lot about the process, I just had some specific questions.
Thanks
Sent from my Transformer Pad TF300T using xda app-developers app
im trying to build the kernel from androids googlesource website, and want to know which defconfig i need to use to start the build
tegra3_android_defconfig
tegra_android_defconfig
tegra3_defconfig
tegra_defconfig
i couldnt find a grouper specific one
azoller1 said:
im trying to build the kernel from androids googlesource website, and want to know which defconfig i need to use to start the build
tegra3_android_defconfig
tegra_android_defconfig
tegra3_defconfig
tegra_defconfig
i couldnt find a grouper specific one
Click to expand...
Click to collapse
tegra3_android_defconfig seems to be the one.
Yes, I am trying to rebuild their from source. But, when I have testing on running. There are found red splash when I click them on screen. May I know what the caused of this ?
Thanks.
Ok, The problem has resolved now .
AOSP's guide to building kernels is quite useful. I actually used it earlier today.
http://source.android.com/source/building-kernels.html
It contains building instructions (obviously) as well as the proper defconfig for all AOSP devices.
So, how to build my own custom rom version ?
I want to build CM and cherrypicks some feature.
Does anyone have a guide or maybe anyone could teach me? Because i can't really follow the tutorial on CM wiki page.
Thanks a lot !
You need fairly decent specs internet and specs to compile. You can rent a linux VPS to compile to get rid of most of the headaches, or install a Linux distribution on your pc. Then you can follow https://wiki.cyanogenmod.org/w/Build_for_bacon#Build_CyanogenMod_and_CyanogenMod_Recovery if you have a Debian based Linux(Ubuntu) install, just substitute the branch in "repo init -u https://github.com/CyanogenMod/android.git -b cm-12.1" with cm-13, if you want to build cm13 nighties. If you want to cherry go to the root of the build directory and copy and paste the commands from the cm gerrit. You can find the command under the download tab.
Hello since I'm kinda new to xda , I cant create a thread
Quick question
How can I implement kexec hardboot patch in my kernel ,
I found this kernel by the mod developer
github. com/ davidepianca98/android_kernel_oneplus_msm8974-kexec
But cm-13.0 branch isn't available
https://github.com/davidepianca98/a...mmit/af5ef3d76f863f02c51cf860702b01536620ebf5 this commit tells you how to modify your kernel to implement it. You can possibly cherrypick it too.
Hello,
I recently compiled CyanogenMod 14.1 for my Android device using the official sources and want to compile Omni 7.1 for the same device and use the device tree and kernel from the official CM sources because there's no device tree for Omni. Is there a way to "convert" the CM device tree to work with the Omni sources? My exact problem is the compiler doesn't know my device so I can't run something like "brunch [device]" or "make [device]", although I already downloaded all device-specific repositories to the same subdirectory as I'd do it on CM.
Thanks in advance,
Oebbler
Oebbler1 said:
Hello,
I recently compiled CyanogenMod 14.1 for my Android device using the official sources and want to compile Omni 7.1 for the same device and use the device tree and kernel from the official CM sources because there's no device tree for Omni. Is there a way to "convert" the CM device tree to work with the Omni sources? My exact problem is the compiler doesn't know my device so I can't run something like "brunch [device]" or "make [device]", although I already downloaded all device-specific repositories to the same subdirectory as I'd do it on CM.
Thanks in advance,
Oebbler
Click to expand...
Click to collapse
You have to go to your android_device_manufacturer_yourphonecodename repo and rename cm.mk to omni_codename.mk, open it and change cm_codename to omni_codename.
You have also to rename cm.dependencies to omni.dependencies, but the repos included in that file may not be in omnirom source, so you would need to manually sync those repos in your android sorce tree.
You might have to make other minor changes, take a look at the rest of code in that repo.
For further info: https://docs.omnirom.org/Porting_Omni_To_Your_Device
Thank you, but I think I won't succeed in building Omni for my device because I always get strange errors.
Probs will get annoyed, cmsdk, cmhw, and cm encryption are significantly annoying. Also they moved their build dir, generally include useless common subtrees, and named dtbtool with CM suffix. Their build tree might be the most significant hindrance to unified building on Android, not only for the many unnecessary additions and dependencies they have for devices, but also they generally lack a community presence to answer or respond to users, so a lot of us get stuck with cleaning up their mess.
Notice how TWRP has a community presence here and are helpful. I'm not hating on cm, they have been doing this longer than most of us, but for ease id recommend using your rom choices tree.
Also the immensely significant annoyance of having to track devicesettings and the unwillingnes to nuke cmactions, combine it with cmsdk, or at least remove it's dependency in most trees is almost certainly going to cause you errors.
Sent from my One using XDA-Developers Legacy app