Julian Jeremiah wrote:Thanks Master!
Btw did you ever try "screen on time" on each governor after you've tweaked its parameters? Sorry if Ive phrased my question wrongly
What I'm trying to ask is how long can the % of battery lasts (says 90%) before it descends to 98% while browsing on web. I've tried almost all kernels which is available, finding the one best fits my needs, using different governors to test, tweaking its parameters, etc and on the worst scenario it could lasts is 1% : 2-3 mins (ratio); at the best is 1% : 5 1/2 mins (estimated). I'm unable to squeeze more juice out of it to lasts longer
Hard to analyse it that way because of a lot of things :
1) Battery % is an estimate calculated based on battery voltage, that is not precise and not linear, meaning you will lose 1% sooner at high battery level compared to lower battery level, so you need to calculate the average over a longer period, like 1 charge cycle.
2) Governors have an impact on CPU freq. which in turn has an impact on voltage applied which has an impact on the current drawn (that's what you want to analyse).
3) Hotplugging will on/offline cores, so basically the current drawn will be 1-4x higher, 1 core at 1GHz draws 4 times less than 4 cores at 1GHz, so hotplug is even more important than frequency.
4) With screen on, all of the above don't matter that much, because they represent peanuts compared to the display panel ! We have an Amoled panel, which means the more pixels are lit and the brighter they are lit the more current they will draw and that will be what determines actual battery life. Keep it dark and you will go further.
----
I tend to chose a governor I find ok as base, tweak it towards battery until I feel it's 'presence' (tiny lags here and there) and then bump it one nod up again, and stick with that.
Where all this really makes a difference, that's during screen off, as then the only thing really left drawing battery are the CPUs and the radio (gsm, 3g, wifi, bt...), since the 'big guy' (display) is turned off and not drawing any current at all.
Not much you can do for the radio (except turning it partly off), the CPU handling is what will make the biggest difference, that's why there's focus on that in kernels.
On the Note 3 influencing the hotplug driver, as in getting rid of mpdecision, is a way to get proper control over how many CPU should be online, and when to take them on/offline. With mpdecision, those choices have been made for us by Qualcomm.
So at some point that will be something I'll be looking into...
JP.
Send from my 'proudly eFused' Note 3 (n9005) running Temasek v75 on Yank555.lu htle v1.0a-beta4 (3.4.90) kernel.
Edit :
Also, with Samsung's default touchboost freq., governors don't really matter anymore, as the first touch will bump the freq. to 1.2GHz and after several repetitve touches 1.7GHz, so the governor has but 1.7 - 2.3 to play with (without OC that is) when you actively use your device.