Related
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..
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!!
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
Hello,
I am trying to build CM13 for h815 myself, following the instructions from the CyanogenMod wiki.
When I execute brunch h815, after some time the build breaks with the message
make: *** No rule to make target 'vendor/lge/g4-common/proprietary/vendor/lib/libTimeService.so', needed by '~/android/system/out/target/product/h815/obj_arm/SHARED_LIBRARIES/libTimeService_intermediates/LINKED/libTimeService.so'. Stop.
Click to expand...
Click to collapse
I know that libTimeService was in the proprietary files list in CM12, but was removed in CM13 and is also not present on my device (I searched in each lib and lib64 folder I was able to find on the device running CM13).
Is there some option to disable libraries dependend on libTimeService being built or do I forget some other step? Obviously, it must be possible to build for h815 from source as there are nightly builds for the device, so I think there is some configuration missing on my machine, but I don't see which.
Kind regards
spainer
Did no one else have a similar problem when building for H815 yourself? Do you all have the library on your phone?
I would also be thankful for tips where to start trying to solve the problems or which components could be related to this...
you need to sync the proprietary files in vendor/lge
https://github.com/TheMuppets/proprietary_vendor_lge
This worked, thank you very much.
So, if I see it right, the build instructions in the CyanogenMod wiki are wrong I the section to extract the proprietary blobs. Instead of executing ./extract_files.sh in ~/android/system/device/lge/h815, one should
1. create a local manifest to sync vendor/lge to the repository given above and
2. execute repo sync.
When you confirm this fix for the build instructions, I can change the CyanogenMod wiki, so that others can benefit from your solution...
spainer said:
This worked, thank you very much.
When you confirm this fix for the build instructions, I can change the CyanogenMod wiki, so that others can benefit from your solution...
Click to expand...
Click to collapse
Works for me apparently. As as newbie, it's not obvious how to create the local manifest.
I went with this
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github />
</manifest>
in ".repo/local_manifests/mine.xml", leaving "roomservice.xml" alone. Not sure if that one would
be needed still.
Yours,
Kay
kayhayen said:
Works for me apparently. As as newbie, it's not obvious how to create the local manifest.
I went with this
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github />
</manifest>
in ".repo/local_manifests/mine.xml", leaving "roomservice.xml" alone. Not sure if that one would
be needed still.
Yours,
Kay
Click to expand...
Click to collapse
I ran into the same problem. I'm going to try your solution and see what happens. BTW I noticed your code has a couple of typos. This should work:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>
Thanks
---------- Post added at 08:32 AM ---------- Previous post was at 08:30 AM ----------
Also, does this mean we should throw out the proprietary blobs if we've already extracted them?
Got a successful build, gonna test it soon.
Hi all,
I have been trying to boot LineageOS 15 on the One M9 as I think they have it booting on the M8.
By searching through github and looking at the M8 changes, I have managed to pull a bunch of trees together and complete a build, but it does not boot. It does not get past the bootloader to even get to the boot animation.
The roomservice.xml I am using is shown below:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_htc_himaul" path="device/htc/himaul" remote="github" revision="cm-14.1" />
<project name="me2151/android_device_htc_hima-common" path="device/htc/hima-common" remote="github" revision="lineage-15.0" />
<project name="me2151/android_kernel_htc_msm8994" path="kernel/htc/msm8994" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-15.0" />
</manifest>
And I've had to change the .repo/manifest.xml a bit to include these revisions:
Code:
<project path="hardware/qcom/audio/default" name="LineageOS/android_hardware_qcom_audio" groups="qcom,qcom_audio,pdk" revision="lineage-15.0-caf-8994" />
<project path="hardware/qcom/display" name="LineageOS/android_hardware_qcom_display" groups="pdk,qcom,qcom_display" revision="lineage-15.0-caf-8994" />
<project path="hardware/qcom/media" name="LineageOS/android_hardware_qcom_media" groups="qcom,pdk" revision="lineage-15.0-caf-8994" />
I've also had to change a bunch of /vendor/cm/ to /vendor/lineage as said in this post. I might have changed some other things (I seem to remember there was an issue in framework/core/res/res/values.xml or something where some strings relating to rebooting weren't defined ...)
Anyway, any ideas as to how to proceed? None of the logs are showing any kernel activity, only when it boots into the bootloader do I get any kind of logs. I've gone through all the logs in /devlog and there's nothing =[
EDIT:
This build is currently bootlooping, but adb is working. The guide of how I got this far is in this post.
EDIT2:
This rom is currently booting, but camera is broken, selinux is in permissive, and there's probably a load of errors floating around in adb that I don't really have time to solve =[ The link for this build for LineageOS 15.0 GSM/himaul is in THIS POST.
Maybe you can post a link to the source? or the build?
lucyr03 said:
Maybe you can post a link to the source? or the build?
Click to expand...
Click to collapse
Yay, a reply!
So the sources I'm using are:
/me2151/android_device_htc_hima-common
/me2151/android_kernel_htc_msm8994
/TheMuppets/proprietary_vendor_htc
Then the normal LineageOS 15 sources, except the -caf-8994 ones for qcom_media, qcom_display, and qcom_audio.
I've noticed the generated boot.img is ~10mb smaller than the one I built from the LineageOS 14.1 sources. I'm thinking this might be the problem, but I don't hugely know where to go next. I unmkbootimg'd the boot.img, and the ramdisks are around the same size as in LOS 14.1 , but the zImage's are very different. I can upload the build if you want, but it doesn't boot or even boot the kernel in normal mode to log anything.
xangma said:
Yay, a reply!
So the sources I'm using are:
/me2151/android_device_htc_hima-common
/me2151/android_kernel_htc_msm8994
/TheMuppets/proprietary_vendor_htc
Then the normal LineageOS 15 sources, except the -caf-8994 ones for qcom_media, qcom_display, and qcom_audio.
I've noticed the generated boot.img is ~10mb smaller than the one I built from the LineageOS 14.1 sources. I'm thinking this might be the problem, but I don't hugely know where to go next. I unmkbootimg'd the boot.img, and the ramdisks are around the same size as in LOS 14.1 , but the zImage's are very different. I can upload the build if you want, but it doesn't boot or even boot the kernel in normal mode to log anything.
Click to expand...
Click to collapse
Can you post the rom or send it as pm? I want to test something if it's possible...
lucyr03 said:
Can you post the rom or send it as pm? I want to test something if it's possible...
Click to expand...
Click to collapse
Yeah no problem. I'll just try to revert some changes that didn't work before I upload (might take a few hours). I'm also going to try a clean rebuild tonight too.
xangma said:
Yeah no problem. I'll just try to revert some changes that didn't work before I upload (might take a few hours). I'm also going to try a clean rebuild tonight too.
Click to expand...
Click to collapse
Ok, let me know your progress, I want to test builds and help with what I can...
And about smaller zImage maybe it's just a compilation error or missing some things from kernel source...
lucyr03 said:
Ok, let me know your progress, I want to test builds and help with what I can...
And about smaller zImage maybe it's just a compilation error or missing some things from kernel source...
Click to expand...
Click to collapse
Yeah I'm thinking that's the case. Now I just have to learn how the kernel gets built to compare it to LOS 14.1 and the M8.
Sounds great. Here's the download link.
Though I would warn anyone downloading this - this build does not boot. I didn't do anything crazy to the code, but I'm not taking responsibility for other people using their devices to test. I haven't gone back to LOS 14.1 since this either.
With all that said, thanks for your offer to help! And thanks to anyone else that does too! Also thanks to the actual coders of the source =D
EDIT: Oh, and if for any reason I have to take this down, just let me know.
So I found a big problem and I'm rerunning the build now. I wasn't paying attention and hadn't properly updated the LineageOS device_htc_himaul branch. This meant the build was using the vendor_lineage/config/common_full_phone.mk instead of common.mk and missed a lot out.
I've made the changes locally for now while I test *crosses fingers*, then I'll eventually upload my changes to github if they work.
EDIT: I now realise that common_full_phone.mk calls common.mk eventually anyway, so I've just taken out the telephony packages. Oh well, doesn't hurt to make the problem simpler.
xangma said:
So I found a big problem and I'm rerunning the build now. I wasn't paying attention and hadn't properly updated the LineageOS device_htc_himaul branch. This meant the build was using the vendor_lineage/config/common_full_phone.mk instead of common.mk and missed a lot out.
I've made the changes locally for now while I test *crosses fingers*, then I'll eventually upload my changes to github if they work.
Click to expand...
Click to collapse
Good, I'll wait for the build.
Hope will boot
Any news?
lucyr03 said:
Any news?
Click to expand...
Click to collapse
Unfortunately it didn't boot either (nothing changed with the kernel), but I do feel I'm getting a bit closer. I found a new android_device_htc_hima-common and kernel which I'm going to try and build now.
xangma said:
Unfortunately it didn't boot either (nothing changed with the kernel), but I do feel I'm getting a bit closer. I found a new android_device_htc_hima-common and kernel which I'm going to try and build now.
Click to expand...
Click to collapse
How's with new kernel source?
lucyr03 said:
How's with new kernel source?
Click to expand...
Click to collapse
Not too good. I'm very lazy and unorganised so purged all the source and started again just to be sure about what's going into the build.
I have 'updated' the android_device_htc_himaul source to LOS15.0. When I say updated, I mean copy what I saw someone else doing for the himawl. I was using this updated version for the previous non working build, but I thought I'd share what I'd done.
Still battling to get this build completed without errors, it's at 5% at the moment and they take up to 5 hours on my PC
Woohoo! I have a bootanimation! Just waiting to see what it does next =D
Ok, amazingly adb is working, which is great news. Here's my bootloop error log.
Unfortunately, I can't work on this for a while, so I'll post up instructions of how I got where I am.
1. Install all the packages to build LineageOS as listed here and make a folder for your source and initialise the repo in that folder using 'repo init -u https://github.com/LineageOS/android.git -b lineage-15.0'
2. Run 'repo sync -c'.
3. Make a directory in the .repo folder called 'local_manifests' and add a file called 'roomservice.xml' containing this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xangma/android_device_htc_himaul" path="device/htc/himaul" remote="github" revision="lineage-15.0" />
<project name="Mirenk/android_device_htc_hima-common" path="device/htc/hima-common" remote="github" revision="o8.0" />
<project name="Mirenk/chinomofu_kernel_m9" path="kernel/htc/msm8994" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-15.0" />
</manifest>
4. Force sync all these project paths by running 'repo sync --force-sync $path$'. For example for the first project it'd be 'repo sync --force-sync device/htc/himaul'
5. Comment out the 'TARGET_KERNEL_APPEND_DTB := true' line in device/htc/hima-common/BoardConfigCommon.mk
6. Make this change to hardware/qcom/audio-caf/msm8994/hal/audio_hw.c
7. Added system mount point
Code:
/dev/block/platform/soc.0/f9824900.sdhci/by-name/system /system ext4 ro,barrier=1 wait
to this file: device/htc/hima-common/rootdir/etc/fstab.qcom
8. Run 'source build/envsetup.sh'
9. Run 'brunch lineage_himaul-eng'
10. In the created zip file, remove the assert at the top of the updater-script (spans 4 lines?) to avoid error 7 while flashing in TWRP.
That's it! That's the 10 steps you need to get to a bootlooping Oreo rom! =P
EDIT:
Looks like the error at the bottom of the logcat is looking for /system/vendor/firmware/image/keymaster.mdt when in fact it is stored at /firmware/keymaster/keymaster.mdt ...
And the mc_v2.mdt is in /system/etc/firmware/
Don't know about the others though. Maybe it'll get further into the boot if we point it to those files.
Looks like this might be a good fix ...
Can you upload the build? I don't have any good pc to build it and will take 10-12 hours I think on my pc.
Sadly not. I have no proper computer access at the moment. I'm actually now unsure the keymaster is preventing it booting as I've seen other logcats that get past this point.
I think the answer might be in /devlog but I've gone back to LOS14.1 until I can get back to this ...
xangma said:
Sadly not. I have no proper computer access at the moment. I'm actually now unsure the keymaster is preventing it booting as I've seen other logcats that get past this point.
I think the answer might be in /devlog but I've gone back to LOS14.1 until I can get back to this ...
Click to expand...
Click to collapse
Really!? My M9's logcat dosen't move from keymaster error…[emoji26]
Could you show me logcat if you still have it ?
Mirenk said:
Really!? My M9's logcat dosen't move from keymaster error…[emoji26]
Could you show me logcat if you still have it ?
Click to expand...
Click to collapse
It does after your edits! (I think). I'm just syncing your vendor/htc/ and rebuilding.
Thanks for all your work, seriously, I'm just mashing things together and fixing small problems I think I understand. I updated the proprietary-files.txt a little here: https://pastebin.com/SxSr56hi
And I also added another hidl definition in the manifest.xml so surfaceflinger would start:
Code:
<hal format="hidl">
<name>android.hardware.configstore</name>
<transport>hwbinder</transport>
<version>1.0</version>
<interface>
<name>ISurfaceFlingerConfigs</name>
<instance>default</instance>
</interface>
</hal>
EDIT: To answer your question though, the logcats I saw getting past the keymaster error were from other devices. So I thought it wouldn't be a problem. It's to do with qualcomm hardware encryption right? Always good to have that working though I guess haha =]
EDIT2: Now I'm just hoping your vendor/htc/hima-common updates will fix this error:
Code:
10-22 16:35:14.033 466 466 E QCOM PowerHAL: Unable to open prefetcher: dlopen failed: library "libqti-iop-client.so" not found
10-22 16:35:14.033 466 466 E QCOM PowerHAL: Failed to get prefetcher handle.
10-22 16:35:14.033 466 466 I QCOM PowerHAL: QCOM power HAL initing.
Ok, after installing your vendor/htc repo, the keymaster error is back. I think when using your latest device/htc/hima-common and the TheMuppets vendor/htc repo, the keymaster error went away.
I'm very confused ...
Code:
10-22 18:59:48.194 531 531 E [email protected]: Error opening keystore keymaster0 device.
10-22 18:59:48.195 531 531 E [email protected]: Could not get passthrough implementation for [email protected]::IKeymasterDevice/default.
10-22 18:59:53.194 532 532 I [email protected]: Fetching keymaster device name default
10-22 18:59:53.194 532 532 I vndksupport: sphal namespace is not configured for this process. Loading /vendor/lib64/hw/keystore.msm8994.so from the current namespace instead.
10-22 18:59:53.195 532 532 I [email protected]: Found keymaster0 module Keymaster QCOM HAL, version 3
10-22 18:59:53.195 532 532 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
10-22 18:59:53.195 532 532 D QSEECOMAPI: : App is not loaded in QSEE
10-22 18:59:53.195 532 532 E QSEECOMAPI: : Error::Cannot open the file /vendor/firmware/keymaster.mdt
10-22 18:59:53.195 532 532 E QSEECOMAPI: : Error::Loading image failed with ret = -1
This looks different now though. it was looking for them in /vendor/firmware/images before...