[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] LineageOS 16.0

[jjcdennis]

I have noticed that my battery life has gone down maybe a factor of 50% with the Nov rom. I'm having trouble producing a logcat. I get this error when entering the log request - logcat -b all -d -D > /sdcard/Download/logcat.txt
/system/bin/sh: adb: not found
127Ih812_usu:/ #

Still get the error, so I pulled the logcat directly from the phone. I am still finding reduced battery life, maybe 50% and am looking for help in determining why and how to fix.
The second error I am now getting is the No Sim Card - No Service. The "Mobil Network" settings are all greyed out. This started after a reboot which I did to try to run the logcat. Phone sat all night and this error
was still shown on the phone. Rebooted - no sim card error is gone, but still no phone service.
Thanks for any help offered.

https://paste.ubuntu.com/p/tBW3qMbrb3/

 

[steadfasterX]

I have noticed that my battery life has gone down maybe a factor of 50% with the Nov rom. I'm having trouble producing a logcat. I get this error when entering the log request - logcat -b all -d -D > /sdcard/Download/logcat.txt
/system/bin/sh: adb: not found
127Ih812_usu:/ #

Still get the error, so I pulled the logcat directly from the phone. I am still finding reduced battery life, maybe 50% and am looking for help in determining why and how to fix.
The second error I am now getting is the No Sim Card - No Service. The "Mobil Network" settings are all greyed out. This started after a reboot which I did to try to run the logcat. Phone sat all night and this error
was still shown on the phone. Rebooted - no sim card error is gone, but still no phone service.
Thanks for any help offered.

https://paste.ubuntu.com/p/tBW3qMbrb3/

regarding battery: try to turn off GPS and see if that helps. I had done a lot of optimizations here which might affect battery life though. Unfortunately this test won't help much unless your SIM issue isnt solved (as SIM detection errors will do big battery drainings..)
regarding logcat: Im just guessing here but if you are at step 4 where you want to pull the log: this has to be done from your PC not in the adb shell..
regarding sim issue: for this only option "C) FULL BOOT log (requires Linux / FWUL)" could help .. I will add a special boot logging to one of the next builds which will make this obsolete but atm its the only way.

.-

 

[jjcdennis]

regarding battery: try to turn off GPS and see if that helps. I had done a lot of optimizations here which might affect battery life though. Unfortunately this test won't help much unless your SIM issue isnt solved (as SIM detection errors will do big battery drainings..)
regarding logcat: Im just guessing here but if you are at step 4 where you want to pull the log: this has to be done from your PC not in the adb shell..
regarding sim issue: for this only option "C) FULL BOOT log (requires Linux / FWUL)" could help .. I will add a special boot logging to one of the next builds which will make this obsolete but atm its the only way.

.-

Unfortunately I am a away and have no access to my laptop with linux/fwul on it. Would a TWRP recovery to 9/17 make sense for now?
I reflashed 09/17 and everything is working properly again.

 

[falenjam]

according to the logs it might be "just" an issue with a limit.. you can test this if you like:

adb root && adb shell (or adb shell and su)
ulimit -n 4096

Re-produce the issue and regardless if it works or not share a new logcat again.

It might NOT help depending on which limit will exceed but lets give it a try.
Note: The ulimit setting will NOT survive a reboot, i.e. after a reboot you have to re-do that cmd.


.-

I executed the ulimit command and reproduced the issue. Here is the logcat:
https://paste.omnirom.org/view/download/f2a498a5
But it looks like the ulimit setting does not survive after leaving adb shell because "ulimit -n" then returns "32768".

 

[masemoel]

I'm having some problems with SIM detection sometimes too.
But I haven't seen any battery draining as far as i know.
And WiFi hostpot with 5.0GHz is still not working.
Nevertheless, this ROM is the best by far at this moment, and it's worth upgrading!

 

[FerdiCildiz]

working very smooth, fast and awesome. better than aoscp rom on the LG G4 h815 usu'd. Thanks a million!

 

[I-Immortal]

Hi, being tired of the random reboots I had on my officially unlocked H815, I clean flashed the latest ROM along with the 20P Bootloader and Modem TWRP zip in the OP of this thread.

Apparently I had an old version of the bootloader and modem (I noticed some changes during boot since I flashed the new bootloader). Sadly I cannot connect to the mobile data network (E, H+, LTE) anymore. When I activate the mobile data nothing happens. I also sometimes get no signal at all.

What can I do to get back my mobile network data to work again please ?

 

[masemoel]

Hi, being tired of the random reboots I had on my officially unlocked H815, I clean flashed the latest ROM along with the 20P Bootloader and Modem TWRP zip in the OP of this thread.

Apparently I had an old version of the bootloader and modem (I noticed some changes during boot since I flashed the new bootloader). Sadly I cannot connect to the mobile data network (E, H+, LTE) anymore. When I activate the mobile data nothing happens. I also sometimes get no signal at all.

What can I do to get back my mobile network data to work again please ?

Have you checked the APN of the SIM ?

 

[I-Immortal]

Have you checked the APN of the SIM ?

Yes, the APN was properly set up. Since then I tried to do a full wipe of my device and then flashed LG-H815_Official_v29A_keepsTWRP-LAF.zip but sadly I still have no mobile network (SIM is detected though)...

I really don't know what to do now.

EDIT: After this I went to TWRP again, did a full wipe again, then flashed the 29A/20P bootloader and modem zip, then the ROM + Magisk + open Gapps and it finally works !!
All of this was really weird...

 

[steadfasterX]

New builds are cooking...

I have added a test in my jenkins build process to ensure that the unified device tree is working as it should.
Unifying our device tree makes it much easier to maintain and to add other not-yet added models - while it comes with the risk something goes wrong when it comes to blobs.

Nevertheless:
I would highly recommend doing the following (I have done that in my manual builds but you get it from jenkins - so there is a tiny little chance of bad luck .. ):

Pre-Cautions | Flashing instructions

1. Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)
2. Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)
3. Flash LOS - DO NOT choose to reboot afterwards - stay in TWRP.
4. TWRP menu: "Mount" --> choose "System"
5. From a terminal execute:

   adb shell md5sum /system/etc/firmware/venus.mbn

6. Compare the value (last 4 characters is fully enough) with these:
   If you flash:
   h815, f500, h818, h819 it should be: d1f6fe863643b1e8d1e597762474928c
   h810, h811, h812, ls991, us991, vs986 it should be: 78e5cf520d0de4a413ef1cfa7bbbe713
   WARNING: If that checksum is NOT as it should be: DO NOT PANIC! simply FLASH the PREVIOUS LOS version BEFORE booting!. This will ensure you will not blow a fuse.
   While the above test should be considered safe: If you are unsure about this procedure: WAIT before flashing until someone (or I) had done the above quick test from the builds jenkins is providing at my leech server.
7. Whenever an error occurs while flashing in TWRP (e.g "E1001: Failed to update system image.Updater process ended with ERROR: 7")
   or if the above checksum does not match:
   provide the recovery.log (FAQ #4 A)!!
   ... then flash the previous LOS version to get back to life - without harming your device.
8. if instead (as we all expect) all went well and you had opengapps before - ensure you reflash gapps

Cooking order & LIVE cooking view

• H815
• H811
• H815 UsU
• VS986
• H812
• H810

Live - View:

• Normal view: https://shebang.binbash.rocks:8800/...0/job/Build all LGE-G4 models/workflow-stage/
• Blue Ocean: https://shebang.binbash.rocks:8800/...-G4/LOS-16.0/Build all LGE-G4 models/activity (click at the top line )

Noteworthy Changes:

Flashing method: "REGULAR CLEAN FLASH" is recommended while not required
(See the FAQ #2 of this thread how to do this)

• fixed: vibrator intensity too strong (reports on this are welcome as I hadn't the time to test) EDIT: from the reports I got this has NOT been fixed. Thx for your feedback
  
  
• platform security patch: 2019-11-05
  
  
• reminder: system apps permissions are enforced, too.
  If you convert (e.g by titanium backup) an app to be a system app it may not allow it to boot anymore!
  Apps & tools which provide TWRP flashable zip's should come with proper permissions already but if not LOS will not boot anymore. Good examples are OpenGapps or Magisk which both come with proper privapp permission confs.
  If you (really!) need to convert an app checkout the current integrated permissions before.
  If your app does not come with a flashable TWRP installer you can request to add your app by providing a log (FAQ 1 - option specific issue before starting that app) and I might add it.
  
  
• Full details:
  kernel: commits
  g4-common tree: commits
  g4 unified tree: commits
  closed issues (if any): github issue tracker
  LOS: all merged changes since last build
  

IMPORTANT:

• If you encounter issues try this first:
  

  adb shell
  su
  (or adb root when enabled)
  setenforce permissive

  Try again and if the issue is gone when in permissive mode: provide me a logcat as described here
  On step 3 I need the SELINUX log (option D)
  
  
• Taking a backup before is recommended - always
  

Keep in mind that almost all pie ROM's sharing the same common device tree (or main parts of it), same model device trees and for sure the same kernel - so you can enjoy most fixes for any pie ROM available.. :victory:

ok enough of words, just one more thing:
flash and enjoy this a bit more secure, hand picked, fresh and simply beautiful new LOS version - ever





Sent from my OnePlus 6T using XDA Labs

 

[rundumdieuhr]

Keep in mind that we still on opengl graphic rendering here as I preferred a stable ROM instead of having a bit faster UI but graphic bugs like when using skiagl. The bugs in skiagl are much decreased while not completely gone and @kessaras and I trying to fix the rest. He found the bug in the code which might be responsible for that so a fix is possible . Regardless of the full fix I will switch to skiagl in the next build as the glitches are really very rare now.

tons(!) of kernel fixes & optimizations thx to @kessaras . That includes e.g the graphic driver as well (thats why I keep staying with opengl and not switched to skiagl as I first planned to)

Hi steadfasterX, may I inquire on what graphic lib the 16.0 ROM is currently basing: OpenGL or SkiaGL? Is there a toggle in developer options to play around with the other one?
Background for my question is that I encounter some reproducible glitches in the (vertical) middle of the screen when scrolling through apps, such as the Google app news feed and Onefootball article view (so not limited to opengapps which I first figured). These are not a disturbance, the ROM works fine. I just did not know such display glitches from 15.1 and thought I might assist with a log, trying different graphics options and posting it in github then anyway.
Thx

 

[steadfasterX]

Hi steadfasterX, may I inquire on what graphic lib the 16.0 ROM is currently basing: OpenGL or SkiaGL? Is there a toggle in developer options to play around with the other one?
Background for my question is that I encounter some reproducible glitches in the (vertical) middle of the screen when scrolling through apps, such as the Google app news feed and Onefootball article view (so not limited to opengapps which I first figured). These are not a disturbance, the ROM works fine. I just did not know such display glitches from 15.1 and thought I might assist with a log, trying different graphics options and posting it in github then anyway.
Thx

We are still on OpenGL until further notice.
interesting that you see glitches on openGL.. you can also try to enable GPU rendering for 2D drawing in the developer options to see if that helps.

You can easily test skiaGL by following this : https://forum.xda-developers.com/showpost.php?p=79514888&postcount=19

let me know your results..

.-

 

[steadfasterX]

I executed the ulimit command and reproduced the issue. Here is the logcat:
https://paste.omnirom.org/view/download/f2a498a5
But it looks like the ulimit setting does not survive after leaving adb shell because "ulimit -n" then returns "32768".

ok first of all pls do not share the "download" link to a paste. just the paste url.
ok the ulimit part "fixed" the symptom but as thought it was just that, a symptom.
sorry cannot look into that further atm. Feel free to open a bug report https://github.com/Suicide-Squirrel/issues_pie/issues with a log attached(!) to the issue and with time notes when you started the call and when the issue occurs (best is up to the seconds). Then I can take a look at that when I find the time.

.-

 

[pharham]

I have noticed that my battery life has gone down maybe a factor of 50% with the Nov rom. I'm having trouble producing a logcat. I get this error when entering the log request - logcat -b all -d -D > /sdcard/Download/logcat.txt
/system/bin/sh: adb: not found
127Ih812_usu:/ #

Still get the error, so I pulled the logcat directly from the phone. I am still finding reduced battery life, maybe 50% and am looking for help in determining why and how to fix.

Go to recovery and wipe Dalvik + Cache. That, somehow, fixed my battery drain problem.

 

[jjcdennis]

Go to recovery and wipe Dalvik + Cache. That, somehow, fixed my battery drain problem.

I moved back to 9/17 build, as I have no cell due to sim issues. I'm not sure that this has been fixed. The 9/17 build has good battery life and the sim/cell loads up quickly. Thanks for the suggestion.

---------- Post added at 02:42 PM ---------- Previous post was at 01:45 PM ----------

I installed new 11/19 rom and had no issues on reboot with the sim card. Cell booted up almost immediately. I did notice that my wifi was off and I had to set it up with the key. No big deal. Will keep an eye on battery life over the next day or so.
Thanks again steadfasterX

 

[vq8acsxht]

Quote/ Go to recovery and wipe Dalvik + Cache. That, somehow, fixed my battery drain problem. /Quote

On the H811 that seems to work. Battery drain was 12% in about 12 hours. 1% per hour. CPU was running at 12-20% all the time. On a clean install I wiped the Dalvik + Cache which did not help. THE KEY IS TO LET THE PHONE FULLY BOOT AND THEN WIPE THE DALVIK + CACHE AGAIN.

Now, the CPU uses less the 0.5% and battery is about 3% in about 12 hours.

 

[jjcdennis]

Quote/ Go to recovery and wipe Dalvik + Cache. That, somehow, fixed my battery drain problem. /Quote

On the H811 that seems to work. Battery drain was 12% in about 12 hours. 1% per hour. CPU was running at 12-20% all the time. On a clean install I wiped the Dalvik + Cache which did not help. THE KEY IS TO LET THE PHONE FULLY BOOT AND THEN WIPE THE DALVIK + CACHE AGAIN.

Now, the CPU uses less the 0.5% and battery is about 3% in about 12 hours.

Are you measuring consumption via the Battery tool included with the rom, or with a play store app?

 

[vq8acsxht]

Are you measuring consumption via the Battery tool included with the rom, or with a play store app?

Play store app Gsam battery monitor.

 

[Ximo F. Verde]

Battery drain here looks good, same as previous builds. Remember to wait for a couple of cycles after deleting cache.

 

[vq8acsxht]

Quote/ Go to recovery and wipe Dalvik + Cache. That, somehow, fixed my battery drain problem. /Quote

On the H811 that seems to work. Battery drain was 12% in about 12 hours. 1% per hour. CPU was running at 12-20% all the time. On a clean install I wiped the Dalvik + Cache which did not help. THE KEY IS TO LET THE PHONE FULLY BOOT AND THEN WIPE THE DALVIK + CACHE AGAIN.

Now, the CPU uses less the 0.5% and battery is about 3% in about 12 hours.

Edit: wow the battery consumption is amazing now. Overnight it used just 2% while GPS was on. Good job!
Before the battery used about 12% with gps off and 24% with gps on.