[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)

re-add: d2tw (double tap to wakeup), huge thx to [MENTION=4956374]aoleary[/MENTION] who spend the time to find all relevant commits

You can disable or enable d2tw in the Android settings ofc but if you enable it (default) consider to also enable the "Prevent accidental wake-up". In my tests it made not a difference of the detect behavior of dt2w in general but it prevents turning on the screen when your phone is in your pocket.

NOTE: This re-implements dt2w as we had it before. That means:

same bugs,

same latency,

often enough not working so that it is annoying,

with one little exception: I fixed 1 bug when the double tap gets detected but the screen does not turn on. still .. its not that reliable as we want it to be.

regarding battery drain concerns: one of my devices have this running since 7 days with not much usage, 3 hours SOT and still 20% of battery. so no, I don't think that dt2w drains the battery more, at least not usually. I could provide kernel builds without the dt2w patches if enough users want that though.

platform security patch: 2019-12-05

re-add: skiaGL instead of OpenGL. skia is the new and faster renderer coming with pie by default. I had it disabled here as it had graphic glitches in the past which seems to be fixed now.

skiaGL should be enabled properly even on a regular clean flash but to ensure the new (and faster) graphic renderer is in place you can do this:

adb shell getprop debug.hwui.renderer

If you get an empty result it means skiaGL is active.

If for any reason you wanna go back and enforce OpenGL you can do so by

temporary (immediately active):

adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer opengl

persistent:

boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=opengl" >> /system/build.prop
sync
reboot

new: camera app pinning. Regardless of which camera app you are using LOS will pin that one in memory and so load it faster next time

fix: boot debug logs are generated properly now

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,touch-sensitive, fast, furious and simply beautiful new LOS version -

ever

:D

.-