[ROM][H870|H872|US997] UNOFFICIAL LineageOS-15.1 for LG G6

[x86cpu]

Disclaimer

Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.

Introduction

LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. More info.


These are my UNOFFICIAL builds of LineageOS-15.1 for LG G6 variants. I did NOT create this ROM. I am helping to contribute to this ROM. Thanks to all other coders who contributed to LineageOS.

IMPORTANT

• BACKUP! These are UNTESTED builds. Please be ready to recover your previous ROM. If it kernel panic, boots into bootloader, etc... grab as much info as you can.
• Builds are done periodically (see download below)
• Do NOT be rude.
• Respect all users.
• Any and all users, please help each other. I have a us997 variant for testing, so other variants might have some issues.

Known items

• • VoLTE and WiFi calling do not work yet
• Other known issues (same as OFFICIAL too):
  • WiFi or Bluetooth MAC is "00:00:00:00:00:00" - You wiped the misc partition, you'll need to fix: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12
  • 5Ghz tether not working due to "error"

Install

• You can upgrade from 14.1 (UNOFFICIAL) to 15.1. If you are not on my UNOFFICIAL yet, flash the to-x86cpu.zip first (and reboot recover before upgrade, not reboot into system).
• Flash to-x86cpu.zip if you want. (See Downloads below)
• Flash UNOFFICIAL ROM
• Wipe cache, and dalvik cache
• Magisk if you choose
• Flash GAPPS (I use nano)
• Reboot and wait....

Notes
To enable Developer Options go to Settings, About Phone and repeatedly press Build Number.
If you use ADB read this: PSA by CM
If you use reboot to recovery read this: PSA by CM
Regarding new Superuser: PSA by CM


Bugs
If you encounter issues/bugs that are not known, please report. This is not the OFFICIAL ROM, but I can help to get any issues fixed. I have a us997 variant for testing. If I can replicate your issue then I can track it down. If I cannot, please provide as much detail as possible. Logcats are great.
Please indicate what g6 variant you have (h870, h872, us997) and what you are running (OFFICIAL or UNOFFICIAL) and date. Any mods (no judgment) as well.
I am aware people run mods or change things. I am not against it (as I do myself). However, if needed I may ask you to data wipe (you can say no), or remove a mod that might be interfering. I will do the best I can.

Thanks

• Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
• LineageOS Team
• @Rashed97 for continuing
  

Downloads
ROM: UNOFFICIAL downloads (Note date and variant)
Gapps: arm64 nano 8.1

Sources

• https://github.com/LineageOS
• https://github.com/LineageOS/android_kernel_lge_msm8996
• https://github.com/LineageOS/android_device_lge_msm8996-common
• https://github.com/LineageOS/android_device_lge_g6-common
• h870
• h872
• us997

 

[x86cpu]

What is not working or problematic

What is not working or still wonky:

• Encryption -- Works.
• USB OTG -- Should be working.
• Ambient display -- Disabled now.
• Livedisplay -- Should be working.
• IR will work, then timeout, then work again.
• Video recording -- Should be working. Works sometimes, appears to record, but playing back audio is at the beginning, video at the end, and the duration is messed up.
• 5g tether -- Not working still.
• No FM driver.

 

[x86cpu]

TBD

 

[jjohn7293]

Thank you for making this! Waiting for a list of working/non-working feature before install.

 

[dom133]

Bugs on H870:
* Preferred network type in default is WCDMA
* Data isn't working on LTE
* Blackscreen issues

Wysłane z mojego LG-h870 przy użyciu Tapatalka

 

[x86cpu]

Bugs on H870:
* Preferred network type in default is WCDMA
* Data isn't working on LTE
* Blackscreen issues

Wysłane z mojego LG-h870 przy użyciu Tapatalka

Are you able to change preferred network time to get to working? What's the blackscreen issue?

 

[dom133]

Are you able to change preferred network time to get to working? What's the blackscreen issue?

I can change preferred network to GSM/WCDMA/LTE but lte isn't working. Screen some time is going black and after second is back to normal

Wysłane z mojego LG-h870 przy użyciu Tapatalka

 

[natemckn]

Are you able to change preferred network time to get to working? What's the blackscreen issue?

If its the black screen issue I think it is, then the screen goes black whenever you use multi touch like pinch to zoom. Its caused by this commit in the kernel:

https://github.com/LineageOS/androi...mmit/f4c2e96015404ec8d6fb0bbc1c3e1bfe75d36a40

I've got that reverted on my builds.

 

[x86cpu]

If its the black screen issue I think it is, then the screen goes black whenever you use multi touch like pinch to zoom. Its caused by this commit in the kernel:

https://github.com/LineageOS/androi...mmit/f4c2e96015404ec8d6fb0bbc1c3e1bfe75d36a40

I've got that reverted on my builds.

Thanks, I'll have to check into that. Unfortunately, I cannot revert it on Lineage builds, the kernel is the same for g5/g6/v20, and this works good for the v20. Does anyone have logcat's and more specifically dmesg output from this occuring?

 

[zefie]

If its the black screen issue I think it is, then the screen goes black whenever you use multi touch like pinch to zoom. Its caused by this commit in the kernel:

https://github.com/LineageOS/androi...mmit/f4c2e96015404ec8d6fb0bbc1c3e1bfe75d36a40

I've got that reverted on my builds.

The black screen I had with your build seemed to happen after the screen would lock up, it would flash black quick, in place of what you would expect the ROM to go back to bootanim during a soft crash.

Other times, harder to explain, but basically turning the screen on, off, on too fast would result in it acting like the screen was on, but it would be off. Slowing down the same process would restore it.

It is possible the first half was the system mis-recognizing a pinch touch but I don't think thats quite it. Sadly, I didn't think to look at dmesg/logcat, and I'm back on stock-based for the moment. Even then probably going the treble/GSI route. But I'll try to help where I can.

 

[x86cpu]

The black screen I had with your build seemed to happen after the screen would lock up, it would flash black quick, in place of what you would expect the ROM to go back to bootanim during a soft crash.

Other times, harder to explain, but basically turning the screen on, off, on too fast would result in it acting like the screen was on, but it would be off. Slowing down the same process would restore it.

It is possible the first half was the system mis-recognizing a pinch touch but I don't think thats quite it. Sadly, I didn't think to look at dmesg/logcat, and I'm back on stock-based for the moment. Even then probably going the treble/GSI route. But I'll try to help where I can.

The plan is getting Lineage OS 15.1 to treble too..... Thanks, still looking into it.

 

[natemckn]

Thanks, I'll have to check into that. Unfortunately, I cannot revert it on Lineage builds, the kernel is the same for g5/g6/v20, and this works good for the v20. Does anyone have logcat's and more specifically dmesg output from this occuring?

I haven't flashed your build, so I'm not 100% sure if its the same black screen bug or not, but every build I've done with that specific commit added to the kernel caused the screen to go black when i pinched to zoom. I would be able to replicate consistently just by going to google maps and zooming in and out. I did collect a dmesg at the time and showed it to Rashed and he said it was something with the touch driver:

https://hastebin.com/awuhonuzum.vbs

 

[x86cpu]

I haven't flashed your build, so I'm not 100% sure if its the same black screen bug or not, but every build I've done with that specific commit added to the kernel caused the screen to go black when i pinched to zoom. I would be able to replicate consistently just by going to google maps and zooming in and out. I did collect a dmesg at the time and showed it to Rashed and he said it was something with the touch driver:

https://hastebin.com/awuhonuzum.vbs

Yeah, I checked and this was supposed to fix it: https://github.com/LineageOS/androi...mmit/09ae5fbb4f3c69146ef022914f0f789133c57c78

I see, there's new firmware for the touch that might help and it not in Lineage, but it in in LG's Oreo... or it could make touch not work either, I'll try to get a build and see if anyone might be willing to flash it to see it if helps to fix it.

 

[natemckn]

Yeah, I checked and this was supposed to fix it: https://github.com/LineageOS/androi...mmit/09ae5fbb4f3c69146ef022914f0f789133c57c78

I see, there's new firmware for the touch that might help and it not in Lineage, but it in in LG's Oreo... or it could make touch not work either, I'll try to get a build and see if anyone might be willing to flash it to see it if helps to fix it.

Yeah Rashed pointed to that same commit, but it wasn't the answer for me. Before that commit, the screen would go black randomly when just scrolling through stuff which was super annoying. After that commit, the scrolling/random black screen was fixed but I still had the pinch to zoom black screen issue. The dmesg I got was from a build I did on 4/29 that did have that commit.

 

[x86cpu]

I haven't flashed your build, so I'm not 100% sure if its the same black screen bug or not, but every build I've done with that specific commit added to the kernel caused the screen to go black when i pinched to zoom. I would be able to replicate consistently just by going to google maps and zooming in and out. I did collect a dmesg at the time and showed it to Rashed and he said it was something with the touch driver:

https://hastebin.com/awuhonuzum.vbs

dmesg was helpful, make some kernel adjustments that affect that area, so new builds incoming. BUT.. it might cause no-touch at all. It might fix the black screen. It'd be helpful to know. I usually test myself, but have no G6 (if you know where to get a us997 boot-loader unlocked cheaply .. even screen cracked, let me know).

 

[x86cpu]

lineage-15.1-20180513-UNOFFICIAL

New build, but a warning, this has firmware updates and kernel update for touch screen. Hopefully to resolve the back screen issue. If someone can try and if it fails, please grab as much dmesg as possible. You might also loss touch screen, so be prepared to adb in, and reboot to recovery if needed to go back. Thanks.

 

[natemckn]

New build, but a warning, this has firmware updates and kernel update for touch screen. Hopefully to resolve the back screen issue. If someone can try and if it fails, please grab as much dmesg as possible. You might also loss touch screen, so be prepared to adb in, and reboot to recovery if needed to go back. Thanks.

https://hastebin.com/uvogumamin.vbs

I flashed your 0513 build and can still replicate the screen going black when i pinch to zoom.

Also the colors are washed out which I think means you need these:

https://review.lineageos.org/q/topic:"hdr-extra"+(status:open OR status:merged)

 

[x86cpu]

https://hastebin.com/uvogumamin.vbs

I flashed your 0513 build and can still replicate the screen going black when i pinch to zoom.

Also the colors are washed out which I think means you need these:

https://review.lineageos.org/q/topic:"hdr-extra"+(status:open OR status:merged)

Thanks, the g6 I believe I have, the qcom one may not get applied, I sometimes wait on them figuring things out. I see the dmesg, some errors have changed. Any way to try to get a dmesg sooner, more specifically when it loads the firmware? ( img references) ? Thanks.

 

[htsnorman]

all camera works fine ? and what about bluetooth speaker, is too good ?

 

[x86cpu]

lineage-15.1-20180620-UNOFFICIAL

lineage-15.1-20180620-UNOFFICIAL

New build up. I believe almost everything is in working order. Anyone please test and report.