yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] rundumdieuhr:
Read https://wiki.lineageos.org/devices/h815/install#installing-lineageos-from-recovery

Vol down + Power has not worked for me either on some occassions. Vol up in addition works for me essentially always:

One hand fingers Vol up + Vol down + other hand finger Power

–> wait for LG logo, release Power

–> After 1-2 sec, press Power again until Reset prompt appears

–> Yes, wipe, yes confirm
[G4 Android Development] hamed_forum:
Press power down and hold it down. Put battery back while keeping vol down pressed. Press power button and keep now both buttons pressed. Directly you see the LG logo the first time just release only the power button for 1 second ( do not release vol down ) and then press power again and keep both pressed until you see the factory reset screen. Proceed like you would to the factory reset (as long as TWRP is installed it will not reset but just open TWRP instead).

This method work
[G4 Android Development] steadfasterX:
ah nice thanks! something learned again. will pick these, too to keep 16 updated!

I cant rem that we had this issue ever seen before on pie(!) and: I cannot re-produce it here on my h815 -> video recording is just working fine. do you have tried to re-produce this on my build or just tested on yours? Thats the first thing I would suggest to try (trying my build).
[G4 Android Development] sdembiske:
OK - I'll back up in TWRP first and try your build as you've suggested. Just a heads up, the last officially merged in security patches were P_asb_2022-04 so you'll have to repopick topics from P_asb_2022-05 through P_asb_2022-08.

I'm still wondering why this has started occurring as I have been using your posted roomservice.xml file for 16.0 and I'm not sure when it started occurring as I rarely use the video recording function.
[G4 Android Development] steadfasterX:
well yea it depends tbh. when you have used the LGgFour repo then this is the reason. on the Suicide repo it should be not an issue. at least I was able to re-produce the problem in the latest eOS pie build (which also uses the LGgFour repos).

As Suicide is dead I am currently revamping everything in LGgFour org and checking which change introduced this bug. it was def not there before. so no need to do anything on your site atm.
[G4 Android Development] sdembiske:
I was using the Suicide roomservice.xml file when this first occurred and had it up-to-date, so I'm not sure either why or when it started ...
[G4 Android Development] metropical:
I've had to wake up the G4 whiie I await parts for another newer phone.

Is this ROM a lot more stable and even just a little quicker them the OEM on Android 6?

Even launching gmail is stoopit slow.

Magisk 20.4. Mangaer 7.5.1.

H81120x

TWRP 3.2.3
[G4 Android Development] steadfasterX:
Could you retry to build on the latest manifest and repo changes? But not suicide thats dead. Use the LGgFour ones (Link in the OP has been updated).

You've less bloat on any non stock which alone makes things running faster. Besides that a lot of optimizations have been done in all parts of the ROM and kernel. But the only way to find out is trying on your own. Many (including me) feels it runs way smoother.

But beware of the limitations flashing any(!) custom ROM has:

- no fm radio

- no LG camera app

- no VoLTE

Update TWRP with the latest PREVIEW variant though.
[G4 Android Development] metropical:
no fm and LG crappy camera app. Don't care.

but isn't VoLTE basically 4G LTE therefore only 4G for voice?

Gotta check what bands T-Mo US is on as compared to what the G4 has.

WiFi and BT OK?
[G4 Android Development] steadfasterX:
no VoLTE creates a VPN tunnel to your provider for enhancing the quality. any known issues are in the known issues topic.
[G4 Android Development] metropical:
much better explanation of VoLTE then I've seen anywhere. Thanks.
[G4 Android Development] steadfasterX:
ok investigating.. I can re-produce it like that: factory reset. boot. cam works (incl video). reboot. cam stops working. Will check and test and let you know when I find smth
[G4 Android Development] metropical:
if the ROM is no better or doesn't cut it for me, can I just factory reset to get back or do I need to go the whole RUU routine?
[G4 Android Development] steadfasterX:
thanks to @sdembiske I've noticed that we can still get Security Patches for pie. not in an official manner but well still from the LOS gerrit.

Thanks again dude and so we have new builds now for LOS 16 on the latest and greatest patch level 2022-08-05 :)

also new in these build(s):

- wifi /bt mac fix

- switched to the latest and greatest TITAN kernel branch

have fun..
[G4 Android Development] sdembiske:
Any progress on this video recording issue? Latest LGG4 updated roomservice file has not solved. I'm willing to test any potential solutions or help in any way I can.

Thanks,

S.
[G4 Android Development] bollux78:
Hi, how did you unlock the H815P bootloader??
[G4 Android Development] steadfasterX:
works perfectly fine here.

do you ever flashed the Video Lag fix?
[G4 Android Development] sdembiske:
Yes, I had previously flashed the Video Lag Fix, back when the issue was first discovered and we tested the fix - do I need to flash it again or ... ?
[G4 Android Development] sdembiske:
Check this thread out:

[UNLOCK][UNOFFICIAL][G4] Unlock ANY* LG G4 device with UsU​

As the bootloader cannot be "Officially" unlocked through LG any more, this is the only 'safe' way to do it. Read everything thoroughly and make sure you understand it and then follow the instructions exactly.
[G4 Android Development] steadfasterX:
Pls read the readme within the lag fix.. ;)
[G4 Android Development] sdembiske:
Oops: "My memory is like RAM - always too small and volatile". (Author: steadfasterX) - Too much time had elapsed to remember the little 'important' details ... will flash it again ...
[G4 Android Development] sdembiske:
Same issue after doing regular clean flash, 'Can't connect to camera" - flashed the Video Lag Fix immediately after the rom flash and before open gapps.

What's interesting is that in all previous installations I have not had to re-flash the Video Lag Fix and everything continued to work. I'm still thinking that this may be a result of all the fixes that were done to get the camera working in LOS 17 and 18 ... ?

@steadfasterX

Addendum: Cleared Camera cache and data and video recording is now working - Thanks for the suggestions - appreciate it.
[G4 Android Development] thedery01:
hello steadfasterX the truth is that the work you do with these roms for the lg g4 is very great, I would like to know if you can help me with my problem, it turns out that I have the lg g4 h811 version I flash the rom and everything without problem, but sometimes I feel sorry that slows down using the rom and heats up a little, I don't have restart problems or anything, is there a solution to this problem so that the rom works better, it only happens to me in the roms, it's as if the performance drops when the cel is heated , thanks for the great job of keeping the lg g4 alive
[G4 Android Development] steadfasterX:
Yes when the system overheat the cpus will be throttled to avoid damage. We tightened that behavior a bit more since the time we discovered the ilapo to give devices with the ilapo hw fault more time to live. What are the first 3 digits of your serial (can be found on a sticker behind the battery)?
[G4 Android Development] thedery01:
Thanks for the prompt response, but unfortunately the label on the back is a bit worn and I can't distinguish which model it is. although I thought that the ilapo was if the phone restarted or stayed in the logo, like mine it does not have any of those problems because I did not pay much attention to it, but anyway, if the performance is going down something it is not good since It is not normal for this to happen in roms, does it have a solution in case it is ilapo
[G4 Android Development] steadfasterX:
the model is not important the first 3 digits of the SERIAL is. anyways the ILAPO has several stages. it always starts with that the devices gets very warm, throttling due to that and this will become worse when flashing new ROMs or rebooting often. at one day it will not boot anymore and so on. all written in the ilapo thread. also possible solutions (X cores guide would be the first thing to do). https://xdaforums.com/t/guide-ilapo...xit-list-index-for-all-known-methods.3667688/
[G4 Android Development] thedery01:
well, thank you very much, then I'm going to go in and see if I can solve it, you're great bro, thank you very much for your attention, then I'll go in and do all the steps of the cores x guide
[G4 Android Development] keeepinitgansta:
Nice! Thanks!
[G4 Android Development] Valwit:
Awsome work!

I'm using an older build from 2021, the only annoyance is the not working NFC. but i downloaded the latest build, gonna give it a clean new try :) tried to install it over, ended up in loop at bootloader, hehehe :)
[G4 Android Development] steadfasterX:
Thx. If you've a h815 then your bootloader is likely not on 20p or a full clean flash is required.
[G4 Android Development] Besonderss:
What page is FAQ #8 on?
[G4 Android Development] steadfasterX:
You want to flash the bl stack the hard way? Well page 1, post 2.

Or for the easy way in the OP under requirements the link to the twrp flashable files
[G4 Android Development] Valwit:
it is possible. is there any way to check it? current os version is 16.0-20210608. and seriously: apart from NFC i see no issues
[G4 Android Development] steadfasterX:
Yes there's a way: fetch the bootloader stack with SALT , extract all kdz files which may be installed currently and use hashes to compare. Or.. simply flash the TWRP bootlader file which doesn't hurt (when flashing the correct one).

Not sure if that fixes your issues with NFC though. Here it worked fine but that does not mean anything bc it depends on what you wanna do. You can also try to disable selinux at a first try .
[G4 Android Development] mvn77:
Help! After installation, I can not set the screen lock. I go through all the steps in the setup, but in the end there is no blocking.
[G4 Android Development] steadfasterX:
factory reset done? if not do so. if you have it done also to a format data, see FAQ full clean install
[G4 Android Development] em181_1:
Hello, I'm having sound, camera and sensor issues with this rom in my LG G4 H812, the files that I flashed were h812_20z_modem.zip, and lineage-16.0-20220131-UNOFFICIAL-h812_usu.zip.

[LOGS:]

boot_lc_crash.txt

boot_lc_full.txt

boot_lc_kernel.txt

(by the way, how are y'all doing)
[G4 Android Development] steadfasterX:
thx for the logs. ok first of all ensure you re-read the UsU thread and consider doing the same for the whole UsU FAQ as it might answer some questions.

From the UsU OP:

View attachment 5842873

so as you flashed the baseband package on an UsU compatible ROM (identied by "UsU" in the ROM file name) you should flash your modem partition back. the baseband is needed only for ROMs which not providing UsU compatible builds.

After that do a "full clean" flash (see FAQ) of this ROM and see what happens.

Note: do not flash anything else yet, no magisk, no gapps, nothing but the ROM.

If the issue persists share the logs again, pls.
[G4 Android Development] em181_1:
Thanks for the reply, I'll try that as soon as I get home.
[G4 Android Development] em181_1:
I'm still having the same issue even though I re-flashed the ROM and the * untouched * modem without anything else. Here are the logs:

[LOGS]

boot_lc_full.txt

boot_lc_kernel.txt

boot_lc_crash.txt
[G4 Android Development] steadfasterX:
maybe I am too late but these logs are gone. consider a paste service (with long timeout) or use github gists
[G4 Android Development] em181_1:
Thanks for telling me!

New logs:

boot_lc_crash.txt

boot_lc_kernel.txt

boot_lc_full.txt
[G4 Android Development] steadfasterX:
Ok that looks pretty clear:

subsys-pil-tz fe200000.qcom,lpass: adsp: Invalid firmware metadata
adsp-loader qcom,msm-adsp-loader.33: adsp_loader_do: pil get failed,
adsp-loader qcom,msm-adsp-loader.33: adsp_loader_do: Q6 image loading failed

Translated that means the firmware in your modem does not match with the device's ARB level. This particular issue regarding adsp is related to sound and sensors and it also has a domino effect on things like the cam which crashes when that is not loaded.

Adsp is part of the baseband zip. Ofc that is not needed on an UsU compat rom but well there are edge cases. Your device might not be a real h812 but a frankenstein and due to the fact that you correctly flashed the baseband it increased the arb level on adsp and modem firmware. My current assumption is that the original untouched firmware is not working anymore due to the arb. while using the baseband zip is not compatible with your specific device likely bc its a frankenstein (see usu faq). So .. how to proceed? Well to be sure flash the baseband again even though this is an usu rom and fetch the logs again pls.
[G4 Android Development] em181_1:
Ah, makes sense since I bought this G4 from ebay.

btw new logs with flashed baseband:

boot_lc_full (baseband).txt

boot_lc_kernel (baseband).txt

boot_lc_crash (baseband).txt
[G4 Android Development] em181_1:
OK, so I took apart my LG (which I should've done a long time ago) and I found out that it is actually a H810, so you were right, steadfasterX.

How do I proceed now? Do I re-UsU it with the H810 zip instead of H812? Or what should I do????

edit: nvm, I read this thread and it looks that I'm f❤️❤️❤️ed, and the only way to revert it is to get a new motherboard right?!?!? or did I misunderstood?

(pic of motherboard below!)
[G4 Android Development] steadfasterX:
thanks. same error there so ig its a frankenstein

ok it IS a frankenstein. yes unfortunately you have blown fuses (on adsp) which is irreversible which means you have to live with it as it is or u have to replace the mainboard..
[G4 Android Development] em181_1:
Thanks for telling me 👍
[G4 Android Development] xzenx1234x:
I am asking you very sincerely for help and support. Please give me tips. Which LineageOS Android version for LG G4 H815 - has full support to run DSU? I need DSU to run properly - so I can run the Pixel Experience Custom Rom Android image.

I kindly ask you for tips for me.
[G4 Android Development] lukasz152q_:
Hi, is it possible to disable rounded corners? I don't like the fact that the screen is square and a rounded interface is forced.
[G4 Android Development] aoleary:
What's DSU?
[G4 Android Development] aoleary:
Would need a recompile of the ROM, with the overlay removed.. Not sure if SFX is maintaining Pie anymore
[G4 Android Development] steadfasterX:
i guess he meant UsU ;)

Sent from HD1911 using ReLabs
[G4 Android Development] steadfasterX:
only the eOS one and there security patch integration only..

Sent from HD1911 using ReLabs
[G4 Android Development] lukasz152q_:
Thank you for the answer, do all newer ROMs have the screen rounding set up like this?
[G4 Android Development] aoleary:
No. We removed that in A10+, I think.

But LOS is not maintained anymore after Pie.

You can flash A11 (crDroid 7.39) or A13 (crDroid 9.13).

A13 has some lingering bugs, but A11 runs faster than Pie now..
[G4 Android Development] sdembiske:
@steadfasterX For the ' kernel_lge_msm8992' what is the difference between the branches of 'android-9.0' and 'android-9.0_titan' and what one should be used for h812_usu ? Thanks, S.
[G4 Android Development] steadfasterX:
always check the manifests I link in my OP's.

in this case: https://github.com/LGgFour/local_manifests -> and more explicitly: https://github.com/LGgFour/local_manifests/blob/lineage-16.0/roomservice.xml#L23

the _titan one was a try to get the latest titan one working in A9 (which fails)
[G4 Android Development] sdembiske:
I did check the local_manifest but wondered if the _titan was a newer version and what it applied to - Thanks, again
[G4 Android Development] girdap:
I think thats the best custom rom for lg g4, why no improvements? I do not understand?
[G4 Android Development] electronique13:
H, thank you for your answer :)

What do you mean by "then boot to recovery" ? Do you mean I should go in recovery mode by using the power+volume down methode ? If you meant that, I didn't manage to make it work, the phone ask me if I want to factory reset, if I say yes it does indeed factory reset, and boots normally, if I say no it boots normally, but no TWRP menu :(
[G4 Android Development] polfrank:
Yes, but if you have previously installed twrp recovery, it will not do a factory reset if you press yes, even if it says do. It will just take you to twrp.

The fact that in your case a factory reset is performed, means that you haven't installed twrp. And remember: you do not want to just boot it with "fastboot boot" (which doesn't work either way I'm Nougat). You want to install it, with the "fastboot flash recovery *recovery*.img" command.
[G4 Android Development] steadfasterX:
That's all described in the TWRP thread where this discussion belongs to anyways .
[G4 Android Development] electronique13:
Thank you for your help, I managed to make it work :)
[G4 Android Development] LukeSlovian:
Hello All very warmly in a good mood :) I inform you that I managed to upload the img image from TWRP Recovery myself, to the LG G4 H815 smartphone on the recovery partition. I gave Root permission - via Magisk Mask for TWRP applications, then downloaded the latest version of TWRP Recovery in the img file. I chose the flash tecovery option in the TWRP Recovery application menu. Now I have a bigger problem because after updating Android 7.0 Nougat to Android 9.0 Pie. LG probably detected that I could commit corruption by unblocking the bootloader. I would like to delete this message that appears. Therefore, I am asking you with a very cordial request for your technical support, how should I remove this message.

https://photos.app.goo.gl/LTrdNxa5oWQU6wmF6
[G4 Android Development] steadfasterX:
https://xdaforums.com/g4/development/rom-lineageos-16-0-t3929082/post79512652
[G4 Android Development] horvalos:
It seems that nothing works for my G4... I've checked everything also the translation was correct the setting at developers options is called "wireless display certification" but neither did work... :confused:

Edit:I tried and I can cast through YouTube to my TV but I still can't cast my smartphone screen... :confused:
[G4 Android Development] rundumdieuhr:
Screen casting has been an issue in G4's Oreo LOS. https://github.com/Suicide-Squirrel/issues_oreo/issues/7

Might be present in Pie as well. Contribute a log if you can, please.

YouTube casting is another function (server-based pairing instead of Wi-Fi Direct) so not comparable.
[G4 Android Development] busattovini:
It's working PERFECTLY. Thank you!
[G4 Android Development] MEMO#22:
Is this LOS build 64-bit?
[G4 Android Development] aha360:
No - it's for the Zilog Z80 CPUs.
[G4 Android Development] electronique13:
Hi ! So now lineage os is working but problem :

4G and phone calls are working but I can't receive/send sms, if I use another SMS app from the app store I can send SMS but I don't receive them, do you know why ?
[G4 Android Development] horvalos:
I've created a log and posted at github pie issues...:)
[G4 Android Development] LukeSlovian:
Will someone help me remove this message about my unlocked bootloader?
[G4 Android Development] steadfasterX:
Read the faq and share a log of both situations (one log when using the LOS app and a new one with your other app )
[G4 Android Development] horvalos:
Has anyone found a good version of Google Camera for our G4?
[G4 Android Development] Gigio755:
Try this one, i really love it: PerceptionGalaxy_6.2.030.apk

or always from Sani1y dev: GoogleCamera_6.2.030_stable_alt.apk

The cam quality i think is even better than the stock LG one
[G4 Android Development] horvalos:
Thanks for your suggestion,they are very similar i prefered the first one..I had found the perfect version for Nougat and i was searching a similar for Pie..Thank you again :laugh:
[G4 Android Development] sdembiske:
Confirming LOS 16.0 stock screen cast issues (as first reported by member [MENTION=6439522]horvalos[/MENTION] in post # 194) - failure to recognize device(s) - device: Roku 2

Stock screen cast does not recognize the Roku media player whatsoever. The Roku app (downloaded from Play Store) recognizes it right away and plays a short home video, recorded with Cinema FV5, with no buffering issues, etc. Two other screen cast apps, downloaded from Play Store, also recognized the Roku quickly but had huge buffering issues etc., on the same video play.

LOS 16 stock screen cast log: https://gist.github.com/sdembis/0b91bd87bdf45cea1ae7d88b20869e98

Roku app screen cast log: https://gist.github.com/sdembis/3626509edfcd7851412adacbf861b696

Same issue with the stock screen app on LOS 15.1 was noted as well.

Perhaps it's only geared to Chromecast/Google devices? It really should be able to handle most smart TV's, media players, etc., in this day & age.

Thanks,

S.
[G4 Android Development] raptorddd:
are this nightvision.?

---------- Post added at 12:06 AM ---------- Previous post was at 12:05 AM ----------

are this nightvision and does it work.?
[G4 Android Development] polfrank:
They are night vision but it doesn't work.

For me, the Galaxy one is smoother.

Hey let's continue this conversation on the dedicated Google camera thread! (If anybody has something more to ask.)
[G4 Android Development] steadfasterX:
New builds are cooking...

In progress (in that order):

H812

H810

Done:

H815

H811

H815 UsU

VS986

Noteworthy Changes:

LOS stuff

sec patch level
[G4 Android Development] busattovini:
Thanks! You're the best.
[G4 Android Development] steadfasterX:
New builds are cooking...

In progress (in that order):

all done

Done:

H815

H811

H815 UsU

VS986

H812

H810

Noteworthy Changes:

LOS stuff

sec patch level
[G4 Android Development] sperelli:
My favourite calls list keeps on resetting now and then.

Out of nothing.

Does anyone have a clue?
[G4 Android Development] busattovini:
Battery is 10/10 ?
[G4 Android Development] belrik:
Updated but still seeing lag. Left phone for 5 minutes after start-up and first unlock works ok but after that unlock sometimes lags out when unlocking and I have to pull the battery out.
[G4 Android Development] wotofoko:
I have an issue with the in-call voice volume. It is too low to the extent that if I am outdoors and there is some noice I can hardly hear anything.

It only happens with LineageOS (tried 15 before and now also 16). Whenever I go back to another rom the in-call voice volume is back to normal.

Any suggestions? :)
[G4 Android Development] steadfasterX:
Do you have a SIM inserted ?

You mean the handset not the speaker right?
[G4 Android Development] wotofoko:
Exactly, sorry for no clarifying that.
[G4 Android Development] serhat190562:
H818P

Is it working on H818P dual sim version LG G4 ?
[G4 Android Development] raptorddd:
i think yes if U.S.U method is done.
[G4 Android Development] Sir Daniel III:
I have the same issue as he does; first reboot lags a lot and I have to wait for a couple minutes for the phone to become responsive again. I have an unprovsioned SIM in my phone.
[G4 Android Development] steadfasterX:
If he has no SIM inserted his issue is different that's why I'm asking. That issue was described here https://github.com/Suicide-Squirrel/issues_pie/issues/20

The regular lagging on first boot is described in the well known issue see here: https://github.com/Suicide-Squirrel/issues_pie/issues/15
[G4 Android Development] Sir Daniel III:
Is this just a Pie problem? I'm not sure if I remember booting load issues back on Oreo...
[G4 Android Development] steadfasterX:
Depends again on what you mean but the continues rild crashing when no SIM is in is Pie only .