What is ur vfs setting buddy?? From where do u change it?

standard usage? well standard usage for me is all day everyday connected to wifi answering a few calls forwarding major amounts of texts, making notes, playing music, games occasionally.
so my standard usage is different to someone else's standard usage.

used swappolube at first mate changed vfs cache pressure to 10, but then used karam's battery script as this changes it from 10 when idle to 100 when you are using so your getting best of both worlds.

If reducing frequency "jitter" is your goal, you should concentrate on tuning the sampling_rate and up_threshold parameters, or even using the conservative governor. Note that this doesn't necessarily equate to longer battery life.

That's the entire point of powersave_bias, you sacrifice peak performance in exchange for (hopefully) reduced energy consumption.

You need to define a specific workload that can be executed non-interactively (for accurate testing), and then compare the total (ie, spontaneous measurements are useless) energy expended for performing that load at various configurations.

With hw acceleration on, peek performance in basically visual for most of us. No body likes lags even if the process is damn slow.
I'm focusing on using needed frequency and not going to up highest for almost no reason at all. At the same time, Not ignoring the highest frequency but using it only if its completely necessary.
Although conservative governor is a good choice too *i just googled it*

In terms of a phone, Its either we're using it or we're not using it.
In my opinion, even powersave governor would be useful because the processes stop the moment we close the app and phone goes back to idle. In idle, lowest possible frequency is used when powersave_bias is used which would be 500 and wont go higher too often an 250 is disabled and after installing alotta apps, it automatically goes to 500 *thats why 250 is removed from ideal kernel settings*, a constant 500mhz wont consume as much power as fluctuating btwn 500 and 600/700.

I'm looking for something that doesn't reduce the frequency to minimum and lags everything but not too high that its unnecessary and uses alot of power. Its hard to explain. I don't want extremes of either. I want it to be controllable so it saves power and doesn't get too slow. Makes Powersave_bias the best choice.


Powersave governor would cause lags. *the last time i tried it without knowing what it is LOL*
I'm about to switch to conservative gorernor to see the results.

A specific worklod for an hour.. perhaps youtube with wifi on for an hour and see the difference in power consumed. thats high end, Music on for an hour for casual. and idle for no usage. and time difference in 1 hour and difference btwn mAh recorded.

Edit: , I've noticed that on conservative, while calling, the max frew is 750 and on ondemand with powersave, its fluctuating btwn 600 and 700..
plus the effects are faster on ondemand and conservative sticks to one frequency for too long. For example, If I'm using the phone and then close all apps, It take around 10 seconds to come back to 500 and does it slowly step by step eg 750, 700, 600, 550 then 500. and same goes for when you use your phone from idle to start a process.

On my HTC G1 optimal values were:

POWERSAVE_BIAS=200;
SAMPLING_RATE=1000000;
CPU_UP_THRESHOLD=45;

I'm testing them now on the N900.

how did it turn out?

Not bad, lasts about 2 days with standard battery and normal usage pattern.