[Q] Help me figure out why my battery is so bad

[lourivellini]

Battery life started off OK with this rom, now its just awful. After 8 hours today, im now at 16%. I have cpuspy installed, and betterbatterystats as well, but i dont know how to interpret them (wake-locks and such).

Rom is shostock v1.9.4
stock kernel

Barely used the phone at all today

let me know if any additional information is needed.

Here are screen shots that might be relevant:

Heres my betterbatterystats dump:
===================
General Information
===================
BetterBatteryStats version: 1.7.1.0
Creation Date: 2012-04-12 15:07:10
Statistic Type: (3)
Since 8 h 12 m
VERSION.RELEASE: 2.3.6
BRAND: samsung
DEVICE: SGH-I777
MANUFACTURER: samsung
MODEL: SAMSUNG-SGH-I777
RADIO: unknown
BOOTLOADER: unknown
FINGERPRINT: samsung/SGH-I777/SGH-I777:2.3.6/GINGERBREAD/UCKK6:user/release-keys
HARDWARE: smdkc210
ID: GINGERBREAD
Rooted: true
===========
Other Usage
===========
Wifi On (): 8 h 12 m (29520 s) Ratio: 100.0%
Wifi Running (): 8 h 12 m (29520 s) Ratio: 100.0%
Awake (): 6 h 30 m 58 s (23458 s) Ratio: 79.5%
Screen On (): 35 m 41 s (2141 s) Ratio: 7.3%
Phone On (): 2 m 15 s (135 s) Ratio: 0.5%
=========
Wakelocks
=========
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 8 m 52 s (532 s) Count:69 1.8%
RILJ (Dialer): 2 m 59 s (179 s) Count:1351 0.6%
*sync* (com.google.android.gm.Gmail): 2 m 9 s (129 s) Count:20 0.4%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 1 m 59 s (119 s) Count:74 0.4%
ActivityManager-Launch (Android System): 1 m 16 s (76 s) Count:247 0.3%
AlarmManager (Android System): 60 s (60 s) Count:3193 0.2%
GTALK_ASYNC_CONN (Google Services): 59 s (59 s) Count:49 0.2%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 43 s (43 s) Count:16 0.1%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 40 s (40 s) Count:73 0.1%
*sync* (com.cooliris.media.Gallery): 38 s (38 s) Count:6 0.1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 38 s (38 s) Count:41 0.1%
GSM (Dialer): 35 s (35 s) Count:22 0.1%
FacebookService (com.facebook.katana.Facebook): 34 s (34 s) Count:9 0.1%
com.dropbox.android.taskqueue.CameraUploadTask (com.dropbox.android.Dropbox): 33 s (33 s) Count:5 0.1%
*sync* (com.twitter.android.Twitter): 28 s (28 s) Count:8 0.1%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 25 s (25 s) Count:5 0.1%
SMSDispatcher (Dialer): 18 s (18 s) Count:6 0.1%
NetworkLocationLocator (Google Services): 16 s (16 s) Count:16 0.1%
GpsLocationProvider (Android System): 16 s (16 s) Count:337 0.1%
sleep_broadcast (Android System): 16 s (16 s) Count:526 0.1%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 15 s (15 s) Count:13 0.1%
Event Log Service (Google Services): 13 s (13 s) Count:131 0.0%
GTALK_CONN (Google Services): 12 s (12 s) Count:483 0.0%
show keyguard (Android System): 10 s (10 s) Count:50 0.0%
keyguardWakeAndHandOff (Android System): 7 s (7 s) Count:2498 0.0%
Checkin Service (Google Services): 4 s (4 s) Count:580 0.0%
StartingAlertService (com.android.mms.Messaging): 4 s (4 s) Count:11 0.0%
SyncManagerHandleSyncAlarm (Android System): 2 s (2 s) Count:400 0.0%
*sync* (ch.teamtasks.tasks.paid.Tasks): 2 s (2 s) Count:1 0.0%
ActivityManager-Sleep (Android System): 2 s (2 s) Count:3257 0.0%
WifiService (Android System): 2 s (2 s) Count:2433 0.0%
DownloadManager (Media): 1 s (1 s) Count:1 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:538 0.0%
com.google.android.music.MusicPlaybackService.mAsyncWakeLock (com.google.android.music.Google Play Music): 1 s (1 s) Count:6 0.0%
GOOGLE_C2DM (Google Services): 1 s (1 s) Count:115 0.0%
NfcService (com.android.nfc3.Nfc Service): 1 s (1 s) Count:60 0.0%
================
Kernel Wakelocks
================
"wlan_wake" (): 2 h 50 m 16 s (10216 s) Cntc/wc/ec)79022/3620/0 34.6%
"sec-battery-monitor" (): 2 h 37 m 47 s (9467 s) Cntc/wc/ec)7909/4194/0 32.1%
"wlan_rx_wake" (): 2 h 13 m 11 s (7991 s) Cntc/wc/ec)12848/0/12847 27.1%
"svnet" (): 1 h 19 m 53 s (4793 s) Cntc/wc/ec)8339/0/8340 16.2%
"AudioOutLock" (): 13 m 52 s (832 s) Cntc/wc/ec)50/0/0 2.8%
"gps-lock" (): 10 m 51 s (651 s) Cntc/wc/ec)7/0/0 2.2%
"[P]_NetworkLocationPassiveCollector" (): 9 m 11 s (551 s) Cntc/wc/ec)24/0/0 1.9%
"radio-interface" (): 9 m 4 s (544 s) Cntc/wc/ec)647/0/0 1.8%
"[P]_RILJ" (): 2 m 46 s (166 s) Cntc/wc/ec)1368/0/0 0.6%
"alarm_rtc" (): 2 m 36 s (156 s) Cntc/wc/ec)199/0/88 0.5%
"alarm" (): 2 m 34 s (154 s) Cntc/wc/ec)754/0/0 0.5%
"[P]_*sync*" (): 2 m 15 s (135 s) Cntc/wc/ec)35/0/0 0.5%
"[P]_NetworkLocationActiveCollector" (): 2 m (120 s) Cntc/wc/ec)1/0/0 0.4%
"svnet-dormancy" (): 1 m 52 s (112 s) Cntc/wc/ec)25/0/25 0.4%
"power-supply" (): 1 m 40 s (100 s) Cntc/wc/ec)7881/0/0 -0.0%
"[P]_AlarmManager" (): 58 s (58 s) Cntc/wc/ec)706/0/0 0.2%
"[P]_SignalCollector.ScannerThread" (): 40 s (40 s) Cntc/wc/ec)4/0/0 0.1%
"[P]_AlarmReceiver" (): 40 s (40 s) Cntc/wc/ec)16/0/0 0.1%
"[P]_FacebookService" (): 33 s (33 s) Cntc/wc/ec)9/0/0 0.1%
"[P]_GTALK_ASYNC_CONN" (): 31 s (31 s) Cntc/wc/ec)33/0/0 0.1%
"[P]_NetworkLocationLocator" (): 27 s (27 s) Cntc/wc/ec)21/0/0 0.1%
"event1-2796" (): 25 s (25 s) Cntc/wc/ec)204/13/0 0.1%
"[P]_GmailProviderProviderChangedBroadcastWakeLock" (): 22 s (22 s) Cntc/wc/ec)21/0/0 0.1%
"[P]_GTALK_CONN" (): 12 s (12 s) Cntc/wc/ec)302/0/0 0.0%
"[P]_GpsLocationProvider" (): 12 s (12 s) Cntc/wc/ec)96/0/0 0.0%
"[P]_GSM" (): 11 s (11 s) Cntc/wc/ec)2/0/0 0.0%
"[P]_ActivityManager-Launch" (): 8 s (8 s) Cntc/wc/ec)178/0/0 0.0%
"sec_jack_det" (): 8 s (8 s) Cntc/wc/ec)4/1/4 0.0%
"prx_wake_lock" (): 5 s (5 s) Cntc/wc/ec)3/0/3 0.0%
"[P]_com.google.android.apps.googlevoice.UpdateService" (): 5 s (5 s) Cntc/wc/ec)12/0/0 0.0%
"mmc_delayed_work" (): 3 s (3 s) Cntc/wc/ec)8661/0/0 0.0%
"[P]_WifiService" (): 2 s (2 s) Cntc/wc/ec)7669/0/0 0.0%
"[P]_SMSDispatcher" (): 2 s (2 s) Cntc/wc/ec)5/0/0 0.0%
"vbus_present" (): 2 s (2 s) Cntc/wc/ec)0/0/1 0.0%
"[P]_SyncManagerHandleSyncAlarm" (): 2 s (2 s) Cntc/wc/ec)63/0/0 0.0%
"[P]_StartingAlertService" (): 1 s (1 s) Cntc/wc/ec)11/0/0 0.0%
"[P]_ActivityManager-Sleep" (): 1 s (1 s) Cntc/wc/ec)64/0/0 0.0%
"[P]_GOOGLE_C2DM" (): 1 s (1 s) Cntc/wc/ec)80/0/0 0.0%
"event4-2796" (): 1 s (1 s) Cntc/wc/ec)6/1/0 0.0%
"[P]_NetworkLocationCallbackRunner" (): (0 s) Cntc/wc/ec)43/0/0 0.0%
"[P]_ServiceStateTracker" (): (0 s) Cntc/wc/ec)14/0/0 0.0%
"[P]_com.google.android.music.MusicPlaybackService.mAsyncWakeLock" (): (0 s) Cntc/wc/ec)6/0/0 0.0%
"[P]_PhoneApp" (): (0 s) Cntc/wc/ec)1/0/0 0.0%
"[P]_sleep_broadcast" (): (0 s) Cntc/wc/ec)126/0/0 0.0%
"event7-2796" (): (0 s) Cntc/wc/ec)9843/0/0 0.0%
"[P]_NfcService" (): (0 s) Cntc/wc/ec)63/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)18256/0/0 0.0%
"[P]_keyguardWakeAndHandOff" (): (0 s) Cntc/wc/ec)56/0/0 0.0%
"[P]_HeadsetObserver" (): (0 s) Cntc/wc/ec)4/0/0 0.0%
"[P]_com.google.android.music.MediaButtonIntentReceiver" (): (0 s) Cntc/wc/ec)2/0/0 0.0%
"[P]_AsyncCollectorListener" (): (0 s) Cntc/wc/ec)4/0/0 0.0%
"[P]_LocationManagerService" (): (0 s) Cntc/wc/ec)57/0/0 0.0%
"[P]_com.google.android.music.AsyncMediaPlayer" (): (0 s) Cntc/wc/ec)4/0/0 0.0%
"ApmCommandThread" (): (0 s) Cntc/wc/ec)161/0/0 0.0%
======================
Alarms (requires root)
======================
android (): Wakeups: 69
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 470, Intent: android.intent.action.TIME_TICK
Alarms: 5, Intent: android.intent.action.DEVICE_LOCKSCREEN_ACTION
Alarms: 49, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 1, Intent: android.appwidget.action.APPWIDGET_UPDATE
Alarms: 63, Intent: android.content.syncmanager.SYNC_ALARM

com.google.android.gsf (): Wakeups: 43
Alarms: 10, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 17, Intent: com.google.android.intent.action.GTALK_HEARTBEAT

com.google.android.apps.maps (): Wakeups: 47
Alarms: 3, Intent: com.google.android.location.ALARM_WAKEUP_ACTIVE_COLLECTOR
Alarms: 8, Intent: com.google.android.location.ALARM_WAKEUP_S_COLLECTOR
Alarms: 0, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.9
Alarms: 5, Intent: com.google.android.location.ALARM_WAKEUP_LOCATOR
Alarms: 1, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.5
Alarms: 1, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.7
Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_CACHE_UPDATER
Alarms: 4, Intent: com.google.android.location.ALARM_WAKEUP_PASSIVE_COLLECTOR
Alarms: 1, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.1
Alarms: 1, Intent: com.google.android.location.ALARM_WAKEUP_BURST_COLLECTOR
Alarms: 1, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.3
Alarms: 6, Intent: com.google.android.location.ALARM_WAKEUP_SENSOR_UPLOADER
Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_CALIBRATION_COLLECTOR

com.google.android.location (): Wakeups: 10
Alarms: 10, Intent: com.google.android.location.ALARM_WAKEUP_LOCATOR

com.facebook.katana (): Wakeups: 9
Alarms: 0, Intent: com.facebook.katana.service.19
Alarms: 1, Intent: com.facebook.katana.service.43
Alarms: 1, Intent: com.facebook.katana.service.41
Alarms: 0, Intent: com.facebook.katana.service.25
Alarms: 0, Intent: com.facebook.katana.service.11
Alarms: 0, Intent: com.facebook.katana.service.23
Alarms: 0, Intent: com.facebook.katana.service.13
Alarms: 0, Intent: com.facebook.katana.service.29
Alarms: 0, Intent: com.facebook.katana.service.15
Alarms: 0, Intent: com.facebook.katana.service.27
Alarms: 0, Intent: com.facebook.katana.service.17
Alarms: 0, Intent: com.facebook.katana.service.10
Alarms: 0, Intent: com.facebook.katana.service.31
Alarms: 0, Intent: com.facebook.katana.service.4
Alarms: 0, Intent: com.facebook.katana.service.21
Alarms: 0, Intent: com.facebook.katana.service.6
Alarms: 1, Intent: com.facebook.katana.service.35
Alarms: 1, Intent: com.facebook.katana.service.45
Alarms: 1, Intent: com.facebook.katana.service.33
Alarms: 1, Intent: com.facebook.katana.service.47
Alarms: 1, Intent: com.facebook.katana.service.39
Alarms: 1, Intent: com.facebook.katana.service.49
Alarms: 1, Intent: com.facebook.katana.service.37

com.levelup.beautifulwidgets (): Wakeups: 8
Alarms: 8, Intent: com.levelup.beautifulwidgets.ACTION_UPDATEWEATHER
Alarms: 2302, Intent: com.levelup.beautifulwidgets.ACTION_UPDATECLOCK

com.sec.android.app.clockpackage (): Wakeups: 2
Alarms: 2, Intent: com.samsung.sec.android.clockpackage.alarm.ALARM_ALERT

com.android.phone (): Wakeups: 3
Alarms: 3, Intent: com.android.internal.telephony.gprs-reconnect

com.twitter.android (): Wakeups: 3
Alarms: 3, Intent: com.twitter.android.poll.alarm

com.android.vending (): Wakeups: 2

com.geeksoft.screenshot (): Wakeups: 1

 

[mattdm]

The problem is with the firmware base. ShoStock is based on UCKK6, which has a notorious wifi wakelock bug. I would suggest moving to a different ROM.

 

[lourivellini]

which do you recommend? I was on CM7, but was having some problems, so i decided to go to a stock-ish experience (why i choose shostock).

At this point id be fine with just flashing back to stock (if that is the most stable and bug-less method), as long as i can root and remove some ATT bloat.

Not saying im opposed to any other rom, but im just at a point where im done tweaking and trying out different roms for this reason. I just want something that works.

 

[trell959]

which do you recommend? I was on CM7, but was having some problems, so i decided to go to a stock-ish experience (why i choose shostock).

At this point id be fine with just flashing back to stock (if that is the most stable and bug-less method), as long as i can root and remove some ATT bloat.

Not saying im opposed to any other rom, but im just at a point where im done tweaking and trying out different roms for this reason. I just want something that works.

Right now I'm going about 13 hours with 40% left. This is on cm9 with siyah's kernel.

Sent from my SGH-I777 using xda premium

 

[mattdm]

which do you recommend? I was on CM7, but was having some problems, so i decided to go to a stock-ish experience (why i choose shostock).

At this point id be fine with just flashing back to stock (if that is the most stable and bug-less method), as long as i can root and remove some ATT bloat.

Not saying im opposed to any other rom, but im just at a point where im done tweaking and trying out different roms for this reason. I just want something that works.

I'm a big fan of UnOriginal, because it's based on UCKH7, and it gives me awesome battery life(it's heavily debloated).

For you, though, you might want to just go back to stock UCKH7 using this method. That'll get you a completely stock, and relatively bugless, experience.

 

[gsrrr]

Most stable (for me) was UnNamed 2.2.1. I'd go with that if you want Gingerbread. If you want to try out ICS, flash a few of them and see what you like. I like SHOStock2 myself.

 

[votinh]

Kernel Wakelocks
================
"wlan_wake" (): 2 h 50 m 16 s (10216 s) Cntc/wc/ec)79022/3620/0 34.6%
"sec-battery-monitor" (): 2 h 37 m 47 s (9467 s) Cntc/wc/ec)7909/4194/0 32.1%
"wlan_rx_wake" (): 2 h 13 m 11 s (7991 s) Cntc/wc/ec)12848/0/12847 27.1%
"svnet" (): 1 h 19 m 53 s (4793 s) Cntc/wc/ec)8339/0/8340 16.2%
"AudioOutLock" (): 13 m 52 s (832 s) Cntc/wc/ec)50/0/0 2.8%
.
.
.

What is it? The BBS itself?

 

[lourivellini]

What is it? The BBS itself?

no idea, whats bbs?

btw normal drain has temporarily been restored. I charged it to 50 a few hours ago, and im only at like 43% with moderate usage -__-

 

[votinh]

BBS = BetterBatteryStat

 

[inspectagadget]

The problem is with the firmware base. ShoStock is based on UCKK6, which has a notorious wifi wakelock bug. I would suggest moving to a different ROM.

Update to SHOstock v3.1.

 

[lourivellini]

Haven't changed roms yet, will do it pretty soon, but i really wanted to figure out what exactly is eating up my battery.

I have bbs and cpuspy installed, but i have no idea how to interpret them, can someone help with this?

I feel like this happens to me with every phone i own, regardless of what i have installed.

 

[alacrify]

Facebook can be bad.
NFC was a HUGE battery drain on mine.

I really like Task's AOKP ROM...

 

[lourivellini]

Facebook can be bad.
NFC was a HUGE battery drain on mine.

I really like Task's AOKP ROM...

facebook isnt the problem, i installed it only after relazing my battery sucks, and it wouldnt make a difference either way.

The point of the thread was to actually make sense of what bbs spits out, as of right now i have no clue what that crap means, and thoeries of why my battery sucks are just pure speculation.

Switching roms may or may not help me, but i at least want to know WHY...

 

[blackplague1347]

I was getting quite good battery life with CM9. I had to switch to AOKP though, because for some reason CM9 wouldn't see a lot of the files on my internal sd card (meaning, they would not show up in any file browser - directories would show as empty). Today is my first full day on AOKP with no bugs to speak of. So far I'm at 88% battery, after 5 hours and 20 minutes, with the screen on for 30 minutes.

Browser, AudioOut_1, and FacebookService are my top 3 partial wakelocks in BBS. CPU Spy tells me my phone is usualy at 200 MHz or in Deep Sleep (94% of the time, combined).

Maybe give AOKP a try? Also, SHOStock2 was pretty good in terms of battery and performance the last time I used it.

As for your terrible battery life, it's probably wifi. I'm not the most technical user, so whenever I was on a ROM where I wanted to figure out of wifi was a killer, I'd just turn it on and off every couple of hours and then look at the battery graph/chart. If it's dropping more quickly... well, you get the idea.

 

[skatcat31]

Your drain is from the wifi not sleeping. Use wifi only when you need to, it uses MUCH more power than 2/3/4g. What's happening is that your wifi isn't entering sleep mode, so while your phone is sleeping, your wifi is still pumping out huge amounts of data. Literally your entire drain problem. Uckk6 had a bug that prevented wifi from sleeping if it got de bloated. Sadly stock kk6 which came out as an ota stone time ago, didn't have this bug. Since then it's been fixed in some roms. To fix this issue a newer ROM is required. Either that our very sparing wifi use. If you turn wifi off when you are not using it, your battery life should jump to fifteen hours early, if not more.

Sent from my SGH-I777 using xda premium

 

[alacrify]

facebook isnt the problem, i installed it only after relazing my battery sucks, and it wouldnt make a difference either way.

The point of the thread was to actually make sense of what bbs spits out, as of right now i have no clue what that crap means, and thoeries of why my battery sucks are just pure speculation.

Switching roms may or may not help me, but i at least want to know WHY...

There's a nice long thread called "Known identified battery drainers" that will give you info on Wireshark, BBS, drainers, and other information. http://forum.xda-developers.com/showthread.php?t=1308030.

 

[lourivellini]

Your drain is from the wifi not sleeping. Use wifi only when you need to, it uses MUCH more power than 2/3/4g. What's happening is that your wifi isn't entering sleep mode, so while your phone is sleeping, your wifi is still pumping out huge amounts of data. Literally your entire drain problem. Uckk6 had a bug that prevented wifi from sleeping if it got de bloated. Sadly stock kk6 which came out as an ota stone time ago, didn't have this bug. Since then it's been fixed in some roms. To fix this issue a newer ROM is required. Either that our very sparing wifi use. If you turn wifi off when you are not using it, your battery life should jump to fifteen hours early, if not more.

Sent from my SGH-I777 using xda premium

Its for sure not the wifi. I switched over to AOKP, and my battery life is still terrible. I've had this happen on multiple phones, multiple roms, etc. I only install needed apps. Even had a thread going through exactly what i did to my phone. right now im at 66% after 6 hours, pretty awful, especially compared to what i used to get.

There's a nice long thread called "Known identified battery drainers" that will give you info on Wireshark, BBS, drainers, and other information. http://forum.xda-developers.com/showthread.php?t=1308030.

Nothing in there was the problem with my phone.

Im honestly at my wits end with this phone, and android altogether. I dont even see what the point of installing bbs and cpuspy is if you cant really see anything from its results. Honestly, the only thing people say is its probably this and probably that, but nothing i have shows that.

If i wifi was really the problem, then wouldnt disabling it solve everything? If the ip5 is decent, and has a bigger screen, im probably going to bail on android unless i can get these issues figured out.

 

[Winklie]

FWIW, Wifi is a battery killer, I had the worst habit of leaving it on and my battery surely paid for it. I found this app https://play.google.com/store/apps/details?id=com.diordsoft.wifiauto&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5kaW9yZHNvZnQud2lmaWF1dG8iXQ.. that will turn it on only when connected to a charger. If I am somewhere that has a hotspot, I use a toggle for it, if I need to download something.

I get about 2 days out of a full battery charge (light use), using the NEAK Kernel (and it was about the same with Siyah RC5).

Wink

 

[Plasmamuffins]

3G/4G > Wifi in terms of battery consumption.

However, if the signal is weak, your wifi radio will struggle to maintain the connection. Thus draining more battery.

Sent from my SGH-I777

 

[ejosh1]

This may sound silly

My daughters captivate had a similar problem and it was pissing me off, finally somebody told me to check the battery by spinning it, if it spins at all its bad well it was only 6 months old and it spun alomost 3x my sgs2 battery didnt spin at all and has been fine.