I tried the starving config, but that was unstable on my phone (videos wouldn't play). I upped the voltages for the lower frequencies a bit until it became stable for me... I think the result is pretty much the same as the 'ideal' config, but with lower frequencies added on.

FREQS="0:25,90 125:28,90 250:28,180 500:30,360 550:33,400 600:38,430 700:45,430 750:45,430 805:48,430 850:48,500 900:54,500 950:54,500 1000:60,500 1100:72,520 1150:72,520"

I wrote a couple of dbus scripts so that when the phone is unlocked it runs from 250-1150Mhz (scripts take temperature into account and set max speed accordingly), but when locked it goes down to 125-250Mhz instead.

I've been running like this for about a week with no crashes. The only problem I've had was that one time (and only once) I was unable to answer an incoming call as the touchscreen was unresponsive. I did have a little fiddle with a dbus script to increase clock speeds in the event of an incoming call - I might finish them off if the incoming call problem happens for me again.

In my locked/underclock settings, I use 1% battery per hour... wifi, bluetooth and 3g all enabled... no apps actively running.

In overclock state, the phone seems to reach a maximum of 49celcius no matter how hard I hammer it (I've been using UAE running State of the Art demo, combined with watching BBC News... locks the CPU at 100% at all times). Room temperature here is 23C. This compares to a max temp of 44C when running at the default of 600Mhz.