[ROM][DISCONTINUED][UNOFFICIAL] Lineage OS 13 for G4 Play - Moto G4 Play ROMs, Kernels, Recoveries, & Other De

LINEAGE OS 13 FOR HARPIA​
​In the wake of perfected Nougat and nearly complete Oreo for our beloved G4 Play… the ROM literally none of you have asked for is finally here!!!
​:victory::victory::victory:​
NOTE: This ROM has been discontinued, due to Xposed being released for Nougat, but more so due to sync errors whenever I try to pull the latest changes to my system with repo sync. I'll keep the thread here in case any of you want to build this for yourselves, since the steps needed to build everything differ from what the official Lineage wiki says about building Lin13.
What’s Working
Everything seems good to me
What’s Not Working
I can't find anything, so let me know
How To Build
Follow the standard procedure found on the Lineage Wiki for building Lineage 13, except DO NOT INSTALL OPENJDK 7!!! If you have this on your system, remove it before starting the process. JUST STICK WITH JAVA 8!!!
After doing your repo sync to get everything on your computer, run "breakfast harpia" so it creates a roomservice.xml file. After breakfast is done, replace the roomservice file it auto-generates with this one below:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Dark98/android_device_motorola_harpia" path="device/motorola/harpia" remote="github" />
<project name="Dark98/android_device_motorola_msm8916-common" path="device/motorola/msm8916-common" remote="github" />
<project name="SubhrajyotiSen/android_kernel_motorola_msm8916" path="kernel/motorola/msm8916" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="moto8916/proprietary_vendor_motorola" path="vendor/motorola/" remote="github" revision="cm-13.0" />
</manifest>
and do a "repo sync --force-sync". Once that's done, just brunch it and you'll be good to go!
As a side note, to add custom ringtones/alarms/sounds to your ROM, you need to wait for it to successfully build once, then put your desired .ogg files in the respective /system/media/audio/ folder that's contained in your specific device's /out directory, and build again (don't do a make clean or make clobber, it'll erase your work). Interpret me saying this however you want
Download Link
DOWNLOAD FROM GOOGLE DRIVE HERE
I also recommend a custom kernel, like SomeFeak or SquidKernel.
Questions You May Want To Ask
Why would I even want to use this ROM?
Since Xposed for Nougat just came out, there's literally no practical reason for you to need to use this anymore. I guess if you want some nostalgia, but that's it.
Why would you want to even make this ROM?
Something about me just wants at least one stable, updated MM ROM for this thing. I really can’t tell you why, just a weird urge I have.
I’m getting Java build errors when I try to compile!!!
Make sure you have only Java 8, and no Java 7.
I’m getting build errors at Gello when I try to compile!!!
You can disable Gello during the build process, which I did. Edit the moto8916.mk file in moto8916-common device directory and comment out all the stuff about Gello.
I’m getting status 2 errors at the kernel part when I try to compile!!!
GET RID OF JAVA 7!!!!!
How often will you be updating this?
This is obviously an unofficial build, so while I’ll try to make regular releases if everything works out alright, don’t expect that. I’m thinking maybe once a week or so, maybe every 2 weeks if life gets really busy.
Why won't my device encrypt? When I try to make it encrypt it just bootloops or reboots without doing anything
Make sure you're UNROOTED before you try and encrypt. Having a custom kernel/Xposed/etc. is fine, you just need to take off root before running the encryption process. Once it's done, you can reroot and be happy again.
There's something wrong with jack-admin when I try to compile and it won't work!!!
Run the following commands from inside the root of your build directory:
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx#g" (REPLACE # WITH 1GB LESS THAN THE AMOUNT OF RAM YOU HAVE)
./prebuilts/sdk/tools/jack-admin kill-server
./prebuilts/sdk/tools/jack-admin start-server
Then try to brunch again, see if that fixes it
Special Thanks
My good man @Dark98 has been a huge help in getting this to work. He was actually the first to make a Lin13 build for Harpia about 2 months ago, so without his initial work in solving all the compiler error stuff (like the BoardConfig thing mentioned above) I wouldn’t be able to release what I did. Also, special thanks to all you guys in the SomeFeak telegram group!

One day I want to learn how to make ROMs and have that same willpower as you. xD
I've never used Xposed. Maybe I'll test the ROM to see what it looks like.
Good luck and good work!

Arushidesu said:
One day I want to learn how to make ROMs and have that same willpower as you. xD
I've never used Xposed. Maybe I'll test the ROM to see what it looks like.
Good luck and good work!
Click to expand...
Click to collapse
I just flashed back to MM firmware from soak test 7.1.1, and even when installing the ROM on this bootloader/firmware it still doesn't boot. Stay tuned though, I feel like I'm VERY close to getting this thing to work!

UPDATE: After fixing a command regarding GCC exporting, I'm getting new compilation errors with the kernel. I COULD skip kernel compilation, but I'm not sure how that would work out when trying to actually flash the ROM.

jasonmerc said:
UPDATE: After fixing a command regarding GCC exporting, I'm getting new compilation errors with the kernel. I COULD skip kernel compilation, but I'm not sure how that would work out when trying to actually flash the ROM.
Click to expand...
Click to collapse
Alright, I don't know a thing about what goes on under the hood here, but doesn't getting compilation errors mean a broken kernel? And as far as I know, a broken kernel would lead to booting errors, won't even boot up I guess? Correct me if I'm wrong, please

NovaKenn said:
Alright, I don't know a thing about what goes on under the hood here, but doesn't getting compilation errors mean a broken kernel? And as far as I know, a broken kernel would lead to booting errors, won't even boot up I guess? Correct me if I'm wrong, please
Click to expand...
Click to collapse
That's exactly what a broken kernel would do. Before the kernel would compile, but it still wouldn't boot even when flashing a different kernel. Something else under the hood is going on here, which I was told my gcc export commands would fix. Now that I put in the gcc export stuff, it can't compile the kernel, and therefore never finishes compiling the ROM. I'm looking into this right now, not sure when I'l get a solution though (seems harder than I thought to fix)

jasonmerc said:
That's exactly what a broken kernel would do. Before the kernel would compile, but it still wouldn't boot even when flashing a different kernel. Something else under the hood is going on here, which I was told my gcc export commands would fix. Now that I put in the gcc export stuff, it can't compile the kernel, and therefore never finishes compiling the ROM. I'm looking into this right now, not sure when I'l get a solution though (seems harder than I thought to fix)
Click to expand...
Click to collapse
Appreciate the amount of effort you're putting in here, but I really think it would have been worth the hard work if you had gone for LOS 15 instead. Not many seem to have interest in opting for a MM ROM now. Personally, I would like to try Xposed on MM at least once as I stumbled across XDA only after N.
Anyways, we'll be waiting for your ROM! All the best to you mate!

NovaKenn said:
Appreciate the amount of effort you're putting in here, but I really think it would have been worth the hard work if you had gone for LOS 15 instead. Not many seem to have interest in opting for a MM ROM now. Personally, I would like to try Xposed on MM at least once as I stumbled across XDA only after N.
Anyways, we'll be waiting for your ROM! All the best to you mate!
Click to expand...
Click to collapse
Some other developers are already working on O roms: There's an alpha build of GZOSP Oreo on Android File Host (made by the same guy that's helped me with building this ROM) if you'd like to look at that as well. I may move to Oreo eventually, but I'd REALLY like to get this working before I do. Even if it's not my daily driver forever, to be able to make builds if I want to would be ideal.

jasonmerc said:
Some other developers are already working on O roms: There's an alpha build of GZOSP Oreo on Android File Host (made by the same guy that's helped me with building this ROM) if you'd like to look at that as well. I may move to Oreo eventually, but I'd REALLY like to get this working before I do.
Click to expand...
Click to collapse
GZOSP done so soon? Well gotta try it out once anyway. Let's taste it once.

NovaKenn said:
GZOSP done so soon? Is that for harpia though?
Click to expand...
Click to collapse
It's far from stable, but yes it is for Harpia. Feel free to take a look and flash it if you want, help give Dark98 some support as a thanks for helping me with this
But back on topic though, I have another build running on my PC at home at the moment. I had to edit the gcc export script a little bit, if it fixes the problem I'll update the first post with the fixed command to add.

UPDATE: My good man @facuarmo suggested I take the boot.img of Josh's older (but more stable) Lin13 build and put it in my newer, non-booting Lin13 build for a sort of workaround until I can figure out how to get sources compiled correctly on my own. I've just uploaded a "fixed" ROM zip to my google drive if any of you want to try this out. I'll be making a NAND backup of my Nougat ROM then giving this a try myself.
EDIT: Replacing the boot image did nothing, so back to the drawing board

GOOD NEWS SORTA!!! Josh was able to compile a new Lineage 13 build, which I tested and can confirm it works. He's gonna share his local manifests with me so I can build and maintain it. If it still won't build even after that, I'll ask him if I can give a link to his build, to hold you guys over who are waiting for this.
Big shout out to Josh who's been a tremendous help this whole time. If I knew his XDA username I'd cite it, but otherwise you can find him on GitHub:
https://github.com/dark98

I am testing the update of Josh and it goes very well, I keep in touch with the (telegram)

Is Lineage 13 marshmallow?
Enviado desde mi Moto G Play mediante Tapatalk

mario156090 said:
Is Lineage 13 marshmallow?
Enviado desde mi Moto G Play mediante Tapatalk
Click to expand...
Click to collapse
yup

Neither Josh nor I have any idea why this isn't working for me. I've seemingly 1:1 copied everything he's done (besides the distro of Linux I use) and I still get weird errors when he gets none. My last hope is going to be replace Ubuntu with Debian for my Android Building VM, and if that doesn't work I'm going to have to abandon this since I'm not sure how to fix the problems I'm getting.
In the meantime though, here is his build of Lin13 in case you all want to run that.

jasonmerc said:
Neither Josh nor I have any idea why this isn't working for me. I've seemingly 1:1 copied everything he's done (besides the distro of Linux I use) and I still get weird errors when he gets none. My last hope is going to be replace Ubuntu with Debian for my Android Building VM, and if that doesn't work I'm going to have to abandon this since I'm not sure how to fix the problems I'm getting.
In the meantime though, here is his build of Lin13 in case you all want to run that.
Click to expand...
Click to collapse
Running stable? Or is it unstable-ish?

NovaKenn said:
Running stable? Or is it unstable-ish?
Click to expand...
Click to collapse
100% stable, everything works great from what I can see. I flashed SomeFeaK kernel as well, so maybe that's attributing to it, but still everything works fine.
Quick update though, I found out from Josh that I apparently DON'T NEED JAVA 7 AT ALL during the compilation, contrary to what Lineage WIki's build instructions say for Lineage 13. Not only am I removing Java 7 completely and trying again, but I'm editing my manifests as well. I hope this works.

Great news guys! It built on my own system!!! I'm not sure if it'll actually boot (since I'm rebuilding with a some little goodies in there to thank you all for your partience) but this is a very good sign! As usual, stay tuned for updates!
EDIT 1: New build is up, check the download link for Lineage 10062017. I haven't been able to test if it boots yet, but it's there nonetheless

I just flashed my new 10-06 build over the 10-01 one Josh made, and I was actually able to boot it!!!!! Everything is officially working now!

Related

[WIP][DEV] Ubuntu Touch for Sony Xperia Z Ultra

Hi folks,
I just started to port UbuntuTouch for the Sony Xperia Z Ultra and I think I should have a *.zip ready for testing in 2 weeks.
Until then, I will use this thread as a scrap book to document all the troubles I run into, all the things that needed my special attention and fixes that are not that obvious. I hope there will be some fellas brave enough to test everything and report back or even to join me with the development.
Best regards,
Kalle
First Update:
I found that the Ubuntu Touch version that ist based on CyanogenMod was not updated to a more recent version. This means that I have to either look into AOSP or backport everything to CM-10.1. I think backporting is kinda stupid because newer we are writing new software to improve things. Sadly I don't have much experiance with AOSP so I will have to find out how everything works and what the differences to CyanogenMod are.
The good news is, that I'm catching up with the mailing list, which means I'll have a place to call for help.
Also I'm in the progress to start a git repo, but I'm unsure what I will need to add, maybe some common stuff from sony does not need to be changed.
So long,
Kalle
Update!
There is a new porting guide! See here
I already freed some space for it and ordered a bit more ram so after my exam next week, I'll pick this up/Start all over.
Hope you are as excited as I am,
Kalle
XDA:DevDB Information
Ubuntu Touch for Sony Xperia Z Ultra, ROM for the Sony Xperia Z Ultra
Contributors
KalleEatingBrain, Kohelet
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2014-05-14
Last Updated 2015-02-24
freaking awesome!
freaking awesome!
i would like to test. maybe i can help with developing/porting
Thank you for your efforts. I will test if needed.
Sent from my C6806 using XDA Premium 4 mobile app
Great this would be awesome if you can make it happen. I'm here for testing if required.
Sent from my C6833 using XDA Premium 4 mobile app
In also here for testing... Ubuntu Touch has intruiged me, I would love to try it out.
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
iBuzman said:
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
+1
Nice.ill be watching out everyday
Sent from my C6833 using XDA Premium 4 mobile app
blueether said:
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
Click to expand...
Click to collapse
Cool, thanks can you give me a hint on how to deal with new targets in Aosp? I mean setting up the files in a way "lunch" is able to find the right target.
Sent from my C6833 using XDA Free mobile app
vendersetup.sh file in vender/ might be what you are looking for?
have a gander at this http://www.kandroid.org/online-pdk/guide/build_new_device.html
How are you doing on this? I've just started working on this as well and am curious to know how far along you've gotten/what issues you've run into.
Sent from my Nexus 7 using XDA Free mobile app
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Kohelet said:
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Click to expand...
Click to collapse
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
KalleEatingBrain said:
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
Click to expand...
Click to collapse
I actually got past the libhybris issue. The problem was that the porting guide is out of date. It's based on using cm-10.1 whereas the current source for Ubuntu is based on cm-11.0. So if you use 4.4.2 instead instead of 4.2.2 then it works. But there are so many other issues and the documentation for fixing them is so poor. I've kept a running list of problems I've come across and the solutions for them (it's below).
Also they dropped the whole UCM thing so you should be able to get sound working once you actually get a working build, but I couldn't get it to build. The error that is currently in my way has to do with "No rule to make target signapk.jar needed by com.qualcomm.location" or something or other. And I found nothing on how to solve that online.
At this point I've decided to take a short break from the whole thing because it's so frustrating.
Once I get motivated to work on it again, I'll probably start from scratch.
Issues List (I apologize for not being specific about the errors, I didn't write them down verbatim):
If you get an error about libelf you need to add CyanogenMod/android_external_elfutils to your local_manifests/roomservice.xml and also add external/elfutils under subdirs in build/core/main.mk
Don't forget to also add device/sony and vendor/sony to build/core/main.mk as well.
The build will complain about not having a rule to make android-boot.img. To fix you have to go to device/sony/fusion3-common/custombookimg.mk and change boot.img to android-boot.img. You need to make the same change in device/sony/rhine-common/custombootimg.mk
I got an error about android.hardware.bluetooth_le.xml. If you just restart the build it doesn't complain, but I didn't find a proper solution to that.
If you get the libhybris error you have the wrong version of the Ubuntu source. Make sure you're using 4.4.2 when you phablet-dev-botstrap. It should be phablet-dev-bootstrap --sources aosp --repo-branch phablet-4.4.2_r1 [target_directory]
You might get an error about a product_config.mk and how it's missing a makefile for togari. You have to make sure that in device/sony/togari Android.mk, cm.mk, full_togari.mk, and vendorsetup.sh PRODUCT_NAME is the same. I solved this by changing PRODUCT_NAME to cm_togari in all of them and then renamed full_togari.mk to cm_togari.mk
You might get an error like MODULE.TARGET.SHARED_LIBRARIES.libOmxCore already defined in hardware/qcom/media. You should have CyanogenMod/android_hardware_qcom_media-caf-new in your repo manifest with a path of android/qcom/media-caf-new so you can safely rm -rf the hardware/qcom/media directory to get past this error.
If you get an error about dtbToolCM, add /device/qcom/common/dtbtool to your subdirs in build/core/main.mk
You may get an error about mkbootimg, that's because Sony uses a different version of mkbootimg. The only option I found was to download it from the internet (Thanks DooMLorD!). Once you get that version edit device/sony/rhine-common/custombootimg.mk and replace $(MKBOOTIMG) with the path to your downloaded mkbootimg binary.
You might get an error about no rule to make target something/something/signapk.jar needed by something/something/com.qualcomm.location. I didn't find a solution to this error.
Click to expand...
Click to collapse
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
blueether said:
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
Click to expand...
Click to collapse
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Kohelet said:
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Click to expand...
Click to collapse
Yeh carbon and slim were easy to build, and simple fixes. AOSP on the other hand I wish I had kept a build log
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch. I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
KalleEatingBrain said:
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch.
Click to expand...
Click to collapse
That could potentially be a major source of my problems. i wasn't aware of that.
I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
All I have at the moment is a fork of the CM repos. Feel free to add me to your repo. My username on Github is Kohelet as well. I can start to look into removing java dependencies as well.
As for the sound, the mailing list made it appear as if it was a simple matter of running
Code:
$ sudo apt-add-repository ppa:ci-train-ppa-service/landing-018
$ sudo apt-get update
$ sudo apt-get dist-upgrade
$ sudo apt-get install pulseaudio-module-droid
I could be wrong though.

roomservice.xml for Nexus 6P - Angler

​
Hey guys, since development for our Nexus 6P is taking off quite nicely, I was hoping to get a solid roomservice.xml written up so we can start compiling our own ROMs from source. Here is CM's Device and Kernel Tree, as well as the Vendor files from @TheMuppets. I am assuming though, there are a few other additions to this roomservice.xml that I have missed, but all in good time. If anyone wants to weigh in or advise please do, expect this post to change overtime.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_huawei_angler" path="device/huawei/angler" remote="github" />
<project name="CyanogenMod/android_kernel_huawei_angler" path="kernel/huawei/angler" remote="github" />
<project name="TheMuppets/proprietary_vendor_huawei" path="vendor/huawei/angler" remote="github" />
</manifest>
you dont really need an xml file though
just download the files manually and build
flex360 said:
you dont really need an xml file though
just download the files manually and build
Click to expand...
Click to collapse
Wow, to be honest I had no idea, I've only ever used the roomservice.xml method. Makes sense though. Just as a reference I'll add that in later when all the dependencies are figured out. Any idea what other dependencies are needed to build for Angler by chance?
Just lunch angler and add the muppets. Not sure why you are over thinking this. Room service is automatically created when you lunch (or breakfast) a device.
adzcache said:
Wow, to be honest I had no idea, I've only ever used the roomservice.xml method. Makes sense though. Just as a reference I'll add that in later when all the dependencies are figured out. Any idea what other dependencies are needed to build for Angler by chance?
Click to expand...
Click to collapse
you need device/huawei/angler/angler-kernel
akellar said:
Just lunch angler and add the muppets. Not sure why you are over thinking this. Room service is automatically created when you lunch (or breakfast) a device.
Click to expand...
Click to collapse
Perhaps I am over thinking all this. I was under the impression a roomservice.xml is handy for building a ROM for an unsupported device.
Say I wanted to build another ROM based on CM, that has outdated sources for Angler (or none at all), wouldn't a roomservice.xml pull updated CM sources to the project that I'm attempting to build?
That of course is just an example, I actually would prefer building Slim or something of the sort that utilizes Layers.
Damn I miss Slim..
adzcache said:
Perhaps I am over thinking all this. I was under the impression a roomservice.xml is handy for building a ROM for an unsupported device.
Say I wanted to build another ROM based on CM, that has outdated sources for Angler (or none at all), wouldn't a roomservice.xml pull updated CM sources to the project that I'm attempting to build?
That of course is just an example, I actually would prefer building Slim or something of the sort that utilizes Layers.
Damn I miss Slim..
Click to expand...
Click to collapse
6P is a supported device though. As far as building for another rom that doesn't have 6P support, there likely is much more to it than just pulling CM device trees.
akellar said:
6P is a supported device though. As far as building for another rom that doesn't have 6P support, there likely is much more to it than just pulling CM device trees.
Click to expand...
Click to collapse
Oh okay. Last time I built for an unsupported device all I changed to get a successful build was the cm.dependencies and cm.mk files (Maybe a few other minor changes), however that was on my old OnePlus One.
Thanks for clearing that up @akellar, I suppose it would probably be better to just wait for more ROMs to support Angler, then to screw around with the device tree. I may give it a go, just for testing sake though. Cheers!

For devs: Looking to play with the kernel sources?

The good stuff: https://github.com/jcadduono/android_kernel_lge_msm8996/commits/android-7.0
Fork it!
Update: CAF branch has some problems at the moment, use this one instead for now.
So this is currently the v10d release. It's compatible with V20 Nougat v10d and G5 v20a.
Place toolchain (pick one up from here) in ~/build/toolchain & tar xf.
git clone https://[email protected]/yourname/android_kernel_lge_msm8996.git
If you want to change any config options:
./menuconfig.sh (optional target, ex. twrp or lge)
Ready?
./build.sh h850/h830/h918/us996/any model you want
Models are applied onto the target base defconfig, so your V20 kernels will build for all V20 variants and for all variants of the G5 as well.
Create your own by copying arch/arm64/configs/lge_defconfig to arch/arm64/configs/your-awesome_defconfig!
Grab:
build/arch/arm64/boot/Image.lz4-dtb [or] build/arch/arm64/boot/Image.gz-dtb
build/lib/modules
Place in:
https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
make
You got yourself a magical all-powerful custom kernel installer, complete with your own custom kernel!
Notice that there's a few branches:
opensource is where I merge LG changes, when it's updated, android-7.0 is rebased on it
android-7.0 is a starting off point closest to absolute stock, base off here
android-7.0-security adds security and bug fixes from CAF on top of android-7.0 branch
twrp-7.0 is for Team Win Recovery Project (yes, it's ready, come with an unlocked device and I'll give it to you)
nethunter-7.0 is for the Kali NetHunter project (if you dare, some fun there)
Another issue was their weird build system, I dropped that. Replaced tuxera's exFAT prebuilt downloader with Samsung's GPL'd exFAT drivers instead. Unsure how well it works replacing it like that, we'll have to see.
I also added Qualcomm's Core Control which they just released the sources to somewhat recently. I believe it's already included on the G5 and probably V20 as a kernel module. Their released version doesn't have module support yet but it's fairly easy to add I guess with the leaked proprietary module version out there to pick pieces from.
Have fun!
Great Man !
thanks for this..
I've been following the root process since the beginning and I'm amazed at the relatively short amount of time it took. Huge kudos to @jcadduono! I will purchase this phone. Now, since the kernel needed to have it's encryption support modifed, are the patches added to a branch on your Github fork? I would like to compile a custom kernel, along with patching it with SultanXDA's SafetyNet boot bypass. Which branch will be appropiate to fork to flash on the TWRP/Rooted V20?
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
zabracks said:
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
Click to expand...
Click to collapse
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
I've got an H918, if you need somebody to test a kernel.
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
which branch/repo is the one that boots but messed up display?
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
lightninbug said:
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
Click to expand...
Click to collapse
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:25 PM ----------
Artcrime said:
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
Click to expand...
Click to collapse
There is v10d version for 918. opensource.lge.com forgive me if this is old news. a|c
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
slayerh4x said:
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
Click to expand...
Click to collapse
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
Sent from my LG-H990 using Tapatalk
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Is a kernel the main thing stopping us from a CM rom?
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
jcadduono said:
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Click to expand...
Click to collapse
I'm there.
albinoman887 said:
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
Click to expand...
Click to collapse
gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu.tar.xz .Be sure to change the PATH in menuconfig.sh
@jcadduono , thank you. You are truly an inspiration
Wondering if anyone can help me learn how to do this right...
So I was able to compile the kernel, but I didn't get an Image.gz (which im sure is fine). I did get an Image.lz4, Image.lz4-dtb, and Image (no extension). I figure only the .lz4* files are needed. I added all 3 to the lazyflasher, and ran make. The resulting zip flashed, but sent me straight to Bootloader. I then tried to fix by flashing the stock kernel, but this still did not boot. ReFlashed my ROM and it's booting now.
I used this toolchain gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu
Any guidance? My guess is it's flashing at the wrong point?
Here is the ZIP. DO NOT FLASH. This is only for someone who knows what they are looking at to tell me what is wrong with it. No modifications were done. Source was forked from OP, and compiled with default menuconfig, then build.sh h918

[KERNEL] FenomenalMOD [UBERTC][24-03-2017]

INTRO:
I present a new version of my kernel, now for the lg k7, the kernel has patches that will help you get a very good performance, as well as a longer battery life, and better fluidity, is compiled with UbertTC in its version 5.2, in addition to containing patches for a correct stability.
Features:
* Compiled with UberTC
* More coming soon...
Downloads:
Preview version -> Download
Instructions:
* Flash in TWRP
Notes:
* Im only test in MetroPCS variant
Sources:
GitHub
Reserved
....
Worked flawlessly. Flashed with TWRP and rebooted and system loaded up fine. There was a few minor lags as it booted into the system past the MetroPCS logo but that was probably due to the changes made by the zip but after that the system was more fluid than it previously was even after having soo many apps installed. Great work. This is one step closer to completing a custom rom like CM13 or Lineage OS. Good luck with more development.
thepcwiz101 said:
Worked flawlessly. Flashed with TWRP and rebooted and system loaded up fine. There was a few minor lags as it booted into the system past the MetroPCS logo but that was probably due to the changes made by the zip but after that the system was more fluid than it previously was even after having soo many apps installed. Great work. This is one step closer to completing a custom rom like CM13 or Lineage OS. Good luck with more development.
Click to expand...
Click to collapse
Im already working on Lineage
xperiafan13 said:
Im already working on Lineage[/QUO
Hey people don't forget to hit the thanks button.
By the way ty Dev keep up the good work. This phone is def a decent phone surprise nothing been built for it.
Click to expand...
Click to collapse
xperiafan13 said:
Im already working on Lineage
Click to expand...
Click to collapse
Nice. I hope Development is going well. If you need any testers i am up for testing any builds.
thepcwiz101 said:
Nice. I hope Development is going well. If you need any testers i am up for testing any builds.
Click to expand...
Click to collapse
I second that statement... I'll be a test dummy ?? anything for a new ROM!
Im already compile lineage, but this not boot, im need more time
xperiafan13 said:
Im already compile lineage, but this not boot, im need more time
Click to expand...
Click to collapse
Need any help let me know. . I'd love to help!
xperiafan13 said:
Im already compile lineage, but this not boot, im need more time
Click to expand...
Click to collapse
Hopefully it boots. Many of us have been waiting for a custom rom ??? btw, I tried to make help with compiling a custom rom but haven't had time. I'm also a noob in this so Im researching on "How to complie a custom rom from scratch" but its really difficult ?? Thank you for your efforts???
SageTheMage99 said:
Hopefully it boots. Many of us have been waiting for a custom rom ??? btw, I tried to make help with compiling a custom rom but haven't had time. I'm also a noob in this so Im researching on "How to complie a custom rom from scratch" but its really difficult ?? Thank you for your efforts???
Click to expand...
Click to collapse
Yeah I have ported a few ROMs but when it comes down to comp... A ROM that's a whole different ball park for me also.
You could try to Port the LG Leon ROMs. There's 2 I don't have the phone so I can not try.
Good job on the kernel compile i couldnt get mine to boot, good luck on the lineage compile. Ive picked this phone back up so let me know if you need any help.
NASSTYROME said:
Good job on the kernel compile i couldnt get mine to boot, good luck on the lineage compile. Ive picked this phone back up so let me know if you need any help.
Click to expand...
Click to collapse
Hello, i just downloaded LineageOS but everytime i type:
"breakfast m1", i get:
** Don't have a product spec for 'lineage_m1'
** Do you have the right repo manifest?
Any help is appreciated, for better way to reach me is my kik: SageOfSixPaths999
Breakfast wont work u need to manually set variables and make calls like old android.
NASSTYROME said:
Breakfast wont work u need to manually set variables and make calls like old android.
Click to expand...
Click to collapse
Would you please guide me or send link to where i could do this?
At the moment I am not working on this, since I am in school projects, but once I finish with it I will continue with this, both the kernel and the development of rom, the sourves are in my github of the kernel, if they want to modify it or Add improvements
xperiafan13 said:
At the moment I am not working on this, since I am in school projects, but once I finish with it I will continue with this, both the kernel and the development of rom, the sourves are in my github of the kernel, if they want to modify it or Add improvements
Click to expand...
Click to collapse
Ok thank you for your work ether way but i can try to help, i just need info. But i will do and find out whatever i can. I really am exited for a new rom lol. I will continue once i get home.
xperiafan13 said:
At the moment I am not working on this, since I am in school projects, but once I finish with it I will continue with this, both the kernel and the development of rom, the sourves are in my github of the kernel, if they want to modify it or Add improvements
Click to expand...
Click to collapse
Just curious, what version of Lineage OS were you building?
EDIT: I am running the kernel on the T-Mobile K330 variant with no issues. Good work :good:
QuickNET Tech said:
Just curious, what version of Lineage OS were you building?
EDIT: I am running the kernel on the T-Mobile K330 variant with no issues. Good work :good:
Click to expand...
Click to collapse
I know you didn't ask me but if it helps, I'm working on CM-14.1
All i need is to "set the variables manually" but so far no luck in my research and also no one helps me with my questions. I also posted a post on the thread of k7 questions and such but so far no luck.

OmniRom Oreo 8.1 unofficial

So I have successfully built OmniRom 8.1 Oreo for Shamu the zip file is a little over 500mb. The package flashes correctly but fails to boot. I have already tried to change the BoardConfig.mk file to be SeLinux=Permissive but it still fails to boot. My device is decrypted as well. What could be a source of the non boot issue other than what I have mentioned. This project is taking quite some time to complete.
HELP!!!!!
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Rondeau79 said:
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Click to expand...
Click to collapse
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
Elektroschmock said:
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Click to expand...
Click to collapse
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Do an -eng build and read logcat and dmesg via ADB. Usually you see whats wrong.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
webdroidmt said:
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
Click to expand...
Click to collapse
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Rondeau79 said:
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Click to expand...
Click to collapse
If you push your sources somewhere where we can see it, it should be easier for us to help you.
nitin.chobhe said:
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Click to expand...
Click to collapse
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Elektroschmock said:
If you push your sources somewhere where we can see it, it should be easier for us to help you.
Click to expand...
Click to collapse
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Rondeau79 said:
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Click to expand...
Click to collapse
Even though it is outdated it is still very much applicable. I linked that thread because you mentioned this.
Good that you know the problem. All the best!
Nitin
Rondeau79 said:
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Click to expand...
Click to collapse
It's not that you need to push it somewhere to get working zips, it's just for us to see your modifications.
Otherwise it is just guessing what you did.
Making it compile is one thing...making it work is a whole different story. When I did the Lineage Oreo bringup I had many things to fix untill it bootet properly.
Lineage's device tree for shamu depends on several other Lineage repositories. For example:
android_hardware_lineage_interfaces
android_hardware_qcom_gps
android_vendor_lineage
android_device_lineage_sepolicy
So just cloning the device repo without examining the reason for your 'bootloop' will get you nowhere.
I'd suggest you to do an engineering build which is easier to debug. Altought I would make this build permissive as selinux denials are a common reason for a bootloop.
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
runekock said:
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
Click to expand...
Click to collapse
If he is based of lineage's device tree, then Lineage's kernel is the best choice.
You should always be able to grab a log, no matter which kernel you are using.
Yeah willing to help out put your stuff up on git and give links
My webhost is down right meow but I can post my Oreo build I had of Omni here I didn't use Los trees i used aosp trees from camcory , joryb and mine cleanos
---------- Post added at 08:47 PM ---------- Previous post was at 08:28 PM ----------
i found my build i had it on afh if you want it to try this was early oreo so some things not fully functional i think gps was iffy https://www.androidfilehost.com/?fid=889964283620775520 i am syncing up omni oreo again for sure will help out if you want please pm
---------- Post added at 08:47 PM ---------- Previous post was at 08:47 PM ----------
nougat builds in that root folder also
bthorne79 said:
Yeah willing to help out put your stuff up on git and give links
Click to expand...
Click to collapse
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Rondeau79 said:
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Click to expand...
Click to collapse
Your probably going to want to fork the toolchains over that was used with cleanaosp
<!-- Prebuilts --> <project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" name="joryb/arm-eabi-7.x" clone-depth="1" remote="bb" revision="master"/> <project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" name="joryb/arm-linux-androideabi-7.x" clone-depth="1" remote="bb" revision="master"/>

Categories

Resources