[G4 General] steadfasterX:
current state and (unsorted) to-do list for the public release (the major ones)

For stuff already

DONE

read the previous posts.. (XDA search on this thread with term: "to-do list for the public release")

H818 Touch is not working (this will

not

delay the release - I very likely will release without support for the h818 first)

I need to fix or at least get a proof of a workaround if someone encounters issues like the h818. For this I work together with jmefcon as I do not own that device but we both have a real life so it takes its time

if you have C knowledge and want to help? Click the button:

--> analyzing root cause (again) and identify the real issue -> 20%

Current assumption: the lge.sim_num=2 is not enough and it seems it "just" can not load the firmware PLG468 maybe due to a wrong smem address

Besides that the 2 dmesg files are from different devices and they seem to have a different LCD panel?! wtf..

If anyone wants to help:

Working

H818 dmesg,

Non-Working

H818 dmesg

H818 kernel sources

Product ID ident: here

The complete diff 1 (left = working, right = not working) => https://www.diffchecker.com/TDXZ6i6U

The complete diff 2 (left = working, right = not working) => https://www.diffchecker.com/0kaYDl9h

unify REAL model detection

unified UsU kernel --> 25% I am able to load the module but file open is still failing here. I guess its too early started atm.. will try to figure out where the best init start is first (where mmc is initialized)

Anyone else here with C knowledge willing to help? This part is f** hard. Atm I'm really sick of this.. so if you have C knowledge and want to help? Click the button:

The idea is "easy" ;)

https://github.com/Suicide-Squirrel...lob/UsU_testing/drivers/soc/qcom/usu_detect.c

I want to:

Step 1:

Open a file (in this case a device) read from a given offset and print the result. Tbh for devices which are not unlocked by UsU it will contain binary stuff so we need to ensure it is readable but that's for step 2.

Step 2:

Detect unreadable output i.e binary crap and replace it by an empty string nor sim throng

Step 3:

Based on the result of 1 and 2 I want to modify the cmdline as the REPLACE stuff does here:

https://github.com/Suicide-Squirrel...5ce6#diff-603376ac7b8737d94a63e7a29e1574b7R88

Tbh I want to just call my own function before the replace happens.

The goal is to replace LS991 by the real model taken from 1 but only if it was not empty / binary crap.

Thats it.. lol. Atm I'm able to see the print statements so my functions get called but as soon as I try to use file_read it just hang on boot. No last kmsg ramoops after that or kernel crash. Just hang.

As this is kernel level we have to use vfs_read..

Keep in mind that I can speak Bash even when sleeping and a bit of python but all this low level C coding is... Well if can read and modify but writing.. Is a complete different story.

stuff that happens on the way..

UPDATE: build FWUL 2.6 with SALT v3.8 --> 100% --> FWUL v2.6 has been released.

IMPORTANT NOTE: Ensure you use the latest FWUL version when using FWUL in forgetful mode! when you have FWUL in persistent mode ensure you update SALT to

v3.8

!

creating release thread including the full glory guide

UPDATE: Content --> 100%

UPDATE: Release thread --> 90%

Getting a proof for every device (would be nice but optional / running in parallel)

Keep in mind: UsU will work for

ANY

LG G4 model and does not care about country specific ones, too! When I say:

ANY

, I

MEAN

any!

The only device which is a real special one because of different hardware (2 SIM slots) is the

H818

which

can

be unlocked but has issues (see above)

unconfirmed

(read the above!):

F500 --> I need

you

- write me a PM with the model name as subject plus a link to your SALT debug log (while phone is connected)!

H819 --> I need

you

- write me a PM with the model name as subject plus a link to your SALT debug log (while phone is connected)!

US991 --> I need

you

- write me a PM with the model name as subject plus a link to your SALT debug log (while phone is connected)!

confirmed:

H810 (confirmed) --> https://xdaforums.com/showpost.php?p=75126190&postcount=298 and https://xdaforums.com/showpost.php?p=75736723&postcount=456

H812 (confirmed) --> https://xdaforums.com/showpost.php?p=75126190&postcount=298

H815 (confirmed) --> My own one! and https://xdaforums.com/showpost.php?p=75086602&postcount=276 and https://xdaforums.com/showpost.php?p=75737617&postcount=458

H818 (confirmed)* --> https://xdaforums.com/showpost.php?p=75133410&postcount=307 * SEE ABOVE REGARDING THE CURRENT ISSUES

LS991 (confirmed) --> mine and 2 others (no link available - IRC only)

VS986 (confirmed) --> https://xdaforums.com/showpost.php?p=75109841&postcount=293

Thx all for your patience ... We are very very close now!.... :fingers-crossed: :victory: :victory: :fingers-crossed:

sfX