Thanks freemangordon, now i understand what it is going about. In situation, where we're close to optimal values, I always prefer a little "too high" voltage, than one "tiny-bit too low", even if it may appear only during certain, specific situations - but, AIUI, You're trying to achieve exactly same thing, 100% safe values, that are - at the same time - saving battery. The idea is very appealing - I wonder, how up times on one battery will look with dual-scud 3000 mAh I'm using

Only one small question remain - do you think that - with new values - current idea of "race-to-idle" (i.e, that limits 500-900, are more power-efficient that 250-900 or 1250-900, due to device finishing tasks faster on 500-900, and setting on 0 for more time), are outdated with new Sr, i.e 125-900 is now more power-efficient (or will be, after finalizing SR vdd2 also)? "Common sense" still tells me, that it's better to finish task on 500 mhz, and sit on 0 mhz (saving on power leakage), than doing it longer on 125 mhz, even extra-low-voltaged. but, I may miss something, that's why I'm asking.

/Estel

@freemangordon...
i tried lowering dsp rates but same results..
and one more thing...it seems like sr_vdd1 decreases the voltages too much as the video that starts playback smoothly starts stuttering in between, when i pause at that moment and resume it, the same sequelae is repeated and ultimately the same notice (saying media format not supported) pops up...the same video is played with my custom profile 250-805 limits with dsp 520 at 805 and 430 at 720 and much reduced voltages i.e 50 at 805 and 720, 48 at 500 550 and 600...
ps vdd1=0 vdd2=1
thanks..

@knobby could you please lock frequencies one by one (starting @500) to check which frequency is problematic.

sorry but did u mean with dsp profile and vdd1=1

locking frequency = device is all the time sitting on one frequency, no matter of load. You can achieve this from kernel-settings. See:

http://wiki.maemo.org/Kernel_Power

yep.

kernel-config load dsp

and after that ssh into device while playing video
and start:

kernel-config lock 500
kernel-config lock 550
...
kernel-config lock 805

and report on which frequency video stops

EDIT:
should we move on IRC?

Is KP profile voltage the minimum voltage that is used and SR enable higher voltages when needed (e.g SR cannot set VDD1 below profile voltages)?

Fast testing w/o SR (w SR)
Incl. File browsing, web surfing, leafpad editing, etc...
17 -> OK (17)
16 -> OK (16)
15 -> OK (18)
14 -> OK (18)
13 -> OK (18)
12 -> OK (18)
11 -> OK (18)
10 -> reset

I thought also same way, but long term testing has shown that 125M & 500M profile is better that single 500M. Most of the prosessing time is on 125M (~75%) and 500M (~25%).
Use case: night time, phone not in use at all.

EDIT: I'll do more testing with 125:12,90 setting. I'll make this a new default setting and w/o SR

It is the starting point, i.e. initial voltage.

EDIT:
So it seems we can go as lower as 11-12 (~740mV). That are very good news re battery life

@freemangordon...
at 500 550 and 600 video is stuttering all the way but no such message (media format unsupported)popped up..(maybe it is normal bcoz of low dsp)

but at 720 and 805 the video showed the same phenomenon but at 720 it was far less than 805...

How's the lag when using the device at 125 min? At 250 I notice a huge lag compared to 500 min when entering the app menu. I know that it's lighter on the battery, but it's annoying