IMPORTANT ANNOUNCEMENT #2

REALLY IMPORTANT ANNOUNCEMENT:

Please read it!



I also need to thanks all the awesome people that have made this possible, therefore thanks to @

Thanks to @

We ( @ patalao and me) have decided to create a new thread since the @ op from the thread we were using seems to be inactive, so doing this will give us more freedom for editing the main post and providing you guys with more information.I also need to thanks all the awesome people that have made this possible, therefore thanks to @ soniCron and @ Alcolawl for being the creators of the original guide and all the fantastic tweaks that you have made.Thanks to @ flar2 for his great app (EXKM) and his kernel and to @ patalao for his superb tweaks and all the help he has provided me.

What I'm talking about is 7-14 hour screen on

Voltages and Frequencies:

expect new updates and rework for the current tweaks

new ones

NO

UPDATE:

How this affect your device (ROM/KERNEL)

Disclaimer:

What About Touchboost?

MY DEVICE LAGS!!! WHY?!?!

First of all, Check If the tweaks have been applied correctly

Our first one is modifying the Input boost (not touchboost) most of our tweaks have an already established Input boost clock speeds and time, you can incise does too a bit. For example, we have 960(Mhz) for all the CPU at 40ms you could bump it up to ~1036(Mhz) and 42ms, don't modify too much this values since it will potentially increase your battery drain.

Our second tool for fixing lags is min_sample_time , my recommendation is to increase the value by 5000 each time till you no longer suffer any stutter or lag.

, my recommendation is to increase the value by 5000 each time till you no longer suffer any stutter or lag. Try another tweak, for example;

If you are using Project X.A.N.A Battery, try using Balanced option...



Get rid of unnecessary (background-)apps

Try a different IO-Scheduler

Try another profile

My phone still uses too much battery

First of all, Check If the tweaks have been applied correctly

Make sure that you have disabled touchboost.

Set brightness to a lower level.

Use a dark / black theme

Don't play games all day

Try other tweak, for example;

If you are using Project Zhana Balanced, try using Battery option...

All that you are about to read is based onso go there and thanks @ soniCron for it.I'll go ahead and copy and paste some of the firsts paragraphs so those who don't know what this all is about can understand a bit.I'm about to tell you how to get buttery smooth, lag-free performance with insanely good battery life, using an old school governor featured in practically every kernel...--stock or custom--that provides the Interactive Governor.Yeah, yeah... everyone promises good battery with great performance, but who actually delivers? Maybe it isn't as smooth as you want, or maybe it requires something your kernel or ROM don't support. Or maybe the battery life promises just aren't what you expected. There's always some awful compromise. Not here!This isn't a guide to get 36 hour battery life... provided you never use your phone. That's deep sleep optimization, which is lovely and all, but what good is the phone if you can never use it?! And with the new Marshmallow Doze feature, this strategy is becoming a thing of the past., actual hands-on usage times! Without compromising anything, you can get(Up to 14+ hours if you can stand minimum brightness and WiFi-only with a custom ROM and other stuff turned off! And this is with stock voltages and full frequency range--you'll likely get even more if you choose to optimize those as well!)However, it should be noted that this does not apply to gaming, heavy camera use, etc. Anything that is an automatic battery killer in and of itself. There's nothing that can be done about anything that forces the phone to utilize its maximum resources all the time. But you should know that by now. Further, this guide is about optimizing the CPU as much as possible. It does not cover things like eliminating wakelocks so your phone sleeps well, removing unnecessary and battery draining stock apps, keeping your screen brightness down*, and all that stuff that's been covered in other posts ad infinitum. Those optimizations are up to you.If you really want to know the principles of this tweaks, please go to this thread since there everything is really well explained and I know you guys just want to apply the tweak and forget about everything behind it, so just keep scrolling!So recently I have been investigating about the Voltages of our device (since that is a really useful information to know) before that we only have the(If you don't know what I am talking about go ahead and read @ soniCron thread because I won't explain it) we could develop some tweaks with that, but we were pretty much making blind shots, guessing and hoping that all will be right. Well, now that we have all this information we can optimize our tweaks even more soand of courseI have made a little spreadsheet with the Nominal and Efficient frequencies for you guys, so you can take a look and maybe modify our tweaks to your needs, since, all of them have been tested by @ patalao , our tester and me, which involves that are tested without usage and not yours.We have more to talk about this, as you can seehavedown points since it will consume the same voltage as the maximum stock clock speed and it will give use more performance.It's true that the voltage it's the same, but there is some downpoint which are explained in this posts. Here and here Thanks to @ bedalus for pointing itn out!Notice that the voltages on CM ROMs are higher that on OOS and that the values were shown there are from OOS. We are already working on a flashable zip or script for modifying those values since cannot be modified anyway else.On the Snapdragon 820 (Our chipset) things have changed a lot from the previous chipsets like the 808 (Nexus 5X) and 810 (Nexus 6P). Now we are back to the Quad-Core, which is good, more cores= more battery consumption but we continue with the Little.BIG set up, where we have a Little Cluster (really efficient and fast) and a Big Cluster (slow but good for heavy loads). On previous chipsets, the Little kernel was really good on low-mid clock speeds and the Big cluster was really good on high frequencies and bad on low. Well, this is still true, but not we don't have such difference than before. Our Little cluster is going to be "thething" as it was before, but now the Big cluster has a really low consumption on lower frequencies so can bewhich only demand low~mid clock speeds as well it will be used as a quick burst for help the Little cluster to not reach High freq here it's not that efficient anymore.You might NOT get the same results as me or other, it will depend mainly on your usage, secondly on the kernel and finally on the ROM that you currently using.Not all the tweaks work the same way for certain kernel, what I mean with this is that the battery life/performance might be better running X kernel with X tweak, but the same tweak applied to another kernel might not be that good at allWait what? What you want to tell me is that some kernel is better than other, right?Yes and No, Some kernel is better than other but also, some kernel perform better with certain tweaks as can be seen in the following screenshots (This test have been performed using AnTuTu tester with a clean install of last RR + the Kernel, nothing else. I know is a benchmark and the perfect thing whole be a real life test but that takes days, so If somebody wants to do it, I'll post the results): This is just a profile (tweaks) for the interactive governor. If you experience any unexpected fc, reboots, massive stuttering/lagging, etc, this profile isn't most likely not responsible for that.Since I've noticed that a lot of people was asking about Thouchboost, I decided to add this little explanation from @ soniCron With all that been said, you shouldn't confuse Touchboost with CPU Boost and more specifically Input boost. Both are used to boost the clock speed of our device whenever we touch the touchscreen, so we don't suffer any lags.The difference is that Input boost can be configured and Touchboost cannot, making it a really inefficient.First of all, it's athing, as I have stated before, all these tweaks have been done for fit my usage or certain usage which is most likely not the same as yours. Because this, when the are put on a certain scenario the might stutter or lag just a bit (If you are experimenting huge lags, you have done something wrong)And yes, this can be fixed. We have a couple of ways of fixing it:I'll keep this post updated with new information, so make sure to subscribe to it.