Hi,
I read the previous post in the thread and see that some people didn't realy know how to optimyze the battery life whith screen off.Or why they didn't get a good battery life.
Because dk doing an amazing job, I decide to contribute to the thread and spend a lot of time to explain how i get great results.( it work for all others rom)
For me last night, i was at 98 % left after 5,5 hours in sleep...(GSM and Wifi always on, GPS off, bluetooth off and of course sreen off...)
First my config.
recovery 4ext.Data++.ext 4(1 go),no swap partition.
Full wipe except sdcard.
In aroma, customize install, just to have a working video playback and i didn't installed gmail, coze i don't use it... all the rest is set by default.
I have typocloclock, facebook for android, plume, Go weather, xda app,
system panel,my google account sync + 3 mails(1 push and 2 with update interval of 1 hours) these app are runing in background.
1)-Don't use app like setcpu or juice defender etc... they use themself some battery juice.
2)-'calibrating battery.'
Let your phone discharge to 0%.
Plug in then turn on the phone.
Charge it to 100%.Let it plug.
Discharge it to ~98%.
Turn off the phone. (The led is red.)
Let it plug to have green led.(it can take more than 2hours)
Unplug it then plug it.(The led is again red.)
Let it charge to have green led.(again it can take much time)
Now boot in recovery mod (Vol down+Power)
Wipe battery stats.
Now you sure that the phone is completly charge and will ether be at each charge.
3)-Check all the update interval of your apps(ex: plume 10 min by default :/)
4)-There's a little app who can show you the time that each app take.It's "Sytem panel"( i have the paid version)
Go in menu/setting/, select 'show app cpu' time and 'system process'
With this app you're now able to see how much cpu time yours apps take. (of course, more time=more battery juice).
5)-something else who's very important, it's to have good gsm signal, because with a bad signal it can take very much juice.(mine was at 0% without signal ,this last night.)
An another think, it's not recomended to play with the vdd level voltage, it can make your phone sluggish and made reboot (it take 2~3% to reboot) or freeze etc ...(and in terms of bl it don't make much difference)
Also, sometimes, it can help to fix permissions in recovery (to avoid read/write in system or sdcard ,but this time i didn't do it.)
Now i've made an other experience.
In setting/performance, i've select 'Performance' ,245 min,1113600 max, 'set to boot' .(with performance governors, the cpu is always at the max freq.)
Normaly, whith this setting the phone must be always at 1113600 whith screen on and must go down 245000mhz with screen off(this is doing by the powersave_screenstate scaling script in init.d.)
Whith this setting the phone is extremely responssive, smooth and must have a great battery life with screen off.
But now i want to know if with screen off it goes realy to 245mhz (an other world, if the phone return to the powersave governor)
Lol, i've made some screenshoot, but i'm unable to see them in my windaube.
Now when i check the time_in_state with root explorer, i can see this..(sys/devices/system//cpu/cpu0/cpufreq/stats/time_in_state)
Freq. time in state
245000 90753 ->whith this value, it's sure, the phone change governors to powersave and run at 245000 whith screen off.
384000 24
422400 5
460800 12
499200 0
537600 8
576000 9
614400 8
652800 27
691200 26
729260 40
768000 8
806400 1272
844800 21
883200 8
844800 21
883200 8
921600 30
960000 20
998400 3644
1036800 0
1075200 0
1113600 145108 -> because of the screen on and the performance governors.
There is also an alternative method to know at wich freq your phone is in real time.
you need to have adb and the correct driver on your PC.
This is a copy/paste from suiller's thread(thx to him).
"to check correct behavior connect your device and open a shell (adb shell) then put commands:
cd /sys/devices/system/cpu/cpu0/cpufreq
turn off display (without detach of course)
cat scal*
last two numbers are current min-max frequencies, your freq min-max should be the lowest possible
turn on display and repeat step 3, your freq min-max should jump
if you turn off again your freq min-max should be lowered"
And we can also see the scaling governors.
It look like this;
cat scal*
Voila, that's all
Of course perhaps it can be something wrong with my explain ( i don't know everything), but i think that it's the correct way to have a better phone in terms of performance and battery life.
All credits goesTo dk-zero_cool, suiller, CM team...
Oh and just to say that with the 3,7U0, i haven't encontered any reboot, bsod or sod
I hope it's clear and that it will help you guys to get a better phone, thx for reading and sorry for my bad english