[Droid Eris Android Development] wilshyre:
Ok guys, I've messed around with this a lot because I really wanted to get it to work for me.. my main rom is taintedtenzo 2.1 v8, and I switch between that and kaos froyo v30.

When I first saw this I tried setting my main profile to 19.2 - 787 MHz and I noticed instantly when my phone clocked down with the screen on that it was settling at 19.2 and staying there if no input activity by me existed to clock it up again! I couldn't believe it. Then I changed my advanced settings some since I had changed my main and other profiles to lowest clock at 19.2.

I changed my sampling rate back to 2,000,000 and killed the power save bias after reading what you guys had to say about the bias killing wake time.. figured I needed to since I changed my clock minimum to 19.2 and it would be clocked so much lower during sleep and idle times.

So anyway, after I did that I checked out my main profile again and watched clock speeds. Now it was clocking down to 19.2 but then it would immediately jump up to 787 or 710 or so and then it would repeat the process of clocking down and then jumping up really high over and over. It was like as soon as it hit 122 to 19.2, something was crashing and jumping up the clock speed again to restart. I knew that was unacceptable.. I couldn't duplicate those results of settling at 19.2 and remaining stable at that clock speed.. well, as I said I really wanted this to work so I continued to play around with my advanced settings.

I tried various settings with the power save bias, as well as sampling rate, up threshold, and ignore nice load.. finally I tried simply changing my sampling rate back to what it was set at when I first tried this, which was 200,000. Up threshold set to 60, ignore nice load=1, power save at 100.. then I checked main profile to watch clock speeds and it worked! With my screen ON I am able to idle at 19.2 mhz and remain stable there with no problems! I then played around some with the settings again to make sure that it was the sampling rate that was affecting this. I was able to change the other settings pretty much to whatever I wanted and it would still idle at 19.2 mhz just fine as long as I didn't mess with the sampling rate if 200,000. As soon as I changed my sampling rate to any substantially different setting number-wise, it would start repeating the cycle of clocking down, reaching 122 mhz to 19.2 mhz, and then immediately jumping up to 710 or more before it would step down again in increments til reaching the lower extremes and then repeat the clock cycling process. Then I just changed it back to sampling rate 200000, and it would clock down fine and remain at 19.2 mhz as long as no input activity interrupted it and clocked it back up.

My settings are now:

200000

60

1 (as hungry man suggested)

60 (as hungry man suggested, thanks)

AND I AM ABLE TO IDLE WITH OR WITHOUT THE SCREEN ON AT 19.2 MHZ AND REMAIN THERE AS LONG AS THERE IS NO INPUT ACTIVITY BY ME!

Also, I checked my time in state readings and after leaving settings like that all night, my time spent in 19.2 mhz DRAMATICALLY outnumbered any time spent in other clock speeds. I also watched my time in state live readings while letting the phone idle with my screen on and the whole time it shows my time in state in 19.2 going up with the occasional jump to 122, only to immediately go right back down to 19.2.

This is awesome. I hope this might help some of you recreate these results as I know it will be saving me a ton of battery. I have not tested battery saving results exactly yet, but it definitely seems to be prolonging battery life already.. I just have not yet made notes and exact time measurements. I will try to later and edit to give results if anyone else is able to duplicate these results. Hope this helps.

Thanks, DS36, for this idea, as I imagine this will save me a lot of battery life.

Tainted Tenzo 2.1 v8 and/or Kaos Froyo v30