CyanogenMod vs Froyo - battery drains

[cooladityarai]

Anyway to do this via terminal .....??

Sent from my GT-I5500 using Tapatalk

[Ice The Gun™]

Anyway to do this via terminal .....??

Sent from my GT-I5500 using Tapatalk

just remove the adb shell text,
su first
go to /sdcard
and type dumstate >dumstate.txt

but got dumping problem for some process

Sent from my GT-I5500 using Tapatalk

[Leproso_Ivan]

Hi..
I use CyanogenMod 7 v1.3 + hotfix 1 >> Full charged 100% >> used by 13 hs >> Use message, Twitter in 3g, 2 calls..


You are not allowed to view links. Register or Login

Sorry for my bad english 

[wisanggeni]

You are not allowed to view links. Register or Login
15,5 hours using,3 % left,using it for calling, facebook,browsing,txt,chat,take some picture,2 hours off playing music,6 hours idle(sleep).
35 apps,font custom, launcher adw ex, swap 128Mb, no compchace, cpu default 245-604,smartass, Vm 24 MB,s2e with apps, private apps, dalvik and chace on ext4.
1.3+hf1

[celula]

Hi again, first of all, i've done a Battery Calibration and i think it works, my battery life has improved, and if there is a battery life issue in this rom, i think is small. I don't know if you're interested in steps i followed to do it, if you're just tell me.

I gave a normal use: A lot of WiFi (Tapatalk, Facebook, MSN, etc.), a little phone calls, sms day & night, little playing, and not very much music.
Has you can see, mi battery lasted 1d 9h 40m. (Now 4%.)
In screenshots doesn't appear all what i've used, don't know why.

CPU Settings: Governor smartass.
                       Min 245Mhz, Max 604Mhz.
Compcache: 18% (default)
JIT: Disabled.
Surface Dithering: Disabled.
VM heap size: 24m.

Just want share my experience. And hope be useful in some way.
And of course, the dumpstate:
You are not allowed to view links. Register or Login

[topsi]

Hope this helps:
You are not allowed to view links. Register or Login

Baseband: I5500LUYJPE
governor: ondemand
min: 245, max 604
Using JIT

Not using 3G or GPRS
Bluetooth on most of the time.
Few wireless connections, few calls.
No GPS usage.

I noticed that battery scale is logarithmic. First 10% of battery drain takes same time as from 90 to 50 and from 50 to 0 takes half the time. I did battery calibration, doesn't help.
I also noticed some problems connecting to wireless networks - on specific networks DHCP doesn't work, I must use static IP.

[MayurV]

I had same problem, and i have troubleshooted by doing 2 thing....1. reflash CM7.1 with data wipe and all    2.used Autokiller memory optimized app. I never believed in any app those claim battery optimization but the Autokiller memory optimizer description makes sense...since it hard code the Ram memory usage level and kill hidden app that you no longer using. try it and let me know if both way it works or not.

Hope this helps:
You are not allowed to view links. Register or Login

Baseband: I5500LUYJPE
governor: ondemand
min: 245, max 604
Using JIT

Not using 3G or GPRS
Bluetooth on most of the time.
Few wireless connections, few calls.
No GPS usage.

I noticed that battery scale is logarithmic. First 10% of battery drain takes same time as from 90 to 50 and from 50 to 0 takes half the time. I did battery calibration, doesn't help.
I also noticed some problems connecting to wireless networks - on specific networks DHCP doesn't work, I must use static IP.

[psyke83]

Thanks again for all the testing. I'll be analysing the dump logs.

I have one more request for people:

Please follow the same instructions again, with one important difference. Before you begin (at 100% battery), modify your configuration:

Settings -> ADWLauncher -> System Preferences -> Home Orientation. Change this setting to Portrait.

If you are using LauncherPro, there may be a similar setting to disable the automatic orientation.

I'd appreciate the logs again, but also some feedback as to whether you think the battery life has improved when sensors are not used by the home launcher.

[topsi]

Hi,
I am already using ADW launcher with portrait home orientation, so my previous log made with the setting required.

I cannot say anything about battery life improvance because I use this setting from beggining.

[wisanggeni]

Thanks again for all the testing. I'll be analysing the dump logs.

I have one more request for people:

Please follow the same instructions again, with one important difference. Before you begin (at 100% battery), modify your configuration:

Settings -> ADWLauncher -> System Preferences -> Home Orientation. Change this setting to Portrait.

If you are using LauncherPro, there may be a similar setting to disable the automatic orientation.

I'd appreciate the logs again, but also some feedback as to whether you think the battery life has improved when sensors are not used by the home launcher.

i think ive already done this, i always disable my auto rotate, what about the theme? is it afect the battery life?

[MayurV]

ADWLauncher doesn't help with disabling sensor.

I was playing around...found interesting....ActivityManagerService.java tracks the processes which is foreground, is running a service.. and its because a value is set in setting "oom_adj" of the process. This oom_adj give signal to android kernal to kill the process if it goes out of memory(oom). I found this kernel source in "lowmemorykiller.c" which is located in the kernel source tree under "drivers/misc/".

so i ran
# cat /sys/module/lowmemorykiller/parameters/minfree

and got output like this: 1536,2048,4096,5120,5632,6144  this numbers are pagesize.
I changed this page value in terms of MB. (for calculation 1 page=4kb)
and there you go, i set minimum page size 60MB...if android memory usage goes below 60MB it will kill those foreground processes that actually using kernel resources . I think it saved almost 15% of my battery so far...can not say exactly...but still working on that if i can get better page size for our CM 7.1. May this concept can give better idea to you.

Any thoughts, Psyke83?

Thanks

It seems that on Android the current forefround application gets an oom_adj value of 0 and as soon it's not visible anymore it gets some higher value. I assume the concrete value is dependent by the processes' place in the LRU list.

Thanks again for all the testing. I'll be analysing the dump logs.

I have one more request for people:

Please follow the same instructions again, with one important difference. Before you begin (at 100% battery), modify your configuration:

Settings -> ADWLauncher -> System Preferences -> Home Orientation. Change this setting to Portrait.

If you are using LauncherPro, there may be a similar setting to disable the automatic orientation.

I'd appreciate the logs again, but also some feedback as to whether you think the battery life has improved when sensors are not used by the home launcher.

[MayurV]

Anyone has noticed below post.

ADWLauncher doesn't help with disabling sensor.

I was playing around...found interesting....ActivityManagerService.java tracks the processes which is foreground, is running a service.. and its because a value is set in setting "oom_adj" of the process. This oom_adj give signal to android kernal to kill the process if it goes out of memory(oom). I found this kernel source in "lowmemorykiller.c" which is located in the kernel source tree under "drivers/misc/".

so i ran
# cat /sys/module/lowmemorykiller/parameters/minfree

and got output like this: 1536,2048,4096,5120,5632,6144  this numbers are pagesize.
I changed this page value in terms of MB. (for calculation 1 page=4kb)
and there you go, i set minimum page size 60MB...if android memory usage goes below 60MB it will kill those foreground processes that actually using kernel resources . I think it saved almost 15% of my battery so far...can not say exactly...but still working on that if i can get better page size for our CM 7.1. May this concept can give better idea to you.

Any thoughts, Psyke83?

Thanks

It seems that on Android the current forefround application gets an oom_adj value of 0 and as soon it's not visible anymore it gets some higher value. I assume the concrete value is dependent by the processes' place in the LRU list.

[roofrider]

@psyke83
i'm on cm7 by tj_style, charged to 100% at night and morning only 95% n with use of 3 mins reduced to 90%
this is my dumpstate wen battery was around 88%..can u tel wats draining my battery wen it's idle in night??solution?
Tass_dumpstate.txt
You are not allowed to view links. Register or Login

also these are frm battery monitor widget:
           

[psyke83]

ADWLauncher doesn't help with disabling sensor.

I was playing around...found interesting....ActivityManagerService.java tracks the processes which is foreground, is running a service.. and its because a value is set in setting "oom_adj" of the process. This oom_adj give signal to android kernal to kill the process if it goes out of memory(oom). I found this kernel source in "lowmemorykiller.c" which is located in the kernel source tree under "drivers/misc/".

so i ran
# cat /sys/module/lowmemorykiller/parameters/minfree

and got output like this: 1536,2048,4096,5120,5632,6144  this numbers are pagesize.
I changed this page value in terms of MB. (for calculation 1 page=4kb)
and there you go, i set minimum page size 60MB...if android memory usage goes below 60MB it will kill those foreground processes that actually using kernel resources . I think it saved almost 15% of my battery so far...can not say exactly...but still working on that if i can get better page size for our CM 7.1. May this concept can give better idea to you.

Any thoughts, Psyke83?

Thanks

It seems that on Android the current forefround application gets an oom_adj value of 0 and as soon it's not visible anymore it gets some higher value. I assume the concrete value is dependent by the processes' place in the LRU list.

I have been using lowmemorykiller tweaks to reduce lag - however, the tweaks were not really needed if swap was activated, and would cause applications to get prematurely killed if swap was not active. Not a perfect solution by any means.

I've removed these tweaks again, since we now have swap (compcache) enabled by default. Try hotfix 2 and see if it has any improvement.

[psyke83]

@psyke83
i'm on cm7 by tj_style, charged to 100% at night and morning only 95% n with use of 3 mins reduced to 90%
this is my dumpstate wen battery was around 88%..can u tel wats draining my battery wen it's idle in night??solution?

I have a feeling that the problem is the Samsung RIL, which is why the galaxy5 and tass ports are draining battery. I can't really do much until I get my phone back... but I will look at all the logs given to me and try to see if it helps.