For people who want to make AOSP ROMs and Not cyanogenMod based ROMs
I have a present for you
Till the android.git.kernel.org is down
I have found a alternative
I have edited the Original "Repo" File to allow flawless syncing of google's resources
They can be found
https://github.com/spaarc/tools_repo
simply use
curl https://github.com/spaarc/tools_repo/blob/master/repo > ~/bin/repo
OR
curl https://github.com/spaarc/tools_repo/repo > ~/bin/repo
and to set git INIT use this command
repo init -u https://github.com/android/platform_manifest.git -b gingerbread
That is about it
Happy Building
First!
And what?
Prodigy said:
First!
And what?
Click to expand...
Click to collapse
How old are you? Stop this first thing. It's getting annoying. Especially when that reply is pointless.
And just read and understand that text.
spaarc provides a solution to get AOSP sources. That's it.
i was so excited when i saw this!!
but its times out on the "repo init -u https://github.com/android/platform_manifest.git -b gingerbread"
looks like its still trying to go to kernel.org
any ideas?
this repo isnt working
i keep getting error at line 1
How can I build the current stable version of Cyanogen?
With the following call I try to initialize the repo:
Code:
./repo init -u git://github.com/CyanogenMod/android.git -b cm-7.1.0 --repo-url=git://github.com/android/tools_repo.git
But this error occurs:
Code:
error: revision cm-7.1.0 in manifests not found
This is probably because there is no branch but only a tag for 7.1.0.
So, how to compile CyanogenMod 7.1.0?
xdanapo said:
How can I build the current stable version of Cyanogen?
With the following call I try to initialize the repo:
Code:
./repo init -u git://github.com/CyanogenMod/android.git -b cm-7.1.0 --repo-url=git://github.com/android/tools_repo.git
But this error occurs:
Code:
error: revision cm-7.1.0 in manifests not found
This is probably because there is no branch but only a tag for 7.1.0.
So, how to compile CyanogenMod 7.1.0?
Click to expand...
Click to collapse
cm-7.1.0 is simply a tag, a "point in time" for the gingerbread branch.
i'm pretty sure that gingerbread-release is what you're looking for, i think it's updated to 7.1.0.
otherwise, clone the entire gingerbread repository, and then do
Code:
git checkout cm-7.1.0
it should work.
Just follow this i believe. (Worked for me).
http://wiki.cyanogenmod.com/wiki/Building_from_source
Follow my guide here, works. I used it all the time.
Above reply does not work.
android git is down
ok, but how can I build the tag cm-7.1.0?
if I build the branch "gingerbread" I get a nightly build, right?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
There are 301 git repositories. I did a "git checkout cm-7.1.0" on every git repository and build cyanogen.
Now I get the file out/target/product/ace/update-cm-nightly-signed.zip.
Is this now the stable version 7.1.0 of cyanogenmod? Or is it a nightly build?
I need to add the SMSC95XX drivers to the Linux Kernel in an AOSP for the Moto-Z. Can someone tell me how one builds the Linux Kernel then the AOSP for the Moto-Z?
Thx,
Y-
YileKu said:
I need to add the SMSC95XX drivers to the Linux Kernel in an AOSP for the Moto-Z. Can someone tell me how one builds the Linux Kernel then the AOSP for the Moto-Z?
Thx,
Y-
Click to expand...
Click to collapse
Hello,
to include the driver download the kernel sources from here:
https://github.com/boulzordev/android_kernel_motorola_msm8996
and change
Code:
# CONFIG_USB_NET_SMSC95XX is not set to
to
Code:
CONFIG_USB_NET_SMSC95XX=Y
in "arch/arm64/configs/griffin_defconfig"
Something like
Code:
sed "/CONFIG_USB_NET_SMSC95XX/d" -i arch/arm64/configs/griffin_defconfig/griffin_defconfig && echo "CONFIG_USB_NET_SMSC95XX=y" >> arch/arm64/configs/griffin_defconfig/griffin_defconfig
should do the job ( run these inside the cloned kernel repo )
Moto-Z AOSP newbie
Thanks for the pointer. I can do that. I have built AOSP for the Nexus-6, but I have not built it for the Moto-Z Droid. Can someone point me to the general instructions on how to build for the Moto-Z?
CHeers,
Y-
Maybe can build MIUI for the Moto-Z?
rakee said:
Maybe can build MIUI for the Moto-Z?
Click to expand...
Click to collapse
Building miui has 2 way :
Building with rompatch and porting from similar device (Mi5 is good for for moto z) (it's not very common and certain way)
Here's patchrom link : https://github.com/MiCode/patchrom/branches
Patchrom latest version is marshmallow and it's too late to start building most of the people is updated to nuogat so they can't install MM kernel
But about second way (porting), I've tried this but no success to boot I got some errors on netlink uevent
So we need to wait for patchrom to get nougat update and I'll try porting it if I didn't buy new phone
rakee said:
Maybe can build MIUI for the Moto-Z?
Click to expand...
Click to collapse
I don't recognize 'MIUI' what is meant by this?
YileKu said:
I don't recognize 'MIUI' what is meant by this?
Click to expand...
Click to collapse
MIUI is a custom ROM from china
Any chance I can build a ROM for the Moto-Z from here https://source.android.com/source/building-kernels?
StarStorm said:
Hello,
to include the driver download the kernel sources from here:
https://github.com/boulzordev/android_kernel_motorola_msm8996
and change
Code:
# CONFIG_USB_NET_SMSC95XX is not set to
to
Code:
CONFIG_USB_NET_SMSC95XX=Y
in "arch/arm64/configs/griffin_defconfig"
Something like
Code:
sed "/CONFIG_USB_NET_SMSC95XX/d" -i arch/arm64/configs/griffin_defconfig/griffin_defconfig && echo "CONFIG_USB_NET_SMSC95XX=y" >> arch/arm64/configs/griffin_defconfig/griffin_defconfig
should do the job ( run these inside the cloned kernel repo )
Click to expand...
Click to collapse
Thanks StarStorm,
After making these changes, how does one build the ROM with the new kernel?
Y-
YileKu said:
Thanks StarStorm,
After making these changes, how does one build the ROM with the new kernel?
Y-
Click to expand...
Click to collapse
Oh, didn't see your reply until you quoted me~
You can follow Lineage's wiki entry for the Moto Z. Depending on which ROM you want to build you just change
Code:
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
to
Code:
repo init -u <url> -b <branch>
, e.g.
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat
for Resurrection Remix. If you use a ROM that doesn't officially support the Moto Z ( everything other than AOKP/Lineage afaik ) you'll have to add https://github.com/boulzordev/android_device_motorola_griffin and https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your local manifest. You can skip the "extract-files.sh" step if you do that. Once you synched everything with "repo sync" you can make the changes I described in my earlier post.
StarStorm said:
Oh, didn't see your reply until you quoted me~
You can follow Lineage's wiki entry for the Moto Z. Depending on which ROM you want to build you just change
Code:
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
to
Code:
repo init -u <url> -b <branch>
, e.g.
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat
for Resurrection Remix. If you use a ROM that doesn't officially support the Moto Z ( everything other than AOKP/Lineage afaik ) you'll have to add https://github.com/boulzordev/android_device_motorola_griffin and https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your local manifest. You can skip the "extract-files.sh" step if you do that. Once you synched everything with "repo sync" you can make the changes I described in my earlier post.
Click to expand...
Click to collapse
StarStorm,
Thanks for the direction. I am a bit of a newbie on this so I want to verify the steps:
1. Follow the instructions at https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484, up to the point you do the 'repo init'
2. Use the repo init command 'repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat' instead.
3. Add the following repos to my manifest: https://github.com/boulzordev/androi...torola_griffin and https://github.com/boulzordev/propri...torola_griffin
4. Skip the 'extract-files.sh' command
5. do a 'repo sync' command
6. Modify the linux kernel to include the driver
7. follow the instructions for building at: https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t355148
thx,
Y-
YileKu said:
StarStorm,
Thanks for the direction. I am a bit of a newbie on this so I want to verify the steps:
1. Follow the instructions at https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484, up to the point you do the 'repo init'
2. Use the repo init command 'repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat' instead.
3. Add the following repos to my manifest: https://github.com/boulzordev/androi...torola_griffin and https://github.com/boulzordev/propri...torola_griffin
4. Skip the 'extract-files.sh' command
5. do a 'repo sync' command
6. Modify the linux kernel to include the driver
7. follow the instructions for building at: https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t355148
thx,
Y-
Click to expand...
Click to collapse
Yep, looks good to me :good:
StarStorm said:
Yep, looks good to me :good:
Click to expand...
Click to collapse
I did the repo init command and I was looking to add the repos to the manifest. The only file I found was .repo/manifest.xml, it didn't seem obvious how to add the two repos above.
Y-
StarStorm said:
Oh, didn't see your reply until you quoted me~
You can follow Lineage's wiki entry for the Moto Z. Depending on which ROM you want to build you just change
Code:
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
to
Code:
repo init -u <url> -b <branch>
, e.g.
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat
for Resurrection Remix. If you use a ROM that doesn't officially support the Moto Z ( everything other than AOKP/Lineage afaik ) you'll have to add https://github.com/boulzordev/android_device_motorola_griffin and https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your local manifest. You can skip the "extract-files.sh" step if you do that. Once you synched everything with "repo sync" you can make the changes I described in my earlier post.
Click to expand...
Click to collapse
When I did the 'breakfast lineage_griffin-userdebug'
I get:
.......
* [new branch] cm-14.1 -> github/cm-14.1
Fetching projects: 100% (5/5), done.
Checking out files: 100% (52729/52729), done.
Syncing work tree: 100% (5/5), done.
Looking for dependencies in kernel/motorola/msm8996
Dependencies file not found, bailing out.
Looking for dependencies in external/bson
Dependencies file not found, bailing out.
Looking for dependencies in external/stlport
Dependencies file not found, bailing out.
Looking for dependencies in device/qcom/common
Dependencies file not found, bailing out.
Looking for dependencies in packages/resources/devicesettings
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'lineage_griffin'
** Do you have the right repo manifest?
[email protected]:~/android/system$
YileKu said:
When I did the 'breakfast lineage_griffin-userdebug'
I get:
.......
* [new branch] cm-14.1 -> github/cm-14.1
Fetching projects: 100% (5/5), done.
Checking out files: 100% (52729/52729), done.
Syncing work tree: 100% (5/5), done.
Looking for dependencies in kernel/motorola/msm8996
Dependencies file not found, bailing out.
Looking for dependencies in external/bson
Dependencies file not found, bailing out.
Looking for dependencies in external/stlport
Dependencies file not found, bailing out.
Looking for dependencies in device/qcom/common
Dependencies file not found, bailing out.
Looking for dependencies in packages/resources/devicesettings
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'lineage_griffin'
** Do you have the right repo manifest?
[email protected]:~/android/system$
Click to expand...
Click to collapse
Did you add https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your manifest? What does your local manifest look like?
YileKu said:
I did the repo init command and I was looking to add the repos to the manifest. The only file I found was .repo/manifest.xml, it didn't seem obvious how to add the two repos above.
Y-
Click to expand...
Click to collapse
You aren't supposed to modify .repo/manifest.xml , add your local changes to .repo/local_manifests.xml ( with the same syntax as manifest.xml uses )
StarStorm said:
Did you add https://github.com/boulzordev/proprietary_vendor_motorola_griffin to your manifest? What does your local manifest look like?
Click to expand...
Click to collapse
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'lineage_griffin'
** Do you have the right repo manifest?
[email protected]:~/moto-z/lineage$ cat .repo/local_manifest
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="1"
fetch="https://github.com/boulzordev/android_device_motorola_griffin" />
<remote name="2"
fetch="https://github.com/boulzordev/proprietary_vendor_motorola_griffin" />
</manifest>
[email protected]:~/moto-z/lineage$
YileKu said:
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/motorola/griffin/lineage.mk]]: "vendor/motorola/griffin/griffin-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'lineage_griffin'
** Do you have the right repo manifest?
[email protected]:~/moto-z/lineage$ cat .repo/local_manifest
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="1"
fetch="https://github.com/boulzordev/android_device_motorola_griffin" />
<remote name="2"
fetch="https://github.com/boulzordev/proprietary_vendor_motorola_griffin" />
</manifest>
[email protected]:~/moto-z/lineage$
Click to expand...
Click to collapse
Add something like this to your local manifest, right now you only defined from where you want to download the device tree and the vendor files, you also need to specify where you want them located
Code:
<project path="device/motorola/griffin" name="android_device_motorola_griffin" remote="1" />
<project path="vendor/motorola/griffin" name="proprietary_vendor_motorola_griffin" remote="1" />
StarStorm said:
Add something like this to your local manifest, right now you only defined from where you want to download the device tree and the vendor files, you also need to specify where you want them located
Code:
<project path="device/motorola/griffin" name="android_device_motorola_griffin" remote="1" />
<project path="vendor/motorola/griffin" name="proprietary_vendor_motorola_griffin" remote="1" />
Click to expand...
Click to collapse
Thanks that worked. I had to remove a duplicate path in roomservice.xml, then the sync and breakfast worked.
Y-
Thanks. Okay the build is working. I tried : 'cd kernel/motorola/msm8996'; make ARCH=arm64 CROSS_COMPILE=arm-linux-androideabi- menuconfig; /* enabled SMSC drivers to be in the kernel */; cd -; breakfast lineage_griffin-userdebug; brunch lineage_griffin-userdebug;" and get an error compiling setup.c. Any chance i can get the steps to configure, compile and include the kernel in an android build?
Thanks,
Y-
Hello
I'm trying to build AOSP 6.0.1 using your CM device files (CM13 has been successfully built for my device, Huawei P8). I'm not too experienced with this so some help is appreciated. Right now I have synced the google repo
repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.1_r80
cd .repo
git clone https://github.com/CM-Huawei-P8-Development/local_manifests_gra_l09
cd local_manifests_gra_l09
cd ../..
repo sync
This is where I'm now. The confusion is about am I supposed to also download or sync the device files from https://github.com/CM-Huawei-P8-Development/device_gra_l09 (the device tree)
Also is this https://github.com/CM-Huawei-P8-Development/kernel needed to be downloaded separately? I see in the hwgra-l09-dev.xml file that the repos are indeed listed but will it also work for AOSP?
I'm following a guide for Sony device and it says that next I'm supposed to
source build/envsetup.sh && lunch <--- here something device specific maybe?
and
make –j 8
What am I missing ?