Related
Call all BetterBatteryStats pros. I'm trying to figure out what is causing these wakelocks on my phone. I'm running RedPill (CM7 with tweaks) on my Motorola Atrix.
I can't figure out what is giving me such large SyncManagerHandleSyncAlarm and AlarmManager wakelocks. I only have my Google Account syncing Contacts, Gmail, and Calendar with "Background data" and "Auto-sync" checked. I can't think of any other things that are causing this.
Also, I cannot figure out what AlarmManager and FDCompleteTime is and how I can stop that from wakelocking. Everything else seems pretty normal.
For my CM7 email app, I turned it from Push to Fetch every 30 minutes so that should help it from wakelocking.
Thanks for all the help!
Code:
===================
General Information
===================
BetterBatteryStats version: 1.1.1.0
Creation Date: 2011-12-06 15:10:49
Statistic Type: (3)
Since 7 h 2 m 7 s
VERSION.RELEASE: 2.3.7
BRAND: MOTO
DEVICE: olympus
MANUFACTURER: Motorola
MODEL: MB860
===========
Other Usage
===========
Wifi On (): 4 h 9 m 52 s (14992 s) Ratio: 59.2%
Awake (): 2 h 2 m 23 s (7343 s) Ratio: 29.0%
Screen On (): 1 h 26 m 56 s (5216 s) Ratio: 20.6%
=========
Wakelocks
=========
SyncManagerHandleSyncAlarm (Android System): 32 m 48 s (1968 s) Count:943 26.8%
MAIL_SERVICE (com.android.email.Email): 20 m 14 s (1214 s) Count:137 16.5%
FDCompleteTime (Dialer): 13 m 21 s (801 s) Count:293 10.9%
AlarmManager (Android System): 9 m 24 s (564 s) Count:2570 7.7%
*wifi* (Android System): 7 m 31 s (451 s) Count:1088 6.2%
Event Log Service (Google Services): 6 m 23 s (383 s) Count:216 5.2%
*network-location* (com.google.android.googlequicksearchbox.Google Search): 5 m 34 s (334 s) Count:40 4.6%
*sync* (com.google.android.gm.Gmail): 4 m 37 s (277 s) Count:65 3.8%
ActivityManager-Launch (Android System): 3 m 6 s (186 s) Count:669 2.5%
SmsBackup+ (com.zegoggles.smssync.SMS Backup+): 2 m 36 s (156 s) Count:6 2.1%
RILJ (Dialer): 2 m 16 s (136 s) Count:1191 1.9%
GTALK_ASYNC_CONN (Google Services): 2 m 10 s (130 s) Count:21 1.8%
android.media.MediaPlayer (com.android.music.Music): 1 m 32 s (92 s) Count:22 1.3%
*network-location* (Android System): 1 m 12 s (72 s) Count:709 1.0%
GTALK_CONN (Google Services): 54 s (54 s) Count:641 0.7%
BWL (com.levelup.beautifulwidgets.Beautiful Widgets): 54 s (54 s) Count:7 0.7%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 52 s (52 s) Count:110 0.7%
GpsLocationProvider (Android System): 49 s (49 s) Count:808 0.7%
FacebookService (com.facebook.katana.Facebook): 41 s (41 s) Count:12 0.6%
*vibrator* (Android System): 34 s (34 s) Count:1834 0.5%
show keyguard (Android System): 29 s (29 s) Count:35 0.4%
android.media.MediaPlayer (com.doubleTwist.androidPlayer.doubleTwist): 28 s (28 s) Count:10 0.4%
*network-location* (com.android.browser.Browser): 24 s (24 s) Count:29 0.3%
StartingAlertService (UID): 23 s (23 s) Count:50 0.3%
sleep_broadcast (Android System): 18 s (18 s) Count:1031 0.3%
*sync* (Google Services): 17 s (17 s) Count:146 0.2%
*network-location* (com.facebook.katana.Facebook): 14 s (14 s) Count:15 0.2%
*sync* (com.google.android.apps.docs.Docs): 11 s (11 s) Count:4 0.2%
Managewakelock: partial (UID): 10 s (10 s) Count:54 0.1%
DocsSyncAdapter (com.google.android.apps.docs.Docs): 9 s (9 s) Count:7 0.1%
*network-location* (Google Services): 9 s (9 s) Count:201 0.1%
Checkin Service (Google Services): 9 s (9 s) Count:712 0.1%
NetworkLocationCacheUpdater (com.google.android.apps.maps.Maps): 8 s (8 s) Count:13 0.1%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 7 s (7 s) Count:5 0.1%
SMSDispatcher (Dialer): 7 s (7 s) Count:297 0.1%
SCREEN_FROZEN (Android System): 7 s (7 s) Count:1107 0.1%
DownloadManager (Media): 6 s (6 s) Count:4 0.1%
*network-location* (com.levelup.beautifulwidgets.Beautiful Widgets): 5 s (5 s) Count:14 0.1%
Browser (com.android.browser.Browser): 4 s (4 s) Count:4 0.1%
MediaScannerService (Media): 4 s (4 s) Count:3 0.1%
GOOGLE_C2DM (Google Services): 3 s (3 s) Count:197 0.1%
M (net.dinglisch.android.taskerm.Tasker): 3 s (3 s) Count:241 0.0%
com.keramidas.TitaniumBackup.service.WorkerService (com.keramidas.TitaniumBackup.Titanium Backup): 3 s (3 s) Count:2 0.0%
*network-location* (com.handmark.tweetcaster.premium.TweetCaster Pro): 3 s (3 s) Count:4 0.0%
FDRILCommandTime (Dialer): 2 s (2 s) Count:142 0.0%
*vibrator* (UID): 2 s (2 s) Count:4 0.0%
StartingPopupUtilsService (UID): 2 s (2 s) Count:32 0.0%
DownloadManager (com.google.android.gm.Gmail): 1 s (1 s) Count:70 0.0%
*network-location-cell-update* (Google Services): 1 s (1 s) Count:139 0.0%
com.google.android.apps.googlevoice.PushNotificationRegistrationService (com.google.android.apps.googlevoice.Google Voice): 1 s (1 s) Count:1 0.0%
*wifi* (com.google.android.apps.maps.Maps): 1 s (1 s) Count:6 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 1 s (1 s) Count:5 0.0%
E (net.dinglisch.android.taskerm.Tasker): 1 s (1 s) Count:245 0.0%
=========
Processes
=========
suspend (0): Sys: 1 m 25 s (85 s) Us: (0 s) Starts: 0
com.quoord.tapatalksumsang.activity (com.quoord.tapatalksumsang.activity.Tapatalk): Sys: 6 s (6 s) Us: 24 s (24 s) Starts: 3
com.android.browser (com.android.browser.Browser): Sys: 4 s (4 s) Us: 21 s (21 s) Starts: 6
*wakelock* (Dialer): Sys: 14 s (14 s) Us: 4 s (4 s) Starts: 0
com.google.android.gm (com.google.android.gm.Gmail): Sys: 2 s (2 s) Us: 14 s (14 s) Starts: 8
android.process.acore (com.fede.launcher.LauncherPro): Sys: 1 s (1 s) Us: 9 s (9 s) Starts: 1
com.keramidas.TitaniumBackup (com.keramidas.TitaniumBackup.Titanium Backup): Sys: 1 s (1 s) Us: 7 s (7 s) Starts: 10
net.cdeguet.smartkeyboardpro (net.cdeguet.smartkeyboardpro.Smart Keyboard Pro): Sys: 1 s (1 s) Us: 6 s (6 s) Starts: 1
com.facebook.katana (com.facebook.katana.Facebook): Sys: 1 s (1 s) Us: 6 s (6 s) Starts: 2
com.asksven.betterbatterystats_xdaedition (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): Sys: 1 s (1 s) Us: 6 s (6 s) Starts: 3
netd (0): Sys: (0 s) Us: 5 s (5 s) Starts: 0
com.android.email (com.android.email.Email): Sys: (0 s) Us: 4 s (4 s) Starts: 2
com.android.settings (Android System): Sys: (0 s) Us: 4 s (4 s) Starts: 15
com.google.android.talk (com.google.android.talk.Talk): Sys: (0 s) Us: 3 s (3 s) Starts: 3
com.mint (com.mint.Mint.com): Sys: (0 s) Us: 3 s (3 s) Starts: 2
com.handcent.nextsms (UID): Sys: (0 s) Us: 3 s (3 s) Starts: 4
cpufreq-dvfsd (0): Sys: 3 s (3 s) Us: (0 s) Starts: 0
com.doubleTwist.androidPlayer (com.doubleTwist.androidPlayer.doubleTwist): Sys: (0 s) Us: 2 s (2 s) Starts: 6
nvrm_daemon (0): Sys: 1 s (1 s) Us: 1 s (1 s) Starts: 0
com.android.systemui (Android System): Sys: (0 s) Us: 2 s (2 s) Starts: 1
com.roflharrison.agenda.plus (com.roflharrison.agenda.plus.Android Agenda Widget Plus): Sys: (0 s) Us: 2 s (2 s) Starts: 11
cn.miren.browser (cn.miren.browser.Miren Browser): Sys: (0 s) Us: 1 s (1 s) Starts: 30
net.dinglisch.android.taskerm (net.dinglisch.android.taskerm.Tasker): Sys: (0 s) Us: 2 s (2 s) Starts: 1
com.android.mms (com.android.mms.Messaging): Sys: (0 s) Us: 2 s (2 s) Starts: 1
com.google.process.gapps (Google Services): Sys: (0 s) Us: 1 s (1 s) Starts: 1
com.android.vending (com.android.vending.Market): Sys: (0 s) Us: 2 s (2 s) Starts: 9
com.cyanogenmod.cmparts (Android System): Sys: (0 s) Us: 1 s (1 s) Starts: 5
org.gtmedia.seekdroid (org.gtmedia.seekdroid.SeekDroid): Sys: (0 s) Us: 1 s (1 s) Starts: 5
mediaserver (1013): Sys: (0 s) Us: 1 s (1 s) Starts: 0
com.levelup.beautifulwidgets (com.levelup.beautifulwidgets.Beautiful Widgets): Sys: (0 s) Us: 1 s (1 s) Starts: 37
com.android.phone (Dialer): Sys: (0 s) Us: 1 s (1 s) Starts: 1
*wakelock* (com.google.android.gm.Gmail): Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.handmark.tweetcaster.premium (com.handmark.tweetcaster.premium.TweetCaster Pro): Sys: (0 s) Us: 1 s (1 s) Starts: 1
com.discoverfinancial.mobile (com.discoverfinancial.mobile.Discover): Sys: (0 s) Us: 1 s (1 s) Starts: 1
events/0 (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
als_wq (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
========
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
com.authentec.TrueSuiteMobile (com.authentec.GfxEngine.Control.GfxService)
Active since: 32 s
Last activity: 1 h 32 m 2 s
Crash count:0
net.dinglisch.android.taskerm (net.dinglisch.android.taskerm.MonitorService)
Active since: 39 s
Last activity: 2 h 2 m
Crash count:0
com.google.android.apps.googlevoice (com.google.android.apps.googlevoice.UpdateService)
Active since: 1 h 54 m 36 s
Last activity: 1 h 59 m 5 s
Crash count:0
com.motorola.usb (com.motorola.usb.UsbService)
Active since: 33 s
Last activity: 33 s
Crash count:0
com.android.email (com.android.exchange.SyncManager)
Active since: 34 s
Last activity: 1 h 59 m 32 s
Crash count:0
com.google.android.talk:videoChat (com.google.android.talk.videochat.VideoChatService)
Active since: 58 m 55 s
Last activity: 53 m 27 s
Crash count:0
com.crittercism.service (com.crittercism.service.CrittercismService)
Active since: 45 s
Last activity: 2 h 1 m 15 s
Crash count:0
net.cdeguet.smartkeyboardpro (net.cdeguet.smartkeyboardpro.SmartKeyboard)
Active since: 24 s
Last activity: 24 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 24 s
Last activity: 24 s
Crash count:0
system (com.android.internal.service.wallpaper.ImageWallpaper)
Active since: 24 s
Last activity: 24 s
Crash count:0
com.android.systemui (com.android.systemui.statusbar.StatusBarService)
Active since: 22 s
Last activity: 22 s
Crash count:0
com.google.android.apps.googlevoice (com.google.android.apps.googlevoice.CallLogService)
Active since: 44 s
Last activity: 1 h 58 m 55 s
Crash count:0
com.th.android.widget.gTabsimiClock (com.th.android.widget.gTabsimiClock.UpdateService)
Active since: 47 s
Last activity: 2 h 1 m 58 s
Crash count:0
com.bel.android.dspmanager (com.bel.android.dspmanager.HeadsetService)
Active since: 32 s
Last activity: 32 s
Crash count:0
android.tts (android.tts.TtsService)
Active since: 6 h 54 m 1 s
Last activity: 1 h 59 m 57 s
Crash count:0
com.android.phone (com.motorola.fastdormancy.FastDormancyService)
Active since: 34 s
Last activity: 34 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 33 s
Last activity: 33 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 21 s
Last activity: 21 s
Crash count:0
com.handmark.tweetcaster.premium (com.handmark.tweetcaster.UpdateService)
Active since: 45 s
Last activity: 1 h 48 m 54 s
Crash count:0
com.cyanogenmod.dockaudio (com.cyanogenmod.dockaudio.ListenSwitch)
Active since: 34 s
Last activity: 34 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 21 s
Last activity: 25 s
Crash count:0
com.mhuang.overclocking (com.mhuang.overclocking.ProfilesService)
Active since: 36 s
Last activity: 1 h 38 m 16 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 27 s
Last activity: 1 h 50 m 22 s
Crash count:0
com.facebook.katana (com.facebook.katana.service.UploadManager)
Active since: 31 s
Last activity: 1 h 50 m 22 s
Crash count:0
kshiuan said:
I cannot figure out what AlarmManager and FDCompleteTime is and how I can stop that from wakelocking. Everything else seems pretty normal.
Click to expand...
Click to collapse
AlarmManager:
AlarmManager provides access to the system alarm services. In simple English, it provides alarm services for the phone, like 'ring in an hour time'. You problem is that Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. What that means that if an app is requesting to be 'called' by the Alarm Service, the phone will not sleep. Once onReceive() returns, the Alarm Manager releases the wake lock and the phone will in some cases sleep as soon as your onReceive() method completes. What that means, is that once the app/apps say, figuratively "I got the Alarm Call and I did what I wanted to do!" the AlarmManager will release the wake lock and the phone will go to sleep.
Solution: Check for apps that call on AlarmManger. Apps that request for current time can also call upon AlarmManager. Apps that are well programmed and request, for example, the current time, but is non-crucial for that app to know that info when the phone is sleeping can use RTC. Using that, your phone will only give that info when it wakes up. However, apps can also use RTC_WAKEUP, which will force your phone to wake up, registering as a wakelock under AlarmManager, not the app that requested it. More info can be found here.
FDCompleteTime:
FDCompleteTime is the time which your phone takes to 'complete' FD, or Fast Dormancy. FD usually saves battery. For example, email update checks are done by the email application which, after receiving the server response, knows that it is not going to transmit or receive any further data. At that point the phone can tell the network “I don’t need to keep this connection active any more” and the network can immediately move the phone to a low energy state as preferred by the network operator, saving wasted battery and network resource. FDCompleteTime is there when the phone tells the network that “I don’t need to keep this connection active any more”. Usually, it is a very short period of time, but when your phone does not get a answer from the network, this time can stretch.
Solutions:FD can be turned off on some phones, but AFAIK, not on the ATRIX. I would STRONGLY DISCOURAGE you from touching FD though. More info on FD (VERY TECHNICAL) by the GSMA (random: I like their logo, especially the GSMA part. Love that font!) can be found here.
Hope that helps!
To ALL: I am NOT an expert. If I did say something wrong, or you think something is not right, or can be put a better way, please tell me. We both learn from the experience. Thanks!
Since around Thanksgiving, my battery has been draining in about 36 hours when it normally lasts 3 - 4 days. What I gathered from BetterBatteryStats is that the Wi-Fi is keeping the phone from sleeping about half the time. I used a different app to monitor data usage, and Wi-Fi traffic was low. My guess is that an app is frequently accessing the Wi-Fi without sending much (or any) data. Is there a way to find the culprit without uninstalling apps one by one?
Code:
===================
General Information
===================
BetterBatteryStats version: 1.11.0.0
Creation Date: 2012-12-13 15:24:34
Statistic Type: (3) Since Unplugged
Since 1 d 15 h 50 m 17 s
VERSION.RELEASE: 2.3.4
BRAND: tmobile
DEVICE: glacier
MANUFACTURER: HTC
MODEL: HTC Glacier
OS.VERSION: 2.6.35.10-g4dcb781
BOOTLOADER: 0.89.0006
HARDWARE: glacier
FINGERPRINT: tmobile/htc_glacier/glacier:2.3.4/GRJ22/209954.1:user/release-keys
ID: GRJ22
TAGS: release-keys
USER: unknown
PRODUCT: htc_glacier
RADIO: unknown
Rooted: false
============
Battery Info
============
Level lost [%]: 95 Bat.: 95% (100% to 5%) [2.4%/h]
Voltage lost [mV]: 620 (4207-3587)
===========
Other Usage
===========
Wifi On (): 1 d 15 h 50 m 17 s (143417 s) Ratio: 100.0%
Wifi Running (): 1 d 15 h 50 m 17 s (143417 s) Ratio: 100.0%
No Data Connection (): 1 d 13 h 3 m 15 s (133395 s) Ratio: 93.0%
No or Unknown Signal (): 1 d 13 h 3 m 15 s (133395 s) Ratio: 93.0%
Awake (): 20 h 13 m 4 s (72784 s) Ratio: 50.7%
Deep Sleep (): 19 h 37 m 12 s (70632 s) Ratio: 49.2%
Good Signal (): 2 h 29 m 45 s (8985 s) Ratio: 6.3%
Screen On (): 12 m 46 s (766 s) Ratio: 0.5%
Phone On (): 6 m 19 s (379 s) Ratio: 0.3%
=========
Wakelocks
=========
WifiService (Android System): 18 h 48 m 7 s (67687 s) Count:4645 47.2%
AlarmManager (Android System): 1 h 54 m 36 s (6876 s) Count:14892 4.8%
*sync* (Calendar): 7 m 22 s (442 s) Count:29 0.3%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 2 m 51 s (171 s) Count:4 0.1%
WifiStateTracker (Android System): 2 m 33 s (153 s) Count:363 0.1%
ActivityManager-Launch (Android System): 1 m 39 s (99 s) Count:316 0.1%
*network-location* (com.groupon.Groupon): 1 m 18 s (78 s) Count:40 0.1%
keyguardWakeAndHandOff (Android System): 1 m 7 s (67 s) Count:4664 0.0%
MdmDataReporter (com.mobidia.android.mdm.My Data Manager): 1 m 6 s (66 s) Count:270 0.0%
GTALK_ASYNC_CONN (Google Services): 54 s (54 s) Count:17 0.0%
BatteryServiceWakeLock (com.modroid.battery.Battery Graph): 53 s (53 s) Count:478 0.0%
*network-location* (Android System): 52 s (52 s) Count:349 0.0%
GSM (Dialer): 51 s (51 s) Count:50 0.0%
*sync* (com.google.android.gm.Gmail): 39 s (39 s) Count:17 0.0%
MAIL_BLK (com.htc.android.mail.Mail): 28 s (28 s) Count:28 0.0%
RILJ (Dialer): 27 s (27 s) Count:490 0.0%
*network-location* (Calendar): 27 s (27 s) Count:85 0.0%
MAIL_PWR_LOCK (com.htc.android.mail.Mail): 26 s (26 s) Count:14 0.0%
sleep_broadcast (Android System): 18 s (18 s) Count:663 0.0%
SYNCHRONIZED (com.htc.android.mail.Mail): 18 s (18 s) Count:27 0.0%
*sync* (com.htc.android.mail.Mail): 15 s (15 s) Count:24 0.0%
*sync* (Google Services): 14 s (14 s) Count:161 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 13 s (13 s) Count:26 0.0%
GTALK_CONN (Google Services): 10 s (10 s) Count:798 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 8 s (8 s) Count:38 0.0%
ActivityManager-Sleep (Android System): 7 s (7 s) Count:14919 0.0%
Event Log Service (Google Services): 6 s (6 s) Count:254 0.0%
htcCheckinService (Android System): 6 s (6 s) Count:4666 0.0%
GpsLocationProvider (Android System): 5 s (5 s) Count:589 0.0%
com.smartandroidapps.audiowidgetlib (com.smartandroidapps.audiowidget.AudioManager): 5 s (5 s) Count:24 0.0%
*sync* (com.google.android.music.Google Play Music): 4 s (4 s) Count:2 0.0%
Checkin Service (Google Services): 4 s (4 s) Count:947 0.0%
*network-location-cell-update* (Google Services): 4 s (4 s) Count:156 0.0%
LocationManagerService (Android System): 3 s (3 s) Count:177 0.0%
*network-location* (Google Services): 3 s (3 s) Count:175 0.0%
HtcPhoneSensorFunctions (Dialer): 2 s (2 s) Count:508 0.0%
CalendarAppWidgetProvider (Calendar): 2 s (2 s) Count:70 0.0%
NetworkLocationCacheUpdater (com.google.android.apps.maps.Maps): 1 s (1 s) Count:1 0.0%
PreventScreenOn Partial (Android System): 1 s (1 s) Count:355 0.0%
SyncManagerHandleSyncAlarm (Android System): 1 s (1 s) Count:483 0.0%
Proximity Partial (Android System): 1 s (1 s) Count:30 0.0%
Event Log Handoff (Google Services): 1 s (1 s) Count:877 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 19 h 10 m 10 s (69010 s) Cnt:(c/wc/ec)6336/0/0 48.1%
"dhd_wake_lock" (): 1 h 23 m 50 s (5030 s) Cnt:(c/wc/ec)19077/937/19077 3.5%
"alarm_rtc" (): 29 m 4 s (1744 s) Cnt:(c/wc/ec)3435/0/396 1.2%
"alarm" (): 3 m 54 s (234 s) Cnt:(c/wc/ec)11754/1/0 0.2%
"dhd_wake_lock_link_event" (): 3 m 40 s (220 s) Cnt:(c/wc/ec)14/0/14 0.1%
"deleted_wake_locks" (): 3 m 1 s (181 s) Cnt:(c/wc/ec)19979/0/0 0.1%
"SMD_DATA5" (): 2 m 33 s (153 s) Cnt:(c/wc/ec)290/70/290 0.1%
"dhd_dpc_thread" (): 2 m 32 s (152 s) Cnt:(c/wc/ec)34524/0/0 0.1%
"SMD_DS" (): 2 m 9 s (129 s) Cnt:(c/wc/ec)509/17/509 0.1%
"radio-interface" (): 1 m 14 s (74 s) Cnt:(c/wc/ec)134/0/0 0.1%
"AudioHardwareOut" (): 19 s (19 s) Cnt:(c/wc/ec)14/0/0 0.0%
"audio_pcm" (): 19 s (19 s) Cnt:(c/wc/ec)14/0/0 0.0%
"audpp" (): 19 s (19 s) Cnt:(c/wc/ec)14/0/0 0.0%
"proximity" (): 17 s (17 s) Cnt:(c/wc/ec)24/0/24 0.0%
"rmt_storage" (): 9 s (9 s) Cnt:(c/wc/ec)16/0/0 0.0%
"qmi0" (): 7 s (7 s) Cnt:(c/wc/ec)16/0/16 0.0%
"SMD_RPCCALL" (): 6 s (6 s) Cnt:(c/wc/ec)32983/2724/0 0.0%
"ApmCommandThread" (): 2 s (2 s) Cnt:(c/wc/ec)46/0/0 0.0%
"vbus_present" (): 2 s (2 s) Cnt:(c/wc/ec)0/0/1 0.0%
"dhd_watchdog_thread" (): 1 s (1 s) Cnt:(c/wc/ec)24298/0/0 0.0%
"rpc-interface" (): 1 s (1 s) Cnt:(c/wc/ec)2556/0/0 0.0%
"rpc_reply" (): 1 s (1 s) Cnt:(c/wc/ec)2389/0/0 0.0%
"rpc_read" (): 1 s (1 s) Cnt:(c/wc/ec)23967/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)93/0/0 0.0%
"rpc_server" (): (0 s) Cnt:(c/wc/ec)112/0/0 0.0%
"rpc_reply" (): (0 s) Cnt:(c/wc/ec)107/0/0 0.0%
"rpc_read" (): (0 s) Cnt:(c/wc/ec)1489/0/0 0.0%
"port_list" (): (0 s) Cnt:(c/wc/ec)80313/0/0 0.0%
"gpio_input" (): (0 s) Cnt:(c/wc/ec)237/14/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)27203/0/0 0.0%
"event4-1348" (system, com.android.browser): (0 s) Cnt:(c/wc/ec)70/3/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
245.76 MHz (): 18 h 32 m 13 s 46.5%
368.64 MHz (): 4 m 41 s 0.2%
768 MHz (): 5 m 36 s 0.2%
1.02 GHz (): 1 h 33 m 16 s 3.9%
Deep Sleep (): 19 h 37 m 12 s 49.2%
==================
Reference overview
==================
Custom: Reference custom_ref created 1 m 50 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
Since charged: Reference since_charged_ref created 59 m 24 s (Wl: 0 elements; KWl: 26elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 7 elements; CPU: 5 elements)
Since screen off: Reference since_screen_off created 1 d 16 h 49 m 41 s (Wl: 42 elements; KWl: 35elements; NetS: null; Alrm: null; Proc: 16 elements; Oth: 9 elements; CPU: 5 elements)
Since unplugged: Reference since_unplugged_ref created 59 m 23 s (Wl: 0 elements; KWl: 26elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 7 elements; CPU: 5 elements)
Since boot: Reference since_boot created 1 m 52 s (Wl: 0 elements; KWl: 5elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 0 elements; CPU: 5 elements)
What is the WIFI sleep policy of your device set to?
I hadn't changed the sleep policy, which has always been set to "never" and my battery still lasted 3+ days. Maintaining a Wi-Fi connection actually uses very little power, despite people mistakenly blaming it as a power drainer. It's always an app or setting causing undesired use of the Wi-Fi that can cause battery issues, not the Wi-Fi itself.
Anyway, problem solved. Using a data monitor I saw a lot of activity coming from the DHCP service. It was actually a problem with the DHCP lease time on my router, and the phone was trying to renew its IP address thousands of times a day. I fixed the lease time and now one battery charge lasts more than 3 days again.
I'm not certain if it helps, but I use DroidWall to prevent most of the apps from accessing the internet. You can customize which apps you want to give access to Wifi and/or Data.
It should help your battery a bit.
Hi,
I have unrooted stock I9500.
I see that something keeps waking my phone (Android OS getting 40% when idle).
I used to have battery life of 2 days waiting and 3 hours of screen.
Now I worse battery life. about 2% per hour.
Will you please help me?
here's my bbs
===================
General Information
===================
BetterBatteryStats version: 1.14.0.0
Creation Date: 2013-11-28 08:43:10
Statistic Type: Unplugged to Current
Since 1 d 10 h 42 m 45 s
VERSION.RELEASE: 4.2.2
BRAND: samsung
DEVICE: ja3g
MANUFACTURER: samsung
MODEL: GT-I9500
OS.VERSION: 3.4.5-1083225
BOOTLOADER: I9500XXUBMG9
HARDWARE: universal5410
FINGERPRINT: samsung/ja3gxx/ja3g:4.2.2/JDQ39/I9500XXUBMG9:user/release-keys
ID: JDQ39
TAGS: release-keys
USER: se.infra
PRODUCT: ja3gxx
RADIO: I9500JKUBMG9
Rooted: false
============
Battery Info
============
Level lost [%]: Bat.: -52% (100% to 48%) [1.5%/h]
Voltage lost [mV]: (4288-3713) [16.6%/h]
===========
Other Usage
===========
Deep Sleep (): 1 d 7 h 9 m 49 s (112189 s) Ratio: 89.8%
Awake (): 3 h 32 m 55 s (12775 s) Ratio: 10.2%
Screen On (): 23 m 8 s (1388 s) Ratio: 1.1%
Phone On (): 8 s (8 s) Ratio: 0.0%
Good Signal (): 44 s (44 s) Ratio: 0.0%
Screen dark (): 21 m 18 s (1278 s) Ratio: 1.0%
Screen dimmed (): 55 s (55 s) Ratio: 0.0%
Screen bright (): 54 s (54 s) Ratio: 0.0%
=========
Wakelocks
=========
NlpCollectorWakeLock (Google Services): 5 m 44 s (344 s) Count:1079 0.3%
AlarmManager (מערכת Android): 5 m 26 s (326 s) Count:3150 0.3%
*sync*_gmail-ls_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.gm.Gmail): 4 m 51 s (291 s) Count:200 0.2%
AudioOut_2 (1013): 4 m 41 s (281 s) Count:68 0.2%
fullsync (com.whatsapp.WhatsApp): 3 m 12 s (192 s) Count:64 0.2%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.apps.plus.Google+): 2 m 37 s (157 s) Count:59 0.1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 2 m 1 s (121 s) Count:90 0.1%
ActivityManager-Launch (מערכת Android): 1 m 40 s (100 s) Count:415 0.1%
MAIL_SERVICE (com.android.exchange.שירותי Exchange): 1 m 40 s (100 s) Count:154 0.1%
Icing (Google Services): 1 m 15 s (75 s) Count:852 0.1%
MediaScannerService (מדיה): 1 m 2 s (62 s) Count:2 0.0%
FbClientConnManager (com.facebook.katana.Facebook): 38 s (38 s) Count:28 0.0%
RILJ (טלפון): 23 s (23 s) Count:1673 0.0%
GTALK_CONN (Google Services): 19 s (19 s) Count:1805 0.0%
NlpWakeLock (Google Services): 17 s (17 s) Count:607 0.0%
sendinactive (com.whatsapp.WhatsApp): 17 s (17 s) Count:8 0.0%
AlarmManager (Google Services): 13 s (13 s) Count:2158 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 13 s (13 s) Count:723 0.0%
AlarmManager (com.viber.voip.Viber): 12 s (12 s) Count:211 0.0%
AlarmManager (com.android.exchange.שירותי Exchange): 11 s (11 s) Count:323 0.0%
AlarmManager (טלפון): 8 s (8 s) Count:330 0.0%
Event Log Service (Google Services): 7 s (7 s) Count:1309 0.0%
SyncLoopWakeLock (מערכת Android): 7 s (7 s) Count:3899 0.0%
AlarmReceiver (com.sec.android.app.clockpackage.שעון): 7 s (7 s) Count:3 0.0%
GOOGLE_C2DM (Google Services): 6 s (6 s) Count:1239 0.0%
show keyguard (מערכת Android): 6 s (6 s) Count:51 0.0%
SNS (com.sec.android.app.sns3.SNS): 5 s (5 s) Count:2 0.0%
GSM (טלפון): 5 s (5 s) Count:332 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 5 s (5 s) Count:2 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 4 s (4 s) Count:5 0.0%
backupdb (com.whatsapp.WhatsApp): 4 s (4 s) Count:10 0.0%
AlarmManager (com.facebook.katana.Facebook): 3 s (3 s) Count:92 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 3 s (3 s) Count:17 0.0%
SyncManagerHandleSyncAlarm (מערכת Android): 3 s (3 s) Count:561 0.0%
NetworkStats (מערכת Android): 2 s (2 s) Count:124 0.0%
NetworkLocationLocator (Google Services): 2 s (2 s) Count:858 0.0%
AlarmManager (flipboard.app.Flipboard): 2 s (2 s) Count:3 0.0%
AlarmManager (com.whatsapp.WhatsApp): 2 s (2 s) Count:61 0.0%
AlarmManager (com.sec.esdk.elm.ELM Agent): 2 s (2 s) Count:5 0.0%
*sync*_com.google.android.location.reporting_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 2 s (2 s) Count:610 0.0%
mResetWakelock (מערכת Android): 2 s (2 s) Count:10 0.0%
wake:com.sofascore.android/.GCMIntentService (com.sofascore.android.SofaScore): 2 s (2 s) Count:39 0.0%
RingtonePlayer (com.android.systemui.ממשק המערכת): 2 s (2 s) Count:36 0.0%
*sync*_subscribedfeeds_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 1 s (1 s) Count:2161 0.0%
ActivityManager-Sleep (מערכת Android): 1 s (1 s) Count:3182 0.0%
SamsungPhoneWindowManager.mBroadcastWakeLock (מערכת Android): 1 s (1 s) Count:423 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.syncadapters.calendar.סינכרון 'יומן Google'): 1 s (1 s) Count:2 0.0%
GCM_LIB (Google Services): 1 s (1 s) Count:718 0.0%
AlarmManager (com.google.android.apps.plus.Google+): 1 s (1 s) Count:101 0.0%
TAG (טלפון): 1 s (1 s) Count:333 0.0%
AlarmManager (com.sec.chaton.ChatON): 1 s (1 s) Count:5 0.0%
GpsLocationProvider (מערכת Android): 1 s (1 s) Count:568 0.0%
AlarmManager (com.sec.android.app.shealth.S Health): 1 s (1 s) Count:2 0.0%
com.coolots.chaton.lock.noncerefresh (מערכת Android): 1 s (1 s) Count:417 0.0%
*sync*_com.sec.android.app.sbrowser.tabs_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 1 s (1 s) Count:3 0.0%
com.coolots.chaton.lock.startlogin (מערכת Android): 1 s (1 s) Count:3189 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
l2_hsic (): 1 h 59 m 43 s (7183 s) Cntc/wc/ec)5666/563/5666 5.7%
radio-interface (): 53 m 47 s (3227 s) Cntc/wc/ec)3239/45/0 2.6%
PowerManagerService (): 33 m 39 s (2019 s) Cntc/wc/ec)4582/198/0 1.6%
umts_ipc0 (): 31 m 56 s (1916 s) Cntc/wc/ec)3727/198/3727 1.5%
rpm_hsic (): 25 m 19 s (1519 s) Cntc/wc/ec)5711/279/0 1.2%
rmnet0 (): 18 m 33 s (1113 s) Cntc/wc/ec)1314/372/1314 0.9%
alarm (): 9 m 18 s (558 s) Cntc/wc/ec)3413/200/0 0.4%
sec-battery-monitor (): 6 m 5 s (365 s) Cntc/wc/ec)4419/136/0 0.3%
alarmtimer (): 4 m 19 s (259 s) Cntc/wc/ec)131/131/131 0.2%
battery (): 1 m 46 s (106 s) Cntc/wc/ec)4419/136/0 0.1%
event11-2940 (): 16 s (16 s) Cntc/wc/ec)302/24/0 0.0%
ssp_sensorhub_wake_lock (): 15 s (15 s) Cntc/wc/ec)59/7/60 0.0%
KeyEvents (): 3 s (3 s) Cntc/wc/ec)16500/1043/0 0.0%
mmc2_detect (): 2 s (2 s) Cntc/wc/ec)4531/131/0 0.0%
mmc0_detect (): 2 s (2 s) Cntc/wc/ec)4531/131/0 0.0%
sec-battery-vbus (): 1 s (1 s) Cntc/wc/ec)0/0/1 0.0%
vib_present (): (0 s) Cntc/wc/ec)42/1/0 0.0%
autosleep (): (0 s) Cntc/wc/ec)72/4/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.6 GHz (): 1 m 22 s 0.1%
1.5 GHz (): 4 s 0.0%
1.4 GHz (): 4 s 0.0%
1.3 GHz (): 10 s 0.0%
1.2 GHz (): 2 m 31 s 0.1%
1.1 GHz (): 10 s 0.0%
1 GHz (): 24 s 0.0%
900 MHz (): 19 s 0.0%
800 MHz (): 1 m 15 s 0.1%
600 MHz (): 26 m 34 s 1.3%
550 MHz (): 1 m 4 s 0.1%
500 MHz (): 1 m 3 s 0.1%
450 MHz (): 1 m 3 s 0.1%
400 MHz (): 1 m 7 s 0.1%
350 MHz (): 54 s 0.0%
300 MHz (): 1 h 1 m 14 s 2.9%
250 MHz (): 1 h 53 m 30 s 5.4%
Deep Sleep (): 1 d 7 h 9 m 49 s 89.8%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 45 s (Wl: 0 elements; KWl: 10elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 0 elements; CPU: 7 elements)
ref_unplugged: Reference ref_unplugged created 3 h 58 m 23 s (Wl: 0 elements; KWl: 20elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 4 elements; CPU: 18 elements)
ref_charged: Reference ref_charged created 3 h 58 m 23 s (Wl: 0 elements; KWl: 20elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 4 elements; CPU: 18 elements)
ref_current: Reference ref_current created 1 d 14 h 41 m 8 s (Wl: 56 elements; KWl: 19elements; NetS: null; Alrm: null; Proc: 95 elements; Oth: 8 elements; CPU: 18 elements)
Thank you.
try to calibrate your battery
is it swelled ?
my friends battery also showed such problem when it swelled in size he changed it and everything is fine now
aditya rathee said:
try to calibrate your battery
is it swelled ?
my friends battery also showed such problem when it swelled in size he changed it and everything is fine now
Click to expand...
Click to collapse
It doesn't look swelled.
it's seems that something keeps waking the phone.
just charged 2 hours ago and now it has 93%. when I enter the battery I see under "Wake" alot of stripes.
please help?
Turn off location settings
Me Gusta!
Turn off Google Now if enabled, turn off location in the Google settings app, go into WiFi settings and turn off always scan even if WiFi off along those lines it's a Google thing. All these may help. Reduce any widgets or apps that rely on location such as weather apps.
Sent from my GT-I9505 using Tapatalk
nikzDHD said:
Turn off Google Now if enabled, turn off location in the Google settings app, go into WiFi settings and turn off always scan even if WiFi off along those lines it's a Google thing. All these may help. Reduce any widgets or apps that rely on location such as weather apps.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I've noticed that I have alot of wakelocks from Exchange services.
I thinks that's hotmail sync.
I configured it to sync only manually but still even if I don't launch the mail app I can see almost 200 wakelocks from this process.
Why is this happenning?
TheBenjamin said:
I've noticed that I have alot of wakelocks from Exchange services.
I thinks that's hotmail sync.
I configured it to sync only manually but still even if I don't launch the mail app I can see almost 200 wakelocks from this process.
Why is this happenning?
Click to expand...
Click to collapse
As nikzDHD said, " Turn off Google Now if enabled, turn off location in the Google settings app, go into WiFi settings and turn off always scan even if WiFi off along those lines it's a Google thing"
It is something about Google Services.
About batery stats, thats ok, but sometimes we can see better the problem by watching the battery graphs in Android settings. Upload some screenshots for both battery graph screens.
jaswinky said:
As nikzDHD said, " Turn off Google Now if enabled, turn off location in the Google settings app, go into WiFi settings and turn off always scan even if WiFi off along those lines it's a Google thing"
It is something about Google Services.
About batery stats, thats ok, but sometimes we can see better the problem by watching the battery graphs in Android settings. Upload some screenshots for both battery graph screens.
Click to expand...
Click to collapse
So you're saying that Exchange services is something of Google?
TheBenjamin said:
So you're saying that Exchange services is something of Google?
Click to expand...
Click to collapse
No, I mean your main problem is something in Google services. Exchange is not very different to others I have seen.
I assume you have tried our suggestions about turn off all about Google locations, if it didn't work, I am really sure that if you update to last Android 4.3 it will be fixed.
Enviado desde mi GT-I9500 usando Tapatalk 2
jaswinky said:
No, I mean your main problem is something in Google services. Exchange is not very different to others I have seen.
I assume you have tried our suggestions about turn off all about Google locations, if it didn't work, I am really sure that if you update to last Android 4.3 it will be fixed.
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
I'm trying to figure out why there is a 400+ wakelocks from exchange services when I configured it on manual sync only.
TheBenjamin said:
I'm trying to figure out why there is a 400+ wakelocks from exchange services when I configured it on manual sync only.
Click to expand...
Click to collapse
There is no direct relation between syncs and wakelocks. Most of wakelocks are caused by other processes from the app.
Enviado desde mi GT-I9500 usando Tapatalk 2
TheBenjamin said:
I'm trying to figure out why there is a 400+ wakelocks from exchange services when I configured it on manual sync only.
Click to expand...
Click to collapse
Hi.
Make sure in wifi/advanced, scanning always available in unchecked.
In Settings/MyDevice/Accessibility, notification reminder is unchecked.
Open Google Settings app, go to Android Device Manager and unchecked "Remotely locate this device".
Anyways, u might want to refer here: http://forum.xda-developers.com/showthread.php?t=2532210
There may be 3rd party apps u had installed that's making the Android OS to wake.
Cheers.
Hello. I have this terrible wakelock. I searched the web and didn't find anything. I'm really tired of these wakelocks
Version MK2
It won't let my phone to go to deep sleep. my wifi was off all the time. if I turn it on other wakelocks happen too
Actually, Most of the times I have lots of kernel wakelocks. and Android OS battery drain
Another wakelocks are sec-battery-monitor and wlan_rx_wake when I turn on wifi.
Hope Samsung fix all of these terrible wakelocks...
But anyway... Does anyone know what is causing this wakelock?
No one knows? It's the only thing that won't let my phone to go to deep sleep.
I think it's related to bluetooth maybe. But it's off all the time.
Anyone can help me?
Sent from my SM-N900 using Tapatalk
Same here.
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2013-12-23 07:39:12
Statistic Type: Unplugged to Current
Since 7 h 56 m 25 s
VERSION.RELEASE: 4.3
BRAND: samsung
DEVICE: ha3g
MANUFACTURER: samsung
MODEL: SM-N900
OS.VERSION: 3.4.39-2217357
BOOTLOADER: N900XXUCMK2
HARDWARE: universal5420
FINGERPRINT: samsung/ha3gxx/ha3g:4.3/JSS15J/N900XXUCMK2:user/release-keys
ID: JSS15J
TAGS: release-keys
USER: dpi
PRODUCT: ha3gxx
RADIO: N900XXUCMK1
Rooted: false
============
Battery Info
============
Level lost [%]: Bat.: -20% (100% to 80%) [2.5%/h]
Voltage lost [mV]: (4317-4017) [37.8%/h]
===========
Other Usage
===========
Awake (): 7 h 56 m 25 s (28585 s) Ratio: 100.0%
Screen On (): 47 m 5 s (2825 s) Ratio: 9.9%
Wifi On (): 7 h 56 m 25 s (28585 s) Ratio: 100.0%
Wifi Running (): 2 h 50 m 14 s (10214 s) Ratio: 35.7%
Screen dark (): 40 m 55 s (2455 s) Ratio: 8.6%
Screen medium (): 6 m 9 s (369 s) Ratio: 0.6%
=========
Wakelocks
=========
AudioOut_F6 (1013): 4 m 54 s (294 s) Count:4 1.1%
android.media.MediaPlayer (com.sec.android.app.music.Music): 4 m 50 s (290 s) Count:6 1.1%
AudioOut_2 (1013): 2 m 21 s (141 s) Count:12 0.5%
ConnectivityService (Android System): 2 m 7 s (127 s) Count:1125 0.5%
FbClientConnManager (com.facebook.katana.Facebook): 1 m 56 s (116 s) Count:81 0.5%
TimaService (Android System): 1 m 26 s (86 s) Count:98 0.3%
AlarmManager (com.devexpert.weather.Android Weather): 1 m 10 s (70 s) Count:476 0.3%
NlpWakeLock (Google Services): 1 m 10 s (70 s) Count:65 0.3%
ActivityManager-Launch (Android System): 51 s (51 s) Count:403 0.2%
AlarmManager (Android System): 42 s (42 s) Count:1120 0.2%
*sync*_com.android.contacts_Account {name=a0edf64bcb96cc80c74f8b215dc4ded0, type=com.facebook.auth.login} (com.facebook.katana.Facebook): 31 s (31 s) Count:3 0.1%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 26 s (26 s) Count:6 0.1%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 16 s (16 s) Count:12 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 16 s (16 s) Count:6 0.1%
RILJ (Phone): 15 s (15 s) Count:457 0.1%
WifiStateMachine (Android System): 14 s (14 s) Count:523 0.1%
*sync*_gmail-ls_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.gm.Gmail): 10 s (10 s) Count:13 0.0%
*sync*_com.android.calendar_Account {name=0c074206062eebb0a95994421870ecb0, type=com.sec.android.app.sns3.facebook} (com.sec.android.app.sns3.SNS): 10 s (10 s) Count:3 0.0%
wakeLock (Android System): 9 s (9 s) Count:121 0.0%
*sync*_com.samsung.android.SmartClip_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (com.samsung.android.app.pinboard.Scrapbook): 7 s (7 s) Count:3 0.0%
*sync*_com.google.android.gms.people_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 7 s (7 s) Count:415 0.0%
*sync*_com.sec.android.app.sbrowser_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 6 s (6 s) Count:15 0.0%
GCM_CONN_ALARM (Google Services): 5 s (5 s) Count:171 0.0%
Icing (Google Services): 5 s (5 s) Count:514 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 5 s (5 s) Count:18 0.0%
NlpCollectorWakeLock (Google Services): 5 s (5 s) Count:556 0.0%
NetworkLocationLocator (Google Services): 5 s (5 s) Count:517 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.linkedin.android} (com.linkedin.android.LinkedIn): 5 s (5 s) Count:3 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 4 s (4 s) Count:177 0.0%
AlarmManager (com.facebook.katana.Facebook): 4 s (4 s) Count:361 0.0%
NetworkStats (Android System): 4 s (4 s) Count:225 0.0%
SNS (com.sec.android.app.sns3.SNS): 4 s (4 s) Count:12 0.0%
*sync*_com.google.android.music.MusicContent_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.music.Google Play Music): 4 s (4 s) Count:20 0.0%
AlarmManager (Google Services): 3 s (3 s) Count:412 0.0%
*sync*_subscribedfeeds_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 3 s (3 s) Count:636 0.0%
*sync*_com.anydo.provider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.anydo.account} (Any.DO): 2 s (2 s) Count:19 0.0%
SyncLoopWakeLock (Android System): 2 s (2 s) Count:1389 0.0%
E (net.dinglisch.android.taskerm.Tasker): 2 s (2 s) Count:111 0.0%
fullsync (com.whatsapp.WhatsApp): 2 s (2 s) Count:39 0.0%
*sync*_com.evernote.evernoteprovider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.evernote} (com.evernote.Evernote): 2 s (2 s) Count:5 0.0%
M (net.dinglisch.android.taskerm.Tasker): 2 s (2 s) Count:99 0.0%
com.google.android.music.leanback.AutoCacheSchedulingService (com.google.android.music.Google Play Music): 2 s (2 s) Count:17 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 2 s (2 s) Count:4 0.0%
SyncService (com.evernote.Evernote): 2 s (2 s) Count:2 0.0%
DHCP (Android System): 1 s (1 s) Count:453 0.0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar storage): 1 s (1 s) Count:34 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:583 0.0%
*sync*_com.google.android.gms.games.background_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 1 s (1 s) Count:3 0.0%
*sync*_com.google.android.location.reporting_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 1 s (1 s) Count:93 0.0%
show keyguard (Android System): 1 s (1 s) Count:126 0.0%
ConnectMQTT (com.nuance.swype.dtc.Swype + Dragon): 1 s (1 s) Count:33 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 1 s (1 s) Count:4 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:455 0.0%
RILS (com.sec.phone.com.sec.phone): 1 s (1 s) Count:11 0.0%
AudioOut_F7 (1013): 1 s (1 s) Count:14 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
BT_bt_wake (): 7 h 9 m (25740 s) Cntc/wc/ec)6/0/6 -387.9%
PowerManagerService.WakeLocks (): 17 m 34 s (1054 s) Cntc/wc/ec)2411/0/0 3.7%
l2_hsic (): 9 m 17 s (557 s) Cntc/wc/ec)1163/0/1163 2.0%
bluetooth_timer (): 7 m 21 s (441 s) Cntc/wc/ec)12/0/0 1.5%
umts_ipc0 (): 5 m 57 s (357 s) Cntc/wc/ec)1070/0/1070 1.3%
ril-fd (): 5 m 9 s (309 s) Cntc/wc/ec)23/0/0 1.1%
radio-interface (): 3 m 58 s (238 s) Cntc/wc/ec)342/0/0 0.8%
rmnet0 (): 2 m 43 s (163 s) Cntc/wc/ec)123/0/123 0.6%
wlan_rx_wake (): 2 m 37 s (157 s) Cntc/wc/ec)813/0/814 0.6%
wlan_ctrl_wake (): 1 m 41 s (101 s) Cntc/wc/ec)156/0/157 0.4%
wlan_wd_wake (): 56 s (56 s) Cntc/wc/ec)4838/0/0 0.2%
rpm_hsic (): 55 s (55 s) Cntc/wc/ec)1176/0/0 0.2%
alarm (): 22 s (22 s) Cntc/wc/ec)1790/0/0 0.1%
wlan_wake (): 20 s (20 s) Cntc/wc/ec)34092/0/0 0.1%
sec-battery-monitor (): 20 s (20 s) Cntc/wc/ec)952/0/0 0.1%
LightsService (): 16 s (16 s) Cntc/wc/ec)38/0/0 0.1%
bcm2079x_wake_lock_timeout (): 10 s (10 s) Cntc/wc/ec)12/0/12 0.0%
AudioOutLock (): 7 s (7 s) Cntc/wc/ec)5/0/0 0.0%
battery (): 6 s (6 s) Cntc/wc/ec)952/0/0 0.0%
PowerManagerService.Broadcasts (): 2 s (2 s) Cntc/wc/ec)18/0/0 0.0%
PowerManagerService.Display (): (0 s) Cntc/wc/ec)9/0/0 0.0%
bcm2079x_wake_lock (): (0 s) Cntc/wc/ec)13/0/0 0.0%
KeyEvents (): (0 s) Cntc/wc/ec)65473/0/0 0.0%
ApmCommand (): (0 s) Cntc/wc/ec)64/0/0 0.0%
event19-2744 (): (0 s) Cntc/wc/ec)118/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.9 GHz (): 3 m 50 s 0.8%
1.8 GHz (): 1 m 21 s 0.3%
1.7 GHz (): 43 s 0.2%
1.6 GHz (): 1 m 26 s 0.3%
1.5 GHz (): 58 s 0.2%
1.4 GHz (): 21 s 0.1%
1.3 GHz (): 33 s 0.1%
1.2 GHz (): 54 s 0.2%
1.1 GHz (): 2 m 3 s 0.4%
1 GHz (): 1 m 19 s 0.3%
900 MHz (): 1 m 30 s 0.3%
800 MHz (): 5 m 46 s 1.2%
650 MHz (): 5 m 8 s 1.1%
600 MHz (): 15 m 45 s 3.3%
550 MHz (): 25 s 0.1%
500 MHz (): 51 s 0.2%
450 MHz (): 43 s 0.2%
400 MHz (): 2 m 43 s 0.6%
350 MHz (): 5 m 31 s 1.2%
300 MHz (): 2 m 36 s 0.5%
250 MHz (): 7 h 1 m 49 s 88.5%
Deep Sleep (): 0.0%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 40 s (Wl: 7 elements; KWl: 9elements; NetS: null; Alrm: null; Proc: 9 elements; Oth: 3 elements; CPU: 1 elements)
ref_unplugged: Reference ref_unplugged created 9 h 47 m 1 s (Wl: 0 elements; KWl: 39elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 22 elements)
ref_charged: Reference ref_charged created 9 h 47 m 1 s (Wl: 0 elements; KWl: 39elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 22 elements)
ref_current: Reference ref_current created 17 h 43 m 27 s (Wl: 55 elements; KWl: 39elements; NetS: null; Alrm: null; Proc: 89 elements; Oth: 7 elements; CPU: 22 elements)
Same here
My Note 3 is just a few days old. It was fine till now, with no funny wakelocks. But all of a sudden, it seeing the same BT_bt_wake activity today. It's draining like 3% every hour.
contactsunny said:
My Note 3 is just a few days old. It was fine till now, with no funny wakelocks. But all of a sudden, it seeing the same BT_bt_wake activity today. It's draining like 3% every hour.
Click to expand...
Click to collapse
My guess is that it is Bluetooth-related, and it should go away if you turn-off Bluetooth (for instance using the quick toggles), so this should be your first test.
If that is correct but you still need to use your Bluetooth-related devices then the next step is to see which device from your paired devices creates problems - my guess is that Bluetooth v4 devices would be fine, but maybe older Bluetooth devices are not handled so well in hardware and as a result keep a wakelock in software.
The problem might also be from a device that is not even paired with your Note 3 but is active around you and keeps sending (discovery?) packets around - in that case I really am curious what could be done (other than trying to turn-off that device).
http://forum.xda-developers.com/showthread.php?t=2473748
Sent from my SM-N9005 using XDA Premium 4 mobile app
xclub_101 said:
My guess is that it is Bluetooth-related, and it should go away if you turn-off Bluetooth (for instance using the quick toggles), so this should be your first test.
If that is correct but you still need to use your Bluetooth-related devices then the next step is to see which device from your paired devices creates problems - my guess is that Bluetooth v4 devices would be fine, but maybe older Bluetooth devices are not handled so well in hardware and as a result keep a wakelock in software.
The problem might also be from a device that is not even paired with your Note 3 but is active around you and keeps sending (discovery?) packets around - in that case I really am curious what could be done (other than trying to turn-off that device).
Click to expand...
Click to collapse
I just did a short test:
activated BT for 10 seconds, didn't connect anything to it.
deactivated BT.
left the device for an hour.
bt_bt_wakelock was stuck
sekely said:
I just did a short test:
activated BT for 10 seconds, didn't connect anything to it.
deactivated BT.
left the device for an hour.
bt_bt_wakelock was stuck
Click to expand...
Click to collapse
That is very interesting (and a little worrying, since it means that turning it off does not solve the problem, at least not immediately) - how many devices do you have in your list of paired devices? And how many other devices do you see around you?
I would assume that restarting the phone would fix things, but that is a really messy workaround.
Same stuff w. my SM-N900
P30SiNa said:
No one knows? It's the only thing that won't let my phone to go to deep sleep.
I think it's related to bluetooth maybe. But it's off all the time.
Anyone can help me?
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Have same **** w. my SM-N900 - afther first on/off bluetooth phone does not go to "deep sleep" if I switch WiFi on. Tried wipe out / safe mode etc - does not help. Looks like either SW bug or something wrong w. hardware (unlikely). The only thing helps for a while - to swithch bluethooth on and off once again, then phone goes to bed till next WiFi on/off. Then you need to on-off your bluetooth once again - and os in the loop.
And yes - bt_bt_wake is whown by BBS as main system wakelock.
any ideas how to shoot this bt_bt_wake issue?... Probably buy IPas mini?.. but it does not have awesome stylus...
make Factory reset and try
Sent from my SM-N900 using xda app-developers app
Already tries, as written above. Did not help. Other ideas?..
xclub_101 said:
That is very interesting (and a little worrying, since it means that turning it off does not solve the problem, at least not immediately) - how many devices do you have in your list of paired devices? And how many other devices do you see around you?
I would assume that restarting the phone would fix things, but that is a really messy workaround.
Click to expand...
Click to collapse
I have 3 devices paired (headphone, earphone, keyboard).
regarding to other devices @ the near surrounding - not related. the issue was reproduced in different environments.
restarting the phone solving the issue but I don't think that this is an appropriate solution.
I found an old android code from 2011 that takes the bt_bt_wake. I couldn't find any release.
since I haven't seen much complain about bt_bt_wake my best guess is - rare system flow which cause an internal exception, which doesn't release the lock. but it's just a shot in the dark, I hate C code.
BT is the obvious culprit
xclub_101 said:
My guess is that it is Bluetooth-related, and it should go away if you turn-off Bluetooth (for instance using the quick toggles), so this should be your first test.
If that is correct but you still need to use your Bluetooth-related devices then the next step is to see which device from your paired devices creates problems - my guess is that Bluetooth v4 devices would be fine, but maybe older Bluetooth devices are not handled so well in hardware and as a result keep a wakelock in software.
The problem might also be from a device that is not even paired with your Note 3 but is active around you and keeps sending (discovery?) packets around - in that case I really am curious what could be done (other than trying to turn-off that device).
Click to expand...
Click to collapse
Sorry, I hadn't seen your reply. And a simple restart fixed the issue. This only occurs when I switch on the BT. And then I'll have to restart the device to stop this from occurring again. Its a bit frustrating. If this is fixed, i easily get 24 hours of more with at least 3 hours of screen on, 1 hour of GPS, 1 hour of gaming, and 1 hour of music. That's a good backup for me.
bt_bt_wake wakelock issue has gone after Kitkat upgrade. Confirmed also by other fellows. But still there are some other wakelocks like sec-battery-stat which drain battery fadt if WiFi is on.
Note 3 wakelock
Follow this:
0)I use Cpu Spy app to determine wakelock & Deep Sleep Problems
1) go to Wifi settings & turn on Wifi
2) go to Advanced
3)Set "Keep Wi-Fi on during sleep" to "Never"
4)Wait some seconds (I used to turn off screen, wait for some seconds)
5) turn off wifi
if you want to use wifi, turn on wifi and set "keep Wi-Fi..." to "Always" or not.
Notice that befor turning of Wifi, set it to "Never"
notice that when your phone is connected to charger T before disconnecting charger, unlock phone and wait for a few seconds while screen is on, then disconnect charger,
MTU79 said:
bt_bt_wake wakelock issue has gone after Kitkat upgrade. Confirmed also by other fellows. But still there are some other wakelocks like sec-battery-stat which drain battery fadt if WiFi is on.
Click to expand...
Click to collapse
same here, I'll keep following and update if anything changes.
now I have the l2_hsic issue. it's like hydra - you kill one wakelock issue, 2 pops instead
Today i met this sec-battery-monitor wakelock which is huge problem for going into a deepsleep and drains the battery a lot. Did the postera under these thread resolve the issue?
PS I tried to use a chinese powerbank yesterday and also charged the phone via chinesee car plug today...
solution
I had wlan_wake and bt_bt_wake issue on v4.3. Clear the cache for the system (or all) of the applications for me is the solution!
I used SD Maid to clean.
hello
yesterday i bought the LG G2 .
tonight the battery went up from 40% to 30% ....
i think the battery doesnt good like what its need to be .
please check the BBS .
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2014-04-09 08:06:26
Statistic Type: Unplugged to Current
Since 1 d 2 m 16 s
VERSION.RELEASE: 4.2.2
BRAND: lge
DEVICE: g2
MANUFACTURER: LGE
MODEL: LG-D802
OS.VERSION: 3.4.0-perf-g1433746
BOOTLOADER: unknown
HARDWARE: g2
FINGERPRINT: lge/g2_open_ame/g2:4.2.2/JDQ39B/D80210a.1378380209:user/release-keys
ID: JDQ39B
TAGS: release-keys
USER: prasanth.kumar
PRODUCT: g2_open_ame
RADIO: M8974A-AAAANAZM-1.0.190036
Rooted: false
============
Battery Info
============
Level lost [%]: Bat.: -59% (90% to 31%) [2.5%/h]
Voltage lost [mV]: (4085-3767) [13.2%/h]
===========
Other Usage
===========
Deep Sleep (): 17 h 47 m 25 s (64045 s) Ratio: 74.0%
Awake (): 6 h 14 m 50 s (22490 s) Ratio: 26.0%
Screen On (): 2 h 35 m 23 s (9323 s) Ratio: 10.8%
Phone On (): 33 m 16 s (1996 s) Ratio: 1.2%
Wifi On (): 5 h 25 m 35 s (19535 s) Ratio: 22.6%
Wifi Running (): 5 h 25 m 32 s (19532 s) Ratio: 22.6%
No Data Connection (): 5 h 28 m 32 s (19712 s) Ratio: 22.8%
No or Unknown Signal (): 5 h 28 m 32 s (19712 s) Ratio: 22.8%
Poor Signal (): 3 m 36 s (216 s) Ratio: 0.1%
Good Signal (): 7 s (7 s) Ratio: 0.0%
Screen dark (): 42 m 37 s (2557 s) Ratio: 3.0%
Screen dimmed (): 4 m 30 s (270 s) Ratio: 0.3%
Screen medium (): 1 h 35 m 59 s (5759 s) Ratio: 6.7%
Screen light (): 10 m 16 s (616 s) Ratio: 0.4%
Screen bright (): 1 m 59 s (119 s) Ratio: 0.1%
=========
Wakelocks
=========
PhoneGlobals (טלפון): 20 m 54 s (1254 s) Count:1401 1.1%
AudioOut_2 (1013): 15 m 26 s (926 s) Count:459 1.1%
com.lge.camera.CameraApp (com.lge.camera.מצלמה): 9 m 21 s (561 s) Count:45 0.5%
WifiOffDelayIfNotUsed (מערכת Android): 7 m 36 s (456 s) Count:1306 0.5%
BlockBeforeSleep (מערכת Android): 7 m 16 s (436 s) Count:3900 0.5%
AudioOut_3 (1013): 5 m 54 s (354 s) Count:204 0.4%
ActivityManager-Launch (מערכת Android): 5 m 51 s (351 s) Count:1229 0.4%
RILJ (טלפון): 2 m 57 s (177 s) Count:31143 0.2%
GSM (טלפון): 2 m 56 s (176 s) Count:1362 0.1%
sendinactive (com.whatsapp.WhatsApp): 2 m 44 s (164 s) Count:261 0.2%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (שירותי Google Play): 2 m 41 s (161 s) Count:50 0.1%
AlarmManager (טלפון): 2 m 20 s (140 s) Count:24655 0.2%
DataTracker-FD (טלפון): 2 m 8 s (128 s) Count:12863 0.1%
AlarmManager (מערכת Android): 2 m 5 s (125 s) Count:5599 0.1%
Icing (שירותי Google Play): 1 m 3 s (63 s) Count:294 0.1%
show keyguard (מערכת Android): 58 s (58 s) Count:110 0.0%
*vibrator* (מערכת Android): 52 s (52 s) Count:3657 0.1%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=58c00fff9b1313c465c1cc8790ea7ba8, type=com.google} (com.google.android.apps.plus.Google+): 46 s (46 s) Count:234 0.0%
ActivityManager-Sleep (מערכת Android): 42 s (42 s) Count:5803 0.0%
AlarmManager (com.ayce.Playzone): 38 s (38 s) Count:1442 0.0%
DropboxCpuOnlyWakeLock (com.dropbox.android.Dropbox): 27 s (27 s) Count:5 0.0%
SyncLoopWakeLock (מערכת Android): 24 s (24 s) Count:6971 0.0%
AlarmManager (com.facebook.katana.Facebook): 23 s (23 s) Count:446 0.0%
SMSDispatcher (טלפון): 22 s (22 s) Count:1328 0.0%
StartingAlertService (com.android.mms.הודעות): 22 s (22 s) Count:422 0.0%
QcConnectivityService (מערכת Android): 18 s (18 s) Count:3697 0.0%
SCREEN_FROZEN (מערכת Android): 15 s (15 s) Count:1611 0.0%
CM_local (com.google.android.apps.plus.Google+): 13 s (13 s) Count:287 0.0%
com.lge.streamingplayer.StreamingPlayer (com.lge.streamingplayer.נגן סטרימינג): 12 s (12 s) Count:2 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 10 s (10 s) Count:16 0.0%
AlarmManager (שירותי Google Play): 9 s (9 s) Count:1403 0.0%
Checkin Service (שירותי Google Play): 6 s (6 s) Count:91 0.0%
AlarmManager (com.whatsapp.WhatsApp): 6 s (6 s) Count:220 0.0%
NetworkStats (מערכת Android): 6 s (6 s) Count:287 0.0%
DHCP (מערכת Android): 5 s (5 s) Count:1693 0.0%
GTALK_CONN (שירותי Google Play): 4 s (4 s) Count:1337 0.0%
GOOGLE_C2DM (שירותי Google Play): 4 s (4 s) Count:770 0.0%
NfcService:mRoutingWakeLock (com.android.nfc.NFC שירות): 3 s (3 s) Count:383 0.0%
*backup* (מערכת Android): 3 s (3 s) Count:3680 0.0%
Event Log Service (שירותי Google Play): 3 s (3 s) Count:719 0.0%
LocationManagerService (מערכת Android): 2 s (2 s) Count:519 0.0%
StartingAlertService (com.android.calendar.לוח שנה): 2 s (2 s) Count:82 0.0%
android.media.MediaPlayer (com.google.android.music.Google Play מוסיקה): 2 s (2 s) Count:150 0.0%
DownloadManager (מדיה): 2 s (2 s) Count:2 0.0%
WifiStateMachine (מערכת Android): 2 s (2 s) Count:3816 0.0%
*sync*_com.android.chrome_Account {name=58c00fff9b1313c465c1cc8790ea7ba8, type=com.google} (com.android.chrome.Chrome): 2 s (2 s) Count:74 0.0%
AlarmManager (com.google.android.talk.Hangouts): 2 s (2 s) Count:74 0.0%
QcrilMsgTunnelSocket (טלפון): 2 s (2 s) Count:757 0.0%
WifiSuspend (מערכת Android): 1 s (1 s) Count:1615 0.0%
com.google.android.music.playback.LocalDevicePlayback.mAsyncWakeLock (com.google.android.music.Google Play מוסיקה): 1 s (1 s) Count:89 0.0%
fingerprint_scanner_local (com.google.android.apps.plus.Google+): 1 s (1 s) Count:96 0.0%
UlrDispatchingService (שירותי Google Play): 1 s (1 s) Count:110 0.0%
Event Log Handoff (שירותי Google Play): 1 s (1 s) Count:1403 0.0%
RingtonePlayer (com.android.systemui.ממשק משתמש של המערכת): 1 s (1 s) Count:37 0.0%
AudioIn_2A9 (1013): 1 s (1 s) Count:485 0.0%
babel_rtcs (com.google.android.talk.Hangouts): 1 s (1 s) Count:55 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
mmc0_detect (): 1 h 7 m 3 s (4023 s) Cntc/wc/ec)7963/6069/7963 4.6%
alarm_rtc (): 1 h 2 m 3 s (3723 s) Cntc/wc/ec)6751/9972/46 4.3%
bam_dmux_wakelock (): 57 m 39 s (3459 s) Cntc/wc/ec)1629/637/0 4.0%
radio-interface (): 54 m 6 s (3246 s) Cntc/wc/ec)3619/3650/0 3.8%
PowerManagerService (): 36 m 1 s (2161 s) Cntc/wc/ec)15134/7566/0 2.5%
sns_async_ev_wakelock (): 8 m 13 s (493 s) Cntc/wc/ec)446/73/0 0.6%
alarm (): 6 m 46 s (406 s) Cntc/wc/ec)16401/7605/0 0.5%
smdcntl0 (): 2 m 35 s (155 s) Cntc/wc/ec)42010/14406/0 0.2%
PowerManagerService.Broadcasts (): 1 m 19 s (79 s) Cntc/wc/ec)399/57/0 0.1%
qpnp-vadc-d80f8400 (): 25 s (25 s) Cntc/wc/ec)9103/3292/0 0.0%
touch_irq (): 23 s (23 s) Cntc/wc/ec)167/29/150 0.0%
qcril (): 16 s (16 s) Cntc/wc/ec)14333/3138/0 0.0%
qmuxd_port_wl_0 (): 3 s (3 s) Cntc/wc/ec)47628/12321/0 0.0%
smdcntl1 (): 3 s (3 s) Cntc/wc/ec)3133/1344/0 0.0%
smsm_snapshot (): 2 s (2 s) Cntc/wc/ec)4648/1473/0 0.0%
power-supply (): 2 s (2 s) Cntc/wc/ec)257/103/0 -0.0%
[rmt_storage] msm_ipc_read00000 (): 1 s (1 s) Cntc/wc/ec)-151/-16/0 0.0%
KeyEvents (): (0 s) Cntc/wc/ec)83037/9365/0 0.0%
max17048_alert (): (0 s) Cntc/wc/ec)104/16/0 0.0%
rmt_storage_1088648472 (): (0 s) Cntc/wc/ec)9/0/0 0.0%
rmt_storage_1088648648 (): (0 s) Cntc/wc/ec)8/0/0 0.0%
qmuxd_port_wl_1 (): (0 s) Cntc/wc/ec)3135/1261/0 0.0%
qpnp-iadc-d80f8600 (): (0 s) Cntc/wc/ec)75/28/0 0.0%
ipc_rtr_q6_ipcrtr (): (0 s) Cntc/wc/ec)82352/8994/0 0.0%
[LBSSystemMonito] msm_ipc_read0 (): (0 s) Cntc/wc/ec)136/15/0 0.0%
[kworker/0:1] msm_ipc_read00000 (): (0 s) Cntc/wc/ec)410/47/0 0.0%
[atd] msm_ipc_read00000001:0000 (): (0 s) Cntc/wc/ec)-32/-1/0 0.0%
[time_daemon] msm_ipc_read00000 (): (0 s) Cntc/wc/ec)-32/-1/0 0.0%
[time_daemon] msm_ipc_read00000 (): (0 s) Cntc/wc/ec)-4/-1/0 0.0%
ipc_rtr_smd_ipcrtr (): (0 s) Cntc/wc/ec)1952/9/0 0.0%
event2-740 (): (0 s) Cntc/wc/ec)78/10/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
300 MHz (): 3 h 7 m 42 s 13.0%
422.4 MHz (): 8 m 59 s 0.6%
652.8 MHz (): 16 m 41 s 1.2%
729.6 MHz (): 1 m 24 s 0.1%
883.2 MHz (): 2 m 26 s 0.2%
960 MHz (): 1 h 49 m 42 s 7.6%
1.04 GHz (): 7 m 50 s 0.5%
1.19 GHz (): 3 m 41 s 0.3%
1.27 GHz (): 57 s 0.1%
1.5 GHz (): 2 m 15 s 0.2%
1.57 GHz (): 1 m 20 s 0.1%
1.73 GHz (): 2 m 32 s 0.2%
1.96 GHz (): 3 m 2 s 0.2%
2.27 GHz (): 26 m 13 s 1.8%
Deep Sleep (): 17 h 47 m 25 s 74.0%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 21 h 19 m 16 s (Wl: 24 elements; KWl: 83elements; NetS: null; Alrm: null; Proc: 83 elements; Oth: 10 elements; CPU: 15 elements)
ref_current: Reference ref_current created 1 d 21 h 21 m 33 s (Wl: 57 elements; KWl: 80elements; NetS: null; Alrm: null; Proc: 160 elements; Oth: 15 elements; CPU: 15 elements)
thanks very much !