[ROM][H830|H850|RS988] UNOFFICIAL LineageOS 18.1 for LG G5

[aleasto]

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.

Install

• Update recovery to the latest TWRP or Lineage Recovery build
• Format data if coming from an UNOFFICIAL or non-Lineage build.
• Flash the ROM
• Flash any addons
• Reboot

Bugs
If you encounter issues/bugs that are not known, please report. If I can replicate your issue then I can track it down.
If I cannot, please provide as much detail as possible. Logcats are a must.
Please indicate what g5 variant you have (h830, h850, rs988), the dated version, and any third party mods.
I am aware people run mods or change things. If needed I may ask you to data wipe or remove a mod that might be interfering.
Please avoid bringing up issues with your favourite gapps package. If a bug only exists with gapps, it's not my problem.

Changelog

[03/03/2021]
March security patch (android-11.0.0_r32)

[20/12/2021]
January security patch (android-11.0.0_r27)
Fixed camera crashes

[04/12/2021]
Updated LineageOS apps and frameworks

[13/12/2020]
LineageOS 18.1 - Android 11 QPR1

[30/11/2020]
Fixed boot after encrypting with a lockscreen set
Updated LineageOS apps and frameworks

[B]16/11/2020[/B]
First release

Downloads
Official builds
Archived unofficial builds: sourceforge


Sources

• Gerrit
• 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_g5-common
• h830
• h850
• rs988

 

[Dlions]

Will los 18.0 be coming to g6

 

[lgg5.845lol]

hi will this work on h845 as well? if not, is it okay to flash h850 or h830 on my h845?

 

[ROMSG]

hi will this work on h845 as well? if not, is it okay to flash h850 or h830 on my h845?

No, it won't work, don't try flashing an h830/h850 ROM as flashing a ROM not meant for the variant of your device will most likely land you in an unfixable hard brick. Ask me how I know.

 

[Arda Süzen]

Great to see you with new topics! I will try soon as possible :good:

 

[lgg5.845lol]

No, it won't work, don't try flashing an h830/h850 ROM as flashing a ROM not meant for the variant of your device will most likely land you in an unfixable hard brick. Ask me how I know.

damn...sorry for that... its weird there's no new custom rom for h845, at least. on android 8 or 9 :laugh:

 

[ROMSG]

damn...sorry for that... its weird there's no new custom rom for h845, at least. on android 8 or 9 :laugh:

The h845 is very different from the G5 h850/h830/rs988 instead of the sdm 820 it uses the sdm 652. A much cheaper and slower soc. So you see the sources listed in the op.

Sources
Gerrit
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android...msm8996-common
https://github.com/LineageOS/android..._lge_g5-common
h830
h850
rs988

Even though @synescu has made a twrp pot almost all of these would have to be heavily modified to work with the g5 se. I tried to build android 7 for the se but the only device tree available is horribly out of date and even android 7 wouldn't build successfully ( @synescu who wrote this tree and made twrp for the g5 se has been inactive for a year). It also doesn't help that the g5 SE is very rare in the united states as it was a Europe exclusive and even using sites that will import from Europe the g5 se is super overpriced (sometimes even more than $300!) on the used market. So unless someone can find a g5 se for cheap a rom for the se won't be happening anytime soon, unfortunately.

 

[rfrazier]

When I try to build 18.0, all goes well. Then there is an error when it comes to signing the build. (I'm using the same scripts I use for 17.1, except s/17.1/18.0/g.)

   ERROR: Failed to run signapk.jar: return code 1:
Error: Unable to access jarfile /home/rfrazier/android/lineage/lineage-18.0/build/make/tools/framework/signapk.jar

And here's the command.

## Signing      
  echo "Signing the APK."

 time ./build/tools/releasetools/sign_target_files_apks -o -d ~/.android-certs \
    $OUT/obj/PACKAGING/target_files_intermediates/*-target_files-*.zip \
    signed-target_files.zip &>>${LOGFILE}

I suspect that it is operator error, but any suggestions would be welcome.

Best wishes,
Bob

PS signapk.jar exists in the directory in which I think i should be looked for: out/host/linux-x86/framework

So, I suspect that an environmental variable is being incorrectly set. Something to look into when I get some more time.
RLF

 

[tomb20]

Great to see more development for the G5, thanks!
How is the stability of this compared to Lineage 17.1?

 

[ajasei]

H820?

How about H820?

 

[tomb20]

How about H820?

As far as I know the H820 is not bootloader unlockable. There aren't any lineage builds for h820 anyway.

 

[rfrazier]

I think that the signing problem is related to a change in /build/tools/releasetools/common.py, and more particularly in changes to the following.
class Options(object):
def __init__(self):

Now if I could only read it (not being a programmer). I guess I'll give it a go later.

Best wishes,
Bob

 

[rfrazier]

Yes, something is definitely going on there. I hardwired in the path in /build/tools/releasetools/common.py , and it was built and signed just fine.

class Options(object):

  def __init__(self):
    # Set up search path, in order to find framework/ and lib64/. At the time of
    # running this function, user-supplied search path (`--path`) hasn't been
    # available. So the value set here is the default, which might be overridden
    # by commandline flag later.
    exec_path = sys.argv[0]
    if exec_path.endswith('.py'):
      script_name = os.path.basename(exec_path)
      # logger hasn't been initialized yet at this point. Use print to output
      # warnings.
      print(
          'Warning: releasetools script should be invoked as hermetic Python '
          'executable -- build and run `{}` directly.'.format(script_name[:-3]),
          file=sys.stderr)
#    self.search_path = os.path.realpath(os.path.join(os.path.dirname(exec_path), '..'))
    self.search_path = "out/host/linux-x86"

The last commented out line
self.search_path = os.path.realpath ...."
was replaced with
self.search_path = "out/host/linux-x86"

I haven't figured out the logic of the rest of the stuff, so don't know what's wrong with it.

Best wishes,
Bob

PS I tried a dirty update (on my spare phone), but it didn't work. I had to format data. It might have been because I had Magisk installed and that messed up the recovery partition, but I'm not sure. In any case, after formatting data it came up just fine. I haven't checked much yet, but WIFI works.
RLF

PPS It looks like a mistaken assumption about the location of the .jar file related to the file which calls it, i.e., that the files should be in the same subdirectory as common.py(c), which calls it, i.e., build/make/tools/<framework ...>. While, actually, the files are in out/host/linux-x86*/<framework ...>.

*Or, whatever platform is being used.

Unless, of course, one is supposed to do something to get those files (.jar lib) into the correct directories.

In any case. hardwiring isn't ideal, but at least it works.

RLF

 

[rfrazier]

Since it was working okay on my spare phone, I decided to give it a go on the phone I used. It installed okay, I set it up okay, got all the apps installed okay, etc. NFC works (yubico), BT works (keyboard). Unfortunately, I decided to encrypt. Wouldn't work. Said my data may be corrupted, I would have to format data and start again. Bummer.

And, of course, it was harder than ever to back up settings, including app settings, so, mostly, they aren't. There's an area ripe for improvement.

Note to self. Try encryption on the spare phone before even contemplating putting it on the main phone.

Best wishes,
Bob

PS I have /tmp/recovery.log, if anyone wants to see it. Although it may not be as useful as it could have been, as I reinstalled system on a whim before the last time of giving it a shot.
RLF

PPS I reinstalled, and everything seems to be working smoothly. Although I haven't tried much beyond basic call, NFC, BT, wifi, and the like. I'll try encrypting again, on my spare phone, in a couple of weeks, perhaps when the December security update comes out.
RLF

 

[tremalnaik]

Thank you for the time you spent trying to check what's working and what's not. There was an annoying bug in the previous LineageOS versions: IR blaster doesn't work, or works once and then you need to reboot the phone to use it again. Can you please test if it works in 18.0? It's an underestimated feature that I use on a daily basis. This bug was the main reason, together with the lack of camera apps better than the G5's default (and G7's camera port, also based on LG framework), why I never used Lineage for more than a couple of days before reverting to stock based roms.

 

[rfrazier]

I didn't see IR blaster in the pull-down from the status bar, and didn't see it in the connected devices section. Also, I don't think that I have anything amenable to being blased by IR.

Best wishes,
Bob

 

[DrowningInFreedom]

wifi - works
bluetooth - works, and so does AudioFX, listening to music works great
ir blaster - not working |Confirmed working (with bug, can only blast one command before losing functionality, restarting device restores functionality for one blast) in latest 17.1 build|
encryption - not working, hangs after reboot on animation boot |Confirmed working in latest 17.1 build|
nfc - unknown, couldn't test since my G3's seem to have issues also
auto rotate - works
camera - works, front and back
torch - works

testing done on h830

quite the shame about how bugged the ir blaster is, my G3 running latest lineageos build blasts great.

 

[rfrazier]

NFC works - G5 (h850) Yubico Authenticator, with YubiKey 5 NFC.

 

[DrowningInFreedom]

whoops, reflashed between 17.1 and 18 a lot, during one of the quick setups of 18 I forgot to uncheck the box for lineageos custom recovery, but went back to uncheck it before finishing the rest.

TWRP still got erased and now with LineageOS recovery, whats the easiest way back to getting TWRP?

(I know I could reflash 20A and dirtycow, but i'm hoping for a cleaner way)

 

[rfrazier]

whoops, reflashed between 17.1 and 18 a lot, during one of the quick setups of 18 I forgot to uncheck the box for lineageos custom recovery, but went back to uncheck it before finishing the rest.

TWRP still got erased and now with LineageOS recovery, whats the easiest way back to getting TWRP?

(I know I could reflash 20A and dirtycow, but i'm hoping for a cleaner way)

Just flash it using fastboot. Look at the lineage wiki entry for your device.
Best wishes,
Bob