the kernel-specific area and the 5,000 plus messages in the Overclocking thread

Hey, I set my settings at xlv power scheme and @ 250 1000 but I just noticed that my cpu doesn't go anywhere between them. It's just like 250 and 1000 are the only speeds. Any Idea?

Sometimes it will hit 500. Sometimes it may go directly from 250 to 1000. Assuming your tracking this with Conky, you may not see 500 even if it's used for just a second due to the sampling interval Conky uses. IOW, Conky might effectively 'miss' it. Keep watching while something is running and eventually you'll see 500.

I'll try to set the update interval in conky.conf to 0.5 and see what happens

Yes I saw 500 a couple of times!

By default all (I think) the profiles use the "ondemand" scaling governor, this is quite aggressive in increasing the frequency under load.

If it bothers you, you can change this to "conservative", which is far less aggressive about increasing the frequency so is more likely to spend time on the inbetween frequencies, for a temporary change as root type "echo conservative >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor".

For a more permanent change save yourself a custom profile (you may have done this already), you'll find it in /home/user/.kernel and change the line in that file that says "GOVERNOR=ondemand" to "GOVERNOR=conservative", and set your custom profile as default.

Thx i guess this will conserve battery life?

Maybe. It is hard to say. There is an argument that it is better to run at a higher frequency so your N900 can finish what it is doing and go back to idle mode more quickly (where the CPU uses virtually zero power), but I think most people fail to take into account that the voltage is typically increased when the frequency is increased which affects the power calculations, this argument may still be valid even considering that, but I'm not sure.

For me, I use my N900 a lot for listening to downloaded radio shows via the Media Player, which means the CPU is constantly active at a low level, so I think it is better for my use case, since I don't think there is much opportunity for it to idle while doing that, but I also put it on charge when I can, which makes it hard to evaluate the effect on battery life.

Maybe you should try it yourself and see, one effect you may notice from switching the scaling governor to conservative is that it may be a little less responsive at times because it takes longer to scale the frequency up when needed.

Following a few recent posts, I set my max and min freqs to 900, which gave good enough results for me.

Also remember to check after undervolting and overclocking that your DSP is still working. The device can work otherwise fine, but DSP acceleration no longer work for example in Mediaplayer.

For my device this combination seems to be the best and if I try to squeeze any parameter "better", either the device crashes or DSP starts to have hick-ups: LV-profile, 250-900 Mhz, vdd2 SmartReflex enabled but vdd1 disabled.