Overclocking and Undervolting

---

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 1000@56 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.

Originally Posted by hello moto

@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.

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 ...

Originally Posted by yamandude

my setting are -

310MHz - 15vsel

620MHz - 28vsel

820MHz - 38vse

rock stable ....

though even i noticed the unused 2nd clk value ...

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 300@20 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 :P ....

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 ... :P

Originally Posted by yamandude

ol rite .!! .. my eyes were opened :P ....

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 ... :P

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.