Related
I do it on my laptop, was wondering if I can do it on my phone to save power?
I looked aound a bit and everyone seems vey focused on overcloking. I don't have a problem with the 1Ghz speed, was ust wondering if I can stay at that speed and save some juice and if it' safe.
Yes you can. Get one of the apps off the market either unstable apps or jrummy. I use the unstable version to under clock from stock down to values of 50, 43, 36, 25. Which is quite a lot lower I think.
Sent from my DROIDX using XDA App
The apps are only .99 -so you can't go wrong with 'em. But I like learning this stuff and tinkering. So you may have already checked out this thread...
http://forum.xda-developers.com/showthread.php?t=812749
It is about overclocking- but you can use the same information to underclock. You just need the overclock.ko file and then adjust the setscaling.sh file so that it uses lower vsels.
I did a little write up in that thread...
http://forum.xda-developers.com/showpost.php?p=8771591&postcount=43
so if you want to check into- once you fool around with it a bit- it is not that hard. I now actually have 3 scripts I can run. 1 for stock clock speeds undervolted. 1 for stock speed stock voltage. and 1 for high voltage clocked to 1.3mhz.
good luck.
it has definitely been a great mod to my phone. I'm running stock speeds and ULV. Battery life has been phenomenal.
Aggie12 said:
it has definitely been a great mod to my phone. I'm running stock speeds and ULV. Battery life has been phenomenal.
Click to expand...
Click to collapse
Care to post the file you are using?
Sent from my DROIDX using XDA App
The stock vsel is 56, right? I've tried going down to 54 and the stress test in set CPU goes well for 5 minutes. At some point between 5 and 10 minutes I get an error.
Is that normal and I should go with 54 or should the test last a lot longer without an error? Or is the stock vsel higher?
Sent from my DROIDX using XDA App
coolj478 said:
The stock vsel is 56, right? I've tried going down to 54 and the stress test in set CPU goes well for 5 minutes. At some point between 5 and 10 minutes I get an error.
Is that normal and I should go with 54 or should the test last a lot longer without an error? Or is the stock vsel higher?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
58, 44, 33, 27 are my vsel values oc'd to 1.125. Any higher oc will slow me down to a crawl.
To answer your question, I think stock vsel is 62 on Froyo.
I have been running the Ultra low voltage 1.3ghz preset from jrummy's app for a couple of weeks now with zero stability problems. Improved my battery by about 15-20 percent. I have seen warnings about stability with ultra low voltage but I guess I got lucky. Low 18's in Linpack and upper 1600 quadrants.
@aggie12 Care to share your vsel numbers? Im doing the same stock cpu speed just undervolted but I have hardly noticed a difference in battery life. How many hrs does your phone last in average use?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I typically get 36 hours before I get nervous at 20%. This is without juice defender, just straight 1ghz use on regular battery manager
From my Droid X with love...
@aggie12 Care to share your vsel numbers? Im doing the same stock cpu speed just undervolted but I have hardly noticed a difference in battery life. How many hrs does your phone last in average use?
Sent from my DROIDX using XDA App
Daali said:
I typically get 36 hours before I get nervous at 20%. This is without juice defender, just straight 1ghz use on regular battery manager
From my Droid X with love...
Click to expand...
Click to collapse
How is 36s hours even possible? I get around 10-12 hours of use, but I'm a heavy phone user...
Also, is it possible to undervolt using setCPU?
DawidD said:
How is 36s hours even possible? I get around 10-12 hours of use, but I'm a heavy phone user...
Also, is it possible to undervolt using setCPU?
Click to expand...
Click to collapse
No- set cpu only adjust your clock speeds- not the amount of power the phone is drawing to obtain those speeds. The .99 apps will allow for undervolting though. Or if you do a little study on the OverClock thread- it is not to hard to do with a script.
@Daali What are your vsel numbers? Mine are:
1ghz/45vsel
800/40
600/30
300/18
I get only 12 hrs of heavy use.
Sent from my DROIDX using XDA App
^^ siphen^^i just set this i'll start my test 2/marrow after I unplug for the day. I have extended battery mild user mainly txt/mms/no more than 30 min a day calling but i do surf sites quite often and wifi is on 24/7 as I have it at work and home> i'll let you know how those work for me.
How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.
Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App
Jasonhunterx said:
Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I just got Voltage Control (the free one)
but I don't get how to use it. Can you please guide me? Which Mhz is sleep profile? and what do you mean build prop tweaks?
Well its pretty simple open app click second tab the you will see sliders you slide them down slide it down 1 notch
Sent from my GT-I9000 using XDA App
But like which ones? I set the 100 to -25 and went to sleep and most 13% overnight.
Which other ones should I set there.sorry for the questions I just don't want to mess up my phone
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
So basically, I have to go through the voltages (-#'s) and see how low i can go without crashing?
}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
What would happen if you set it to 1000= -0 ??? Couldn't you just odin back to stock if the phone crashed?
}{Alienz}{ said:
Start with these
(Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor
check this out
http://forum.xda-developers.com/showthread.php?t=829731
nbhnohome said:
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor
Click to expand...
Click to collapse
I don't think I want to go THAT low, maybe it'll crash my phone or someting?
caldran said:
http://forum.xda-developers.com/showthread.php?t=829731
Click to expand...
Click to collapse
that thread doesn't help. I've seen it before, its just info.
I think people are answering the wrong question. Or I should say, giving answers to a different question.
To the OP: You're talking about Deep Sleep battery usage, right? There's no way to undervolt Deep Sleep. It's already using very minimal voltage. I believe what causes excessive Deep Sleep battery drain is the number of apps still running and using the CPU during Deep Sleep.
Undervolting will help a bit with battery drain during normal usage. For Deep Sleep, turn off your various apps' syncing ability, as well as freezing programs you don't use but that run in the background. For instance, if you don't use navigation very often, consider freezing the Maps app, as it runs all the time in the background. A number of popular games like to run in the background like GunBros and Aqua Pets. Also switch from 2g/3g or 3g to 2g only at night to save battery there.
To recap, the less you have running in the background, the less battery you'll lose when you phone is in Deep Sleep.
I was also going to say switch to 2g if you don't need the speed. It helps a lot for me. I also usually put my phone in flight mode before I sleep. I lose like 0.5% of battery an hr on flight mode. I'm not on MIUI yet, still on froyo, but should still help.
I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV
mohitmoudgil said:
I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV
Click to expand...
Click to collapse
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.
Can I do voltage Control on stock MIUI Kernal or do I need Neo?
Sent from my Vibrant.
In my experience (admittedly only been on MIUI for a few weeks), Pimp my CPU, Voltage Control, and SetCPU all work fine on MIUI, so yes. You should be able to use Voltage Control. Not entirely sure about Stock MIUI, but if you use the (superior) Revamped version (either SS or Lithium editions) the kernel that comes stock with it allows you to change voltages, though I would still recommend moving to Glitch and using either the ML or LL versions if you want to maximize battery savings.
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.
Click to expand...
Click to collapse
OV/UV settings can vary widely between phones. Some offer little to no leeway at all, and can't even be overclocked to the rather tame 1200mhz. Others can sit at 1700mhz at 100uv. It's luck of the draw really. Also, Conservative Governor will be kinder to more exotic UV settings, while others like Smartass or OnDemand may only allow for a slight 25 or 50uv for most voltage levels.
Trial and error, my friend. Find what works best for your phone.
Thanks guys.
One more question
If when I test if my phone can handle a certain UV is it good to have it at the lowest I can?
Like example
My 400mhz can go down to -200UV is that good or bad? Should I keep it that low if its not crashing or anything
You need to do some stress testing to be sure it's stable at those frequencies. Depending on the governor you use, your phone may not hit 400mhz often enough for you to really tell if it's stable or not. You could set 800mhz to -800uv, but if your phone tends to skip over 800mhz most of the time...
Undervolting can cause other problems if it's not completely stable. For instance, on Froyo I would get annoying static during music playback. Took me nearly a month to figure out that it was because I was undervolting the 400 to 100mhz range too much.
Undervolting doesn't make THAT big a difference. If you don't want to tweak and stress test and tweak and tweak again and stress test again, etc etc etc, then just reasonable settings that most phones can handle. For instance, 1200 0uv, 1000 25uv, 800 50uv, 400 75uv, 200 100uv, 100 125uv.
xriderx66 said:
How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.
Click to expand...
Click to collapse
In my experience when I switch to only use only 2G networks I get damn near twice the standy time. Also, changing wifi to never sleep and staying connected to wifi has about the same effect. This also holds true for CM7.
3G is a battery killer for MIUI and CM7
The only resolution I see to this is a GB source drop but I'm not holding my breath.
Off topic but does anyone know a good, fast device that runs CM7/MIUI without bugs or this horrible battery drain? I've been running some form of CM7 since Eugene's build this spring and it has gotten MUCH better but I'm kind of disappointed at the lack of vibrant-specific progress lately. There's only so much the devs can do without source (or a working vibrant and a T-Mobile data plan for that matter....). Don't get me wrong, I'm thankful for what we have and what the devs have given us but I'd love GPS that isn't f'd and 3G that doesn't suck my battery dry in a little over 10 hours (working 911 wouldn't hurt either.
Sent from my T959 using xda premium
I have the Franco kernel on my nexus 4 and loving it so far, definitely have seen a battery improvement. However there are times when it doesn't feel as responsive as stock. I know I can tweak things in governor control but I have no idea what any of it means.
Ideally I want to decrease the time it takes for the cpu to ramp up in frequency even if it's by a little bit(less than a second) so I can have the off the bat smoothness. Possibly might also want to decrease the time it takes for the cpu to ramp down.
I know straight out increasing the minimum cpu frequency would help with this but I'd rather it remain on 384 for when my phone is turned off and not getting any use at all.
<edit> this page is what I'm talking about
Manbot27 said:
I have the Franco kernel on my nexus 4 and loving it so far, definitely have seen a battery improvement. However there are times when it doesn't feel as responsive as stock. I know I can tweak things in governor control but I have no idea what any of it means.
Ideally I want to decrease the time it takes for the cpu to ramp up in frequency even if it's by a little bit(less than a second) so I can have the off the bat smoothness. Possibly might also want to decrease the time it takes for the cpu to ramp down.
I know straight out increasing the minimum cpu frequency would help with this but I'd rather it remain on 384 for when my phone is turned off and not getting any use at all.
<edit> this page is what I'm talking about
Click to expand...
Click to collapse
Why don`t you post this in the Franco thread?. You might get more feedback by users there, just an idea
I was going to, but an auto message said I should post in Q&A since my account is new..
try lowering the go_highspeed_load to like 80 or so. whatever your highspeed frequency is, the phone jumps straight to it skipping the other cpu steps when the cpu is at whatever percent you set the go highspeed load at. ie: if the go highspeed load is set to 80, when your cpu hit 80% load, the frequency goes directly to your highspeed frequency, skipping all the cpu steps on the way there.
Manbot27 said:
I have the Franco kernel on my nexus 4 and loving it so far, definitely have seen a battery improvement. However there are times when it doesn't feel as responsive as stock. I know I can tweak things in governor control but I have no idea what any of it means.
Ideally I want to decrease the time it takes for the cpu to ramp up in frequency even if it's by a little bit(less than a second) so I can have the off the bat smoothness. Possibly might also want to decrease the time it takes for the cpu to ramp down.
I know straight out increasing the minimum cpu frequency would help with this but I'd rather it remain on 384 for when my phone is turned off and not getting any use at all.
<edit> this page is what I'm talking about
Click to expand...
Click to collapse
I suggest you lower your timer_rate to 20000 or 30000. See if that makes a difference.
scream4cheese said:
I suggest you lower your timer_rate to 20000 or 30000. See if that makes a difference.
Click to expand...
Click to collapse
Oo, could you explain to me what the numbers mean so I can tweak it?
Manbot27 said:
Oo, could you explain to me what the numbers mean so I can tweak it?
Click to expand...
Click to collapse
Yes I can but perhaps in the morning. I'm tired. Lol. Try to find some info on it on Google and see what you can dig up.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
I suggest you lower your timer_rate to 20000 or 30000. See if that makes a difference.
Click to expand...
Click to collapse
HI~:laugh:
How should I set the value in GOVERNOR CONTROL, can you suggested me for these values?
These values are my current settings.which item should modify?
Above_hispeed_delay 10000
Boost 0
Go_hispeed_load 90
Hispeed_freq 1512
Input_boost 1
Min_sample_time 20000
Timer_rate 25000
input_boost_freq 1026
Thanks a lot ！
nexus 4 pa3.15(Apr16) with franco r127
k8563 said:
HI~:laugh:
How should I set the value in GOVERNOR CONTROL, can you suggested me for these values?
These values are my current settings.which item should modify?
Above_hispeed_delay 10000
Boost 0
Go_hispeed_load 90
Hispeed_freq 1512
Input_boost 1
Min_sample_time 20000
Timer_rate 25000
input_boost_freq 1026
Thanks a lot ！
nexus 4 pa3.15(Apr16) with franco r127
Click to expand...
Click to collapse
I totally forgot about this thread. Lol.
I think you could lower the hispeed_freq to 1026. You'll still get wonderful smoothness. My go_hispeed_load is at default 99. But 90 is good. Leave everything else as is...unless Franco changes them.
Sent from my Nexus 4 using Tapatalk 2
Manbot27 said:
I have the Franco kernel on my nexus 4 and loving it so far, definitely have seen a battery improvement. However there are times when it doesn't feel as responsive as stock. I know I can tweak things in governor control but I have no idea what any of it means.
Ideally I want to decrease the time it takes for the cpu to ramp up in frequency even if it's by a little bit(less than a second) so I can have the off the bat smoothness. Possibly might also want to decrease the time it takes for the cpu to ramp down.
I know straight out increasing the minimum cpu frequency would help with this but I'd rather it remain on 384 for when my phone is turned off and not getting any use at all.
<edit> this page is what I'm talking about
Click to expand...
Click to collapse
k8563 said:
HI~:laugh:
How should I set the value in GOVERNOR CONTROL, can you suggested me for these values?
These values are my current settings.which item should modify?
Above_hispeed_delay 10000
Boost 0
Go_hispeed_load 90
Hispeed_freq 1512
Input_boost 1
Min_sample_time 20000
Timer_rate 25000
input_boost_freq 1026
Thanks a lot ！
nexus 4 pa3.15(Apr16) with franco r127
Click to expand...
Click to collapse
You guys can checkout this guide for using governors.. Its the basic stuff, but hope that will help you
http://androidforums.com/nexus-7-all-things-root/653973-franco-kernel-guide-those-new-kernels.html
The stock android 4.2.2 freqs are 102 min 1512 max...
I works liquid smooth and gives love battery life.
My question: does cpu freqs not have any impact the n battery and heat..?
Sent from my Nexus 4 using xda
faddyie said:
The stock android 4.2.2 freqs are 102 min 1512 max...
I works liquid smooth and gives love battery life.
My question: does cpu freqs not have any impact the n battery and heat..?
Sent from my Nexus 4 using xda
Click to expand...
Click to collapse
Hi,
Higher the CPU freq is, higher the electrical consumption will be, higher the temperature too
So higher freq finally mean lower battery.
faddyie said:
The stock android 4.2.2 freqs are 102 min 1512 max...
I works liquid smooth and gives love battery life.
My question: does cpu freqs not have any impact the n battery and heat..?
Sent from my Nexus 4 using xda
Click to expand...
Click to collapse
Technically, high frequency will use more current as well as often requiring a higher voltage to the cpu to maintain stability. Both of those would increase battery consumption and heat. However....
When the cpu is working at a higher frequency, it finishes whatever its doing sooner and therefore has more time to idle, thereby countering some of the higher consumption/heat. Another thing to keep in mind is that on a smartphone, the LCD screen takes up alot more power than the cpu, so that an increase of a few 100 MHz and mV will have a negligible effect on the battery. However, because the heat increases with the square of the voltage, a higher frequency with higher voltage will result in a possibly noticeable increase in temperature.
Hope thats thorough enough for you.
Sent from my Nexus 4 using xda app-developers app
faddyie said:
The stock android 4.2.2 freqs are 102 min 1512 max...
I works liquid smooth and gives love battery life.
My question: does cpu freqs not have any impact the n battery and heat..?
Sent from my Nexus 4 using xda
Click to expand...
Click to collapse
Get Franco kernel, and undervolt some to get rid of heat, and the battery is super++++.
Sent from my Nexus 4 using xda premium
Hey guys, Kyuubi10 back once again with another Guide.
I thought it might be useful to pop in a couple results of my trial and error for the HTC One M8.
Note: This is not scientifically, calculated accurate, but it's close enough, based on estimates.
After following these guides:
http://forum.xda-developers.com/showthread.php?t=2769899
https://vjnaik.wordpress.com/2015/06/25/kernel-tweak-interactive-governor-paramaters-rooted-phone/
I decided to make a summary guide of the above but with specific HTC One M8 values.
Since I agree with the idea of "race to idle" embodied in the Wheatley governor, I tried emulating that on the Interactive governor while also keeping it as efficient as possible.
Here are the values (all others not mentioned, leave default):
Code:
[B]above_hispeed_delay [/B]- 80000 2265600:10000
[B]go_hispeed_load[/B] - 95
[B]hispeed_freq[/B] - 1728000
[B]io_is_busy[/B] - 1
[B]min_sample_time[/B] - 10000
[B]target_loads[/B] - 45 729000:80 883200:50 1267000:85 1497600:50 1728000:90 1958400:50
[B]timer_rate[/B] - 10000
[B]timer_slack[/B] - 5000
"above_hispeed_delay" makes sure that longer time is spent on the frequency step 1.72Ghz, before quickly raising higher into max freq.
1.72Ghz is the most energy efficient frequency with a good performance, e.g. it will not cause lag during casual usage, while it uses minimal voltage.
If the load is too high for this frequency to handle, I set the time short once it's gone over this freq step so that it will not waste time before reaching max freq. Thus dealing with the issue asap.
Another important parameter is "target_load", with this I have defined that at each efficient freq step the load needed to overcome it would be higher than normal. But it would up-scale quickly when using non-efficient frequencies.
The other parameters I have set so that the frequency is lowered as soon as CPU load is finished, so that it will rush back to idle as quickly as possible.
The interesting thing about this set-up is that for general, non heavy usage, it basecally functions as if I have underclocked to 1.72Ghz, but when the CPU is truly pushed it reaches up to 2.5Ghz which is my Overclocked max freq value.
Thus both saving battery and providing high performance.
I have felt no lag, and it's been quite a smooth experience while I used this
Combined with using GPU rendering (found in developer settings), and Seeder, the over all usage is pretty good.
Battery usage has been very efficient and I have managed to squeeze out an extra hour or two using this.
I highly recommend it!
Hope I helped you guys... don't forget to press the thanks button if you also feel that I did!:good::good:
I noticed I have some governor settings left at 0 or blank. I did some quick googling, found some other tweaks for the M8 and the interactive governor. So I played around a bit, and I think the following would be useful to add to the above tweaks.
-----------------------
sampling_down_factor: 60000
sync_freq: 1036800
up_threshold_any_cpu_load: 65
up_threshold_any_cpu_freq: 1190400
boost: 0
boostpulse_duration: 80000
--------------------
Also of note there is not a entry for " io_is_busy " under the Interactive governor under ElementalX Sense kernel v6.03. I believe it's possible to modify the governor to add the function, if it's desired.
Hope this helps others.
nice one i read the links that you posted and follow the guides there also to tweak the interactive governor on the first link that you posted is really interesting he has updated that post also, i followed his guide inspired by your guide and i have been getting good results on my phone with battery and performance i mean almost no battery drain at all while my phone is idle. thanks for the help mate!
Plugged the settings into Yankactive on DU. Quick, freqs stay low when nothings going on, seems legit. I set my timer_rate higher tho, 10000 feels a little low, makes me think that the CPU will spend too much time polling loads.
SaskFellow said:
I noticed I have some governor settings left at 0 or blank. I did some quick googling, found some other tweaks for the M8 and the interactive governor. So I played around a bit, and I think the following would be useful to add to the above tweaks.
-----------------------
sampling_down_factor: 60000
sync_freq: 1036800
up_threshold_any_cpu_load: 65
up_threshold_any_cpu_freq: 1190400
boost: 0
boostpulse_duration: 80000
--------------------
Also of note there is not a entry for " io_is_busy " under the Interactive governor under ElementalX Sense kernel v6.03. I believe it's possible to modify the governor to add the function, if it's desired.
Hope this helps others.
Click to expand...
Click to collapse
Some of those actually make no difference. Since they are overruled by other perameters. E.g. up_threshold aren't used in interactive, since they follow target_load instead.
Sampling_down_factor on the other hand is overrulled by the timer features of interactive.
When you use ondemand, or conservative, sampling_down_factor is a fun parameter to play with, but not interactive.
While Sync_Freq I don't like using because it raises minimum frequency to its value...although temporarily, the timer features can already deal with CPU loads efficiently.
lil_kujo said:
nice one i read the links that you posted and follow the guides there also to tweak the interactive governor on the first link that you posted is really interesting he has updated that post also, i followed his guide inspired by your guide and i have been getting good results on my phone with battery and performance i mean almost no battery drain at all while my phone is idle. thanks for the help mate!
Click to expand...
Click to collapse
Great The links are important!! They are my sources, and often contain much more detail than what I use in my guides. I attempt creating a well ordered summary, but my sources are better if you don't mind reading loads.
I'm glad I could help
munkyvirus said:
Plugged the settings into Yankactive on DU. Quick, freqs stay low when nothings going on, seems legit. I set my timer_rate higher tho, 10000 feels a little low, makes me think that the CPU will spend too much time polling loads.
Click to expand...
Click to collapse
That's the idea. And never heard of Yankactive...but I'm gonna assume it's good lol.
And about time_rate, you are right, but you are also wrong.
There isn't a true right answer unless someone performs a scientific experiment in order to fully test which one is better.
But I'll explain why I put my one short... I want the frequencies returning to IDLE asap. While yes, you are right it's polling often, it also returns to idle much faster, rather than staying at higher frequency uselessly wasting battery.
I'll try to run some tests checking CPU load, if CPU load considerable lowers I'll come back and report.
Yankactive is Interactive with some under the hood tweaks, I believe, same tunables. I also looked at some documentation on Interactive and I think the target_loads have to be in ascending order based on load when paired with clock speeds, I'm gonna mess with them a bit and see what I get. Link
munkyvirus said:
Yankactive is Interactive with some under the hood tweaks, I believe, same tunables. I also looked at some documentation on Interactive and I think the target_loads have to be in ascending order based on load when paired with clock speeds, I'm gonna mess with them a bit and see what I get. Link
Click to expand...
Click to collapse
And no, target_loads has to be in ascending order based on FREQUENCY. You are applying load percentages to frequency ranges, therefore it is imperative that its the frequency defining the order.
e.g. 50 4:80 10:20 12: 50 means:
50% load before going to the next frequency step, until you reach frequency 4, then use 80% instead until frequency 10, then use 20% instead until 12, then use 50% until max frequency.
Feel free to play with them as much as you want, just make sure to keep the idea of using efficient frequency steps in mind.
Kyuubi10 said:
And no, target_loads has to be in ascending order based on FREQUENCY. You are applying load percentages to frequency ranges, therefore it is imperative that its the frequency defining the order.
e.g. 50 4:80 10:20 12: 50 means:
50% load before going to the next frequency step, until you reach frequency 4, then use 80% instead until frequency 10, then use 20% instead until 12, then use 50% until max frequency.
Feel free to play with them as much as you want, just make sure to keep the idea of using efficient frequency steps in mind.
Click to expand...
Click to collapse
Thank you for the knowledge dump, been scraping the barrel for weeks trying to figure out tunables!
munkyvirus said:
Thank you for the knowledge dump, been scraping the barrel for weeks trying to figure out tunables!
Click to expand...
Click to collapse
Hehe it's a pleasure.
It's a way I find to give back to the community, since I learn so much through it. I can try help make life easier for those who follow the same path I did.
Hello kyuubi10 thanks for your help, would it be ok to change mp decision to battery saver mode ? Whats your take on that?
Wow, this is awesome! I had the performance gov on, which just destroyed my battery. Now, I have a question for you!
What is your take on "Multicore Power Savings" ? I'm using a flarport kernel which has it set to aggressive by default. Should this be changed to anything else while using your gov settings? Thanks for any assistance!
lil_kujo said:
Hello kyuubi10 thanks for your help, would it be ok to change mp decision to battery saver mode ? Whats your take on that?
Click to expand...
Click to collapse
I have never heard of mpdecision having a battery saver mode XD
Would you please expand on that? Also tell me which tweaking app you are using?
Kyuubi10 said:
I have never heard of mpdecision having a battery saver mode XD
Would you please expand on that? Also tell me which tweaking app you are using?
Click to expand...
Click to collapse
It's in the ex app mate, it uses a less aggressive version of mpdecision to saver on battery power but I can't say that I noticed much improvement TBH.
Sent from my HTC One_M8 using Tapatalk
Anonaru said:
Wow, this is awesome! I had the performance gov on, which just destroyed my battery. Now, I have a question for you!
What is your take on "Multicore Power Savings" ? I'm using a flarport kernel which has it set to aggressive by default. Should this be changed to anything else while using your gov settings? Thanks for any assistance!
Click to expand...
Click to collapse
You had performance on?? You do realise that the perf gov basically keeps your CPU cores running on max frequency all the time right?
No wonder your battery was dying XD
Anyhoo....good thing you found my guide
Now, about multicore power savings, as usually with most things you will be compromising something to gain something else...always keep that in mind.
With MPS you'll be giving up some multitasking, in order to gain some battery savings.
Why (you may ask)?
Well, think about a to-do list, and for each list you have one person completing the tasks within that list. Let's say you have four lists and 4 people completing those tasks.
What MPS does is it takes as many tasks as possible and places them within a single list, for one person to do. At the end of the day that one person will have done a lot of work, while the other 3 will have done very little work. The drawback? The work was completed much slower, because only one person was doing it.
Why can MPS be good? It is the way it chooses which CPU to use to add the tasks to, it chooses CPUs which are already turned on, rather than turning a new one on.
The frequency voltages on each core range from the lowest of 775mV, to the highest of 1075mV. That's a 300mV increase in battery consumption between lowest frequency and highest. (Mind you, 1075 for me is an overclocked value, if you are not OC then it will be even less)
When CPU cores have nothing to do they get turned off....they don't idle at 775mV....they are literally off. Therefore around 0mV usage XD
If you get tasks which would have run on 2 CPUs at minimum frequency, using only 775mV each, and put them to run on only 1 CPU at MAX frequency at 1075mV, you still have about 400mV battery savings. Now lets say its something which would have used 4 CPUs, but you end up using only two.... then the battery savings double to 800mV.
Final answer...it depends on your tastes, what do you prefer most? Multitasking or battery saving.
Personally I keep it enabled, but not aggressive.
But if you really don't care about multitasking, you may as well leave it as aggressive.
lil_kujo said:
Hello kyuubi10 thanks for your help, would it be ok to change mp decision to battery saver mode ? Whats your take on that?
Click to expand...
Click to collapse
smeejaytee said:
It's in the ex app mate, it uses a less aggressive version of mpdecision to saver on battery power but I can't say that I noticed much improvement TBH.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Well, I use adiutor, so I don't have that option.
I am happy with my phone how it is (if it wasn't for the damned plug issues XD)
But @lil_kujo, as @smeejaytee said....he hasn't noticed much improvement.
So I'd trust his advice
Kyuubi10 said:
You had performance on?? You do realise that the perf gov basically keeps your CPU cores running on max frequency all the time right?
No wonder your battery was dying XD
Anyhoo....good thing you found my guide
Now, about multicore power savings, as usually with most things you will be compromising something to gain something else...always keep that in mind.
With MPS you'll be giving up some multitasking, in order to gain some battery savings.
Why (you may ask)?
Well, think about a to-do list, and for each list you have one person completing the tasks within that list. Let's say you have four lists and 4 people completing those tasks.
What MPS does is it takes as many tasks as possible and places them within a single list, for one person to do. At the end of the day that one person will have done a lot of work, while the other 3 will have done very little work. The drawback? The work was completed much slower, because only one person was doing it.
Why can MPS be good? It is the way it chooses which CPU to use to add the tasks to, it chooses CPUs which are already turned on, rather than turning a new one on.
The frequency voltages on each core range from the lowest of 775mV, to the highest of 1075mV. That's a 300mV increase in battery consumption between lowest frequency and highest. (Mind you, 1075 for me is an overclocked value, if you are not OC then it will be even less)
When CPU cores have nothing to do they get turned off....they don't idle at 775mV....they are literally off. Therefore around 0mV usage XD
If you get tasks which would have run on 2 CPUs at minimum frequency, using only 775mV each, and put them to run on only 1 CPU at MAX frequency at 1075mV, you still have about 400mV battery savings. Now lets say its something which would have used 4 CPUs, but you end up using only two.... then the battery savings double to 800mV.
Final answer...it depends on your tastes, what do you prefer most? Multitasking or battery saving.
Personally I keep it enabled, but not aggressive.
But if you really don't care about multitasking, you may as well leave it as aggressive.
Click to expand...
Click to collapse
Hah, thanks for the guide-- I am pretty well versed in task / resource allocation on multi-threaded systems, though
Main reason I was asking was because I haven't a clue what some of the values are on this interactive gov. Just wanted to make sure they didn't clash! I'll chance it to "Enabled" rather than "Aggressive," because a compromise between the two sounds the best
As for Performance gov-- default setting on this flarport kernel, didn't bother to check it until I noticed that any time a core was on, it was racing at 2.5ghz, even with nothing going on. Battery pretty much committed suicide
Anonaru said:
Hah, thanks for the guide-- I am pretty well versed in task / resource allocation on multi-threaded systems, though
Main reason I was asking was because I haven't a clue what some of the values are on this interactive gov. Just wanted to make sure they didn't clash! I'll chance it to "Enabled" rather than "Aggressive," because a compromise between the two sounds the best
As for Performance gov-- default setting on this flarport kernel, didn't bother to check it until I noticed that any time a core was on, it was racing at 2.5ghz, even with nothing going on. Battery pretty much committed suicide
Click to expand...
Click to collapse
LOL I suggest you change kernel asap! If the dev uses uses Performcance gov as his default he doesn't know what he is doing XD
And no, as far as I know governor tunables won't ever clash with MPS.
Thanks!
rjavc said:
Thanks!
Click to expand...
Click to collapse
You're welcome! Pleasure to help.
But I'd appreciate if you press the thanks button on the relevant posts which helped you. That's the XDA way :good::good:
Kyuubi10 said:
You're welcome! Pleasure to help.
But I'd appreciate if you press the thanks button on the relevant posts which helped you. That's the XDA way :good::good:
Click to expand...
Click to collapse
Hi mate, I wondered if I could ask your advice, I want to set interactive up on my maw Android TV box it's quad 1.5gb and I want maximum performance as its constantly plugged in, there is no battery so that's not an issue,
Sorry if you think this OT but I thought I'd ask you as you know the governor well, thank you in advance mate.
Sent from my HTC One_M8 using Tapatalk