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

Root {MS323} Cyanogenmod Development thread.

Who actually building CM12? And what your progress?
CM11 source can be reconfigured to work with CM12. @chevanlol360 has already been able to build and boot CM12 (I haven't had proof from him, but I trust him and I believe him.) He has not uploaded any builds nor source for it, he probably will upload source one day when he's not feeling lazy :D
 
CM11 source can be reconfigured to work with CM12. @chevanlol360 has already been able to build and boot CM12 (I haven't had proof from him, but I trust him and I believe him.) He has not uploaded any builds nor source for it, he probably will upload source one day when he's not feeling lazy :D
I dont know how can be configured to CM12 :D
Yes i read this ;) I trust him too :P
 
Wow... That's... Wow.... Would like... 95 GB of free space be able to be enough to build? I know that I need ~50 for ccache... If that's the case (with being enough space and the bugs) I'll build CM12 right now
Theoretically yes.
From source.android.com:
  • 30GB of free disk space to complete a single build and up to 100GB or more for a full set of builds. The source download is approximately 8.5GB in size.
 
I found an alternative for the menu button that doesn't work right. I downloaded Easy Touch (Holo Style) from Google Play Store and in the second screen option it has a menu button setting. I can even use it inside any app with the option to turn off if I like. Just thought I would share.
 
Only things that need fixed:
Menu button--nevermind, fixed this.
Back camera
Camera flash
Torch
Over all, this is a great ROM. Once these things are fixed, it should be submitted to CyanogenMod devs as a stable build.
 
Last edited:
Can CM-11 trees be used to build CM-12 and if not does anyone have advice on how to convert them? Also I am missing a few CM-12 trees. According to VM03's local manifest.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/w3ds" name="vm03/android_device_lge_w3ds" remote="github" revision="cm-12.0" />
<project path="device/lge/w5ds" name="vm03/android_device_lge_w5ds" remote="github" revision="cm-12.0" />
<project path="device/lge/msm8610-common" name="vm03/android_device_lge_msm8610-common" remote="github" revision="cm-12.0" />
<project path="kernel/lge/msm8610" name="vm03/android_kernel_lge_msm8610" remote="github" revision="cm-12.0" />
<project path="vendor/lge/msm8610" name="vm03/proprietary_vendor_lge_msm8610" remote="github" revision="cm-12.0" />
<project path="hardware/qcom/display-caf-new" name="CyanogenMod/android_hardware_qcom_display-caf-new" revision="cm-12.0" />
<project path="hardware/qcom/media-caf-new" name="CyanogenMod/android_hardware_qcom_media-caf-new" revision="cm-12.0" />
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" revision="cm-12.0" />
<project path="hardware/qcom/fm" name="CyanogenMod/android_hardware_qcom_fm" revision="cm-12.0" />
</manifest>
android_device_lge_w3ds only cm-11 branch
android_hardware_qcom_display-caf-new only cm-11 branch
android_hardware_qcom_media-caf-new only cm-11
android_device_qcom_common https://github.com/CyanogenMod/android_device_qcom_common/tree/staging/cm-12.0-caf
Looks like a lot of Qualcomm props are only cm-11?
 
Can CM-11 trees be used to build CM-12 and if not does anyone have advice on how to convert them? Also I am missing a few CM-12 trees. According to VM03's local manifest.

android_device_lge_w3ds only cm-11 branch
android_hardware_qcom_display-caf-new only cm-11 branch
android_hardware_qcom_media-caf-new only cm-11
android_device_qcom_common https://github.com/CyanogenMod/android_device_qcom_common/tree/staging/cm-12.0-caf
Looks like a lot of Qualcomm props are only cm-11?
Yes, the CM11 tree has been modified. If you follow what chevan said, you can build CM12. I am currently syncing the source and will post my build after a bit of testing. Hopfully CM12 before end of the week!
 
Err wait... Was that even on here? Oh well, here's what he told me to be able to run to get source and ready to build for CM2:

repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0

curl --create-dirs -L -o .repo/local_manifests/local_manifest.xml -O -L https://raw.githubusercontent.com/chevanlol360/android_local_manifest/master/local_manifest.xml

repo sync
vendor/cm/get-prebuilts
I'm talking porting the cm11 tree for cm12. Starting with qcom blobs.
 
Err wait... Was that even on here? Oh well, here's what he told me to be able to run to get source and ready to build for CM2:

repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0

curl --create-dirs -L -o .repo/local_manifests/local_manifest.xml -O -L https://raw.githubusercontent.com/chevanlol360/android_local_manifest/master/local_manifest.xml

repo sync
vendor/cm/get-prebuilts
I'm talking porting the cm11 tree for cm12. Starting with qcom blobs.
 
Only things that need fixed:
Menu button--nevermind, fixed this.
Back camera
Camera flash
Torch
Over all, this is a great ROM. Once these things are fixed, it should be submitted to CyanogenMod devs as a stable build.
I'm guessing this could be solved but I'm kinda new at this. I think we need a different kernel or the w5ds a small has difference. At least GPS works.
 
I'm guessing this could be solved but I'm kinda new at this. I think we need a different kernel or the w5ds a small has difference. At least GPS works.
The accelerometer is a bit messy. I'm going to try to start compiling jellybean for the device. My original goal was to play need for speed most wanted.
 
I'm guessing this could be solved but I'm kinda new at this. I think we need a different kernel or the w5ds a small has difference. At least GPS works.
The accelerometer is a bit messy. I'm going to try to start compiling jellybean for the device. My original goal was to play need for speed most wanted.
 
If you compile jellybean, do you think that might fix the GPS and camera? Or do you think its the kernel on cm11?
 
Back
Top Bottom