Database Develop

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

will someone take the time to help me with my wakelock issue

So first off I don't even know if I'm having wakelock issues but im pretty sure I am I just do not understand it..
So to get right to the point, in the gsam app it said I had very high "google services" wakelocks, 1795 to be exact (i will post screenshots in a second) and i didnt understand what this was so i downloaded the wakelock detector app and then everything just started getting confusing. as of now i have absolutely no clue what is keeping my device awake, all i know is that i am only getting about 12 hours off the charger and my phone is getting pretty warm even when not in use.
i do not have google now turned on, i downloaded greenify but i do not know which apps to hibernate, and i have auto sync turned off for now until i figure out whats causing my phones bad battery life
i am on viper 1.2.1
please, any information would be better than none at this point and this issues driving me freaking crazy

Yesterday's stats:
Sent from my HTC One using xda app-developers app

milesjohnson said:
So first off I don't even know if I'm having wakelock issues but im pretty sure I am I just do not understand it..
So to get right to the point, in the gsam app it said I had very high "google services" wakelocks, 1795 to be exact (i will post screenshots in a second) and i didnt understand what this was so i downloaded the wakelock detector app and then everything just started getting confusing. as of now i have absolutely no clue what is keeping my device awake, all i know is that i am only getting about 12 hours off the charger and my phone is getting pretty warm even when not in use.
i do not have google now turned on, i downloaded greenify but i do not know which apps to hibernate, and i have auto sync turned off for now until i figure out whats causing my phones bad battery life
i am on viper 1.2.1
please, any information would be better than none at this point and this issues driving me freaking crazy
Click to expand...
Click to collapse
Until you post that screenshot, for greenify, greenify everything, unless you want instant notifications on some apps. For ex, you will only receive whatsapp msgs when you open it if it'd greenified. I don't mind that. Try to do all apps.
Do you have betterbatterystats?
Sent from my HTC One

Some more stats
Sent from my HTC One using xda app-developers app

I don't see the big concern about number of wakelocks. If you switch Gsam app sucker to be by power usage, you'll see that Google services isn't even that high compared to other apps. If you don't need Google syncing or regular syncing you can Greenify Google services but it will affect how often your phone is able to interact with Google services.

chc31 said:
Until you post that screenshot, for greenify, greenify everything, unless you want instant notifications on some apps. For ex, you will only receive whatsapp msgs when you open it if it'd greenified. I don't mind that. Try to do all apps.
Do you have betterbatterystats?
Sent from my HTC One
Click to expand...
Click to collapse
ok i posted screenshots, looks like im getting high wake lock counts from xda (294) wallpaper lock screen (416) twitter (197) messages (243) i just realized some of those screenshots are mismatched with the proper day but are these pretty high or normal for an average day

can someone please help me i have tried countless times to get help over here on xda but it seems as if no one can help me and its driving me crazy. what am i doing wrong to not be getting help. am i not posting enough information in my posts? because i will gladly post more just tell me what i need to post in order for you guys to help me.
ive posted about 3 threads, posted in many battery stats threads and still cant get the help i need.
the reason im so concerned about these wakelocks is im only getting about 12 hours off the charger and im thinking once i figure out my wakelock problem ill get some better time off the charger. PLEASE I HATE TO BE THE ANNOYING NOOB BUT PLEASE HELP ME

Didn't you already make a thread?

a box of kittens said:
Didn't you already make a thread?
Click to expand...
Click to collapse
yes i did and i just want to get the help i need for this problem.

milesjohnson said:
can someone please help me i have tried countless times to get help over here on xda but it seems as if no one can help me and its driving me crazy. what am i doing wrong to not be getting help. am i not posting enough information in my posts? because i will gladly post more just tell me what i need to post in order for you guys to help me.
ive posted about 3 threads, posted in many battery stats threads and still cant get the help i need.
the reason im so concerned about these wakelocks is im only getting about 12 hours off the charger and im thinking once i figure out my wakelock problem ill get some better time off the charger. PLEASE I HATE TO BE THE ANNOYING NOOB BUT PLEASE HELP ME
Click to expand...
Click to collapse
Use BetterBatteryStats and check partial and kernel wakelocks. The screenshots don't really show the cause of keeping the phone awake. A high number of wakelocks isn't really a big deal if the phone goes back to sleep right away. I'd be more interested in amount of time something is keeping the phone awake.

tiny4579 said:
Use BetterBatteryStats and check partial and kernel wakelocks. The screenshots don't really show the cause of keeping the phone awake. A high number of wakelocks isn't really a big deal if the phone goes back to sleep right away. I'd be more interested in amount of time something is keeping the phone awake.
Click to expand...
Click to collapse
ok i just got BBS so do i let it run basically all day and then check back with you guys, should we both have a better understanding of whats keeping my phone awake, hell i might not even be having any problems but gsam and wakelock detector sure made it seem like i was.
will this be more accurate at detecting if my phone is running properly or not? ill report back at the end of today

milesjohnson said:
ok i just got BBS so do i let it run basically all day and then check back with you guys, should we both have a better understanding of whats keeping my phone awake, hell i might not even be having any problems but gsam and wakelock detector sure made it seem like i was.
will this be more accurate at detecting if my phone is running properly or not? ill report back at the end of today
Click to expand...
Click to collapse
I use BBS. It's good. Make sure you open the app at least once. LoL!! And if you're rooted that's better. Go into settings and enabled root features. This will show you alarms, which apps keep waking.
Charge your phone fully, then just act normally. BBS will do it's own thing. Try not to let your phone restart doing this time. If it restarts, BBS will show settings from the last boot.
Around 5% take some screen shots. Then we can see what apps keep waking your phone. That battery life doesn't sound good at all. Your standby time should be EXCELLENT on this phone. It's not like my GS2 where standby was just horrible regardless. (Witnessed on multiple phones) LoL!!
You can even start now. If you can leave your phone off the charger over night. That will yield the best results to see what's waking your phone when you do nothing.
I have Google Now and one email syncing. I leave GPS on and turn off WiFi when I'm not connected. I get great standby time. Those settings shouldn't be affecting your phone.
I don't have any apps to save energy. I let the built in Power Saver do that.

No_Nickname90 said:
I use BBS. It's good. Make sure you open the app at least once. LoL!! And if you're rooted that's better. Go into settings and enabled root features. This will show you alarms, which apps keep waking.
Charge your phone fully, then just act normally. BBS will do it's own thing. Try not to let your phone restart doing this time. If it restarts, BBS will show settings from the last boot.
Around 5% take some screen shots. Then we can see what apps keep waking your phone. That battery life doesn't sound good at all. Your standby time should be EXCELLENT on this phone. It's not like my GS2 where standby was just horrible regardless. (Witnessed on multiple phones) LoL!!
You can even start now. If you can leave your phone off the charger over night. That will yield the best results to see what's waking your phone when you do nothing.
I have Google Now and one email syncing. I leave GPS on and turn off WiFi when I'm not connected. I get great standby time. Those settings shouldn't be affecting your phone.
I don't have any apps to save energy. I let the built in Power Saver do that.
Click to expand...
Click to collapse
THANKYOU so much really helpful information, finally. atleast i know where to start! feel like 1000 pounds has been lifted off me as this has really been stressing me out because i KNOW i should be getting more than 12 hours off the charger.
im letting my phone charge up all the way now (about 10 minutes left). already opened bbs once so itll run in the background and i guess the next step from here would be to report back after todays usage.

Yes. And also there's no harm in checking in on BBS. Like after an hour or so you can go look to see if you see anything unusual. Like if you didn't use your phone for an hour, yet it was awake for an hour. LoL!! You might be able to catch the culprit early on.
You can also tap on the apps when viewing them to see what command keeps waking. So if Google Maps keeps waking that could mean there's an app that keeps looking for your location. On my GS2, the GPS was HORRIBLE, so it could never find a location. Well Facebook didn't care and kept looking for my location. I found that out when I noticed that my GPS icon would freeze while opening Facebook and I had to restart the phone.
Turning off GPS gave me less wakelock issues. That's how I knew it was tied to my GPS not getting a location.
You say Google Services keeps waking the device, so it may be an app that's using the service. It may not necessarily be Google's fault. Just some ideas to help you solve the issue.

milesjohnson said:
THANKYOU so much really helpful information, finally. atleast i know where to start! feel like 1000 pounds has been lifted off me as this has really been stressing me out because i KNOW i should be getting more than 12 hours off the charger.
im letting my phone charge up all the way now (about 10 minutes left). already opened bbs once so itll run in the background and i guess the next step from here would be to report back after todays usage.
Click to expand...
Click to collapse
In order to get the best results from BBS you have the leave the phone idle for 4 hours after unplugged. You're trying to find the cause of wake locks held by apps while not in use, so; open the app, if you have root enable root functions to see the alarms and processes, if not just set the app and charge the phone to 100%.
After you unplug do not use it... Leave it alone for about 4 hours or more. After that period of time run the app, in the menu you will see dump stats, click on it, find it on your SD card (probably /mnt/data/media or /sdcard/ depending on your Android version), put it here and will take a look for you.
Do not hibernate Google Services if you have apps using GCM structure (push). Google Services works together with Google Services Framework (com.android.gsf) to deliver the push messages from app servers to device.
Sent from my GT-I9300 using Tapatalk 2

bnbasarir said:
In order to get the best results from BBS you have the leave the phone idle for 4 hours after unplugged. You're trying to find the cause of wake locks held by apps while not in use, so; open the app, if you have root enable root functions to see the alarms and processes, if not just set the app and charge the phone to 100%.
After you unplug do not use it... Leave it alone for about 4 hours or more. After that period of time run the app, in the menu you will see dump stats, click on it, find it on your SD card (probably /mnt/data/media or /sdcard/ depending on your Android version), put it here and will take a look for you.
Do not hibernate Google Services if you have apps using GCM structure (push). Google Services works together with Google Services Framework (com.android.gsf) to deliver the push messages from app servers to device.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
okay i have left the phone idle for 4 hours i dont see the dump stats option in the menu so ill just post some screenshots from the app. i can dump stats if necessary though

Here are some screenshots from my five hours of not using the phone.
Sent from my HTC One using xda app-developers app

So these stats look pretty normal?
Sent from my HTC One using xda app-developers app

===================
General Information
===================
BetterBatteryStats version: 1.13.4.0B2
Creation Date: 2013-07-20 22:58:29
Statistic Type: Boot to Current
Since 6 h 9 m 4 s
VERSION.RELEASE: 4.2.2
BRAND: performance_test
DEVICE: m7
MANUFACTURER: HTC
MODEL: HTC One
OS.VERSION: 3.4.10-faux123-JB4.2.2-GE
BOOTLOADER: 1.54.0000
HARDWARE: m7
FINGERPRINT: performance_test/m7/m7:4.2.2/JDQ39/202917.1:user/release-keys
ID: JDQ39
TAGS: release-keys
USER: unknown
PRODUCT: m7
RADIO: 4A.17.3250.14_10.39.1150.04L
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -13% (90% to 77%) [2.1%/h]
Voltage lost [mV]: (4135-4035) [16.3%/h]
===========
Other Usage
===========
Deep Sleep (): 4 h 59 m 31 s (17971 s) Ratio: 81.0%
Awake (): 1 h 9 m 32 s (4172 s) Ratio: 18.8%
Screen On (): 27 m 41 s (1661 s) Ratio: 7.5%
Wifi On (): 8 m 5 s (485 s) Ratio: 2.2%
Wifi Running (): 8 m 3 s (483 s) Ratio: 2.2%
Screen dark (): 5 m 51 s (351 s) Ratio: 1.6%
Screen dimmed (): 1 m 45 s (105 s) Ratio: 0.5%
Screen medium (): 19 m 23 s (1163 s) Ratio: 5.2%
Screen light (): 40 s (40 s) Ratio: 0.2%
Screen bright (): (0 s) Ratio: 0.0%
=========
Wakelocks
=========
NlpCollectorWakeLock (Google Services): 21 m 27 s (1287 s) Count:1600 5.8%
BrowserVsync_20 (com.android.browser.Internet): 1 m 53 s (113 s) Count:139 0.5%
BatteryServiceUpdateStats (Android System): 1 m 3 s (63 s) Count:449 0.3%
RILJ (Dialer): 47 s (47 s) Count:1716 0.2%
NlpWakeLock (Google Services): 44 s (44 s) Count:898 0.2%
ActivityManager-Launch (Android System): 37 s (37 s) Count:158 0.2%
AbsListViewScroll_5.0 (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 36 s (36 s) Count:56 0.2%
AlarmManager (Android System): 33 s (33 s) Count:1248 0.1%
BrowserPerf_8 (com.android.browser.Internet): 31 s (31 s) Count:169 0.1%
LocationReceiverService (Google Services): 23 s (23 s) Count:1984 0.1%
AbsListViewScroll_5.0 (com.quoord.tapatalkxda.activity.XDA): 21 s (21 s) Count:42 0.1%
AudioOut_4 (1013): 19 s (19 s) Count:6 0.1%
SMSDispatcher (Dialer): 19 s (19 s) Count:6 0.1%
PrismScroll_2 (com.htc.launcher.HTC Sense): 13 s (13 s) Count:47 0.1%
prepareNotification_5 (com.android.mms.Messages): 12 s (12 s) Count:56 0.1%
*backup* (Android System): 10 s (10 s) Count:757 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 10 s (10 s) Count:13 0.0%
AlarmManager (Google Services): 10 s (10 s) Count:2812 0.0%
MediaScannerService (Media): 10 s (10 s) Count:0 0.0%
HtcListViewScroll_5.527 (com.m0narx.fileexplorer.File Explorer): 8 s (8 s) Count:11 0.0%
PrismLaunchActivity_4 (com.htc.launcher.HTC Sense): 7 s (7 s) Count:20 0.0%
LocationReportingService (Google Services): 7 s (7 s) Count:2817 0.0%
*vibrator* (Android System): 7 s (7 s) Count:691 0.0%
BrowserMaxPerf_1 (com.android.browser.Internet): 7 s (7 s) Count:149 0.0%
StartingAlertService_0 (com.android.mms.Messages): 6 s (6 s) Count:23 0.0%
*sync*_com.htc.sync.provider.weather_Account {name=3ee2849f6ac635949a0d833a9e9b8043, type=com.htc.sync.provider.weather} (HTC Services): 5 s (5 s) Count:24 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 5 s (5 s) Count:6 0.0%
ActivityManager-MultiCore-Num (Android System): 5 s (5 s) Count:1362 0.0%
ActivityManager-MultiCore-Freq (Android System): 5 s (5 s) Count:289 0.0%
HomeKeyHandlerFreq (Android System): 5 s (5 s) Count:209 0.0%
*sync*_com.soundcloud.android.provider.ScContentProvider_Account {name=fc5ef5060a405524f9ba22a8e2aaf1ad, type=com.soundcloud.android.account} (com.soundcloud.android.SoundCloud): 4 s (4 s) Count:4 0.0%
*sync*_gmail-ls_Account {name=eff16ca33766080e3e9c8404163782c4, type=com.google} (com.google.android.gm.Gmail): 4 s (4 s) Count:9 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 3 s (3 s) Count:924 0.0%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 3 s (3 s) Count:93 0.0%
IdleScreen:command_15 (com.htc.idlescreen.shortcut.Wallpaper Lock screen): 3 s (3 s) Count:156 0.0%
EmailServiceControllerPowerLockRefreshCommand_0 (com.htc.android.mail.Mail): 3 s (3 s) Count:10 0.0%
NetworkLocationLocator (Google Services): 3 s (3 s) Count:942 0.0%
AlarmManager (com.s0up.goomanager.GooManager): 3 s (3 s) Count:1 0.0%
IdleScreen:event_15 (com.htc.idlescreen.shortcut.Wallpaper Lock screen): 2 s (2 s) Count:196 0.0%
*sync*_com.google.android.location.reporting_Account {name=eff16ca33766080e3e9c8404163782c4, type=com.google} (Google Services): 2 s (2 s) Count:1610 0.0%
SimIoUtil_0 (com.android.mms.Messages): 2 s (2 s) Count:63 0.0%
show keyguard (Android System): 2 s (2 s) Count:19 0.0%
HtcDeviceInfoWakeLock_5 (Android System): 2 s (2 s) Count:704 0.0%
Icing (Google Services): 1 s (1 s) Count:966 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1330 0.0%
WifiStateMachine (Android System): 1 s (1 s) Count:759 0.0%
GOOGLE_C2DM (Google Services): 1 s (1 s) Count:1606 0.0%
HtcListViewScroll_5.527 (com.android.mms.Messages): 1 s (1 s) Count:29 0.0%
din (Google Services): 1 s (1 s) Count:1171 0.0%
GTALK_CONN (Google Services): 1 s (1 s) Count:2058 0.0%
Cleaner (com.oasisfeng.greenify.Greenify): 1 s (1 s) Count:1 0.0%
GpsLocationProvider (Android System): 1 s (1 s) Count:233 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1349 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 23 m 24 s (1404 s) Cntc/wc/ec)1461/0/0 6.3%
"msm_hsic_host" (): 14 m 38 s (878 s) Cntc/wc/ec)856/62/0 4.0%
"alarm_rtc" (): 3 m 18 s (198 s) Cntc/wc/ec)836/754/16 0.9%
"pmic_led" (): 45 s (45 s) Cntc/wc/ec)44/0/44 0.2%
"pn544" (): 35 s (35 s) Cntc/wc/ec)41/0/41 0.2%
"alarm" (): 28 s (28 s) Cntc/wc/ec)1301/0/0 0.1%
"radio-interface" (): 15 s (15 s) Cntc/wc/ec)134/0/0 0.1%
"wlan_ctrl_wake" (): 11 s (11 s) Cntc/wc/ec)29/0/29 0.1%
"PowerManagerService.Broadcasts" (): 5 s (5 s) Cntc/wc/ec)70/0/0 0.0%
"pm8xxx_adc_wakelock" (): 3 s (3 s) Cntc/wc/ec)3376/0/0 0.0%
"proximity" (): 2 s (2 s) Cntc/wc/ec)6/0/6 0.0%
"gpio_input" (): 1 s (1 s) Cntc/wc/ec)144/25/0 0.0%
"wlan_wake" (): 1 s (1 s) Cntc/wc/ec)719/3/0 0.0%
"htc_battery_8960" (): 1 s (1 s) Cntc/wc/ec)121/0/0 0.0%
"gpio_input_pwr_clear" (): 1 s (1 s) Cntc/wc/ec)70/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)32034/0/0 0.0%
"efsks" (): (0 s) Cntc/wc/ec)4/0/0 0.0%
"deleted_wake_locks" (): (0 s) Cntc/wc/ec)2/0/0 0.0%
"qcril" (): (0 s) Cntc/wc/ec)1832/0/0 0.0%
"qmuxd_port_wl_9" (): (0 s) Cntc/wc/ec)3509/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)120/0/0 0.0%
"port_list" (): (0 s) Cntc/wc/ec)10068/0/0 0.0%
=========
Processes
=========
com.android.browser (com.android.browser.Internet): Uid: 10032 Sys: 1 s (1 s) Us: 12 s (12 s) Starts: 4
*wakelock* (Google Services): Uid: 10042 Sys: 7 s (7 s) Us: 4 s (4 s) Starts: 0
surfaceflinger (Android System): Uid: 1000 Sys: 7 s (7 s) Us: 4 s (4 s) Starts: 0
com.google.process.location (Google Services): Uid: 10042 Sys: 1 s (1 s) Us: 8 s (8 s) Starts: 1
kworker/0:3 (0): Uid: 0 Sys: 9 s (9 s) Us: (0 s) Starts: 0
com.quoord.tapatalkxda.activity (com.quoord.tapatalkxda.activity.XDA): Uid: 10022 Sys: (0 s) Us: 5 s (5 s) Starts: 2
com.htc.idlescreen.shortcut (com.htc.idlescreen.shortcut.Wallpaper Lock screen): Uid: 10216 Sys: (0 s) Us: 4 s (4 s) Starts: 1
kworker/0:2 (0): Uid: 0 Sys: 5 s (5 s) Us: (0 s) Starts: 0
com.htc.android.htcime (com.htc.android.htcime.HTC Sense Input): Uid: 10069 Sys: (0 s) Us: 4 s (4 s) Starts: 1
com.htc.launcher (com.htc.launcher.HTC Sense): Uid: 10179 Sys: (0 s) Us: 4 s (4 s) Starts: 1
com.android.systemui (Android System): Uid: 1000 Sys: (0 s) Us: 3 s (3 s) Starts: 1
com.asksven.betterbatterystats_xdaedition (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): Uid: 10102 Sys: (0 s) Us: 3 s (3 s) Starts: 5
kworker/0:0 (0): Uid: 0 Sys: 3 s (3 s) Us: (0 s) Starts: 0
kworker/0:1 (0): Uid: 0 Sys: 3 s (3 s) Us: (0 s) Starts: 0
com.android.mms (com.android.mms.Messages): Uid: 10162 Sys: (0 s) Us: 1 s (1 s) Starts: 5
com.gsamlabs.bbm (com.gsamlabs.bbm.GSam Battery Monitor): Uid: 10046 Sys: (0 s) Us: 1 s (1 s) Starts: 5
irq/322-synapti (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
ksoftirqd/0 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.android.phone (Dialer): Uid: 1001 Sys: (0 s) Us: 1 s (1 s) Starts: 1
mmcqd/0 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
*wakelock* (Dialer): Uid: 1001 Sys: (0 s) Us: (0 s) Starts: 0
rcuc/0 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
*wakelock* (Media): Uid: 10048 Sys: (0 s) Us: (0 s) Starts: 0
======================
Alarms (requires root)
======================
Boot event was not registered yet, it will at next reboot (): Wakeups: 0
======================
Network (requires root)
======================
-1 () (Boot event was not registered yet, it will at next reboot): 1.0 Bytes 100.0%
==========
CPU States
==========
162 MHz (): 40 m 21 s 10.9%
216 MHz (): 42 s 0.2%
270 MHz (): 34 s 0.2%
324 MHz (): 42 s 0.2%
378 MHz (): 31 s 0.1%
384 MHz (): 2 s 0.0%
486 MHz (): 44 s 0.2%
594 MHz (): 35 s 0.2%
702 MHz (): 48 s 0.2%
810 MHz (): 28 s 0.1%
918 MHz (): 23 s 0.1%
1.03 GHz (): 1 m 24 s 0.4%
1.13 GHz (): 34 s 0.2%
1.24 GHz (): 26 s 0.1%
1.35 GHz (): 6 m 13 s 1.7%
1.46 GHz (): 8 s 0.0%
1.57 GHz (): 7 s 0.0%
1.67 GHz (): 5 s 0.0%
1.73 GHz (): 14 m 36 s 4.0%
Deep Sleep (): 4 h 59 m 31 s 81.0%
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
com.m0narx.xloud (com.m0narx.xloud.AudioEffectService)
Active since: 32 s
Last activity: 32 s
Crash count:0
com.google.process.location (com.google.android.location.internal.GoogleLocationManagerService)
Active since: 33 s
Last activity: 41 m 6 s
Crash count:0
com.google.process.gapps (com.google.android.gms.gcm.GcmService)
Active since: 33 s
Last activity: 56 m 38 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pbap.BluetoothPbapService)
Active since: 21 s
Last activity: 21 s
Crash count:0
com.android.location.fused (com.android.location.fused.FusedLocationService)
Active since: 21 s
Last activity: 21 s
Crash count:0
com.android.phone (com.android.phone.NetworkQueryService)
Active since: 22 s
Last activity: 22 s
Crash count:0
com.bonfiremedia.dots (com.ansca.corona.CoronaService)
Active since: 36 s
Last activity: 1 h 1 m 1 s
Crash count:0
com.htc.android.htcime (com.htc.android.htcime.HTCIMEService)
Active since: 20 s
Last activity: 1 h 9 m 14 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkServiceProxy)
Active since: 34 s
Last activity: 10 m 23 s
Crash count:0
com.gsamlabs.bbm (com.gsamlabs.bbm.lib.NotifyingService)
Active since: 36 s
Last activity: 59 m 17 s
Crash count:0
com.google.process.location (com.google.android.location.NetworkLocationService)
Active since: 21 s
Last activity: 21 s
Crash count:0
system (com.htc.smartdim.sensor_eye)
Active since: 6 h 6 m 20 s
Last activity: 1 h 6 m 49 s
Crash count:0
com.google.android.talk (com.google.android.videochat.VideoChatService)
Active since: 34 s
Last activity: 34 s
Crash count:0
system (com.android.providers.htcCheckin.htcCheckinService)
Active since: 18 s
Last activity: 18 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 19 s
Last activity: 19 s
Crash count:0
com.htc.idlescreen.shortcut (com.htc.idlescreen.shortcut.ShortcutService)
Active since: 34 s
Last activity: 34 s
Crash count:0
com.whatsapp (com.whatsapp.messaging.MessageService)
Active since: 35 s
Last activity: 47 m 40 s
Crash count:0
com.google.process.location (com.google.android.location.internal.server.NetworkLocationService)
Active since: 21 s
Last activity: 22 s
Crash count:0
com.android.htcdialer (com.android.htcdialer.DialerService)
Active since: 21 s
Last activity: 37 s
Crash count:0
com.quoord.tapatalkxda.activity (com.quoord.tapatalkxda.alarm.NotificationAlarmService)
Active since: 6 h 6 m 52 s
Last activity: 1 h 7 m 21 s
Crash count:0
com.google.process.location (com.google.android.location.GeocodeService)
Active since: 21 s
Last activity: 21 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 31 s
Last activity: 39 s
Crash count:0
com.android.nfc:handover (com.android.nfc.handover.HandoverService)
Active since: 21 s
Last activity: 21 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 18 s
Last activity: 18 s
Crash count:0
com.google.process.location (com.google.android.location.internal.server.GoogleLocationService)
Active since: 26 s
Last activity: 1 h 3 m 36 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 20 s
Last activity: 20 s
Crash count:0
com.oasisfeng.greenify:service (com.oasisfeng.greenify.CleanerService)
Active since: 35 s
Last activity: 1 h 56 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 34 s
Last activity: 34 s
Crash count:0
com.android.phone (com.android.phone.BluetoothPhoneService)
Active since: 22 s
Last activity: 22 s
Crash count:0
==================
Reference overview
==================
ref_boot: Reference ref_boot created 38 s (Wl: 7 elements; KWl: 0elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 5 elements; CPU: 15 elements)
ref_current: Reference ref_current created 6 h 9 m 42 s (Wl: 54 elements; KWl: 22elements; NetS: 22 elements; Alrm: 15 elements; Proc: 23 elements; Oth: 12 elements; CPU: 20 elements)

milesjohnson said:
So these stats look pretty normal?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Nope. That nlp wakelock is a beeeetch. There is a better battery stats thread. Post a logcat or a screen shot there and ask, the devs will help you personally.
OR Google nlp collector wakelock, OR search for those keywords in the thread. You should come up with something. I think it has something to do with Google service framework/maps/playstore. The solution would be to clear dats of an app or 2 from Google, I'm not sure which one it is.
Off to bed!
Sent from my HTC One

[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

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

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.....)