yashsingh1/xdaforums huggingface dataset:
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jl10101:
Dial *#*#4636#*#*

Go to phone settings

Then 3 menu dots top right

Should be there

---------- Post added at 11:28 AM ---------- Previous post was at 11:21 AM ----------

[MENTION=2881807]x86cpu[/MENTION] [MENTION=5103965]Omar-Avelar[/MENTION] [MENTION=5988026]iDefalt[/MENTION]

Another great leap forward.

Bluetooth calling works perfectly now!

It was literally just white noise and loud feedback and hissing for the call sound (media streaming worked fine).

This is with LOS 15.1 20180629 and Gamma v14.0

H990 single sim

UPDATE: so, just made a call, other person says I sound like I'm under water and very soft. So that's the next thing to hunt down. Maybe the clarity / which mics / and the mic gain need tweaking.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
Could you elaborate what change you made?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Nakashima Taiki:
Found it. Thanks
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jl10101:
Sorry, should have been clearer. I just used Gamma kernel v14.0 instead of stock LOS kernel. And have advanced LTE disabled and carrier video calling disabled. I doubt the last two options have anything to do with the Bluetooth call.

The last thing I want to try investigate is the mic issue when on Bluetooth (edit: and speakerphone call). Sounds like I'm underwater to the other person in the line.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
Advanced LTE/Wifi calling/video are all not working, even if the options indicate.

Bluetooth is having an issue on BCM4345 chipset. That includes the h990, and the rs988(g5), and another g5 I don't remember at the moment.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
v15.0 working okay here :)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zacharias.maladroit:
[MENTION=5103965]Omar-Avelar[/MENTION]

Can you please explain what disabling "qcom,partial-update-enabled;" is the workaround for ?

https://github.com/oxavelar/V20-Kernel-Gamma/commit/9c5bb2834ff9c429073d3bf8d0f6369358309fe7

Were you having output distortion on the panel ?

Thanks
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] :
[MENTION=5103965]Omar-Avelar[/MENTION] May you please add Adreno boost in a future update?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
The screen would flicker during refresh updates. We had it enabled for the V20 and so far we know it is working in LineageOS 14.1 builds just fine, but recently with LOS 15.1 we haven't been able to get this thing to work just yet... there might be some dependence somewhere from userspace or libraries that have not been tracked down.. so we are keeping partial panel update disabled for now in 15.1... (@x86cpu).

I am unsure for any slimport or display port outputs crazyness as I don't have external panel dongles. But for the internal built-in panel there was no output distortion noticed with pp enabled as I still have one V20 phone running LOS14.1 with pp enabled.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zacharias.maladroit:
ah - bummer,

thanks for the explanation

It might be only a OLED display thing but you could take a look into qcom,panel-allow-phy-poweroff property which might help even more

the dtsi files on the V20 also uses qcom,ulps-enabled; & qcom,suspend-ulps-enabled;

so they should work pretty efficient already
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
Let me try the qcom,panel-allow-phy-poweroff override, worth a shot ;)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jl10101:
[MENTION=5103965]Omar-Avelar[/MENTION] 15.2.0 working well on the H990

Wanted to ask if there is anyway to add in USB fast charge on LOS 15.1?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
Fast charger has been working for quite a while now on LineageOS, I believe it's working for the Gamma kernel too.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jl10101:
Thanks - is that usb through? (from a laptop for example, not the fast charger brick itself)

I've noticed that the phone can drain quicker than it can charge when just over USB. Otherwise, with the brick, it's as fast as stock.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
Same. Phone drains faster than charging via USB to PC, perfectly fine on charger.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
That PD (Power Delivery), which I do not believe works, it uses the 500mah when plugged into PC.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
Hmm, odd. Is it just a LOS/ASOP Kernel thing? It charges when USB'd on stock.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
v16.0.0 is up, some changes in it to allow for starting the msm_irqbalance service by default on boot, disabled lp11 and enabled allow mdss phy powerdown during idle screen, let's see how this build goes :)...
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
16.0.0 working okay here after initial tests. Will report back later with more findings :)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
It replaces LOS thermal engine with that of what comes by default in the LG V20.

Could you try installing it on 15.1? I see that you are gaming and are sort of getting stuttering and would like to rule out any extreme Kernel thermal throttling since user-space thermal throttling might be failing to lower processor temperatures. Kernel takes extremes measures to power-off cores when it reaches 80 to 90 degrees. But the LG throttling engine starts doing soft throttling from 60-80 to keep it stable before taking any extreme measures.

Btw, I use the zip on my daily basis without any problem... do try it, worth a shot... and let me know if it fixes your gaming problems. I would also reccomend disabling KA at boot for doing component isolation and help pin point where the problem you are facing might be.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Still_living714:
OK I flashed your latest kernel, the stock thermal zip and uninstalled KA. The problem still persists... Any other ideas? I don't mind if it costs more battery, TIA.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jl10101:
V16.0.0

Seems deep sleep is working nicely here now.

See below screenshots. Was on charge for some time, but deep sleep of Big CPU matches deep sleep of Little CPU. And BBS shows deep sleep time that matches Big and Little cores. So job well done! Thanks so much!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
Wish there was a notifications feature on mobile for when a new version gets uploaded haha.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] :
Hmm, maybe a Telegram group would suffice.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
Strangely there's a "bug" when using the latest combo (I updated both LOS and my Kernel) where the extended part of the display is not doing auto-brightness. And this results in a strange color shading in the top status bar (as the backlight is uneven):

This can be noticed by checking, e.g:

us996:/ # cat /sys/class/leds/lcd-backlight/brightness
61
us996:/ # cat /sys/class/leds/lcd-backlight-ex/brightness
127

Trying to figure out what happened... I think this might be due to LineageOS user-space and not the low power panel Kernel changes introduced... but gotta confirm...

UPDATE: Ok, I've reverted to my favorite build for now "lineage-15.1-20180620-UNOFFICIAL-us996.zip" (I had to use the to-UNOFFICIAL.zip to use the old signatures) and now the auto-brightness now does both sysfs entries, this has no strange top status bar shading as the backlight is not uneven. Thought this "weird behavior" was because of the recent Kernel panel updates but it is not the case...
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
I was having this problem and scratching my head as to why it was happening suddenly. Hopefully [MENTION=2881807]x86cpu[/MENTION] can fix it from the LOS side.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CrUxXxX:
I have a problem with stranger lights shadow nearby right corner by status bar. I was adjusting my kcal to fix it but still not working.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jl10101:
It's the same problem outlined a couple posts before yours. Basically, the latest build of LOS has a "bug" where the second screen is not matching the autobrightness of the main screen, so there is a strange bleed of light happen until at the top.

This is a build specific, software issue, so nothing physically wrong. I have it too. Flash back to a previous build or hang in there until the next LOS build.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] TripOG:
H910 Los 15.1 los, Anyone having an issue where the screen won't turn on when you wake the device up? Also after entering passcode on boot it turns off? I'm not really sure how to troubleshoot this.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
I like to think of them as battery saving measures ;)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] :
The only method that's worked for me is to disable the lock screen completely. :/
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] TripOG:
What build kernel and los are you on? Also are you using an h910? I just realized there is a v17 of gamma, I think im still on 16

same issue with v17
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
Just wanting to add. I finally updated to v17 and the brightness issue is considerably better than on v16, presumably this has something to do with the v17 change in the OP. I'm on Lineage 20180712 build. It's barely noticeable tbh, but still hoping for a fix from [MENTION=2881807]x86cpu[/MENTION] for LOS
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] phr00t:
I'm trying to build a Lineage 15.1 ROM using this kernel & the latest second screen changes being worked on in the [BOUNTY!] thread. I've heard there is some configuration line somewhere that "disables" the second screen that I need to change? Where can I find that? Thank you for your help!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] phr00t:
When trying to build the Gamma kernel with Lineage 15.1, I'm getting these errors:

../../../../../../kernel/lge/msm8996/drivers/input/keyboard/gpio_keys.c: In function 'virtual_hallic_state_show':

../../../../../../kernel/lge/msm8996/drivers/input/keyboard/gpio_keys.c:212:31: error: 'hallic_sdev' undeclared (first use in this function)

return sprintf(buf, "%d\n", hallic_sdev.state);

^

../../../../../../kernel/lge/msm8996/drivers/input/keyboard/gpio_keys.c:212:31: note: each undeclared identifier is reported only once for each function it appears in

../../../../../../kernel/lge/msm8996/drivers/input/keyboard/gpio_keys.c: In function 'virtual_hallic_state_store':

../../../../../../kernel/lge/msm8996/drivers/input/keyboard/gpio_keys.c:218:3: error: implicit declaration of function 'switch_set_state' [-Werror=implicit-function-declaration]

switch_set_state(&hallic_sdev, val);

^

../../../../../../kernel/lge/msm8996/drivers/input/keyboard/gpio_keys.c:218:21: error: 'hallic_sdev' undeclared (first use in this function)

switch_set_state(&hallic_sdev, val);

^

../../../../../../kernel/lge/msm8996/drivers/input/keyboard/gpio_keys.c: In function 'virtual_hallic_state_show':

../../../../../../kernel/lge/msm8996/drivers/input/keyboard/gpio_keys.c:213:1: warning: control reaches end of non-void function [-Wreturn-type]

error, forbidden warning: gpio_keys.c:213

/home/phr00t/android/lineage/kernel/lge/msm8996/scripts/Makefile.build:257: recipe for target 'drivers/input/keyboard/gpio_keys.o' failed

make[4]: *** [drivers/input/keyboard/gpio_keys.o] Error 1

/home/phr00t/android/lineage/kernel/lge/msm8996/scripts/Makefile.build:402: recipe for target 'drivers/input/keyboard' failed

make[3]: *** [drivers/input/keyboard] Error 2

/home/phr00t/android/lineage/kernel/lge/msm8996/scripts/Makefile.build:402: recipe for target 'drivers/input' failed

make[2]: *** [drivers/input] Error 2

/home/phr00t/android/lineage/kernel/lge/msm8996/Makefile:962: recipe for target 'drivers' failed

make[1]: *** [drivers] Error 2

... any help would be appreciated!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
Yes. arch/arm64/boot/configs (going from memory). it's the defconfig directory. There is a SECOND_SCREEN_DISABLE .. just comment it out.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
Yeah [MENTION=2881807]x86cpu[/MENTION] is right on the path, btw when building the Gamma Kernel could you use the defconfig from "lineageos_<<variant>>_oxavelar_defconfig" instead of the ones that LOS uses by default? I didn't sync LOS defconfigs, so there might be some dangling stuff there.

For example : lineageos_us996_oxavelar_defconfig has:

# LGE - Misc
CONFIG_LGE_DISABLE_SECOND_SCREEN=y
CONFIG_LGE_QPNP_HAPTIC_OV_RB=y
CONFIG_LGE_HALL_IC=y
CONFIG_LGE_HANDLE_PANIC=y

Just comment it out for the variants you are building and you should be good to go...
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zacharias.maladroit:
anyone else besides [MENTION=5988026]iDefalt[/MENTION] that owns the H990DS who tested with 2 SIMs ?

So there's perhaps some kind of dtsi switching magic (or whatever) involved that makes it work via appending that argument ...
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] phr00t:
I'm trying to use the lineageos_h910_oxavelar_defconfig by default. I modified the Makefile in the arch/arm64 directory like so:

#KBUILD_DEFCONFIG := defconfig

KBUILD_DEFCONFIG := lineageos_h910_oxavelar_defconfig

... but that didn't work -- still got the same errors. I tried copying the lineageos_h910_oxavelar_defconfig over defconfig, and that still gives me the same errors too.

I do see CONFIG_LGE_HALL_IC needs to be defined for hallic_sdev to be defined, so it does appear getting the oxavelar_defconfig applied will fix these compiling errors.

After making the above changes, I'm just re-running brunch h910 at the source root, which I presume is considering the changes to my Makefiles & defconfig files (especially for something that previously failed to compile).

Any help would be appreciated & thank you for the help thus far!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] phr00t:
I got it to compile. It appears I needed to replace the lineageos_h910_defconfig file with the contents of lineageos_h910_oxavelar_defconfig

There were a TON of uninitialized variable warnings were not allowed, so I had to force -Wuninitialized-maybe into the build process. After finally building, I got some errors that there were "mismatched sections" & there was a flag to allow building the kernel anyway (which I'm not sure was the best solution, but it worked).

Anyway, after building, flashing & testing... I get to the welcome screen. Physical buttons work. Sound works. Screen works... but I can't tap anything. The touch screen appears unresponsive & I need to pull the battery. Any ideas what could cause the screen to be unresponsive...? :-/
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
Awaiting that v18 upload ;)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] SebTech33:
Beta 5 worked fine on H990ds. Ill test if there is a newer version out
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zacharias.maladroit:
I didn't write that :cowboy:

glad the new panel changes don't cause trouble though :)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zinou213:
Stock ROM ?

Can i use this kernel with super V20 rom in my h990ds ?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] :
I'm sorry, but no. :( Gamma kernel is only compatible with LOS/LOS based ROMS.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
DOTS kernel is what you want
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] cnjax:
Mk2000 is better and more up to date
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
Debatable, imo. But that's what these forums are for ;)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] phr00t:
OK, so building Gamma alongside Lineage hasn't been working out so well... I'm trying to build Gamma for myself with the SECOND_SCREEN_DISABLED define commented out. I did make lineageos_h910_oxavelar_defconfig which worked to generate a .config file. I'm trying to use your build tools & source, and I get this error:

aarch64-linux-gnu-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found

compilation terminated.

arch/arm64/kernel/vdso/Makefile:34: recipe for target 'arch/arm64/kernel/vdso/vdso.so.dbg' failed

make[1]: *** [arch/arm64/kernel/vdso/vdso.so.dbg] Error 1

arch/arm64//Makefile:133: recipe for target 'vdso_prepare' failed

make: *** [vdso_prepare] Error 2

I don't see that .so library in the Gamma build tools, but I do see it in the Lineage build environment. I tried copying that .so file in a few locations, but still got the error. I don't know where it is suppose to go to be properly picked up or what bigger I may be doing wrong here. Any help is greatly appreciated!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] phr00t:
After installing the arm cross compiler & trying different ones in the Makefile, I got past the liblto_plugin problem. Compilation gets much further now, but now I get this error:

In file included from include/linux/rcupdate.h:43:0,

from include/linux/rbtree.h:34,

from include/linux/mm_types.h:9,

from include/asm-generic/pgtable.h:7,

from ./arch/arm64//include/asm/pgtable.h:522,

from ./arch/arm64//include/asm/io.h:29,

from include/linux/clocksource.h:19,

from include/clocksource/arm_arch_timer.h:19,

from ./arch/arm64//include/asm/arch_timer.h:27,

from ./arch/arm64//include/asm/timex.h:19,

from include/linux/timex.h:65,

from include/linux/sched.h:19,

from ./arch/arm64//include/asm/compat.h:25,

from ./arch/arm64//include/asm/stat.h:23,

from include/linux/stat.h:5,

from include/linux/module.h:10,

from init/main.c:15:

include/linux/completion.h:45:9: error: initializer element is not constant

struct completion work = COMPLETION_INITIALIZER(work)

^

init/main.c:391:19: note: in expansion of macro 'DECLARE_COMPLETION'

static __initdata DECLARE_COMPLETION(kthreadd_done);

^

include/linux/completion.h:45:9: error: (near initialization for 'kthreadd_done.wait.lock')

struct completion work = COMPLETION_INITIALIZER(work)

^

init/main.c:391:19: note: in expansion of macro 'DECLARE_COMPLETION'

static __initdata DECLARE_COMPLETION(kthreadd_done);

^

scripts/Makefile.build:257: recipe for target 'init/main.o' failed

make[1]: *** [init/main.o] Error 1

Makefile:965: recipe for target 'init' failed

make: *** [init] Error 2
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Nakashima Taiki:
[MENTION=5103965]Omar-Avelar[/MENTION]: Saftynet issue on H990DS:

I'm running on latest LOS 15.1 with your latest v18.0 gamma kernel. When I reboot my phone, my safetynet results turn false. So I tried reboot it again and still showing false. I look at this article, https://www.didgeridoohan.com/magisk/MagiskHide, and thought that maybe it's the kernel problem. So I dirty flash LOS 15.1 without your kernel and pass the safetynet result (Basic Integrity). I don't know what happen but just want to let you know.

Update: After flash your kernel from stock kernel, it seems both BasicIntegrity and CtsProfile sticks to true. Will update if it turn to false.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Tilde88:
Hello. I need info on this kernel. It seems to lock CPU frequencies to 1036mhz on big, and 729 on little.

First I thought it was me since I tried to under clock and change governor. Full wipe, reinstall lineage alone, kernel options work fine. Full wipe again, and this time I Install this kernel BC all I really want is kcal. Didn't touch anything in CPU section of KA (didn't even ever go to CPU section.) Phone not charging, cool as could be--no heat. Clocks stuck.

Decide to try and change, but again, the frequencies are locked. Reflash kernel, clear all caches, no change. Dirty reflash lineage just for the kernel replacement (I know i don't have to reflash the whole rom), lock goes away. Reflash this kernel, CPU gimped again.

Looked for stock thermal driver in OP, dead link. Tried enabling and disabling all combos in thermal section, no change.

Tried again to switch frequencies and/or governor, stays stuck.

What the actual hell?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] adityajiwap:
[MENTION=5103965]Omar-Avelar[/MENTION]

Is it possible to implement on/off toggle for our sensors?

My proximity sensor is fked after a screen replacement, I'm looking for a way to be able to turn off the sensor completely so the screen will not stay turned off during calls.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Tilde88:
Ok so it looks like even tunables break the kernel config. Does anyone know why this kernel is locked down where if you change any one setting, everything gets stuck at these low frequencies? I would like to remove whatever is causing this symptom, and do a fresh compile. Any info would be great... I don't want to not use this kernel, as it is the only 8.1 AOSP kernel with KCAL built-in, and everything within it actually works amazing... But not being able to choose my own settings is a bit Apple IMO

Edit : (After re-reading this post, I would like to express my gratitude to OP for amazing work. I do not intend my posts to be in any way negligent to anyone's work)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] SebTech33:
Otg is working on v18.0.0 (h990ds)

http://imgur.com/gallery/fYkjMRS

Battery is charging extremely slow when screen is on. Any tips?

http://imgur.com/gallery/5Y6xlBO
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] uxairmalik:
Is this working on h990n the dual sim variant for hong kong?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] SebTech33:
is there a v19.0.0 update out or is it on the way?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Jongla:
Same here.

Only thing I changed was KCAL settings.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
Please check here, here and here. EAS has a user-space perfd as well as other components that if you change CPU governors on boot or someone meddles with the CPU governors without doing a "stop perfd" it will mess up various things (such as min freq and input boost). It is not recommended to change the schedutil (or sched in stock LOS) governor at all or you will impact what EAS is for.

If you don't mind at all about EAS and plan on using legacy governors then I suggest you delete /system/vendor/bin/perfd but at your own risk if you insist... I would not recommend deleting perfd either since that's what adds the input frequency boost and is also what changes schedTune tunables upon certain detected events, so if you delete it and use non-EAS governors your performance will suffer greatly as the Kernel does not have HMP.

the settings are not a bit Apple btw, it is just that EAS is way more complicated than HMP and you have to know what you're doing and changing. Please go and find the source of the CPU changing sysfs entries at boot that cause the problem...

To begin isolating the component that causes the problem please disable root access to your Kernel Tuning apps to begin with and reboot -- you should see no problem with frequency changes at all in this step. Now go on and enable one by one... then find the settings/toggle that cause this and let us know...

UPDATE: Btw to the more knowledgeable folks if you really want to change CPU governor settings open my Kernel *.zip and navigate in ramdisk, edit init.msm8996.rc and add in the enable-cpu-tweaks trigger section "stop perfd" at the beginning and and "start perfd" at the end. And in between those two sections change whatever you want on CPU governor tunables. Re-zip and re-flash....
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
Btw... I've removed the stock LG thermal driver as [MENTION=2881807]x86cpu[/MENTION] is providing a stock LG thermal engine in his Oreo builds ;)