Database Users

BetterBatteryStats Interpretation help.

Call all BetterBatteryStats pros. I'm trying to figure out what is causing these wakelocks on my phone. I'm running RedPill (CM7 with tweaks) on my Motorola Atrix.
I can't figure out what is giving me such large SyncManagerHandleSyncAlarm and AlarmManager wakelocks. I only have my Google Account syncing Contacts, Gmail, and Calendar with "Background data" and "Auto-sync" checked. I can't think of any other things that are causing this.
Also, I cannot figure out what AlarmManager and FDCompleteTime is and how I can stop that from wakelocking. Everything else seems pretty normal.
For my CM7 email app, I turned it from Push to Fetch every 30 minutes so that should help it from wakelocking.
Thanks for all the help!
Code:
===================
General Information
===================
BetterBatteryStats version: 1.1.1.0
Creation Date: 2011-12-06 15:10:49
Statistic Type: (3)
Since 7 h 2 m 7 s
VERSION.RELEASE: 2.3.7
BRAND: MOTO
DEVICE: olympus
MANUFACTURER: Motorola
MODEL: MB860
===========
Other Usage
===========
Wifi On (): 4 h 9 m 52 s (14992 s) Ratio: 59.2%
Awake (): 2 h 2 m 23 s (7343 s) Ratio: 29.0%
Screen On (): 1 h 26 m 56 s (5216 s) Ratio: 20.6%
=========
Wakelocks
=========
SyncManagerHandleSyncAlarm (Android System): 32 m 48 s (1968 s) Count:943 26.8%
MAIL_SERVICE (com.android.email.Email): 20 m 14 s (1214 s) Count:137 16.5%
FDCompleteTime (Dialer): 13 m 21 s (801 s) Count:293 10.9%
AlarmManager (Android System): 9 m 24 s (564 s) Count:2570 7.7%
*wifi* (Android System): 7 m 31 s (451 s) Count:1088 6.2%
Event Log Service (Google Services): 6 m 23 s (383 s) Count:216 5.2%
*network-location* (com.google.android.googlequicksearchbox.Google Search): 5 m 34 s (334 s) Count:40 4.6%
*sync* (com.google.android.gm.Gmail): 4 m 37 s (277 s) Count:65 3.8%
ActivityManager-Launch (Android System): 3 m 6 s (186 s) Count:669 2.5%
SmsBackup+ (com.zegoggles.smssync.SMS Backup+): 2 m 36 s (156 s) Count:6 2.1%
RILJ (Dialer): 2 m 16 s (136 s) Count:1191 1.9%
GTALK_ASYNC_CONN (Google Services): 2 m 10 s (130 s) Count:21 1.8%
android.media.MediaPlayer (com.android.music.Music): 1 m 32 s (92 s) Count:22 1.3%
*network-location* (Android System): 1 m 12 s (72 s) Count:709 1.0%
GTALK_CONN (Google Services): 54 s (54 s) Count:641 0.7%
BWL (com.levelup.beautifulwidgets.Beautiful Widgets): 54 s (54 s) Count:7 0.7%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 52 s (52 s) Count:110 0.7%
GpsLocationProvider (Android System): 49 s (49 s) Count:808 0.7%
FacebookService (com.facebook.katana.Facebook): 41 s (41 s) Count:12 0.6%
*vibrator* (Android System): 34 s (34 s) Count:1834 0.5%
show keyguard (Android System): 29 s (29 s) Count:35 0.4%
android.media.MediaPlayer (com.doubleTwist.androidPlayer.doubleTwist): 28 s (28 s) Count:10 0.4%
*network-location* (com.android.browser.Browser): 24 s (24 s) Count:29 0.3%
StartingAlertService (UID): 23 s (23 s) Count:50 0.3%
sleep_broadcast (Android System): 18 s (18 s) Count:1031 0.3%
*sync* (Google Services): 17 s (17 s) Count:146 0.2%
*network-location* (com.facebook.katana.Facebook): 14 s (14 s) Count:15 0.2%
*sync* (com.google.android.apps.docs.Docs): 11 s (11 s) Count:4 0.2%
Managewakelock: partial (UID): 10 s (10 s) Count:54 0.1%
DocsSyncAdapter (com.google.android.apps.docs.Docs): 9 s (9 s) Count:7 0.1%
*network-location* (Google Services): 9 s (9 s) Count:201 0.1%
Checkin Service (Google Services): 9 s (9 s) Count:712 0.1%
NetworkLocationCacheUpdater (com.google.android.apps.maps.Maps): 8 s (8 s) Count:13 0.1%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 7 s (7 s) Count:5 0.1%
SMSDispatcher (Dialer): 7 s (7 s) Count:297 0.1%
SCREEN_FROZEN (Android System): 7 s (7 s) Count:1107 0.1%
DownloadManager (Media): 6 s (6 s) Count:4 0.1%
*network-location* (com.levelup.beautifulwidgets.Beautiful Widgets): 5 s (5 s) Count:14 0.1%
Browser (com.android.browser.Browser): 4 s (4 s) Count:4 0.1%
MediaScannerService (Media): 4 s (4 s) Count:3 0.1%
GOOGLE_C2DM (Google Services): 3 s (3 s) Count:197 0.1%
M (net.dinglisch.android.taskerm.Tasker): 3 s (3 s) Count:241 0.0%
com.keramidas.TitaniumBackup.service.WorkerService (com.keramidas.TitaniumBackup.Titanium Backup): 3 s (3 s) Count:2 0.0%
*network-location* (com.handmark.tweetcaster.premium.TweetCaster Pro): 3 s (3 s) Count:4 0.0%
FDRILCommandTime (Dialer): 2 s (2 s) Count:142 0.0%
*vibrator* (UID): 2 s (2 s) Count:4 0.0%
StartingPopupUtilsService (UID): 2 s (2 s) Count:32 0.0%
DownloadManager (com.google.android.gm.Gmail): 1 s (1 s) Count:70 0.0%
*network-location-cell-update* (Google Services): 1 s (1 s) Count:139 0.0%
com.google.android.apps.googlevoice.PushNotificationRegistrationService (com.google.android.apps.googlevoice.Google Voice): 1 s (1 s) Count:1 0.0%
*wifi* (com.google.android.apps.maps.Maps): 1 s (1 s) Count:6 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 1 s (1 s) Count:5 0.0%
E (net.dinglisch.android.taskerm.Tasker): 1 s (1 s) Count:245 0.0%
=========
Processes
=========
suspend (0): Sys: 1 m 25 s (85 s) Us: (0 s) Starts: 0
com.quoord.tapatalksumsang.activity (com.quoord.tapatalksumsang.activity.Tapatalk): Sys: 6 s (6 s) Us: 24 s (24 s) Starts: 3
com.android.browser (com.android.browser.Browser): Sys: 4 s (4 s) Us: 21 s (21 s) Starts: 6
*wakelock* (Dialer): Sys: 14 s (14 s) Us: 4 s (4 s) Starts: 0
com.google.android.gm (com.google.android.gm.Gmail): Sys: 2 s (2 s) Us: 14 s (14 s) Starts: 8
android.process.acore (com.fede.launcher.LauncherPro): Sys: 1 s (1 s) Us: 9 s (9 s) Starts: 1
com.keramidas.TitaniumBackup (com.keramidas.TitaniumBackup.Titanium Backup): Sys: 1 s (1 s) Us: 7 s (7 s) Starts: 10
net.cdeguet.smartkeyboardpro (net.cdeguet.smartkeyboardpro.Smart Keyboard Pro): Sys: 1 s (1 s) Us: 6 s (6 s) Starts: 1
com.facebook.katana (com.facebook.katana.Facebook): Sys: 1 s (1 s) Us: 6 s (6 s) Starts: 2
com.asksven.betterbatterystats_xdaedition (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): Sys: 1 s (1 s) Us: 6 s (6 s) Starts: 3
netd (0): Sys: (0 s) Us: 5 s (5 s) Starts: 0
com.android.email (com.android.email.Email): Sys: (0 s) Us: 4 s (4 s) Starts: 2
com.android.settings (Android System): Sys: (0 s) Us: 4 s (4 s) Starts: 15
com.google.android.talk (com.google.android.talk.Talk): Sys: (0 s) Us: 3 s (3 s) Starts: 3
com.mint (com.mint.Mint.com): Sys: (0 s) Us: 3 s (3 s) Starts: 2
com.handcent.nextsms (UID): Sys: (0 s) Us: 3 s (3 s) Starts: 4
cpufreq-dvfsd (0): Sys: 3 s (3 s) Us: (0 s) Starts: 0
com.doubleTwist.androidPlayer (com.doubleTwist.androidPlayer.doubleTwist): Sys: (0 s) Us: 2 s (2 s) Starts: 6
nvrm_daemon (0): Sys: 1 s (1 s) Us: 1 s (1 s) Starts: 0
com.android.systemui (Android System): Sys: (0 s) Us: 2 s (2 s) Starts: 1
com.roflharrison.agenda.plus (com.roflharrison.agenda.plus.Android Agenda Widget Plus): Sys: (0 s) Us: 2 s (2 s) Starts: 11
cn.miren.browser (cn.miren.browser.Miren Browser): Sys: (0 s) Us: 1 s (1 s) Starts: 30
net.dinglisch.android.taskerm (net.dinglisch.android.taskerm.Tasker): Sys: (0 s) Us: 2 s (2 s) Starts: 1
com.android.mms (com.android.mms.Messaging): Sys: (0 s) Us: 2 s (2 s) Starts: 1
com.google.process.gapps (Google Services): Sys: (0 s) Us: 1 s (1 s) Starts: 1
com.android.vending (com.android.vending.Market): Sys: (0 s) Us: 2 s (2 s) Starts: 9
com.cyanogenmod.cmparts (Android System): Sys: (0 s) Us: 1 s (1 s) Starts: 5
org.gtmedia.seekdroid (org.gtmedia.seekdroid.SeekDroid): Sys: (0 s) Us: 1 s (1 s) Starts: 5
mediaserver (1013): Sys: (0 s) Us: 1 s (1 s) Starts: 0
com.levelup.beautifulwidgets (com.levelup.beautifulwidgets.Beautiful Widgets): Sys: (0 s) Us: 1 s (1 s) Starts: 37
com.android.phone (Dialer): Sys: (0 s) Us: 1 s (1 s) Starts: 1
*wakelock* (com.google.android.gm.Gmail): Sys: 1 s (1 s) Us: (0 s) Starts: 0
com.handmark.tweetcaster.premium (com.handmark.tweetcaster.premium.TweetCaster Pro): Sys: (0 s) Us: 1 s (1 s) Starts: 1
com.discoverfinancial.mobile (com.discoverfinancial.mobile.Discover): Sys: (0 s) Us: 1 s (1 s) Starts: 1
events/0 (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
als_wq (0): Sys: 1 s (1 s) Us: (0 s) Starts: 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.authentec.TrueSuiteMobile (com.authentec.GfxEngine.Control.GfxService)
Active since: 32 s
Last activity: 1 h 32 m 2 s
Crash count:0
net.dinglisch.android.taskerm (net.dinglisch.android.taskerm.MonitorService)
Active since: 39 s
Last activity: 2 h 2 m
Crash count:0
com.google.android.apps.googlevoice (com.google.android.apps.googlevoice.UpdateService)
Active since: 1 h 54 m 36 s
Last activity: 1 h 59 m 5 s
Crash count:0
com.motorola.usb (com.motorola.usb.UsbService)
Active since: 33 s
Last activity: 33 s
Crash count:0
com.android.email (com.android.exchange.SyncManager)
Active since: 34 s
Last activity: 1 h 59 m 32 s
Crash count:0
com.google.android.talk:videoChat (com.google.android.talk.videochat.VideoChatService)
Active since: 58 m 55 s
Last activity: 53 m 27 s
Crash count:0
com.crittercism.service (com.crittercism.service.CrittercismService)
Active since: 45 s
Last activity: 2 h 1 m 15 s
Crash count:0
net.cdeguet.smartkeyboardpro (net.cdeguet.smartkeyboardpro.SmartKeyboard)
Active since: 24 s
Last activity: 24 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 24 s
Last activity: 24 s
Crash count:0
system (com.android.internal.service.wallpaper.ImageWallpaper)
Active since: 24 s
Last activity: 24 s
Crash count:0
com.android.systemui (com.android.systemui.statusbar.StatusBarService)
Active since: 22 s
Last activity: 22 s
Crash count:0
com.google.android.apps.googlevoice (com.google.android.apps.googlevoice.CallLogService)
Active since: 44 s
Last activity: 1 h 58 m 55 s
Crash count:0
com.th.android.widget.gTabsimiClock (com.th.android.widget.gTabsimiClock.UpdateService)
Active since: 47 s
Last activity: 2 h 1 m 58 s
Crash count:0
com.bel.android.dspmanager (com.bel.android.dspmanager.HeadsetService)
Active since: 32 s
Last activity: 32 s
Crash count:0
android.tts (android.tts.TtsService)
Active since: 6 h 54 m 1 s
Last activity: 1 h 59 m 57 s
Crash count:0
com.android.phone (com.motorola.fastdormancy.FastDormancyService)
Active since: 34 s
Last activity: 34 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 33 s
Last activity: 33 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 21 s
Last activity: 21 s
Crash count:0
com.handmark.tweetcaster.premium (com.handmark.tweetcaster.UpdateService)
Active since: 45 s
Last activity: 1 h 48 m 54 s
Crash count:0
com.cyanogenmod.dockaudio (com.cyanogenmod.dockaudio.ListenSwitch)
Active since: 34 s
Last activity: 34 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 21 s
Last activity: 25 s
Crash count:0
com.mhuang.overclocking (com.mhuang.overclocking.ProfilesService)
Active since: 36 s
Last activity: 1 h 38 m 16 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 27 s
Last activity: 1 h 50 m 22 s
Crash count:0
com.facebook.katana (com.facebook.katana.service.UploadManager)
Active since: 31 s
Last activity: 1 h 50 m 22 s
Crash count:0

kshiuan said:
I cannot figure out what AlarmManager and FDCompleteTime is and how I can stop that from wakelocking. Everything else seems pretty normal.
Click to expand...
Click to collapse
AlarmManager:
AlarmManager provides access to the system alarm services. In simple English, it provides alarm services for the phone, like 'ring in an hour time'. You problem is that Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. What that means that if an app is requesting to be 'called' by the Alarm Service, the phone will not sleep. Once onReceive() returns, the Alarm Manager releases the wake lock and the phone will in some cases sleep as soon as your onReceive() method completes. What that means, is that once the app/apps say, figuratively "I got the Alarm Call and I did what I wanted to do!" the AlarmManager will release the wake lock and the phone will go to sleep.
Solution: Check for apps that call on AlarmManger. Apps that request for current time can also call upon AlarmManager. Apps that are well programmed and request, for example, the current time, but is non-crucial for that app to know that info when the phone is sleeping can use RTC. Using that, your phone will only give that info when it wakes up. However, apps can also use RTC_WAKEUP, which will force your phone to wake up, registering as a wakelock under AlarmManager, not the app that requested it. More info can be found here.
FDCompleteTime:
FDCompleteTime is the time which your phone takes to 'complete' FD, or Fast Dormancy. FD usually saves battery. For example, email update checks are done by the email application which, after receiving the server response, knows that it is not going to transmit or receive any further data. At that point the phone can tell the network “I don’t need to keep this connection active any more” and the network can immediately move the phone to a low energy state as preferred by the network operator, saving wasted battery and network resource. FDCompleteTime is there when the phone tells the network that “I don’t need to keep this connection active any more”. Usually, it is a very short period of time, but when your phone does not get a answer from the network, this time can stretch.
Solutions:FD can be turned off on some phones, but AFAIK, not on the ATRIX. I would STRONGLY DISCOURAGE you from touching FD though. More info on FD (VERY TECHNICAL) by the GSMA (random: I like their logo, especially the GSMA part. Love that font!) can be found here.
Hope that helps!
To ALL: I am NOT an expert. If I did say something wrong, or you think something is not right, or can be put a better way, please tell me. We both learn from the experience. Thanks!

[Q] Wi-Fi keeping phone awake 50% of the time - with BetterBatteryStats dump

Since around Thanksgiving, my battery has been draining in about 36 hours when it normally lasts 3 - 4 days. What I gathered from BetterBatteryStats is that the Wi-Fi is keeping the phone from sleeping about half the time. I used a different app to monitor data usage, and Wi-Fi traffic was low. My guess is that an app is frequently accessing the Wi-Fi without sending much (or any) data. Is there a way to find the culprit without uninstalling apps one by one?
Code:
===================
General Information
===================
BetterBatteryStats version: 1.11.0.0
Creation Date: 2012-12-13 15:24:34
Statistic Type: (3) Since Unplugged
Since 1 d 15 h 50 m 17 s
VERSION.RELEASE: 2.3.4
BRAND: tmobile
DEVICE: glacier
MANUFACTURER: HTC
MODEL: HTC Glacier
OS.VERSION: 2.6.35.10-g4dcb781
BOOTLOADER: 0.89.0006
HARDWARE: glacier
FINGERPRINT: tmobile/htc_glacier/glacier:2.3.4/GRJ22/209954.1:user/release-keys
ID: GRJ22
TAGS: release-keys
USER: unknown
PRODUCT: htc_glacier
RADIO: unknown
Rooted: false
============
Battery Info
============
Level lost [%]: 95 Bat.: 95% (100% to 5%) [2.4%/h]
Voltage lost [mV]: 620 (4207-3587)
===========
Other Usage
===========
Wifi On (): 1 d 15 h 50 m 17 s (143417 s) Ratio: 100.0%
Wifi Running (): 1 d 15 h 50 m 17 s (143417 s) Ratio: 100.0%
No Data Connection (): 1 d 13 h 3 m 15 s (133395 s) Ratio: 93.0%
No or Unknown Signal (): 1 d 13 h 3 m 15 s (133395 s) Ratio: 93.0%
Awake (): 20 h 13 m 4 s (72784 s) Ratio: 50.7%
Deep Sleep (): 19 h 37 m 12 s (70632 s) Ratio: 49.2%
Good Signal (): 2 h 29 m 45 s (8985 s) Ratio: 6.3%
Screen On (): 12 m 46 s (766 s) Ratio: 0.5%
Phone On (): 6 m 19 s (379 s) Ratio: 0.3%
=========
Wakelocks
=========
WifiService (Android System): 18 h 48 m 7 s (67687 s) Count:4645 47.2%
AlarmManager (Android System): 1 h 54 m 36 s (6876 s) Count:14892 4.8%
*sync* (Calendar): 7 m 22 s (442 s) Count:29 0.3%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 2 m 51 s (171 s) Count:4 0.1%
WifiStateTracker (Android System): 2 m 33 s (153 s) Count:363 0.1%
ActivityManager-Launch (Android System): 1 m 39 s (99 s) Count:316 0.1%
*network-location* (com.groupon.Groupon): 1 m 18 s (78 s) Count:40 0.1%
keyguardWakeAndHandOff (Android System): 1 m 7 s (67 s) Count:4664 0.0%
MdmDataReporter (com.mobidia.android.mdm.My Data Manager): 1 m 6 s (66 s) Count:270 0.0%
GTALK_ASYNC_CONN (Google Services): 54 s (54 s) Count:17 0.0%
BatteryServiceWakeLock (com.modroid.battery.Battery Graph): 53 s (53 s) Count:478 0.0%
*network-location* (Android System): 52 s (52 s) Count:349 0.0%
GSM (Dialer): 51 s (51 s) Count:50 0.0%
*sync* (com.google.android.gm.Gmail): 39 s (39 s) Count:17 0.0%
MAIL_BLK (com.htc.android.mail.Mail): 28 s (28 s) Count:28 0.0%
RILJ (Dialer): 27 s (27 s) Count:490 0.0%
*network-location* (Calendar): 27 s (27 s) Count:85 0.0%
MAIL_PWR_LOCK (com.htc.android.mail.Mail): 26 s (26 s) Count:14 0.0%
sleep_broadcast (Android System): 18 s (18 s) Count:663 0.0%
SYNCHRONIZED (com.htc.android.mail.Mail): 18 s (18 s) Count:27 0.0%
*sync* (com.htc.android.mail.Mail): 15 s (15 s) Count:24 0.0%
*sync* (Google Services): 14 s (14 s) Count:161 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 13 s (13 s) Count:26 0.0%
GTALK_CONN (Google Services): 10 s (10 s) Count:798 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 8 s (8 s) Count:38 0.0%
ActivityManager-Sleep (Android System): 7 s (7 s) Count:14919 0.0%
Event Log Service (Google Services): 6 s (6 s) Count:254 0.0%
htcCheckinService (Android System): 6 s (6 s) Count:4666 0.0%
GpsLocationProvider (Android System): 5 s (5 s) Count:589 0.0%
com.smartandroidapps.audiowidgetlib (com.smartandroidapps.audiowidget.AudioManager): 5 s (5 s) Count:24 0.0%
*sync* (com.google.android.music.Google Play Music): 4 s (4 s) Count:2 0.0%
Checkin Service (Google Services): 4 s (4 s) Count:947 0.0%
*network-location-cell-update* (Google Services): 4 s (4 s) Count:156 0.0%
LocationManagerService (Android System): 3 s (3 s) Count:177 0.0%
*network-location* (Google Services): 3 s (3 s) Count:175 0.0%
HtcPhoneSensorFunctions (Dialer): 2 s (2 s) Count:508 0.0%
CalendarAppWidgetProvider (Calendar): 2 s (2 s) Count:70 0.0%
NetworkLocationCacheUpdater (com.google.android.apps.maps.Maps): 1 s (1 s) Count:1 0.0%
PreventScreenOn Partial (Android System): 1 s (1 s) Count:355 0.0%
SyncManagerHandleSyncAlarm (Android System): 1 s (1 s) Count:483 0.0%
Proximity Partial (Android System): 1 s (1 s) Count:30 0.0%
Event Log Handoff (Google Services): 1 s (1 s) Count:877 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 19 h 10 m 10 s (69010 s) Cnt:(c/wc/ec)6336/0/0 48.1%
"dhd_wake_lock" (): 1 h 23 m 50 s (5030 s) Cnt:(c/wc/ec)19077/937/19077 3.5%
"alarm_rtc" (): 29 m 4 s (1744 s) Cnt:(c/wc/ec)3435/0/396 1.2%
"alarm" (): 3 m 54 s (234 s) Cnt:(c/wc/ec)11754/1/0 0.2%
"dhd_wake_lock_link_event" (): 3 m 40 s (220 s) Cnt:(c/wc/ec)14/0/14 0.1%
"deleted_wake_locks" (): 3 m 1 s (181 s) Cnt:(c/wc/ec)19979/0/0 0.1%
"SMD_DATA5" (): 2 m 33 s (153 s) Cnt:(c/wc/ec)290/70/290 0.1%
"dhd_dpc_thread" (): 2 m 32 s (152 s) Cnt:(c/wc/ec)34524/0/0 0.1%
"SMD_DS" (): 2 m 9 s (129 s) Cnt:(c/wc/ec)509/17/509 0.1%
"radio-interface" (): 1 m 14 s (74 s) Cnt:(c/wc/ec)134/0/0 0.1%
"AudioHardwareOut" (): 19 s (19 s) Cnt:(c/wc/ec)14/0/0 0.0%
"audio_pcm" (): 19 s (19 s) Cnt:(c/wc/ec)14/0/0 0.0%
"audpp" (): 19 s (19 s) Cnt:(c/wc/ec)14/0/0 0.0%
"proximity" (): 17 s (17 s) Cnt:(c/wc/ec)24/0/24 0.0%
"rmt_storage" (): 9 s (9 s) Cnt:(c/wc/ec)16/0/0 0.0%
"qmi0" (): 7 s (7 s) Cnt:(c/wc/ec)16/0/16 0.0%
"SMD_RPCCALL" (): 6 s (6 s) Cnt:(c/wc/ec)32983/2724/0 0.0%
"ApmCommandThread" (): 2 s (2 s) Cnt:(c/wc/ec)46/0/0 0.0%
"vbus_present" (): 2 s (2 s) Cnt:(c/wc/ec)0/0/1 0.0%
"dhd_watchdog_thread" (): 1 s (1 s) Cnt:(c/wc/ec)24298/0/0 0.0%
"rpc-interface" (): 1 s (1 s) Cnt:(c/wc/ec)2556/0/0 0.0%
"rpc_reply" (): 1 s (1 s) Cnt:(c/wc/ec)2389/0/0 0.0%
"rpc_read" (): 1 s (1 s) Cnt:(c/wc/ec)23967/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)93/0/0 0.0%
"rpc_server" (): (0 s) Cnt:(c/wc/ec)112/0/0 0.0%
"rpc_reply" (): (0 s) Cnt:(c/wc/ec)107/0/0 0.0%
"rpc_read" (): (0 s) Cnt:(c/wc/ec)1489/0/0 0.0%
"port_list" (): (0 s) Cnt:(c/wc/ec)80313/0/0 0.0%
"gpio_input" (): (0 s) Cnt:(c/wc/ec)237/14/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)27203/0/0 0.0%
"event4-1348" (system, com.android.browser): (0 s) Cnt:(c/wc/ec)70/3/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
245.76 MHz (): 18 h 32 m 13 s 46.5%
368.64 MHz (): 4 m 41 s 0.2%
768 MHz (): 5 m 36 s 0.2%
1.02 GHz (): 1 h 33 m 16 s 3.9%
Deep Sleep (): 19 h 37 m 12 s 49.2%
==================
Reference overview
==================
Custom: Reference custom_ref created 1 m 50 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
Since charged: Reference since_charged_ref created 59 m 24 s (Wl: 0 elements; KWl: 26elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 7 elements; CPU: 5 elements)
Since screen off: Reference since_screen_off created 1 d 16 h 49 m 41 s (Wl: 42 elements; KWl: 35elements; NetS: null; Alrm: null; Proc: 16 elements; Oth: 9 elements; CPU: 5 elements)
Since unplugged: Reference since_unplugged_ref created 59 m 23 s (Wl: 0 elements; KWl: 26elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 7 elements; CPU: 5 elements)
Since boot: Reference since_boot created 1 m 52 s (Wl: 0 elements; KWl: 5elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 0 elements; CPU: 5 elements)

What is the WIFI sleep policy of your device set to?

I hadn't changed the sleep policy, which has always been set to "never" and my battery still lasted 3+ days. Maintaining a Wi-Fi connection actually uses very little power, despite people mistakenly blaming it as a power drainer. It's always an app or setting causing undesired use of the Wi-Fi that can cause battery issues, not the Wi-Fi itself.
Anyway, problem solved. Using a data monitor I saw a lot of activity coming from the DHCP service. It was actually a problem with the DHCP lease time on my router, and the phone was trying to renew its IP address thousands of times a day. I fixed the lease time and now one battery charge lasts more than 3 days again.

I'm not certain if it helps, but I use DroidWall to prevent most of the apps from accessing the internet. You can customize which apps you want to give access to Wifi and/or Data.
It should help your battery a bit.

[Q] Battery Drain Due To Suspend_Backoff Kernel Wakelock, Suspect Wi-Fi

Hi, I've been having issues with the suspend_backoff kernel wakelock since installing CM 10.1.3 stable. It is a fresh install (performed reset in CWM) with almost no user apps. I have disabled and signed out of most Google services, e.g. Google+, Hangouts, Google apps location, Google search, tailored ads, app verification. Bluetooth, NFC, and GPS are all disabled.
When Wi-Fi is enabled, I seem to get "no data connection". The phone is being kept awake by suspend_backoff.
When Wi-Fi is disabled and I am connected to 3G, this problem disappears and the phone is able to enter deep sleep.
I've tried to search for a solution. It is unrelated to the old msm_hsic_host wakelock problem that was fixed upstream by Google. It is also unrelated to Google Chrome problem, as it is not installed. I have tried deleting data and cache for Google apps and services, which does not appear to fix the issue.
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-10-08 11:28:28
Statistic Type: Boot to Current
Since 1 h 32 m 23 s
VERSION.RELEASE: 4.2.2
BRAND: google
DEVICE: mako
MANUFACTURER: LGE
MODEL: Nexus 4
OS.VERSION: 3.4.0-perf-g825e82a
BOOTLOADER: MAKOZ10l
HARDWARE: mako
FINGERPRINT: google/occam/mako:4.2.2/JDQ39/573038:user/release-keys
ID: JDQ39E
TAGS: test-keys
USER: jenkins
PRODUCT: occam
RADIO: M9615A-CEFWMAZM-2.0.1700.33
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -4% (90% to 86%) [2.6%/h]
Voltage lost [mV]: (4101-4116) [-9.8%/h]
===========
Other Usage
===========
Deep Sleep (): 18 m 28 s (1108 s) Ratio: 19.9%
Awake (): 1 h 13 m 55 s (4435 s) Ratio: 80.0%
Screen On (): 2 m 9 s (129 s) Ratio: 2.3%
Wifi On (): 1 h 32 m 23 s (5543 s) Ratio: 100.0%
Wifi Running (): 1 h 32 m 23 s (5543 s) Ratio: 100.0%
No Data Connection (): 1 h 28 m 20 s (5300 s) Ratio: 95.6%
No or Unknown Signal (): 1 h 28 m 20 s (5300 s) Ratio: 95.6%
Good Signal (): (0 s) Ratio: 0.0%
Screen dark (): 2 m 9 s (129 s) Ratio: 2.3%
=========
Wakelocks
=========
RILJ (Phone): 1 m 34 s (94 s) Count:177 1.7%
ConnectivityService (Android System): 1 m 7 s (67 s) Count:360 1.2%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 14 s (14 s) Count:30 0.3%
GCM_CONN_ALARM (Google Services): 13 s (13 s) Count:200 0.2%
AlarmManager (Android System): 12 s (12 s) Count:340 0.2%
GpsLocationProvider (Android System): 5 s (5 s) Count:190 0.1%
AudioOut_2 (1013): 4 s (4 s) Count:7 0.1%
Checkin Service (Google Services): 4 s (4 s) Count:183 0.1%
ActivityManager-Launch (Android System): 4 s (4 s) Count:140 0.1%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 3 s (3 s) Count:7 0.1%
show keyguard (Android System): 3 s (3 s) Count:9 0.1%
WakefulIntentService[GCoreUlr-ExternalChangeService] (Google Services): 2 s (2 s) Count:313 0.1%
DHCP (Android System): 2 s (2 s) Count:214 0.1%
SyncLoopWakeLock (Android System): 2 s (2 s) Count:461 0.0%
GCM_CONN (Google Services): 2 s (2 s) Count:304 0.0%
AudioOut_3 (1013): 2 s (2 s) Count:2 0.0%
NetworkStats (Android System): 2 s (2 s) Count:126 0.0%
SMSDispatcher (Phone): 2 s (2 s) Count:13 0.0%
*sync*_subscribedfeeds_Account {name=b8c35ab0c3f90d29ae9cc189659604ee, type=com.google} (Google Services): 1 s (1 s) Count:3 0.0%
MediaScannerService (Media): 1 s (1 s) Count:2 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:352 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:248 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:471 0.0%
================
Kernel Wakelocks
================
"suspend_backoff" (): 54 m 31 s (3271 s) Cntc/wc/ec)330/0/330 58.8%
"msm_hsic_host" (): 3 m 35 s (215 s) Cntc/wc/ec)128/17/0 3.9%
"PowerManagerService" (): 3 m 31 s (211 s) Cntc/wc/ec)384/0/0 3.8%
"radio-interface" (): 1 m 33 s (93 s) Cntc/wc/ec)100/0/0 1.7%
"alarm_rtc" (): 1 m 13 s (73 s) Cntc/wc/ec)87/7/26 1.3%
"alarm" (): 4 s (4 s) Cntc/wc/ec)192/1/0 0.1%
"wlan" (): 3 s (3 s) Cntc/wc/ec)19/0/0 0.1%
"PowerManagerService.Broadcasts" (): 1 s (1 s) Cntc/wc/ec)19/0/0 0.0%
"qcril" (): 1 s (1 s) Cntc/wc/ec)344/0/0 0.0%
"KeyEvents" (): 1 s (1 s) Cntc/wc/ec)5732/0/0 0.0%
"power-supply" (): 1 s (1 s) Cntc/wc/ec)87/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)3407/0/1 0.0%
"qmuxd_port_wl_9" (): (0 s) Cntc/wc/ec)1263/0/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.gms (): Wakeups: 36
Alarms: 22, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 1, Intent: com.google.android.gms.recovery.WAKEUP
Alarms: 8, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 5, Intent: com.google.android.intent.action.MCS_HEARTBEAT
android (): Wakeups: 16
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 10, Intent: android.net.wifi.DHCP_RENEW
Alarms: 5, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 1, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
com.android.phone (): Wakeups: 11
Alarms: 8, Intent: com.android.internal.telephony.gprs-reconnect.0
Alarms: 3, Intent: com.android.internal.telephony.gprs-data-stall
com.android.vending (): Wakeups: 6
Alarms: 3, Intent: {com.android.vending
Alarms: 3, Intent: {com.android.vending
com.google.android.gsf (): Wakeups: 3
Alarms: 3, Intent: {com.google.android.gsf
com.cyanogenmod.lockclock (): Wakeups: 1
Alarms: 1, Intent: {com.cyanogenmod.lockclock
com.google.android.talk (): Wakeups: 1
Alarms: 1, Intent: com.google.android.apps.babel.CLEANUP_DB
bbc.mobile.weather (): Wakeups: 1
Alarms: 1, Intent: {bbc.mobile.weather
com.mobitobi.android.gentlealarm (): Wakeups: 1
Alarms: 1, Intent: com.mobitobi.android.gentlealarm.ALARM_INIT
com.google.android.apps.plus (): Wakeups: 1
Alarms: 1, Intent: com.google.android.apps.plus.NEW_PICTURE
com.android.providers.calendar (): Wakeups: 1
Alarms: 1, Intent: com.android.providers.calendar.intent.CalendarProvider2
======================
Network (requires root)
======================
10067 (Wifi) (com.google.android.googlequicksearchbox.Google Search): 266.0 KBytes 34.2%
0 (Wifi) (0): 195.0 KBytes 25.1%
10051 (Wifi) (Google Services): 159.0 KBytes 20.5%
10061 (Wifi) (com.android.vending.Google Play Store): 84.0 KBytes 10.9%
10038 (Wifi) (com.google.android.configupdater.ConfigUpdater): 16.0 KBytes 2.1%
10005 (Wifi) (com.cyanogenmod.account.CyanogenMod Account): 11.0 KBytes 1.5%
10078 (Wifi) (com.asksven.betterbatterystats.BetterBatteryStats): 10.0 KBytes 1.3%
10051 (Mobile) (Google Services): 9.0 KBytes 1.3%
0 (Mobile) (0): 9.0 KBytes 1.2%
1014 (Wifi) (1014): 7.0 KBytes 0.9%
1000 (Wifi) (Android System): 6.0 KBytes 0.8%
1000 (Mobile) (Android System): 693.0 Bytes 0.1%
10018 (Wifi) (Media): 373.0 Bytes 0.0%
==========
CPU States
==========
384 MHz (): 1 h 8 m 39 s 74.3%
486 MHz (): 8 s 0.1%
594 MHz (): 37 s 0.7%
702 MHz (): 12 s 0.2%
810 MHz (): 3 s 0.1%
918 MHz (): 3 s 0.1%
1.03 GHz (): 1 m 15 s 1.4%
1.13 GHz (): 6 s 0.1%
1.24 GHz (): 14 s 0.3%
1.35 GHz (): 3 s 0.1%
1.46 GHz (): 5 s 0.1%
1.51 GHz (): 2 m 24 s 2.6%
Deep Sleep (): 18 m 28 s 19.9%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 22 s (Wl: 2 elements; KWl: 0elements; NetS: 7 elements; Alrm: 1 elements; Proc: 0 elements; Oth: 5 elements; CPU: 11 elements)
ref_current: Reference ref_current created 1 h 32 m 45 s (Wl: 23 elements; KWl: 13elements; NetS: 14 elements; Alrm: 11 elements; Proc: 12 elements; Oth: 9 elements; CPU: 13 elements)

[Q] n9005 battery drain

Hey,
My N9005 has recently started to experience battery drain. Couple weeks earlier It was around 0.3..0.5% per hour through the night. Now it is 0.9 and awake time is 2 hours out of 9.
I am rooted, wifi and 4g is on. Location is on (via Network). Google Now is off.
This is the extraction from BBS:
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2014-02-18 08:24:07
Statistic Type: Custom to Current
Since 8 h 42 m 54 s
VERSION.RELEASE: 4.4.2
BRAND: samsung
DEVICE: hlte
MANUFACTURER: samsung
MODEL: SM-N9005
OS.VERSION: 3.4.0-340325
BOOTLOADER: N9005XXUENA6
HARDWARE: qcom
FINGERPRINT: samsung/hltexx/hlte:4.4.2/KOT49H/N9005XXUENA6:user/release-keys
ID: KOT49H
TAGS: release-keys
USER: dpi
PRODUCT: hltexx
RADIO: N9005XXUENA2
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -8% (91% to 83%) [0.9%/h]
Voltage lost [mV]: (4146-4076) [8.0%/h]
===========
Other Usage
===========
Screen On (): 3 m 13 s (193 s) Ratio: 0.6%
Wifi On (): 8 h 42 m 54 s (31374 s) Ratio: 100.0%
Wifi Running (): 8 h 42 m 54 s (31374 s) Ratio: 100.0%
Deep Sleep (): 6 h 37 m 41 s (23861 s) Ratio: 76.1%
Awake (): 2 h 5 m 12 s (7512 s) Ratio: 23.9%
=========
Wakelocks
=========
NlpCollectorWakeLock (Google Services): 6 m 58 s (418 s) Count:35 34.7%
NlpWakeLock (com.google.android.googlequicksearchbox.Google Search): 6 m 1 s (361 s) Count:114 29.9%
AlarmManager (0): 2 m 32 s (152 s) Count:590 12.6%
TimaService (0): 1 m 15 s (75 s) Count:25 6.2%
LocationManagerService (0): 1 m 11 s (71 s) Count:114 5.9%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 20 s (20 s) Count:37 0.6%
StartingAlertService (Calendar): 15 s (15 s) Count:3 1.2%
AlarmManager (Google Services): 8 s (8 s) Count:57 0.7%
NlpWakeLock (Google Services): 8 s (8 s) Count:164 0.7%
VibratorService (com.sec.android.app.clockpackage.Clock): 8 s (8 s) Count:5 0.2%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 7 s (7 s) Count:2 0.6%
GCM_CONN (Google Services): 6 s (6 s) Count:39 0.5%
AlarmManager (com.facebook.katana.Facebook): 6 s (6 s) Count:49 0.5%
*sync*/gmail-ls/com.google/eM_ADDR (com.google.android.gm.Gmail): 6 s (6 s) Count:1 0.5%
hfm (com.google.android.googlequicksearchbox.Google Search): 6 s (6 s) Count:101 0.5%
AlarmManager (com.google.android.googlequicksearchbox.Google Search): 5 s (5 s) Count:107 0.4%
Event Log Service (Google Services): 5 s (5 s) Count:17 0.4%
ActivityManager-Launch (0): 4 s (4 s) Count:18 0.3%
AudioMix (0): 4 s (4 s) Count:2 0.3%
NlpLocationReceiverService (com.google.android.googlequicksearchbox.Google Search): 4 s (4 s) Count:125 0.3%
NetworkStats (0): 2 s (2 s) Count:17 0.2%
NlpWakeLock (0): 2 s (2 s) Count:1 0.2%
LocationManagerService (Google Services): 2 s (2 s) Count:221 0.2%
AlarmManager (com.sec.spp.push.Samsung Push Service): 2 s (2 s) Count:15 0.1%
AlarmManager (com.whatsapp.WhatsApp): 2 s (2 s) Count:18 0.1%
Icing (Google Services): 1 s (1 s) Count:17 0.1%
show keyguard (UID): 1 s (1 s) Count:2 0.1%
AlarmManager (com.android.chrome.Chrome): 1 s (1 s) Count:15 0.1%
SyncManagerHandleSyncAlarm (0): 1 s (1 s) Count:4 0.1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 s (1 s) Count:1 0.1%
GpsLocationProvider (0): 1 s (1 s) Count:8 0.1%
AlarmManager (Calendar): 1 s (1 s) Count:4 0.1%
DHCP (0): 1 s (1 s) Count:2 0.0%
StartingAlertService (com.android.calendar.S Planner): 1 s (1 s) Count:5 0.0%
UlrDispatchingService (Google Services): 1 s (1 s) Count:6 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
PowerManagerService.WakeLocks (): 17 m 47 s (1067 s) Cntc/wc/ec)940/164/0 3.4%
sec-battery-monitor (): 7 m 48 s (468 s) Cntc/wc/ec)4988/84/0 1.5%
alarm (): 7 m 35 s (455 s) Cntc/wc/ec)1350/532/0 1.5%
resume_wakelock (): 7 m 22 s (442 s) Cntc/wc/ec)4646/0/4646 1.4%
qpnp-vadc-ebd30a00 (): 4 m 36 s (276 s) Cntc/wc/ec)35214/2369/0 0.9%
mmc0:0001:2 (): 2 m 33 s (153 s) Cntc/wc/ec)21729/7235/0 0.5%
alarm_rtc (): 1 m 37 s (97 s) Cntc/wc/ec)195/125/0 0.3%
radio-interface (): 16 s (16 s) Cntc/wc/ec)20/4/0 0.1%
ssp_sensorhub_wake_lock (): 11 s (11 s) Cntc/wc/ec)12/2/11 0.0%
ipc00000021_Loc_hal_worker (): 8 s (8 s) Cntc/wc/ec)1432/90/0 0.0%
KeyEvents (): 6 s (6 s) Cntc/wc/ec)7849/265/0 0.0%
smdcntl0 (): 6 s (6 s) Cntc/wc/ec)197/8/0 0.0%
power-supply (): 5 s (5 s) Cntc/wc/ec)4985/83/0 -0.1%
ipc0000000d_rmt_storage (): 2 s (2 s) Cntc/wc/ec)5/0/0 0.0%
PowerManagerService.Broadcasts (): 1 s (1 s) Cntc/wc/ec)10/0/0 0.0%
event18-853 (): 1 s (1 s) Cntc/wc/ec)14/0/0 0.0%
rmt_storage_-1210977736 (): (0 s) Cntc/wc/ec)3/0/0 0.0%
ssp_wake_lock (): (0 s) Cntc/wc/ec)52/2/0 0.0%
rmt_storage_-1210978584 (): (0 s) Cntc/wc/ec)2/0/0 0.0%
event5-853 (): (0 s) Cntc/wc/ec)11/0/0 0.0%
ipc_rtr_smd_ipcrtr (): (0 s) Cntc/wc/ec)1531/105/0 0.0%
MediaPlayerService_Decode (): (0 s) Cntc/wc/ec)4/0/0 0.0%
qpnp-iadc-ebd30c00 (): (0 s) Cntc/wc/ec)25/7/0 0.0%
PowerManagerService.Display (): (0 s) Cntc/wc/ec)5/0/0 0.0%
qmuxd_port_wl_0 (): (0 s) Cntc/wc/ec)248/8/0 0.0%
ipc0000002a_Loc_hal_worker (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000022_Loc_hal_worker (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000003_rfs_access (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000017_time_daemon (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000010_time_daemon (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc0000001d_gsiff_daemon (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc0000000e_rmt_storage (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000007_thermal-engine (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc0000001b_thermal-engine (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000019_thermal-engine (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc0000000c_thermal-engine (): (0 s) Cntc/wc/ec)5/5/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.gms (): Wakeups: 162
Alarms: 109, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR
Alarms: 0, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 35, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 10, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION
Alarms: 2, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.playlog.uploader.UploaderAlarmReceiver}
Alarms: 4, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVE_COLLECTOR
Alarms: 1, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_PASSIVE_COLLECTOR
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.common.download.DownloadAlarmReceiver}
Alarms: 0, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLLECTION_TRIGGER
Alarms: 0, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_CACHE_UPDATER
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE cmp={com.google.android.gms/com.google.android.gms.icing.service.IndexWorkerService}
android (): Wakeups: 67
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 17, Intent: android.appwidget.action.APPWIDGET_UPDATE cmp={com.sec.android.widgetapp.easyfavoritescontactswidget/com.sec.android.widgetapp.easyfavoritescontactswidget.SeniorFavoriteWidgetProviderLarge}
Alarms: 4, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 44, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 0, Intent: edm.intent.action.elm.cleanrecords
Alarms: 0, Intent: com.android.server.LightsService.action.UPDATE_SVC_LED
Alarms: 0, Intent: com.android.server.action.UPDATE_TWILIGHT_STATE
Alarms: 1, Intent: com.android.server.IdleMaintenanceService.action.UPDATE_IDLE_MAINTENANCE_STATE
Alarms: 1, Intent: android.net.wifi.DHCP_RENEW
com.facebook.katana (): Wakeups: 49
Alarms: 35, Intent: com.facebook.push.mqtt.KeepaliveManager.ACTION_INEXACT_ALARM.com.facebook.katana
Alarms: 3, Intent: com.facebook.common.executors.WakingExecutorService.ACTION_ALARM.com.facebook.katana
Alarms: 11, Intent: com.facebook.analytics.service.AnalyticsEventUploader.ACTION_ALARM
Alarms: 0, Intent: {com.facebook.katana/com.facebook.ui.media.cache.MediaCacheCleanupService}
Alarms: 0, Intent: {com.facebook.katana/com.facebook.common.tempfile.TempFileCleanupService}
com.google.android.gsf (): Wakeups: 17
Alarms: 17, Intent: {com.google.android.gsf/com.google.android.gsf.checkin.EventLogService$Receiver}
com.sec.spp.push (): Wakeups: 9
Alarms: 0, Intent: com.sec.spp.push.receiver.PROVISIONING_ACTION
Alarms: 9, Intent: {com.sec.spp.push/com.sec.spp.push.heartbeat.HeartBeat}
Alarms: 0, Intent: com.sec.spp.push.ALARM_TIMER_ACTION
Alarms: 0, Intent: com.sec.spp.push.DAY_TIMER
com.google.android.apps.maps (): Wakeups: 9
Alarms: 9, Intent: {com.google.android.apps.maps/com.google.android.apps.gmm.prefetch.PrefetcherService}
com.google.android.googlequicksearchbox (): Wakeups: 8
Alarms: 8, Intent: {com.google.android.googlequicksearchbox/com.google.android.velvet.VelvetBackgroundTasksImpl$Service}
Alarms: 0, Intent: send_events cmp={com.google.android.googlequicksearchbox/com.google.android.voicesearch.logger.EventLoggerService}
com.whatsapp (): Wakeups: 2
Alarms: 0, Intent: ALARM_ACTION
Alarms: 1, Intent: ALARM_ROTATE_LOGS
Alarms: 0, Intent: ALARM_AVAILABLE_TIMEOUT
Alarms: 1, Intent: ALARM_MESSAGES_DB_BACKUP
Alarms: 0, Intent: com.whatsapp.MessageService.RECONNECT cmp={com.whatsapp/com.whatsapp.messaging.MessageService}
Alarms: 0, Intent: ALARM_CLIENT_PING_TIMEOUT
com.sec.android.app.clockpackage (): Wakeups: 2
Alarms: 1, Intent: com.samsung.sec.android.clockpackage.alarm.ALARM_ALERT
Alarms: 1, Intent: com.samsung.sec.android.clockpackage.alarm.NOTIFY_ALARM_LOCATION
com.sec.chaton (): Wakeups: 2
Alarms: 2, Intent: {com.sec.chaton/com.sec.common.util.log.collector.LogCollectorSender}
com.agilesoftresource (): Wakeups: 1
Alarms: 0, Intent: ALM cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
Alarms: 0, Intent: TSVCDT cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
Alarms: 1, Intent: ADM cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
Alarms: 0, Intent: CSR cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
com.android.calendar (): Wakeups: 1
Alarms: 1, Intent: com.sec.android.calendar.update_data cmp={com.android.calendar/com.android.calendar.magazine.CalendarUpdateRelatedDataReceiver}
com.sec.esdk.elm (): Wakeups: 1
Alarms: 1, Intent: com.sec.esdk.elm.alarm.SAVE_APICALLLOG
======================
Network (requires root)
======================
1000 (Wifi) (Android System): 639.0 KBytes 23.6%
10030 (Wifi) (com.android.chrome.Chrome): 529.0 KBytes 19.5%
10191 (Wifi) (com.google.android.googlequicksearchbox.Google Search): 526.0 KBytes 19.4%
0 (Wifi) (0): 506.0 KBytes 18.7%
10070 (Wifi) (Google Services): 148.0 KBytes 5.5%
10008 (Wifi) (sstream.app.My Magazine): 118.0 KBytes 4.4%
10276 (Wifi) (com.facebook.katana.Facebook): 67.0 KBytes 2.5%
0 (lo) (0): 48.0 KBytes 1.8%
10270 (lo) (com.agilesoftresource.AndroZip File Manager): 33.0 KBytes 1.3%
10069 (Wifi) (com.google.android.gm.Gmail): 22.0 KBytes 0.8%
10064 (Wifi) (com.google.android.apps.maps.Maps): 20.0 KBytes 0.7%
10264 (Wifi) (com.sec.android.daemonapp.Unified Daemon(EUR)): 14.0 KBytes 0.5%
10277 (Wifi) (com.macropinch.swan.Weather): 11.0 KBytes 0.4%
10054 (Wifi) (com.evernote.Evernote): 7.0 KBytes 0.3%
10270 (Wifi) (com.agilesoftresource.AndroZip File Manager): 5.0 KBytes 0.2%
10134 (Wifi) (com.sec.spp.push.Samsung Push Service): 5.0 KBytes 0.2%
10239 (Wifi) (ru.yandex.metro.Yandex.Metro): 1.0 KBytes 0.1%
10113 (Wifi) (com.android.vending.Google Play Store): 992.0 Bytes 0.0%
1014 (Wifi) (1014): 668.0 Bytes 0.0%
10266 (lo) (ru.sports.sochi2014.РћР˜-2014): 500.0 Bytes 0.0%
10030 (lo) (com.android.chrome.Chrome): 200.0 Bytes 0.0%
==========
CPU States
==========
300 MHz (): 1 h 5 m 50 s 12.6%
422.4 MHz (): 48 m 47 s 9.3%
652.8 MHz (): 6 m 19 s 1.2%
729.6 MHz (): 16 s 0.1%
883.2 MHz (): 1 m 21 s 0.3%
960 MHz (): 6 s 0.0%
1.04 GHz (): 9 s 0.0%
1.19 GHz (): 45 s 0.1%
1.27 GHz (): 9 s 0.0%
1.5 GHz (): 30 s 0.1%
1.57 GHz (): 1 s 0.0%
1.73 GHz (): 14 s 0.0%
1.96 GHz (): 21 s 0.1%
2.27 GHz (): 18 s 0.1%
Deep Sleep (): 6 h 37 m 41 s 76.1%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 4 h 19 m 27 s (Wl: 1 elements; KWl: 47elements; NetS: 48 elements; Alrm: 16 elements; Proc: 56 elements; Oth: 5 elements; CPU: 15 elements)
ref_charged: Reference ref_charged created 4 h 19 m 28 s (Wl: 2 elements; KWl: 47elements; NetS: 48 elements; Alrm: 16 elements; Proc: 56 elements; Oth: 5 elements; CPU: 15 elements)
ref_custom: Reference ref_custom created 10 h 10 m 5 s (Wl: 56 elements; KWl: 50elements; NetS: 62 elements; Alrm: 17 elements; Proc: 278 elements; Oth: 6 elements; CPU: 15 elements)
ref_current: Reference ref_current created 18 h 52 m 59 s (Wl: 64 elements; KWl: 50elements; NetS: 62 elements; Alrm: 20 elements; Proc: 281 elements; Oth: 6 elements; CPU: 15 elements)
Click to expand...
Click to collapse

Turn off Location / GPS and freeze Google Now.
Also you will get Loads of Battery saving tips from my thread here -
http://forum.xda-developers.com/show....php?t=2579075

Thanks for reply.
Google Now is off in settings. I don't want to turn GPS off (it wasn't off previously and there were neither batter drain nor huge awake time).
Anyway, I'll try it this night as an experiment.

Use only wifi for location, turn off GPS, and disable google location, that did the trick for me. Here is an image to show the terrible drain I had.

iterimpius said:
Use only wifi for location, turn off GPS, and disable google location, that did the trick for me. Here is an image to show the terrible drain I had.
Click to expand...
Click to collapse
Although you are probably right, this is not how it is supposed to be. I want to have GPS constatntly turned on and do not have battery drain as it previously was (even after upgrade to 4.4.2).
Thanks anyway - I'll let you know about the results next morning.

zipper3 said:
Although you are probably right, this is not how it is supposed to be. I want to have GPS constatntly turned on and do not have battery drain as it previously was (even after upgrade to 4.4.2).
Thanks anyway - I'll let you know about the results next morning.
Click to expand...
Click to collapse
Well, I guess you can still leave GPS on, it will drain little power. The problem with me was that google services were keeping the CPU awake, retrying to get location continuously, which ended up draining the batter, the device never goes to sleep.

So, I switched GPS OFF this night and the phone was awake 1 hour out of 8 hours and battery dropped by from 53 to 49% - not that bad, I guess. But still awake time seems high.

I think mmc0:0001:2 of Kernel wakelock is the culprit. My galaxy S4 LTE-A suffers from battety drain. I found the kernel wakelock only occurs when wifi is on. But when my S4 is connected to specific routers, wakeup count of the wakelock soars up. Yours is about a third of total count, which is very high. I suggest changing your router.. I tried some tricks to make it right, but none did work. Changing router did the trick. Total count of the kernel wakelock was still high, but wakeup count of it considerably dropped, and battery drain was gone.
Sent from my SHV-E330S using Tapatalk

Battery Drain
kulguy said:
I think mmc0:0001:2 of Kernel wakelock is the culprit. My galaxy S4 LTE-A suffers from battety drain. I found the kernel wakelock only occurs when wifi is on. But when my S4 is connected to specific routers, wakeup count of the wakelock soars up. Yours is about a third of total count, which is very high. I suggest changing your router.. I tried some tricks to make it right, but none did work. Changing router did the trick. Total count of the kernel wakelock was still high, but wakeup count of it considerably dropped, and battery drain was gone.
Sent from my SHV-E330S using Tapatalk
Click to expand...
Click to collapse
What do you mean by "change router"? I only have one router at home and my battery loss occurs everywhere I go anyway.

Help me NOT throw my N4 into a brick wall... (battery drain)

Hi,
I'll try to keep this short. I am reading about battery drain from this forum, and I am not finding what I am looking for. So while I continue to look. I figured I'd ask here in case someone can help.
I bought a N4 6-8 months ago with a defective Digitizer. I bought a replacement lcd/dig/front frame assembly and changed it. The phone worked great since a week ago.
A while back I noticed the gps was not working. I found a thread on here about the new front frame not having the proper grounds for the main board. I switched the conductive pads from my old frame (the ones that did not rip) and it worked for a day. After that, it didn't. So I bought copper tape and put some where the pads where. No change. I left it like that. Not sure if this is relevant, but what the hell.
a week and a half later, I clicked the stock phone app (which was deactivated) and the phone blacked out. When i plugged it into a computer, I got "transfer-mode, do not unplug) and the phone did not boot. I brought it home, plugged it into the wall charger, and it charged up. So i thought, cool! This is running stock android 5.0.1 or 5.1 i don't remember.
Woke up the next day, phone is dead, when i plug it in, i get solid red light.
Next day i read up, decide to jump start the battery using a charger with bare wires on the leads for 5-6 min and plus it back in. The phone lights up and starts charging. So i figure, battery is dead. I order one off ebay.
change battery with new one, phone charges up, I'm happy.
Next day, wake up, phone is dead. Plug it in, i get solid red light again. Jump-start the new battery and think maybe it is a sofware issue.
day after flash the phone with CM 10.2 (or what the latest stable build is) and hope for the best. It changes nothing.
next day i open up the phone and remove all the copper tape I installed thinking, maybe I shorted something. No change
day after I completely erase the phone and do a clean install of Android stock 5.1, no change
I then install betterbatterystats and start monitoring. I am not rooted so I don't have access to everything. but from what I can tell, no wakelocks and the phone is pretty much in deep sleep (91%) all night long, yet if I go to bed around 10 with 100% bat, at 5 in the morning i have less than 20%. Everything looks like it is okay to me. Is rooting to see all the stats a good idea?
since the clean install of android. I dont see all the app in the battery stats page, and everything is at 1-3%, which i find odd.
When i was on CM I had "Android idle at 6x%" and "cellphone idle" at 3x%. Not sure those where the exact titles, but something along the lines.
When the phone is fully charged, it says i have 8 hours left (which i find very low), but it seems more like 6-7 hours. and if it drops too low, i get solid red light...
I also noticed that when plugged into a computer, the phone takes forever to charge (like 6-7 hours until full from what android tell me) and if i use the phone when plugged into a computer, it actually discharges faster then it charges...
Can it be my microphone/charger/ect. module that is no good?
The phone literally went from fully functionnal, to totally ****ed in one seconds in my hands...
Any thoughts?

Try to root and track all the services..u might have a massive wakelock..but..i don.t know..this story it.s a nightmare :| it.s preety strange to have such a battery drain..
Sent from my Nexus 4 using XDA Free mobile app

Thank you. I just rooted the phone, I'll charge to 100% and post pics of what betterbatterystats shows.

Also u can try to calibrate the battery , u can find some apps on Play Store

Thanks I'll look into that too.
It's weird because today I only rooted the phone, and stock battery app tells me I have 12 hours on full charge (I still don't see everything in the list) instead of 8-9 hours...
In betterbatterystats i have 9.x%/hr battery drain, compared to 12-20%/hours before rooting... It makes no sense.
I'm charging to phone to full and I'll see what happened with the battery tomorrow morning.
Also I read in other threads here that it can possibly have something to do with the wifi network. I don't even know where to begin on this one... But i did log into a different network at work this week because the usual one wasn't available where i was in the building. Which I hadn't done until now, and my phone had been switching for one network to another when i moved in the building.
Like I said I don't even know where to start if it' sa network/router thing. And I don'T even know if it is at all possible that this could be the source of the problem. And nothing changed at home.
I'm just considering every possible options as I am really stumped, and nothing that has happened until now makes sense... Like the phone getting better battery life from rooting or monitoring with BBS while rooted. It makes no sense.
I didn't mention but all localisation and wifi scanning options have been deactivated. Brightness is at minimum with auto brightness on. Wifi is always on during sleep because I use Fongo to make and receive calls on VoIP.
I never checked battery status before, but i seem to remember having 16-20 hours of battery life if I didn't use the phone.
I can live with having 5-8 hours of usage time, but as is, if i don't fully charge the phone before going to bed (i left it plugged in the last few days), it's dead in the morning and i have to open up the phone to boost the battery....
Thanks again for the help, I'll see if my phone is dead tomorrow, and try a calibration app.

So phone was 100% when i went to bed down to 27% when i woke up. From what i can see, no wakelocks. When i look at stock battery app, i get a steady descending slope to 0% and the numbers don't make sense either. I'll try to attach a pic (sorry the phone is in french)
I decided to see what would happen if i let the phone go down as low as it could. I was at about 18% while using the phone (i think i was looking at instagram or this forum on tapatalk) and the phone blacked out.
It would not boot up and when I plugged it in. I got Solid red light again. The phone won't boot, won't charge.
So i had to take my battery out and boost it again before the phone would recognise it and charge it. The battery is new, from ebay. Is it possible the battery is a dud? then again i had the same results with my old battery. And the one I got from ebay looks pretty much the same as the old one, tagged LG BL-T5 and the seller was a power seller.
Here is a pic of the stock battery settings app, and the text dump from BBS. Thanks for any help
{
"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"
}
BetterBatteryStats-2015-04-23_071904024.txt
Open with
===================
General Information
===================
BetterBatteryStats version: 2.0.0.0
Creation Date: 2015-04-23 07:19:03
Statistic Type: Unplugged to Current
Since 9 h 49 m 30 s
VERSION.RELEASE: 5.1
BRAND: google
DEVICE: mako
MANUFACTURER: LGE
MODEL: Nexus 4
OS.VERSION: 3.4.0-perf-gf75bb4f
BOOTLOADER: MAKOZ30f
HARDWARE: mako
FINGERPRINT: google/occam/mako:5.1/LMY47O/1783956:user/release-keys
ID: LMY47O
TAGS: release-keys
USER: android-build
PRODUCT: occam
RADIO: M9615A-CEFWMAZM-2.0.1701.06
Rooted: true
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -73%(100% to 27%) [7,4%/h]
Voltage lost [mV]: (4255-3562) [70,6%/h]
===========
Other Usage
===========
Deep Sleep (): 9 h 39 m 54 s 98,4%
Awake (): 9 m 35 s 1,6%
Screen On (): 2 m 42 s 0,5%
Wifi On (): 9 h 49 m 30 s 100,0%
Wifi Running (): 9 h 49 m 30 s 100,0%
No Data Connection (): 9 h 49 m 30 s 100,0%
No or Unknown Signal (): 9 h 49 m 30 s 100,0%
Screen dark (): 2 m 42 s 0,5%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
*alarm* (Système Android): 31 s Count:381 0,1%
NextAlarmTracker (Système Android): 24 s Count:83 0,1%
FbClientConnManager (com.facebook.katana.Facebook): 15 s Count:11 0,0%
*net_scheduler* (Services Google): 14 s Count:431 0,0%
*sync*/gmail-ls/com.google/[email protected] (com.google.android.gm.Gmail): 9 s Count:9 0,0%
Checkin Service (Services Google): 9 s Count:359 0,0%
*sync*/com.google.android.apps.plus.content.EsProvider/com.google/[email protected] (com.google.android.apps.plus.Google+): 6 s Count:5 0,0%
FbClientConnManager (com.facebook.orca.Messenger): 6 s Count:5 0,0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 5 s Count:4 0,0%
Config Service fetch (Services Google): 5 s Count:21 0,0%
*backup* (Système Android): 4 s Count:103 0,0%
Icing (Services Google): 3 s Count:69 0,0%
*sync*/com.google.android.apps.docs.editors.trix/com.google/[email protected] (com.google.android.apps.docs.editors.sheets.Feuilles de calcul): 2 s Count:3 0,0%
Event Log Service (Services Google): 2 s Count:48 0,0%
*sync*/subscribedfeeds/com.google/[email protected] (Services Google): 2 s Count:49 0,0%
GCM_CONN (Services Google): 1 s Count:341 0,0%
GCM_CONN_ALARM (Services Google): 1 s Count:23 0,0%
BaseSyncManager (com.google.android.apps.docs.editors.sheets.Feuilles de calcul): 1 s Count:1 0,0%
hangouts_rtcs (com.google.android.talk.Hangouts): 1 s Count:4 0,0%
================
Kernel Wakelocks
================
"PowerManagerService.WakeLocks" (): 2 m 32 s Cntc/wc/ec)472/0/0 0,4%
"msm_hsic_host" (): 57 s Cntc/wc/ec)51/26/0 0,2%
"qcom_rx_wakelock" (): 41 s Cntc/wc/ec)881/458/881 0,1%
"alarm_rtc" (): 11 s Cntc/wc/ec)258/231/0 0,0%
"suspend_backoff" (): 9 s Cntc/wc/ec)1/0/1 0,0%
"alarm" (): 6 s Cntc/wc/ec)457/0/0 0,0%
"radio-interface" (): 5 s Cntc/wc/ec)8/0/0 0,0%
"sns_async_ev_wakelock" (): 3 s Cntc/wc/ec)3/0/0 0,0%
"kickstart" (): 1 s Cntc/wc/ec)7/0/0 0,0%
"KeyEvents" (): Cntc/wc/ec)1568/0/0 0,0%
"power-supply" (): Cntc/wc/ec)-22/0/0 0,0%
"mmc0_detect" (): Cntc/wc/ec)844/0/0 0,0%
"PowerManagerService.Display" (): Cntc/wc/ec)3/0/0 0,0%
"PowerManagerService.Broadcasts" (): Cntc/wc/ec)6/0/0 0,0%
"qmuxd_port_wl_9" (): Cntc/wc/ec)143/0/0 0,0%
======================================================
Processes (requires root / system app on Android 4.4+)
======================================================
system (Système Android): Uid: 1000 Sys: 12 s Us: 24 s Starts: 0
com.asksven.betterbatterystats (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10113 Sys: 6 s Us: 17 s Starts: 0
surfaceflinger (Système Android): Uid: 1000 Sys: 6 s Us: 7 s Starts: 0
mmcqd/0 (0): Uid: 0 Sys: 14 s Us: Starts: 0
com.android.systemui (com.android.systemui.IU système): Uid: 10024 Sys: 2 s Us: 10 s Starts: 0
com.facebook.katana (com.facebook.katana.Facebook): Uid: 10096 Sys: 4 s Us: 6 s Starts: 0
com.fongo.dellvoice (com.fongo.dellvoice.Fongo): Uid: 10090 Sys: 10 s Us: Starts: 0
com.google.android.gm (com.google.android.gm.Gmail): Uid: 10074 Sys: 1 s Us: 6 s Starts: 1
com.facebook.orca (com.facebook.orca.Messenger): Uid: 10112 Sys: 2 s Us: 3 s Starts: 0
mpdecision (0): Uid: 0 Sys: 5 s Us: Starts: 0
com.google.process.gapps (Services Google): Uid: 10009 Sys: 1 s Us: 3 s Starts: 0
com.google.android.gms (Services Google): Uid: 10009 Sys: 2 s Us: 2 s Starts: 0
ueventd (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/0:3 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/u:21 (0): Uid: 0 Sys: 2 s Us: Starts: 0
*wakelock* (com.facebook.katana.Facebook): Uid: 10096 Sys: 1 s Us: Starts: 0
kworker/u:4 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/u:25 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/u:30 (0): Uid: 0 Sys: 2 s Us: Starts: 0
com.android.launcher (com.android.launcher.Lanceur d'appli): Uid: 10016 Sys: Us: 1 s Starts: 0
kworker/0:2 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/u:35 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/0:5 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:7 (0): Uid: 0 Sys: 1 s Us: Starts: 0
migration/0 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/0:0 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:9 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:22 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:37 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:26 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:34 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:28 (0): Uid: 0 Sys: 1 s Us: Starts: 0
*wakelock* (com.facebook.orca.Messenger): Uid: 10112 Sys: 1 s Us: Starts: 0
jbd2/mmcblk0p23 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:18 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:2 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:13 (0): Uid: 0 Sys: 1 s Us: Starts: 0
com.google.android.apps.plus (com.google.android.apps.plus.Google+): Uid: 10071 Sys: Us: 1 s Starts: 0
kworker/u:38 (0): Uid: 0 Sys: 1 s Us: Starts: 0
logd (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:23 (0): Uid: 0 Sys: 1 s Us: Starts: 0
com.google.android.apps.docs.editors.sheets (com.google.android.apps.docs.editors.sheets.Feuilles de calcul): Uid: 10045 Sys: Us: 1 s Starts: 1
kworker/u:17 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:14 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:10 (0): Uid: 0 Sys: 1 s Us: Starts: 0
*wakelock* (Services Google): Uid: 10009 Sys: Us: Starts: 0
kworker/u:6 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:40 (0): Uid: 0 Sys: 1 s Us: Starts: 0
zygote (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:27 (0): Uid: 0 Sys: 1 s Us: Starts: 0
*wakelock* (com.google.android.apps.plus.Google+): Uid: 10071 Sys: Us: Starts: 0
kworker/u:20 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:8 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:5 (0): Uid: 0 Sys: 1 s Us: Starts: 0
netd (0): Uid: 0 Sys: Us: Starts: 0
com.google.android.gms.persistent (Services Google): Uid: 10009 Sys: Us: Starts: 0
kworker/u:29 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:33 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:36 (0): Uid: 0 Sys: Us: Starts: 0
com.google.android.inputmethod.latin (com.google.android.inputmethod.latin.Clavier Google): Uid: 10057 Sys: Us: Starts: 0
kworker/u:15 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:11 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:16 (0): Uid: 0 Sys: Us: Starts: 0
mediaserver (1013): Uid: 1013 Sys: Us: Starts: 0
kworker/u:32 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:12 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:19 (0): Uid: 0 Sys: Us: Starts: 0
tmp-mksh (0): Uid: 0 Sys: Us: Starts: 0
kworker/0:1 (0): Uid: 0 Sys: Us: Starts: 0
com.google.android.gms.unstable (Services Google): Uid: 10009 Sys: Us: Starts: 1
kworker/u:3 (0): Uid: 0 Sys: Us: Starts: 0
sensors.qcom (0): Uid: 0 Sys: Us: Starts: 0
lmkd (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:0 (0): Uid: 0 Sys: Us: Starts: 0
kthreadd (0): Uid: 0 Sys: Us: Starts: 0
daemonsu:10113 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:31 (0): Uid: 0 Sys: Us: Starts: 0
RX_Thread (0): Uid: 0 Sys: Us: Starts: 0
TX_Thread (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:1 (0): Uid: 0 Sys: Us: Starts: 0
com.android.settings (Système Android): Uid: 1000 Sys: Us: Starts: 1
kworker/u:24 (0): Uid: 0 Sys: Us: Starts: 0
su (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10113 Sys: Us: Starts: 0
flush-179:0 (0): Uid: 0 Sys: Us: Starts: 0
bdi-default (0): Uid: 0 Sys: Us: Starts: 0
MC_Thread (0): Uid: 0 Sys: Us: Starts: 0
android.process.media (Médias): Uid: 10006 Sys: Us: Starts: 1
rild (0): Uid: 0 Sys: Us: Starts: 0
com.google.android.googlequicksearchbox:search (com.google.android.googlequicksearchbox.Application Google): Uid: 10026 Sys: Us: Starts: 0
com.android.phone (Téléphone): Uid: 1001 Sys: Us: Starts: 0
kworker/u:41 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:39 (0): Uid: 0 Sys: Us: Starts: 0
thermald (0): Uid: 0 Sys: Us: Starts: 0
ksoftirqd/0 (0): Uid: 0 Sys: Us: Starts: 0
android.process.acore (Applications de base Android): Uid: 10004 Sys: Us: Starts: 1
com.google.android.keep (com.google.android.keep.Keep): Uid: 10075 Sys: Us: Starts: 2
servicemanager (Système Android): Uid: 1000 Sys: Us: Starts: 0
com.google.android.talk (com.google.android.talk.Hangouts): Uid: 10015 Sys: Us: Starts: 1
jbd2/mmcblk0p21 (0): Uid: 0 Sys: Us: Starts: 0
kworker/1:1 (0): Uid: 0 Sys: Us: Starts: 0
com.android.vending (com.android.vending.Google Play Store): Uid: 10020 Sys: Us: Starts: 2
healthd (0): Uid: 0 Sys: Us: Starts: 0
com.android.nfc (com.android.nfc.Service NFC): Uid: 1027 Sys: Us: Starts: 0
jbd2/mmcblk0p22 (0): Uid: 0 Sys: Us: Starts: 0
ks (Système Android): Uid: 1000 Sys: Us: Starts: 0
com.google.android.apps.maps (com.google.android.apps.maps.Maps): Uid: 10060 Sys: Us: Starts: 1
file-storage (0): Uid: 0 Sys: Us: Starts: 0
com.android.providers.calendar (com.android.providers.calendar.Stockage de l'agenda): Uid: 10002 Sys: Us: Starts: 0
com.google.android.calendar (com.google.android.calendar.Agenda): Uid: 10034 Sys: Us: Starts: 2
vold (0): Uid: 0 Sys: Us: Starts: 0
daemonsu:master (0): Uid: 0 Sys: Us: Starts: 0
======================
Alarms (requires BATTERY_STATS permissions)
======================
com.google.android.gms (): Wakeups: 154 (15,7 / h)
Alarms: 0, Intent: ALARM_WAKEUP_ACTIVITY_DETECTION
Alarms: 1, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 127, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 19, Intent: com.google.android.gms/.checkin.EventLogService$Receiver
Alarms: 2, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 1, Intent: com.google.android.gms.reminders.REFRESH_NOTIFICATION
Alarms: 0, Intent: com.google.android.gms.fitness.aggregate
Alarms: 0, Intent: snet.service.intent.action.IDLE_MODE
Alarms: 0, Intent: com.google.android.gms/.common.download.DownloadAlarmReceiver
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE
Alarms: 1, Intent: com.google.android.gms/com.google.android.libraries.social.mediamonitor.MediaMonitorIntentService
Alarms: 1, Intent: com.google.android.gms/.checkin.CheckinService$Receiver
Alarms: 0, Intent: com.google.android.gms.fitness.trim
Alarms: 1, Intent: snet.service.intent.action.NORMAL_MODE
Alarms: 0, Intent: com.google.android.gms.common.receiver.LOG_CORE_ANALYTICS
android (): Wakeups: 82 (8,4 / h)
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: android.content.jobscheduler.JOB_DELAY_EXPIRED
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 46, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 0, Intent: android.content.jobscheduler.JOB_DEADLINE_EXPIRED
Alarms: 23, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 0, Intent: com.android.server.task.controllers.BatteryController.ACTION_CHARGING_STABLE
Alarms: 10, Intent: android.app.backup.intent.RUN
Alarms: 2, Intent: com.android.server.task.controllers.IdleController.ACTION_TRIGGER_IDLE
Alarms: 1, Intent: android.appwidget.action.APPWIDGET_UPDATE
Alarms: 0, Intent: com.android.server.WifiManager.action.START_SCAN
Alarms: 0, Intent: NextAlarmTracker.trigger
com.fongo.dellvoice (): Wakeups: 58 (5,9 / h)
Alarms: 58, Intent: REG_KEEP_ALIVE
com.facebook.orca (): Wakeups: 56 (5,7 / h)
Alarms: 39, Intent: com.facebook.push.mqtt.keepalive.b.ACTION_INEXACT_ALARM.com.facebook.orca
Alarms: 12, Intent: com.facebook.analytics.service.a.ACTION_ALARM
Alarms: 5, Intent: com.facebook.common.executors.cr.ACTION_ALARM.com.facebook.orca
Alarms: 0, Intent: com.facebook.orca.database.ACTION_ALARM
com.facebook.katana (): Wakeups: 53 (5,4 / h)
Alarms: 39, Intent: com.facebook.push.mqtt.keepalive.KeepaliveManager.ACTION_INEXACT_ALARM.com.facebook.katana
Alarms: 12, Intent: com.facebook.analytics.service.AnalyticsEventUploader.ACTION_ALARM
Alarms: 2, Intent: com.facebook.common.executors.WakingExecutorService.ACTION_ALARM.com.facebook.katana
Alarms: 0, Intent: com.facebook.katana/com.facebook.videoads.scheduler.VideoAdsFetchService
Alarms: 0, Intent: com.facebook.orca.database.ACTION_ALARM
com.android.providers.calendar (): Wakeups: 5 (0,5 / h)
Alarms: 5, Intent: com.android.providers.calendar.intent.CalendarProvider2
com.quoord.tapatalkpro.activity (): Wakeups: 4 (0,4 / h)
Alarms: 4, Intent: com.quoord.tapatalkpro.activity/com.quoord.tapatalkpro.alarm.PingsOnAlarmReceiver
com.google.android.googlequicksearchbox (): Wakeups: 2 (0,2 / h)
Alarms: 2, Intent: com.google.android.googlequicksearchbox/com.google.android.velvet.VelvetBackgroundTasksImpl$Service
com.google.android.talk (): Wakeups: 2 (0,2 / h)
Alarms: 0, Intent: com.google.android.apps.hangouts.RENEW_ACCOUNT_REGISTRATION
Alarms: 2, Intent: com.google.android.apps.hangouts.CLEANUP_DB
com.google.android.apps.plus (): Wakeups: 1 (0,1 / h)
Alarms: 1, Intent: com.google.android.apps.moviemaker.analyzer.PING
Alarms: 0, Intent: com.google.android.apps.plus.checkandengagesync
com.google.android.keep (): Wakeups: 1 (0,1 / h)
Alarms: 1, Intent: com.google.android.keep.intent.action.REFRESH_NOTIFICATION
======================
Network (requires root)
======================
10074 (Wifi) (com.google.android.gm.Gmail): 299.0 KBytes 21,8%
10009 (Wifi) (Services Google): 274.0 KBytes 20,0%
10096 (Wifi) (com.facebook.katana.Facebook): 217.0 KBytes 15,8%
10090 (Wifi) (com.fongo.dellvoice.Fongo): 177.0 KBytes 12,9%
10045 (Wifi) (com.google.android.apps.docs.editors.sheets.Feuilles de calcul): 143.0 KBytes 10,5%
10112 (Wifi) (com.facebook.orca.Messenger): 125.0 KBytes 9,1%
0 (Wifi) (0): 55.0 KBytes 4,1%
10071 (Wifi) (com.google.android.apps.plus.Google+): 27.0 KBytes 2,0%
1000 (Wifi) (Système Android): 21.0 KBytes 1,6%
10020 (Wifi) (com.android.vending.Google Play Store): 12.0 KBytes 0,9%
10026 (Wifi) (com.google.android.googlequicksearchbox.Application Google): 10.0 KBytes 0,8%
10060 (Wifi) (com.google.android.apps.maps.Maps): 7.0 KBytes 0,5%
10006 (Wifi) (Médias): 52.0 Bytes 0,0%
==========
CPU States
==========
1,51 GHz (): 3 m 7 s 0,5%
1,46 GHz (): 4 s 0,0%
1,35 GHz (): 6 s 0,0%
1,24 GHz (): 5 s 0,0%
1,13 GHz (): 7 s 0,0%
1,03 GHz (): 1 m 24 s 0,2%
918 MHz (): 4 s 0,0%
810 MHz (): 10 s 0,0%
702 MHz (): 6 s 0,0%
594 MHz (): 10 s 0,0%
486 MHz (): 9 s 0,0%
384 MHz (): 3 m 58 s 0,7%
Deep Sleep (): 9 h 39 m 54 s 98,4%
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
com.android.bluetooth (com.android.bluetooth.hid.HidService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.android.systemui (com.android.systemui.keyguard.KeyguardService)
Active since: 42 s
Last activity: 42 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 39 s
Last activity: 39 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.geocode.GeocodeService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.google.process.gapps (com.google.android.gms.gcm.GcmService)
Active since: 40 s
Last activity: 3 h 50 m 19 s
Crash count:0
com.google.android.music:main (com.google.android.music.download.artwork.ArtDownloadService)
Active since: 4 h 20 m 3 s
Last activity: 1 h 44 m 9 s
Crash count:0
com.google.android.gms (com.google.android.gms.analytics.service.AnalyticsService)
Active since: 12 h 14 m 23 s
Last activity: 3 h 50 m 42 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.fused.service.FusedProviderService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.google.android.music:main (com.google.android.music.preferences.MusicPreferenceService$MusicPreferenceServiceBinder)
Active since: 4 h 20 m 3 s
Last activity: 1 h 42 m
Crash count:0
com.fongo.dellvoice (com.fongo.dellvoice.FongoPhoneService)
Active since: 1 m 2 s
Last activity: 2 h 54 m 51 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pbap.BluetoothPbapService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.fused.FusedLocationService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.a2dp.A2dpService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.google.android.googlequicksearchbox:search (com.google.android.search.core.service.SearchService)
Active since: 56 s
Last activity: 56 s
Crash count:0
com.google.process.gapps (com.google.android.gms.gcm.http.GoogleHttpService)
Active since: 40 s
Last activity: 3 h 51 m 6 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.geofencer.service.GeofenceProviderService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.google.android.talk (com.google.android.libraries.hangouts.video.CallService)
Active since: 10 h 50 m 10 s
Last activity: 3 h 44 m 23 s
Crash count:0
com.google.process.gapps (com.google.android.gms.icing.service.LightweightIndexService)
Active since: 19 h 32 m 28 s
Last activity: 3 h 52 m 30 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 36 s
Last activity: 36 s
Crash count:0
system (android.hardware.location.GeofenceHardwareService)
Active since: 40 s
Last activity: 40 s
Crash count:0
com.google.android.music:main (com.google.android.music.net.NetworkMonitor)
Active since: 4 h 20 m 2 s
Last activity: 1 h 44 m 9 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.internal.PendingIntentCallbackService)
Active since: 1 m 12 s
Last activity: 1 m 29 s
Crash count:0
com.google.process.gapps (com.google.android.gms.auth.GetToken)
Active since: 19 h 32 m 27 s
Last activity: 3 h 52 m 29 s
Crash count:0
system (com.android.server.telecom.BluetoothPhoneService)
Active since: 40 s
Last activity: 41 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.internal.server.GoogleLocationService)
Active since: 41 s
Last activity: 3 h 51 m 16 s
Crash count:0
com.google.android.talk (com.google.android.libraries.hangouts.video.VideoChatService)
Active since: 45 s
Last activity: 45 s
Crash count:0
com.facebook.katana (com.facebook.fbservice.service.DefaultBlueService)
Active since: 10 h 45 m 48 s
Last activity: 3 h 50 m 47 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.network.NetworkLocationService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 55 s
Last activity: 3 h 48 m 52 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.internal.GoogleLocationManagerService)
Active since: 41 s
Last activity: 3 h 48 m 48 s
Crash count:0
com.google.android.inputmethod.latin (com.android.inputmethod.latin.LatinIME)
Active since: 40 s
Last activity: 3 h 48 m 37 s
Crash count:0
com.facebook.orca (com.facebook.fbservice.service.DefaultBlueService)
Active since: 3 h 56 m 19 s
Last activity: 3 h 51 m 14 s
Crash count:0
com.google.android.gms.persistent (com.google.android.gms.deviceconnection.service.DeviceConnectionServiceBroker)
Active since: 41 s
Last activity: 3 h 50 m 19 s
Crash count:0
com.google.android.googlequicksearchbox:interactor (com.google.android.voiceinteraction.GsaVoiceInteractionService)
Active since: 39 s
Last activity: 40 s
Crash count:0
system (com.android.internal.backup.LocalTransportService)
Active since: 36 s
Last activity: 36 s
Crash count:0
com.google.process.gapps (com.google.android.gms.playlog.service.PlayLogBrokerService)
Active since: 12 h 13 m 28 s
Last activity: 3 h 51 m 27 s
Crash count:0
com.google.android.gms.persistent (com.google.android.gms.common.stats.GmsCoreStatsService)
Active since: 40 s
Last activity: 3 h 50 m 19 s
Crash count:0
com.google.process.gapps (com.google.android.gms.clearcut.service.ClearcutLoggerService)
Active since: 4 h 7 m 44 s
Last activity: 3 h 51 m 6 s
Crash count:0
com.facebook.katana (com.facebook.push.mqtt.service.MqttPushService)
Active since: 53 s
Last activity: 2 h 45 m 34 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.map.BluetoothMapService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.facebook.orca (com.facebook.push.mqtt.service.MqttPushService)
Active since: 49 s
Last activity: 50 s
Crash count:0
com.android.phone (com.android.phone.TelephonyDebugService)
Active since: 41 s
Last activity: 41 s
Crash count:0
system (com.android.server.telecom.TelecomService)
Active since: 36 s
Last activity: 36 s
Crash count:0
com.google.android.gms (com.google.android.gms.icing.service.IndexService)
Active since: 19 h 32 m 28 s
Last activity: 3 h 52 m 32 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pan.PanService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.google.android.gms.persistent (com.google.android.gms.backup.BackupTransportService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 16 s
Crash count:0
==================
Reference overview
==================
ref_boot: Reference ref_boot created 1 m 2 s (Wl: 3 elements; KWl: 9elements; NetS: 7 elements; Alrm: 0 elements; Proc: 24 elements; Oth: 9 elements; CPU: 12 elements)
ref_custom: Reference ref_custom created 4 h 5 m 57 s (Wl: 11 elements; KWl: 22elements; NetS: 20 elements; Alrm: 13 elements; Proc: 107 elements; Oth: 9 elements; CPU: 13 elements)
ref_unplugged: Reference ref_unplugged created 9 h 42 m 56 s (Wl: 0 elements; KWl: 23elements; NetS: 23 elements; Alrm: 14 elements; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
ref_charged: Reference ref_charged created 9 h 42 m 58 s (Wl: 0 elements; KWl: 23elements; NetS: 23 elements; Alrm: 14 elements; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
ref_current: Reference ref_current created 19 h 32 m 27 s (Wl: 19 elements; KWl: 23elements; NetS: 24 elements; Alrm: 15 elements; Proc: 111 elements; Oth: 8 elements; CPU: 13 elements)
Displaying BetterBatteryStats-2015-04-23_071904024.txt.

Just installed Battery Calibration and will try to calibrate when the phone reaches 100%

Ok so after installing a new battery, flashing roms, clean install, rooting, betterbatterystats, battery calibration...
I still have the drain... I don't know why I didn't test this earlier, but I charged the phone last night and shut it down before going to sleep. It was at 90% when shutting down, and 17% when booting up this morning...
So now I'm charging at 100%, and I'll unplug the battery for a couple of hours to see if it's the battery itself that doesn't hold a charge...
I have looked for a physical short in the phone and haven't found one...
If it's not the battery I'll try to unplug modules one at a time and leaving the battery plugged in to see if unplugging something stops the drain.
If i can't find the source of the drain, I guess the brick wall is my last option...
If anyone has any ideas, I'm all ears.
Thanks

fullpampers said:
Ok so after installing a new battery, flashing roms, clean install, rooting, betterbatterystats, battery calibration...
I still have the drain... I don't know why I didn't test this earlier, but I charged the phone last night and shut it down before going to sleep. It was at 90% when shutting down, and 17% when booting up this morning...
So now I'm charging at 100%, and I'll unplug the battery for a couple of hours to see if it's the battery itself that doesn't hold a charge...
I have looked for a physical short in the phone and haven't found one...
If it's not the battery I'll try to unplug modules one at a time and leaving the battery plugged in to see if unplugging something stops the drain.
If i can't find the source of the drain, I guess the brick wall is my last option...
If anyone has any ideas, I'm all ears.
Thanks
Click to expand...
Click to collapse
You may have some apps running the background causing the drain. You might check out Greenify App from the App store. It will manage any apps running in the background and it is very simple to use.
I hope that helps........ I seriously doubt that your battery is bad. What version of Lollipop are you on?

Running 4.4.4 right now, just to try a different version of android. was running 5.1 before.
How can apps cause draining if the phone is completely powered down?

with a voltmeter you can check if it may is hardware related..but you have to find someone who knows about circuits and stuff..(I don't know)..

After 4.5 hours with the battery unplugged, the battery retained it's charge.... I'll look again for physical shorts...
This sucks, we're getting closer to the brick wall....

ZaNobey said:
with a voltmeter you can check if it may is hardware related..but you have to find someone who knows about circuits and stuff..(I don't know)..
Click to expand...
Click to collapse
Yeah I thought about using a voltmeter to try and find the short, but with out a schematic, I'd just be blindly probing stuff.
I'll try and isolate modules to see if i can find which one is drawing from the battery. but if it's not just swapping out parts. I guess I'm screwed...

Looking at your BBS logs, your phone is in deep sleep for 98% which is actually very good, minimal wakelocks. Only awake for 9 minutes of of 9 hours.
Looking at the battery lost levels is a bit more telling. You should not be loosing 7.5% an hour, especially with these stats, it should be more around 1%.
Download battery monitor widget and see what your battery drain is like over a 12 hour period. Post results

I'm 90% sure there is something physically (hardware) wrong with the phone.
Last night I charged the battery to 100%, unplugged all modules from the main logic board and left it in the case (so battery plugged into logic board, logic board still in front frame assembly, i left the power and volume buttons in). With the phone powered down.
When I woke I reassembled the phone, battery was at 30%.
Tonight I'll do the same thing but take the battery/logic board out of the frame assembly. If it still drains, then it's the logic board, if not i would suspect a short between the board and the frame of the phone or one of the power/volume buttons.
I really hope it's one of either because if it's something wrong with the logic board, I'm not going to buy a new one. I guess I could look into getting a phone with a broken glass from someone and swapping the logic board, but at the prices people are selling these phone, I might just change phone altogether.
Again, this effin' sucks....

Looks like it's the logic board (motherboard, whatever the kids call it)
The battery plugged into only the logic board (all other modules removed), outside the phone, still drew about 7-9% an hour. The part just above where the battery plugs in got slightly warmer, so maybe it's that part... As to if I can/want to find one and replace it is another story.
Looks like I'm going to have to buy a new phone...
Anyone have any idea if this can be fixed/where to get a cheap main board? Or I just trash the phone?