[imp>dom]

My S2 has been eating battery like never before. Can anyone spot the problem?


General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2013-05-16 07:35:17
Statistic Type: (3) Since Unplugged
Since 6 h 33 m 3 s
VERSION.RELEASE: 4.0.4
BRAND: Samsung
DEVICE: GT-I9100
MANUFACTURER: samsung
MODEL: GT-I9100
BOOTLOADER: unknown
FINGERPRINT: samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPQ:user/release-keys
HARDWARE: smdk4210
ID: IMM76I
TAGS: release-keys
USER: android-build
PRODUCT: GT-I9100
RADIO: I9100XXKG2
Rooted: true
===========
Other Usage
===========
No Data Connection (): 6 h 30 m 19 s (23419 s) Ratio: 99.3%
No or Unknown Signal (): 6 h 30 m 19 s (23419 s) Ratio: 99.3%
Deep Sleep (): 6 h 24 m 2 s (23042 s) Ratio: 97.6%
Awake (): 9 m 1 s (541 s) Ratio: 2.3%
Screen On (): 4 m 21 s (261 s) Ratio: 1.1%
Good Signal (): 1 m 31 s (91 s) Ratio: 0.4%
Phone On (): 30 s (30 s) Ratio: 0.1%
Wifi On (): 10 s (10 s) Ratio: 0.0%
Wifi Running (): 9 s (9 s) Ratio: 0.0%
=========
Wakelocks
=========
AlarmManager (Android System): 2 m 47 s (167 s) Count:138 0.7%
ConnectivityService (Android System): 56 s (56 s) Count:139 0.2%
GSM (Phone): 28 s (28 s) Count:1 0.1%
AudioOut_1 (1013): 22 s (22 s) Count:5 0.1%
ActivityManager-Launch (Android System): 6 s (6 s) Count:63 0.0%
NetworkStats (Android System): 3 s (3 s) Count:44 0.0%
com.bellshare.util.WakefulIntentService (com.bellshare.beweatherfree.BeWeather): 3 s (3 s) Count:9 0.0%
Event Log Service (Google Services): 3 s (3 s) Count:14 0.0%
RILJ (Phone): 3 s (3 s) Count:41 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservi ce.AndroidEndpoint (Google Services): 2 s (2 s) Count:38 0.0%
StartingPopupUtilsService (UID): 1 s (1 s) Count:2 0.0%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 1 s (1 s) Count:1 0.0%
show keyguard (Android System): 1 s (1 s) Count:3 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 3 m 34 s (214 s) Cntc/wc/ec)126/0/0 0.9%
"event1-2042" (): 22 s (22 s) Cntc/wc/ec)41/1/0 0.1%
"alarm" (): 21 s (21 s) Cntc/wc/ec)79/0/0 0.1%
"event0-2042" (): 21 s (21 s) Cntc/wc/ec)39/0/0 0.1%
"event2-2042" (): 21 s (21 s) Cntc/wc/ec)524/0/0 0.1%
"sec-battery-monitor" (): 21 s (21 s) Cntc/wc/ec)46/37/0 0.1%
"event3-2042" (): 21 s (21 s) Cntc/wc/ec)40/0/0 0.1%
"alarm_rtc" (): 20 s (20 s) Cntc/wc/ec)36/0/12 0.1%
"radio-interface" (): 15 s (15 s) Cntc/wc/ec)34/0/0 0.1%
"event7-2042" (): 11 s (11 s) Cntc/wc/ec)82/0/0 0.0%
"l2_hsic" (): 8 s (8 s) Cntc/wc/ec)99/0/0 0.0%
"umts_ipc0" (): 8 s (8 s) Cntc/wc/ec)36/0/36 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)613/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)182/0/0 0.0%
"rpm_hsic" (): (0 s) Cntc/wc/ec)59/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)22/0/0 -0.0%
"mmc1_detect" (): (0 s) Cntc/wc/ec)44/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)44/0/0 0.0%
======================
Alarms (requires root)
======================
android (): Wakeups: 29
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 45, Intent: android.intent.action.TIME_TICK
Alarms: 14, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 27, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 28, Intent: android.appwidget.action.APPWIDGET_UPDATE
Alarms: 1, Intent: android.content.syncmanager.SYNC_ALARM

com.google.android.gsf (): Wakeups: 16
Alarms: 2, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 0, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 1, Intent: com.google.android.intent.action.SEND_IDLE

com.google.android.apps.maps (): Wakeups: 5

com.android.vending (): Wakeups: 5

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

com.google.android.gms (): Wakeups: 1
Alarms: 0, Intent: com.google.android.gms.recovery.WAKEUP
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINT ENANCE

[Eclypz]

I never liked using BBS to troubleshoot battery drain. BBS seems to focus on time used/wake locks, rather than actual power usage. For example, 5min of gaming will use way more battery than 30min of facebook

The only thing that stood out for me is this:
No Data Connection (): 6 h 30 m 19 s (23419 s) Ratio: 99.3%
No or Unknown Signal (): 6 h 30 m 19 s (23419 s) Ratio: 99.3%

Are you in airplane mode or something? Or do you just have really poor coverage in your area? If you have really poor coverage, the phone will pump more power into the radios to keep your connection alive/stable.

Have you tried using GSam?
https://play.google.com/store/apps/details?id=com.gsamlabs.bbm&feature=nav_result#?t=W251bGwsMSwyLDNd

I find their graphical interface way easier to read

[imp>dom]

No I wasn't in airplane mode. Coverage is never a problem. I have actually used manual network as I heard it will save battery that way other than having the phone to search for network all the time.

Will try GSam

[imp>dom]

The only thing that stood out for me is this:
No Data Connection (): 6 h 30 m 19 s (23419 s) Ratio: 99.3%
No or Unknown Signal (): 6 h 30 m 19 s (23419 s) Ratio: 99.3%



What else could have caused this?

[Eclypz]

Before pointing your fingers at that, you should see what GSam is reporting first.

Are you on stock? or did you flash kernels, radios and ROMs?

[imp>dom]

GSam seems to display a lot of info. What is the best place to look at?

[imp>dom]

I've just done a 2 hr test (after a full charge). Phone Radio was up for the whole time 2 hours and used 40% power. Signal strength was 100%. App usage used 35%. Overall I lost 5% of power and 98% of the time phone was in Deep Sleep

[!MiKrofT]

5% battery drop over 2 hours is pretty good...

[imp>dom]

It used to eat only 2% overnight. That was before I installed wechat and some other apps that might keep updating themselves like weather apps. And I don't think I had No Data Connection or No or Unknown Signal before

[Eclypz]

When you open the GSam app, you're presented with the summary screen. This screen gives you the overall usage broken down into a few categories:
Phone (this is your voice calls)
Screen (this is from your screen being on)
Phone Radio (this is your cell radio. Low signal strength would cause this to use more power, as will having a data connection)
Wifi Active (power used by your wifi)
Held Awake (this is your total wake lock from apps or processes. Wake locks are when your phone is prevented from going to sleep. Simple things like receiving an email or instant message will wake your phone from sleep)
Bluetooth
Apps Usage (total used by apps and processes)

I would assume the Phone radio category would be BBS's equivalent of this:
No Data Connection (): 6 h 30 m 19 s (23419 s) Ratio: 99.3%
No or Unknown Signal (): 6 h 30 m 19 s (23419 s) Ratio: 99.3%

If this is true, you should see high % of battery use in "Phone Radio"


Press the Apps Usage category from the summary screen to view the usage by each individual app.

You can also go into the details of each app to view the usage by that app. Anything over 10% is probably worth looking at.

Looking at these things should give you a pretty good idea where majority of your battery usage is going. I can't tell you what's normal and what's not, as everybody's usage varies, but, at least you'll know where your battery is going.

Hope that helps