I noticed my abttery life was getting bad and in the battery use details I saw the a lot of wake time when the screen is off. So got Betterbatterystats and tried to locate the app causing the partial wakelocks. Here is the history of wakelocks:
Wakelocks
=========
*backup* (Android System): 49 m 23 s (2963 s) Count:112 25.2%
AlarmManager (Android System): 41 s (41 s) Count:784 0.4%
*wifi* (Android System): 39 s (39 s) Count:88 0.3%
ActivityManager-Launch (Android System): 16 s (16 s) Count:46 0.1%
LockerService (com.teslacoilsw.widgetlocker.WidgetLocker): 15 s (15 s) Count:8 0.1%
*sync* (com.google.android.gm.Gmail): 9 s (9 s) Count:5 0.1%
FacebookService (com.facebook.katana.Facebook): 7 s (7 s) Count:5 0.1%
sleep_broadcast (Android System): 5 s (5 s) Count:76 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 5 s (5 s) Count:10 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 4 s (4 s) Count:5 0.0%
BackgroundFriendService (com.google.android.apps.maps.Maps): 4 s (4 s) Count:7 0.0%
GTALK_CONN (Google Services): 3 s (3 s) Count:68 0.0%
NotificationService (Android System): 3 s (3 s) Count:114 0.0%
SMSDispatcher (Dialer): 2 s (2 s) Count:1 0.0%
show keyguard (Android System): 2 s (2 s) Count:8 0.0%
com.bellshare.util.WakefulIntentService (com.bellshare.beweather.BeWeather Pro): 1 s (1 s) Count:1 0.0%
LocationReportingService (com.google.android.apps.maps.Maps): 1 s (1 s) Count:28 0.0%
NetworkLocationCacheUpdater (com.google.android.apps.maps.Maps): 1 s (1 s) Count:14 0.0%
*network-location* (com.bellshare.beweather.BeWeather Pro): 1 s (1 s) Count:3 0.0%
Checkin Service (Google Services): 1 s (1 s) Count:77 0.0%
*vibrator* (Android System): 1 s (1 s) Count:106 0.0%
Seems to be the backup is causing the problem. I thought it might have to do with whats syncing, so I disabled everything that syncs except my gmail and calendar, but the problem still persists. Anyone have any idea what could be causing the problem?
sherpajosh said:
I noticed my abttery life was getting bad and in the battery use details I saw the a lot of wake time when the screen is off. So got Betterbatterystats and tried to locate the app causing the partial wakelocks. Here is the history of wakelocks:
Wakelocks
=========
*backup* (Android System): 49 m 23 s (2963 s) Count:112 25.2%
AlarmManager (Android System): 41 s (41 s) Count:784 0.4%
*wifi* (Android System): 39 s (39 s) Count:88 0.3%
ActivityManager-Launch (Android System): 16 s (16 s) Count:46 0.1%
LockerService (com.teslacoilsw.widgetlocker.WidgetLocker): 15 s (15 s) Count:8 0.1%
*sync* (com.google.android.gm.Gmail): 9 s (9 s) Count:5 0.1%
FacebookService (com.facebook.katana.Facebook): 7 s (7 s) Count:5 0.1%
sleep_broadcast (Android System): 5 s (5 s) Count:76 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 5 s (5 s) Count:10 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 4 s (4 s) Count:5 0.0%
BackgroundFriendService (com.google.android.apps.maps.Maps): 4 s (4 s) Count:7 0.0%
GTALK_CONN (Google Services): 3 s (3 s) Count:68 0.0%
NotificationService (Android System): 3 s (3 s) Count:114 0.0%
SMSDispatcher (Dialer): 2 s (2 s) Count:1 0.0%
show keyguard (Android System): 2 s (2 s) Count:8 0.0%
com.bellshare.util.WakefulIntentService (com.bellshare.beweather.BeWeather Pro): 1 s (1 s) Count:1 0.0%
LocationReportingService (com.google.android.apps.maps.Maps): 1 s (1 s) Count:28 0.0%
NetworkLocationCacheUpdater (com.google.android.apps.maps.Maps): 1 s (1 s) Count:14 0.0%
*network-location* (com.bellshare.beweather.BeWeather Pro): 1 s (1 s) Count:3 0.0%
Checkin Service (Google Services): 1 s (1 s) Count:77 0.0%
*vibrator* (Android System): 1 s (1 s) Count:106 0.0%
Seems to be the backup is causing the problem. I thought it might have to do with whats syncing, so I disabled everything that syncs except my gmail and calendar, but the problem still persists. Anyone have any idea what could be causing the problem?
Click to expand...
Click to collapse
Uncheck Google backup transport in settings, privacy. That's the one consuming more battery
Related
I'm having problems with my sgs 2 battery life.. I recently installed litening rom and did a battery calibration and usually my phone lasts for atleast a day and a half, but suddenly my battery began to have a short life, causing it to end after about 9 hours.. any ideas to why?
Thank you!
Post up your battery usage screenshot, and download betterbatterystats for wakelocks, sounds as though you have wakelocks without logs we can't tell.
Sent from my GT-I9100 using Tapatalk
i have battery monitor, last night it lasted about 15 hours because i put it in battery saving mode (phone runs really slow and brightness up to 0).
how do i take photos? when i know i'll be more then happy to post
thanks!
clashed said:
i have battery monitor, last night it lasted about 15 hours because i put it in battery saving mode (phone runs really slow and brightness up to 0).
how do i take photos? when i know i'll be more then happy to post
thanks!
Click to expand...
Click to collapse
To take screenshots just push simultaneously the Power and Home button.
You will find the screenshots on your internal sd card in ScreenCaptures folder.
wakelocs log is very very long.. which part should I post?
clashed said:
wakelocs log is very very long.. which part should I post?
Click to expand...
Click to collapse
Go to pastebin website paste into that and post link.
Sent from my GT-I9100 using Tapatalk
I know I'm really problematic, but how can i copy and paste wakelocs log, i can't copy the text i can see it in pictures.
if that's the case which part of to log should i upload, or should i upload all of it?
clashed said:
I know I'm really problematic, but how can i copy and paste wakelocs log, i can't copy the text i can see it in pictures.
if that's the case which part of to log should i upload, or should i upload all of it?
Click to expand...
Click to collapse
Within app, press the menu button, select actions then Dump to File. It'll create a log file on the sdcard, copy and paste into pastebin or upload the log file.
I found 2 files after I did the file to dump, 1 is battery history.txt: http://www.mediafire.com/?71aqcz2kzl3xeh1
and the other is BetterBatteryStats.txt:
http://www.mediafire.com/?0m6ilysr06ucey5
Many thanks for helping! your help is much appreciated!
*network-location* (com.androidapps.widget.weather2.Weather & Toggle Widgets): 30 m 36 s (1836 s) Count:308 5.4%
ActivityManager-Launch (Android System): 3 m 35 s (215 s) Count:610 0.6%
led_lck (com.devuni.flashlight.Flashlight): 1 m 47 s (107 s) Count:10 0.3%
GSM (Dialer): 1 m 35 s (95 s) Count:34 0.3%
swift CPU (com.samsung.swift.app.kiesair.Kies air): 1 m 20 s (80 s) Count:2 0.2%
AlarmManager (Android System): 1 m 6 s (66 s) Count:3139 0.2%
*sync* (Google Services): 60 s (60 s) Count:12 0.2%
StartingDockService (Android System): 40 s (40 s) Count:1098 0.1%
SMSDispatcher (Dialer): 39 s (39 s) Count:22 0.1%
RILJ (Dialer): 33 s (33 s) Count:1621 0.1%
*network-location* (com.bumptech.bumpga.Bump): 30 s (30 s) Count:10 0.1%
sleep_broadcast (Android System): 29 s (29 s) Count:1057 0.1%
StartingAlertService (com.android.mms.Messaging): 23 s (23 s) Count:36 0.1%
GTALK_CONN (Google Services): 17 s (17 s) Count:607 0.1%
show keyguard (Android System): 16 s (16 s) Count:45 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 10 s (10 s) Count:5 0.0%
*backup* (Android System): 9 s (9 s) Count:1118 0.0%
SCREEN_FROZEN (Android System): 8 s (8 s) Count:1090 0.0%
ScoSocket (Dialer): 7 s (7 s) Count:10 0.0%
*sync* (com.google.android.gm.Gmail): 7 s (7 s) Count:1 0.0%
Event Log Service (Google Services): 6 s (6 s) Count:456 0.0%
keyguardWakeAndHandOff (Android System): 6 s (6 s) Count:1195 0.0%
GTALK_ASYNC_CONN (Google Services): 6 s (6 s) Count:3 0.0%
fullsync (com.whatsapp.WhatsApp): 5 s (5 s) Count:2 0.0%
*network-location* (Google Services): 4 s (4 s) Count:436 0.0%
MediaScannerService (Media): 4 s (4 s) Count:2 0.0%
*network-location-cell-update* (Google Services): 4 s (4 s) Count:424 0.0%
LocationManagerService (Android System): 3 s (3 s) Count:300 0.0%
ActivityManager-Sleep (Android System): 3 s (3 s) Count:3244 0.0%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 2 s (2 s) Count:2 0.0%
Proximity Partial (Android System): 1 s (1 s) Count:50 0.0%
GOOGLE_C2DM (Google Services): 1 s (1 s) Count:434 0.0%
WifiService (Android System): 1 s (1 s) Count:1108 0.0%
Browser (com.android.browser.Internet): 1 s (1 s) Count:4 0.0%
Highlighted in bold, main culprit your weather widget, kept awake for 30mins. Either remove those or decrease intervals. Other than that it's not that bad to be honest.
P.S you should update to a newer 2.3.5 rom, improved to 2.3.4, better battery life using another kernel as well like Speedmod.
Same here from past fews days my battery only lasts for 8 to 9 hours
Sent from my GT-I9100 using xda premium
Alright, thank you very much! one last question, how can i decrease these intervals as you said?
and btw, if I flash a new kernal do i need to perform a full wipe?
When I used Lightning I had the same battery problem, it only lasted for 9hrs MAX with normal use.
Installed this one and now it gives me 26hrs the most ! But still a huge improvement over the old F/W.
http://forum.xda-developers.com/showthread.php?t=1124396
clashed said:
Alright, thank you very much! one last question, how can i decrease these intervals as you said?
and btw, if I flash a new kernal do i need to perform a full wipe?
Click to expand...
Click to collapse
Kernel? No. Wipe both the cache.
Decreasing the intervals? Reduce the refresh time of the weather widget. If you don't use kies air. You could freeze it with TB.
Ok pretty cool app I found, it really helps your battery if you are running any of the ICS roms/kernels. What it does is use your light sensor to see if your screen should be on or not. So if you put your phone face down on your desk, or you put it in your pocket, your screen automatically turns off without you pressing the button, and it stays off until you take it out.
Good idea, but I'd use it in conjunction with Better Battery Stats to see if it will hold a wakelock.. sounds like it might
I am testing this as we speak, only had it for 1/2 hour but when i look in battery stats there is no longer any indication of screen on and awake. Need to look inti the better batt stats app more though.
Code:
===================
General Information
===================
BetterBatteryStats version: 1.7.1.0
Creation Date: 2012-03-23 10:42:17
Statistic Type: (3)
Since 1 h 57 m 12 s
VERSION.RELEASE: 4.0.3
BRAND: Samsung
DEVICE: galaxys2
MANUFACTURER: samsung
MODEL: SGH-I777
RADIO: unknown
BOOTLOADER: unknown
FINGERPRINT: samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPQ:user/release-keys
HARDWARE: smdk4210
ID: IML74K
Rooted: true
===========
Other Usage
===========
Wifi On (): 1 h 57 m 12 s (7032 s) Ratio: 100.0%
Wifi Running (): 1 h 57 m 12 s (7032 s) Ratio: 100.0%
Bluetooth On (): 1 h 57 m 12 s (7032 s) Ratio: 100.0%
Awake (): 29 m 51 s (1791 s) Ratio: 25.5%
Screen On (): 16 m 40 s (1000 s) Ratio: 14.2%
=========
Wakelocks
=========
AudioOut_1 (1013): 2 m 54 s (174 s) Count:49 9.7%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 1 m 18 s (78 s) Count:14 4.4%
SyncLoopWakeLock (Android System): 59 s (59 s) Count:688 3.3%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 30 s (30 s) Count:17 1.7%
[email protected]/android_talk9bec91c984d3 (Google Services): 28 s (28 s) Count:15 1.6%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 22 s (22 s) Count:213 1.3%
sleep_broadcast (Android System): 14 s (14 s) Count:216 0.8%
ActivityManager-Launch (Android System): 10 s (10 s) Count:84 0.6%
RILJ (Phone): 9 s (9 s) Count:261 0.5%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 9 s (9 s) Count:4 0.5%
*sync*_com.twitter.android.provider.TwitterProvider_Account {name=HaruSoul, type=com.twitter.android.auth.login} (com.twitter.android.Twitter): 7 s (7 s) Count:2 0.4%
FacebookService (com.facebook.katana.Facebook): 7 s (7 s) Count:5 0.4%
AlarmManager (Android System): 7 s (7 s) Count:583 0.4%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 6 s (6 s) Count:7 0.3%
Proximity Partial (Android System): 5 s (5 s) Count:15 0.3%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 4 s (4 s) Count:1 0.3%
GTALK_CONN (Google Services): 3 s (3 s) Count:203 0.2%
ConnectivityService (Android System): 3 s (3 s) Count:585 0.2%
ActivityManager-Sleep (Android System): 3 s (3 s) Count:640 0.2%
AudioOut_1281 (1013): 3 s (3 s) Count:3 0.2%
NetworkStats (Android System): 2 s (2 s) Count:52 0.1%
DownloadManager (Media): 2 s (2 s) Count:2 0.1%
*sync*_com.google.android.apps.docs_Account {[email protected], type=com.google} (com.google.android.apps.docs.Docs): 1 s (1 s) Count:2 0.1%
DocsSyncAdapter (com.google.android.apps.docs.Docs): 1 s (1 s) Count:3 0.1%
GpsLocationProvider (Android System): 1 s (1 s) Count:95 0.1%
*vibrator* (Android System): 1 s (1 s) Count:248 0.1%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cnt:(c/wc/ec)1/1/1 100.0%
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
Not sure where I should be looking, or if 2 hours is a long enough time table to test.
Was it face down or in your pocket the entire two hours? Or did you use it for 16 min?
twiggums said:
Was it face down or in your pocket the entire two hours? Or did you use it for 16 min?
Click to expand...
Click to collapse
Used it for 16. I can do a fresh test tonight without using it and post it tomorrow.
I just tested this for 15mins, and CPUspy reports 90% deep sleep. This may be totally valid.
What happens if you are in a totally dark room and want to turn it on? I'll give this a try..
Ashhong said:
What happens if you are in a totally dark room and want to turn it on? I'll give this a try..
Click to expand...
Click to collapse
Carry a mini flashlight with you and point it at your device.
Ashhong said:
What happens if you are in a totally dark room and want to turn it on? I'll give this a try..
Click to expand...
Click to collapse
Oh...
I'm suffering from poor battery life on my S3 - worse than my S2 with the same set of user-installed apps. I suspect that it's because I tend to leave wifi switched on. Could someone provide guidance on a power-efficient way of managing wifi?
I want to receive notifications of incoming emails, and would like this to be done via wifi wherever possible. I have wifi both at home and at work. If I'm away from home and work ideally I don't want the phone to hunt for wifi signals.
Can anyone recommend the best way of achieving the above in the most power-efficient way?
You can try tasker or llama to manage a lot ou things in various conditions... Like Wifi off when Screen off... Etc....
Envoyé depuis mon GT-I9300 avec Tapatalk
Wifi doesn't drain a lot of battery, at least not for me.
Do you have a very faint signal or regular drops?
Please report what BetterBatteryStats (free APK here in XDA) shows after several hours (ideally a full battery cycle) of usage.
Past SG models WiFi has been found to drain battery when searching for networks .
If i turn my router off then SGS is searching for networks .
jje
That's true.
However it's the same for all wiieless data connectionsz sensing across frequencies costs more battery than keeping a connection alive.
I'd recommend JuiceDefender Beta since it can manage all data connections and additronally automatically toggle 3g/2g upon requirement.
The app's cost of a few bucks is in no relation to the worth of a longer-living battery on your 600USD phone
Sent from my GT-I9300 using xda premium
d4fseeker said:
Wifi doesn't drain a lot of battery, at least not for me.
Do you have a very faint signal or regular drops?
Please report what BetterBatteryStats (free APK here in XDA) shows after several hours (ideally a full battery cycle) of usage.
Click to expand...
Click to collapse
Here's the output from BetterBatteryStats, for a period of about 3 hours after unplugging the phone. During this time it was turned on very briefly a couple of times to check notifications, and was within 10 feet of the wifi router.
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-07-06 12:43:46
Statistic Type: (3) Since Unplugged
Since 3 h 19 m 46 s
VERSION.RELEASE: 4.0.4
BRAND: samsung
DEVICE: m0
MANUFACTURER: samsung
MODEL: GT-I9300
BOOTLOADER: I9300XXALE8
FINGERPRINT: samsung/m0xx/m0:4.0.4/IMM76D/I9300XXALE8:user/release-keys
HARDWARE: smdk4x12
ID: IMM76D
TAGS: release-keys
USER: se.infra
PRODUCT: m0xx
RADIO: I9300NELE4
Rooted: true
===========
Other Usage
===========
Wifi On (): 3 h 19 m 46 s (11986 s) Ratio: 100.0%
Poor Signal (): 3 h 4 m 31 s (11071 s) Ratio: 92.4%
Deep Sleep (): 2 h 54 m 59 s (10499 s) Ratio: 87.6%
Awake (): 24 m 47 s (1487 s) Ratio: 12.4%
Wifi Running (): 16 m 8 s (968 s) Ratio: 8.1%
No Data Connection (): 15 m 14 s (914 s) Ratio: 7.6%
No or Unknown Signal (): 15 m 14 s (914 s) Ratio: 7.6%
Screen On (): 15 s (15 s) Ratio: 0.1%
=========
Wakelocks
=========
*sync*_gmail-ls_Account {name=EM, type=com.google} (com.google.android.gm.Gmail): 4 m 48 s (288 s) Count:47 2.4%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 53 s (53 s) Count:79 0.4%
SyncLoopWakeLock (Android System): 52 s (52 s) Count:485 0.4%
*backup* (Android System): 27 s (27 s) Count:84 0.2%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 26 s (26 s) Count:10 0.2%
com.bellshare.util.WakefulIntentService (com.bellshare.beweather.BeWeather Pro): 23 s (23 s) Count:3 0.2%
FacebookService (com.facebook.katana.Facebook): 23 s (23 s) Count:6 0.2%
AlarmManager (Android System): 17 s (17 s) Count:291 0.1%
sleep_broadcast (Android System): 8 s (8 s) Count:80 0.1%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 8 s (8 s) Count:9 0.1%
*sync*_com.android.contacts_Account {name=EM, type=com.google} (Google Services): 7 s (7 s) Count:62 0.1%
GTALK_CONN (Google Services): 6 s (6 s) Count:221 0.1%
DHCP (Android System): 5 s (5 s) Count:81 0.0%
DownloadManager (Media): 4 s (4 s) Count:2 0.0%
GOOGLE_C2DM (Google Services): 4 s (4 s) Count:49 0.0%
NetworkLocationBurstCollector (com.google.android.apps.maps.Maps): 4 s (4 s) Count:11 0.0%
My Tag (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 4 s (4 s) Count:49 0.0%
RILS (com.sec.phone.SecPhone): 4 s (4 s) Count:1 0.0%
EM/android_talk14c111ed2ffe (Google Services): 3 s (3 s) Count:1 0.0%
Push Thread:6866 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 s (3 s) Count:45 0.0%
Push Thread:6793 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 s (3 s) Count:55 0.0%
Push Thread:6831 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 s (3 s) Count:44 0.0%
AudioOut_1 (1013): 2 s (2 s) Count:1 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 s (1 s) Count:229 0.0%
NetworkStats (Android System): 1 s (1 s) Count:23 0.0%
Push Thread:6865 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 1 s (1 s) Count:50 0.0%
Push Service:1 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 1 s (1 s) Count:18 0.0%
Push Thread:6669 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 1 s (1 s) Count:1 0.0%
WifiStateMachine (Android System): 1 s (1 s) Count:94 0.0%
GpsLocationProvider (Android System): 1 s (1 s) Count:76 0.0%
================
Kernel Wakelocks
================
"multipdp" (): 18 m 3 s (1083 s) Cntc/wc/ec)97/0/96 9.0%
"secril_fd-interface" (): 9 m 32 s (572 s) Cntc/wc/ec)153/0/0 4.8%
"PowerManagerService" (): 8 m 37 s (517 s) Cntc/wc/ec)370/0/0 4.3%
"l2_hsic" (): 5 m 13 s (313 s) Cntc/wc/ec)830/75/829 2.6%
"battery-monitor" (): 3 m 7 s (187 s) Cntc/wc/ec)186/0/187 1.6%
"alarm_rtc" (): 1 m 42 s (102 s) Cntc/wc/ec)178/0/65 0.9%
"wlan_rx_wake" (): 1 m 3 s (63 s) Cntc/wc/ec)50/0/49 0.5%
"alarm" (): 46 s (46 s) Cntc/wc/ec)213/0/0 0.4%
"rpm_hsic" (): 46 s (46 s) Cntc/wc/ec)638/0/0 0.4%
"GPS" (): 43 s (43 s) Cntc/wc/ec)1/0/0 0.4%
"wlan_wake" (): 16 s (16 s) Cntc/wc/ec)149802/110/0 0.1%
"tx_hsic" (): 11 s (11 s) Cntc/wc/ec)1021/0/0 0.1%
"umts_rfs0" (): 8 s (8 s) Cntc/wc/ec)3/0/3 0.1%
"AudioOutLock" (): 4 s (4 s) Cntc/wc/ec)1/0/0 0.0%
"umts_ipc0" (): 3 s (3 s) Cntc/wc/ec)10/0/10 0.0%
"vib_present" (): 3 s (3 s) Cntc/wc/ec)2/0/0 0.0%
"radio-interface" (): 2 s (2 s) Cntc/wc/ec)4/0/0 0.0%
"event1-2108" (): 1 s (1 s) Cntc/wc/ec)2/0/0 0.0%
"efsd-interface" (): (0 s) Cntc/wc/ec)6/0/0 0.0%
"event10-2108" (): (0 s) Cntc/wc/ec)1848/0/0 0.0%
"event4-2108" (): (0 s) Cntc/wc/ec)865/0/0 0.0%
"secril_rfs-interface" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"event5-2108" (): (0 s) Cntc/wc/ec)604/0/0 0.0%
"sync_system" (): (0 s) Cntc/wc/ec)2/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)216/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)22/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)239/0/0 0.0%
"mmc1_detect" (): (0 s) Cntc/wc/ec)198/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)198/0/0 0.0%
Please use the code tags when copy-pasting content, since it will format the content in easier-to-read format and prevent the forum from inserting smilies.
Your issue seems to be:
Code:
Poor Signal (): 3 h 4 m 31 s (11071 s) Ratio: 92.4%
That will, of course, drain the battery pretty fast since the Amplifier needs to run at maximum capacity to reach the antenna. If you have better signal on the S2 and use a case on the S3 try removing it (temporarely)
d4fseeker said:
Please use the code tags when copy-pasting content, since it will format the content in easier-to-read format and prevent the forum from inserting smilies.
Your issue seems to be:
Code:
Poor Signal (): 3 h 4 m 31 s (11071 s) Ratio: 92.4%
That will, of course, drain the battery pretty fast since the Amplifier needs to run at maximum capacity to reach the antenna. If you have better signal on the S2 and use a case on the S3 try removing it (temporarely)
Click to expand...
Click to collapse
Presumably it's the wifi signal that's weak, not the GSM signal?
I don't use a case with the S3, and it was sat on my desk all morning 10 feet from the wifi router, so I don't understand why the signal would have been weak :0(
Hi could someone help me interpret my better battery stats? I am trying to figure out if there is something/app eating my battery. here is the log below:
HTML:
===========
Other Usage
===========
Wifi On (): 23 h 28 m 48 s (84528 s) Ratio: 100.0%
Wifi Running (): 23 h 28 m 48 s (84528 s) Ratio: 100.0%
No Data Connection (): 20 h 15 m 20 s (72920 s) Ratio: 86.3%
No or Unknown Signal (): 20 h 15 m 20 s (72920 s) Ratio: 86.3%
Deep Sleep (): 15 h 57 m 51 s (57471 s) Ratio: 68.0%
Awake (): 7 h 30 m 56 s (27056 s) Ratio: 32.0%
Moderate Signal (): 3 h 4 m 17 s (11057 s) Ratio: 13.1%
Screen On (): 1 h 21 m 50 s (4910 s) Ratio: 5.8%
Phone On (): 10 m 44 s (644 s) Ratio: 0.8%
Poor Signal (): 9 m 10 s (550 s) Ratio: 0.7%
=========
Wakelocks
=========
MAIL_SERVICE (com.android.exchange.Exchange services): 1 h 9 m 40 s (4180 s) Count:850 4.9%
AudioOut_1 (1013): 14 m 21 s (861 s) Count:98 1.0%
AlarmManager (Android System): 5 m 25 s (325 s) Count:4722 0.4%
FacebookService (com.facebook.katana.Facebook): 3 m 23 s (203 s) Count:3279 0.2%
ActivityManager-Launch (Android System): 1 m 13 s (73 s) Count:332 0.1%
EM/android_talk601572e25ab2 (Google Services): 1 m 10 s (70 s) Count:134 0.1%
RILJ (Phone): 52 s (52 s) Count:362 0.1%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 49 s (49 s) Count:829 0.1%
RILS (com.sec.phone.SecPhone): 44 s (44 s) Count:11 0.1%
ConnectivityService (Android System): 43 s (43 s) Count:4731 0.1%
DownloadManager (Media): 33 s (33 s) Count:6 0.0%
GSM (Phone): 26 s (26 s) Count:3 0.0%
DHCP (Android System): 24 s (24 s) Count:557 0.0%
show keyguard (Android System): 22 s (22 s) Count:27 0.0%
sleep_broadcast (Android System): 19 s (19 s) Count:535 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 10 s (10 s) Count:379 0.0%
GTALK_CONN (Google Services): 10 s (10 s) Count:805 0.0%
*backup* (Android System): 9 s (9 s) Count:590 0.0%
Event Log Service (Google Services): 5 s (5 s) Count:55 0.0%
*sync*_com.android.calendar_Account {name=EM, type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 5 s (5 s) Count:9 0.0%
NetworkStats (Android System): 5 s (5 s) Count:156 0.0%
*sync*_tasks_Account {name=EM, type=com.android.exchange} (com.android.exchange.Exchange services): 4 s (4 s) Count:851 0.0%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 4 s (4 s) Count:2 0.0%
SyncLoopWakeLock (Android System): 4 s (4 s) Count:4906 0.0%
Checkin Service (Google Services): 3 s (3 s) Count:922 0.0%
C2DM_LIB (com.facebook.orca.Messenger): 3 s (3 s) Count:6 0.0%
VibratorService (com.viber.voip.Viber): 2 s (2 s) Count:5 0.0%
MQTT (com.facebook.orca.Messenger): 2 s (2 s) Count:86 0.0%
VibratorService (com.facebook.orca.Messenger): 2 s (2 s) Count:15 0.0%
*sync*_gmail-ls_Account {name=EM, type=com.google} (com.google.android.gm.Gmail): 2 s (2 s) Count:1 0.0%
SCREEN_FROZEN (Android System): 2 s (2 s) Count:565 0.0%
*sync*_subscribedfeeds_Account {name=EM, type=com.google} (Google Services): 1 s (1 s) Count:8 0.0%
com.google.android.apps.googlevoice.PushNotificationRegistrationService (com.google.android.apps.googlevoice.Google Voice): 1 s (1 s) Count:1 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:4771 0.0%
GOOGLE_C2DM (Google Services): 1 s (1 s) Count:7 0.0%
reset keyguard (Android System): 1 s (1 s) Count:546 0.0%
*sync*_com.android.contacts_Account {name=EM, type=com.google} (Google Services): 1 s (1 s) Count:177 0.0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar storage): 1 s (1 s) Count:6 0.0%
================
Kernel Wakelocks
================
"wlan_rx_wake" (): 2 h 21 m 40 s (8500 s) Cnt:(c/wc/ec)5985/0/5986 10.1%
"battery-monitor" (): 2 h 5 m 10 s (7510 s) Cnt:(c/wc/ec)7601/0/7600 8.9%
"l2_hsic" (): 1 h 44 m 52 s (6292 s) Cnt:(c/wc/ec)13603/527/13603 7.4%
"multipdp" (): 1 h 20 m 21 s (4821 s) Cnt:(c/wc/ec)475/0/475 5.7%
"PowerManagerService" (): 1 h 16 m 47 s (4607 s) Cnt:(c/wc/ec)6978/0/0 5.4%
"alarm_rtc" (): 44 m 25 s (2665 s) Cnt:(c/wc/ec)4594/0/1349 3.2%
"secril_fd-interface" (): 40 m 59 s (2459 s) Cnt:(c/wc/ec)865/0/0 2.9%
"alarm" (): 17 m 50 s (1070 s) Cnt:(c/wc/ec)6002/0/0 1.3%
"mmc1_detect" (): 9 m 54 s (594 s) Cnt:(c/wc/ec)9101/0/0 0.7%
"rpm_hsic" (): 7 m 28 s (448 s) Cnt:(c/wc/ec)4583/0/0 0.5%
"wlan_wake" (): 3 m 11 s (191 s) Cnt:(c/wc/ec)140892/4429/0 0.2%
"umts_ipc0" (): 2 m 6 s (126 s) Cnt:(c/wc/ec)402/0/402 0.1%
"tx_hsic" (): 1 m 57 s (117 s) Cnt:(c/wc/ec)21144/0/0 0.1%
"radio-interface" (): 1 m 46 s (106 s) Cnt:(c/wc/ec)211/0/0 0.1%
"AudioOutLock" (): 44 s (44 s) Cnt:(c/wc/ec)92/0/0 0.1%
"vib_present" (): 40 s (40 s) Cnt:(c/wc/ec)987/0/0 0.0%
"umts_rfs0" (): 32 s (32 s) Cnt:(c/wc/ec)14/0/14 0.0%
"event1-2094" (): 10 s (10 s) Cnt:(c/wc/ec)177/17/0 0.0%
"prx_wake_lock" (): 6 s (6 s) Cnt:(c/wc/ec)4/0/4 0.0%
"efsd-interface" (): 2 s (2 s) Cnt:(c/wc/ec)28/0/0 0.0%
"boot_hsic" (): 1 s (1 s) Cnt:(c/wc/ec)1/0/0 0.0%
"secril_rfs-interface" (): 1 s (1 s) Cnt:(c/wc/ec)14/0/0 0.0%
"sync_system" (): 1 s (1 s) Cnt:(c/wc/ec)40/0/0 0.0%
"secril_fmt-interface" (): 1 s (1 s) Cnt:(c/wc/ec)2098/0/0 0.0%
"event6-2094" (): (0 s) Cnt:(c/wc/ec)4/2/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)7601/2337/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)39537/0/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)9101/0/0 0.0%
"ApmCommandThread" (): (0 s) Cnt:(c/wc/ec)118/0/0 0.0%
"client-interface" (): (0 s) Cnt:(c/wc/ec)79/0/0 0.0%
======================
Alarms (requires root)
======================
OK, anyone? Nothing really to tune or improve? I thought I provided all the info needed for someone to help.
azsamsancho said:
OK, anyone? Nothing really to tune or improve? I thought I provided all the info needed for someone to help.
Click to expand...
Click to collapse
Not the way XDA works is it at all expecting an unpaid service .
Someone can read them is needed to read your post first for that you may wait or post in the better battery stats thread .
jje
Wife's friends has an S-II and she started getting terrible battery life. She took it to Sprint and they replaced the battery but it's still terrible. Draining 15% per hour. I had her install BBS and here is the log. Seems to me that it's a combination of Latitude (guess from NetworkLocation service firing so much) and her WIFI acting up. I leave my WIFI on 100% of the time without having it drain like this so it's a bit confusing. Could it be caused from being in a location with a weak WIFI connection to one in your list and it connecting/disconnecting constantly?
===================
General Information
===================
BetterBatteryStats version: 1.12.0.0RC7
Creation Date: 2013-03-01 18:50:02
Statistic Type: Unplugged to Current
Since 2 h 56 m 33 s
VERSION.RELEASE: 4.0.4
BRAND: samsung
DEVICE: SPH-D710
MANUFACTURER: samsung
MODEL: SPH-D710
OS.VERSION: 3.0.15-1173404
BOOTLOADER: unknown
HARDWARE: smdk4210
FINGERPRINT: samsung/SPH-D710/SPH-D710:4.0.4/IMM76I/FL24:user/release-keys
ID: IMM76I
TAGS: release-keys
USER: se.infra
PRODUCT: SPH-D710
RADIO: S710.10 S.FL24
Rooted: false
============
Battery Info
============
Level lost [%]: 43 Bat.: 43% (99% to 56%) [14.6%/h]
Voltage lost [mV]: 314 (4117-3803) [106.8%/h]
===========
Other Usage
===========
Deep Sleep (): 1 h 4 m (3840 s) Ratio: 36.3%
Awake (): 1 h 52 m 33 s (6753 s) Ratio: 63.7%
Screen On (): 47 m 32 s (2852 s) Ratio: 26.9%
Phone On (): 1 m 23 s (83 s) Ratio: 0.8%
Wifi On (): 2 h 56 m 33 s (10593 s) Ratio: 100.0%
Wifi Running (): 2 h 56 m 33 s (10593 s) Ratio: 100.0%
Bluetooth On (): 2 h 56 m 33 s (10593 s) Ratio: 100.0%
No Data Connection (): 2 h 32 m 55 s (9175 s) Ratio: 86.6%
No or Unknown Signal (): 2 h 32 m 55 s (9175 s) Ratio: 86.6%
Screen dark (): 27 m 18 s (1638 s) Ratio: 15.5%
Screen dimmed (): 2 m 16 s (136 s) Ratio: 1.3%
Screen medium (): 17 m 57 s (1077 s) Ratio: 10.2%
=========
Wakelocks
=========
NetworkLocationLocator (com.google.android.apps.maps.Maps): 12 m 21 s (741 s) Count:175 7.0%
AudioOut_1 (1013): 4 m 4 s (244 s) Count:55 2.3%
StartingAlertService (com.android.mms.Messaging): 2 m 31 s (151 s) Count:25 1.4%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 1 m 59 s (119 s) Count:603 1.1%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 1 m 55 s (115 s) Count:1450 1.1%
*sync*_gmail-ls_Account {name=*****[email protected], type=com.google} (com.google.android.gm.Gmail): 1 m 26 s (86 s) Count:27 0.8%
SyncLoopWakeLock (Android System): 1 m 8 s (68 s) Count:1064 0.7%
Starting CM_VnoteService (com.coremobility.app.vnotes.Voicemail): 57 s (57 s) Count:3 0.5%
LocationReceiverService (com.google.android.apps.maps.Maps): 56 s (56 s) Count:927 0.5%
StartingAlertService (com.handcent.nextsms.Handcent SMS): 52 s (52 s) Count:37 0.5%
Managewakelock: partial (com.handcent.nextsms.Handcent SMS): 52 s (52 s) Count:6 0.5%
AlarmManager (Android System): 42 s (42 s) Count:919 0.4%
RILJ (Phone): 37 s (37 s) Count:413 0.4%
ActivityManager-Launch (Android System): 34 s (34 s) Count:88 0.3%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 30 s (30 s) Count:719 0.3%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 24 s (24 s) Count:532 0.2%
sleep_broadcast (Android System): 23 s (23 s) Count:193 0.2%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 22 s (22 s) Count:32 0.2%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 19 s (19 s) Count:41 0.2%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=****[email protected], type=com.google} (com.google.android.apps.plus.Google+): 18 s (18 s) Count:1 0.2%
GTALK_ASYNC_CONN_****[email protected]/android7e1eea38b005 (Google Services): 17 s (17 s) Count:273 0.2%
SCREEN_FROZEN (Android System): 14 s (14 s) Count:218 0.1%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 13 s (13 s) Count:524 0.1%
GTALK_CONN (Google Services): 12 s (12 s) Count:270 0.1%
show keyguard (Android System): 11 s (11 s) Count:18 0.1%
SMSDispatcher (Phone): 10 s (10 s) Count:8 0.1%
FacebookService (com.facebook.katana.Facebook): 10 s (10 s) Count:3 0.1%
LocationReportingService (com.google.android.apps.maps.Maps): 9 s (9 s) Count:1459 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 8 s (8 s) Count:5 0.1%
ConnectivityService (Android System): 8 s (8 s) Count:921 0.1%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 8 s (8 s) Count:1379 0.1%
StartingPopupUtilsService (com.handcent.nextsms.Handcent SMS): 8 s (8 s) Count:31 0.1%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 6 s (6 s) Count:282 0.1%
NetworkStats (Android System): 4 s (4 s) Count:40 0.0%
LocationManagerService (Android System): 3 s (3 s) Count:47 0.0%
ActivityManager-Sleep (Android System): 3 s (3 s) Count:951 0.0%
MQTT (com.facebook.katana.Facebook): 2 s (2 s) Count:40 0.0%
GpsLocationProvider (Android System): 2 s (2 s) Count:112 0.0%
DataConnection (Phone): 2 s (2 s) Count:32 0.0%
Checkin Service (Google Services): 2 s (2 s) Count:295 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 2 s (2 s) Count:1106 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 1 s (1 s) Count:90 0.0%
ScheduleNextAlarmWakeLock (Calendar): 1 s (1 s) Count:5 0.0%
SyncManagerHandleSyncAlarm (Android System): 1 s (1 s) Count:133 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:33 0.0%
================
Kernel Wakelocks
================
"wlan_wake" (): 31 m 28 s (1888 s) Cntc/wc/ec)27605/189/0 17.8%
"PowerManagerService" (): 21 m 32 s (1292 s) Cntc/wc/ec)1075/0/0 12.2%
"wlan_rx_wake" (): 17 m 54 s (1074 s) Cntc/wc/ec)1094/0/1094 10.1%
"sec-battery-monitor" (): 3 m 43 s (223 s) Cntc/wc/ec)932/168/0 2.1%
"alarm_rtc" (): 3 m 39 s (219 s) Cntc/wc/ec)330/0/88 2.1%
"radio-interface" (): 1 m 46 s (106 s) Cntc/wc/ec)219/0/0 1.0%
"alarm" (): 1 m 9 s (69 s) Cntc/wc/ec)797/0/0 0.7%
"AudioOutLock" (): 32 s (32 s) Cntc/wc/ec)53/0/0 0.3%
"vib_present" (): 16 s (16 s) Cntc/wc/ec)9/0/0 0.2%
"power-supply" (): 15 s (15 s) Cntc/wc/ec)170/0/0 -0.0%
"sync_system" (): 5 s (5 s) Cntc/wc/ec)30/0/0 0.1%
"prx_wake_lock" (): 4 s (4 s) Cntc/wc/ec)4/0/4 0.0%
"BTLowPower" (): 3 s (3 s) Cntc/wc/ec)12/0/12 0.0%
"DPRAM_PWDOWN" (): 3 s (3 s) Cntc/wc/ec)4560/27/0 0.0%
"KeyEvents" (): 2 s (2 s) Cntc/wc/ec)21148/0/0 0.0%
"client-interface" (): (0 s) Cntc/wc/ec)3856/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)536/0/0 0.0%
"ApmCommandThread" (): (0 s) Cntc/wc/ec)37/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.2 GHz (): 6 m 9 s 3.5%
1 GHz (): 43 s 0.4%
800 MHz (): 26 m 1 s 14.7%
500 MHz (): 10 m 12 s 5.8%
200 MHz (): 1 h 9 m 26 s 39.3%
Deep Sleep (): 1 h 4 m 36.3%
fldash said:
Wife's friends has an S-II and she started getting terrible battery life. She took it to Sprint and they replaced the battery but it's still terrible. Draining 15% per hour. I had her install BBS and here is the log. Seems to me that it's a combination of Latitude (guess from NetworkLocation service firing so much) and her WIFI acting up. I leave my WIFI on 100% of the time without having it drain like this so it's a bit confusing. Could it be caused from being in a location with a weak WIFI connection to one in your list and it connecting/disconnecting constantly?
===================
General Information
===================
BetterBatteryStats version: 1.12.0.0RC7
Creation Date: 2013-03-01 18:50:02
Statistic Type: Unplugged to Current
Since 2 h 56 m 33 s
VERSION.RELEASE: 4.0.4
BRAND: samsung
DEVICE: SPH-D710
MANUFACTURER: samsung
MODEL: SPH-D710
OS.VERSION: 3.0.15-1173404
BOOTLOADER: unknown
HARDWARE: smdk4210
FINGERPRINT: samsung/SPH-D710/SPH-D710:4.0.4/IMM76I/FL24:user/release-keys
ID: IMM76I
TAGS: release-keys
USER: se.infra
PRODUCT: SPH-D710
RADIO: S710.10 S.FL24
Rooted: false
============
Battery Info
============
Level lost [%]: 43 Bat.: 43% (99% to 56%) [14.6%/h]
Voltage lost [mV]: 314 (4117-3803) [106.8%/h]
===========
Other Usage
===========
Deep Sleep (): 1 h 4 m (3840 s) Ratio: 36.3%
Awake (): 1 h 52 m 33 s (6753 s) Ratio: 63.7%
Screen On (): 47 m 32 s (2852 s) Ratio: 26.9%
Phone On (): 1 m 23 s (83 s) Ratio: 0.8%
Wifi On (): 2 h 56 m 33 s (10593 s) Ratio: 100.0%
Wifi Running (): 2 h 56 m 33 s (10593 s) Ratio: 100.0%
Bluetooth On (): 2 h 56 m 33 s (10593 s) Ratio: 100.0%
No Data Connection (): 2 h 32 m 55 s (9175 s) Ratio: 86.6%
No or Unknown Signal (): 2 h 32 m 55 s (9175 s) Ratio: 86.6%
Screen dark (): 27 m 18 s (1638 s) Ratio: 15.5%
Screen dimmed (): 2 m 16 s (136 s) Ratio: 1.3%
Screen medium (): 17 m 57 s (1077 s) Ratio: 10.2%
=========
Wakelocks
=========
NetworkLocationLocator (com.google.android.apps.maps.Maps): 12 m 21 s (741 s) Count:175 7.0%
AudioOut_1 (1013): 4 m 4 s (244 s) Count:55 2.3%
StartingAlertService (com.android.mms.Messaging): 2 m 31 s (151 s) Count:25 1.4%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 1 m 59 s (119 s) Count:603 1.1%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 1 m 55 s (115 s) Count:1450 1.1%
*sync*_gmail-ls_Account {name=*****[email protected], type=com.google} (com.google.android.gm.Gmail): 1 m 26 s (86 s) Count:27 0.8%
SyncLoopWakeLock (Android System): 1 m 8 s (68 s) Count:1064 0.7%
Starting CM_VnoteService (com.coremobility.app.vnotes.Voicemail): 57 s (57 s) Count:3 0.5%
LocationReceiverService (com.google.android.apps.maps.Maps): 56 s (56 s) Count:927 0.5%
StartingAlertService (com.handcent.nextsms.Handcent SMS): 52 s (52 s) Count:37 0.5%
Managewakelock: partial (com.handcent.nextsms.Handcent SMS): 52 s (52 s) Count:6 0.5%
AlarmManager (Android System): 42 s (42 s) Count:919 0.4%
RILJ (Phone): 37 s (37 s) Count:413 0.4%
ActivityManager-Launch (Android System): 34 s (34 s) Count:88 0.3%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 30 s (30 s) Count:719 0.3%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 24 s (24 s) Count:532 0.2%
sleep_broadcast (Android System): 23 s (23 s) Count:193 0.2%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 22 s (22 s) Count:32 0.2%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 19 s (19 s) Count:41 0.2%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=****[email protected], type=com.google} (com.google.android.apps.plus.Google+): 18 s (18 s) Count:1 0.2%
GTALK_ASYNC_CONN_****[email protected]/android7e1eea38b005 (Google Services): 17 s (17 s) Count:273 0.2%
SCREEN_FROZEN (Android System): 14 s (14 s) Count:218 0.1%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 13 s (13 s) Count:524 0.1%
GTALK_CONN (Google Services): 12 s (12 s) Count:270 0.1%
show keyguard (Android System): 11 s (11 s) Count:18 0.1%
SMSDispatcher (Phone): 10 s (10 s) Count:8 0.1%
FacebookService (com.facebook.katana.Facebook): 10 s (10 s) Count:3 0.1%
LocationReportingService (com.google.android.apps.maps.Maps): 9 s (9 s) Count:1459 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 8 s (8 s) Count:5 0.1%
ConnectivityService (Android System): 8 s (8 s) Count:921 0.1%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 8 s (8 s) Count:1379 0.1%
StartingPopupUtilsService (com.handcent.nextsms.Handcent SMS): 8 s (8 s) Count:31 0.1%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 6 s (6 s) Count:282 0.1%
NetworkStats (Android System): 4 s (4 s) Count:40 0.0%
LocationManagerService (Android System): 3 s (3 s) Count:47 0.0%
ActivityManager-Sleep (Android System): 3 s (3 s) Count:951 0.0%
MQTT (com.facebook.katana.Facebook): 2 s (2 s) Count:40 0.0%
GpsLocationProvider (Android System): 2 s (2 s) Count:112 0.0%
DataConnection (Phone): 2 s (2 s) Count:32 0.0%
Checkin Service (Google Services): 2 s (2 s) Count:295 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 2 s (2 s) Count:1106 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 1 s (1 s) Count:90 0.0%
ScheduleNextAlarmWakeLock (Calendar): 1 s (1 s) Count:5 0.0%
SyncManagerHandleSyncAlarm (Android System): 1 s (1 s) Count:133 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:33 0.0%
================
Kernel Wakelocks
================
"wlan_wake" (): 31 m 28 s (1888 s) Cntc/wc/ec)27605/189/0 17.8%
"PowerManagerService" (): 21 m 32 s (1292 s) Cntc/wc/ec)1075/0/0 12.2%
"wlan_rx_wake" (): 17 m 54 s (1074 s) Cntc/wc/ec)1094/0/1094 10.1%
"sec-battery-monitor" (): 3 m 43 s (223 s) Cntc/wc/ec)932/168/0 2.1%
"alarm_rtc" (): 3 m 39 s (219 s) Cntc/wc/ec)330/0/88 2.1%
"radio-interface" (): 1 m 46 s (106 s) Cntc/wc/ec)219/0/0 1.0%
"alarm" (): 1 m 9 s (69 s) Cntc/wc/ec)797/0/0 0.7%
"AudioOutLock" (): 32 s (32 s) Cntc/wc/ec)53/0/0 0.3%
"vib_present" (): 16 s (16 s) Cntc/wc/ec)9/0/0 0.2%
"power-supply" (): 15 s (15 s) Cntc/wc/ec)170/0/0 -0.0%
"sync_system" (): 5 s (5 s) Cntc/wc/ec)30/0/0 0.1%
"prx_wake_lock" (): 4 s (4 s) Cntc/wc/ec)4/0/4 0.0%
"BTLowPower" (): 3 s (3 s) Cntc/wc/ec)12/0/12 0.0%
"DPRAM_PWDOWN" (): 3 s (3 s) Cntc/wc/ec)4560/27/0 0.0%
"KeyEvents" (): 2 s (2 s) Cntc/wc/ec)21148/0/0 0.0%
"client-interface" (): (0 s) Cntc/wc/ec)3856/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)536/0/0 0.0%
"ApmCommandThread" (): (0 s) Cntc/wc/ec)37/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.2 GHz (): 6 m 9 s 3.5%
1 GHz (): 43 s 0.4%
800 MHz (): 26 m 1 s 14.7%
500 MHz (): 10 m 12 s 5.8%
200 MHz (): 1 h 9 m 26 s 39.3%
Deep Sleep (): 1 h 4 m 36.3%
Click to expand...
Click to collapse
Start with untick location services, (system settings, location....)
When i don't use wifi or BT i disable them. They are searching for wifi spots and BT continuously. Maybe this will help a bit.
Christiaan91 said:
Start with untick location services, (system settings, location....)
When i don't use wifi or BT i disable them. They are searching for wifi spots and BT continuously. Maybe this will help a bit.
Click to expand...
Click to collapse
I've been experiencing the same problem with my SGS2's battery and noticed that it is getting bloated. I purchased a new one to prevent severe damage on my mobile phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}