Related
I am seeing similar behavior on my Nexus 7 as I did on my other tablet: http://forum.xda-developers.com/showthread.php?t=2155609
Would it be fair to conclude that a recent Google component update (Maps? Gmail?) is causing this tablet to remain awake?
Maybe. Maybe not.
Could be one of your market apps too.
Seem like you need to discover what is holding the wake locks.
Here's a start (if you are rooted)
Code:
$ su
# strings /data/system/packages.xml | awk '/<package name=/{n=$2;}/WAKE_LOCK/{print n;}'
wouldn't it be a kick in the pants if you found out it was the battery monitoring apps
good luck
I have su, but no awk or strings. Where did you get those linux utilities? I've been wanting a full set of those.
I'll copy packages.xml to my Linux box and try it out.
Thanks.
Using the CT702 tablet -
How does this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
correlate with this (output from your script):
name="com.kiloo.subwaysurf"
name="com.snrblabs.grooveip"
name="com.amazon.venezia"
name="com.skype.raider"
name="com.keramidas.TitaniumBackup"
name="com.kiwi.shipwrecked"
name="com.dropbox.android"
name="com.estrongs.android.taskmanager"
name="com.google.android.apps. genie.geniewidget"
name="com.netflix.mediaclient"
name="com.google.android.gm"
name="com.estrongs.android.pop"
name="com.metago.astro"
name="jp.co.johospace.jorte"
name="com.lsdroid.cerberus"
name="com.google.android.apps.googlevoice"
name="com.android.phasebeam"
name="com.android.phasebeam"
name="com.android.phasebeam"
name="com.android.phasebeam"
name="com.android.phasebeam"
name="com.android.phasebeam"
name="com.android.phasebeam"
name="com.android.phasebeam"
my phone too used to stay awake when i wasnt using it the solution being get a task manager and killl all unused apps also gps when not in use
I guess my original point was that you'll find both system and market apps that hold wake locks. (BTW your web browser should be able to display that packages.xml file if you want to have a look in it)
Well, I don't know for sure, but that image you attached sure seems to implicate Maps.
The thing is - and it's one of the things that sort of sucks about android - is that it is difficult to filter broadcast receivers. So, apps can spring back to life even if you've manually killed them if a separate app generates a matching broadcast that the former has registered for.
Some market apps are greedy in this regard - they register for all sorts of broadcasts so an appearance is maintained that they open quickly - on the off chance that a user will be sharing data between the app currently in use and that (other market) app.
In prior versions of Android, lots of apps - both system and market apps - would register as broadcast receivers for certain events produced by the stock email app. If you browsed the inbox, no problem... but as soon as you open an individual email, a whole slew of apps would get launched in the background.
Anyway - and this is a hypothesis - even if Maps is preventing sleep by holding wake locks, it could be a different app that is causing it to spring to life - or even a rather obscure startup cycle that depends on both market apps and/or system apps before Maps finally gets restarted.
If you manually kill off Maps and then shut the screen off, and then come back some time later and find Maps running again, you should be able to observe the event that restarts Maps in the logcat output.
good luck
---------- Post added at 10:58 PM ---------- Previous post was at 10:45 PM ----------
Nate2 said:
I have su, but no awk or strings. Where did you get those linux utilities? I've been wanting a full set of those.
I'll copy packages.xml to my Linux box and try it out.
Thanks.
Click to expand...
Click to collapse
Whoop - sorry. I was using BTEP (Better Terminal Emulator Pro) which comes with it's own private busybox (not installed in /system)
You could also install a busybox flash, but I would recommend you use one that doesn't touch /system/bin or /system/xbin. (I think at least on of the market versions might refer to this as a "safe install") I'm not familiar with them, so I can't recommend a particular version.
Right you are, sir!
I stopped Maps at 19:36, and exactly 1 hour later at 20:36, it re-started itself:
02-23 19:36:57.740 1121 1133 I ActivityManager: Killing proc 5340:com.google.android.apps.maps/10070: kill background
...
02-23 20:36:22.210 1121 1152 I ActivityManager: Start proc com.google.android.apps.maps for service com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService: pid=6033 uid=10070 gids={3003, 1015}
I can't find what app (if any) might have caused that. pid=6033 looks all Maps-related, not 3rd party.
Not sure myself either.
That logcat message looks a little different than an intent sent from a different app.
I suppose you have some more digging to do.
Sorry I'm not more help - my N7 rarely leaves the house, so if it's not in use it is on the charger. The consequence of that is that I have no idea whether it fails to sleep or not; I certainly wouldn't know from looking at the battery charge state/history anyway.
Don't know how helpful this is, but if the N7 does go into deep sleep, you will see messages in the kernel log (dmesg or /proc/kmsg) about entering the LP0 state.
Tedious to correlate those messages with logcat though - I think those messages are reported in seconds since boot rather than GMT or local time ... and worse yet that timestamp seem to get screwed up by LP0 sleep. (LP0 is a very deep sleep - the SoC is very nearly off completely - even the memory controller is turned off)
good luck
have you tried using better battery stats from this thread? It's a great app, and is also available on the play store if you want to donate to the dev.
just let it run for a while and post screenshots of kernel wakelocks, partial wakelocks, and alarms
Trying the XDA version now...
I think I've identified the problem on the CT702 tablet now; the problem on the Nexus 7 is still under investigation (not the same problem).
CT702 is not always awake now:
Google Maps is still the problem:
Better Battery Stats identifies Maps components responsible?
I've turned off these options in Google Maps to enable the tablet to sleep better:
Hopefully, the above will help someone. My Nexus 7 is being kept awake by SystemUpdateService.
More to follow..
Nate2 said:
I think I've identified the problem on the CT702 tablet now; the problem on the Nexus 7 is still under investigation (not the same problem).
CT702 is not always awake now:
View attachment 1762570
Google Maps is still the problem:
View attachment 1762572
Better Battery Stats identifies Maps components responsible?
View attachment 1762575
I've turned off these options in Google Maps to enable the tablet to sleep better:
View attachment 1762577
Hopefully, the above will help someone. My Nexus 7 is being kept awake by SystemUpdateService.
More to follow..
Click to expand...
Click to collapse
2 minutes of wakelocks over 23 hours isn't much. are there kernel wakelocks? the alarms don't seem to be too much either..
CT702:
===================
General Information
===================
BetterBatteryStats version: 1.12.0.0RC11
Creation Date: 2013-02-25 08:11:40
Statistic Type: Boot to Current
Since 10 h 51 m 13 s
VERSION.RELEASE: 4.0.3
BRAND: Android
DEVICE: m805_892x
MANUFACTURER: YG
MODEL: A777
OS.VERSION: 3.0.8-tcc
BOOTLOADER: unknown
HARDWARE: m805_892x
FINGERPRINT: unknown
ID: A777
TAGS: test-keys
USER: root
PRODUCT: full_m805_892x_evm
RADIO:
Rooted: true
============
Battery Info
============
Level lost [%]: 21 Bat.: 21% (98% to 77%) [1.9%/h]
Voltage lost [mV]: 56 (3889-3833) [5.2%/h]
===========
Other Usage
===========
Deep Sleep (): 10 h 36 m 10 s (38170 s) Ratio: 97.6%
Awake (): 15 m 2 s (902 s) Ratio: 2.3%
Screen On (): 11 m 46 s (706 s) Ratio: 1.8%
Wifi On (): 11 m 45 s (705 s) Ratio: 1.8%
Wifi Running (): 11 m 43 s (703 s) Ratio: 1.8%
No Data Connection (): 10 h 51 m 13 s (39073 s) Ratio: 100.0%
No or Unknown Signal (): 10 h 51 m 13 s (39073 s) Ratio: 100.0%
Screen dark (): 11 m 46 s (706 s) Ratio: 1.8%
=========
Wakelocks
=========
CerberusService (com.lsdroid.cerberus.Cerberus): 1 m 3 s (63 s) Count:1 0.2%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 24 s (24 s) Count:44 0.1%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 23 s (23 s) Count:110 0.1%
AlarmManager (Android System): 22 s (22 s) Count:184 0.1%
ActivityManager-Launch (Android System): 21 s (21 s) Count:62 0.1%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 13 s (13 s) Count:10 0.0%
MediaScannerService (Media): 11 s (11 s) Count:2 0.0%
AudioOut_1 (1013): 10 s (10 s) Count:2 0.0%
Event Log Service (Google Services): 6 s (6 s) Count:45 0.0%
maintain LCD off state during 5 second (Android System): 6 s (6 s) Count:63 0.0%
[email protected]/android_talk123456789cb0 (Google Services): 4 s (4 s) Count:3 0.0%
*sync*_com.android.calendar_Account {[email protected], type=com.google} (com.google.android.calendar.Calendar): 3 s (3 s) Count:4 0.0%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 2 s (2 s) Count:2 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 2 s (2 s) Count:2 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 s (2 s) Count:6 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 1 s (1 s) Count:30 0.0%
WifiStateMachine (Android System): 1 s (1 s) Count:94 0.0%
Checkin Service (Google Services): 1 s (1 s) Count:20 0.0%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 1 s (1 s) Count:96 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:76 0.0%
sleep_broadcast (Android System): 1 s (1 s) Count:74 0.0%
*backup* (Android System): 1 s (1 s) Count:97 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 1 m 22 s (82 s) Cntc/wc/ec)152/0/0 0.2%
"alarm_rtc" (): 38 s (38 s) Cntc/wc/ec)73/73/0 0.1%
"alarm" (): 14 s (14 s) Cntc/wc/ec)102/1/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)335/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)1297/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)75/0/1 0.0%
======================
Alarms (requires root)
======================
Boot event was not registered yet, it will at next reboot (): Wakeups: 0
======================
Network (requires root)
======================
==========
CPU States
==========
==================
Reference overview
==================
Custom: null
Since charged: null
Since screen off: null
Since unplugged: null
Since boot: Reference ref_boot created 1 m 49 s (Wl: 9 elements; KWl: 0elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 7 elements; CPU: 0 elements)
Nate2 said:
CT702:
============
Battery Info
============
Level lost [%]: 21 Bat.: 21% ([size=+1]98%[/size] to 77%) [1.9%/h]
Voltage lost [mV]: 56 ([size=+1]3889[/size]-3833) [[size=+1]5.2%/h[/size]]
===========
Other Usage
===========
Deep Sleep (): 10 h 36 m 10 s (38170 s) Ratio: [size=+1]97.6%[/size]
Awake (): 15 m 2 s (902 s) Ratio: 2.3%
Screen On (): 11 m 46 s (706 s) Ratio: 1.8%
Wifi On (): 11 m 45 s (705 s) Ratio: 1.8%
Click to expand...
Click to collapse
I conclude your OS is fine and your battery is bad in the CT702. Perhaps the full cell voltage decreases with age, but what I notice in the above is that it is saying your 98% capacity was only at 3889 mV.
Granted, its not a N7, but I would expect devices using the same battery chemistry to exhibit the same charge voltage range. (Maybe there is more about Li-Ion/Polymer batteries that I need to learn about, too).
The battery in my unit - admittedly only about 8 weeks old - swings between about 3660-4170mv.
That is only a swing of 500 mV for a full discharge cycle - but you are showing less than half of that at a "full charge." I suppose that the full-scale (charged) voltage of the battery pack might decline as it ages, but that seems pretty extreme. Moreover, if you believe the voltage decline statistic, I conclude that whatever made this report thinks that your 100% voltage swing is only 97 mV
( 21% @ 1.9%/hr => 11.1 hrs; 5.2%/hr @ 11.1 hrs => 57%; 56 mV/0.57 = 97 mV)
Those Maps wakelocks are indeed leading the pack - but only in the 2% or so percent of the time that the device is not sleeping. Also - note that 1.9%/hour statistic - when the device is only on about 1.9% of the hour: if it is correct, it would imply that the tablet would fully discharge itself in a single hour if it was on continuously. That certainly can't be the way the tablet is designed to work.
BTW, what app produced this output?
Nate2 said:
Google Maps is still the problem:
View attachment 1762572
Better Battery Stats identifies Maps components responsible?
View attachment 1762575
Click to expand...
Click to collapse
I think that "App Sucker" image is reporting data faithfully, but it's choice of statistic is leading to an unwarranted conclusion - given that the total time wakelocks were held seems to only be two minutes or so out of many hours. That seems to make the assumption that a huge chunk of the battery is used only when wakelocks are held - or that the amount of time the device these locks were held is irrelevant. (Or, to put it another way, would you care if Maps used 73% of the change if the total change was only 5% in 1000 hours?)
BTW, I thought I would tell you about a quick experiment I did the other day. It might help you in your investigation.
I set my tablet aside for about 150 minutes - off the charger, screen off. (This was roughly 10:35am - 1:05pm).
Then I woke it up and captured the kernel log (/proc/kmsg or "dmesg" output) and a logcat. I did this by hand (command line/terminal emulator), so I probably got that done within 2 or 3 minutes.
In the (Stock 4.2.2) kernel log, I see repetitive occurences of entry into LP0 mode: (background on Tegra SoC LPn modes)
Code:
<6>[141548.480341] Entering suspend state LP0
<6>[1415[b][color=red]48.482[/color][/b]222] Tegra: switched to LP cluster
<4>[141548.482430] partition 3d0 is left on before suspend
<4>[141548.482430] partition vde is left on before suspend
<4>[141548.482430] partition heg is left on before suspend
<4>[141548.482430] partition 3d1 is left on before suspend
<6>[1415[b][color=red]48.485[/color][/b]647] Tegra: switched to G cluster
<6>[141548.485791] Exited suspend state LP0
<6>[141548.485921] legacy wake status=0x0
<6>[141548.486145] tegra3 wake status=0x1
<6>[141548.486271] Resume caused by WAKE32, bcmsdh_sdmmc
<6>[1415[b][color=red]48.486[/color][/b]525] Suspended for [b][color=red]597.100 seconds[/color][/b]
<6>[141548.486956] wakeup wake lock: alarm
<6>[141548.492834] PM: early resume of devices complete after 5.636 msecs
Note that the timestamps in this kernel log can not be relied upon - apparently precisely because of the LP0 sleep. I surmise that the kernels' tick counter used for /proc/kmsg logging is suspended and therefore does not accumulate time in a wall-clock fashion; otherwise how could the device sleep for 597 seconds in only 4 milli-seconds?
Having captured the output of "dmesg" into a file "dmesg.txt" (and likewise the logcat into "logcat.txt"), I did a little hand-filtering of the output:
Code:
$ grep 'Tegra: switched to LP' dmesg.txt | wc -l
18
$ grep 'Suspended for' dmesg.txt |wc -l
19
$ grep 'Suspended for' dmesg.txt
<6>[141544.528940] Suspended for 5.813 seconds
<6>[141548.486525] Suspended for 597.100 seconds
<6>[141549.833844] Suspended for 5.610 seconds
<6>[141553.751664] Suspended for 114.785 seconds
<6>[141555.169992] Suspended for 366.895 seconds
<6>[141557.767079] Suspended for 111.202 seconds
<6>[141559.114371] Suspended for 3.868 seconds
<6>[141563.302312] Suspended for 344.820 seconds
<6>[141564.583528] Suspended for 62.516 seconds
<6>[141566.061274] Suspended for 188.582 seconds
<6>[141567.531674] Suspended for 7.695 seconds
<6>[141570.882663] Suspended for 595.651 seconds
<6>[141572.230025] Suspended for 8.666 seconds
<6>[141576.067748] Suspended for 87.744 seconds
<6>[141577.452742] Suspended for 368.048 seconds
<6>[141578.833047] Suspended for 139.359 seconds
<6>[141580.230604] Suspended for 9.878 seconds
<6>[141585.018340] Suspended for 373.786 seconds
<6>[141586.363370] Suspended for 12.157 seconds
$ grep 'Suspended for' dmesg.txt | awk 'BEGIN{s=0;}{s+=0.0+$4;}END{print NR,s;}'
19 3404.18
Now, 3404 seconds is only 3404/(150*60) = 38% of the time of my test... but I just checked and noticed that my kernel log file is exactly 128kB in length - so the kernel log buffer must have rolled over completely during that time, so I really only captured some fraction of the total time of sleep with that log. (The kernel log buffer fills too fast to record that much elapsed time).
But anyway - notice that many of the sleep intervals are several minutes long - once for nearly ten minutes straight!
In comparison, the logcat did capture the entire sleep interval (it had several *days* worth of info in it).
Code:
[l3452:] 02-24 10:35:07.692 481 563 I PowerManagerService: Going to sleep by user request...
[l3453:] 02-24 10:35:08.112 125 169 D SurfaceFlinger: Screen released, type=0 flinger=0x40d12318
...
[l3711:]02-24 13:05:46.952 481 496 I PowerManagerService: Waking up from sleep...
[l3712:] 02-24 13:05:47.222 481 600 D PowerManagerService-JNI: Excessive delay in au\
tosuspend_disable() while turning screen on: 269ms
Or in other words, the logcat capture only had 260 (3712-3452) entries in it for 150 minutes of that elapsed time - less than two entries per minute on average. And there were some notably large gaps. Below are a few excerpts from the logcat which are pairs of immediately adjacent entries in the logcat:
Code:
...
02-24 10:[color=green][b]35[/b][/color]:33.951 585 585 I wpa_supplicant: wlan0: WPA: Group rekeying completed with 00:18:39:cd:99:cb [GTK=CCMP]
02-24 10:[color=red][b]36[/b][/color]:53.731 6683 6683 I RlzPingService: Setting next ping for 1362335813737
...
02-24 10:[color=green][b]37[/b][/color]:00.868 6845 6845 W InvService: Dropping C2DM message for unknown or unstarted client: chromesync#1337300716
02-24 10:[color=red][b]38[/b][/color]:46.241 481 576 D ConnectivityService: Captive portal check NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "notmySSID", roaming: false, failover: false, isAvailable: true
...
02-24 10:[color=green][b]38[/b][/color]:47.261 481 576 D ConnectivityService: NetTransition Wakelock for WifiStateMachine released by timeout
02-24 10:[color=red][b]46[/b][/color]:59.856 913 4117 W Smack/Packet: notify conn break (IOEx), close connection
...
02-24 10:[color=green][b]50[/b][/color]:33.849 585 585 I wpa_supplicant: wlan0: WPA: Group rekeying com\
pleted with 00:18:39:cd:99:cb [GTK=CCMP]
02-24 10:[color=red][b]56[/b][/color]:42.611 913 2062 I EventLogService: Aggregate from 1361730402536 \
(log), 1361730402536 (data)
...
02-24 11:[color=green][b]07[/b][/color]:19.411 481 576 D ConnectivityService: handleInetConditionHoldEnd: net=1, condition=100, published condition=0
02-24 11:[color=red][b]17[/b][/color]:15.824 913 7118 W Smack/Packet: notify conn break (IOEx), close connection
...
Well - anyway : you get the idea - large gaps in time where literally *nothing* is happening. I think you should see the same sort of behavior if your tab is actually sleeping correctly.
bftb0 said:
BTW, what app produced this output?
Click to expand...
Click to collapse
Better Battery Stats - http://forum.xda-developers.com/showthread.php?t=1179809
The "App Sucker" screenshot is from GSAM Battery Monitor - http://play.google.com/store/apps/details?id=com.gsamlabs.bbm
Nexus 7:
===================
General Information
===================
BetterBatteryStats version: 1.12.0.0RC11
Creation Date: 2013-02-25 08:17:25
Statistic Type: Boot to Current
Since 10 h 55 m 33 s
VERSION.RELEASE: 4.1.2
BRAND: google
DEVICE: grouper
MANUFACTURER: asus
MODEL: Nexus 7
OS.VERSION: 3.1.10-g009b6d1
BOOTLOADER: 3.41
HARDWARE: grouper
FINGERPRINT: google/nakasi/grouper:4.1.2/JZO54K/485486:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: android-build
PRODUCT: nakasi
RADIO:
Rooted: true
============
Battery Info
============
Level lost [%]: 1 Bat.: 1% (100% to 99%) [0.1%/h]
Voltage lost [mV]: 0 (4-4) [0.0%/h]
===========
Other Usage
===========
Awake (): 10 h 55 m 33 s (39333 s) Ratio: 100.0%
Screen On (): 12 m 59 s (779 s) Ratio: 2.0%
Wifi On (): 10 h 55 m 33 s (39333 s) Ratio: 100.0%
Wifi Running (): 40 m 18 s (2418 s) Ratio: 6.1%
No Data Connection (): 10 h 55 m 33 s (39333 s) Ratio: 100.0%
No or Unknown Signal (): 10 h 55 m 33 s (39333 s) Ratio: 100.0%
Screen dark (): 12 m 59 s (779 s) Ratio: 2.0%
=========
Wakelocks
=========
SystemUpdateService (Google Services): 10 h 51 m 43 s (39103 s) Count:1 99.4%
AlarmManager (Android System): 45 s (45 s) Count:856 0.1%
[email protected]/android_talk123456789522 (Google Services): 39 s (39 s) Count:5 0.1%
MediaScannerService (Media): 39 s (39 s) Count:2 0.1%
com.zomut.watchdog.MonitorService (com.zomut.watchdog.Watchdog): 38 s (38 s) Count:1308 0.1%
ConnectivityService (Android System): 29 s (29 s) Count:857 0.1%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 17 s (17 s) Count:49 0.0%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 16 s (16 s) Count:127 0.0%
AlarmManager (com.zomut.watchdog.Watchdog): 9 s (9 s) Count:654 0.0%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 8 s (8 s) Count:51 0.0%
ActivityManager-Launch (Android System): 2 s (2 s) Count:58 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 2 s (2 s) Count:5 0.0%
GOOGLE_C2DM (Google Services): 2 s (2 s) Count:26 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 1 s (1 s) Count:34 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 1 s (1 s) Count:2 0.0%
AlarmManager (jp.co.johospace.jorte.Jorte): 1 s (1 s) Count:4 0.0%
NetworkLocationLocator (Google Services): 1 s (1 s) Count:26 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:51 0.0%
WifiStateMachine (Android System): 1 s (1 s) Count:101 0.0%
AudioOut_2 (1013): 1 s (1 s) Count:1 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 10 h 42 m 34 s (38554 s) Cntc/wc/ec)2/0/0 97.9%
"alarm" (): 48 s (48 s) Cntc/wc/ec)1502/0/0 0.1%
"GPS" (): 19 s (19 s) Cntc/wc/ec)2/0/0 0.0%
"power-supply" (): 18 s (18 s) Cntc/wc/ec)656/0/0 0.0%
"wlan_ctrl_wake" (): 16 s (16 s) Cntc/wc/ec)17/0/17 0.0%
"wlan_wake" (): 6 s (6 s) Cntc/wc/ec)3243/0/0 0.0%
"wlan_rx_wake" (): 3 s (3 s) Cntc/wc/ec)57/0/56 0.0%
"KeyEvents" (): 1 s (1 s) Cntc/wc/ec)1571/0/0 0.0%
"event1-351" (system, com.google.android.gm): (0 s) Cntc/wc/ec)2/0/0 0.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
==========
51 MHz (): 9 h 32 m 23 s 87.2%
102 MHz (): 9 m 59 s 1.5%
204 MHz (): 7 m 43 s 1.2%
340 MHz (): 56 m 3 s 8.6%
475 MHz (): 4 m 22 s 0.7%
640 MHz (): 2 m 35 s 0.4%
760 MHz (): 6 s 0.0%
860 MHz (): 8 s 0.0%
1 GHz (): 13 s 0.0%
1.1 GHz (): 0.0%
1.2 GHz (): 1 m 41 s 0.3%
1.3 GHz (): 15 s 0.0%
==================
Reference overview
==================
Custom: null
Since charged: null
Since screen off: null
Since unplugged: null
Since boot: Reference ref_boot created 49 s (Wl: 5 elements; KWl: 0elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 7 elements; CPU: 11 elements)
Looks like maps is the main culprit for my N7 as well I let it run over night while I was sleeping.
Sent from my Nexus 7
@Nate2
I'm not sure I would be too worried about 0.1%/hr, even if the tablet never sleeps! That said, those services (Updater and PowerManager) seem more likely to be the trouble than Maps.
@Triscuit
The second image indicates Maps only held wake locks for a few minutes. Seems highly doubtful that you lost 8% of your battery charge in 5 minutes.
bftb0 said:
I conclude your OS is fine and your battery is bad in the CT702. Perhaps the full cell voltage decreases with age, but what I notice in the above is that it is saying your 98% capacity was only at 3889 mV.
Click to expand...
Click to collapse
Yes, in about 15 minutes off the charger, this CT702 loses 5% battery:
Level lost [%]: 5 Bat.: 5% (100% to 95%) [20.0%/h]
Voltage lost [mV]: 368 (4145-3777) [1472.0%/h]
Hello All
Could somebody with normal - good battery time install betterbatterystats (free download here: http://forum.xda-developers.com/showthread.php?t=1179809&highlight=better+battery+stats) and leave it running for an hour or so. Afterwards send the text dumpfile somewhere and open it.
Could you paste me please your entries under Kernel Wakelocks and CPU States?
Mine (after running it for around 8 minutes look like this):
Code:
================
Kernel Wakelocks
================
"msicbattery_wakelock" (): 1 m 51 s (111 s) Cnt:(c/wc/ec)0/0/0 22,2%
"rx_wake" (): 10 s (10 s) Cnt:(c/wc/ec)45/0/44 2,0%
"PowerManagerService" (): 8 s (8 s) Cnt:(c/wc/ec)81/0/0 1,8%
"hsi_wakelock" (): (0 s) Cnt:(c/wc/ec)152/0/0 0,0%
"wl1271_wake" (): (0 s) Cnt:(c/wc/ec)420/0/0 0,0%
"alarm" (): (0 s) Cnt:(c/wc/ec)40/0/0 0,0%
"intel_scu_ipc" (): (0 s) Cnt:(c/wc/ec)1340/0/0 0,0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)3079/0/0 0,0%
And I have fairly bad battery time at the moment.
And here what CPU looks like:
Code:
==========
CPU States
==========
2 GHz (): 1 m 12 s 14,5%
1,2 GHz (): 6 s 1,3%
900 MHz (): 8 s 1,6%
600 MHz (): 6 m 53 s 82,5%
This is stock JB.
Check another wakelock category other than only the kernel wakelocks. It is clear that the issue is not coming from the kernel with those stats that you posted but from userspace land if the CPU was at 2 GHz for that long :silly:...
It actually went away after rebooting. The thing is, there was no app using the CPU.
I think it has an issue with charging. After unplugging it from the charger, BBS still told me it's charging. Even after hours of the charger. It also used a lot of battery in that time (like 1 day of standby instead of my typical 2). Then I rebooted it and since it's fine again.
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
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.
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%