Related
I use nite slim ics 3.2 and have the same problem with older versions of slim ics and dark knight 4 and all the other ics roms that i tested
All the time i full wipe my device and the first time i have no Android os battery drain. On the second day of use the bug comes out.
wifi and data connection off and the phone eats 5% per hour on standby. Android OS drains the battery with 70% and i think this is to much. maybe the phone don't come in idle mode? Battery stats say the phone is 100% awake time
Yesterday i used the phone 5 hours extremely before the battery was empty and i had 30% drain from display with 5 hours screen on and 30% from Android os. Normally i had Max 5% Android os drain.
What's wrong? What i can do?
And excuse me for my English, best regards from Germany
btw. Have formatted cache, dalvik cache data and system and installed then the slim base and then the essentials.
send from SGS i9000 with Slim ICS 3.2
Please help me, I'm gonna get crazy . . .
battery stats dump file will follow
==================
General Information
===================
BetterBatteryStats version: 1.7.1.0
Creation Date: 2012-04-11 08:51:15
Statistic Type: (0) Since Charged
Since 2 h 19 m 15 s
VERSION.RELEASE: 4.0.4
BRAND: Android
DEVICE: GT-I9000
MANUFACTURER: samsung
MODEL: GT-I9000
RADIO: unknown
BOOTLOADER: unknown
FINGERPRINT: samsung/full_galaxysmtd/galaxysmtd:4.0.4/IMM76D/eng.ar.20120201.181605:user/release-keys
HARDWARE: aries
ID: IMM76D
Rooted: true
===========
Other Usage
===========
Awake (): 2 h 19 m 15 s (8355 s) Ratio: 100,0%
Screen On (): 13 m 10 s (790 s) Ratio: 9,5%
Wifi On (): 3 s (3 s) Ratio: 0,0%
Wifi Running (): 3 s (3 s) Ratio: 0,0%
=========
Wakelocks
=========
AudioOut_1 (1013): 3 m 8 s (188 s) Count:48 2,3%
AlarmManager (Android-System): 57 s (57 s) Count:357 0,7%
ActivityManager-Launch (Android-System): 15 s (15 s) Count:137 0,2%
RILJ (Telefon): 12 s (12 s) Count:106 0,1%
MediaScannerService (Medien): 7 s (7 s) Count:2 0,1%
sleep_broadcast (Android-System): 4 s (4 s) Count:42 0,1%
Checkin Service (Google-Dienste): 2 s (2 s) Count:36 0,0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google-Dienste): 2 s (2 s) Count:27 0,0%
SCREEN_FROZEN (Android-System): 1 s (1 s) Count:45 0,0%
NetworkStats (Android-System): 1 s (1 s) Count:67 0,0%
*vibrator* (Android-System): 1 s (1 s) Count:161 0,0%
GpsLocationProvider (Android-System): 1 s (1 s) Count:8 0,0%
SyncLoopWakeLock (Android-System): 1 s (1 s) Count:363 0,0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Kalenderspeicher): 1 s (1 s) Count:2 0,0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Google Mail): 1 s (1 s) Count:1 0,0%
================
Kernel Wakelocks
================
=========
Processes
=========
kworker/0:1 (0): Sys: 5 s (5 s) Us: (0 s) Starts: 0
kworker/u:1 (0): Sys: 4 s (4 s) Us: (0 s) Starts: 0
kworker/u:2 (0): Sys: 3 s (3 s) Us: (0 s) Starts: 0
kworker/u:0 (0): Sys: 3 s (3 s) Us: (0 s) Starts: 0
kworker/u:3 (0): Sys: 2 s (2 s) Us: (0 s) Starts: 0
kworker/0:0 (0): Sys: 2 s (2 s) Us: (0 s) Starts: 0
it.android.smartscreenoffpro (it.android.smartscreenoffpro.Smart Screen Off PRO): Sys: 1 s (1 s) Us: 1 s (1 s) Starts: 3
com.google.android.apps.maps (com.google.android.apps.maps.Maps): Sys: (0 s) Us: 2 s (2 s) Starts: 2
surfaceflinger (Android-System): Sys: 1 s (1 s) Us: (0 s) Starts: 0
kworker/0:2 (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.dataviz.docstogo (com.dataviz.docstogo.Documents To Go): Sys: (0 s) Us: 1 s (1 s) Starts: 3
kworker/0:3 (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
/init (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
system (Android-System): Sys: (0 s) Us: (0 s) Starts: 0
======================
Alarms (requires root)
======================
========
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 hxxp://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
android.process.media (com.android.providers.media.MediaScannerService)
Active since: 1 m 6 s
Last activity: 1 m 6 s
Crash count:0
com.google.process.gapps (com.google.android.location.internal.server.NetworkLocationService)
Active since: 41 s
Last activity: 42 s
Crash count:0
com.android.smspush (com.android.smspush.WapPushManager)
Active since: 33 s
Last activity: 33 s
Crash count:0
com.swype.android.inputmethod (com.swype.android.inputmethod.SwypeInputMethod)
Active since: 32 s
Last activity: 32 s
Crash count:0
com.android.vending (com.google.android.finsky.services.LicensingService)
Active since: 1 m 2 s
Last activity: 1 m 2 s
Crash count:0
com.shazam.android (com.shazam.advert.admarvel.AdMarvelCachedAdDownloaderService)
Active since: 1 m 2 s
Last activity: 1 m 2 s
Crash count:0
de.tsc.android.haushaltsbuch (de.tsc.android.base.haushaltsbuch.widget.FutureWidget$UpdateService)
Active since: 1 m 1 s
Last activity: 1 m 4 s
Crash count:0
it.android.smartscreenoffpro (it.android.smartscreenoffpro.Servizio)
Active since: 49 s
Last activity: 49 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 40 s
Last activity: 40 s
Crash count:0
com.google.android.talk (com.google.android.videochat.VideoChatService)
Active since: 44 s
Last activity: 44 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 34 s
Last activity: 34 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 32 s
Last activity: 32 s
Crash count:0
com.spotify.mobile.android.ui (com.spotify.mobile.android.service.LocalService)
Active since: 1 m 2 s
Last activity: 1 m 4 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 31 s
Last activity: 31 s
Crash count:0
de.tsc.android.haushaltsbuch (de.tsc.android.base.haushaltsbuch.widget.BudgetWidget$UpdateService)
Active since: 1 m 1 s
Last activity: 1 m 4 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 44 s
Last activity: 1 m 54 s
Crash count:0
com.swype.android.inputmethod:SwypeConnect (com.swype.android.connect.ConnectClient)
Active since: 35 s
Last activity: 35 s
Crash count:0
com.bel.android.dspmanager (com.bel.android.dspmanager.service.HeadsetService)
Active since: 42 s
Last activity: 42 s
Crash count:0
Blainstorm said:
btw. Have formatted cache, dalvik cache data and system and installed then the slim base and then the essentials.
Click to expand...
Click to collapse
When you say installed base and then essentials do you mean you restored apps use some sort of backup??
When you install the base only restore apps via the market. Do NOT restore any app data!
If you reflash roms and have done a proper wipe then and tried this multiple times with different roms and the same thing happens, it must be a certain app causing your phone to stay awake.
Another thing you can try is delete everything but your essentials on your internal and sd card. Maybe something on there has some settings that is causing problems (very unlikely but no harm in clearing up the sd card or trying it)
Good luck
Blainstorm said:
I use nite slim ics 3.2
Android OS drains the battery with 70%
Click to expand...
Click to collapse
I think that you will find that this is a known "bug" from google source if slim is using android 4.0.3
I suggest that you read the slim ics 3.2 thread or use the search function as you may find that it is a 'feature' of 4.0.3
I do not have my usual computer with me ATM but i have screen shots of the battery use showing this "bug" when i was using ICSSGS 4.2
Thank you a lot to answer for my thread.
With base and essential i mean the package from slim ics. You have to install first the base and then the essentials in cwm. The apps i installs from play store. I use the 4.04 ics base :-(
Sent from my GT-I9000 using Tapatalk 2
I don't know if this helps, but you said it may be something to do with phone not entering idle, well how about flashing semaphore 1.0.0 (the ics version of semaphore), and read the guide in the first post on deep idle, could perhaps help
Noob question
same thing happens to me and im on dark knight 4..... thanks in advance its my first custom so sorry for being a noob what should i do? thanks again
I'll testing devil kernel now.
I'm now find out why Android os where so high in battery drain. Get titanium backup and remove all apps (save them before) now reset battery stats in cwm and Android os where by 7% now. All not needed widgets are deleted and it's perfect now.
I thing it was the shazam widget or beautiful widgets. . .
Thanks a lot for your help. I hope my info will help someone
Sent from my GT-I9000 using Tapatalk 2
Drain is caused by a ROM you're using, not restored data etc.
I highly recommend latest CM9 nightly build, I've never seen huge battery life like this ROM.
You can also reduce your apps installed on phone - they are also killing battery by some background processes and similar stuff.
My phone on CM9 after 10-12h (full day) with Wi-Fi and HSDPA on usually has 50% after whole day. I never had similar score on any other ROM before (since Android 2.2).
PS. I've got only 40 apps installed (data from Play Store).
The slim ics ROM is great, i don't want change that. Now after killing the widgets my Android os drain is normally. And i have 35 apps installed.all that i want
Sent from my GT-I9000 using Tapatalk 2
For those on glitch make sure you download NSTools from play market and activate deep idle (I think under settings within the app)
For those on the devil kernel deep idle is possible, too. With ns tools. . . And i think in cwm, too.
Sent from my GT-I9000 using Tapatalk 2
I have the same problem
Hi Blainstorm,
I have the same problem. My phone, Android OS drain 70% battery use when it stand by.
I see you fixed it. But i have some question:
- You use Titanium Backup to backup and remove all app? or downloaded app?
- How did you reset battery stats in cmw? Can you guide me?
Thanks.
Talon26 said:
When you say installed base and then essentials do you mean you restored apps use some sort of backup??
When you install the base only restore apps via the market. Do NOT restore any app data!
If you reflash roms and have done a proper wipe then and tried this multiple times with different roms and the same thing happens, it must be a certain app causing your phone to stay awake.
Another thing you can try is delete everything but your essentials on your internal and sd card. Maybe something on there has some settings that is causing problems (very unlikely but no harm in clearing up the sd card or trying it)
Good luck
Click to expand...
Click to collapse
This solved my os bug
omkarsansare said:
This solved my os bug
Click to expand...
Click to collapse
I had reflash many rom, but no effect. Android OS is still drain many battery.
Should i format all internal & sd card, then reflash original rom?
Hello,
I have huge battery drain by android OS too, but I sort of fixed it.
I´m on CM9 ICS 4.0.3 and latest devil kernel 2_0.94
LiveOC-ed 10% and in total OC 1.32GHz, deep idle enabled, some voltages tweaks, smartassV2 governor (sheduler cfq) and this is how much juice I loose over night.
PS. I have also Airplane over night enabled in JuiceDefender.
{
"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"
}
In first picture:
Signal from mobile network -same as Wi-fi
Wi-Fi -8h15min
Awake -1h58min
Screen On -4min
Charging - /
So, my advice to you is install NSTools and Jucie Defeneder and tweak your settings and you´ll have no problems.
sokre988 said:
Hello,
I have huge battery drain by android OS too, but I sort of fixed it.
I´m on CM9 ICS 4.0.3 and latest devil kernel 2_0.94
LiveOC-ed 10% and in total OC 1.32GHz, deep idle enabled, some voltages tweaks, smartassV2 governor (sheduler cfq) and this is how much juice I loose over night.
PS. I have also Airplane over night enabled in JuiceDefender.
In first picture:
Signal from mobile network -same as Wi-fi
Wi-Fi -8h15min
Awake -1h58min
Screen On -4min
Charging - /
So, my advice to you is install NSTools and Jucie Defeneder and tweak your settings and you´ll have no problems.
Click to expand...
Click to collapse
I can't find deep idle enabled in NSTools or Jucie Defeneder.
Can you show me more detail?
i have changing many rom. Now i'm using stock rom 4.6 Gingebread, but it's still happening. Android OS drain battery so much.
"One Power Guard" can help you fix it. downloaded from http://forum.xda-developers.com/showthread.php?t=1889740
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.
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%
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.....)