Im building Omnirom, from source (im a newbie) and i have succesfully build android 4.4.4 from the official repo.
Now, i want to update that rom, using https://github.com/duvall which has a branch with android 5.1 for my galaxy s2 (i9100)
I haver read some posts, that said that a i have to remove official repo and pull to that custom repo using local manifest. but i dont know how to do that... i dont know what i need to put in that local manifest could anyone help me ?
thanks
Related
I'm trying to better understand how the devs around here do what they do. I'm an Electrical Engineer and I make no claims to be a proper software developer. I know my way around C, Python, and Bash. I know my way around git and have worked with various build/release processes before so I can stumble through some CMAKE and MAKE build processes. Currently I have installed the the android SDK, compiled AOSP master branch and run it in an emulator. I've also compiled Cyanogen mod repos for generic-eng though I haven't gotten that to properly boot on an emulator yet.
So that's an idea of who I am and where I'm starting from. Now for the questions. I figure if I can understand the build environment and process I can learn quite a bit from the large history of available changes, especially since there is an Atrix Dev Team for Cyanogen.
Cyanogen Mod
I can't tell which repo's here are pure AOSP, modified AOSP, or from scratch pure Cyanogenmod.
Do the CM repo's track AOSP as a remote branch?
If yes, does that mean I can build pure AOSP from CM repo's via repo?
If no, how can you tell where in the AOSP development cycle the CM repo's fork from?
Are 'nightly' builds by definition a repo sync of the non-release base simply built as is? AKA for an Atrix nightly, you would checkout the gingerbread, sync, and build (assuming you're setup for building in the first place)
Are Official release only tracked via git tags? IE for CM 7.1 it's not really tracked on the manifest so would you need to find the proper tag and do a repo forall git checkout -b cm-7.1 or similar? I'm asking how you could build a previous release which should match the official release.
Atrix Dev Team
Similar to the CM Question, do these repo's track CM as their base repo's?
Could someone describe the typical development cycle of how the Atrix port is handled on top of a moving CM development? I'm a little lost as to how AOSP -> CM -> Atrix dev works out. If I checkout the Atrix manifest to gingerbread and perform git diff with the /m/gingerbread (I beleive the CM tracking branch) I see no differences. Are Atrix-Dev-Team and Official CM repo's simply fully in sync at this point?
How would I setup my repo to match a given Release (as in what tag or manifest I understand git)?
How would I setup my repo to match a given Nightly (as in what tag or manifest I understand git)?
As above, could you build pure CM from the Atrix repo's? This very well could be answered with the above questions.
Generic Info
What's a 'kang'?
My guess would be it's a build produced from the source repositories and not an official release by the developers.
Exploring the AOSP I noticed a separate kernel download link. I know CM uses a custom kernel but is that included in the default builds or is that typically flashed and managed separately?
After I'm familial with the whole process, and knowing what I've stated above what's the best step form there to be able to help contribute? Right now I've picked up a book on programming Apps on Android so I can learn the tools and some Java and I've had c++ on my radar for some time.
Thanks for your time. I've tried to get relatively well informed before I post questions.
So ... am I asking these in the wrong place?
Ok. I know this is nooby but I don't have anyone else to ask. I am trying to build Android 4.4 Kit Kat for the HTC Flyer. I followed a guide. I installed all the packages, installed the repo downloaded the source code but after that it said that i need to clone my device tree from github. I googled HTC flyer github but i only found a branch of a kernel from doomlord and i don't think that's what I am looking for. Now I am stuck and don't know what to do. So basicly I don't what to after downloading the source code using repo sync.
Any sort of help would be appretiated. I am just trying to bring my device back from the dead. Thank you and again sorry for the nooby question.
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
Hi,
As some of you might be aware of, Sony released the sources to enable building of AOSP straight from their sources for the Z2 (and other devices also).
I was just wondering if any of you has been able to build from those sources ?
I can init the repo.
I can sync the repo.
I can build the envsetup.
But then when it comes to compile the whole bunch, I always end up with an error message stating the I use a version of Make that is too young (4.1) and that I should use 3.8 instead...
Any clue on how to solve this ?
I guess it's trivial, but I have no idea how to proceed
Regards.
I've been trying to figure out how to build Cyanogenmod from source for a few devices. I've looked at many tutorials and such, but I haven't been able to find one that explains how to build Cyanogen for a device that had an old version of Cyanogen but hasn't been updated since. For example, the official builds for a certain device only go up to 12.1, but I want to build it for 13.0. Does anyone have any advice?
spenceboy98 said:
I've been trying to figure out how to build Cyanogenmod from source for a few devices. I've looked at many tutorials and such, but I haven't been able to find one that explains how to build Cyanogen for a device that had an old version of Cyanogen but hasn't been updated since. For example, the official builds for a certain device only go up to 12.1, but I want to build it for 13.0. Does anyone have any advice?
Click to expand...
Click to collapse
I would recommend starting by using the device tree for your device that supports 12.1 and try using that tree to compile 13. To do this download the 13 code and put the 12.1 device tree in the proper folders (device, vendor, kernel) and try compiling a build and start seeing what errors you get. Let me know if you still have questions I'll do my best to help you out!