Hi guys
I'm new to rom development, I have many question to deal with...
First thing first, I'm about to download android source as per the steps in source.android.com, but i have limited data quota per day. so i searched the internet to reduce the downloading source size and i found that adding
Code:
--depth=1
to git clone command will reduce the downloading size.
But I need to know what is the difference between below two git clone commands
Code:
repo init --depth=1 -u https://android.googlesource.com/platform/manifest -b android-5.0.0_r1.0.1
and
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-5.0.0_r1.0.1
Second thing is I'm building rom for Huawei ascend P6-U06 (code name: hwp6-u06), for this device i can't find kernel tree, device tree and vendor blobs for lollipop. I'm only getting kernel tree, device tree and vendor blobs for Kitkat in github (cm-11.0 based) can i use these ones
orelse can i use google common kernel source to build custom kernel
Related
Hi,
In the android git repository, there are three branches/tags. The default one is master. cupcake is the most famous. The last one is release-1.0 but which is not the RC30 release (it can't be compiled at all).
I doesn't know git well, so I must miss some tags for RC30. Is there anyone can tell me how to get the RC30 source code? Big thanks!
Sunner
Try:
repo init -u git://android.git.kernel.org/platform/manifest.git -b release-1.0
jashsu said:
Try:
repo init -u git://android.git.kernel.org/platform/manifest.git -b release-1.0
Click to expand...
Click to collapse
I've tried this command before. There were some error like "nowhere" when "repo sync". And I've mentioned in the first post that the release-1.0 can't be compiled at all. So many .c files in it miss including some header files.
Can't compile? Hmm... Well I am not working with the release-1.0 branch anymore so I can't be of much help there.
As for the source code used to produce G1 Android builds RC19-RC30, those were never made public. All Android platform development prior to cupcake was divided between openly available and private internal branches. The reasons for this are manifold and infinitely debatable in merit. One reason you can not build a true RC30 from the public repo is that they can not legally distribute proprietary modules from there.
Why wont my compiled rom with Linaro optimzations boot ive successfully compiled rom for other devices just not this one have any thoughts i even this
git clone git://github.com/TheMuppets/proprietary_vendor_broadcom.git -b cm-10.1 vendors/broadcom
git clone git://github.com/TheMuppets/proprietary_vendor_nvidia.git -b cm-10.1 vendors/nvidia
git clone git://github.com/TheMuppets/proprietary_vendor_motorola.git -b cm-10.1 vendors/motorola
missed some file/library
dl an rom, open .zip file and compare all file with you rom.
you will find some missing file
Hello xda,
I had a little time on my hands the other night, and wanted to figure out a way that I could work on any of the project repositories needed to build say, aokp, cyanogenmod, aosp, etc... without having to connect to the internet.
Mirroring is not new. Simple enough to:
Code:
mkdir cm-mirror
cd cm-mirror
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1 --mirror
repo sync -j[dl-jobs]
then create a working directory:
Code:
cd ..
mkdir cm-work
cd cm-work
repo init -u file:///Volumes/Android/cm-mirror/CyanogenMod/android.git --reference /Volumes/Android/cm-mirror/ -b cm-10.1
repo sync # no jobs needed. super fast.
But at this point you only have what you need for cm-10.1. What if you also have work you are doing for 10.1.0? Or an old update to make for cm-7.2.0?
I originally started looking for a solution to sync every branch in the manifest one at a time, but while talking with cdesai he showed me a really clean way of getting the repositories directly from gerrit.
Anyways, here is the resulting script. Let me know your thoughts.
I've moved the script to a git repository here: https://github.com/bhundven/repo-mm
in case anyone wants to contribute.
I've also written a post on my blog about using the new gerrit-mirror.sh on gh.
ChangeLog
Changes:
[06/30/13]: Announce some updates to gerrit-mirror.sh, and blog post.
[06/24/13]: Moved gist to github project.
GitHub for repo-mm.
i' m following a guide to try builiding my first rom and i don't understand a step
"6. After the repo sync finally finishes, all you need to do is add your device, kernel, vendor specific files for the device you are building for."
Where can i find these things? Is there a command i should give in the terminal?
I've searched a little but not found anything...any hint would be accepted!
tylpica wives
phoenixita said:
i' m following a guide to try builiding my first rom and i don't understand a step
"6. After the repo sync finally finishes, all you need to do is add your device, kernel, vendor specific files for the device you are building for."
Where can i find these things? Is there a command i should give in the terminal?
I've searched a little but not found anything...any hint would be accepted!
Click to expand...
Click to collapse
What rom are you building? If CM10.1 or CM10.2 just follow the instructions on
wiki.cyanogenmod.org - w - Build_for_ville
(sorry, cannot post the link since I don't have enough posts Just replace - with /)
I guess your point 6 refers to items 2.7-2.9 where prebuilt apps, device-specific code (e.g. kernel etc.) and other
proprietary drivers are copied to your source code.
To init for CM10.1, use
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
for CM10.2 use
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
Hope this helps. good luck
drkxyz said:
What rom are you building? If CM10.1 or CM10.2 just follow the instructions on
wiki.cyanogenmod.org - w - Build_for_ville
(sorry, cannot post the link since I don't have enough posts Just replace - with /)
I guess your point 6 refers to items 2.7-2.9 where prebuilt apps, device-specific code (e.g. kernel etc.) and other
proprietary drivers are copied to your source code.
To init for CM10.1, use
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
for CM10.2 use
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
Hope this helps. good luck
Click to expand...
Click to collapse
I'm trying to build another rom not CM but i'm trying following the 2.7-2.9 steps from your link
What
Building from source or MOD ROM?
xdluisssxd said:
Building from source or MOD ROM?
Click to expand...
Click to collapse
i think i'm building it from source lol
Okay So you we have flashed many custom ROMs in your device, but have you wonder , how developers build custom ROMs , Well as a matter of fact we will Cover this Topic , So To build Custom Rom we need to mainly sync a source. Let's say it's LineageOS , so We have to first initialise the source via
Code:
repo init -u "clone url" -b "branchname"
You need to have a linux distro with atleast 8 cores and atleast 12 gb ram and 130 gb of HDD.
For example :
Let's take lineageOS For pie so the branch will be lineage-16.0
Code:
repo init -u git://github.com/LineageOS/android.git -b lineage-16.0
As we have initialised the source Let's Sync it , but before that you might want to configure your GitHub username and email , here we will do it globally , so that you don't have to do that again and again.
To configure GitHub username
Code:
git config --global user.name "FIRST_NAME LAST_NAME"
To configure GitHub email
Code:
git config --global user.email "YOUR EMAIL"
Now let's sync the Source
Code:
repo sync -j$(nproc --all)
Now as we synced the source , we just need to add device tree , vendor blobs and kernel source. After that we can start the bring up by
Code:
. build/envsetup.sh
lunch lineage_devicename-userdebug
brunch devicename
The build should Start
Well For more detailed explanation refer to my guide which I made for Rookies
Guide :- https://github.com/TheGlitchh/CustomRom_Building_Guide/
You can always pm me at Telegram for build errors and bug fixes ,I will try my best to help you out
Telegram username :- TheGlitchh
========O=======