[LG V20 Questions & Answers] alvinator94:
Introduction: Important shizz is underlined and in bold​

So for the past 2 months I've been flashing away with my new V20. Of course one of the first things that I decided to do was to get a CM/LOS ROM on this bad boy. And thus is where the problems begin. Before I went to any of the AOKP or RRemix ROMs I went straight to LineageOS first as a base point. I installed it successfully did all the necessary procedures (format x3, wipe errthing x3) and then installed the ROM, gapps, and Magisk.

Average battery life with watching a total of 30 minutes of Youtube videos sequentially on my 15 minute breaks, texting throughout the day, and one hour of music playing from spotify (streaming) in the morning. My work is a pretty set schedule and by no means am I on my phone all day or anything like that. So with a total SOT (screen on time) of about 45 minutes I got

5 hours of battery life.

Yes I did a clean clean clean stock install of a Lineage based ROM

No I have no other apps running and draining my batteries

I really do not think its hardware related because it can be fixed!

How I tried to fix it​

Now I try all the other ROMs. AOKP, same deal even with tweaking through Kernel Auditor on the Play Store, so I figured okay maybe just a fluke with these two ROMs. So I go and use previous builds of LOS and AOKP, nothing still the same issue. I go and use RRemix, same issue.

So heres the issue,

100% cpu usage while screen is on (cpus are maxed out on the little and big clusters) unless screen is off, then it goes into deep sleep, and the phone gets ridiculously hot which in turn drains the battery even faster.

Now at this point I'm so frustrated and had already settled on going back to stock until I downloaded Advanced Kernel Tweaker from an XDA post from the OnePlus forums. Its the same chipset (snapdragon 820) and tried applying different profiles. I got an extra hour using these tweaks but I still knew something was going wrong and I cannot figure it out for the life of me until I dug deeper reading posts about this stuff from several months ago and people having issues of

overheating and an average of 5 hours of battery life

In one of the threads I read someone mentioned that it was just Kernel Auditor and its coding had been done in a way that was unoptimized. Because when your system detects you opening an app it boosts your little/big cluster in order to make up for the cpu usage so theres no lag. Well I thought okay I'll just use something else, so I spent money on EX Kernel Manager and by God, still the same issues, UNTIL, I hit the button at the top that is called performance mode.

BY GOD IT WORKED, HOLY CRAP MY CPU USAGE ISN'T JUST AT

FULL USAGE

My temporary fix​

So now, I am constantly in performance mode with using EX Kernel Manager but I have control over my cores!! And they are no longer at 100% usage.

Here are pictures of the new stats with EX Kernel manager and uptimes of my little and big clusters.

Big​

[IMG="Big cluster"]http://i.imgur.com/vYocuoY.png[/IMG]

Little​

[IMG="Little cluster"]http://i.imgur.com/gAMcXDk.png[/IMG]

New battery life on ONE CYCLE

ps. the stent of this cycle was 5/22/2017 15:00hrs to 5/23/2017 19:00hrs​

[IMG="battery cycle img 1"]http://i.imgur.com/QW3BrQz.png[/IMG]

[IMG="battery cycle img 2"]http://i.imgur.com/AnKaIOT.png[/IMG]

Summary of the problem​

So as you can see, there are all of the speeds being used instead of just the one of 1593MHz when performance mode is off. If people would like pictures of 5 hours of constant 1593MHz speeds I can show you them, but I really don't feel like wasting and overheating my devices battery for the purpose of just pictures. Heres a taste of it without perfomance mode on, by the way, the little speedometer gauge in the top right of this image is the performance mode.

Conclusion​

So in conclusion, performance mode on using EX Kernel Manager, Advanced Kernel Tweaker scripts installed and using Project Zhana Battery profile, no more overheating and only getting 5 hours of battery life. YES this is a temporary fix but I hope arming XDA with this knowledge can push people and developers to find a fix. Thank you for your time reading this.