Hello,
I am just a beginner, dont blame me please.
Just forking some repos from github.com/android but there is no vendor repo, CM, omni has one.
Can somebody help me.
Related
So a bunch of friends and I want to try to write a custom ROM from AOSP for Galaxy Nexus (toro). One thing we were thinking about was syncing all our code via github.
We will create our own repo so that we can make sure all our code is in sync.
One thing we looked at was github.com/android
Should we just fork all the repo's from the github.com/android page? We understand that it doesn't make sense to download everything from AOSP and upload via github.
Any help clarifying if we should fork or mirror repo's and what repo's specifically so we can get started.
msg04 said:
So a bunch of friends and I want to try to write a custom ROM from AOSP for Galaxy Nexus (toro). One thing we were thinking about was syncing all our code via github.
We will create our own repo so that we can make sure all our code is in sync.
One thing we looked at was github.com/android
Should we just fork all the repo's from the github.com/android page? We understand that it doesn't make sense to download everything from AOSP and upload via github.
Any help clarifying if we should fork or mirror repo's and what repo's specifically so we can get started.
Click to expand...
Click to collapse
Forking would be the polite thing to do because then the other developer's changes would be logged and tracked in your code. As too which ones that totally depends on what you are wanting to change. I would however suggest just forking the ones you plan on modifying and syncing the rest from the AOSP Github.
You don't always have to "fork" in the traditional sense. As long as you keep the previous commits it will be good taste. If you are only working on a jellybean rom, you can create a repo on github. Clone that repo. Then you can pull only the jellybean aosp branch into the one you created. You can do the same for every other project you add into your repo and before you know it, you saved a ton of bandwidth by only syncing one branch instead of tracking all branches. just my two cents.
i am very much interested in compiling cm from sources . If a device(running 2.3) is not officially supported by cm so no device tree is found in github also..i want to learn how to make a device tree and vendor tree from scrach please guide me .aim fully prepared to spend my free time n this
So, I have this source for building CM11, for xpeira sp, huashan. We already have CM11 but, I desperately need HALO in CM. So I want to cherry-pick HALO to cm.
So I have start from the source. Here's what we have
https://github.com/CyanogenMod/android_device_sony_huashan/
https://github.com/freexperia/android_device_sony_huashan
How do I start from here? I want to cherry-pick the HALO and build the rom, nothing else.
I've set up building environment in my current OS. So I guess I need to fork the repo from git to my pc, then cherry-pick the HALO and build...? Plus, in the source, there's a few folder that says no longer needed, so how I get rid of them, too?
You won't get any help here. Tried getting help here and not a single dev helped. Here we want to help each other but the ones with knowledge don't want to share with us who just want to build and have fun. I'm really sorry kid
Hello
Can anyone please point me out to the DSB sources? Unable to find them, and really want to try porting them. The gerrit links to commits they provided on G+ dont seem to work :/
I want to build OmniRom for my device, but my device isn't supported. I have heard that if you have the device tree, you can build the AOSP or OmniRom 'without any problems'. -Is that true? If yes, do I need to generate the vendor and kernel tree also from boot.img?
It seems like a stupid question, but I'm new to android development.
Am I in the right forum?