• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Cyanogenmod12.1 Build Environment Set-Up

So giving another shot..
Got repo synced.
So now I need device, vendor, and kernel trees? Are those the zips in the cm 12.1 thread?
Just add those to cm 12.1 folder now or do they need to be extracted?

Thanks
You can also add this line to your local manifest:
Code:
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.1"/>
It will automatically download the device/qcom/common sources to your source and automatically update them every time you run "repo sync"
 
Upvote 0
any idea what I'm doing wrong?
Thanks
 

Attachments

  • Screenshot from 2015-05-21 21:59:45.png
    Screenshot from 2015-05-21 21:59:45.png
    279.2 KB · Views: 140
Upvote 0
any idea what I'm doing wrong?
Thanks
Just curious, did you add the device_qcom_common to your local manifest? It should look like this:

Code:
<?xml version="1.0" encoding="UTF-8"?>

<manifest>

[LIST=1]
[*]<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.1"/>
[/LIST]
</manifest>
I had this problem too, but the build ran fine after doing this :)

i have a quad core i5 about how many gigs isit to download i have very crappy speeds 1mbps down where i live

Then you're gonna be waiting a looooong time. The download is about 40~ GB. It took me four days or so to download it out here in redneckville. However, you can pause and restart the download at any time you want. To start it, simply type "repo sync". To pause it, hit Ctrl + Z in your terminal window. To resume the download, just repo sync again.
 
Upvote 0
Just curious, did you add the device_qcom_common to your local manifest? It should look like this:

Code:
<?xml version="1.0" encoding="UTF-8"?>

<manifest>

[LIST=1]
[*]<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.1"/>
[/LIST]
</manifest>
I had this problem too, but the build ran fine after doing this .

Sorry for the all the questions.. But where is my local manifest? I am determined to figuring this out, but man i feel dumb
 
  • Like
Reactions: Ph0enix_216
Upvote 0
Sorry for the all the questions.. But where is my local manifest? I am determined to figuring this out, but man i feel dumb
Hey, no worries, it's good to ask questions :) Your local manifest is stored at /.repo/local_manifests/local_manifest.xml (sometimes its called room service.xml as well). /.repo is at the root of your source code directory, you may hive to hit Ctrl + H in Ubuntu's file explorer to see it, as it's a hidden directory.
 
  • Like
Reactions: adamhos1234
Upvote 0
Hey, no worries, it's good to ask questions :) Your local manifest is stored at /.repo/local_manifests/local_manifest.xml (sometimes its called room service.xml as well). /.repo is at the root of your source code directory, you may hive to hit Ctrl + H in Ubuntu's file explorer to see it, as it's a hidden directory.

Thanks, i did not know about the hidden folders! I see .repo now, but i do not see a local_manifest.xml or room service either.
Do i need to create it?
Thanks again for your help!
 

Attachments

  • Screenshot from 2015-05-22 09:32:51.png
    Screenshot from 2015-05-22 09:32:51.png
    171.5 KB · Views: 120
Upvote 0
Thanks, i did not know about the hidden folders! I see .repo now, but i do not see a local_manifest.xml or room service either.
Do i need to create it?
Thanks again for your help!
You're in ~/.repo/repo. The file you're looking for should be in ~/.repo/local_manifests/ . There should be a file called room_services.xml or something. Or, if you'd like, I can give you my local_manifest :)
 
  • Like
Reactions: adamhos1234
Upvote 0
Upvote 0
so tried fresh again today and i dont know what is going on?
i will have some time a bit later, but does this help anyone know what i'm doing wrong?
Thanks
:~/Cyanogenmod12.1$ . build/envsetup.sh && brunch x5
including device/lge/x5/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
including vendor/cm/vendorsetup.sh
Trying dependencies-only mode on a non-existing device tree?

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.1.1
CM_VERSION=12.1-20150523-UNOFFICIAL-x5
TARGET_PRODUCT=cm_x5
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.16.0-37-generic-x86_64-with-Ubuntu-14.04-trusty
HOST_BUILD_TYPE=release
BUILD_ID=LMY48B
OUT_DIR=/home/adam/Cyanogenmod12.1/out
============================================

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.1.1
CM_VERSION=12.1-20150523-UNOFFICIAL-x5
TARGET_PRODUCT=cm_x5
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.16.0-37-generic-x86_64-with-Ubuntu-14.04-trusty
HOST_BUILD_TYPE=release
BUILD_ID=LMY48B
OUT_DIR=/home/adam/Cyanogenmod12.1/out
============================================
find: `dummy': No such file or directory
build/core/copy_headers.mk:15: warning: overriding commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/include/qcom/display/copybit.h'
build/core/copy_headers.mk:15: warning: ignoring old commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/include/qcom/display/copybit.h'
build/core/copy_headers.mk:15: warning: overriding commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/include/qcom/display/copybit_priv.h'
build/core/copy_headers.mk:15: warning: ignoring old commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/include/qcom/display/copybit_priv.h'
PRODUCT_COPY_FILES device/lge/x5/prebuilt/etc/audio_effects.conf:system/etc/audio_effects.conf ignored.
build/core/Makefile:46: warning: overriding commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/etc/clatd.conf'
build/core/base_rules.mk:550: warning: ignoring old commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/etc/clatd.conf'
build/core/Makefile:46: warning: overriding commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/lib/egl/egl.cfg'
build/core/base_rules.mk:550: warning: ignoring old commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/lib/egl/egl.cfg'
build/core/Makefile:46: warning: overriding commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/lib/libtime_genoff.so'
build/core/prebuilt_internal.mk:247: warning: ignoring old commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/lib/libtime_genoff.so'
build/core/Makefile:46: warning: overriding commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/lib/libcnefeatureconfig.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/lib/libcnefeatureconfig.so'
build/core/Makefile:46: warning: overriding commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/lib/libril.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/lib/libril.so'
build/core/Makefile:46: warning: overriding commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/bin/rild'
build/core/base_rules.mk:550: warning: ignoring old commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/bin/rild'
build/core/Makefile:46: warning: overriding commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/lib/libdashplayer.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `/home/adam/Cyanogenmod12.1/out/target/product/x5/system/lib/libdashplayer.so'
No private recovery resources for TARGET_DEVICE x5
make -C kernel/lge/msm8226 O=/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/adam/Cyanogenmod12.1/prebuilts/misc/linux-x86/ccache/ccache arm-eabi-" VARIANT_DEFCONFIG= SELINUX_DEFCONFIG= cm11_msm8226_defconfig
/bin/bash: m4: command not found
make: *** [/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/ETC/sepolicy_intermediates/policy.conf] Error 127
make: *** Deleting file `/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/ETC/sepolicy_intermediates/policy.conf'
make: *** Waiting for unfinished jobs....
make[1]: Entering directory `/home/adam/Cyanogenmod12.1/kernel/lge/msm8226'
GEN /home/adam/Cyanogenmod12.1/out/target/product/x5/obj/KERNEL_OBJ/Makefile
net/ipv6/Kconfig:260:warning: multi-line strings not supported
warning: (SND_SOC_MSM8226) selects DOLBY_DAP which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && SND_SOC_MSM8974)
warning: (SND_SOC_MSM8226) selects DOLBY_DAP which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && SND_SOC_MSM8974)
#
# configuration written to .config
#
make[1]: Leaving directory `/home/adam/Cyanogenmod12.1/kernel/lge/msm8226'
adam@adam-Latitude-D630:~/Cyanogenmod12.1$
 
Upvote 0
make: *** [/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/ETC/sepolicy_intermediates/policy.conf] Error 127
make: *** Deleting file `/home/adam/Cyanogenmod12.1/out/target/product/x5/obj/ETC/sepolicy_intermediates/policy.conf'
make: *** Waiting for unfinished jobs....

I would delete Cyanogenmod 12.1/build ,/device, /kernel, /vendor directories
re-run repo sync, then re add the device/lge/x5, device/qcom/common, kernel/lge/msm8226, vendor/lge/x5 directories.
then run make installclean && make clobber && brunch x5
 
Last edited:
  • Like
Reactions: adamhos1234
Upvote 0
I would delete Cyanogenmod 12.1/build ,/device, /kernel, /vendor directories
re-run repo sync, then re add the device/lge/x5, device/qcom/common, kernel/lge/msm8226, vendor/lge/x5 directories.
then run make installclean && make clobber && brunch x5

Still had no luck...
That was with Ubuntu..

Wiped EVERYTHING! And installed LinuxMint, ran the script added directories and created a local_manifest.
Ran repo sync again
And then started the build.
It has been building for at least 12 hours so I guess its working? We'll see soon hopefully!
 
  • Like
Reactions: Bad_MOFO_33
Upvote 0
Still had no luck...
That was with Ubuntu..

Wiped EVERYTHING! And installed LinuxMint, ran the script added directories and created a local_manifest.
Ran repo sync again
And then started the build.
It has been building for at least 12 hours so I guess its working? We'll see soon hopefully!
Yeah, the first build takes a while, because it has to generate all the files from scratch. Once they've been creates though, future builds shouldn't take nearly as long.
 
Upvote 0
So I've been building my own updates for this device, and I can get the build to boot fine, but I lose control of my home button. I managed to enable the navbar and include it in my build, but I kinda need the home button lol.

I don't remember exactly but its in system/usr/keylayout
One of those files you need to edit the correct key for 'home' and 'wake'
Maybe 102 or 172.

Sorry my mind is kinda mush now
 
Last edited:
  • Like
Reactions: Ph0enix_216
Upvote 0
Still had no luck...
That was with Ubuntu..

Wiped EVERYTHING! And installed LinuxMint, ran the script added directories and created a local_manifest.
Ran repo sync again
And then started the build.
It has been building for at least 12 hours so I guess its working? We'll see soon hopefully!

Damn man 12 hours and not done yet? What are your computer specs? With my i3 and 4gb ram with 7200 rpm HD and ccache of 50gb on a fresh build, I don't think I've ever topped 4 hours 30 minutes for a complete build. That's KitKat and lollipop.

Your only running a build for the volt right? I know theres a compiling option to compile all targets with source available, hopefully that's not what your doing lol.
 
Upvote 0
Damn man 12 hours and not done yet? What are your computer specs? With my i3 and 4gb ram with 7200 rpm HD and ccache of 50gb on a fresh build, I don't think I've ever topped 4 hours 30 minutes for a complete build. That's KitKat and lollipop.

Your only running a build for the volt right? I know theres a compiling option to compile all targets with source available, hopefully that's not what your doing lol.

Lol!
I have no idea what I'm doing...
BTW it threw an error not long after that post. I'm pretty much giving up, I assume you are right and my computer is not fit for the task.
 
  • Like
Reactions: whoshotjr2006
Upvote 0
Damn man 12 hours and not done yet? What are your computer specs? With my i3 and 4gb ram with 7200 rpm HD and ccache of 50gb on a fresh build, I don't think I've ever topped 4 hours 30 minutes for a complete build. That's KitKat and lollipop.

Your only running a build for the volt right? I know theres a compiling option to compile all targets with source available, hopefully that's not what your doing lol.
Yeah since my computer took a shit, i had to confiscate my sons POS pc. A build now takes nearly 16hrs + with a fresh build. I know it sucks, thats really my main reason for not releasing as often.
 
Upvote 0
@Ph0enix_216 and @adamhos1234 do either of you have volt with borkd cam?
If so, I need you to test my semi-latest build. I have cam working on both of my volts (boost & virgin)
Virgin always worked, boost was always the problem here. but working now.
I do have a borked camera (I'm on Virgin) I'm willing to try anything to get it to work.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones