[Q] S5 Active - Help with determing source of battery drain

[Q] S5 Active - Help with determing source of battery drain - AT&T Samsung Galaxy S 5

Hi Folks,
I'm hoping someone can point me in the right direction. As it stands now I have a (less than 14 day old) galaxy S5 active. It's been rooted and I'm running the stock rom (slightly modified for my taste) within a twrp rom slot (safestrap'd without tripping knox).
That said, I'm experiencing rediculous battery life, in the order of 5 to 6 hours from 100% charge to almost nothing (13% an hour or more). The phone is NOT heavily used, I read emails on it, make some calls, and that's about it. I'm not in a poor signal area (I have 4 bars of LTE).
Looking at wake lock detector output, there's nothing that jumps out to explain the massive battery drain. Standard battery app indicates 43% of the batter eaten up by the screen, which may or may not be correct.
The only real stand out here is better battery status + app indicates both wifi on, and wifi running at 100%.
Here's the output:
Code:
===================
General Information
===================
BetterBatteryStats version: 1.16.0.0
Creation Date: 2014-12-03 16:04:08
Statistic Type: Boot to Current
Since 6 h 37 m 55 s
VERSION.RELEASE: 4.4.2
BRAND: samsung
DEVICE: klteattactive
MANUFACTURER: samsung
MODEL: SAMSUNG-SM-G870A
OS.VERSION: 3.4.0-2304514
BOOTLOADER: G870AUCU1ANG3
HARDWARE: qcom
FINGERPRINT: samsung/klteattactive/klteattactive:4.4.2/KOT49H/G870AUCU1ANG3:user/release-keys
ID: KOT49H
TAGS: release-keys
USER: dpi
PRODUCT: klteattactive
RADIO: G870AUCU1ANG3
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -86% (99% to 13%) [13.0%/h]
Voltage lost [mV]: (4243-3661) [87.8%/h]
===========
Other Usage
===========
Deep Sleep (): 4 h 25 m 50 s (15950 s) Ratio: 66.4%
Awake (): 2 h 12 m 5 s (7925 s) Ratio: 33.2%
Screen On (): 1 h 15 m 8 s (4508 s) Ratio: 18.8%
Phone On (): 56 m 45 s (3405 s) Ratio: 14.2%
Wifi On (): 6 h 37 m 56 s (23876 s) Ratio: 100.0%
Wifi Running (): 6 h 37 m 56 s (23876 s) Ratio: 100.0%
No Data Connection (): 4 h 30 m 57 s (16257 s) Ratio: 68.1%
No or Unknown Signal (): 4 h 30 m 57 s (16257 s) Ratio: 68.1%
Screen dark (): 30 m 20 s (1820 s) Ratio: 7.6%
Screen dimmed (): 15 m 13 s (913 s) Ratio: 3.8%
Screen medium (): 21 m 31 s (1291 s) Ratio: 5.4%
Screen light (): 1 m 47 s (107 s) Ratio: 0.4%
Screen bright (): 6 m 15 s (375 s) Ratio: 1.6%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
NlpCollectorWakeLock (Google Play services): 11 m 41 s (701 s) Count:3029 2.9%
SyncEngineService (com.ninefolders.hd3.Nine): 7 m 53 s (473 s) Count:192 2.0%
AudioMix (1013): 3 m 8 s (188 s) Count:134 0.8%
wake:com.google.android.gms/.config.ConfigFetchService (Google Play services): 3 m 6 s (186 s) Count:2460 0.8%
AMP (com.jrtstudio.AnotherMusicPlayer.Rocket Player): 2 m 53 s (173 s) Count:5 0.7%
MediaScanner (com.jrtstudio.AnotherMusicPlayer.Rocket Player): 2 m 47 s (167 s) Count:3 0.7%
ProximitySensor (Phone): 2 m 20 s (140 s) Count:719 0.6%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 1 m 16 s (76 s) Count:47 0.3%
TimaService (Android System): 1 m 12 s (72 s) Count:26 0.3%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 m 7 s (67 s) Count:98 0.3%
ActivityManager-Launch (Android System): 1 m 4 s (64 s) Count:419 0.3%
*sync*/gmail-ls/com.google/eM_ADDR (com.google.android.gm.Gmail): 59 s (59 s) Count:45 0.2%
GsmConnection (Phone): 56 s (56 s) Count:705 0.2%
wake:com.google.android.gms/.udc.service.LoginAccountsChangedIntentService (Google Play services): 40 s (40 s) Count:1 0.2%
AlarmManager (Android System): 39 s (39 s) Count:1421 0.2%
MediaScannerService (Media): 34 s (34 s) Count:3 0.1%
RILJ1 (Phone): 31 s (31 s) Count:688 0.1%
Icing (Google Play services): 29 s (29 s) Count:2559 0.1%
AudioMix (com.jrtstudio.AnotherMusicPlayer.Rocket Player): 29 s (29 s) Count:13 0.1%
SyncScheduler (Google Play services): 14 s (14 s) Count:1260 0.1%
AudioMix (Phone): 14 s (14 s) Count:793 0.1%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 13 s (13 s) Count:12 0.1%
UlrDispatchingService (Google Play services): 12 s (12 s) Count:2457 0.1%
GCM_CONN_ALARM (Google Play services): 12 s (12 s) Count:1018 0.1%
diagnostics.client.Wakelock (Android System): 10 s (10 s) Count:706 0.0%
o.gG (com.keramidas.TitaniumBackup.Titanium Backup): 9 s (9 s) Count:7 0.0%
show keyguard (UID): 9 s (9 s) Count:35 0.0%
GCM_LIB (com.skype.raider.Skype): 8 s (8 s) Count:2 0.0%
NlpWakeLock (Google Play services): 8 s (8 s) Count:904 0.0%
*sync*/com.google.android.apps.docs/com.google/eM_ADDR (com.google.android.apps.docs.Drive): 7 s (7 s) Count:4 0.0%
*sync*/com.android.contacts/com.skype.contacts.sync/colin_faber (com.skype.raider.Skype): 7 s (7 s) Count:5 0.0%
SyncManager (com.google.android.apps.docs.Drive): 7 s (7 s) Count:6 0.0%
DownloadManager (com.android.vending.Google Play Store): 7 s (7 s) Count:2 0.0%
AudioMix (Android Core Apps): 6 s (6 s) Count:19 0.0%
*net_scheduler* (Google Play services): 5 s (5 s) Count:2200 0.0%
AlarmManager (imoblife.memorybooster.full.Memory Booster Full): 5 s (5 s) Count:79 0.0%
GsmInboundSmsHandler (Phone): 4 s (4 s) Count:69 0.0%
ActivityManager-Sleep (Android System): 4 s (4 s) Count:2000 0.0%
Checkin Service (Google Play services): 4 s (4 s) Count:2257 0.0%
SCREEN_FROZEN (Android System): 4 s (4 s) Count:726 0.0%
ConnectivityService (Android System): 4 s (4 s) Count:1459 0.0%
SyncLoopWakeLock (Android System): 3 s (3 s) Count:1954 0.0%
Config Service fetch (Google Play services): 3 s (3 s) Count:1128 0.0%
NetworkStats (Android System): 2 s (2 s) Count:148 0.0%
*sync*/com.android.calendar/com.google/eM_ADDR (com.google.android.syncadapters.calendar.Google Calendar Sync): 2 s (2 s) Count:20 0.0%
AudioMix (UID): 2 s (2 s) Count:49 0.0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar storage): 2 s (2 s) Count:77 0.0%
*sync*/com.sec.android.gallery3d.picasa.contentprovider/com.google/eM_ADDR (com.sec.android.gallery3d.Gallery): 2 s (2 s) Count:2 0.0%
StartingAlertService (com.android.calendar.Calendar): 2 s (2 s) Count:35 0.0%
DownloadManager (com.google.android.configupdater.ConfigUpdater): 1 s (1 s) Count:3 0.0%
*sync*/com.google.android.location.reporting/com.google/eM_ADDR (Google Play services): 1 s (1 s) Count:1119 0.0%
*net_scheduler* (com.google.android.youtube.YouTube): 1 s (1 s) Count:1 0.0%
DownloadManager (com.google.android.gm.Gmail): 1 s (1 s) Count:50 0.0%
LocationService (Android System): 1 s (1 s) Count:709 0.0%
AlarmManager (com.samsung.android.app.headlines.My Magazine): 1 s (1 s) Count:89 0.0%
SamsungPhoneWindowManager.mBroadcastWakeLock (Android System): 1 s (1 s) Count:424 0.0%
GOOGLE_C2DM (Google Play services): 1 s (1 s) Count:3017 0.0%
hangouts_rtcs (com.google.android.talk.Hangouts): 1 s (1 s) Count:35 0.0%
*sync*/com.google.android.gms.people/com.google/eM_ADDR (Google Play services): 1 s (1 s) Count:957 0.0%
AlarmManager (Google Play services): 1 s (1 s) Count:1253 0.0%
AlarmManager (com.android.providers.calendar.Calendar storage): 1 s (1 s) Count:44 0.0%
AudioMix (com.skype.raider.Skype): 1 s (1 s) Count:3 0.0%
GCM_CONN (Google Play services): 1 s (1 s) Count:3189 0.0%
Event Log Service (Google Play services): 1 s (1 s) Count:3087 0.0%
AlarmManager (com.google.android.talk.Hangouts): 1 s (1 s) Count:40 0.0%
SyncManagerHandleSyncAlarm (Android System): 1 s (1 s) Count:600 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
bluesleep (): 24 m 15 s (1455 s) Cnt:(c/wc/ec)6/0/6 6.1%
PowerManagerService.WakeLocks (): 18 m 36 s (1116 s) Cnt:(c/wc/ec)1795/70/0 4.6%
bam_dmux_wakelock (): 6 m 11 s (371 s) Cnt:(c/wc/ec)380/19/0 1.5%
event0-1121 (): 5 m 50 s (350 s) Cnt:(c/wc/ec)540/0/0 1.5%
alarm (): 3 m 50 s (230 s) Cnt:(c/wc/ec)1173/75/0 1.0%
wlan_rx_wake (): 2 m 13 s (133 s) Cnt:(c/wc/ec)2137/230/2137 0.6%
alarm_rtc (): 1 m 34 s (94 s) Cnt:(c/wc/ec)386/65/0 0.4%
wlan_wd_wake (): 1 m 33 s (93 s) Cnt:(c/wc/ec)6559/99/0 0.4%
wlan_ctrl_wake (): 1 m 5 s (65 s) Cnt:(c/wc/ec)184/20/184 0.3%
mmc2_detect (): 58 s (58 s) Cnt:(c/wc/ec)117/29/117 0.2%
wlan_wake (): 57 s (57 s) Cnt:(c/wc/ec)39065/177/0 0.2%
radio-interface (): 53 s (53 s) Cnt:(c/wc/ec)201/13/0 0.2%
resume_wakelock (): 50 s (50 s) Cnt:(c/wc/ec)537/0/537 0.2%
smdcntl0 (): 27 s (27 s) Cnt:(c/wc/ec)3757/58/0 0.1%
event2-1121 (): 25 s (25 s) Cnt:(c/wc/ec)101/8/0 0.1%
ssp_sensorhub_wake_lock (): 24 s (24 s) Cnt:(c/wc/ec)172/6/172 0.1%
PowerManagerService.Broadcasts (): 22 s (22 s) Cnt:(c/wc/ec)102/2/0 0.1%
LightsService (): 19 s (19 s) Cnt:(c/wc/ec)92/5/0 0.1%
msm_serial_hs_dma (): 13 s (13 s) Cnt:(c/wc/ec)10/0/0 0.1%
ssp_wake_lock (): 12 s (12 s) Cnt:(c/wc/ec)18/0/18 0.1%
ipc00000004_rmt_storage (): 11 s (11 s) Cnt:(c/wc/ec)43/0/0 0.0%
event15-1121 (): 9 s (9 s) Cnt:(c/wc/ec)923/41/0 0.0%
event16-1121 (): 8 s (8 s) Cnt:(c/wc/ec)589/37/0 0.0%
ipc00000025_system_server (): 5 s (5 s) Cnt:(c/wc/ec)755/161/0 0.0%
qpnp-vadc-ea510000 (): 5 s (5 s) Cnt:(c/wc/ec)5317/44/0 0.0%
sec_jack_det (): 5 s (5 s) Cnt:(c/wc/ec)3/0/3 0.0%
PowerManagerService.Display (): 4 s (4 s) Cnt:(c/wc/ec)53/1/0 0.0%
msm_serial_hs_rx (): 3 s (3 s) Cnt:(c/wc/ec)12/0/12 0.0%
sec-battery-monitor (): 3 s (3 s) Cnt:(c/wc/ec)799/37/0 0.0%
MBALBRIDGE (): 2 s (2 s) Cnt:(c/wc/ec)9/19/9 0.0%
MediaPlayerService_Decode (): 1 s (1 s) Cnt:(c/wc/ec)87/3/0 0.0%
KeyEvents (): (0 s) Cnt:(c/wc/ec)22580/498/0 0.0%
rmt_storage_-1200673048 (): (0 s) Cnt:(c/wc/ec)18/0/0 0.0%
rmt_storage_-1200672200 (): (0 s) Cnt:(c/wc/ec)19/0/0 0.0%
vib_present (): (0 s) Cnt:(c/wc/ec)466/6/0 0.0%
smsm_snapshot (): (0 s) Cnt:(c/wc/ec)685/34/0 0.0%
qmuxd_port_wl_0 (): (0 s) Cnt:(c/wc/ec)4078/38/0 0.0%
ipc0000002e_system_server (): (0 s) Cnt:(c/wc/ec)33/7/0 0.0%
ipc00000026_system_server (): (0 s) Cnt:(c/wc/ec)33/7/0 0.0%
ipc00000022_system_server (): (0 s) Cnt:(c/wc/ec)33/7/0 0.0%
ipc_rtr_smd_ipcrtr (): (0 s) Cnt:(c/wc/ec)1215/170/0 0.0%
ipc00000007_time_daemon (): (0 s) Cnt:(c/wc/ec)66/7/0 0.0%
power-supply (): (0 s) Cnt:(c/wc/ec)226/0/0 0.0%
ipc00000005_rmt_storage (): (0 s) Cnt:(c/wc/ec)65/7/0 0.0%
ipc00000003_rfs_access (): (0 s) Cnt:(c/wc/ec)62/7/0 0.0%
ipc0000001d_gsiff_daemon (): (0 s) Cnt:(c/wc/ec)53/7/0 0.0%
ipc00000017_time_daemon (): (0 s) Cnt:(c/wc/ec)50/7/0 0.0%
SMD_TTY_MBALBRIDGE_RA (): (0 s) Cnt:(c/wc/ec)136/19/0 0.0%
ApmAudio (): (0 s) Cnt:(c/wc/ec)748/10/0 0.0%
ipc00000016_time_daemon (): (0 s) Cnt:(c/wc/ec)83/2/0 0.0%
ipc0000000d_thermal-engine (): (0 s) Cnt:(c/wc/ec)69/7/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.gms (): Wakeups: 455 (1.1 / min.)
Alarms: 348, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION
Alarms: 9, Intent: {com.google.android.gms/com.google.android.gms.checkin.EventLogService$Receiver}
Alarms: 0, Intent: com.google.android.gms.location.fused.GPS_ALARM
Alarms: 7, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 19, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 61, Intent: {com.google.android.gms/com.google.android.gms.security.snet.SnetService}
Alarms: 3, Intent: com.google.android.location.reporting.ACTION_UPDATE_WORLD cmp={com.google.android.gms/com.google.android.location.reporting.service.DispatchingService}
Alarms: 1, Intent: {com.google.android.gms/com.google.android.gms.checkin.CheckinService$Receiver}
Alarms: 3, Intent: {com.google.android.gms/com.google.android.libraries.social.mediamonitor.MediaMonitorIntentService}
Alarms: 3, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_CAR_PARKING_DETECTOR
Alarms: 1, Intent: com.google.android.intent.action.GCM_RECONNECT
imoblife.memorybooster.full (): Wakeups: 107 (16.0 / hr.)
Alarms: 31, Intent: imoblife.memorybooster.full.refresh_statusbar
Alarms: 76, Intent: broadcast_optimize
com.ninefolders.hd3 (): Wakeups: 90 (13.5 / hr.)
Alarms: 83, Intent: com.ninefolders.hd3.intent.action.TRIGGER_ACCOUNT_WAKEUP cmp={com.ninefolders.hd3/com.ninefolders.hd3.engine.service.SyncEngineService}
Alarms: 7, Intent: {com.ninefolders.hd3/com.ninefolders.hd3.engine.service.MailboxAlarmReceiver}
android (): Wakeups: 89 (13.4 / hr.)
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 6, Intent: com.carrieriq.iqagent.service.action.WAKEUP
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 6, Intent: android.app.backup.intent.RUN
Alarms: 0, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 76, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 0, Intent: com.android.server.LightsService.action.UPDATE_SVC_LED
Alarms: 1, Intent: com.android.server.IdleMaintenanceService.action.UPDATE_IDLE_MAINTENANCE_STATE
com.android.providers.calendar (): Wakeups: 41 (6.2 / hr.)
Alarms: 33, Intent: com.android.providers.calendar.intent.CalendarProvider2
Alarms: 4, Intent: android.intent.action.EVENT_REMINDER
Alarms: 4, Intent: com.android.providers.calendar.SCHEDULE_ALARM cmp={com.android.providers.calendar/com.android.providers.calendar.CalendarReceiver}
com.android.keyguard (): Wakeups: 10 (1.5 / hr.)
Alarms: 10, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
com.android.vending (): Wakeups: 3 (0.5 / hr.)
Alarms: 2, Intent: {com.android.vending/com.google.android.finsky.services.ContentSyncService}
Alarms: 1, Intent: {com.android.vending/com.google.android.finsky.services.DailyHygiene}
com.google.android.talk (): Wakeups: 3 (0.4 / hr.)
Alarms: 3, Intent: com.google.android.apps.hangouts.CLEANUP_DB
com.google.android.googlequicksearchbox (): Wakeups: 3 (0.4 / hr.)
Alarms: 1, Intent: {com.google.android.googlequicksearchbox/com.google.android.velvet.VelvetBackgroundTasksImpl$Service}
Alarms: 2, Intent: ACTION_MAYBE_UPDATE_CONTACTS cmp={com.google.android.googlequicksearchbox/com.google.android.search.core.summons.icing.InternalIcingCorporaProvider$UpdateCorporaService}
com.android.calendar (): Wakeups: 2 (0.3 / hr.)
Alarms: 2, Intent: android.intent.action.EVENT_REMINDER cmp={com.android.calendar/com.android.calendar.alerts.AlertReceiver}
com.policydm (): Wakeups: 1 (0.2 / hr.)
Alarms: 1, Intent: com.policydm.intent.action.EULA_TIME
======================
Network (requires root)
======================
10034 (Wifi) (com.android.vending.Google Play Store): 32.0 MBytes 73.6%
10234 (Wifi) (com.skype.raider.Skype): 2.0 MBytes 6.3%
10253 (Mobile) (com.opera.browser.Opera): 1.0 MBytes 4.3%
10211 (Wifi) (com.ninefolders.hd3.Nine): 1.0 MBytes 2.9%
10014 (Wifi) (Google Play services): 1.0 MBytes 2.8%
10119 (Wifi) (com.google.android.gm.Gmail): 1.0 MBytes 2.6%
10211 (Mobile) (com.ninefolders.hd3.Nine): 842.0 KBytes 1.9%
10234 (Mobile) (com.skype.raider.Skype): 529.0 KBytes 1.2%
0 (Wifi) (0): 402.0 KBytes 0.9%
10119 (Mobile) (com.google.android.gm.Gmail): 293.0 KBytes 0.6%
10014 (Mobile) (Google Play services): 292.0 KBytes 0.6%
10002 (Wifi) (com.google.android.configupdater.ConfigUpdater): 272.0 KBytes 0.6%
10105 (Wifi) (com.google.android.apps.docs.Drive): 217.0 KBytes 0.5%
0 (Mobile) (0): 193.0 KBytes 0.4%
10253 (Wifi) (com.opera.browser.Opera): 111.0 KBytes 0.2%
1000 (Wifi) (Android System): 49.0 KBytes 0.1%
10120 (Wifi) (com.google.android.syncadapters.calendar.Google Calendar Sync): 39.0 KBytes 0.1%
10204 (Wifi) (com.google.android.youtube.YouTube): 22.0 KBytes 0.1%
10064 (Wifi) (com.google.android.googlequicksearchbox.Google Search): 22.0 KBytes 0.0%
10228 (Mobile) (UID): 18.0 KBytes 0.0%
10064 (Mobile) (com.google.android.googlequicksearchbox.Google Search): 14.0 KBytes 0.0%
10050 (Wifi) (com.sec.android.gallery3d.Gallery): 14.0 KBytes 0.0%
10044 (Wifi) (com.sec.android.app.samsungapps.GALAXY Apps): 11.0 KBytes 0.0%
10262 (Mobile) (com.asksven.betterbatterystats.BetterBatteryStats): 8.0 KBytes 0.0%
10095 (Wifi) (com.android.chrome.Chrome): 7.0 KBytes 0.0%
10095 (Mobile) (com.android.chrome.Chrome): 7.0 KBytes 0.0%
10153 (Wifi) (com.visionobjects.resourcemanager.MyScript Resource Manager): 6.0 KBytes 0.0%
10269 (Mobile) (imoblife.memorybooster.full.Memory Booster Full): 4.0 KBytes 0.0%
10213 (Wifi) (slide.cameraZoom.Camera ZOOM FX): 2.0 KBytes 0.0%
10228 (Wifi) (UID): 2.0 KBytes 0.0%
10049 (Wifi) (Media): 972.0 Bytes 0.0%
10204 (Mobile) (com.google.android.youtube.YouTube): 900.0 Bytes 0.0%
10216 (Mobile) (com.jrtstudio.AnotherMusicPlayer.Rocket Player): 800.0 Bytes 0.0%
10201 (Wifi) (com.sec.android.daemonapp.Unified Daemon): 544.0 Bytes 0.0%
10105 (Mobile) (com.google.android.apps.docs.Drive): 384.0 Bytes 0.0%
10049 (Mobile) (Media): 208.0 Bytes 0.0%
10034 (Mobile) (com.android.vending.Google Play Store): 128.0 Bytes 0.0%
10050 (Mobile) (com.sec.android.gallery3d.Gallery): 128.0 Bytes 0.0%
==========
CPU States
==========
2.46 GHz (): 2 h 12 m 5 s 33.2%
Deep Sleep (): 4 h 25 m 50 s 66.4%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 2 m 39 s (Wl: 5 elements; KWl: 0elements; NetS: 9 elements; Alrm: 1 elements; Proc: 40 elements; Oth: 5 elements; CPU: 1 elements)
ref_current: Reference ref_current created 6 h 40 m 35 s (Wl: 66 elements; KWl: 51elements; NetS: 41 elements; Alrm: 11 elements; Proc: 174 elements; Oth: 13 elements; CPU: 2 elements)
Any help would be appreciated, otherwise this phone is getting returned very soon and I'm ditching samsung.

Have u checked the cpu? It could be hanging.
Samsung unlock Bootloader on SM-870A.

Yeah, it doesn't appear to be out of control

So I've been investigating this further, I've tuned various settings and shut off features I don't need or use, that said, I've gotten a best case, 4.2% battery drain an hour, this is even when the phone is completely idle as the testing I was doing was overnight when the phone should be quiet.
Switching back to the stock firmware which really only has been rooted and contains better battery status, testing the phone the same way, quiet, over night, little to no activity and I'm getting 0.2% to 0.3% battery loss. The disturbing thing about this is that there's much bloat still on the system and many garbage processes running.
So the last test last night was to clone the stock firmware into a rom slot and boot and run that. With that done I was seeing 6.8% battery draw an hour.
So zero changes, the only difference being how it was booted. At this point I'm now suspecting that TWRP or Safestrap it self are eating battery constantly, and that because it's one of those two doing it, none of the apps I'm using are able to detect this usage.
So my question is, how do you debug twrp / safestrap power draw, and is anyone else seeing this?

From what i understand i believe its literally not possible fot a recovery to use battery, so theres nothing really for you to investigate.
Sent from my SM-G900A using Tapatalk

Seems to me that u should stay on stock slot then u have drain under control. No that's not what u wanted to hear.
AT&T u unlocked Lg G3 how about Sm-870A & Sm-900A.

So I factory reset the stock slot, grabbed a backup of it, then restored the rom image which was draining the battery to the stock slot. Doing so left me with less than 1% battery drain at a minimum from a full charge and a maximum of 3% while making calls, etc.
Taking that exact same image, and booting it off of rom-slot-1 yielded 7% minimum battery drain an hour at a minimum and 12% an hour when making calls.
I have no idea how TWRP sets up the rom slots, but if it's using loop device then it's possible theres a bug, resulting in a higher than normal battery drain.
Otherwise, I can't think of any other explanation as to why I'm seeing this behavior. It makes zero sense that the exact same rom (bit for bit) drains the batter so much faster on a rom slot vs stock rom slot.

cfaber said:
So I factory reset the stock slot, grabbed a backup of it, then restored the rom image which was draining the battery to the stock slot. Doing so left me with less than 1% battery drain at a minimum from a full charge and a maximum of 3% while making calls, etc.
Taking that exact same image, and booting it off of rom-slot-1 yielded 7% minimum battery drain an hour at a minimum and 12% an hour when making calls.
I have no idea how TWRP sets up the rom slots, but if it's using loop device then it's possible theres a bug, resulting in a higher than normal battery drain.
Otherwise, I can't think of any other explanation as to why I'm seeing this behavior. It makes zero sense that the exact same rom (bit for bit) drains the batter so much faster on a rom slot vs stock rom slot.
Click to expand...
Click to collapse
From what ive read(not much since I don't use rom slots) rom slots are buggy at best and for a while it was highly suggested to NOT use them for any reason, so you cant really expect perfect functionality from one from what ive seen.
Sent from my SM-G900A using Tapatalk

Related

baseband_xmm_power wakelock

I wonder if anyone have this baseband_xmm_power wakelock. It´s preventing the phone from entering in deep sleep.
I have this since i flashed the leaked 20A, and now i have it too in the official version.
I know this is a common problem in the Nexus and it has no solution. I also disabled fast dormency, it has no effect.
any kind of help to solve this wakelock is appreciated
thanx

xtribas said:
I wonder if anyone have this baseband_xmm_power wakelock. It´s preventing the phone from entering in deep sleep.
I have this since i flashed the leaked 20A, and now i have it too in the official version.
I know this is a common problem in the Nexus and it has no solution. I also disabled fast dormency, it has no effect.
any kind of help to solve this wakelock is appreciated
thanx
Click to expand...
Click to collapse
INFINEON XMM6260 is the call/Hspa board of P880 so this might be needed to let phone calls work in deep sleep

does it mean that it has to be replaced?

I had a lot of baseband_xmm_power wakelock , ppl told me it was because of 4.0.3 , and should be fixed in 4.0.4 or JB, obviously its not working.
Anyway, last month i did a hard reset AGAIN and the baseband_xmm_power wakelock is somehow gone. i dont know why...

i did factory reset when installed the official 20A, i dont think doing it again would solve it

xtribas said:
i did factory reset when installed the official 20A, i dont think doing it again would solve it
Click to expand...
Click to collapse
Well , you can try, and after dooing that, dont install nothing and watch for a day its gone, after that you can install your apps and restore your backuop.

will try that
thanx
---
After a factory reset still got this damn wakelock

Hi,
i've got the same issue with the baseband_xmm_power wakelock. It first appeared after flashing JB on my (at this point) unrooted device.
Short descripiton of my experience so far:
Disconnected fully charged phone in the evening. WLAN on, everything else turned off.
After some hours a massive drain started and stopped a few hours later.
The rest of the time the drain seems normal.
I haven't touched the phone a single time within those two days and ten hours of waiting, so there was absolutely no userinput or anything.
The small drop on the right is activity, so thats no issue.
I hope this helps figuring out what the problem is so we can solve this soon.

now in the new CM10.1 firmware this wakelock remains, i´m starting to think this is hardware related!

I had baseband_xmm_power and I finally solved it!(I hope it wont come back)
U have to use BBS to find out what are your wakelock,what is keeping your phone awake..Install BBS, leave it on for couple of hours(maybe bet over night) and then you can see what is keeping you phone awake..If you are rooted you should allow superuser on BBS so that you can see your alarm wakelocks. Most of the time its apps like facebook,viber,google maps..

brunek said:
I had baseband_xmm_power and I finally solved it!(I hope it wont come back)
U have to use BBS to find out what are your wakelock,what is keeping your phone awake..Install BBS, leave it on for couple of hours(maybe bet over night) and then you can see what is keeping you phone awake..If you are rooted you should allow superuser on BBS so that you can see your alarm wakelocks. Most of the time its apps like facebook,viber,google maps..
Click to expand...
Click to collapse
the wakelock in named baseband_xmm_power, its a partial wakelock, i got almost no alarms

I got that same wakelock in kernel wakelocks...Do you have BBS? Leave the phone for a couple of hours and then do a dump so that you can see what is the problem..If you dont know to read it yourself,post it in BBS thread!

Well I somewhat solved the problem. Turns out baseband_xmm_power wasn't the biggest culprit after all. Networklocationlocator was draining most of my battery according to BBS. It was causing partial wakelocks that was in turn causing kernel wakelocks with powermanagerservice. I turned off all location access and now I only lost 8% overnight. Still not the greatest but way better than 26%. I can live without location access. I'll just turn it on when I need it.
On a side note, did any of you disable Fast Dormancy with the database edit that was posted?
Edit: baseband_xmm_power is still showing battery drain but it's not that much, as I said, I only lost 8% overnight which was 1% per hour.

Before the new CM i had this wakelock with and without fast dormency disabled. Now i didn´t try to disable it yet...

You can`t know for sure what is draining your battery without quality dump from BBS..It can be wide range of things...My problem was google maps and viber..After I resolved that my battery was over 7 hours during the night on 100%!:victory:

xtribas said:
Before the new CM i had this wakelock with and without fast dormency disabled. Now i didn´t try to disable it yet...
Click to expand...
Click to collapse
Try disabling it. Mine is disabled so that might explain why baseband_xmm_power doesn't use as much battery as others reported.
brunek said:
You can`t know for sure what is draining your battery without quality dump from BBS..It can be wide range of things...My problem was google maps and viber..After I resolved that my battery was over 7 hours during the night on 100%!:victory:
Click to expand...
Click to collapse
How do I dump?

After you left your phone for a couple of hours(best over night) at the top you have a "share" icon and you pres share it as a text dumpfile...
Also check all in settings/dumpfile andsettings/advanced..

brunek said:
After you left your phone for a couple of hours(best over night) at the top you have a "share" icon and you pres share it as a text dumpfile...
Also check all in settings/dumpfile andsettings/advanced..
Click to expand...
Click to collapse
I don't really see anything since I turned off location.
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0B1
Creation Date: 2013-04-17 11:01:43
Statistic Type: Unplugged to Current
Since 10 h 19 m 9 s
VERSION.RELEASE: 4.1.2
BRAND: lge
DEVICE: x3
MANUFACTURER: LGE
MODEL: LG-P880
OS.VERSION: 3.1.10-g19c6a62
BOOTLOADER: unknown
HARDWARE: x3
FINGERPRINT: lge/x3_open_esa/x3:4.1.2/JZO54K/P88020a.1e5c83df00:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: prasanth.kumar
PRODUCT: x3_open_esa
RADIO: L6260_MODEM_SIC_02.1233.00
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -25% (100% to 75%) [2.4%/h]
Voltage lost [mV]: (4341-4000) [33.1%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 55 m 38 s (24938 s) Ratio: 67.1%
Awake (): 3 h 23 m 30 s (12210 s) Ratio: 32.9%
Screen On (): 32 m 30 s (1950 s) Ratio: 5.3%
Wifi On (): 10 h 19 m 9 s (37149 s) Ratio: 100.0%
Wifi Running (): 10 h 19 m 9 s (37149 s) Ratio: 100.0%
No Data Connection (): 9 h 41 m 25 s (34885 s) Ratio: 93.9%
No or Unknown Signal (): 9 h 41 m 25 s (34885 s) Ratio: 93.9%
Screen dark (): 2 m 3 s (123 s) Ratio: 0.3%
Screen dimmed (): 6 m 34 s (394 s) Ratio: 0.2%
Screen medium (): 23 m 49 s (1429 s) Ratio: 0.8%
Screen light (): 2 s (2 s) Ratio: 0.0%
Screen bright (): 1 s (1 s) Ratio: 0.0%
=========
Wakelocks
=========
AudioOut_2 (1013): 11 m 26 s (686 s) Count:25 1.8%
WifiOffDelayIfNotUsed (Android System): 3 m 5 s (185 s) Count:236 0.5%
AlarmManager (Android System): 56 s (56 s) Count:1106 0.2%
ActivityManager-Launch (Android System): 44 s (44 s) Count:214 0.1%
FbClientConnManager (com.facebook.katana.Facebook): 42 s (42 s) Count:47 0.1%
StartingAlertService (Calendar): 36 s (36 s) Count:8 0.1%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 21 s (21 s) Count:198 0.1%
LocationPrivacyService (com.google.android.apps.maps.Maps): 13 s (13 s) Count:29 0.0%
sleep_broadcast (Android System): 10 s (10 s) Count:291 0.0%
DownloadManager (Media): 9 s (9 s) Count:3 0.0%
AlarmManager (com.ebay.mobile.eBay): 8 s (8 s) Count:127 0.0%
FacebookService (com.facebook.katana.Facebook): 7 s (7 s) Count:10 0.0%
NetworkStats (Android System): 7 s (7 s) Count:128 0.0%
com.ebay.mobile (com.ebay.mobile.eBay): 6 s (6 s) Count:256 0.0%
*vibrator* (Android System): 6 s (6 s) Count:484 0.0%
AlarmManager (cloudtv.hdwidgets.HD Widgets): 5 s (5 s) Count:27 0.0%
RILJ (Phone): 4 s (4 s) Count:81 0.0%
SMSDispatcher (Phone): 3 s (3 s) Count:9 0.0%
DHCP (Android System): 3 s (3 s) Count:317 0.0%
ConnectivityService (Android System): 3 s (3 s) Count:1108 0.0%
AlarmManager (com.facebook.katana.Facebook): 3 s (3 s) Count:181 0.0%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 2 s (2 s) Count:179 0.0%
show keyguard (Android System): 2 s (2 s) Count:12 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 2 s (2 s) Count:11 0.0%
AlarmManager (com.google.android.googlequicksearchbox.Google Search): 2 s (2 s) Count:90 0.0%
*backup* (Android System): 2 s (2 s) Count:506 0.0%
Icing (Google Services): 1 s (1 s) Count:4 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 s (1 s) Count:184 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:260 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:26 0.0%
CallerInfoCache (Phone): 1 s (1 s) Count:2 0.0%
GTALK_CONN (Google Services): 1 s (1 s) Count:161 0.0%
StartingAlertService (com.android.mms.Messaging): 1 s (1 s) Count:1 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1132 0.0%
================
Kernel Wakelocks
================
"baseband_xmm_power" (): 2 h 23 m 22 s (8602 s) Cntc/wc/ec)615/0/0 23.2%
"PowerManagerService" (): 6 m 9 s (369 s) Cntc/wc/ec)1409/0/0 1.0%
"wlan_rx_wake" (): 4 m 41 s (281 s) Cntc/wc/ec)461/0/461 0.8%
"alarm_rtc" (): 3 m 16 s (196 s) Cntc/wc/ec)360/0/54 0.5%
"alarm" (): 3 m 12 s (192 s) Cntc/wc/ec)1046/299/0 0.5%
"radio-interface" (): 1 m 5 s (65 s) Cntc/wc/ec)98/0/0 0.2%
"wlan_ctrl_wake" (): 46 s (46 s) Cntc/wc/ec)39/0/39 0.1%
"wlan_wake" (): 14 s (14 s) Cntc/wc/ec)63019/35/0 0.0%
"deleted_wake_locks" (): 8 s (8 s) Cntc/wc/ec)500/0/0 0.0%
"KeyEvents" (): 1 s (1 s) Cntc/wc/ec)13022/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)52/0/0 -0.0%
"event9-362" (system, android, com.google.android.backup, com.android.providers.settings): (0 s) Cntc/wc/ec)5/0/0 0.0%
=========
Processes
=========
com.android.chrome (com.android.chrome.Chrome): Uid: 10016 Sys: 8 s (8 s) Us: 13 s (13 s) Starts: 5
mediaserver (1013): Uid: 1013 Sys: 4 s (4 s) Us: 13 s (13 s) Starts: 0
com.android.chrome:sandboxed_process3 (com.android.chrome.Chrome): Uid: 10016 Sys: 3 s (3 s) Us: 14 s (14 s) Starts: 1
surfaceflinger (Android System): Uid: 1000 Sys: 7 s (7 s) Us: 4 s (4 s) Starts: 0
com.android.chrome:sandboxed_process2 (com.android.chrome.Chrome): Uid: 10016 Sys: 1 s (1 s) Us: 7 s (7 s) Starts: 2
dhd_dpc (0): Uid: 0 Sys: 5 s (5 s) Us: (0 s) Starts: 0
com.facebook.katana (com.facebook.katana.Facebook): Uid: 10093 Sys: 1 s (1 s) Us: 3 s (3 s) Starts: 3
cloudtv.hdwidgets (cloudtv.hdwidgets.HD Widgets): Uid: 10112 Sys: (0 s) Us: 3 s (3 s) Starts: 2
mmcqd/0 (0): Uid: 0 Sys: 2 s (2 s) Us: (0 s) Starts: 0
kworker/0:1 (0): Uid: 0 Sys: 2 s (2 s) Us: (0 s) Starts: 0
com.android.vending (com.android.vending.Google Play Store): Uid: 10062 Sys: (0 s) Us: 1 s (1 s) Starts: 2
kworker/u:24 (0): Uid: 0 Sys: 2 s (2 s) Us: (0 s) Starts: 0
com.andrewshu.android.reddit (com.andrewshu.android.reddit.reddit is fun): Uid: 10095 Sys: (0 s) Us: 1 s (1 s) Starts: 4
kworker/0:2 (0): Uid: 0 Sys: 2 s (2 s) Us: (0 s) Starts: 0
kinteractiveup (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.android.defcontainer (com.android.defcontainer.Package Access Helper): Uid: 10017 Sys: (0 s) Us: 1 s (1 s) Starts: 3
kworker/u:6 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
kworker/u:1H (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
sdcard (1023): Uid: 1023 Sys: (0 s) Us: (0 s) Starts: 0
kworker/u:26 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.asksven.betterbatterystats_xdaedition (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): Uid: 10111 Sys: (0 s) Us: 1 s (1 s) Starts: 5
com.lge.mlt (Android System): Uid: 1000 Sys: (0 s) Us: (0 s) Starts: 4
com.quoord.tapatalkxda.activity (com.quoord.tapatalkxda.activity.XDA): Uid: 10100 Sys: (0 s) Us: (0 s) Starts: 2
btld (com.broadcom.bt.app.system.Bluetooth Services): Uid: 1002 Sys: (0 s) Us: (0 s) Starts: 0
edu.apollogrp.android.classroom.activity (edu.apollogrp.android.classroom.activity.Phoenix): Uid: 10096 Sys: (0 s) Us: (0 s) Starts: 1
kworker/u:3 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
kworker/0:0 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
kworker/u:1 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
kworker/u:5 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
kworker/u:13 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
51 MHz (): 2 h 15 m 5 s 21.8%
102 MHz (): 6 m 58 s 1.1%
204 MHz (): 1 m 49 s 0.3%
340 MHz (): 11 m 55 s 1.9%
475 MHz (): 26 m 32 s 4.3%
640 MHz (): 4 m 16 s 0.7%
760 MHz (): 4 m 52 s 0.8%
860 MHz (): 1 m 1 s 0.2%
1 GHz (): 2 m 31 s 0.4%
1.1 GHz (): 31 s 0.1%
1.2 GHz (): 21 s 0.1%
1.3 GHz (): 23 s 0.1%
1.4 GHz (): 5 m 9 s 0.8%
1.5 GHz (): 1 m 59 s 0.3%
Deep Sleep (): 6 h 55 m 38 s 67.1%
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
com.android.phone (com.android.phone.TelephonyDebugService)
Active since: 29 s
Last activity: 29 s
Crash count:0
com.lge.systemserver (com.lge.systemservice.service.LGSystemServerFactory)
Active since: 27 s
Last activity: 27 s
Crash count:0
com.facebook.katana (com.facebook.katana.service.MediaUploadService)
Active since: 46 s
Last activity: 1 d 5 h 22 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 28 s
Last activity: 28 s
Crash count:0
com.facebook.katana (com.facebook.katana.service.BackgroundDetectionService)
Active since: 2 d 11 m 50 s
Last activity: 1 d 5 h 8 m 52 s
Crash count:0
com.sirma.mobile.bible.android (com.urbanairship.push.PushService)
Active since: 50 s
Last activity: 1 d 5 h 15 m 3 s
Crash count:0
com.google.android.apps.maps (com.google.googlenav.prefetch.android.PrefetcherService)
Active since: 1 d 3 h
Last activity: 1 d 5 h 2 m 59 s
Crash count:0
com.facebook.katana (com.facebook.contacts.service.ContactsService)
Active since: 1 d 2 h 53 m 41 s
Last activity: 1 d 5 h 51 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 25 s
Last activity: 25 s
Crash count:0
cloudtv.hdwidgets (cloudtv.hdwidgets.services.WidgetUpdaterService)
Active since: 37 s
Last activity: 1 d 5 h 20 m 38 s
Crash count:0
com.lge.systemserver (com.lge.systemservice.core.unlockcheck.UnlockService)
Active since: 27 s
Last activity: 27 s
Crash count:0
com.lge.lgfotaclient:remote (com.lge.lgfotaclient.DmclientService)
Active since: 45 s
Last
Sent from my LG-P880 using xda app-developers app

You dont have root? Enable all options in advance settings(all root access ) and thick all in dump prefs. You need to see alarm wakelocks.
Locations are not the only thing you should look at. Try disabeling google maps(settings/apps/all apps/maps and there you can disable. If you have viber and facebook uninstall them, maybe they are causing the wakelocks!
poslano s ubojitog LG 4X HD

brunek said:
You dont have root? Enable all options in advance settings(all root access ) and thick all in dump prefs. You need to see alarm wakelocks.
Locations are not the only thing you should look at. Try disabeling google maps(settings/apps/all apps/maps and there you can disable. If you have viber and facebook uninstall them, maybe they are causing the wakelocks!
poslano s ubojitog LG 4X HD
Click to expand...
Click to collapse
I'm only losing 1% per hour. I'm happy with that after solving the networklocationlocator. Thanks though. Everything was checked and I do have root.
Sent from my LG-P880 using xda app-developers app

[Q] How to reduce the 6 sec data-transfer wakelock?

Well I have asked this question a couple of times in the battery and wakelock thread. But that thread seems to be inactive so 'm asking it here.
The thing is I don't have WiFi access at home or college. So I rely totally on mobile data. Now the problem with mobile data is the 6 sec data transfer wakelock(multipdp) and a couple of more wakelocks like the l2hsic. Now is there a way or workaround to reduce that timer to 1 or 2 sec.
I'm using CM(inc) 10.1.3 stable release with default kernel. Modem LT3.
I will attach a bbs log in the second post as I forgot to take the reading this morning.
Sent from my Abacus using xda-developers app

Here's the log i took last morning. It was taken after using the phone for a while though. I mean i got up and used the phone for 5 or 10 minutes.
===================
General Information
===================
BetterBatteryStats version: 1.14.0.0
Creation Date: 2013-11-02 09:44:04
Statistic Type: Unplugged to Current
Since 6 h 47 m 14 s
VERSION.RELEASE: 4.2.2
BRAND: Samsung
DEVICE: GT-N7000
MANUFACTURER: samsung
MODEL: GT-N7000
OS.VERSION: 3.0.64-CM-g9c2e2bc
BOOTLOADER: unknown
HARDWARE: smdk4210
FINGERPRINT: samsung/GT-N7000/GT-N7000:4.0.3/IML74K/ZCLP6:user/release-keys
ID: JDQ39E
TAGS: test-keys
USER: jenkins
PRODUCT: GT-N7000
RADIO: N7000XXLT3
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -10% (100% to 90%) [1.5%/h]
Voltage lost [mV]: (4094-3991) [15.2%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 3 m 18 s (21798 s) Ratio: 89.2%
Awake (): 43 m 55 s (2635 s) Ratio: 10.8%
Screen On (): 12 m 16 s (736 s) Ratio: 3.0%
Moderate Signal (): 6 h 47 m 13 s (24433 s) Ratio: 100.0%
Screen dark (): 51 s (51 s) Ratio: 0.1%
Screen medium (): 11 m 25 s (685 s) Ratio: 2.8%
=========
Wakelocks
=========
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 20 s (140 s) Count:522 0.6%
AudioOut_2 (1013): 2 m 10 s (130 s) Count:23 0.5%
AlarmClock (com.android.deskclock.Clock): 59 s (59 s) Count:59 0.2%
*vibrator* (com.android.deskclock.Clock): 42 s (42 s) Count:33 0.2%
AlarmManager (Android System): 41 s (41 s) Count:422 0.2%
ActivityManager-Launch (Android System): 13 s (13 s) Count:77 0.1%
MAIL_SERVICE (com.android.exchange.Exchange Services): 9 s (9 s) Count:27 0.0%
GTALK_CONN (Google Services): 9 s (9 s) Count:469 0.0%
sendinactive (com.whatsapp.WhatsApp): 9 s (9 s) Count:44 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 3 s (3 s) Count:5 0.0%
Icing (Google Services): 2 s (2 s) Count:9 0.0%
show keyguard (Android System): 2 s (2 s) Count:17 0.0%
Event Log Service (Google Services): 2 s (2 s) Count:110 0.0%
AlarmManager (com.android.deskclock.Clock): 2 s (2 s) Count:46 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:582 0.0%
AlarmManager (com.google.android.apps.genie.geniewidget.News & Weather): 1 s (1 s) Count:203 0.0%
RILJ (Phone): 1 s (1 s) Count:158 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:441 0.0%
AlarmManager (com.android.exchange.Exchange Services): 1 s (1 s) Count:55 0.0%
GOOGLE_C2DM (Google Services): 1 s (1 s) Count:96 0.0%
================
Kernel Wakelocks
================
"multipdp" (): 20 m 17 s (1217 s) Cntc/wc/ec)169/0/170 5.0%
"l2_hsic" (): 8 m 11 s (491 s) Cntc/wc/ec)1266/105/1266 2.0%
"alarm_rtc" (): 5 m 8 s (308 s) Cntc/wc/ec)472/0/130 1.3%
"PowerManagerService" (): 4 m 14 s (254 s) Cntc/wc/ec)796/0/0 1.0%
"sec-battery-monitor" (): 2 m 39 s (159 s) Cntc/wc/ec)474/341/0 0.7%
"alarm" (): 1 m 53 s (113 s) Cntc/wc/ec)725/0/0 0.5%
"rpm_hsic" (): 1 m 46 s (106 s) Cntc/wc/ec)686/0/0 0.4%
"umts_ipc0" (): 51 s (51 s) Cntc/wc/ec)175/0/175 0.2%
"radio-interface" (): 25 s (25 s) Cntc/wc/ec)51/0/0 0.1%
"tx_hsic" (): 12 s (12 s) Cntc/wc/ec)1147/1/0 0.1%
"power-supply" (): 3 s (3 s) Cntc/wc/ec)462/0/0 -0.0%
"PowerManagerService.Broadcasts" (): 3 s (3 s) Cntc/wc/ec)50/0/0 0.0%
"sync_system" (): 1 s (1 s) Cntc/wc/ec)25/0/0 0.0%
"mmc1_detect" (): (0 s) Cntc/wc/ec)598/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)2946/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)598/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)384/0/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.apps.genie.geniewidget (): Wakeups: 204
Alarms: 204, Intent: {com.google.android.apps.genie.geniewidget
com.google.android.gsf (): Wakeups: 58
Alarms: 39, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 5, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 14, Intent: {com.google.android.gsf
Alarms: 0, Intent: com.google.android.intent.action.MCS_HEARTBEAT
com.android.phone (): Wakeups: 57
Alarms: 57, Intent: com.android.internal.telephony.gprs-data-stall
Alarms: 0, Intent: com.android.phone.UPDATE_CALLER_INFO_CACHE
Alarms: 0, Intent: com.android.internal.telephony.gprs-reconnect.0
com.whatsapp (): Wakeups: 41
Alarms: 0, Intent: ALARM_ACTION
Alarms: 37, Intent: com.whatsapp.MessageService.RECONNECT
Alarms: 0, Intent: ALARM_ROTATE_LOGS
Alarms: 3, Intent: ALARM_AVAILABLE_TIMEOUT
Alarms: 1, Intent: ALARM_MESSAGES_DB_BACKUP
Alarms: 0, Intent: ALARM_CLIENT_PING_TIMEOUT
com.android.exchange (): Wakeups: 28
Alarms: 16, Intent: {com.android.exchange
Alarms: -3, Intent: {com.android.exchange
com.android.deskclock (): Wakeups: 13
Alarms: 13, Intent: com.android.deskclock.ALARM_ALERT
com.google.android.gms (): Wakeups: 4
Alarms: 3, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 0, Intent: {com.google.android.gms
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE
android (): Wakeups: 3
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 3, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 0, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
com.google.android.googlequicksearchbox (): Wakeups: 3
Alarms: 3, Intent: {com.google.android.googlequicksearchbox
======================
Network (requires root)
======================
10037 (Mobile) (Google Services): 129.0 KBytes 41.4%
10062 (Mobile) (com.google.android.googlequicksearchbox.Google Search): 80.0 KBytes 25.8%
10068 (Mobile) (com.whatsapp.WhatsApp): 60.0 KBytes 19.5%
10020 (Mobile) (com.android.exchange.Exchange Services): 19.0 KBytes 6.2%
0 (Mobile) (0): 16.0 KBytes 5.4%
10076 (Mobile) (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 5.0 KBytes 1.6%
10071 (Mobile) (com.google.android.youtube.YouTube): 144.0 Bytes 0.0%
10061 (Mobile) (com.android.vending.Google Play Store): 120.0 Bytes 0.0%
==========
CPU States
==========
1.4 GHz (): 1 m 50 s 0.5%
1.2 GHz (): 50 s 0.2%
1 GHz (): 20 s 0.1%
800 MHz (): 4 m 12 s 1.0%
500 MHz (): 10 m 57 s 2.7%
200 MHz (): 25 m 43 s 6.3%
Deep Sleep (): 6 h 3 m 18 s 89.2%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 31 s (Wl: 3 elements; KWl: 0elements; NetS: 2 elements; Alrm: 1 elements; Proc: 0 elements; Oth: 5 elements; CPU: 6 elements)
ref_unplugged: Reference ref_unplugged created 6 h 53 m 52 s (Wl: 0 elements; KWl: 23elements; NetS: 14 elements; Alrm: 12 elements; Proc: 0 elements; Oth: 5 elements; CPU: 7 elements)
ref_charged: Reference ref_charged created 6 h 53 m 53 s (Wl: 0 elements; KWl: 23elements; NetS: 14 elements; Alrm: 12 elements; Proc: 0 elements; Oth: 5 elements; CPU: 7 elements)
ref_custom: Reference ref_custom created 6 h 54 m 7 s (Wl: 1 elements; KWl: 23elements; NetS: 14 elements; Alrm: 12 elements; Proc: 0 elements; Oth: 5 elements; CPU: 7 elements)
ref_current: Reference ref_current created 13 h 41 m 7 s (Wl: 20 elements; KWl: 23elements; NetS: 15 elements; Alrm: 13 elements; Proc: 6 elements; Oth: 6 elements; CPU: 7 elements)
Sent from my Abacus using xda-developers app

Try to enable data roaming in mobile network settings and check again. Also research on your providers fast dormancy settings and apply that on your phone accordingly.
https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/svnet-dormancy

walkermoon said:
Here's the log i took last morning. It was taken after using the phone for a while though. I mean i got up and used the phone for 5 or 10 minutes.
===================
General Information
===================
BetterBatteryStats version: 1.14.0.0
Creation Date: 2013-11-02 09:44:04
Statistic Type: Unplugged to Current
Since 6 h 47 m 14 s
VERSION.RELEASE: 4.2.2
BRAND: Samsung
DEVICE: GT-N7000
MANUFACTURER: samsung
MODEL: GT-N7000
OS.VERSION: 3.0.64-CM-g9c2e2bc
BOOTLOADER: unknown
HARDWARE: smdk4210
FINGERPRINT: samsung/GT-N7000/GT-N7000:4.0.3/IML74K/ZCLP6:user/release-keys
ID: JDQ39E
TAGS: test-keys
USER: jenkins
PRODUCT: GT-N7000
RADIO: N7000XXLT3
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -10% (100% to 90%) [1.5%/h]
Voltage lost [mV]: (4094-3991) [15.2%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 3 m 18 s (21798 s) Ratio: 89.2%
Awake (): 43 m 55 s (2635 s) Ratio: 10.8%
Screen On (): 12 m 16 s (736 s) Ratio: 3.0%
Moderate Signal (): 6 h 47 m 13 s (24433 s) Ratio: 100.0%
Screen dark (): 51 s (51 s) Ratio: 0.1%
Screen medium (): 11 m 25 s (685 s) Ratio: 2.8%
=========
Wakelocks
=========
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 20 s (140 s) Count:522 0.6%
AudioOut_2 (1013): 2 m 10 s (130 s) Count:23 0.5%
AlarmClock (com.android.deskclock.Clock): 59 s (59 s) Count:59 0.2%
*vibrator* (com.android.deskclock.Clock): 42 s (42 s) Count:33 0.2%
AlarmManager (Android System): 41 s (41 s) Count:422 0.2%
ActivityManager-Launch (Android System): 13 s (13 s) Count:77 0.1%
MAIL_SERVICE (com.android.exchange.Exchange Services): 9 s (9 s) Count:27 0.0%
GTALK_CONN (Google Services): 9 s (9 s) Count:469 0.0%
sendinactive (com.whatsapp.WhatsApp): 9 s (9 s) Count:44 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 3 s (3 s) Count:5 0.0%
Icing (Google Services): 2 s (2 s) Count:9 0.0%
show keyguard (Android System): 2 s (2 s) Count:17 0.0%
Event Log Service (Google Services): 2 s (2 s) Count:110 0.0%
AlarmManager (com.android.deskclock.Clock): 2 s (2 s) Count:46 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:582 0.0%
AlarmManager (com.google.android.apps.genie.geniewidget.News & Weather): 1 s (1 s) Count:203 0.0%
RILJ (Phone): 1 s (1 s) Count:158 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:441 0.0%
AlarmManager (com.android.exchange.Exchange Services): 1 s (1 s) Count:55 0.0%
GOOGLE_C2DM (Google Services): 1 s (1 s) Count:96 0.0%
================
Kernel Wakelocks
================
"multipdp" (): 20 m 17 s (1217 s) Cntc/wc/ec)169/0/170 5.0%
"l2_hsic" (): 8 m 11 s (491 s) Cntc/wc/ec)1266/105/1266 2.0%
"alarm_rtc" (): 5 m 8 s (308 s) Cntc/wc/ec)472/0/130 1.3%
"PowerManagerService" (): 4 m 14 s (254 s) Cntc/wc/ec)796/0/0 1.0%
"sec-battery-monitor" (): 2 m 39 s (159 s) Cntc/wc/ec)474/341/0 0.7%
"alarm" (): 1 m 53 s (113 s) Cntc/wc/ec)725/0/0 0.5%
"rpm_hsic" (): 1 m 46 s (106 s) Cntc/wc/ec)686/0/0 0.4%
"umts_ipc0" (): 51 s (51 s) Cntc/wc/ec)175/0/175 0.2%
"radio-interface" (): 25 s (25 s) Cntc/wc/ec)51/0/0 0.1%
"tx_hsic" (): 12 s (12 s) Cntc/wc/ec)1147/1/0 0.1%
"power-supply" (): 3 s (3 s) Cntc/wc/ec)462/0/0 -0.0%
"PowerManagerService.Broadcasts" (): 3 s (3 s) Cntc/wc/ec)50/0/0 0.0%
"sync_system" (): 1 s (1 s) Cntc/wc/ec)25/0/0 0.0%
"mmc1_detect" (): (0 s) Cntc/wc/ec)598/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)2946/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)598/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)384/0/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.apps.genie.geniewidget (): Wakeups: 204
Alarms: 204, Intent: {com.google.android.apps.genie.geniewidget
com.google.android.gsf (): Wakeups: 58
Alarms: 39, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 5, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 14, Intent: {com.google.android.gsf
Alarms: 0, Intent: com.google.android.intent.action.MCS_HEARTBEAT
com.android.phone (): Wakeups: 57
Alarms: 57, Intent: com.android.internal.telephony.gprs-data-stall
Alarms: 0, Intent: com.android.phone.UPDATE_CALLER_INFO_CACHE
Alarms: 0, Intent: com.android.internal.telephony.gprs-reconnect.0
com.whatsapp (): Wakeups: 41
Alarms: 0, Intent: ALARM_ACTION
Alarms: 37, Intent: com.whatsapp.MessageService.RECONNECT
Alarms: 0, Intent: ALARM_ROTATE_LOGS
Alarms: 3, Intent: ALARM_AVAILABLE_TIMEOUT
Alarms: 1, Intent: ALARM_MESSAGES_DB_BACKUP
Alarms: 0, Intent: ALARM_CLIENT_PING_TIMEOUT
com.android.exchange (): Wakeups: 28
Alarms: 16, Intent: {com.android.exchange
Alarms: -3, Intent: {com.android.exchange
com.android.deskclock (): Wakeups: 13
Alarms: 13, Intent: com.android.deskclock.ALARM_ALERT
com.google.android.gms (): Wakeups: 4
Alarms: 3, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 0, Intent: {com.google.android.gms
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE
android (): Wakeups: 3
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 3, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 0, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
com.google.android.googlequicksearchbox (): Wakeups: 3
Alarms: 3, Intent: {com.google.android.googlequicksearchbox
======================
Network (requires root)
======================
10037 (Mobile) (Google Services): 129.0 KBytes 41.4%
10062 (Mobile) (com.google.android.googlequicksearchbox.Google Search): 80.0 KBytes 25.8%
10068 (Mobile) (com.whatsapp.WhatsApp): 60.0 KBytes 19.5%
10020 (Mobile) (com.android.exchange.Exchange Services): 19.0 KBytes 6.2%
0 (Mobile) (0): 16.0 KBytes 5.4%
10076 (Mobile) (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 5.0 KBytes 1.6%
10071 (Mobile) (com.google.android.youtube.YouTube): 144.0 Bytes 0.0%
10061 (Mobile) (com.android.vending.Google Play Store): 120.0 Bytes 0.0%
==========
CPU States
==========
1.4 GHz (): 1 m 50 s 0.5%
1.2 GHz (): 50 s 0.2%
1 GHz (): 20 s 0.1%
800 MHz (): 4 m 12 s 1.0%
500 MHz (): 10 m 57 s 2.7%
200 MHz (): 25 m 43 s 6.3%
Deep Sleep (): 6 h 3 m 18 s 89.2%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 31 s (Wl: 3 elements; KWl: 0elements; NetS: 2 elements; Alrm: 1 elements; Proc: 0 elements; Oth: 5 elements; CPU: 6 elements)
ref_unplugged: Reference ref_unplugged created 6 h 53 m 52 s (Wl: 0 elements; KWl: 23elements; NetS: 14 elements; Alrm: 12 elements; Proc: 0 elements; Oth: 5 elements; CPU: 7 elements)
ref_charged: Reference ref_charged created 6 h 53 m 53 s (Wl: 0 elements; KWl: 23elements; NetS: 14 elements; Alrm: 12 elements; Proc: 0 elements; Oth: 5 elements; CPU: 7 elements)
ref_custom: Reference ref_custom created 6 h 54 m 7 s (Wl: 1 elements; KWl: 23elements; NetS: 14 elements; Alrm: 12 elements; Proc: 0 elements; Oth: 5 elements; CPU: 7 elements)
ref_current: Reference ref_current created 13 h 41 m 7 s (Wl: 20 elements; KWl: 23elements; NetS: 15 elements; Alrm: 13 elements; Proc: 6 elements; Oth: 6 elements; CPU: 7 elements)
Sent from my Abacus using xda-developers app
Click to expand...
Click to collapse
Tried that. Data roaming is on. And fast dormancy doesnt help in this scenario. This wakelock always occurs whenever data transfer happens. I was just curious to know if I can reduce that 6 sec counter.
Thanks anyways.
Sent from my GT-I9105 using xda app-developers app

New Moto X user - Battery problem

Hi all.
I got my moto x on saturday and since that i got big problems with battery...
I left my phone over night and it consumed 35% battery without receving any notification ou phone call.
I tryed to use the BetterBatteryStats but with kitkat i need to root device to check full info (cant do this cause of phone warranty).
I leave 3g on, wi-fi on and location on all the time.
So what you guy think i can do?
He is the parts of BetterBatteryStats i got:
Code:
01-28 06:58:32.713 D/Globals (32350): Wakelock BBS_WAKELOCK_WHILE_SAVING_REF released
01-28 06:58:32.767 I/StatsActivity(32350): Since 7 h 28 m 22 s Bat.: -39% (100% to 61%) [5,2%/h]
01-28 06:58:32.780 I/StatsAdapter(32350): Values: Screen On 4 m 30 s (270 s) in 7 h 28 m 22 s (26902 s) Ratio: 1,0%
01-28 06:58:32.786 I/ReferenceStore(32350): Saved ref ref_current
01-28 06:58:32.790 I/StatsAdapter(32350): Values: Deep Sleep 7 h 13 m 20 s (26000 s) in 7 h 28 m 22 s (26902 s) Ratio: 96,6%
01-28 06:58:32.797 I/StatsAdapter(32350): Values: Awake 15 m 2 s (902 s) in 7 h 28 m 22 s (26902 s) Ratio: 3,4%
===========
Other Usage
===========
Screen On (): 4 m 30 s (270 s) Ratio: 1,0%
Deep Sleep (): 7 h 13 m 20 s (26000 s) Ratio: 96,6%
Awake (): 15 m 2 s (902 s) Ratio: 3,4%
=========
================
Kernel Wakelocks
================
"PowerManagerService.WakeLocks" (): 6 m 24 s (384 s) Cnt:(c/wc/ec)457/0/0 1,4%
"bam_dmux_wakelock" (): 3 m 3 s (183 s) Cnt:(c/wc/ec)172/0/0 0,7%
"wlan" (): 1 m 7 s (67 s) Cnt:(c/wc/ec)92/0/45 0,3%
"pm8921-charger-heartbeat" (): 37 s (37 s) Cnt:(c/wc/ec)321/89/0 0,1%
"power-supply" (): 33 s (33 s) Cnt:(c/wc/ec)285/-2/0 -0,0%
"pm8921_soc_lock" (): 23 s (23 s) Cnt:(c/wc/ec)1404/0/0 0,1%
"alarm_rtc" (): 23 s (23 s) Cnt:(c/wc/ec)115/30/2 0,1%
"alarm" (): 14 s (14 s) Cnt:(c/wc/ec)413/143/0 0,1%
"msp430" (): 14 s (14 s) Cnt:(c/wc/ec)25/8/25 0,1%
"radio-interface" (): 11 s (11 s) Cnt:(c/wc/ec)24/0/0 0,0%
"wlan_scan" (): 9 s (9 s) Cnt:(c/wc/ec)47/0/47 0,0%
"PowerManagerService.Broadcasts" (): 7 s (7 s) Cnt:(c/wc/ec)8/0/0 0,0%
"qcom_rx_wakelock" (): 6 s (6 s) Cnt:(c/wc/ec)287/0/286 0,0%
"PowerManagerService.Display" (): 6 s (6 s) Cnt:(c/wc/ec)8/0/0 0,0%
"msm_serial_hs_rx" (): 2 s (2 s) Cnt:(c/wc/ec)14/0/14 0,0%
"vibrator" (): 1 s (1 s) Cnt:(c/wc/ec)4/0/0 0,0%
"rmt_storage_-1224849472" (): (0 s) Cnt:(c/wc/ec)4/0/0 0,0%
"rmt_storage_-1224848888" (): (0 s) Cnt:(c/wc/ec)4/0/0 0,0%
"smsm_snapshot" (): (0 s) Cnt:(c/wc/ec)528/36/0 0,0%
"ipc0000000c_rmt_storage" (): (0 s) Cnt:(c/wc/ec)8/0/0 0,0%
"ipc00000022_Loc_hal_worker" (): (0 s) Cnt:(c/wc/ec)410/0/0 0,0%
"smdcntl0" (): (0 s) Cnt:(c/wc/ec)485/0/0 0,0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)1736/0/0 0,0%
"qcril" (): (0 s) Cnt:(c/wc/ec)141/0/0 0,0%
"smdcntl1" (): (0 s) Cnt:(c/wc/ec)61/0/0 0,0%
"msm_serial_hs_dma" (): (0 s) Cnt:(c/wc/ec)14/0/0 0,0%
"qmuxd_port_wl_0" (): (0 s) Cnt:(c/wc/ec)526/0/0 0,0%
"ipc_rtr_smd_rpcrpy_cntl" (): (0 s) Cnt:(c/wc/ec)523/4/0 0,0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)369/0/0 0,0%
"qmuxd_port_wl_1" (): (0 s) Cnt:(c/wc/ec)63/0/0 0,0%
"ipc00000018_qmi_motext_hook" (): (0 s) Cnt:(c/wc/ec)59/0/0 0,0%
"ipc0000001d_rild" (): (0 s) Cnt:(c/wc/ec)11/0/0 0,0%
======================
Thanks for your time and help.
P.s: Sorry for my english, not my current language

Give it a few days to settle down. I saw higher usage on powermanagerserivce for the first few days, then it calmed down.

Yeah I'd wait it out. My battery life was terrible at first (so I thought), but I was coming from a Droid Razr Maxx, which i could get 12+ hours of screen on time with no problem.
I was getting about 12 hours per day with my Moto X at first and was not thrilled with it, but after coming to grips with the fact that it is not as good as the Droid Razr Maxx and being happy with it lasting me a full day (7am-11pm, typically) without issue, I'm ok with it.
According to GSAM battery stats I average 16h23m with 7h48m active use and 4h51m average screen on time. Not too bad, in my opinion.
The 35% drain overnight thing seems a little high, but who knows. I'd reboot the phone and see if it happens again.

[Q] Battery drain on wifi @work

Since a couple of weeks I have a heavy battery drain on my HTC One when I'm logged into the unprotected wifi network at my work.
I'm using a custom rom, based on Slimrom 7.8, Android 4.4.4
A strange thing I notice in BestBatteryStats is 126MB use in 7 hours from Google Play-services and 62MB from another source:
10014 (Wifi) (Google Play-services): 126.0 MBytes 62,9%
0 (Wifi) (0): 62.0 MBytes 30,8%
What could be causing this battery drain, and how to fix this?
Internet seems to function fine, I can browse on internet, download and install apps etc.
This is the full BetterBatteryStats log:
===================
General Information
===================
BetterBatteryStats version: 1.16.0.0
Creation Date: 2014-09-17 13:31:28
Statistic Type: Charged to Current
Since 7 h 11 m 44 s
VERSION.RELEASE: 4.4.4
BRAND: htc
DEVICE: m7
MANUFACTURER: HTC
MODEL: One
OS.VERSION: 3.4.82-g9bd7e49
BOOTLOADER: 1.56.0000
HARDWARE: qcom
FINGERPRINT: htc/m7_google/m7:4.4.3/KTU84L.H4/347097:user/release-keys
ID: KTU84L.H4
TAGS: test-keys
USER: kasper
PRODUCT: slim_m7
RADIO: 4A.22.3263.14_10.38n.1157.04L
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -87% (100% to 13%) [12,1%/h]
Voltage lost [mV]: (4222-3365) [119,2%/h]
===========
Other Usage
===========
Deep Sleep (): 2 h 11 m 54 s (7914 s) Ratio: 30,6%
Awake (): 4 h 56 m 16 s (17776 s) Ratio: 68,6%
Screen On (): 58 m 11 s (3491 s) Ratio: 13,5%
Wifi On (): 7 h 3 m 6 s (25386 s) Ratio: 98,0%
Wifi Running (): 7 h 3 m 5 s (25385 s) Ratio: 98,0%
No Data Connection (): 6 h 45 m 46 s (24346 s) Ratio: 94,0%
No or Unknown Signal (): 6 h 45 m 46 s (24346 s) Ratio: 94,0%
Good Signal (): 21 m 45 s (1305 s) Ratio: 1,6%
Screen dark (): 53 m 57 s (3237 s) Ratio: 12,5%
Screen dimmed (): 1 m 34 s (94 s) Ratio: 0,1%
Screen light (): (0 s) Ratio: 0,0%
Screen bright (): 2 m 40 s (160 s) Ratio: 0,2%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
DirectTrack (1013): 12 m 35 s (755 s) Count:42 2,9%
AudioMix (1013): 6 m 9 s (369 s) Count:515 1,4%
*sync*/com.android.email.provider/com.android.exchange/[email protected] (com.android.exchange.Exchange Services): 2 m 25 s (145 s) Count:25 0,6%
AudioMix (com.spacegame.forestmania.Forest Mania): 1 m 17 s (77 s) Count:357 0,3%
AlarmManager (Android-systeem): 57 s (57 s) Count:1200 0,2%
ActivityManager-Launch (Android-systeem): 52 s (52 s) Count:658 0,2%
DHCP (Android-systeem): 34 s (34 s) Count:308 0,1%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 30 s (30 s) Count:12 0,1%
sendinactive (com.whatsapp.WhatsApp): 28 s (28 s) Count:128 0,1%
AudioMix (com.whatsapp.WhatsApp): 25 s (25 s) Count:118 0,1%
GCM_CONN_ALARM (Google Play-services): 25 s (25 s) Count:615 0,1%
DropboxCpuOnlyWakeLock (com.dropbox.android.Dropbox): 23 s (23 s) Count:4 0,1%
lock (org.telegram.messenger.Telegram): 20 s (20 s) Count:6 0,1%
RILJ (Telefoon): 16 s (16 s) Count:101 0,1%
TimedEventQueue (1013): 13 s (13 s) Count:30 0,1%
*sync*/com.android.email.provider/com.android.exchange/[email protected] (com.android.exchange.Exchange Services): 12 s (12 s) Count:37 0,0%
show keyguard (UID): 10 s (10 s) Count:28 0,0%
NetworkStats (Android-systeem): 9 s (9 s) Count:521 0,0%
StartingAlertService (com.android.calendar.Agenda): 9 s (9 s) Count:2 0,0%
Checkin Service (Google Play-services): 8 s (8 s) Count:562 0,0%
AlarmManager (org.yoki.android.buienalarm.Buienalarm): 7 s (7 s) Count:144 0,0%
GpsLocationProvider (Android-systeem): 6 s (6 s) Count:226 0,0%
GCM_CONN (Google Play-services): 5 s (5 s) Count:920 0,0%
SyncLoopWakeLock (Android-systeem): 4 s (4 s) Count:1678 0,0%
*sync*/com.android.email.provider/com.android.email/[email protected] (com.android.email.E-mail): 4 s (4 s) Count:49 0,0%
AlarmManager (com.facebook.orca.Messenger): 4 s (4 s) Count:141 0,0%
AudioMix (UID): 3 s (3 s) Count:37 0,0%
AlarmManager (com.facebook.katana.Facebook): 3 s (3 s) Count:146 0,0%
*vibrator* (org.telegram.messenger.Telegram): 2 s (2 s) Count:3 0,0%
SyncManagerHandleSyncAlarm (Android-systeem): 2 s (2 s) Count:105 0,0%
*vibrator* (com.whatsapp.WhatsApp): 2 s (2 s) Count:5 0,0%
ConnectivityService (Android-systeem): 2 s (2 s) Count:1201 0,0%
WifiSuspend (Android-systeem): 2 s (2 s) Count:259 0,0%
*vibrator* (com.android.email.E-mail): 1 s (1 s) Count:12 0,0%
*net_scheduler* (Google Play-services): 1 s (1 s) Count:426 0,0%
SCREEN_FROZEN (Android-systeem): 1 s (1 s) Count:310 0,0%
*vibrator* (com.spacegame.forestmania.Forest Mania): 1 s (1 s) Count:4 0,0%
SnetLaunchService (Google Play-services): 1 s (1 s) Count:935 0,0%
Event Log Service (Google Play-services): 1 s (1 s) Count:733 0,0%
*sync*/com.android.contacts/com.skype.contacts.sync/scoutcow (com.skype.raider.Skype): 1 s (1 s) Count:1 0,0%
================
Kernel Wakelocks
================
"wlan_rx_wake" (): 3 h 53 m (13980 s) Cntc/wc/ec)576/0/575 16,9%
"wlan_wd_wake" (): 2 h 55 m 58 s (10558 s) Cntc/wc/ec)99911/0/0 12,8%
"wlan_wake" (): 11 m 4 s (664 s) Cntc/wc/ec)411392/286/0 0,8%
"PowerManagerService.WakeLocks" (): 6 m 51 s (411 s) Cntc/wc/ec)1678/0/0 0,5%
"msm_hsic_host" (): 2 m 52 s (172 s) Cntc/wc/ec)113/11/0 0,2%
"wlan_ctrl_wake" (): 1 m 47 s (107 s) Cntc/wc/ec)116/0/116 0,1%
"suspend_backoff" (): 1 m 9 s (69 s) Cntc/wc/ec)7/0/7 0,1%
"pm8921_eoc" (): 1 m 8 s (68 s) Cntc/wc/ec)3/0/0 0,1%
"alarm_rtc" (): 60 s (60 s) Cntc/wc/ec)129/60/30 0,1%
"htc_battery_8960" (): 59 s (59 s) Cntc/wc/ec)305/0/0 0,1%
"pmic_led" (): 44 s (44 s) Cntc/wc/ec)175/0/175 0,1%
"alarm" (): 35 s (35 s) Cntc/wc/ec)2225/0/0 0,0%
"PowerManagerService.Broadcasts" (): 21 s (21 s) Cntc/wc/ec)68/0/0 0,0%
"gpio_input" (): 5 s (5 s) Cntc/wc/ec)141/13/0 0,0%
"radio-interface" (): 4 s (4 s) Cntc/wc/ec)49/0/0 0,0%
"msm_usb_cable" (): 2 s (2 s) Cntc/wc/ec)5/0/6 0,0%
"KeyEvents" (): 1 s (1 s) Cntc/wc/ec)38803/0/0 0,0%
"proximity" (): 1 s (1 s) Cntc/wc/ec)7/0/7 0,0%
"PowerManagerService.Display" (): (0 s) Cntc/wc/ec)34/0/0 0,0%
"efsks" (): (0 s) Cntc/wc/ec)4/0/0 0,0%
"vbus_lock" (): (0 s) Cntc/wc/ec)6/0/0 0,0%
"qcril" (): (0 s) Cntc/wc/ec)101/0/0 0,0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)515/0/0 0,0%
"mmc1_detect" (): (0 s) Cntc/wc/ec)515/0/0 0,0%
"qmuxd_port_wl_9" (): (0 s) Cntc/wc/ec)807/0/0 0,0%
======================
Alarms (requires root)
======================
android (): Wakeups: 188 (26,2 / hr.)
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 34, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 105, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 49, Intent: android.net.wifi.DHCP_RENEW
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 0, Intent: com.android.server.IdleMaintenanceService.action.UPDATE_IDLE_MAINTENANCE_STATE
com.facebook.katana (): Wakeups: 173 (24,1 / hr.)
Alarms: 95, Intent: com.facebook.push.mqtt.keepalive.KeepaliveManager.ACTION_INEXACT_ALARM.com.facebook.katana
Alarms: 31, Intent: com.facebook.analytics.service.AnalyticsEventUploader.ACTION_ALARM
Alarms: 47, Intent: com.facebook.common.executors.WakingExecutorService.ACTION_ALARM.com.facebook.katana
Alarms: 0, Intent: JewelCountFetcher.INITIATE_BACKGROUND_FETCH cmp={com.facebook.katana/com.facebook.notifications.util.JewelCountFetcher$JewelCountBroadcastReceiver}
Alarms: 0, Intent: {com.facebook.katana/com.facebook.videoads.scheduler.VideoAdsFetchService}
Alarms: 0, Intent: com.facebook.orca.database.ACTION_ALARM cmp={com.facebook.katana/com.facebook.contacts.database.AddressBookPeriodicRunner$LocalBroadcastReceiver}
com.facebook.orca (): Wakeups: 158 (22,0 / hr.)
Alarms: 93, Intent: com.facebook.push.mqtt.keepalive.b.ACTION_INEXACT_ALARM.com.facebook.orca
Alarms: 30, Intent: com.facebook.analytics.service.b.ACTION_ALARM
Alarms: 35, Intent: com.facebook.common.executors.ch.ACTION_ALARM.com.facebook.orca
Alarms: 0, Intent: com.facebook.orca.database.ACTION_ALARM cmp={com.facebook.orca/com.facebook.contacts.database.AddressBookPeriodicRunner$LocalBroadcastReceiver}
com.nuance.swype.dtc (): Wakeups: 102 (14,2 / hr.)
Alarms: 102, Intent: {com.nuance.swype.dtc/com.nuance.swype.connect.ConnectClient}
com.whatsapp (): Wakeups: 95 (13,2 / hr.)
Alarms: 0, Intent: ALARM_ACTION
Alarms: 37, Intent: com.whatsapp.messaging.MessageService.CLIENT_PINGER_ACTION
Alarms: 40, Intent: ALARM_CLIENT_PING_TIMEOUT
Alarms: 10, Intent: ALARM_AVAILABLE_TIMEOUT
Alarms: 5, Intent: com.whatsapp.messaging.MessageService.LOGOUT_ACTION
Alarms: 3, Intent: com.whatsapp.MessageService.RECONNECT cmp={com.whatsapp/com.whatsapp.messaging.MessageService}
Alarms: 0, Intent: ALARM_MESSAGES_DB_BACKUP
Alarms: 0, Intent: ALARM_ROTATE_LOGS
org.yoki.android.buienalarm (): Wakeups: 86 (12,0 / hr.)
Alarms: 0, Intent: android.appwidget.action.APPWIDGET_UPDATE cmp={org.yoki.android.buienalarm/org.yoki.android.buienalarm.BuienAlarmWidget}
Alarms: 86, Intent: org.yoki.android.buienalarm.UPDATE_START
com.google.android.gms (): Wakeups: 52 (7,2 / hr.)
Alarms: 24, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 14, Intent: {com.google.android.gms/com.google.android.gms.checkin.EventLogService$Receiver}
Alarms: 11, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.playlog.uploader.UploaderAlarmReceiver}
Alarms: 1, Intent: {com.google.android.gms/com.google.android.gms.checkin.CheckinService$Receiver}
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.common.download.DownloadAlarmReceiver}
Alarms: 0, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 1, Intent: com.google.android.gms.auth.authzen.CHECK_REGISTRATION
Alarms: 1, Intent: {com.google.android.gms/com.google.android.gms.security.snet.SnetService}
Alarms: 0, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE cmp={com.google.android.gms/com.google.android.gms.icing.service.IndexWorkerService}
net.nurik.roman.dashclock (): Wakeups: 14 (1,9 / hr.)
Alarms: 14, Intent: com.google.android.apps.dashclock.action.PERIODIC_ALARM cmp={net.nurik.roman.dashclock/com.google.android.apps.dashclock.PeriodicExtensionRefreshReceiver}
com.ing.mobile (): Wakeups: 7 (1,0 / hr.)
Alarms: 7, Intent: {com.ing.mobile/com.ing.mobile.service.INGService}
com.google.android.apps.maps (): Wakeups: 7 (1,0 / hr.)
Alarms: 7, Intent: {com.google.android.apps.maps/com.google.android.apps.gmm.prefetch.PrefetcherService}
com.spacegame.forestmania (): Wakeups: 4 (0,6 / hr.)
Alarms: 1, Intent: 6 cmp={com.spacegame.forestmania/com.zegame.erasegame.AlarmReceiver}
Alarms: 1, Intent: 7 cmp={com.spacegame.forestmania/com.zegame.erasegame.AlarmReceiver}
Alarms: 0, Intent: 2 cmp={com.spacegame.forestmania/com.zegame.erasegame.AlarmReceiver}
Alarms: 2, Intent: 4 cmp={com.spacegame.forestmania/com.zegame.erasegame.AlarmReceiver}
org.telegram.messenger (): Wakeups: 4 (0,2 / hr.)
Alarms: 4, Intent: {org.telegram.messenger/org.telegram.android.NotificationRepeat}
com.android.phone (): Wakeups: 2 (0,3 / hr.)
Alarms: 2, Intent: com.android.internal.telephony.data-stall
Alarms: 0, Intent: com.android.phone.UPDATE_CALLER_INFO_CACHE cmp={com.android.phone/com.android.phone.CallerInfoCacheUpdateReceiver}
Alarms: 0, Intent: com.android.internal.telephony.dataconnection.DataConnection.DC-2.action_retry
com.android.keyguard (): Wakeups: 2 (0,1 / hr.)
Alarms: 2, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
com.agilesoftresource (): Wakeups: 1 (0,1 / hr.)
Alarms: 0, Intent: ALM cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
Alarms: 1, Intent: CSR cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
======================
Network (requires root)
======================
10014 (Wifi) (Google Play-services): 126.0 MBytes 62,9%
0 (Wifi) (0): 62.0 MBytes 30,8%
10123 (Wifi) (com.dropbox.android.Dropbox): 5.0 MBytes 2,8%
10163 (Wifi) (com.spacegame.forestmania.Forest Mania): 2.0 MBytes 1,1%
10073 (Wifi) (org.telegram.messenger.Telegram): 846.0 KBytes 0,4%
10117 (Wifi) (com.facebook.katana.Facebook): 834.0 KBytes 0,4%
10029 (Wifi) (com.android.exchange.Exchange Services): 723.0 KBytes 0,4%
10118 (Wifi) (com.estrongs.android.pop.ES File Explorer): 336.0 KBytes 0,2%
10157 (Wifi) (com.facebook.orca.Messenger): 289.0 KBytes 0,1%
10091 (Wifi) (nl.sanomamedia.android.nu.NU.nl): 275.0 KBytes 0,1%
10044 (Wifi) (com.android.email.E-mail): 271.0 KBytes 0,1%
10052 (Wifi) (com.teslacoilsw.launcher.Nova Launcher): 228.0 KBytes 0,1%
10066 (Wifi) (com.whatsapp.WhatsApp): 220.0 KBytes 0,1%
10133 (Wifi) (org.yoki.android.buienalarm.Buienalarm): 200.0 KBytes 0,1%
10020 (Wifi) (com.android.vending.Google Play Store): 129.0 KBytes 0,1%
10091 (Mobile) (nl.sanomamedia.android.nu.NU.nl): 98.0 KBytes 0,0%
10137 (Wifi) (com.asksven.betterbatterystats.BetterBatteryStats): 82.0 KBytes 0,0%
10074 (Wifi) (com.nuance.swype.dtc.Swype + Dragon): 43.0 KBytes 0,0%
10138 (Wifi) (com.ing.mobile.Bankieren): 39.0 KBytes 0,0%
10117 (Mobile) (com.facebook.katana.Facebook): 31.0 KBytes 0,0%
1014 (Wifi) (1014): 30.0 KBytes 0,0%
1000 (Wifi) (Android-systeem): 29.0 KBytes 0,0%
0 (Mobile) (0): 26.0 KBytes 0,0%
10029 (Mobile) (com.android.exchange.Exchange Services): 22.0 KBytes 0,0%
10128 (Wifi) (com.android.chrome.Chrome): 21.0 KBytes 0,0%
10063 (Wifi) (com.hbwares.wordfeud.full.Wordfeud): 18.0 KBytes 0,0%
10076 (Wifi) (com.skype.raider.Skype): 12.0 KBytes 0,0%
10157 (Mobile) (com.facebook.orca.Messenger): 11.0 KBytes 0,0%
10098 (Wifi) (com.google.android.apps.maps.Maps): 9.0 KBytes 0,0%
10061 (Wifi) (cn.wps.moffice_eng.WPS Office (Kingsoft Office)): 7.0 KBytes 0,0%
10098 (Mobile) (com.google.android.apps.maps.Maps): 7.0 KBytes 0,0%
10073 (Mobile) (org.telegram.messenger.Telegram): 3.0 KBytes 0,0%
10014 (Mobile) (Google Play-services): 2.0 KBytes 0,0%
10133 (Mobile) (org.yoki.android.buienalarm.Buienalarm): 1.0 KBytes 0,0%
10076 (Mobile) (com.skype.raider.Skype): 1.0 KBytes 0,0%
1000 (Mobile) (Android-systeem): 1.0 KBytes 0,0%
10074 (Mobile) (com.nuance.swype.dtc.Swype + Dragon): 1.0 KBytes 0,0%
10146 (Wifi) (com.agilesoftresource.AndroZip File Manager): 1.0 KBytes 0,0%
10043 (Wifi) (com.slim.ota.SlimCenter): 52.0 Bytes 0,0%
==========
CPU States
==========
1,73 GHz (): 2 h 34 m 32 s 35,8%
1,67 GHz (): 23 s 0,1%
1,57 GHz (): 8 m 42 s 2,0%
1,46 GHz (): 2 m 3 s 0,5%
1,35 GHz (): 2 m 3 s 0,5%
1,24 GHz (): 2 m 19 s 0,5%
1,13 GHz (): 2 m 36 s 0,6%
1,03 GHz (): 1 h 12 m 33 s 16,8%
918 MHz (): 2 m 29 s 0,6%
810 MHz (): 2 m 17 s 0,5%
702 MHz (): 2 m 29 s 0,6%
594 MHz (): 2 m 39 s 0,6%
486 MHz (): 2 m 44 s 0,6%
384 MHz (): 41 m 54 s 9,7%
Deep Sleep (): 2 h 11 m 54 s 30,6%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 1 m 13 s (Wl: 0 elements; KWl: 0elements; NetS: 0 elements; Alrm: 0 elements; Proc: 0 elements; Oth: 0 elements; CPU: 11 elements)
ref_charged: Reference ref_charged created 15 h 48 m 3 s (Wl: 1 elements; KWl: 35elements; NetS: 48 elements; Alrm: 21 elements; Proc: 0 elements; Oth: 8 elements; CPU: 15 elements)
ref_unplugged: Reference ref_unplugged created 22 h 58 m 14 s (Wl: 40 elements; KWl: 35elements; NetS: 51 elements; Alrm: 23 elements; Proc: 158 elements; Oth: 12 elements; CPU: 15 elements)
ref_current: Reference ref_current created 22 h 59 m 48 s (Wl: 40 elements; KWl: 35elements; NetS: 52 elements; Alrm: 23 elements; Proc: 159 elements; Oth: 12 elements; CPU: 15 elements)

[Help] Screen turning on and on again.

Hello Guys,
lately something happend to my S3 Mini and i was trying to analyze it but i am not able to locate the problem alone.
The problem is that my S3 Mini (even when is not in use) is turning screen constinously on. It cause huge battery drain and i can not use it anymore as my battery lasts only for 4-6 hours of normal use.
I have also tried couple of things: factory reset, system changes (CM12, CM11, Original 4.1.2 - currently in use), replacement of battery - no influance to this behaviour.
I have charged phone to 100% and then leave it in flight mode (without sim/sd card) to minimize number of events and then left the phone to gather some data. I have tried to analyze logs from Better Battery Stats but it is to hard for my. Could you please take a look at my phone logs and maybe give some hint what may be a problem?
PS. sorry for my poor english
Here are some stats:
============
Battery Info
============
Level lost [%]: Bat.: -84%(100% to 16%) [2.1%/h]
Voltage lost [mV]: (4222-3619) [15.0%/h]
===========
Other Usage
===========
Deep Sleep (): 1 d 7 h 5 m 30 s 77.2%
Awake (): 9 h 10 m 56 s 22.8%
Screen On (): 8 h 31 m 42 s 21.2%
Wifi On (): 24 m 45 s 1.0%
Wifi Running (): 24 m 36 s 1.0%
No Data Connection (): 1 d 16 h 16 m 26 s 100.0%
No or Unknown Signal (): 1 d 16 h 16 m 26 s 100.0%
Screen dark (): 8 h 31 m 42 s 21.2%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
PhoneWindowManager.mBroadcastWakeLock (Android System): 21 m 24 s Count:3001 0.9%
sleep_broadcast (Android System): 15 m 10 s Count:8583 0.6%
reset keyguard (Android System): 7 m 27 s Count:12638 0.3%
AlarmManager (Android System): 1 m 4 s Count:16282 0.0%
ActivityManager-Launch (Android System): 36 s Count:215 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 18 s Count:6 0.0%
keyguardWakeAndHandOff (Android System): 17 s Count:15435 0.0%
FaceDetectionService (Android System): 12 s Count:12656 0.0%
WifiStateMachine (Android System): 10 s Count:12668 0.0%
AudioOut_2 (1013): 9 s Count:3 0.0%
DHCP (Android System): 8 s Count:12652 0.0%
Event Log Service (Google Services): 8 s Count:88 0.0%
RILJ (Phone): 7 s Count:5584 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 5 s Count:254 0.0%
AlarmManager (Google Services): 4 s Count:368 0.0%
SCREEN_FROZEN (Android System): 4 s Count:12646 0.0%
Checkin Service (Google Services): 2 s Count:266 0.0%
ActivityManager-Sleep (Android System): 2 s Count:16304 0.0%
NetworkStats (Android System): 2 s Count:121 0.0%
show keyguard (Android System): 1 s Count:4 0.0%
Event Log Handoff (Google Services): 1 s Count:248 0.0%
AlarmManager (com.google.android.apps.maps.Maps): 1 s Count:159 0.0%
DownloadManager (Media): 1 s Count:1 0.0%
WifiSuspend (Android System): 1 s Count:9873 0.0%
AudioIn_86 (1013): 1 s Count:6 0.0%
GpsLocationProvider (Android System): 1 s Count:3010 0.0%
GTALK_CONN (Google Services): 1 s Count:167 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 24 m 41 s Cnt: (c/wc/ec)3975/0/0 1.0%
"mali_wakelock" (): 19 m 8 s Cnt: (c/wc/ec)4258/0/0 0.8%
"radio-interface" (): 3 m 49 s Cnt: (c/wc/ec)235/0/0 0.2%
"alarm_rtc" (): 2 m 55 s Cnt: (c/wc/ec)205/201/153 0.1%
"svnet" (): 1 m 53 s Cnt: (c/wc/ec)235/0/235 0.1%
"alarm" (): 35 s Cnt: (c/wc/ec)1098/7/0 0.0%
"sec-battery-monitor" (): 31 s Cnt: (c/wc/ec)1305/13/0 0.0%
"KeyEvents" (): 8 s Cnt: (c/wc/ec)65666/0/0 0.0%
"power-supply" (): 6 s Cnt: (c/wc/ec)1116/0/0 0.0%
"deleted_wake_locks" (): Cnt: (c/wc/ec)25601/0/233 0.0%

Database Develop

welcome

[Q] S5 Active - Help with determing source of battery drain - AT&T Samsung Galaxy S 5

Have u checked the cpu? It could be hanging. Samsung unlock Bootloader on SM-870A.

Yeah, it doesn't appear to be out of control

From what i understand i believe its literally not possible fot a recovery to use battery, so theres nothing really for you to investigate. Sent from my SM-G900A using Tapatalk

Seems to me that u should stay on stock slot then u have drain under control. No that's not what u wanted to hear. AT&T u unlocked Lg G3 how about Sm-870A & Sm-900A.

Related

baseband_xmm_power wakelock

[Q] How to reduce the 6 sec data-transfer wakelock?

New Moto X user - Battery problem

[Q] Battery drain on wifi @work

[Help] Screen turning on and on again.

Categories

Resources