[G4 Android Development] 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

Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)

Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)

Flash LOS - DO

NOT

choose to reboot afterwards - stay in TWRP.

TWRP menu: "Mount" --> choose "System"

From a terminal execute:

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

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.

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.

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

.

(See the FAQ #2 of this thread how to do this)

fixed: extreme low brightness levels are possible now (request by [MENTION=8039462]tfotakis[/MENTION] )

fixed: brightness levels are now working as they should with clean and smooth steps

If the brightness fixes do not work for you you have an unknown lcd panel. Solution:

send me the output of your cmdline:

if magisk/los root-addon:
adb shell
su

if no magisk/root-addon: enable root for adb in Settings -> System -> Developer options
adb root
adb shell

then in both cases:
cat /proc/cmdline

fixed: auto brightness levels optimized

fixed: priv app permissions causing a bootloop when installing TWRP as system app

new: optimized GUI rendering (thx to [MENTION=4956374]aoleary[/MENTION])

new: when doing a full clean flash the defaults for quick tiles and brightness level have been adjusted

platform security patch: 2019-09-05

reminder: system apps permissions are enforced now, 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..

The above fixes are brought to you by the Suicide Squirrel Team :victory:

ok enough of words, just

one

more thing:

flash and enjoy this butter smooth, bright shining, secure and simply wonderful new LOS version -

ever

:D