Related
I've been using setcpu for a while now, but have never bothered to mess with the advanced settings. Searching around I have only found out what most of this stuff means, but I'm missing some still. I thought I would share my findings. I have included SetCPU's descriptions (in italics) supplemented with my findings.
Governor choices (I'm using king's bfs kernel #1 on fresh 3.1.0.2) -
Ondemand - Uses the highest frequency when tasks are started, decreases step by step
Conservative - Increases frequency step by step, decreases instantly
Interactive - I couldn't figure this one out... any help?
Powersave - Uses the lowest possible clock speed to complete its tasks
Userspace - Manual controll of the frequency
Performance - Always uses the highest clock speed
Advanced Settings -
Sampling Rate - An interval (in microseconds) at which the governor will poll for updates. When this happens, the governor will decide whether to scale the CPU up or down. It uses such little power that it is better at lower values when using profiles such as screen off.
Up Threshold (1%-100%) - Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU up. When using low min values (245), this happens instantly, using higher values (768) it overclocks less often. With Conservative lower values are better because it slowly increases your clock speed to what you need, with Ondemand, higher is better, as it overclocks less often.
Down Threshold (1%-100%) (conservative only) - Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU down. Higher values will offer more aggressive battery saving, lowering the clock speed quicker.
Ignore Nice Load (0/1) - If this value is "1," the system will ignore "Nice" processes when deciding to scale up or down. I need a little more info for this one, what exactly is a nice process? DO NOT GOOGLE 'NICE LOAD' ESPECIALLY AT WORK OR AROUND CHILDREN/WIFE
Freq Step (0%-100%) (conservative only) - Defines how much (as a percentage of the maximum CPU speed) the conservative governor will increase the CPU speed by each time the CPU load reaches the Up Threshold. Increased the value slightly to be able to overclock quicker, but not to high to avoid unnecessary overclocking.
Powersave Bias (0-1000) (ondemand only) - Setting this value higher will "bias" the governor toward lower frequencies. This is a percentage, where 1000 is 100%, 100 is 10%, and 0 is 0%. The ondemand governor will scale the CPU to a frequency lower than its "target" speed according to this value. Gives ondemand some more battery saving potential. High values give worse performance than conservative with equal or worse battery saving. If you want the performance of ondemand with some more battery use values under 200.
I hope this info was helpful to someone, and here are my setcpu settings. I have attempted to target 150-175ms for short and 350-400ms for long benchmarks to match my performance governor and save battery at the same time.
With ondemand I get about 170ms short and 380ms long. I use 90 for up and 50 for powersave. The performance is slightly better than the default settings, and the battery is about equal. I might play with this more, as it should hit the same values as performance with better battery life.
In conservative long benchmarks in setcpu are actually faster than short ones because it takes setcpu time to adjust the speed. Run a short one immediately after a long one to see its actual value. Up changed 75 and down to 25, not much of a change, but drastic performance increase with no battery change. I also increased freq step to 10% to obtain higher speeds faster. Getting the same 170ms short and 370ms long.
My Settings
Conservative 245-1190
Temp > 50C - 768 conservative
Screen Off - 499 ondemand (allows for the screen to be unlocked faster, especially useful with incoming calls)
Charging/Full - 1190 performance
Battery < 15% - 652 conservative
Sampling - 200000
Up Thresh - 75
Down Thresh -25
Ignore Nice - 0
Freq - 10
More DFS Info
SetCPU Info
davebu said:
DO NOT GOOGLE 'NICE LOAD' ESPECIALLY AT WORK OR AROUND CHILDREN/WIFE
Click to expand...
Click to collapse
LMAO 10chars
HondaCop said:
LMAO 10chars
Click to expand...
Click to collapse
Yeah. I almost spit out my Vanilla Coke on that one. LOL
Anytime have any info about nice load or anything to add?
Sent from my HTC EVO 4G.
HondaCop said:
LMAO 10chars
Click to expand...
Click to collapse
I missed this yesterday... Post of the day in my opinion
Thanks dave...good write up
This is what I found about the interactive governor in github:
cpufreq: interactive: New 'interactive' governor
New interactive governor.
This governor is designed for latency sensitive workloads, UI interaction for
example.
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a
workqueue context, the 'interactive' governor does this in a timer context, which
gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling
up, giving the remaining tasks the cpu performance benefit, unlike existing
governors which schedule rampup work to occur after your performance starved
tasks have completed.
Existing governors sample cpu load at a particular rate, typically
every X ms. Which can lead to under powering UI threads when the user has
interacted with an idle system until the next sample period happns.
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to.
There is only one tuneable for this governor:
/sys/devices/system/cpu/cpufreq/interactive/min_sample_rate:
The minimum ammount of time to spend at the current frequency before
ramping down. This is to ensure that the governor has seen enough
historic cpu load data to determine the appropriate workload.
Default is 5000 uS.
Also, in the original application thread as explained by the dev, "nice" processes are:
2. Nice processes are used by the IO scheduler to designate a low-priority process. Ignore nice load basically tells ondemand to disregard processes with higher nice values.
Good topic. You covered the bases pretty well. Glad someone finally put this together as it is useful to know. Now prepare for 1000 threads in the next month asking for the information you just posted.
hey question. i went and purchased SetCPU and attempted to follow your instruction. problem is, whenever SetCPU tries to gain super user permission, it says "no root access granted. Are applications allowed root access?" i dunno what to do. can someone advise me?
Umm, is your phone rooted?
Sent from the void...
Yessir. Since day 2 ^_^ (plus its in my sig)
Sent from my Evo using Tapatalk
SilverStone641 said:
Yessir. Since day 2 ^_^ (plus its in my sig)
Sent from my Evo using Tapatalk
Click to expand...
Click to collapse
Try uninstalling and reinstalling it.
Then double check all of your superuser settings.
SilverStone641 said:
Yessir. Since day 2 ^_^ (plus its in my sig)
Sent from my Evo using Tapatalk
Click to expand...
Click to collapse
Sorry, using the xda app which doesn't display the sig.
Sent from the void...
So, as far as speed/responsiveness of governors goes:
Fastest ------------------------------------------------------> Slowest
Performance ------> ondemand ------> Interactive? ------> Conservative
Poor battery consumption --------------------> Best battery consumption
This thread is exactly what i was looking for, thanks for the detailed explanation of the what and why.
Will try it out this week with Fresh 3.1 and KK#8.
this thread helped a lot, i was just in setCPU messing around with things, now i can use this thread to help get what i want. i bookmark'd the hell out of this thread
Thanks...OP...hopefully people will read it first...try things..then ask questions...
I am still working to see how to get the best battery life from cm6 and snap..
Thanks for the helpful post!
I experienced a "nice load" when I unboxed my EVO. Anyway the only setting I use is:
Screen off: 245/128 on demand.
Works for me. And thanks for this helpful post to help us understand all that technical mumbo jumbo.
So I got a rooted Vanilla install of the latest Sprint OTA Froyo build on my EVO. (the 3.29.651.5 build).
I purchased the latest version of SetCPU (2.03) last night and used the autodetect method for the CPU governor.
I notice on my EVO that I only have these 3 options:
Scaling:
ondemand, userspace and performance....
Is this normal to not have the conservative setting since I have the defacto kernel with a vanilla rom?
Thanks
Sheldon
Okay, so I figured it out, my default kernel does not have these other options, oh well......
Nice app though, so far its working really well.
Was wondering what type of profiles people got setup on setcpu for some good battery durations oc'ed.
I'm currently running at 1417MHZ and only profile I have setup is screen off. 275 / 275 conservative. Priority is at 100.
Sent from my HTC Vision G2
I'm running at 1305MHz.
Screen off 245min/245max
Temp > 38.2 C 245min/768max
Battery < 15% 245min/768max
Mines going at 200 mhz to 1000 mhz, on demand governor, and a powersave bias of 20%. No profiles. Why? Because to implement the profiles setcpu has to remain in memory. It does not feel slow at all and I'm getting terrific battery life.
Sent from my G2.
mejorguille said:
Mines going at 200 mhz to 1000 mhz, on demand governor, and a powersave bias of 20%. No profiles. Why? Because to implement the profiles setcpu has to remain in memory. It does not feel slow at all and I'm getting terrific battery life.
Sent from my G2.
Click to expand...
Click to collapse
sorry im a newbie, how do you set the "on demand governor?" .and powersave bias, u get that from the advanced tab where it says "powersave bias (1-1000)" and just put 20?
donaliar said:
sorry im a newbie, how do you set the "on demand governor?" .and powersave bias, u get that from the advanced tab where it says "powersave bias (1-1000)" and just put 20?
Click to expand...
Click to collapse
Well the scaling governor is on the main page, right under the minimum frequency slider. You are only half right on the powersave bias: 20 would be 2%. So to do 20%, you need 200. Sorry if I wasn't clear.
Sent from my G2.
mejorguille said:
Well the scaling governor is on the main page, right under the minimum frequency slider. You are only half right on the powersave bias: 20 would be 2%. So to do 20%, you need 200. Sorry if I wasn't clear.
Sent from my G2.
Click to expand...
Click to collapse
Oh alright. my sampling rate is 50000. up threshold 95. ignore nice load 0. and powersave bias 200. does that sound about right? or should i change somehthing else? Thanks for the help!
Got my profiles at:
Screen off 245/245 priority 100
Temp > 102F 245/768 priority 80
Battery < 10% 245/245 priority 70
Battery <15% 245/368 priority 65
Battery <25% 245/768 priority 60
Charging/full 245/1459 priority 50
I just set these up so ill report back with how it turned out
mejorguille said:
Mines going at 200 mhz to 1000 mhz, on demand governor, and a powersave bias of 20%. No profiles. Why? Because to implement the profiles setcpu has to remain in memory. It does not feel slow at all and I'm getting terrific battery life.
Sent from my G2.
Click to expand...
Click to collapse
Questions:
Did you notice battery drain with setcpu in memory?
How is the battery temp?
Does the powersave bias mean that you will never scale to the peak value?
Had the phone off the charger since 11am.
Moderate call usage
Heavy texting
Moderate internet usage
Music for roughly 3hours straight
Wireless tethering on Xbox live for roughly an hour
At 9:15pm I have exactly 40% with my profiles from my post above
what does 245/768 mean?
nvm i got it
potentdro said:
what does 245/768 mean?
Click to expand...
Click to collapse
245 min, 768 max
So its a bit after 1am and just over 14hrs after a full charge. While using my profiles and info as posted in my above 2 posts along with 2hrs of GPS usage, light phone call usage, and heavy internet usage my phone finally died 14hrs later with the Gov module on conservative with posted profiles and OC'd at 1459.
Although abought 10min prior to it dieing I did attempt to submit this post from the phone but near the end of the post it froze up, showed the desktop and my battery notification showed 0% and the phone then rebooted itself but I got a bootloop on the "g2" screen and had to pull the battery to fix it.
After 10% battery level I was experiencing lagging and slowness while online so I'm assuming because of my profile setting of 245/245 at that battery level and what probably caused my bootloop.
*Edit: I must say I'm pretty impressed. I had my Nexus one alot more heavily modified than my g2 and only OC'd to 1113 with similar daily usage and I would have to charge it one time at some point during the day to last me throughout the night.
SRT102JZ said:
Got my profiles at:
Screen off 245/245 priority 100
Temp > 102F 245/768 priority 80
Battery < 10% 245/245 priority 70
Battery <15% 245/368 priority 65
Battery <25% 245/768 priority 60
Charging/full 245/1459 priority 50
I just set these up so ill report back with how it turned out
Click to expand...
Click to collapse
What do you have set up in "Main" tab?
Thanks. I'm going to try your settings.Battery life is disappointing...
Sent from my T-Mobile G2 using Tapatalk
Okay, so I got my G2 about two weeks ago, and have been running set CPU with these settings since then.
Main profile: 1478 max / 245 min
Screen Off: 245/245, Priority 100
Temp > 100.4 F: 368/245 Priority 97
Temp > 96.8 F: 768/245 Priority 95
Battery < 20%: 245/245 Priority: 82
Battery < 30%: 368/245 Priority: 81
Battery < 40%: 768/245 Priority: 80
Charging/Full: 1478/245 Priority 60
Charging USB/Full: 768/245 Priority 55
Charging AC/Full: 1478/245 Priority 50
On light use I've gotten almost two days, by light use I mean only a few phone calls or text messages and data turned off. On Normal use I've been averaging around 16 hours, and on heavy use I've been getting around 10 hours. Pretty good battery life, I'm pleased with it being my first Android phone, was a black berry user before this.
I have SetCPU set with all of these profiles, other then charging profiles and it seems that the "Screen Off" profile isn't working. I have it set to 245/245 and it still seems to be at 1497/245 because the battery gets hot and drains very fast (about 8 hours with literally zero use). It shows idle Cell Standby and Phone Idle taking up most of the battery (a combined total of about 85%) anyone know why it wouldn't be working properly?
SetCPU has SU permissions and profiles are enabled... Anything else?
Is SetCPU a lot better then the free CPU tuner? I know it's only 1.99, but I'm feeling cheap at the moment.
ScottRTL said:
I have SetCPU set with all of these profiles, other then charging profiles and it seems that the "Screen Off" profile isn't working. I have it set to 245/245 and it still seems to be at 1497/245 because the battery gets hot and drains very fast (about 8 hours with literally zero use). It shows idle Cell Standby and Phone Idle taking up most of the battery (a combined total of about 85%) anyone know why it wouldn't be working properly?
SetCPU has SU permissions and profiles are enabled... Anything else?
Click to expand...
Click to collapse
you have to make sure the priority is at a higher level than all the others...like 100
abenco said:
Is SetCPU a lot better then the free CPU tuner? I know it's only 1.99, but I'm feeling cheap at the moment.
Click to expand...
Click to collapse
You can get the full version on xda for free. It's nice to donate though.
Sent from my T-Mobile G2 using XDA App
need some help
my htc wont show any clock speeds past the 806mhz. ...any ideas? i tried to perflock disable and it says it is already..and in custom profiles it shows still only max up to 806
edt** read a custom kernal may be required...im on stock. thats probably why
I was wondering what would be considered optimal settings for SetCpu. I amn running BaconBits and am not sure how I should do the settings.
Any help would be appreciated!
Thanks.
i have mine set at:
Profile 1 : 806 MHz max, 245MHz min, On Demand, priority 50
Profile 2 : 245 MHz max , 245MHz min, On Demand, for when the screen is off, priority 50
if i change the MHz, i change it higher on profile 1 for whatever i need it for then i just scale it back down to 806 when i am done...
Mines pretty much the same as the one above save for max clock speed being 1500Mhz.
Sent from my HTC Vision using XDA App
I have my scaling set ondemand, have setcpu set at boot, with 1497 max and 245 min, with profiles for various states of the phone.
My profiles:
Screen off: 245 max, 245 min - Priority=100
Battery temp >104: 806 max, 245 min - Priority=90
Battery <10: 245 max, 245 min - Priority=80
Battery <20: 368 max, 245 min - Priority=70
Battery <30: 768 max, 245 min - Priority=60
Charging/Full: 1497 max, 245 min - Priority=50
I get well over a day of use, even with moderate-heavy usage, even with my overclocking on Evil's Sense ROM.
If you search google for an "overclocking 101" thread you should find a rather large ongoing break down of setcpu and the most efficient way to use it. I believe its on one of the droid forums, awesome info.
tazz9690 said:
I have my scaling set ondemand, have setcpu set at boot, with 1497 max and 245 min, with profiles for various states of the phone.
My profiles:
Screen off: 245 max, 245 min - Priority=100
Battery temp >104: 806 max, 245 min - Priority=90
Battery <10: 245 max, 245 min - Priority=80
Battery <20: 368 max, 245 min - Priority=70
Battery <30: 768 max, 245 min - Priority=60
Charging/Full: 1497 max, 245 min - Priority=50
I get well over a day of use, even with moderate-heavy usage, even with my overclocking on Evil's Sense ROM.
Click to expand...
Click to collapse
I just stole the rest of your settings, hope you dont mind!
WarBird87 said:
I just stole the rest of your settings, hope you dont mind!
Click to expand...
Click to collapse
By all means, have at it!
Main profile: 245 - 1017 on demand
Charging/Full: 1017 - 1017 performance 90 priority
Screen Off: 245 - 245 performance; mainly as this mode will bypass the need to poll/sample for CPU speeds, thus reduces some CPU load. 100 priority
Battery < 20%: 245 - 768 on demand 75 priority
i decided to put the SetCPU widget on my homescreen last night so i could see if the profiles were actually changing as my battery ran lower... and my phone got reaaaalllly sluggish to the point where i would have to wait a few seconds for it to flip back and forth between screens... i deleted the widget thinking that might have caused it, but it was still laggy... so i unclicked on the profiles for battery and got it back to 806MHz and it was fine again...
im guessing that it supposed to slow down the phone when the CPU drops below 806MHz but i didnt think it would be that bad... anyone else experiance this?
WarBird87 said:
i decided to put the SetCPU widget on my homescreen last night so i could see if the profiles were actually changing as my battery ran lower... and my phone got reaaaalllly sluggish to the point where i would have to wait a few seconds for it to flip back and forth between screens... i deleted the widget thinking that might have caused it, but it was still laggy... so i unclicked on the profiles for battery and got it back to 806MHz and it was fine again...
im guessing that it supposed to slow down the phone when the CPU drops below 806MHz but i didnt think it would be that bad... anyone else experiance this?
Click to expand...
Click to collapse
What are the profiles you are using? The ones you copied shouldn't have run into any conflicts... except when you're under 20% battery where the CPU is throttled under 368.
What is your powersave bias?
Speaking of powersave bias, could anyone tell me some optimal settings for the setCPU advanced tab? Don't mean to derail this thread, I've just never used that tab.
Sent from my T-Mobile G2 using XDA App
SeReaction said:
What are the profiles you are using? The ones you copied shouldn't have run into any conflicts... except when you're under 20% battery where the CPU is throttled under 368.
What is your powersave bias?
Click to expand...
Click to collapse
I believe i was right at 20% batt or right below,so that could have been the issue... I havent messed with anything on the advanced tab as i dont know much about it, the powersave bias is still set to 0
I have HTC heroc 200 alltel running fresh 2.40 rom firerat mtd 160 10. what should I set CPU to
Sent from my HERO200 using XDA App
does anyone else feel that their battery lasts longer without using setcpu at all? I mean I love what setcpu can do but in terms of power efficiency, even without overclocking, for some reason I feel like my battery last longer without it.... or am I just crazy?
j.books said:
does anyone else feel that their battery lasts longer without using setcpu at all? I mean I love what setcpu can do but in terms of power efficiency, even without overclocking, for some reason I feel like my battery last longer without it.... or am I just crazy?
Click to expand...
Click to collapse
I used to get about a whole day without setcpu. With setcpu, same amount of usage, I get well over a day and a half before having to charge it up.
Been lurking for close to a year, but first time posting, so my apologies if this is not the correct forum or location for this question. I would have posted in the Glitch kernel thread but I'm still stuck in the noob-lockout.
I'm running the latest CM7 with the latest, high-leakage Glitch kernel. I became suspicious after I "calibrated" my battery (charged to 100%, reset stats, drained to 0%) and noticed that my battery life was much better while in deep sleep, but with the screen on it was draining at almost 1% per minute. In deep sleep I will get somewhere between 2-5% drain per hour.
CPU Spy shows my frequency breakdown as 1000Mhz at ~10% and Deep Sleep at ~90% with all other frequencies at virtually 0% (this is with resetting the timers and running for a day).
I would think that even with the screen on, there will be moments when the CPU will be throttled down. Running SetCPU on previous roms, I noticed that when idling, the CPU speed would often drop to 100Mhz, but this doesn't seem to be happening with my setup.
I didn't notice any comments in the Glitch or CM7 threads regarding this phenomenon, so I'm wondering if it's something I failed to setup correctly or some other cause.
As an update, I've switched back to the stock CM7 kernel and it is properly throttling down now. 100Mhz is now showing a much higher percentage in CPU Spy.
I would really like to switch back to Glitch, but unless there's some solution it doesn't seem like it's worth the huge increase in battery usage.
Sent from my SCH-I500 using XDA App
You must have a setting incorrect.
Being clocked at 1.2ghz (BFQ i/o and Smartass) CPU spy is telling me the following
1200Mhz - 4:03 - 0%
1000Mhz - 1:01 - 0%
800Mhz - 9:05 - 1%
400Mhz - 7:037 - 1%
200Mhz - 4:59 - 0%
100Mhz - 21:09 - 4%
Deep sleep - 7:40:15 - 90%
What Governor did you try?
I was using bfq with smartass.
Sent from my SCH-I500 using XDA App
I'm also using cm7 and tk-glitch v11 hl since yesterday.
Playing with settings right now, using pimp my cpu and cpu spy.
Questions:
-Do I have to enable the option "force minimal freq. when screen off''?
-After how many minutes does my sgs go into deep sleep mode?
Cota82 said:
I'm also using cm7 and tk-glitch v11 hl since yesterday.
Playing with settings right now, using pimp my cpu and cpu spy.
Questions:
-Do I have to enable the option "force minimal freq. when screen off''?
-After how many minutes does my sgs go into deep sleep mode?
Click to expand...
Click to collapse
Are you experiencing the same increased battery drain with the screen on?
1. Using SetCPU is asking for trouble (random reboots, etc). The Glitch thread OP says to use Voltage Control instead.
2. High Leakage = fewer problems for those with lower quality hardware build (yes, it varies from Fascinate to Fascinate - all Fascinates are not assembled equally), but poorer battery life. Low-leakage = better battery life, but you better hope your Fascinate was assembled well because if it wasn't, you'll have more fcs and freezes than on medium or high leakage.
3. There is no combination of governors, voltages, and schedulers that is the best for everyone - each combo will work better for some than for others
I hope this helps
Another Fascinating post by my XDA app...
I remember reading about the dangers of using SetCPU with this ROM, so I've only been using Voltage Control.
My problem doesn't seem related to the governor or scheduler, since each combination yields the same result.
The problem is that the CPU speed jumps to 1000Mhz as soon as the screen is turned on, and stays at 1000Mhz until it's turned off, which causes it to drop down into Deep Sleep. There is no in between, not with any combination of scheduler or governor, it's either full blast or nothing.
lagbot7000 said:
I remember reading about the dangers of using SetCPU with this ROM, so I've only been using Voltage Control.
My problem doesn't seem related to the governor or scheduler, since each combination yields the same result.
The problem is that the CPU speed jumps to 1000Mhz as soon as the screen is turned on, and stays at 1000Mhz until it's turned off, which causes it to drop down into Deep Sleep. There is no in between, not with any combination of scheduler or governor, it's either full blast or nothing.
Click to expand...
Click to collapse
Try an overclock - train your phone to use something other than 1000 Mhz
Another Fascinating post by my XDA app...
I decided to restore back to DI01, and use the OTA updates to bring myself back up to ED05. I then reflashed CM7 and Glitch and this problem has gone away. Not quite sure what caused it, but it's running great now.
Running at a solid 1200Mhz with -50mV.
Yes still draining, locked up in 800 mhz cpu freq. (cpu spy) and no deep sleep mode. I'm going to reflash the kernel soon.
Something went wrong I guess (stucked in glitch bootscreen after flashing).
First cleaning scripts and flash the default cm7 kernel for my sgs to be sure.
It should work well according to a member in glitch sgs topic.
The past few days, I started really paying attention to my overclock settings to save battery life. But I noticed a major bug---no matter what I did on ANY CM7 rom---, Vsel 2 would have 3 seconds max use over many hours of use, or be the ONLY one used, besides deepsleep. I tried different combinations of governors and settings until I found a solution to get the governors to work and behave correctly. You can check with CPU Spy.
It seems to be a loading error when using the same governor in bootmenu and CM7 settings.
What I did was go to the bootmenu and enable load all modules, configure the governor I wanted to use, then select a different governor to use.
Then after booting, go to the CPU settings and select the governor you want to use and the apply on boot setting. As long as boot governor and cm7 governor are different and apply on boot is selected, the cm7 selected governor will perform like you programmed it to do in the bootmenu.
That made all the difference in the world. Before I rebooted to install Test3, CPU Spy showed 6 hours deepsleep, 10 hours Vsel1, 5 hours Vsel2, and 1.5 hours Vsel 1. Vsel 1 would have been lower, about 3~4 hours, but I fell asleep listening to music.
After 8 hours, lots of use (30 mins wifi, 15 mins talk, 45 mins screen on time) I still had 89% battery when I plugged in to my pc to transfer WR1.4.
My CPU settings are
Vsel1 300\22
Vsel2 700\44
Vsel3 1100\56
Governor Conservative (in CM7 Settings, smartass in bootmenu)
con up threshold 100
con down threshold 40
con freq step 4
con sampling rate 160000
I've also had good results with these smartass settings
smt_min_cpu_load 40
smt_max_cpu_load 100
smt_awake_min_freq 300000
smt_sleep_max_freq 450000
smt_up_min_freq 1100000
smt_wakeup_freq 700000
smt_ramp_up_step 400000
Anyone else have any good OV\UV settings?
And yes, my Bravo does run stable with the above CPU rates. I've read posts where people couldn't UV to [email protected] or 57 without instability issues. Makes me feel lucky and happy. But that is my phone's limit with good roms. I have to use 700\45 and 1100\57 with ICS. 1200\58 no matter what rom.
more undervolting
My current settings (on MIUI 2.3.30) are:
300MHZ @ 16
700MHZ @ 36
1100MHZ @ 54
At first I only got
300MHZ @ 21
700MHZ @ 44
1100MHZ @ 55
I think the key here is letting the chip be familiar with a new voltage. Everyday I only reduced the voltage settings by 1 or 2, and I did it until I couldn't. I also recommend an app called SetVsel. It has an utility to stress test the chip at a specific speed.
Hope this will help.
I may be mistaken, but I believe 20 is the hard coded lowest vsel you can actually go. 75 is highest. I actually use Stability Test for variable voltage testing, and also by setting the min/max values to whatever I'm currently testing in performance settings. I used to use SetVsel, but I got rid of it since I can do everything it can do with any rom other than stability testing.
Gradually stepping down over time is an interesting idea I'll have to try.
I will try this out, thanks
@skeevy420
I'm not so sure, but 16 is fine for 300Mhz, and when I changed it to 15, the phone rebooted. Yes I agree with you on SetVsel, I just used to find the lowest vsel levels, I don't use it anymore.
For the battery life, my cell lasts for roughly 3 days. I listen to music 4-5 hrs day, do some calling, some angry bird, and surfing over the WiFi sometime, of course I switch it to flight mode at night. I guess 45nm process makes the OMAP3630 really awesome.
hello moto said:
@skeevy420
I'm not so sure, but 16 is fine for 300Mhz, and when I changed it to 15, the phone rebooted. Yes I agree with you on SetVsel, I just used to find the lowest vsel levels, I don't use it anymore.
For the battery life, my cell lasts for roughly 3 days. I listen to music 4-5 hrs day, do some calling, some angry bird, and surfing over the WiFi sometime, of course I switch it to flight mode at night. I guess 45nm process makes the OMAP3630 really awesome.
Click to expand...
Click to collapse
20 was something I read at Deft Dev a few months back. Not sure if it was 300mhz or 20vsel being the lowest. 16 is awesome. I need to try that when I'm done with MS2G.
my setting are -
310MHz - 15vsel
620MHz - 28vsel
820MHz - 38vse
rock stable ....
though even i noticed the unused 2nd clk value ...
yamandude said:
my setting are -
310MHz - 15vsel
620MHz - 28vsel
820MHz - 38vse
rock stable ....
though even i noticed the unused 2nd clk value ...
Click to expand...
Click to collapse
Pick different governors in the boot menu and in the CM7 Performance menu and select apply on boot. There's a bit of a glitch when you don't, unless you're using ondemand, then 2nd clk may never be used.
Ondemand, Performance, and userspace will use the most Battery; Performance\userspace will stay at vsel3 so its best for performance testing\draining the battery for calibration.
Smartass and Conservative, when properly configured, use all the vsel's efficiently, but Smartass jumps to vsel3 then scales down to where its needed while Conservative only scales up as needed. That's why you can get a bit of lag with conservative--it hasn't scaled up yet. Try using these to get vsel2 to be used.
The only problem is that 600mhz really isn't that powerful and will probably always get scaled up, that's why I use 700mhz at vsel2, its barley enough to play mp3's with dsp and effects without going up to vsel3. I actually get pretty even usage of all 3 vsel's, but I've modified my conservative settings since the first post. Now I use:
300MHZ @ 20
700MHZ @ 42
1100MHZ @ 56
con up threshold 100
con down threshold 30
con freq step 8
con sampling rate 160000
I could probably lower the voltage a bit, but when you're always changing crap, testing things, and have wifi on a lot and tether, the [email protected] keeps it stable, and won't crash when receiving a call when doing that.
The low vsel1 rates are good and fine, until you have your screen off-mp3's playing, or are tethering with wifi and your phone reboots when an incoming call comes in. I really wouldn't go past 20 on the lowest vsel---undervolting too much is just as bad as overvolting and can fc apps or short out your hardware when it doesn't get the juice it requires. Undervolting too much is actually worse for your phones, btw.
I'm a welder by trade, so I know a thing or two about not supplying enough power to your tools--try welding off a 2500amp generator. Won't happen, 3250amp is minimum, and that barley cuts it. Same thing when using thin gauge power cords, they'll fry tools quicker than a dumbass using them improperly. My power cord for my flux core tig is 1.5 inches thick and only 25 ft long. My alternate cord is just as thick, but 50 ft long and is only used when we can't use a generator in the neighborhood and the 25 footer isn't long enough. The same principles apply when undervolting your phone, and too little voltage is the worst thing you can do.
ol rite .!! .. my eyes were opened ....
cool so if i do the settings , same as urz , the threshold values and all with smartass governor ... and do the minimum clk at 350MHz with 20vsel ....
that'll be cool ?
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
or perhaps 320 MHz ...
yamandude said:
ol rite .!! .. my eyes were opened ....
cool so if i do the settings , same as urz , the threshold values and all with smartass governor ... and do the minimum clk at 350MHz with 20vsel ....
that'll be cool ?
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
or perhaps 320 MHz ...
Click to expand...
Click to collapse
I'd use 20-24 at 350mhz. Any reason why you're using 350mhz instead of 300mhz? Only reason I can think is for the (slightly) extra power, maybe less lag right when the screen comes on\exiting deep sleep mode.
Try these settings for smartass, but adjust up_min_freq to your vsel3, awake_min_freq to vsel1, I like to set wakeup_freq to vsel2 for responsiveness or vsel1 for battery, vsel 3 for max power. I use sleep_max_freq at 450000 because I use wifi and tethering at the same time a lot and it helps with stability. If you haven't noticed, I use the same setup with smartass and conservative. If you have scaling lag with these settings, lower max_cpu_load down a bit, but I wouldn't go past 90 with smartass since it'll turn into be a cpu intensive ondemand; same thing with conservative.
Also, all my suggestions\tips are based on my 1100\700\300 setup. You can lower min_cpu_load as you lower vsel3 and 2, but I don't recommend going under 20 or over 50. Under 20 may not drop vsel and over 50 can drop abruptly when it shouldn't or cause the phone to switch frequencies to often to be useful and cause instability.
smt_min_cpu_load 30-35 (My formula is take Vsel3 and figure out what percentage lands between Vsel 1 and 2. @1100, 30 is 330mhz, 40 is 440mhz; don't go too high or it can drop too fast, especially with conservative.)
smt_max_cpu_load 100 (lower if you get lag)
smt_awake_min_freq 300000 (set to Vsel1)
smt_sleep_max_freq 450000 (or 300000) (or Vsel1)
smt_up_min_freq 1100000 (set to Vsel3)
smt_wakeup_freq 700000 (vsel1 for battery, 2 for responsiveness, 3 for power)
smt_ramp_up_step 400000 (I set to the difference between frequencies)
When not configured correctly to you're current frequencies, there's no point in smartass or conservative. It took me about a week of experimenting to find those values for those frequencies.
ok .. mine now are ...
350MHZ @ 20
650MHZ @ 32
1000MHZ @ 46
con up threshold 100
con down threshold 30
con freq step 8
con sampling rate 160000
smt_min_cpu_load 30
smt_max_cpu_load 90
smt_awake_min_freq 350000
smt_sleep_max_freq 450000
smt_up_min_freq 1000000
smt_wakeup_freq 650000
smt_ramp_up_step 350000
this cool or ... do temme
F
yamandude said:
ok .. mine now are ...
350MHZ @ 20
650MHZ @ 32
1000MHZ @ 46
con up threshold 100
con down threshold 30
con freq step 8
con sampling rate 160000
smt_min_cpu_load 30
smt_max_cpu_load 90
smt_awake_min_freq 350000
smt_sleep_max_freq 450000
smt_up_min_freq 1000000
smt_wakeup_freq 650000
smt_ramp_up_step 350000
this cool or ... do temme
Click to expand...
Click to collapse
Shouldn't be a problem. Are you actually stable at those voltages? If so, stay
if you get good vsel usage. Bravo doesn't like going under [email protected], but I think Bravo's are made with sub par Defy processors (didn't pass quality control for 1000mhz.). Cheaper to use them at 800mhz than it is to scrap them). Although I haven't tried going that low in a while, CM7 may be more stable for that now. Miui always handles undervolting better than CM though.
My ghetto stability test is to open 10+ loading tabs in Dolphin HD Dolphin fc's easily when many tabs are open when undervolted too low.
Its best to wait 12 hours with real world usage to see how effective the oc settings are, unless its obvious that you're getting bad usage. Also try to wait a half hour minimum after booting before using CpuSpy to see better results. Boot up uses vsel3, so account for a 1-2 minute difference when checking levels right after boot.
ok .. and yes . m geting stable usage at those voltage ... even 1.2GHz at 58 vsel ... .. though m cool with these ... so .. will tell the results later