[G4 Android Development] steadfasterX:
BREAKING NEWS

I've decided to create a Telegram group for all stuff around Android : here

and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here

.. ah well and yea:

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)

If you encounter any overheat or lagging issues follow this:

adb shell
logcat -b all -d | egrep -i "thermal|kill" > /sdcard/Download/log.txt
ps -A >> /sdcard/Download/log.txt
free -m >> /sdcard/Download/log.txt
logcat -b crash -d >> /sdcard/Download/log.txt
exit
adb pull /sdcard/Download/log.txt

Share the log.txt as an attachment of your reply (bc txt is fine for that) or - as usual - by your favorite paste service

Build signing. You may now the "Trust" feature by LOS telling you if the build is trustworthy or not?! It checks if selinux is enforcing (it is in my builds) and if non-default signing keys (I sign my builds with my own ones from now on) are in use.

The signing keys are also important when it comes to OTA updates (it downloads, checks if the signature is mine, rejects if not or accepts and installs if).

From this build on my LOS 16 builds are signed and can also be manually verified if needed: Details

Introducing OTA update support. From this build on any

next

build can be downloaded Over The Air (OTA). I have setup an own server for that now :highfive:

Platform Security Patch: 2020-08-05

Note: avoid flashing GAPPS newer then the

build date

. Best practice is using 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.

Btw: did you know there is now a very easy way to get back your privacy and having a complete google-free phone? Check out /e/ OS! (yes even LOS without GAPPS communicates a lot with Google servers..)

...... 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

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, full of magic and simply beautiful new LOS version -

ever

:D

.-