help me make heads or tails of these BetterBatteryStats - Galaxy S II Q&A, Help & Troubleshooting

i used BetterBatteryStats to try and see what was killing my battery. in an 8 hour night, i lose 20% battery.. not cool. thats over 2% an hour, with bluetooth off, and gps off, (i leave my wifi connected because ive been told wifi uses less battery than 3G). i turn my brightness all the way down, and call it a night. yet i still wake up so drained.. could someone a little more knowledgeable take a look at my log and see if they can make heads or tails of what are the big drainers here?
ill drop rep for anyone who can offer any input
===================
General Information
===================
BetterBatteryStats version: 1.4.2.0
Creation Date: 2011-12-14 12:19:44
Statistic Type: (0) Since Charged
Since 8 h 11 m 11 s
VERSION.RELEASE: 2.3.4
BRAND: samsung
DEVICE: GT-I9100
MANUFACTURER: samsung
MODEL: GT-I9100
===========
Other Usage
===========
Wifi On (): 8 h 11 m 11 s (29471 s) Ratio: 100.0%
Awake (): 1 h 34 m 14 s (5654 s) Ratio: 19.2%
Screen On (): 50 s (50 s) Ratio: 0.2%
=========
Wakelocks
=========
NetworkLocationLocator (com.google.android.apps.maps.Maps): 38 m 31 s (2311 s) Count:494 7.8%
AlarmManager (Android System): 5 m 10 s (310 s) Count:17937 1.1%
*sync* (com.google.android.apps.reader.Google Reader): 1 m 9 s (69 s) Count:16 0.2%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 31 s (31 s) Count:1962 0.1%
*network-location* (Google Services): 31 s (31 s) Count:169 0.1%
BWL (com.levelup.beautifulwidgets.Beautiful Widgets): 25 s (25 s) Count:8 0.1%
*network-location* (Android System): 25 s (25 s) Count:48 0.1%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 19 s (19 s) Count:1468 0.1%
FacebookService (com.facebook.katana.Facebook): 13 s (13 s) Count:8 0.0%
LocationReceiverService (com.google.android.apps.maps.Maps): 9 s (9 s) Count:2474 0.0%
LockerService (com.teslacoilsw.widgetlocker.WidgetLocker): 8 s (8 s) Count:2 0.0%
LocationReportingService (com.google.android.apps.maps.Maps): 8 s (8 s) Count:2988 0.0%
*sync* (com.google.android.gm.Gmail): 6 s (6 s) Count:1 0.0%
BackgroundFriendService (com.google.android.apps.maps.Maps): 5 s (5 s) Count:499 0.0%
Event Log Service (Google Services): 4 s (4 s) Count:17 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 4 s (4 s) Count:2978 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:133 0.0%
SyncManagerHandleSyncAlarm (Android System): 2 s (2 s) Count:105 0.0%
ActivityManager-Launch (Android System): 2 s (2 s) Count:37 0.0%
SMSDispatcher (Dialer): 2 s (2 s) Count:1 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 s (1 s) Count:2 0.0%
*backup* (Android System): 1 s (1 s) Count:679 0.0%
StartingAlertService (com.android.mms.Messaging): 1 s (1 s) Count:1 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 48 m 2 s (2882 s) Cntc/wc/ec)8681/0/0 9.7%
"sec-battery-monitor" (): 24 m 16 s (1456 s) Cntc/wc/ec)1580/1205/0 4.9%
"alarm" (): 23 m 21 s (1401 s) Cntc/wc/ec)23255/6/0 4.7%
"svnet" (): 20 m 39 s (1239 s) Cntc/wc/ec)1652/0/1652 4.2%
"wlan_rx_wake" (): 7 m 54 s (474 s) Cntc/wc/ec)676/0/676 1.6%
"wlan_wake" (): 7 m 7 s (427 s) Cntc/wc/ec)9321/358/0 1.4%
"alarm_rtc" (): 6 m 37 s (397 s) Cntc/wc/ec)628/0/48 1.3%
"power-supply" (): 58 s (58 s) Cntc/wc/ec)1581/0/0 0.2%
"radio-interface" (): 31 s (31 s) Cntc/wc/ec)43/0/0 0.1%
"AudioOutLock" (): 3 s (3 s) Cntc/wc/ec)15/0/0 0.0%
"vbus_present" (): 1 s (1 s) Cntc/wc/ec)1/0/1 0.0%
"event1-2655" (): (0 s) Cntc/wc/ec)5/1/0 0.0%
"sync_system" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"mmc_delayed_work" (): (0 s) Cntc/wc/ec)1852/0/1 0.0%
"sec-battery-cable" (): (0 s) Cntc/wc/ec)2/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)1125/0/0 0.0%
=========
Processes
=========
suspend (0): Sys: 3 m 14 s (194 s) Us: (0 s) Starts: 0
events/0 (0): Sys: 2 m 47 s (167 s) Us: (0 s) Starts: 0
*wakelock* (com.google.android.apps.maps.Maps): Sys: 1 m 8 s (68 s) Us: 5 s (5 s) Starts: 0
tvout resume wo (0): Sys: 16 s (16 s) Us: (0 s) Starts: 0
mmcqd (0): Sys: 3 s (3 s) Us: (0 s) Starts: 0
*wakelock* (com.google.android.apps.reader.Google Reader): Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.google.android.apps.reader (com.google.android.apps.reader.Google Reader): Sys: (0 s) Us: 1 s (1 s) Starts: 1
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
org.artsplanet.android.pesobatteryfull (org.artsplanet.android.pesobatteryfull.PesoWidgetProvider$WidgetService)
Active since: 36 s
Last activity: 36 s
Crash count:0
com.sec.android.fotaclient (com.sec.android.fotaclient.FOTAService)
Active since: 33 s
Last activity: 31 m 10 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 18 s
Last activity: 18 s
Crash count:0
system (com.android.internal.service.wallpaper.ImageWallpaper)
Active since: 17 s
Last activity: 17 s
Crash count:0
com.android.systemui (com.android.systemui.statusbar.StatusBarService)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.PushMessagingRegistrar)
Active since: 24 s
Last activity: 24 s
Crash count:0
ch.blinkenlights.battery (ch.blinkenlights.battery.BlinkenlightsBatteryService)
Active since: 30 s
Last activity: 31 m
Crash count:0
com.pandaroid.clockno1cute (com.pandaroid.clockno1cute.PandaClockService)
Active since: 31 s
Last activity: 1 h 36 m 30 s
Crash count:0
org.adw.launcher.notifications (org.adw.launcher.notifications.ADWService)
Active since: 30 s
Last activity: 1 h 8 m 51 s
Crash count:0
com.teslacoilsw.widgetlocker (com.teslacoilsw.widgetlocker.LockerService)
Active since: 29 s
Last activity: 1 h 36 m 31 s
Crash count:0
com.beansoft.keyboardplus (com.beansoft.keyboardplus.LatinIME)
Active since: 17 s
Last activity: 17 s
Crash count:0
com.smlds (com.smlds.smlStartService)
Active since: 24 s
Last activity: 1 h 1 m 15 s
Crash count:0
com.sec.android.providers.drm (com.sec.android.providers.drm.OmaDrmConfigService)
Active since: 25 s
Last activity: 1 h 2 m 2 s
Crash count:0
com.sec.android.app.FileTransferServer (com.sec.android.app.FileTransferServer.FTSService)
Active since: 2 h 36 m 56 s
Last activity: 31 m 57 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 24 s
Last activity: 1 m 11 s
Crash count:0
com.sec.android.app.FileTransferManager (com.sec.android.app.FileTransferManager.FTSRunningChecker)
Active since: 20 s
Last activity: 31 m 57 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.google.android.apps.maps:NetworkLocationService (com.google.android.location.internal.server.NetworkLocationService)
Active since: 29 s
Last activity: 1 h 35 m 20 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 15 s
Last activity: 20 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 20 s
Last activity: 1 m 28 s
Crash count:0
com.rhythm.hexise.task (com.rhythm.hexise.task.TaskService)
Active since: 30 s
Last activity: 30 s
Crash count:0
com.facebook.katana (com.facebook.katana.service.UploadManager)
Active since: 22 s
Last activity: 1 m 28 s
Crash count:0
Click to expand...
Click to collapse
[email protected]
ill drop rep for anyone who can offer any input

---

better off asking in the better battery stats thread arent you?

---

wow there is such a thing? lol yeah ill go try and find it

---

From your stats, I believe your latitude is on.
Go to Latitude, settings (or location reporting), click on sign out of latitude.
Second, just in case if you have a dlink router, turn wifi off.
Now let your phone sits for a couple of hours, everything should be improved.
Sent from my GT-I9100 using Tapatalk

---

not necessarily latitude, maps can do the same thing.
i had the same problem, and read a solution that i donwt yet know if works, but worth trying: freezing the network location with titanium backup.
---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------
dikai_yang said:
From your stats, I believe your latitude is on.
Go to Latitude, settings (or location reporting), click on sign out of latitude.
Second, just in case if you have a dlink router, turn wifi off.
Now let your phone sits for a couple of hours, everything should be improved.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
why specifically dlink?

---

Your gtalk, facebook etc are taking a toll on your battery

---

D-Link routers have problems with pinging the phone excessively draining the battery. I have the problem with this router and non others (at work, at friends, etc). I don't think a lot of people know about this. They simply accept the battery drain. Turning wifi off when not in use (through juicedefender not wifi sleep policy) is a workaround.
Unless maps is running, the network usage shouldn't stand out at the top unless latitude is signed in.
Facebook drain is unfortunate but normal. Even if notification is set to off, it still wakes the device periodically. Don't try to kill it because when it restarts itself it does a full sync causing a cpu spike.
There are several apps that uses a good amount of cpu even when idle. TVUPlayer, Polaris office, tapatalk, soundhound, goggles translate.
All these are results of a long period of testing on cpu usage and battery analysis.
With that said, not all wakelocks cause battery drain. A lot of people are obsessed with killing / freezing all apps they see as wakelocks in bbs. This is not necessary. Otherwise, don't run Facebook, ebay, skype, push email, then why get a sgs2? Battery monitor widget causes the most wakes in bbs yet it only uses a very small % of battery.
Sent from my GT-I9100 using Tapatalk

---

so helpful dang.. yeah I logged out of latitude.. I never use it anyways.. should I uninstall Polaris? do apps drain data even if they aren't being used? I mean I know some do.. but even Polaris? dang.. I wonder what other apps I have that use background data when I'm not using them.. is there any way to check?
Sent from my GT-I9100 using XDA App
edit: oh yeah, does having live Widgets (like my live clock panda, and panda battery widget, and other stuff that makes my homescreen super cute) hurt me? I mean anything noticeable?

---

ok well ty guys
Sent from my GT-I9100 using XDA App

---

The apps I mentioned above don't necessarily use data in background (in a noticeable amount anyway). What I meant is that after quitting the app (back key), it keeps consuming a fairly small amount of cpu constantly, indefinitely, and is unnecessary. TVU player isvthe worst. Try watching a show for 5 seconds, quit the app, you'll see in System Tuner that it keeps consuming about 5% of battery constantly.
Good workaround. Install System Tuner (requires root), and set it to kill the problematic programs on screen off (problematic programs only). If you kill system apps or Facebook, etc, they'll keep restarting themselves and everytime this happens, more cpu time is consumed.
Widgets (battery, weather, news, etc) don't "drain" your battery. But of course they do make your phone "consume" a bit more battery. With widgets that update, you will see a lot of Alarm Manager wake counts in BBS, which is fine. Battery widget for instance, it polls your battery stay every minute or so, so an internal clock timer will be active at all times. But a several-hour-long cpu usage analysis will show minimal battery usage.
In my experience for fixingbmy own battery drain perceived, biggest killer is wifi on dlink router, latitude, and a few badly written apps that consume cpu even after quitting. All other stuff are not really battery drainers. Bottom line is, the more apps you install, the more battery is used. But 8 hours standby time, there's definitely a battery drain. If you don't touch you phone, expect no more than 2% drop an hour to be normal. My drops about 1.5% every 2 hours after careful tweaking.
Sent from my GT-I9100 using Tapatalk