Database Develop

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

New Moto X user - Battery problem

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

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

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

[Q] 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.....)