Database Develop

[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

[Battery GURU] Battery Myths/Problems/Questions [CALIBRATION + MORE]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tired of seeing thread where you need to calibrate the battery or discharge it and fully charge it and or stuff like you need to charge it over night
so this thread will prevent you from going FULL stupid/retard and will save your phone's battery!
Lets begin shall we..
with older battery technologies they would loose capacity until they are calibrated 0% to 100% this is due to the chemistry of the battery is based on Nickel
LI-ON battery's have a different chemistry which allows them to store greater capacity without loss like NI-CAD and NIMH did this is why you turn off your phone for a week and turn it on you find it still has about the same battery percentage as you turned it off before.
here's an example of a NI-CAD battery which needs to be calibrated.
You have a drill you haven't used for 3 days it was fully charged before you put it away if you take that same drill 3 days later you'd find it dead. where as LI-ON battery's would still be alive and full capacity. if you charge it from there it wouldn't be calibrated. as calibration requires you to drain the battery 2 times or more till it reaches it full capacity and charge it back up to 100% and repeat.
If you were to do that with a LI-ON battery you're basically doing nothing but wasting your charge cycles on the battery and you could kill it as LI-ON battery's DO NOT LIKE TO BE EMPTY
Because of all that NI-CAD and NIMH mess mostly all power tools you'd find in a shop such as home depot are now equipped with LI-ON battery's as they don't require calibration and can be left for months and it would still have its initial capacity prior to charging because Ni-cad battery's suffer from a memory effect and LI-ON does not, NI-CAD Requires full discharge before recharge LI-ON does not you get the point here right? LI-ON is better!
Now for those apps that claim calibrate the battery they do nothing they just Improve the reading of the software in android to get the battery percentage which is reset every time the battery charges to 100% so in short don't calibrate your battery, You don't need to drain it to Zero then charge to 100, you don't need to charge it overnight
You can read more here http://www.diffen.com/difference/Li-ion_vs_NiCad
and watch this video: http://www.youtube.com/watch?v=hrcbcm11830
Any Questions ask them here and i or someone will answer it​

I hope people listen to you. For every new phone that comes out, there is always a thread saying "Do i need to calibrate the battery?".

Let's put you to the test shall we?
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2014-01-21 06:50:20
Statistic Type: Screen Off to Current
Since 3 h 32 m 44 s
VERSION.RELEASE: 4.4.2
BRAND: Google
DEVICE: hammerhead
MANUFACTURER: LGE
MODEL: Nexus 5
OS.VERSION: 3.4.0-ElementalX-0.24+
BOOTLOADER: HHZ11k
HARDWARE: hammerhead
FINGERPRINT: google/hammerhead/hammerhead:4.4.2/KOT49H/937116:user/release-keys
ID: KOT49H
TAGS: test-keys
USER: dariosf
PRODUCT: hammerhead
RADIO: M8974A-1.0.25.0.13
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -17% (100% to 83%) [4.8%/h]
Voltage lost [mV]: (4273-4053) [62.1%/h]
===========
Other Usage
===========
Deep Sleep (): 3 h 29 m 2 s (12542 s) Ratio: 98.3%
Awake (): 3 m 41 s (221 s) Ratio: 1.7%
Screen On (): 15 s (15 s) Ratio: 0.1%
Screen dark (): 15 s (15 s) Ratio: 0.1%
=========
Wakelocks
=========
AlarmManager (Android System): 5 s (5 s) Count:105 0.0%
AlarmClock (com.android.deskclock.Clock): 5 s (5 s) Count:7 0.0%
StartingAlertService (com.google.android.calendar.Calendar): 5 s (5 s) Count:1 0.0%
AudioMix (com.android.deskclock.Clock): 5 s (5 s) Count:8 0.0%
AudioMix (1013): 3 s (3 s) Count:2 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 1 s (1 s) Count:3 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
bam_dmux_wakelock (): 2 m 49 s (169 s) Cntc/wc/ec)84/2/0 1.3%
PowerManagerService.WakeLocks (): 14 s (14 s) Cntc/wc/ec)116/2/0 0.1%
event0-936 (): 12 s (12 s) Cntc/wc/ec)126/0/0 0.1%
event1-936 (): 12 s (12 s) Cntc/wc/ec)126/0/0 0.1%
event2-936 (): 12 s (12 s) Cntc/wc/ec)126/0/0 0.1%
alarm (): 9 s (9 s) Cntc/wc/ec)106/1/0 0.1%
alarm_rtc (): 3 s (3 s) Cntc/wc/ec)52/2/0 0.0%
event4-936 (): 2 s (2 s) Cntc/wc/ec)129/1/0 0.0%
event5-936 (): 2 s (2 s) Cntc/wc/ec)129/1/0 0.0%
event6-936 (): 2 s (2 s) Cntc/wc/ec)129/1/0 0.0%
max17048_alert (): 1 s (1 s) Cntc/wc/ec)87/1/0 0.0%
qpnp-vadc-ee205e00 (): 1 s (1 s) Cntc/wc/ec)286/3/0 0.0%
qpnp-iadc-ee206000 (): (0 s) Cntc/wc/ec)123/1/0 0.0%
smsm_snapshot (): (0 s) Cntc/wc/ec)217/2/0 0.0%
power-supply (): (0 s) Cntc/wc/ec)6/0/0 -0.0%
KeyEvents (): (0 s) Cntc/wc/ec)217/1/0 0.0%
PowerManagerService.Broadcasts (): (0 s) Cntc/wc/ec)1/0/0 0.0%
======================
Alarms (requires root)
======================
com.android.phone (): Wakeups: 30
Alarms: 30, 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}
android (): Wakeups: 19
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 13, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 2, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 3, Intent: android.app.backup.intent.RUN
Alarms: 1, Intent: com.android.server.IdleMaintenanceService.action.UPDATE_IDLE_MAINTENANCE_STATE
com.google.android.gms (): Wakeups: 7
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.playlog.uploader.UploaderAlarmReceiver}
Alarms: 6, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 0, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE cmp={com.google.android.gms/com.google.android.gms.icing.service.IndexWorkerService}
Alarms: 0, Intent: com.google.android.intent.action.GCM_RECONNECT
com.google.android.gsf (): Wakeups: 6
Alarms: 6, Intent: {com.google.android.gsf/com.google.android.gsf.checkin.EventLogService$Receiver}
com.android.deskclock (): Wakeups: 4
Alarms: 4, Intent: change_state cmp={com.android.deskclock/com.android.deskclock.alarms.AlarmStateManager}
com.rageconsulting.android.lightflow (): Wakeups: 1
Alarms: 1, Intent: {com.rageconsulting.android.lightflow/com.rageconsulting.android.lightflow.receiver.OnAlarmReceiver}
com.whatsapp (): Wakeups: 1
Alarms: 0, Intent: ALARM_ACTION
Alarms: 1, Intent: ALARM_MESSAGES_DB_BACKUP
Alarms: 0, Intent: ALARM_ROTATE_LOGS
======================
Network (requires root)
======================
10008 (Mobile) (Google Play services): 6.0 KBytes 42.9%
10087 (Mobile) (com.handmark.expressweather.1Weather): 4.0 KBytes 28.8%
0 (Mobile) (0): 4.0 KBytes 26.9%
0 (lo) (0): 140.0 Bytes 0.9%
10075 (lo) (com.google.android.gallery3d.Gallery): 100.0 Bytes 0.6%
==========
CPU States
==========
300 MHz (): 2 m 32 s 1.2%
422.4 MHz (): 3 s 0.0%
652.8 MHz (): 11 s 0.1%
729.6 MHz (): 1 s 0.0%
883.2 MHz (): 2 s 0.0%
960 MHz (): 0.0%
1.04 GHz (): 4 s 0.0%
1.19 GHz (): 34 s 0.3%
1.27 GHz (): 8 s 0.1%
1.5 GHz (): 1 s 0.0%
1.57 GHz (): 0.0%
1.73 GHz (): 0.0%
1.96 GHz (): 0.0%
2.27 GHz (): 0.0%
Deep Sleep (): 3 h 29 m 2 s 98.3%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 38 s (Wl: 1 elements; KWl: 8elements; NetS: 7 elements; Alrm: 0 elements; Proc: 6 elements; Oth: 3 elements; CPU: 14 elements)
ref_unplugged: Reference ref_unplugged created 5 h 37 m 30 s (Wl: 0 elements; KWl: 33elements; NetS: 17 elements; Alrm: 10 elements; Proc: 0 elements; Oth: 4 elements; CPU: 15 elements)
ref_charged: Reference ref_charged created 5 h 37 m 30 s (Wl: 0 elements; KWl: 33elements; NetS: 17 elements; Alrm: 10 elements; Proc: 0 elements; Oth: 4 elements; CPU: 15 elements)
ref_screen_off: Reference ref_screen_off created 5 h 37 m 34 s (Wl: 0 elements; KWl: 33elements; NetS: 17 elements; Alrm: 10 elements; Proc: 0 elements; Oth: 4 elements; CPU: 15 elements)
ref_current: Reference ref_current created 9 h 10 m 18 s (Wl: 6 elements; KWl: 33elements; NetS: 17 elements; Alrm: 11 elements; Proc: 34 elements; Oth: 4 elements; CPU: 15 elements)
The good and knowledgeable folks believe the source of my drain is a cell tower issue/APN issue but my APN's for Vodafone UK are correct and the drain doesn't seem to drain anything like this during the morning.
I'm at a loss to explain it but I only had such bad drain after 4.4.2.
I've tried factory resets, flashing factory images, flashing radios' kernels I've even changed network but the issue still persists.
Th drain per hour doesn't reflect the deep sleep time.

r0cafella said:
Let's put you to the test shall we?
The good and knowledgeable folks believe the source of my drain is a cell tower issue/APN issue but my APN's for Vodafone UK are correct and the drain doesn't seem to drain anything like this during the morning.
I'm at a loss to explain it but I only had such bad drain after 4.4.2.
I've tried factory resets, flashing factory images, flashing radios' kernels I've even changed network but the issue still persists.
Th drain per hour doesn't reflect the deep sleep time.
Click to expand...
Click to collapse
Yeah that's pretty bad, but that has nothing to do with this thread. Try posting in the "post your battery" thread and see if someone fixed it there.

r0cafella said:
Let's put you to the test shall we?
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2014-01-21 06:50:20
Statistic Type: Screen Off to Current
Since 3 h 32 m 44 s
VERSION.RELEASE: 4.4.2
BRAND: Google
DEVICE: hammerhead
MANUFACTURER: LGE
MODEL: Nexus 5
OS.VERSION: 3.4.0-ElementalX-0.24+
BOOTLOADER: HHZ11k
HARDWARE: hammerhead
FINGERPRINT: google/hammerhead/hammerhead:4.4.2/KOT49H/937116:user/release-keys
ID: KOT49H
TAGS: test-keys
USER: dariosf
PRODUCT: hammerhead
RADIO: M8974A-1.0.25.0.13
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -17% (100% to 83%) [4.8%/h]
Voltage lost [mV]: (4273-4053) [62.1%/h]
===========
Other Usage
===========
Deep Sleep (): 3 h 29 m 2 s (12542 s) Ratio: 98.3%
Awake (): 3 m 41 s (221 s) Ratio: 1.7%
Screen On (): 15 s (15 s) Ratio: 0.1%
Screen dark (): 15 s (15 s) Ratio: 0.1%
=========
Wakelocks
=========
AlarmManager (Android System): 5 s (5 s) Count:105 0.0%
AlarmClock (com.android.deskclock.Clock): 5 s (5 s) Count:7 0.0%
StartingAlertService (com.google.android.calendar.Calendar): 5 s (5 s) Count:1 0.0%
AudioMix (com.android.deskclock.Clock): 5 s (5 s) Count:8 0.0%
AudioMix (1013): 3 s (3 s) Count:2 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 1 s (1 s) Count:3 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
bam_dmux_wakelock (): 2 m 49 s (169 s) Cntc/wc/ec)84/2/0 1.3%
PowerManagerService.WakeLocks (): 14 s (14 s) Cntc/wc/ec)116/2/0 0.1%
event0-936 (): 12 s (12 s) Cntc/wc/ec)126/0/0 0.1%
event1-936 (): 12 s (12 s) Cntc/wc/ec)126/0/0 0.1%
event2-936 (): 12 s (12 s) Cntc/wc/ec)126/0/0 0.1%
alarm (): 9 s (9 s) Cntc/wc/ec)106/1/0 0.1%
alarm_rtc (): 3 s (3 s) Cntc/wc/ec)52/2/0 0.0%
event4-936 (): 2 s (2 s) Cntc/wc/ec)129/1/0 0.0%
event5-936 (): 2 s (2 s) Cntc/wc/ec)129/1/0 0.0%
event6-936 (): 2 s (2 s) Cntc/wc/ec)129/1/0 0.0%
max17048_alert (): 1 s (1 s) Cntc/wc/ec)87/1/0 0.0%
qpnp-vadc-ee205e00 (): 1 s (1 s) Cntc/wc/ec)286/3/0 0.0%
qpnp-iadc-ee206000 (): (0 s) Cntc/wc/ec)123/1/0 0.0%
smsm_snapshot (): (0 s) Cntc/wc/ec)217/2/0 0.0%
power-supply (): (0 s) Cntc/wc/ec)6/0/0 -0.0%
KeyEvents (): (0 s) Cntc/wc/ec)217/1/0 0.0%
PowerManagerService.Broadcasts (): (0 s) Cntc/wc/ec)1/0/0 0.0%
======================
Alarms (requires root)
======================
com.android.phone (): Wakeups: 30
Alarms: 30, 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}
android (): Wakeups: 19
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 13, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 2, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 3, Intent: android.app.backup.intent.RUN
Alarms: 1, Intent: com.android.server.IdleMaintenanceService.action.UPDATE_IDLE_MAINTENANCE_STATE
com.google.android.gms (): Wakeups: 7
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.playlog.uploader.UploaderAlarmReceiver}
Alarms: 6, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 0, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE cmp={com.google.android.gms/com.google.android.gms.icing.service.IndexWorkerService}
Alarms: 0, Intent: com.google.android.intent.action.GCM_RECONNECT
com.google.android.gsf (): Wakeups: 6
Alarms: 6, Intent: {com.google.android.gsf/com.google.android.gsf.checkin.EventLogService$Receiver}
com.android.deskclock (): Wakeups: 4
Alarms: 4, Intent: change_state cmp={com.android.deskclock/com.android.deskclock.alarms.AlarmStateManager}
com.rageconsulting.android.lightflow (): Wakeups: 1
Alarms: 1, Intent: {com.rageconsulting.android.lightflow/com.rageconsulting.android.lightflow.receiver.OnAlarmReceiver}
com.whatsapp (): Wakeups: 1
Alarms: 0, Intent: ALARM_ACTION
Alarms: 1, Intent: ALARM_MESSAGES_DB_BACKUP
Alarms: 0, Intent: ALARM_ROTATE_LOGS
======================
Network (requires root)
======================
10008 (Mobile) (Google Play services): 6.0 KBytes 42.9%
10087 (Mobile) (com.handmark.expressweather.1Weather): 4.0 KBytes 28.8%
0 (Mobile) (0): 4.0 KBytes 26.9%
0 (lo) (0): 140.0 Bytes 0.9%
10075 (lo) (com.google.android.gallery3d.Gallery): 100.0 Bytes 0.6%
==========
CPU States
==========
300 MHz (): 2 m 32 s 1.2%
422.4 MHz (): 3 s 0.0%
652.8 MHz (): 11 s 0.1%
729.6 MHz (): 1 s 0.0%
883.2 MHz (): 2 s 0.0%
960 MHz (): 0.0%
1.04 GHz (): 4 s 0.0%
1.19 GHz (): 34 s 0.3%
1.27 GHz (): 8 s 0.1%
1.5 GHz (): 1 s 0.0%
1.57 GHz (): 0.0%
1.73 GHz (): 0.0%
1.96 GHz (): 0.0%
2.27 GHz (): 0.0%
Deep Sleep (): 3 h 29 m 2 s 98.3%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 38 s (Wl: 1 elements; KWl: 8elements; NetS: 7 elements; Alrm: 0 elements; Proc: 6 elements; Oth: 3 elements; CPU: 14 elements)
ref_unplugged: Reference ref_unplugged created 5 h 37 m 30 s (Wl: 0 elements; KWl: 33elements; NetS: 17 elements; Alrm: 10 elements; Proc: 0 elements; Oth: 4 elements; CPU: 15 elements)
ref_charged: Reference ref_charged created 5 h 37 m 30 s (Wl: 0 elements; KWl: 33elements; NetS: 17 elements; Alrm: 10 elements; Proc: 0 elements; Oth: 4 elements; CPU: 15 elements)
ref_screen_off: Reference ref_screen_off created 5 h 37 m 34 s (Wl: 0 elements; KWl: 33elements; NetS: 17 elements; Alrm: 10 elements; Proc: 0 elements; Oth: 4 elements; CPU: 15 elements)
ref_current: Reference ref_current created 9 h 10 m 18 s (Wl: 6 elements; KWl: 33elements; NetS: 17 elements; Alrm: 11 elements; Proc: 34 elements; Oth: 4 elements; CPU: 15 elements)
The good and knowledgeable folks believe the source of my drain is a cell tower issue/APN issue but my APN's for Vodafone UK are correct and the drain doesn't seem to drain anything like this during the morning.
I'm at a loss to explain it but I only had such bad drain after 4.4.2.
I've tried factory resets, flashing factory images, flashing radios' kernels I've even changed network but the issue still persists.
Th drain per hour doesn't reflect the deep sleep time.
Click to expand...
Click to collapse
Download an app on the play store called signal check and report to me the dbm or screenshot the app opened thanks
Sent from my iPhone using Tapatalk

markdapimp said:
Download an app on the play store called signal check and report to me the dbm or screenshot the app opened thanks
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Right now:
-94DBM *45 ASU.
However at present the drain which I described isn't present.
I'll check back in tomorrow however at work the signal strength is about the same.

I'm sorry but what you write is confusing, misleading and most importantly partially wrong!
Your main message might contain some truth, but your justification is wrong.
Without knowing it you mix up a lot of different properties like 'Memory effect, self discharge, energy density, ...' and try to use those effects to justify your guide.
Li-Ion have a self-discharge, just like Ni-Cd or Ni-Mh, it's just not as bad, but still worse than modern Eneloop Ni-Mh batteries. Your Ni-Mh tool won't be empty after three days (except your batteries are broken), but after maybe two to three months. Your Li-Ion powered keeps the charge about three times longer, but still just as long as a Ni-Cd powered tool. This self-discharge has nothing to do with calibration.
http://en.wikipedia.org/wiki/Lithium-ion_battery#Self-discharge
Modern tools use Li-Ion batteries instead of Ni-Mh because they don't suffer from the memory effect (no need to refresh the batteries) but mainly because they can store much more energy at the same volume. About twice as much as Ni-Mh. Again, this has nothing to do with calibration:
http://en.wikipedia.org/wiki/Energy_density#Energy_densities_of_common_energy_storage_materials
By calibration you mix up different use terms:
Do you want to adress the myth that a Li-Ion battery takes several charges until it unfolds it full energy capacity.
Or do you want to adress the myth that the charging circuit might use misleading informations and thus calculates and displays wrong capacity values?
Or do you want to adress the myth that a Li-Ion battery has a memory effect and thus needs once in a while a full discharge/recharge to gain full capacity again like people tend to do with Ni-Mh?
Or do you talk about something else.
Whatever you do, read a proper guide first please:
http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
Then either delete your misleading post or correct it accordingly. Right now it's garbage, sorry.

What needs to be addressed is people looking at a problem that won't exists for months to years. Charge controller calibration problems generally only appear on old well worn cells.
NiCad "calibration" was a physical one, Lithium ion is purely controller. Its not in the nature of the battery chemistry but the fact that the controller is designed to prevent charging under certain conditions. Problems with capacity misreads shouldn't happen in the first year and thats why discussions by Nexus 5 owners shouldnt even exist yet.
A lithium ion/polymer controller should only need to be calibrated when the actual chemical capacity of the battery is much higher than the controllers (Calculated, Observed, Stored) value is way out of synch. A single deep discharge can actually harm the battery more than the difference you are trying to correct and it is NOT worth it. Until you wake up in the morning and the battery is reaching a full charge in 5 minutes from dead just put the battery in the back of your head.

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

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

[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%

Battery use on SM-N910T Note 4 - How much time should Wi-Fi be on?

About 6 months ago my Note 4 suddenly lost half its battery life. No new applications were installed at that time, but there was a "security update". I've replaced the battery twice, but the significantly reduced battery life continues.
I purchased BetterBatteryStats to help understand what's going on.
The only thing that caught my attention is Wi-Fi On and Wi-Fi running are both 100%. Is that typical? If not, what settings control it?
I have "Keep Wi-Fi on during sleep" set to "only when plugged in", and "Always allow scanning" is unchecked.
Also I noticed that the log says "Root perms: false", but this phone has systemless root.
Dump File Unplugged to Current - approx 6 hours
Code:
/*
===================
General Information
===================
BetterBatteryStats version: 2.4-265
Creation Date: 2018-11-25 13:14:22
Statistic Type: Unplugged to Current
Since 6 h 42 m 5 s
Note:
VERSION.RELEASE: 5.1.1
BRAND: samsung
DEVICE: trltetmo
MANUFACTURER: samsung
MODEL: SM-N910T
OS.VERSION: 3.10.40-6209177
BOOTLOADER: N910TUVU2DOK2
HARDWARE: qcom
FINGERPRINT: samsung/trltetmo/trltetmo:5.1.1/LMY47X/N910TUVU2DOK2:user/release-keys
ID: LMY47X
TAGS: release-keys
USER: dpi
PRODUCT: trltetmo
RADIO: N910TUVU2DOK2
Root perms: false
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -19%(100% to 81%) [2.8%/h]
Voltage lost [mV]: (4348-4072) [41.2%/h]
===========
Other Usage
===========
Deep Sleep (): 4 h 40 m 27 s 69.7%
Awake (Screen Off) (): 1 h 48 m 59 s 27.1%
Screen On (): 12 m 41 s 3.2%
[COLOR="Red"]Wifi On (): 6 h 42 m 8 s 100.0%
Wifi Running (): 6 h 42 m 8 s 100.0%[/COLOR]
Doze Interactive Time (): 12 m 36 s 3.1%
Sync (): 2 m 18 s 0.6%
No Data Connection (): 2 h 20 m 14 s 34.9%
No or Unknown Signal (): 0.0%
Poor Signal (): 20 m 36 s 5.1%
Moderate Signal (): 27 m 45 s 6.9%
Good Signal (): 2 h 25 m 56 s 36.3%
Great Signal (): 1 h 53 m 42 s 28.3%
Screen dark (): 8 s 0.0%
Screen dimmed (): 6 m 2 s 1.5%
Screen medium (): 3 m 26 s 0.9%
Screen light (): 2 m 42 s 0.7%
Screen bright (): 21 s 0.1%
======================================================
Wakelocks
======================================================
SmartManager Framework Thread (Android System): 26 m 3 s Count:1869 6.5%
bluedroid_timer (com.android.bluetooth.Bluetooth): 10 m 46 s Count:215 2.7%
PollService wakeLockAcquire (com.fsck.k9.K-9 Mail): 5 m 28 s Count:150 1.4%
NlpWakeLock (Google Services): 5 m 10 s Count:4535 1.3%
Tasker.UserAbsentWakelock (net.dinglisch.android.tasker.Tasker): 4 m 7 s Count:78 1.0%
SyncEngineService (com.ninefolders.hd3.Nine): 3 m 22 s Count:65 0.8%
*alarm* (Android System): 1 m 37 s Count:944 0.4%
NlpWakeLock (com.google.android.googlequicksearchbox.Google): 1 m 27 s Count:766 0.4%
Icing (com.google.android.apps.messaging.Messages): 1 m 13 s Count:28 0.3%
bugle_datamodel_executor_wakelock (com.google.android.apps.messaging.Messages): 1 m 11 s Count:54 0.3%
<------snip - wakelocks less than 1 minute deleted------------>
================
Kernel Wakelocks
================
=========
Processes
=========
system (Android System): Uid: 1000 Sys: 12 m 49 s Us: 43 m 17 s Starts: 0
com.getpebble.android.basalt:framework (com.getpebble.android.basalt.Pebble): Uid: 10249 Sys: 4 m 28 s Us: 7 m 9 s Starts: 0
com.aa.android (com.aa.android.American Airlines): Uid: 10281 Sys: 2 m 6 s Us: 4 m 25 s Starts: 6
*wakelock* (com.android.bluetooth.Bluetooth): Uid: 1002 Sys: 2 m 31 s Us: 3 m 45 s Starts: 0
surfaceflinger (Android System): Uid: 1000 Sys: 2 m 42 s Us: 1 m 50 s Starts: 0
com.google.android.gms.persistent (Google Services): Uid: 10017 Sys: 1 m 7 s Us: 3 m Starts: 0
*wakelock* (Google Services): Uid: 10017 Sys: 1 m 40 s Us: 2 m 20 s Starts: 0
<------snip - processes less than 1 minute deleted------------>
======================
Network
======================
10102 (Wifi) (com.android.chrome.Chrome): 5.0 MBytes 30.6%
10073 (Wifi) (com.google.android.googlequicksearchbox.Google): 2.0 MBytes 14.4%
10269 (Mobile) (com.fsck.k9.K-9 Mail): 1.0 MBytes 6.9%
10017 (Mobile) (Google Services): 1.0 MBytes 6.8%
10073 (Mobile) (com.google.android.googlequicksearchbox.Google): 1.0 MBytes 6.7%
10256 (Mobile) (com.nstudio.weatherhere.NOAA Weather): 996.0 KBytes 5.8%
10269 (Wifi) (com.fsck.k9.K-9 Mail): 789.0 KBytes 4.6%
10257 (Mobile) (com.ninefolders.hd3.Nine): 672.0 KBytes 3.9%
10017 (Wifi) (Google Services): 558.0 KBytes 3.3%
10257 (Wifi) (com.ninefolders.hd3.Nine): 501.0 KBytes 2.9%
1000 (Mobile) (Android System): 312.0 KBytes 1.8%
10036 (Mobile) (com.android.vending.Google Play Store): 248.0 KBytes 1.5%
10256 (Wifi) (com.nstudio.weatherhere.NOAA Weather): 243.0 KBytes 1.4%
10212 (Mobile) (com.sec.android.daemonapp.Unified Daemon): 192.0 KBytes 1.1%
<------snip - network less than 1% deleted------------>
Additional parts of log are available if needed. (14K lines.....)