[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

REQUIRED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

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

Thanks (again) to [MENTION=4956374]aoleary[/MENTION] for his continues work on kernel and other parts!

complete re-work of the thermal handling, throttling and performance increase

The kernel handles hotplug of all cores if needed (just HIGHLY optimized now), while frequencies will be handled by the resurrected thermal-engine service.

Fully explained:

KERNEL

DEVICE TREE

Before, when I had started a video capture it was like I could cook a meal on the G4 after 5 min latest.

Now its getting just warm. Ofc that comes with a little drawback as when reducing frequencies the system will get slower - but not as as slow as when unplugging the whole core(s) (which was the case before my changes).

That means optimized throttling (as integrated in the above experiment build) is better for your performance then hotplugging (current stable LOS).

At least it should.

If you encounter any overheat or lagging issues or just being curious how this thermal stuff works grab/monitor the log while/after doing high cpu usage tasks:

adb logcat -b all | grep -i "thermal"

h815/h815_usu: switching back to LTE, GSM/WCDMA instead of just LTE, WCDMA for the preferred network.

switching to Anxiety I/O scheduler

revert rounded corners

platform security patch: 2020-05-05

Note: do not flash GAPPS newer then the

build date

. Recommended is to switch to a life without google anyways (see FAQ #9) but if you rely on Google then use GAPPS which are released at least 1-10 days before the build date. If you flash later versions it MIGHT work but a lot of weird issues can happen so better avoid it.

...... and more. Read "Full details"

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 lightning fast, even more secure, coooooool(ing) and simply beautiful new LOS version -

ever

:D

.-