Develop Bugs

Compiling CM 10.1 toro?

Hi, I was trying to compile CM 10.1 for toro and was following this guide http://wiki.cyanogenmod.org/w/Build_for_toro
I couldn't find extract-files.sh so I skipped it and used the blobs from https://developers.google.com/android/nexus/drivers#toro
It compiles all the way through and generates a zip file but it just causes a blank screen when it tries to boot.
Does anybody know where I can find extract-files.sh? I did repo sync a few times and even deleted my entire directory and started over. It never shows up in the directory stated in the guide.
I'm also using ubuntu 12.04

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Have you completed every step successfully before you are supposed to execute the extract-files.sh?
Also: which java version and toolchain do you use for compiling?

tbguy said:
Hi, I was trying to compile CM 10.1 for toro and was following this guide http://wiki.cyanogenmod.org/w/Build_for_toro
I couldn't find extract-files.sh so I skipped it and used the blobs from https://developers.google.com/android/nexus/drivers#toro
It compiles all the way through and generates a zip file but it just causes a blank screen when it tries to boot.
Does anybody know where I can find extract-files.sh? I did repo sync a few times and even deleted my entire directory and started over. It never shows up in the directory stated in the guide.
I'm also using ubuntu 12.04
Click to expand...
Click to collapse
you can get blob here: https://github.com/TheMuppets/proprietary_vendor_samsung

hiepgia said:
you can get blob here: https://github.com/TheMuppets/proprietary_vendor_samsung
Click to expand...
Click to collapse
If it still fails after that, just get the google android NDK and use the provided 4.6 toolchain. Also, do not use Java 7 for compiling, use Java 6 instead (oracle Java always worked good for me, dunno about openJDK).

BUMP, having the same problem with the blank screen after building. No problems with completing the guide. Everything is as it should be
just get the blank screen after the google splash.....

MaceBewley said:
BUMP, having the same problem with the blank screen after building. No problems with completing the guide. Everything is as it should be
just get the blank screen after the google splash.....
Click to expand...
Click to collapse
What Java and GCC toolchain are you using?

Java 6, not sure about the toolchain. Kinda of frustrating cause my grouper builds boot fine...

I'm also using Java 6. And when I enter "gcc --version", I get 4.6.3
I tried using the blobs from the link above and still getting the same black screen.
I had also tried manually running generate-blob-lists.sh in devices/common. it took forever but it created extract-files.sh. It didn't even compile after that so I deleted my source directory again and used the blobs from hiepgia's link.

lunch a eng build, then LOGCAT! You'll know why it's bootlooping. And you know you need to run extract-files.sh from a toro running CM right? 'make clobber', then brunch.
Sent from my Nexus

Looking at the source tree at github, I see an extract-files.sh for maguro, but, no such file exists in the toro branch.
https://github.com/CyanogenMod/android_device_samsung_maguro/tree/cm-10.1
https://github.com/CyanogenMod/android_device_samsung_toro/tree/cm-10.1
After my repo sync finishes I'm going to go thru the steps again, if there is still no extract-files.sh (which I'm sure will be the case, unless it get's generated somehow), I'll try copying the maguro one in (with requisite changes)...

crpeck said:
Looking at the source tree at github, I see an extract-files.sh for maguro, but, no such file exists in the toro branch.
*snip*
Click to expand...
Click to collapse
I assume it doesn't exist due to toro officially not being able to be above 4.1.1 with OTAs. Making CM10 and CM10.1 problematic with the older binaries...etc people potentially would be pulling from their device with the script.
https://github.com/TheMuppets <-- as mentioned previously that is what I use to get the proprietary stuff for my toro. You can make a local_manifest.xml in your .repo directory, then a repo sync with download them all for you.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="http://github.com/" name="gh" revision="master" />
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_toro" path="device/samsung/toro" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" revision="cm-10.1" />
</manifest>

OH sweet - sorry I missed that before... Very nice fix..

[Q] D850 CM12 Local Manifest

I am trying to compile CM12 on my own for the D850 and I am curious what people are using for the Local Manifest file. I found one thread talking about building CM12 for the LG G3, but it seemed to be for the D855 and it seemed like it might be using 3rd party sources on Github.
So I'm trying to find out what the full local manifest should be for my D850 CM12 build. I am a compile noob, so being able to tell me/show me what the full manifest file should contain would be greatly appreciated. Also, if you could tell/show me how you found out this information, so I can figure it out for myself in the future, that would be awesome

I found this on the CM website - http://wiki.cyanogenmod.org/w/Local_manifest
It tells me to grab this file on the LG G3 that I have CM12 on already "/system/etc/build-manifest.xml", but when I look at that file, it has HUGE. the local_manifest.xml file for the N5 that I'm building only has like 3-4 entries.
Is this huge file really the local_manifest that I need to use to build CM12 for the D850 LG G3?

Here's mine (edited for you), cyanogenmod doesnt seem to have "proprietary_vendor_lge", so i left it how I have mine.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/g3-common" name=CyanogenMod/android_device_lge_g3-common" remote="github" revision="cm-12.0" />
<project path="device/lge/d850" name="CyanogenMod/android_device_lge_d850" remote="github" revision="cm-12.0" />
<project path="kernel/lge/g3" name="CyanogenMod/android_kernel_lge_g3" remote="github" revision="cm-12.0" />
[B]<project path="vendor/lge" name="ResurrectionRemix/proprietary_vendor_lge" remote="github" revision="lollipop" />[/B]
<project path="device/qcom_common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.0" />
</manifest>

Thank you for the response. I did just find this in CM's github
- https://github.com/CyanogenMod/android_device_lge_g3-common
and this
- https://github.com/CyanogenMod/android_kernel_lge_g3

rhystagram said:
Here's mine (edited for you), cyanogenmod doesnt seem to have "proprietary_vendor_lge", so i left it how I have mine.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/g3-common" name=CyanogenMod/android_device_lge_g3-common" remote="github" revision="cm-12.0" />
<project path="device/lge/d850" name="CyanogenMod/android_device_lge_d850" remote="github" revision="cm-12.0" />
<project path="kernel/lge/g3" name="CyanogenMod/android_kernel_lge_g3" remote="github" revision="cm-12.0" />
[B]<project path="vendor/lge" name="ResurrectionRemix/proprietary_vendor_lge" remote="github" revision="lollipop" />[/B]
<project path="device/qcom_common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.0" />
</manifest>
Click to expand...
Click to collapse
Very awesome. Thank you for your help. Is there anything wrong/bad about using Resurrection's proprietary vendor one for my vanilla CM12 build for the d850?
I've seen someone using this one. . .
<project path="vendor/lge" name="sooti/proprietary_vendor_lge" remote="github" revision="cm-12.0" />
but it was for the D855. I don't know if these will mess up my build since I'm compiling for the D850 instead.
Again, thank you for the help. It is greatly appreciated.

view step 3 here, it has the local_manifest details, they're from sooti, which was before CM official builds..
maybe use his vendor, but official cm repostories for others.
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
just noticed you replied, pretty sure as long as you have the d850 files, and run the "brunch d850" the vendor will still run correctly, as it's a vendor for LGE.

rhystagram said:
view step 3 here, it has the local_manifest details, they're from sooti, which was before CM official builds..
maybe use his vendor, but official cm repostories for others.
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
just noticed you replied, pretty sure as long as you have the d850 files, and run the "brunch d850" the vendor will still run correctly, as it's a vendor for LGE.
Click to expand...
Click to collapse
Awesome. Thank you again, sooooo very much. It's running a repo sync now :fingers-crossed:
I'm used to running "time brunch <codename>"
is that the same as the "brunch <codename>" that you just suggested? I'm not sure what the difference between time brunch and just brunch

Enddo said:
Awesome. Thank you again, sooooo very much. It's running a repo sync now :fingers-crossed:
I'm used to running "time brunch <codename>"
is that the same as the "brunch <codename>" that you just suggested? I'm not sure what the difference between time brunch and just brunch
Click to expand...
Click to collapse
time brunch shows you how long it takes to build (i think), brunch just builds .

rhystagram said:
time brunch shows you how long it takes to build (i think), brunch just builds .
Click to expand...
Click to collapse
Well, it all seemed to work but then I got an error toward the end
Code:
/bin/sh: 1: lz4c: not found
make[4]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/doug/lgg3/kernel/lge/g3'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
real 52m2.413s
user 204m32.365s
sys 21m4.082s
I found a thread talking about that error and someone suggested to do a sudo apt-get install lzop, but it says I already have that
Code:
sudo apt-get install lzop
[sudo] password for doug:
Reading package lists... Done
Building dependency tree
Reading state information... Done
lzop is already the newest version.
The following packages were automatically installed and are no longer required:
libgpds0 linux-headers-3.13.0-32 linux-headers-3.13.0-32-generic
linux-headers-generic linux-image-3.13.0-32-generic
linux-image-extra-3.13.0-32-generic linux-image-generic python-pyudev
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Found a suggestion to run "sudo apt-get install liblz4-tool", I installed that and am trying the process over again

Enddo said:
Well, it all seemed to work but then I got an error toward the end
Code:
/bin/sh: 1: lz4c: not found
make[4]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/doug/lgg3/kernel/lge/g3'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
real 52m2.413s
user 204m32.365s
sys 21m4.082s
Click to expand...
Click to collapse
can't help here man, it's happened to me, only solution i found to fix it for me was to make a new directory & download all sources again & build from there. (didn't try the solution you are, let me know how it goes?)

rhystagram said:
can't help here man, it's happened to me, only solution i found to fix it for me was to make a new directory & download all sources again & build from there. (didn't try the solution you are, let me know how it goes?)
Click to expand...
Click to collapse
After doing a "sudo apt-get install liblz4-tool", I did the whole compile process over, didn't even do a make clean(but I might if there is something wrong with the flash), and it seemed to compile perfectly.
I had to let it run while I was sleeping so I didn't get a chance to flash it yet. Do you know if these are already 'bumped', or if I have to do something special to them now that they have been compiled? I'm almost certain the CM repos have the Bump code in them, but I just wanted to double check in case anyone else knows for sure
and thank you again for all the help. I just have no idea how to get the local manifest information for these builds. I've had help with both the N5 and now the G3. I would love to know how to figure out this on my own so I don't have to keep bothering the community
Do you know how to do this? How to know when you have enough items in the manifest and where to get them. It seems like most come from CM but on both the G3 and the N5, there's one that comes from somewhere else.
Like with the N5, it was the proprietary one that came from somewhere else
"<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.0"/>"

I just flashed it and it worked perfectly! Well, I had a force close error on a google app, so I uninstalled the updates, and updated it from Google Play and it launched. This was probably something to do with the dirty flash more than the compile
Thanks again @rhystagram !
I couldn't be more grateful

image is bumped yes
Target boot image: /home/rhys/newrr/out/target/product/d855/boot.img
/home/rhys/newrr/out/target/product/d855/boot.img maxsize=17031168 blocksize=135168 total=7329792 reserve=270336
bumped image: /home/rhys/newrr/out/target/product/d855/boot.img
Made boot image: /home/rhys/newrr/out/target/product/d855/boot.img
glad i could help & glad you got it working!!

roomservice.xml for Nexus 5 (bullhead)?

hi, i'm requesting devs who build cm 13 for bullhead to kindly share their roomservice.xml. i'm trying to build cm from source and the system generated roomservice.xml is as follows:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_bullhead" path="device/lge/bullhead" remote="github" />
<project name="CyanogenMod/android_kernel_lge_bullhead" path="kernel/lge/bullhead" remote="github" />
</manifest>
i think this does not contain bolbs, which are also required for building from source. i tried building without them and i get the following error:
Code:
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/home/gururoop/android/cm13/out/target/product/bullhead/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/LINKED/libsurfaceflinger.so] Error 1
make: Leaving directory `/home/gururoop/android/cm13'
Can anyone help me with these errors?

gururoop said:
hi, i'm requesting devs who build cm 13 for bullhead to kindly share their roomservice.xml. i'm trying to build cm from source and the system generated roomservice.xml is as follows:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_bullhead" path="device/lge/bullhead" remote="github" />
<project name="CyanogenMod/android_kernel_lge_bullhead" path="kernel/lge/bullhead" remote="github" />
</manifest>
i think this does not contain bolbs, which are also required for building from source. i tried building without them and i get the following error:
Code:
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/home/gururoop/android/cm13/out/target/product/bullhead/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/LINKED/libsurfaceflinger.so] Error 1
make: Leaving directory `/home/gururoop/android/cm13'
Can anyone help me with these errors?
Click to expand...
Click to collapse
Vendor files? https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-13.0
I know the vendor stuff is different from everything else I've used/built for and I only had to "brunch bullhead" to build a different rom I tried.

Keithn said:
Vendor files? https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-13.0
I know the vendor stuff is different from everything else I've used/built for and I only had to "brunch bullhead" to build a different rom I tried.
Click to expand...
Click to collapse
did you extract blobs using extract-files.sh script? can you please share the roomservice.xml of the ROM that built successfully and booted?

gururoop said:
did you extract blobs using extract-files.sh script? can you please share the roomservice.xml of the ROM that built successfully and booted?
Click to expand...
Click to collapse
Nope I never had to do it that way and I usually just add the vendor files from the muppets git (linked above) instead.
What commands are you using to build?
Try just using ". build/envsetup.sh" then use "brunch bullhead". Downloaded everything I needed to build omni last I tried. My server/PC I use for building isn't connected or running right now so I can't directly pull the XML I used. I probably could later though.
Another thing is that you can add your own XML into the local manifests to sync files so you don't have to touch the room service.XML. Here is one I was using for an example https://github.com/Keith-N/local_manifests/blob/master/local_manifests.xml

Keithn said:
Nope I never had to do it that way and I usually just add the vendor files from the muppets git (linked above) instead.
What commands are you using to build?
Try just using ". build/envsetup.sh" then use "brunch bullhead". Downloaded everything I needed to build omni last I tried. My server/PC I use for building isn't connected or running right now so I can't directly pull the XML I used. I probably could later though.
Another thing is that you can add your own XML into the local manifests to sync files so you don't have to touch the room service.XML. Here is one I was using for an example https://github.com/Keith-N/local_manifests/blob/master/local_manifests.xml
Click to expand...
Click to collapse
I would really appreciate if you could share your roomservice.xml whenever possible. I did try to give commands as per your post and got the error mentioned in the OP. I'm trying to start with building CM and expand the base if I succeed.

I tried it out and it's missing the vendor files. You'll notice no vendor/lge in your cm13 directory. The way I talked about in the previous post will work. You need to get those vendor files. I could give you my roomservice.xml but it shouldn't look any different because I never touched it. I used an addition xml to add aditional files which is why my roomservice.xml was never changed. The easy way is to add this line into whatever xml you are planning on using to sync the files.
Code:
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0" />
It grabs the files from https://github.com/TheMuppets/proprietary_vendor_lge and syncs them into vendor/lge
If you have troubles then let me know, but that is all I needed to do.

[dev] CyanogenMod Bringup

I have made some decent progress on bringing up CM 12.1 on the KIW-L24. If you are able to help and willing to do so, please build off of these three repos:
* https://github.com/crpalmer/android_device_huawei_kiwi
* https://github.com/crpalmer/android_kernel_huawei_kiwi
* https://github.com/crpalmer/proprietary_vendor_huawei using branch kiwi-12.1
and repopick the topic "kiwi_12.1_bringup".
Then submit any fixes you can make via pull requests.
Edit:: Well, that is now officially outdated... The repos have been imported into the CyanogenMod github (this makes it easier to collaborate). You should now submit changes via gerrit and not via pull requests.
The current status is that it boots, runs just fine and telephony / mobile data is working (for sim 1, I haven't tested sim2). Bluetooth may work. Everything else should be assumed to be broken (at least not tested). In particular, that includes wifi, audio, gps, camera and sensors.
But getting a first boot is a major step forward and then getting telephony working was another big step. It's now at a point where it is easy enough to colloborate if there is anyone out that with the skills and time to help out.
And, no, I am not posting builds right now and, no, I don't need people as testers at this time.

Wow you're awesome. Good luck with everything. I'll be looking forward to this.
Sent from my KIW-L24 using Tapatalk

It's awesome that you got it to boot and that you have ril working. Planning on getting this phone when there is an AOSP ROM for it. Currently using a $10 Verizon Moto E LTE on T-Mobile.

I'm syncing the code today, I was downloading the angler code as reference yesterday, but it's good to know that I'm not the only one willing to bring CM to this device

I wish I knew how to help, alas I don't. But you sir, I take my hat off to you and wish you the best!

crpalmer said:
I have made some decent progress on bringing up CM 12.1 on the KIW-L24. If you are able to help and willing to do so, please build off of these three repos:
* https://github.com/crpalmer/android_device_huawei_kiwi
* https://github.com/crpalmer/android_kernel_huawei_kiwi
* https://github.com/crpalmer/proprietary_vendor_huawei using branch kiwi-12.1
and repopick the topic "kiwi_12.1_bringup". . .
Click to expand...
Click to collapse
First, thanks for you work on this!
Second, how should I go about building this? I've setup my roomservice like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="crpalmer/android_device_huawei_kiwi" path="device/huawei/kiwi" revision="cm-12.1" remote="github" />
<project name="crpalmer/android_kernel_huawei_kiwi" path="kernal/huawei/kiwi" revision="cm-12.1" remote="github" />
<project name="Huawei-Kiwi/android_kernel_huawei_msm8939" path="kernel/huawei/msm8939" revision="Huawei" remote="github" />
<project name="crpalmer/proprietary_vendor_huawei" path="vendor/huawei/kiwi" revision="kiwi-12.1" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" />
</manifest>
(I repo synced) but I can't get it to "lunch cm_kiwi-userdebug". Is there something else I need to do to build this?
and repopick the topic "kiwi_12.1_bringup". . .
Click to expand...
Click to collapse
Is that something I need to do to build this, or just to commit my changes? I don't know how to repopick.
Sorry for the noob questions, but I'd appreciate any help.

I am not a developer, but I work for Huawei. Let me know if there are any specific requests for information or resources that I can help out with.

Thanx for all the work.... you're awesome
Ps. Plz don't miss out the L21 ver
Sent from my KIW-L21 using Tapatalk

Cool to see boot.....Imma look over some things and see what i see as well....

Good morning, I also would like to say good work so far on this, and I too am not sure if I got things set up right. I repo synceed CM12.1 for Cherry, then replaced the device, vendor and kernel folders with your kiwi repos, then made sure qcom_common and _sepolicy were the latest.
The only repopick topic commit I see on Gerrit is "libcutils: Add huawei logging symbol". I added that in manually. Are there more commits under that topic? And is Gerrit the place to find those?
My build hangs up with this error: <device/qcom/sepolicy/common/mpdecision.te:42:ERROR 'unknown type sysfs_devices_system_iosched' at token ';' on line 14532:>
I added a commit from Slim that supposedly dealt with this error (https://github.com/SlimSaber/vendor_...ae52d3d3391500), but that didn't help.
Any advice or tips would be awesome.
Thanks again

wimbet said:
I am not a developer, but I work for Huawei. Let me know if there are any specific requests for information or resources that I can help out with.
Click to expand...
Click to collapse
You could mention that the kernel source which was released was either not the source for the kiw-l24 launch or was incomplete. It did not contain the DTB files for any of the kiw-l24 devices. It would be nice if future releases were complete and up-to-date...

Bandit Development said:
First, thanks for you work on this!
Second, how should I go about building this? I've setup my roomservice like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="crpalmer/android_device_huawei_kiwi" path="device/huawei/kiwi" revision="cm-12.1" remote="github" />
<project name="crpalmer/android_kernel_huawei_kiwi" path="kernal/huawei/kiwi" revision="cm-12.1" remote="github" />
<project name="Huawei-Kiwi/android_kernel_huawei_msm8939" path="kernel/huawei/msm8939" revision="Huawei" remote="github" />
<project name="crpalmer/proprietary_vendor_huawei" path="vendor/huawei/kiwi" revision="kiwi-12.1" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" />
</manifest>
(I repo synced) but I can't get it to "lunch cm_kiwi-userdebug". Is there something else I need to do to build this?
Is that something I need to do to build this, or just to commit my changes? I don't know how to repopick.
Sorry for the noob questions, but I'd appreciate any help.
Click to expand...
Click to collapse
If you sync'ed the repos and lunch is failing, it will give you an error. You'll have to figure out what error you are getting and what you need to do to fix it.

crpalmer said:
You could mention that the kernel source which was released was either not the source for the kiw-l24 launch or was incomplete. It did not contain the DTB files for any of the kiw-l24 devices. It would be nice if future releases were complete and up-to-date...
Click to expand...
Click to collapse
Noted, I just sent this request to the dev team. They just released a new build B140 for KIW-L24, so I can request they update the kernel source.

crpalmer said:
If you sync'ed the repos and lunch is failing, it will give you an error. You'll have to figure out what error you are getting and what you need to do to fix it.
Click to expand...
Click to collapse
The error:
Code:
[email protected]:~/android/system$ lunch cm_kiwi-userdebug
Looking for dependencies
Traceback (most recent call last):
File "build/tools/roomservice.py", line 237, in <module>
fetch_dependencies(repo_path)
File "build/tools/roomservice.py", line 208, in fetch_dependencies
dependencies = json.loads(dependencies_file.read())
File "/usr/lib/python2.7/json/__init__.py", line 338, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
obj, end = self.scan_once(s, idx)
ValueError: Expecting , delimiter: line 4 column 5 (char 57)
** Don't have a product spec for: 'cm_kiwi'
** Do you have the right repo manifest?
I thought the error was that the lunch combo "cm_kiwi" was not available, but I guess that's not the case? Maybe it's failing because of "ValueError: Expecting , delimiter: line 4 column 5 (char 57)"?
Anyway, I don't want to bother you, just curious if you had a quick suggestion. Thanks

Bandit Development said:
The error:
Code:
[email protected]:~/android/system$ lunch cm_kiwi-userdebug
Looking for dependencies
Traceback (most recent call last):
File "build/tools/roomservice.py", line 237, in <module>
fetch_dependencies(repo_path)
File "build/tools/roomservice.py", line 208, in fetch_dependencies
dependencies = json.loads(dependencies_file.read())
File "/usr/lib/python2.7/json/__init__.py", line 338, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
obj, end = self.scan_once(s, idx)
ValueError: Expecting , delimiter: line 4 column 5 (char 57)
** Don't have a product spec for: 'cm_kiwi'
** Do you have the right repo manifest?
I thought the error was that the lunch combo "cm_kiwi" was not available, but I guess that's not the case? Maybe it's failing because of "ValueError: Expecting , delimiter: line 4 column 5 (char 57)"?
Anyway, I don't want to bother you, just curious if you had a quick suggestion. Thanks
Click to expand...
Click to collapse
That's my mistake. Try a repo sync and then lunch again.

CM would really make the H5X fly!

Well, this is now officially outdated... The repos have been imported into the CyanogenMod github (this makes it easier to collaborate). You should now submit changes via gerrit and not via pull requests.

Are you guys planning on adding official support for the L-21 and L-22 variants? They are quite similar barring the antenna bands if I'm not wrong.
I have the L-22 variant. Tell me if you require any sort of testing/info.
BTW, nice seeing you here, @crpalmer.

crpalmer said:
You could mention that the kernel source which was released was either not the source for the kiw-l24 launch or was incomplete. It did not contain the DTB files for any of the kiw-l24 devices. It would be nice if future releases were complete and up-to-date...
Click to expand...
Click to collapse
wimbet said:
I am not a developer, but I work for Huawei. Let me know if there are any specific requests for information or resources that I can help out with.
Click to expand...
Click to collapse
Hah, it seems to be a Huawei company policy to release incomplete source codes.
After two months of sending emails to Huawei someone finally replied and Huawei took another try at releasing source code for Huawei Y5 (Y560-L01&L02&L03&L23) yesterday. Unfortunately it's the same exact incomplete source code they had already released. Still missing ft5x36 touchscreen driver. Still missing some dtsi to compile dt.img. Still missing Huawei's USB modification. Still missing any modification Huawei has done to any Makefile/Kconfig...
@wimbet
Maybe you could use your contacts to move this thing forward? We already discussed this about a month ago, remember?

Discussion Thread
I have created a thread for non-development-related and off topic discussion.
Keep this dev thread clutter free.
http://forum.xda-developers.com/honor-5x/how-to/discussion-honor-5x-cyanogenmod-t3324177

Help building LineageOS 16.0

Hi, I'm trying to build LOS 16.0 for the kltedv but it keeps crashing (error message at the end of post).
These are the steps I'm taking on Ubuntu.
Code:
repo init -u git://github.com/LineageOS/android.git -b lineage-16.0
Code:
repo sync --force-sync --no-clone-bundle --no-tags
Code:
cd .repo && mkdir local_manifests && cd local* && subl roomservice.xml
In roomservice.xml, I have
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="platform/prebuilts/qemu-kernel" />
<project name="knaik95/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_kltedv" path="device/samsung/kltevzw" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_samsung_klte-common" path="device/samsung/klte-common" remote="github" revision="lineage-16.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="lineage-16.0"/>
<project name="LineageOS/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" revision="lineage-16.0"/>
</manifest>
Code:
repo sync
Code:
source build/envsetup.sh
Code:
add_lunch_combo lineage_kltedv-userdebug
Code:
breakfast kltedv
And this is where it says
Code:
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_kltedv".
Has something changed in the build process from the upgrade from 15.1 to 16.0?

Same here. I am trying to build LOS16 for my moto device. Device tree builds fine with LOS 15.1. But fails for LOS 16. Error is same "build/make/core/product_config.mk:234: error: Can not locate config makefile for product". @knaik95, were you able to get pass this situation? Please update.
Thanks
KS

kalyansundhar said:
Same here. I am trying to build LOS16 for my moto device. Device tree builds fine with LOS 15.1. But fails for LOS 16. Error is same "build/make/core/product_config.mk:234: error: Can not locate config makefile for product". @knaik95, were you able to get pass this situation? Please update.
Thanks
KS
Click to expand...
Click to collapse
Defining AndroidProducts.mk in device tree resolved the problem.
Thanks
KS

kalyansundhar said:
Defining AndroidProducts.mk in device tree resolved the problem.
Thanks
KS
Click to expand...
Click to collapse
Yep. I also renamed lineage.mk to lineage_[device name].mk just to be safe. Did you get any farther? I was met with a bunch of missing dependencies after that. The first one was gradle-plugin, which I fixed by git cloning from the official aosp site, but the others I'm not sure how to get past.

knaik95 said:
Yep. I also renamed lineage.mk to lineage_[device name].mk just to be safe. Did you get any farther? I was met with a bunch of missing dependencies after that. The first one was gradle-plugin, which I fixed by git cloning from the official aosp site, but the others I'm not sure how to get past.
Click to expand...
Click to collapse
I didn't face any further issues so far. But I have to wait and watch.
Thanks
KS
Sent from my Moto G5s using Tapatalk

Can you explain that.. in that detail please
kalyansundhar said:
Defining AndroidProducts.mk in device tree resolved the problem.
Thanks
KS
Click to expand...
Click to collapse
there is a file exist in device tree AndroidProduct.mk

I wish you success @knaik95 with your build.
I do recall flashing your RR Oreo builds and they were awesome!!

pmduper said:
I wish you success @knaik95 with your build.
I do recall flashing your RR Oreo builds and they were awesome!!
Click to expand...
Click to collapse
Oh, uh.... yeah I figured out what I was doing a while ago. I've built and tested LiquidRemix based on Android Pie a couple times; I was satisfied with the result. Not a daily driver yet because we're atm without Xposed SDK28 so still on RR Oreo :silly:

knaik95 said:
Oh, uh.... yeah I figured out what I was doing a while ago. I've built and tested LiquidRemix based on Android Pie a couple times; I was satisfied with the result. Not a daily driver yet because we're atm without Xposed SDK28 so still on RR Oreo :silly:
Click to expand...
Click to collapse
Best of luck with your project.
I've been using a variety of Pie builds for the past couple of months. :good:

pmduper said:
Best of luck with your project.
I've been using a variety of Pie builds for the past couple of months. :good:
Click to expand...
Click to collapse
If you wanna give LiquidRemix a try, I can try to post a link. It was daily driver back when the Galaxy S3 was still relevant and the ROM was called LiquidSmooth. I haven't done a thorough examination of features and what not, but I'd say Liquid rivals the customizability of RR.

redacted