Tried 115% and 125%, none of them boot. Lost 20% of battery try both!
On a side note:
Why remove the user-control through SetCPU and the likes? Now we have to flash a new kernel each time we want to try a different max frequency?
What's the point of the battery saver? Very few phone provide a real 100% (the full capacity is reached only after fully charging that last 1%! I had a HTC Sensation which was doing that and I kept loosing battery capacity over time! Not to mention the small discharge/charge cycles that were taking place between 9x% and 100% killing the battery in the first place: batteries have a limited number of charge cycles).
I wanted to try this C4 state, but bad luck I suppose.
Agreed that setting lowest frequency on standby can be counter-productive: anything running while in standby (sync as one) will keep the phone awake much longer, consuming much more than without reducing frequency! Though measuring the real effect is still to be done: recording CPU activity and awake time would help. Did it in the past and always came to the same conclusion: on dual cores lowering max frequency does the trick, but on single core it's best not to use the lowest frequency but a little higher than the lowest.
128
bloodmoney, on 17 January 2012 - 05:46 PM, said:
