yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] steadfasterX:
ok finally had the time to look more deeply into this... and fixed it :)

I fixed the stupid brightness behavior as well where you see no diff between 0 and ~60% of the slider position.. and fine tuned the rest between 60 and 100% brightness, too.

pls send me the output of your cmdline:

if magisk/los root-addon:
adb shell
su

if no magisk/root-addon: enable root for adb in Settings -> System -> Developer options
adb root
adb shell

then for both:
cat /proc/cmdline

.-
[G4 Android Development] sbasil:
System - Advanced - Gestures - Jump to camera (-->off)
[G4 Android Development] busattovini:
Yeeeeah

Will the new build have it fixed?
[G4 Android Development] sutrus:
Result for H815, no USU, magisk

cat /proc/cmdline
sched_enable_hmp=1 sched_enable_power_aware=1 androidboot.selinux=enforcing console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 lge_monitor_thermal.enable=1 buildvariant=userdebug lge.rev=rev_10 model.name=LG-H815 lge.sim_num=1 lge.battid=SW3800_VC0 lge.bootreason=Reboot_by_PowerKey maxcpus boot_cpus=0-5 kswitch cc_mode=0 androidboot.bl_unlock_complete=true androidboot.dlcomplete=0 gpt bootcable.type=400MA androidboot.ddr_info=0x3b000306 fakebattery=disable lge.bootreasoncode=0x77665501 lge.hreset=off fips_allow_others=1 fips_panic=0 fips=0 androidboot.bootdevice=f9824900.sdhci androidboot.serialno=LGH8153b46f7b0 lge.signed_image=false lge.dsv_id=DW androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_jdi_nt36850_1440p_mipi0_cmd:1:qcom,mdss_dsi_jdi_nt36850_1440p_mipi1_cmd
[G4 Android Development] Over567:
Is there any way to install the G4's stock quick remote app? That's the only thing I miss from the original rom.
[G4 Android Development] a tiny ant:
Nope unfortunately it's reliant on LGs proprietary framework.

You could try Mi Remote from the play store. It seems to come pretty close.
[G4 Android Development] busattovini:
Code

h815:/ # cat /proc/cmdline
sched_enable_hmp=1 sched_enable_power_aware=1 androidboot.selinux=enforcing console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 lge_monitor_thermal.enable=1 buildvariant=userdebug lge.rev=rev_10 model.name=LG-H815 lge.sim_num=1 lge.battid=ISL6296_L lge.bootreason=0x776655ff maxcpus boot_cpus=0-3 kswitch cc_mode=0 androidboot.bl_unlock_complete=true androidboot.dlcomplete=0 gpt bootcable.type=400MA androidboot.ddr_size=3221225472 androidboot.ddr_info=0x3b000306 fakebattery=disable lge.bootreasoncode=0x776655ff lge.hreset=off lge.dsds=none androidboot.revision=11 fips_allow_others=1 fips_panic=0 fips=0 lge.signed_image=false androidboot.verifiedbootstate=green androidboot.bootdevice=f9824900.sdhci androidboot.serialno=LGH81550345ef8 androidboot.authorized_kernel=true lge.signed_image=true lge.dsv_id=DW androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_jdi_nt36850_1440p_mipi0_cmd:1:qcom,mdss_dsi_jdi_nt36850_1440p_mipi1_cmd
h815:/ #
[G4 Android Development] kinuris:
On the move from android:

sched_enable_hmp=1 sched_enable_power_aware=1 androidboot.selinux=enforcing console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 lge_monitor_thermal.enable=1 buildvariant=userdebug lge.rev=rev_10 lge.battid=DS2704_C lge.bootreason=0x20220c52 maxcpus boot_cpus=0-5 kswitch cc_mode=0 androidboot.dlcomplete=0 gpt model.name=LG-H815 lge.sim_num=1 bootcable.type=NO_INIT androidboot.ddr_size=3221225472 androidboot.ddr_info=0x3b000501 fakebattery=disable lge.bootreasoncode=0x20220c52 lge.hreset=off fips_allow_others=1 fips_panic=0 fips=0 androidboot.bootdevice=f9824900.sdhci androidboot.serialno=LGH815b8892dc2 lge.signed_image=false lge.dsv_id=DW androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_lgd_r69007_1440p_mipi0_cmd:1:qcom,mdss_dsi_lgd_r69007_1440p_mipi1_cmd usb.diag_enable=true
[G4 Android Development] busattovini:
"SURE" is also very good.
[G4 Android Development] MunemWerk:
Anyone knows how to implement the "knock to wake" feature? Is it like a kernel flash or something?
[G4 Android Development] breversa:
"Double-touch to wake" (DT2W) has apparently been disabled because it was buggy and power-consumming.

I tried to find the source, but could only find this : https://xdaforums.com/showpost.php?p=79528082&postcount=1223

I miss it a lot myself :(

I've found a workaround by using WaveUp : https://f-droid.org/fr/packages/com.jarsilio.android.waveup/

It's not perfect at all, but it's the best I've found so far. Any better option would be highly appreciated. :)
[G4 Android Development] Scooterthedude:
The aoscp 6 official oreo has DT2W on our device working. Didn't notice any more power usage then normal using it. But that's up to you if you want to go back to oreo.
[G4 Android Development] tonycfc:
I don't want to go back to Oreo. I love to use the latest Android! <3
[G4 Android Development] rundumdieuhr:
In case still needed (on Android 8.1 LOS 15):View attachment 4819307
[G4 Android Development] Alextrophysics:
Thank you very much [MENTION=5545101]steadfasterX[/MENTION] ! I finally was able to unlock with FWUL booted in a usb key, then followed the rest of the tutorials, installed this rom (I was sure for a moment that I bricked it) and in the end worked flawlessly! Just bought another battery and it's almost brand new! Now I can say "damn to you planned obsolescence"!
[G4 Android Development] sperelli:
which battery did u choose?
[G4 Android Development] mrcry:
great rom.

i've seen that there is a kernel folder on the site. do i need to install the latest available?
[G4 Android Development] Bullnados:
No, latest one is still implemted
[G4 Android Development] Alextrophysics:
A standard LG battery. I've found a small electronic shop in my city that sells old but unused stuff. They had a few new and unused LG g4 battery so I bought it!
[G4 Android Development] Korin67:
Hello, I have a problem boot the newest version of LOS16.0. The 0823 version boots without any issue, it is great. But not for the 0906 version. When I tried to boot it, purple led on/off more than 5 mins, then return to TWRP. I do not know how I can take log in this situation. Please let me know.
[G4 Android Development] Korin67:
With small experiment, I could boot the latest ROM. What I did is take out the boot.img from the 0823 version. In TWRP clean flash 0906 version, then install (overwrite) boot.img of 0823 version. This time when boot blue led on shortly as in the case of 0823 version, no purple led ofc, then the latest ROM booted. The boot.img included in the latest ROM zip does not match my phone? I am curious why other user do not have this problem.
[G4 Android Development] Gigio755:
Already installed this night before your post :cowboy:

Everything rock :cowboy: thank you
[G4 Android Development] Saturation.mvp:
Hi [MENTION=5545101]steadfasterX[/MENTION],

Thanks for you efforts :)

Is Google Duo issue solved yet?
[G4 Android Development] breversa:
[MENTION=5545101]steadfasterX[/MENTION] :

Do you have any idea on how would NanoDroid (https://nanolx.org/nanolx/nanodroid) work with that ? Also, what about the F-Droid privileged extension ?
[G4 Android Development] steadfasterX:
you would have seen that listed.. so no sorry.

F-Droid is included in LOS 16. Of course with the privileged extension and all necessary permissions to run both.

According to the nanodroid repo they come with proper permission confs so it might just work. No guarantees though so do a backup before testing.

.-
[G4 Android Development] tseeling:
you're not alone

I had the same problem. I was on 0628 and wanted to update to 0906, but the phone stayed at the "LG ..." power-on screen.

Luckily I could still boot to TWRP (the keys are a bit tricky timing-wise) and go back to 20190628 which worked - but only when flashed together with GApps. Flashing only the LOS file did not help.

I will download the latest zip and try again. If this doesn't work I'll replace the boot.img with an older one after flashing.
[G4 Android Development] steadfasterX:
See https://xdaforums.com/showpost.php?p=80153358&postcount=868 with details to the new priv-app permissions which are enforced now.

The kernels have been removed already as they were just a workaround and the reason for the previous issue have been fixed.

If you still encounter an issue with the todays build you should do a full clean flash, no gapps nothing. just LOS and try again. If that still fails (impossible but who knows) then let me know and I will share a permissive kernel for you to test.

.-
[G4 Android Development] jjcdennis:
Just noticed that there is a new version of the Lineage addon su (07 09) available - h**ps://download.lineageos.org/extras

Thanks again steadfasterX
[G4 Android Development] steadfasterX:
yep. solution is FAQ #1 - and in that guide: option "specific issue"
[G4 Android Development] tseeling:
success - mostly

I installed the latest zip and it still blocks at the power-on screen. Before wiping I wanted to try some more and uninstalled Magisk. This was mostly successfull - booting went on, the only "problem" now is a constantly flashing red light while booting. The flashing stops when Lineage is finished starting. I cannot install Magisk afterwards, or better: I can install, but it reports "not installed". When I try to install Magisk with the Manager app it tells me "model not supported". So I have to live without Magisk - not a big deal for me.
[G4 Android Development] steadfasterX:
whats your TWRP version? latest PREVIEW pie is required.

.-
[G4 Android Development] tfotakis:
Thank you very much! Really appreciate it! Great work! This is what I was looking for since KitKat.
[G4 Android Development] a tiny ant:
[MENTION=5545101]steadfasterX[/MENTION] I've since upgraded to a new phone and I'll be demoting my G4 to a carkit and/or emergency backup. You can forget about the watch plugin issue :)

Thanks for all the hard work so far, also [MENTION=5461026]kessaras[/MENTION] and [MENTION=8699949]ThePiGuy[/MENTION]

Cheers!
[G4 Android Development] sperelli:
Upgraded to latest update. Everything works flawless. Only IFont says it is unable to change font. Untill the latter rom upgrade, it worked.
[G4 Android Development] hteles:
Probably SELinux permissions.

Do as told by the master sfx asn grab some logs.
[G4 Android Development] tseeling:
I flashed 3.3.1-P207 a few minutes ago and still fails to install Magisk. Booting is ok although the red light is flashing all the time until start process is done.

Magisk install in the manager app says "unknown image format" for failure reason.
[G4 Android Development] steadfasterX:
my signature -> get recovery log after installing magisk

.-
[G4 Android Development] Lizenzloser Fahrer:
Thank you for the last update [MENTION=5545101]steadfasterX[/MENTION]. It runs flawlessly! My only problem with the phone is that I can't play games, because after a short time the phone gets very warm, the screen suddenly turns black and the phone simply restarts. I've tried several different batteries and tried to keep the phone connected to power while playing. Maybe this has something to do with kernel settings? I created a pstore.zip for this again as described in FAQ #6. Maybe this reveals the problem. https://ufile.io/598hc8j2

(But I have to say that playing games on a mobile phone is not so important for me. I remember, however, that I didn't have these problems with Lineage OS 15.1.)
[G4 Android Development] steadfasterX:
When temperature reaches 70°C LOS will shutdown to prevent damage .

Your log shows that:

msm_thermal:msm_thermal_bite TSENS:14 reached temperature:115. System reset

I can't do anything bc that's hardware related.
[G4 Android Development] masemoel:
And any way to disable that? Maybe msm thermal? (Habilitado= enabled)
[G4 Android Development] steadfasterX:
There is a reason why this shouldn't be disabled . Read about the ilapo / infamous bootloop..
[G4 Android Development] sperelli:
not selinux related at all. the app is updated to android 8, but it used to work on preceeding pie release.
[G4 Android Development] busattovini:
Here it's working perfectly! No bugs.
[G4 Android Development] djmgermanos:
I don't know how to do a log, sorry.
[G4 Android Development] pedrogcsb:
https://paste.omnirom.org/view/85cbc1c8

This is the logcat to the sound issue. I think I did it right. :P
[G4 Android Development] busattovini:
Is there a way to set the brightness even lower?
[G4 Android Development] steadfasterX:
Try https://play.google.com/store/apps/details?id=com.velis.auto.brightness
[G4 Android Development] steadfasterX:
Ok when did you started the logcat? the ghost call occured and then you started it? That's fine I just need to verify..

The next question I have is what was your actions or what you have done with the phone when the issue occurs ? Do you played music? Or pressed a button? Or was it just in sleep mode? Also do you have any third party music players installed?
[G4 Android Development] pedrogcsb:
I pressed the volume buttom and turned off the vibration mode. I started the logcat after that. The only music app I got its Spotify.
[G4 Android Development] steadfasterX:
so to be clear:

the ghost ring happens

you pressed vol button

you turned off vibration mode

you started logcat

is that correct???

I am wondering why it rings even in vibration mode then.. ?!

.-
[G4 Android Development] pedrogcsb:
Turned off vibration mode

The ghost ring started

Started logcat

It rang 2 ou 3 times and saved logcat
[G4 Android Development] steadfasterX:
does this happen always when you turn off vibration mode?

does it stop some-when from alone or do you need to turn on vibration again for stopping it?

.-
[G4 Android Development] pedrogcsb:
It happens 90% of the times i turn off vibration mode. Sometimes it does not ring instantly but it starts 1-5 minutes after.
[G4 Android Development] raptorddd:
does titan support f2fs.? and so does the twrp.?

is there a difference between oreo and pie in performance battery.?
[G4 Android Development] baconbacon:
I reinstalled the phone from scratch starting with UsU. Sound still does not work, so I wrote this to try and grab dmesg as high up as possible

for i in $(seq 1 50); do
echo "pass ${i}"
adb wait-for-device
sleep 1
#adb root
while true; do
adb shell su -c dmesg -c
#adb shell dmesg -c
[ $(cat "dmesg${i}.log" | wc -l) -gt 3000 ] && break
done >> "dmesg${i}.log"
adb shell reboot
sleep 10
done

toggle the commented out parts if the phone lets you do "adb root". So after 50 reboots this is the highest I could get https://pastebin.com/gY1pgn96 which is quite a bit higher then the last one I posted.
[G4 Android Development] rundumdieuhr:
Did you try this, [MENTION=6836148]pedrogcsb[/MENTION]?
[G4 Android Development] steadfasterX:
Yes your issue is clear and I have a fix but that has to wait until at least tomorrow sorry
[G4 Android Development] steadfasterX:
Do you still have ARB 0?

Do you ever had flashed the video lag fix?

Do you ever flashed a vs986 or h811 ROM ? If so which one ?
[G4 Android Development] baconbacon:
I think you accidentally responded to me twice, I hope the fix you mentioned above applies to me ;)

Just checked in salt, it's 2 now.

Yes, plus I checked all the files md5 on the phone and they match up.

Neither, only H810 and H812 in the past. H812 acted flaky.
[G4 Android Development] steadfasterX:
So you had ARB 0 some time ago and now 2.

that happens only when flashing another bootloader stack so which one has been flashed?
[G4 Android Development] baconbacon:
Unfortunately I'm not sure. I only have a screenshot of salt when I got the phone back from repair pre-UsU. That was almost a year ago now.
[G4 Android Development] steadfasterX:
well UsU does not change the ARB of the bootloader stack - at least not within the stage SALT is checking.

That means your bootloader stack

must

has been flashed (consciously or unconsciously) after your first ARB 0 screen.

For a fix of your current issue - which is not related to this thread or ROM:

open a new thread (Help forum)

mention my nickname there so I get notified

attach the latest dmesg you linked above there too

do a custom backup with SALT and backup: sbl1, rpm, tz, pmic and attach those as a zip file to that post as well

really the easiest way is when you remember and / or try to figure out which bootloader stack you had flashed

mention anything else you had flashed in the past (e.g. the Video lag fix)
[G4 Android Development] Lizenzloser Fahrer:
I almost thought so. Unfortunately our mobile phone reaches its limits. But as I said, the games are not so important for me. Thank you very much for the confirmation! :good:
[G4 Android Development] fi5z.x9:
Thank you [MENTION=5545101]steadfasterX[/MENTION]

Thank you [MENTION=8699949]ThePiGuy[/MENTION]

Thank you [MENTION=5461026]kessaras[/MENTION]

Thank you @Acleary

Thank you [MENTION=8451122]WiZaRd981[/MENTION]

Thank you [MENTION=238696]hards[/MENTION]tyI3r

I appreciate you'll the Suicide-Squirrel Team. Thank you all so so much. It's actually a joyful feeling considering what you'll have accomplished. Best regards guys... In life and in all your pursuits.

You'll are amazing. :victory:
[G4 Android Development] JK-FINN:
What would be a good modded Google Camera for this ROM, that you have had good user experience with?
[G4 Android Development] tseeling:
rebooted, flashed Magisk again, and this time it works!

Apart from the red flashing LED everything looks good.

Thanks very much for your help!
[G4 Android Development] steadfasterX:
the purple (not red) blinking led has been introduced here: https://xdaforums.com/showpost.php?p=80191509&postcount=915

I liked to have a feedback while it is booting.

.-
[G4 Android Development] omer1992:
Hi,

I flashed new firmware but vibration force increased it's very loudly how can we fix it?
[G4 Android Development] steadfasterX:
https://github.com/Suicide-Squirrel/issues_pie/issues/29

.-
[G4 Android Development] miXXed404:
I'm also facing same issue while using Snapchat, when it tries to get location whole systemUI crashes(?) then after minute or 2 its working again

just try to use snapmap or send snap
[G4 Android Development] kinuris:
Hello [MENTION=5545101]steadfasterX[/MENTION]

I would like you to reconsider the integration of some spoofing signature patch in the ROM.

I know you have investigated this before., so please read this before take a decision.

The thing is that I'd like to use microG, as a substitute for Play services. You get low power use, and mainly, you get much better privacy, as you can get ride off all the google apps.

You can consider then why not get your system run without Google services completely, why use microG. Well, a lot of apps work using the G messaging system, and more things that I don't really understand.

I don't think it could really be a serious security issue, just because what the patch do is add the feature to spoof as per-app based permission, so you can choose which app activate it or not.

And you will stop the data leaking that you have using the Google thing.

Then you can use Aurora Store, or a patched PlayStore, ... etc.

You can read about this here: https://shadow53.com/android/no-gapps/setup-guide/microg/#prerequisites

And of course, thank you for your amazing work in this, ROM, and all the incredible projects you are sharing.

Best regards
[G4 Android Development] polfrank:
Hey and thanks for the good result. One quick question: Has anyone tried encryption? Is it working?
[G4 Android Development] steadfasterX:
sure. this ROM has encryption fully supported (last test: today on latest build)

BUT

TWRP for pie is still in BETA and is NOT able to decrypt.

Other then that there are no known issues with encryption

.-
[G4 Android Development] steadfasterX:
https://github.com/Suicide-Squirrel/issues_pie/issues/30

.-
[G4 Android Development] polfrank:
Okay, but I suppose that we can do system updates with twrp if needed right? Can we also wipe cache and dalvik?

Furthermore, is it possible to wipe data if needed? I mean, ok, it cannot be decrypted, but can it be wiped?
[G4 Android Development] steadfasterX:
system updates: yes

wipe cache: yes

wipe dalvik: no (as thats in /data) while you never need to do that these days

wipe data: yes by choosing the FORMAT button in the TWRP wipe menu

.-
[G4 Android Development] kinuris:
Well, I want to thank you for the link, and all your knowledge and time dedicated to this subject.

I've read all the info, and I've seen that there is controversy on this matter. The comparison with the integrated root is really interesting.

I think I understand the risks, and as you pointed the best use is a whitelist model. But you can't get the primary risk off, the substitution of an application, and get access to system and hidden APIs.

Well, if you trust microG, maybe root your phone is riskier than use it.

Anyway, you have more data, I think the security is part of your job, and you are giving us your time, work, an patience.

Thank you
[G4 Android Development] polfrank:
So, if I get it right, we cannot do a "regular clean flash" but it is alright because the changes of the new updates are small. Right?
[G4 Android Development] steadfasterX:
yea and regarding root they complained about "CM" (see how old that is) comes with root pre-installed but this is not true for LOS anymore. you have to install the root add-on first.

This is what I mean, the discussion is quite old and outdated (in parts at least) so all this might need to be reviewed again .

well no, dalvik cache is not part of a "regular clean flash" (anymore). Its simply not needed. I have updated the FAQ.

Even cache is needed in absolute rare cases only (since N or O) but it doesn't hurt so I left it there.

so tl;dr: you can safely upgrade your ROM even when TWRP cannot decrypt.

With one exception: switching between ROMs (e.g LOS and AOSCP) or between major ROM versions (e.g 15.1 <--> 16.0) requires a data wipe but that should be well known.

right now I have also tested these root methods on my encrypted phone (again as I did all this a while ago already):

- LOS root add-on, no issues

- magisk 19.3 : requires additional tasks on first magisk manager start (due to the fact /data was encrypted). you will be guided through, afterwards all fine here
[G4 Android Development] steadfasterX:
I have created an issue for that: https://github.com/Suicide-Squirrel/issues_pie/issues/31

thx for reporting.

.-
[G4 Android Development] masemoel:
Portable WiFi hotspot

Hi steadfasterX! ;)

I am not able to enable the portable WiFi hotspot neither with the quick toggle nor at the settings option (it enables and then disables automatically after a second).

LTE is working OKAY and WiFi too.

Here I attach you the logcat:

https://paste.omnirom.org/view/e8955eb7

My best wishes and thanks again for your hard work!!
[G4 Android Development] kosi27:
AudioFX issue

Hello, I have a problem playing music from a ripped audio CD when AudioFX is turned on: with the original LG-headphone (jack plug) and with some - but not all - bluetooth devices sound is terribly distorted when a new title begins. It's ok again when pausing and restarting playing.

I never had this problem with LOS14/15 - it began after the full clean flash of LOS16-0520 and continued steadily with the switches to 0620->0724->0916 (regular clean flashes).

It doesn't happen when AudioFX is off (but I like basses :) )

Here is the log: paste.omnirom.org/view/19d928ff (this is without "https://" - cannot insert links because I don't have 10 posts yet ...)

Log starts with starting mp3 player, the described effect starts around line number 2640.

Greets ...
[G4 Android Development] Over567:
Same for me when I connect my phone with jack to my car. Thought it's on my device only. Going to turn off audio fx then thanks for the solution.