yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] steadfasterX:
yes thats what I thought (just the modem).

you should check the OP of this thread (topic Requirements) and flash the linked bootloader stack for the h815 20p - UsU:

h815_UsU_20p_bootloader_20p_modem_TWRP-flashable.zip (ensure you select the "UsU" one and

not

the mixed one with 29a modem)

and before doing anything ensure you have an ARB of 0 (start SALT and you see it).

PS: ARB = AntiRollBack (rest in the UsU FAQ or simply in my signature..), KDZ = LG firmware file in a specific format (kdz. like zip, rar, ..).

.-
[G4 Android Development] zohar_ml:
Sadly, I still have the same boot loop.

I have ABR=0

TWRP installed the file h815_UsU_20p_bootloader_20p_modem_TWRP-flashable.zip (after MD5 check) (in the process it prints “preparing to flash H815 29A modem” , should it not been 20? No errors in the process.

Reboot to system, but still the boot loop, getting to that blue-green circle of the LOS animation.

Did a regular clean install, but same result.
[G4 Android Development] rundumdieuhr:
Can you try a full clean install? You install no additional packages after the ROM, right? Could there be any remainders of Magisk, for example?

Oh, and steadfasterX provides usu specific ROMs in a dedicated directory: http://leech.binbash.rocks:8008/lineage/pie/h815-UsU/

Did you see that?
[G4 Android Development] zohar_ml:
I am SO ASHAMED … I’ve installed the h815 and not the h815-UsU !!!

Downloaded the h815-UsU version and new I have a G4 with a wonderful clean and nice ROM.

[MENTION=5545101]steadfasterX[/MENTION] Thanks for all the time you put into this!
[G4 Android Development] steadfasterX:
Omg i even didn't thought about that one lol! Thanks for helping dude! :)
[G4 Android Development] stlstl:
Hi,

I'm also having issues, if there's many apps in the background the phone starts to lag to the point it's unusable. Closing the apps or restarting the phone solves the problem.

My phone isn't rooted but I do have root via ADB enabled in the developer options. How can I apply the new LMK values? Is there a way to do it via recovery? I don't want to root it for safety reasons, it's my main phone.

Right now I get su: not found

Thanks
[G4 Android Development] guillefs:
not work in H815P , lineage-16.0-20200515-UNOFFICIAL-h815_usu.zip not install in TRWP .

this package is for device: G4,p1,h815

this device is

ERROR 7

EDIT: MODEM 20P. !SOLUTION!
[G4 Android Development] Daniel071:
Make sure you've enabled adb root in developers settings

Then run

adb root
adb shell

After that, you can apply the echo command in this post
[G4 Android Development] Feduz:
anyone have problems with 4g connectivity? with the stock nougat I could navigate in 4g, after update, I never saw this.. (it's enabled in the option)
[G4 Android Development] owlery_hk:
i managed to catch one at 1523.

there were some before that but not sure if it was captured in the log.

i still have not been able to catch ones that results in the phone not recognising the sim card unless i reboot it.

will post logs when i catch it.

https://paste.ubuntu.com/p/25KtR7nwJn/

thank you steadfaster!

edit: got one!

https://paste.ubuntu.com/p/pfFkYFFcrs/
[G4 Android Development] Daniel071:
Even with the LMK value applied,

(I ran this earlier today)

echo '2560,5120,12800,17920,25600,51200' > /sys/module/lowmemorykiller/parameters/minfree

my phone completely locked up. It stopped responding though I managed to get a log with ADB. I've also noticed that the LED light was stuck on bright green. It didn't respond for over 15 minutes so I pulled out the battery.

I also noticed that the last line of the logcat was

\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\

I don't know why this happened, I ran the PS and FREE commands though they didn't appear in this logcat.

Here is the logcat:

https://gist.github.com/daniel071/d40b06a4b7ab239c48efc92acfb21a39

EDIT:

My phone completely locked up again, I had to pull out the battery, after I rebooted I took a logcat.

This time I had applied this echo command:

echo '10240,12800,30720,51200,30720,115200' > /sys/module/lowmemorykiller/parameters/minfree

Here is the new logcat:

https://gist.github.com/daniel071/b040a42654a1d5adc5e10e362bc6a74d
[G4 Android Development] stlstl:
Hi,

I've applied the values tree days ago:

2560,5120,36096,79360,108288,115456

Since then the phone didn't became unresponsive.

Have you updated the web view? The browsers would freeze sometimes before I installed and enabled the latest version.
[G4 Android Development] falenjam:
Yes, I can confirm too that the phone runs better with these values.
[G4 Android Development] vertian:
Camera hangs

Hi, the camera app hangs and doesn't load. I cannot playback video either.

This is a US991 which was unlocked using UsU and flashed with lineage-16.0-20200515-UNOFFICIAL-h811.zip via TWRP install. There is no added root or kernel images flashed yet.

I will note that I previously flashed lineage-14.1-20200612-UNOFFICIAL-h811.zip followed by h811_los_boot_build-3-nougat.img. The camera worked, but video recording or playback did not.

paste.omnirom.org/view/aa2342d3
[G4 Android Development] Daniel071:
I've got a new issue now,

While I was using my phone, it just suddenly stopped responding (again), I pulled out the battery and attempted to reboot. I saw the LG Logo, and then after that instead of a LineageOS boot animation, it was completely blank. I tried to access TWRP to get boot logs, when it asks me if I wanted to "Factory data reset", I selected "Yes" though after that, it froze and didn't boot into TWRP.

I tried booting into download mode, but it's not booting up anymore (even while its charging, no battery preview shows up)

Is my device bricked?
[G4 Android Development] steadfasterX:
that one was wrong (I told that in my prev post as the last value must be higher then the one before)

your device is getting too hot dude! expect the ILAPO one day..

your issue is related to an RIL issue (which I can't solve)

thx dude for sharing that!

Follow FAQ #7 and share these logs.

well sorry. The ILAPO starts exactly like this :( especially when looking at your above logs where your device is getting too hot. Thats why I implemented the thermal engine again which at the end causes lagging to users which are in high risk for the ILAPO - or are close to have it.

you can verify that by: flashing the ILAPO twrp image and boot to it, if that works while the current one does not it is 100% the ILAPO.

you can checkout my signature on how to proceed (mainly flashing an own boot image by the "X core guide" linked there)

gl

-.
[G4 Android Development] Daniel071:
I used the pressure method and my LG G4 powered on! The only issue now is that its in a bootloop and never boots into LineageOS. I couldn't even boot into the Factory Reset Screen. I couldn't access download mode nor TWRP.

I contacted LG Warranty Support and they told me that they will fix the boot loop issue for free, and there is an unlimited warranty for boot loop issues. But because their "system" only accepts American addresses, I have to wait 3 months for one of my relatives to move in.

I looked for replacement motherboards but they were either unavailable or very expensive. I'll try the hairdryer method and maybe the Advanced disassemble method and see if that will fix it for me.
[G4 Android Development] stlstl:
Hi,

After the boot this is what I have in the minfree (before changes):

7680,10240,30720,51200,30720,76800

Could the 5th value cause the issues?

How can I make the changes in the minfree permanent?

Thanks
[G4 Android Development] vertian:
boot_lc_crash.txt

paste.omnirom.org/view/b1344b98

boot_lc_full.txt

del.dog/gefyjysucr

boot_lc_kernel.txt

del.dog/ococrestag
[G4 Android Development] stlstl:
Hi,

I've recently installed the previous ROM and can't spare the time to reinstall and configure everything in my phone right now.

How can I add the command "echo '2560,5120,36096,79360,108288,115200' > /sys/module/lowmemorykiller/parameters/minfree" to a script that runs at startup? I've created the userinit.sh script but it seems SeLinux doesn't let it run.

Thanks
[G4 Android Development] steadfasterX:
you dont need to re-configure anything. just follow the faq to do a regular clean flash and flash the latest version (ok plus flashing gapps and magisk if you need those)

there is no need to (tbh it is a bad idea) using a custom script here. just modify the existing one.

for that boot TWRP/SHRP and:

adb pull /system/vendor/bin/init.qcom.post_boot.sh

--> modify that file with notepad++ or sim (NOT with any MS bull**** tool like word etc)

then follow just step 3 from here:

https://xdaforums.com/showpost.php?p=82776203&postcount=1597

.-
[G4 Android Development] owlery_hk:
I guess it is time to move on and get a new phone then.....

The xperia 5 ii looks interesting.

Thank you for all the dev work you have been doing.

Just flashed the new june build.

All seems well and functional, but I have not tested it in details yet.
[G4 Android Development] sciss1968:
I'm currently testing on one of my three H812-USU which have the videolag patch.

I started with a full clean install. (including internal storage)

Install LOS + videolag + gapps + magisk 20.4.

Install keep spinning (40 minutes) on the downloading updates.

Had to pull my battery and retry.

Experienced quite a few slowdown when accessing apps.

Phone hard freeze three times so far....

Once when closing Pokemon Go.

Once when playing with the camera.

Once when Pokemon Go was idle.

Dragging and moving objects is not fluid.

Unlocking the phone with schema is also not fluid.

Will continue my tests after work today.

Average temperature while playing Pokemon Go seems to be a little hotter than with AOSiP.

** Update **

I redid the installation again from scratch. Full wipe and data format.

I experienced another two hard freeze.

Graphical issues...

A Pokemon Go screen with 8-9 nearby pokemons is slowing the phone so it is barely usable.

But when there's less details (like the pokemon capture screen) it is ligthing fast.

I reverted to my backup for now. Will attempt again in a few days.
[G4 Android Development] Feduz:
I have already installed the rom, now I want to flash the last trwp like you said in OP:

Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #8 for how to upgrade your bootloader stack witbout lgup).

.... and for your convenience I have alternatively created TWRP flashable files for that !!!! (click)

How can I know if my H815 is 20p or 29a? thanks
[G4 Android Development] rojanor:
app crash

Hi again :)

I finally came around to try your option 2, however the app (vipps) is still refusing to start (security check failed on rooted device blabla). Could you please take a look at the logcat? Thanks :)

https://paste.omnirom.org/view/d1d95440
[G4 Android Development] steadfasterX:
could you pls install and run this app:

https://play.google.com/store/apps/details?id=com.scottyab.rootbeer.sample

and ofc share the results ;)

.-
[G4 Android Development] steadfasterX:
you get catched by multiple issues here. Caused by an incompatible modem partition.

This prevents RIL from working:

12-31 18:00:13.542 0 0 I [ 5.300015 / 01-01 00:00:13.531][2] ueventd: firmware: loading 'mba.b00' for '/devices/soc.0/fc880000.qcom,mss/firmware/mba.b00'
12-31 18:00:13.609 0 0 E : [ 5.373329 / 01-01 00:00:13.603][3] pil-q6v5-mss fc880000.qcom,mss:[B] modem: Invalid firmware metadata[/B]

This causes audio issues:

12-31 18:00:12.736 0 0 I [ 4.503440 / 01-01 00:00:12.731][1] ueventd: loading /devices/soc.0/fe200000.qcom,lpass/firmware/adsp.mdt took 7m
12-31 18:00:12.744 0 0 E : [ 4.510996 / 01-01 00:00:12.739][3] subsys-pil-tz fe200000.qcom,lpass: [B]adsp: Invalid firmware metadata[/B]

This prevents camera from working:

06-29 09:56:26.286 0 0 I [ 51.514909 / 06-29 09:56:26.280][3] ueventd: firmware: loading 'venus.mdt' for '/devices/soc.0/fdce0000.qcom,venus/firmware/venus.mdt'
06-29 09:56:26.302 0 0 E : [ 51.532214 / 06-29 09:56:26.296][0] subsys-pil-tz fdce0000.qcom,venus:[B] venus: Invalid firmware metadata[/B]

This all together means you might have used a modem partition in the past with ARB higher then it is currently. Actually thats the only thing making sense here.

For example if you ever had used the Video-lag-fix before then we would just see venus incompatibility but as we see even baseband (mbXX) it seems you just flashed a wrong modem partition.

Which modem partitions did you flashed in the past (exact versions / links)? Remember loading an ARB based modem partition (as it is the case for your model) means you cannot revert back to a lower ARB and that is the case including the modem partition.

.-
[G4 Android Development] hamed_forum:
i use this gapps

open_gapps-arm64-9.0-micro-20200627.zip

its ok?
[G4 Android Development] rojanor:
"seems" like im rooted, LOL :)

This is with your newest build with full wipe (lineage-16.0-20200629-UNOFFICIAL-h815.zip) with opengapps pico, and the modified boot.img (ro.debuggable=0)

Any suggestions? :)
[G4 Android Development] steadfasterX:
yes sure thats the detection system behind your app so as all is opensource we will find out why.

can you drill down where it said failed (test keys is the only interesting one) or is that just static?

can you please also share a log as usual from before starting the app and after finished?

.-
[G4 Android Development] User_99:
Should work...
[G4 Android Development] vertian:
I flashed G4_29a_N_modem_UsU.zip from androidfilehost.com/?w=files&flid=239970 according to your instructions found at part 1 of your installation instructions 'for UsU'd devices only'
[G4 Android Development] steadfasterX:
US991 requires an US991 modem partition. The G4 universal one is not working for you and as there are no US991 users out there (it seems) there was never the need to upload a specific one.

The OP states clearly that the best option is to use your backup for that:

View attachment 5054753

if you do not have a backup of your modem partition you have to:

1. find out your ARB (SALT)

2. download a KDZ with exactly that identified ARB (SALT will show ARB before extract) - even better you will see in SALT the last known official firmware version, so best is finding exact that one to avoid issues with ARB etc. never just use the latest one you can find as ARB will likely be increased. Regardless if you use that one shown in SALT or any other: always verify the ARB matches your current one.

3. extract the modem partition from that KDZ (SALT) and flash it in fastboot:

fastboot flash modem modem.img

4. tell me the ARB and KDZ filename, then zip and share the modem partition so I can upload it for others :)

Feel free to do step 4 also when you have a backup of course ;)

.-
[G4 Android Development] vertian:
The camera works now! Video does not, however. It reads 'Camera error - Can't connect to the camera'. I tapped 'REPORT', if you would like a log (boot or logcat) I would be happy to.

I used US99121a_02_0620.kdz

ARB 2

filedropper.com/modem
[G4 Android Development] steadfasterX:
Good.

Yes share both boot log as before and as written in faq 1 the specific issue logcat
[G4 Android Development] Vetal_ca:
H815

Used to be on previous build. Slowdown became unbearable at times, especially when maps, navigation or Chrome involved. Kind of get used to unavailability and frequent restarts, even while driving.: navigation, Android Auto + Waze became slow so losing navigation at a times

With latest (2020-06-29) seems to be fine now in most scenarios.

H815 + GApps (2020-06-30)

Thank you for your job! Not everyone writing here but a lot of people use LG G4 with LOS
[G4 Android Development] steadfasterX:
Regarding video recording switch to opengl (search this thread for opengl or skiagl)

Or wait for next build. I will switch back to opengl again.
[G4 Android Development] vertian:
I made the switch to opengl and the problem persisted.

logcat.txt

del.dog/ullelecuwu.log

dmesg.log

del.dog/nilypefene.txt
[G4 Android Development] stezo2k:
This ROM is brilliant. It's so quick and haven't really noticed any issues. No camera video issues at all. Even using the latest GAPPS and that works great too. Best pie ROM I've used yet. Keep up the good work
[G4 Android Development] falenjam:
H815 freeze

Hello steadfasterX,

The last build clearly improved on slowness we used to experience :good:

But I still have freezes from time to time, particularly when charging the phone (and it becomes noticeably hot also).

I managed to get a logcat just before the device stopped responding. Here is the paste: https://paste.omnirom.org/view/56953cac

I hope it will help you fix this issue and thank you for your investment in the community!
[G4 Android Development] steadfasterX:
thx for your report.

Unfortunately the log is not enough for that kind of issue.

try to reproduce the issue then follow this guide:

https://xdaforums.com/showpost.php?p=82758511&postcount=1594

.-
[G4 Android Development] falenjam:
It's done ;)

Here is the file:

https://paste.omnirom.org/view/0632a757
[G4 Android Development] steadfasterX:
well .. your issue is that it gets too hot and these are coming a lot - which then causes system resets to avoid damage of your phone:

07-14 15:47:15.407 0 0 E [19150.562834 / 07-14 15:47:15.385][5] msm_thermal: msm_thermal_bite TSENS:0 reached temperature:116. System reset

TL;DR

as your device gets too hot the thermal engine I've added some builds ago ensures that it does not overheat by stopping the system.

There are at least 2 possible reasons for that:

1. the environment temperature is unusual hot

2. you see the first signs of the ILAPO here

you can try to charge in powered off state and check if it gets unusual hot (a bit of heat is normal) there as well. If it does: ILAPO for sure.

you can also try an older build or different ROM to see if it behaves different there.

.-
[G4 Android Development] busattovini:
So I have finally moved to a new phone. I want to thank all devs for being so amazing and keeping it alive. It was awesome trying these builds on the legendary G4. Bye! ❤️
[G4 Android Development] owlery_hk:
what did you change to?
[G4 Android Development] Root_newvie:
Hi, I installed this rom to my G4 but my problem is I feel the instagram stories are kinda laggy now. Is there a solution for this?
[G4 Android Development] Gigio755:
Same here, thank you so much everyone, i will keep G4 as a backup phone and will continue to install latest los release :cowboy:
[G4 Android Development] masemoel:
Hello guys. Here same too, I am getting the Redmi K30 5G (Picasso) next week as my G4's battery died.

I will miss the G4 and this community :( Good luck to the developers and keep on!

---------- Post added at 00:23 ---------- Previous post was at 00:22 ----------

Look at the ROMs changelog (the December one) the way to change the renderer to OpenGL. It worked for me!
[G4 Android Development] Root_newvie:
It worked for me, too. Thanks!
[G4 Android Development] Root_newvie:
Not so necessary but I wonder if there is a way to bring lg knock code lock and double tap shut down function to this rom? I know this rom also turns off the screen when double tapped but it works only when tapped on the upper side of the screen.
[G4 Android Development] steadfasterX:
This is (almost) pure LOS. For (more) fancy stuff use one of the other Android flavors.. there are a few out there for the G4.. maybe there is one having that included.

.-
[G4 Android Development] stlstl:
With Microsoft launcher you can enable double tap to turn off the screen.
[G4 Android Development] 99913308:
Is slimport working?
[G4 Android Development] Root_newvie:
Is there a way to reflect the phone screen on TV wirelessly in this rom? I tried miracast but it says no devices were found.
[G4 Android Development] steadfasterX:
no won't work on any pie ROM bc this hasn't be solved: https://github.com/Suicide-Squirrel/issues_pie/issues/27

.-
[G4 Android Development] Root_newvie:
Could you solve it in the upcoming builds? I think it would be amazing.
[G4 Android Development] Benshilla:
Flash LOS

Hy,

I'm a newbie here and know nothing,

Here the dumb question : how to "flash LOS" ?

Thx
[G4 Android Development] jjcdennis:
Steadfaster, thanks again for the update. Sent a beer your way.
[G4 Android Development] User_99:
Via recovery plus GApps in you want. All written here in the forum....
[G4 Android Development] steadfasterX:
Note:

If you require GPS skip the last version. It seems there is an issue in there.

For those who had flashed the latest version pls get a log for gps (specific issue - reproduce to get gps location)
[G4 Android Development] rundumdieuhr:
Confirm. I just had Google Fit on my G4 track my run. It got a GPS fix quickly so I figured it was fine and departed. On my return, however, I noticed there has been a 15 min GPS loss while tracking. Will amend this post with a log once I get one.

Edit: [MENTION=5545101]steadfasterX[/MENTION] Can you see if this report of the concerned timeframe contains anything helpful, a relevant log particular? Otherwise I'd need to start from scratch along the logcat guide. But as I mentioned, the GPS was there at first and restored itself 15 min later without interference.

https://drive.google.com/file/d/1jgp_R3D-qXZ3KwpDc5XjY7XRGKKJUHrY/view?usp=sharing

I haven't run into any other problems, I think this (and the previous) build are really quick! Reverted GL is an improvement as well. Thank you for all your work!
[G4 Android Development] Root_newvie:
Hi, my problem is that while chatting, when I try to take the second picture on whatsapp after the first one to send someone, the app stops working. That's not a big deal but if there is a solution, I'd be happy to know. Thanks!
[G4 Android Development] kessaras:
my bad. i removed the gnss hal because i thought we have a proprietary one. i didn't realise it was a mistake because of a dirty build. I mean, without proper cleaning steps, i kept using the gnss hal i removed. Anyway. Hold on couple of days and i'll push it back. i'm just making sure that this really was the issue.

EDIT:

Yes i did update gps and it does work. And magnetic readings work. I just did this little mistake with the gnss hal. So next build will have it fixed.

EDIT_2:

Yup, indeed. gnss hal !

Now gps reports:

01-02 01:42:05.171][5] init: starting service 'vendor.gnss_service'...

fixed. As soon as sfx builds, it's back to working state again
[G4 Android Development] steadfasterX:
sounds like that one: https://github.com/Suicide-Squirrel/issues_pie/issues/35

atm there is no one working on that topic so maybe try the workaround mentioned there.

.-
[G4 Android Development] karomann:
Got bootloop with opengapps pico 20200718, successfully installed pico 20200714 (after cleaning data). So far so good.
[G4 Android Development] hamed_forum:
I have same problem

Whenbootloop how to can go recovery mode?
[G4 Android Development] Daniel071:
To go into the recovery mode for the LG G4:

With the device powered off, hold Volume Down + Power until the LG logo appears, then release Power for a second and hold it again until the recovery comes up.

You may have a prompt asking if you want to "factory reset" the device. If you have a custom recovery installed, you can select "Yes" and it'll boot into the recovery.
[G4 Android Development] kessaras:
maybe i can do something about that.

Try the latest build (maybe it's been fixed) and create a logcat while the crash happen and send me a link of the log on the issues https://github.com/Suicide-Squirrel/issues_pie/issues/35

If you crash , i will also need a kmsg.

with adb as root

adb root

Do a

adb shell cat /dev/kmsg > whatsapp_crash-kmsg.txt

and go crash it again. After crash press control+c at terminal to stop the logging. Send me the "whatsapp_crash-kmsg.txt" created and maybe i can fix it ;)

EDIT:

i logged it myself. I can't fix it. the problem is at the closed source camera hal from LG which we use. No code to edit, no fix there :( sorry
[G4 Android Development] dat_benjie:
Can confirm it works. Installed Micro Gapps 14/07/2020

Cheers for that :)