Develop Bugs

[BATTERY]AudioOut_3 Wakelock causes battery drain. Tip on how to get rid the wakelock

Hi guys.
Just thought i give you guys a heads up if you are having battery drainage. I know i have my other thread regarding battery tips but this is more of a heads up and what to do to stop this wakelock for now.
Right if you are rooted first thing i would suggest download BetterbatteryStats from here on xda. Thread is here. Once you have installed that on your phone make sure you fully charge your phone. Once that is done just use your phone as normal. Say once your battery has dropped down to say 60% check the partial wakelocks. I bet you guys any money that the first thing you will see is AudioOut_3 wakelock. Now if you have your phone on silent and only onto vibrate then you will not have it.
But for those of you that have lockscreen sounds on, touch screen sounds on and dialpad touch tones on then you will have massive wakelock. I had this same problem with my S2.
Only way to beat this. Settings - Sound - system and untick the first 3 options. Reboot and charge your phone and then check the difference. You will see that the wakelock is not as high as it use to be.
Hope this thread will become useful to few of you guys out there and if you guys know any other way that we can keep the sounds on and keep that wakelock at bare minimal please give your feedback here.

Better explanation for this wakelock can be found here in the bottom link
https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/AudioOut_1

Im still getting these wake locks even after following your advice. any ideas?

Thank you for your advice but I also still have the AudioOut_3 wake lock and I have had my phone tones turned off since I got my phone and generally have it on Vibrate. Could it be something else?
Sent from my HTC One X using xda premium

you two should read here more about it...it is basically the same thing that i suggested to do but users go into more indepth of how to advice to tackle it..so if you are using dsp manager that could be another reason or if you are listening to music ie using poweramp and not exiting the player properly that can also cause the wakelock.
Links:
http://droidtricks.blogspot.co.uk/2012/04/dealing-with-audioout1-partial-wakelock.html
http://forum.xda-developers.com/showthread.php?t=1629346
listentochaos said:
Im still getting these wake locks even after following your advice. any ideas?
Click to expand...
Click to collapse
bamboosensei said:
Thank you for your advice but I also still have the AudioOut_3 wake lock and I have had my phone tones turned off since I got my phone and generally have it on Vibrate. Could it be something else?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse

Hi All. i am trying to track down exactly whats hammering my battery as i am down to 8% now after 13hours only since last unplugged with only 1hour screen time
Below is screenshots of the standard power management in my htc one x:
2012-05-23_22-36-40 by jonneymendoza, on Flickr
2012-05-23_22-36-53 by jonneymendoza, on Flickr
2012-05-23_22-37-07 by jonneymendoza, on Flickr
And here is screenshots and dump file from BetterBatteryStas app:
2012-05-23_22-39-48 by jonneymendoza, on Flickr
2012-05-23_22-38-57 by jonneymendoza, on Flickr
2012-05-23_22-38-27 by jonneymendoza, on Flickr
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-05-23 23:14:38
Statistic Type: (3) Since Unplugged
Since 6 h 42 m 29 s
VERSION.RELEASE: 4.0.3
BRAND: htc_europe
DEVICE: endeavoru
MANUFACTURER: HTC
MODEL: HTC One X
BOOTLOADER: 0.95.0000
FINGERPRINT: htc_europe/endeavoru/endeavoru:4.0.3/IML74K/62864.11:user/release-keys
HARDWARE: endeavoru
ID: IML74K
TAGS: release-keys
USER: unknown
PRODUCT: endeavoru
RADIO: 1.1204.105.14
Rooted: false
===========
Other Usage
===========
Wifi On (): 6 h 42 m 28 s (24148 s) Ratio: 100.0%
Wifi Running (): 6 h 42 m 26 s (24146 s) Ratio: 100.0%
Deep Sleep (): 4 h 13 s (14413 s) Ratio: 58.9%
Poor Signal (): 3 h 27 m 15 s (12435 s) Ratio: 51.5%
Awake (): 2 h 42 m 16 s (9736 s) Ratio: 40.3%
No Data Connection (): 1 h 31 m 6 s (5466 s) Ratio: 22.6%
No or Unknown Signal (): 1 h 31 m 6 s (5466 s) Ratio: 22.6%
Good Signal (): 40 m 27 s (2427 s) Ratio: 10.0%
Screen On (): 24 m 54 s (1494 s) Ratio: 6.2%
Phone On (): 2 m 40 s (160 s) Ratio: 0.7%
=========
Wakelocks
=========
AudioOut_3 (1013): 20 m 39 s (1239 s) Count:27 5.1%
*sync*_gmail-ls_Account {name=jri*******************m, type=com.google} (com.google.android.gm.Gmail): 16 m 48 s (1008 s) Count:244 4.2%
Poweramp scan (UID): 15 m 9 s (909 s) Count:142 3.8%
WifiStateMachine (Android System): 9 m 16 s (556 s) Count:812 2.3%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 4 m 49 s (289 s) Count:316 1.2%
*sync*_gmail-ls_Account {name=jon**************m, type=com.google} (com.google.android.gm.Gmail): 4 m 24 s (264 s) Count:138 1.1%
AlarmManager (Android System): 3 m 28 s (208 s) Count:2051 0.9%
*sync*_com.google.android.apps.plus.content.EsGooglePhotoProvider_Account {name=jri*******************m, type=com.google} (com.google.android.apps.plus.Google+): 3 m 3 s (183 s) Count:67 0.8%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=jri*******************m, type=com.google} (com.google.android.apps.plus.Google+): 2 m 57 s (177 s) Count:74 0.7%
*sync*_com.google.android.apps.currents_Account {name=jri*******************m, type=com.google} (com.google.android.apps.currents.Currents): 2 m 24 s (144 s) Count:6 0.6%
SYNCHRONIZED (com.htc.android.mail.Mail): 2 m 8 s (128 s) Count:60 0.5%
com.joelapenna.foursquared.app.WakefulintentService.Static (com.quoord.tapatalkpro.activity.Tapatalk): 2 m 6 s (126 s) Count:14 0.5%
GSM (Dialer): 1 m 40 s (100 s) Count:20 0.4%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 m 24 s (84 s) Count:61 0.4%
com.maxmpz.audioplayer.player.PlayerService temp (UID): 1 m 19 s (79 s) Count:19 0.3%
*sync*_com.twitter.android.provider.TwitterProvider_Account {name=jon*********a, type=com.twitter.android.auth.login} (com.twitter.android.Twitter): 1 m 16 s (76 s) Count:7 0.3%
SyncLoopWakeLock (Android System): 1 m 8 s (68 s) Count:3522 0.3%
ActivityManager-Launch (Android System): 1 m 7 s (67 s) Count:320 0.3%
GTALK_CONN (Google Services): 52 s (52 s) Count:1577 0.2%
[email protected]/android_talkab02600e9e2f (Google Services): 52 s (52 s) Count:1591 0.2%
*sync*_com.android.calendar_Account {name=jon*******************m, type=com.htc.android.windowslive} (com.htc.android.mail.Mail): 46 s (46 s) Count:76 0.2%
RILJ (Dialer): 44 s (44 s) Count:730 0.2%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 39 s (39 s) Count:897 0.2%
*sync*_com.htc.sync.provider.weather_Account {name=Wea***r, type=com.htc.sync.provider.weather} (HTC Weather Service): 36 s (36 s) Count:40 0.2%
[email protected]/android_talka4064094afb8 (Google Services): 36 s (36 s) Count:14 0.2%
*sync*_com.android.contacts_Account {name=jon*******************m, type=com.htc.android.windowslive} (com.htc.android.mail.Mail): 36 s (36 s) Count:109 0.1%
*sync*_mail_Account {name=Jon*******************************m, type=com.htc.android.mail.eas} (com.htc.android.mail.Mail): 35 s (35 s) Count:100 0.1%
IdleScreen:command (com.htc.productivitylockscreen.Productivity): 34 s (34 s) Count:126 0.1%
*sync*_com.htc.socialnetwork.facebook_Account {name=jri************************m, type=com.facebook.auth.login} (UID): 32 s (32 s) Count:6 0.1%
*sync*_com.android.contacts_Account {name=Jon*******************************m, type=com.htc.android.mail.eas} (com.htc.android.mail.Mail): 31 s (31 s) Count:438 0.1%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 31 s (31 s) Count:139 0.1%
SyncManagerHandleSyncAlarm (Android System): 31 s (31 s) Count:3763 0.1%
FacebookService (com.facebook.katana.Facebook): 30 s (30 s) Count:4 0.1%
GpsLocationProvider (Android System): 29 s (29 s) Count:444 0.1%
Managewakelock: partial (com.handcent.nextsms.Handcent SMS): 29 s (29 s) Count:69 0.1%
*sync*_com.htc.htctwitter_Account {name=jon*********a, type=com.htc.htctwitter} (UID): 29 s (29 s) Count:38 0.1%
*sync*_mail_Account {name=jon*******************m, type=com.htc.android.windowslive} (com.htc.android.mail.Mail): 27 s (27 s) Count:409 0.1%
*sync*_com.android.contacts_Account {name=jri************************m, type=com.linkedin.android} (com.linkedin.android.LinkedIn): 27 s (27 s) Count:2 0.1%
DIRECTPUSH (com.htc.android.mail.Mail): 27 s (27 s) Count:348 0.1%
Checkin Service (Google Services): 26 s (26 s) Count:249 0.1%
START_SERVICE (com.htc.android.mail.Mail): 24 s (24 s) Count:258 0.1%
NetworkStats (Android System): 23 s (23 s) Count:230 0.1%
EmailServiceController_PWR_LOCK (com.htc.android.mail.Mail): 23 s (23 s) Count:117 0.1%
*vibrator* (com.handmark.tweetcaster.TweetCaster): 21 s (21 s) Count:38 0.1%
StartingAlertService (com.htc.task.Tasks): 20 s (20 s) Count:8 0.1%
NetworkLock (com.htc.android.mail.Mail): 20 s (20 s) Count:387 0.1%
fullsync (com.whatsapp.WhatsApp): 16 s (16 s) Count:1 0.1%
*sync*_com.htc.task.dm_Account {name=jon*******************m, type=com.htc.android.windowslive} (com.htc.android.mail.Mail): 16 s (16 s) Count:416 0.1%
ConnectivityService (Android System): 14 s (14 s) Count:2055 0.1%
StartingPopupUtilsService (com.handcent.nextsms.Handcent SMS): 13 s (13 s) Count:61 0.1%
*backup* (Android System): 12 s (12 s) Count:3896 0.1%
*sync*_com.android.calendar_Account {name=Jon*******************************m, type=com.htc.android.mail.eas} (com.htc.android.mail.Mail): 12 s (12 s) Count:402 0.1%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 12 s (12 s) Count:644 0.1%
NetworkLocationLocator (Google Services): 11 s (11 s) Count:266 0.0%
ScheduleServiceLock (com.htc.android.mail.Mail): 11 s (11 s) Count:429 0.0%
LocationReportingService (com.google.android.apps.maps.Maps): 10 s (10 s) Count:1420 0.0%
sleep_broadcast (Android System): 10 s (10 s) Count:485 0.0%
LocationReceiverService (com.google.android.apps.maps.Maps): 9 s (9 s) Count:1164 0.0%
Camera Monitor (com.google.android.apps.plus.Google+): 9 s (9 s) Count:66 0.0%
SMSDispatcher (Dialer): 7 s (7 s) Count:7 0.0%
SWITCH_NETWORK_MODE_WAKE_LOCK (com.htc.flexnet.FlexNet): 6 s (6 s) Count:203 0.0%
*sync*_com.linkedin.android_Account {name=jri************************m, type=com.linkedin.android} (com.linkedin.android.LinkedIn): 6 s (6 s) Count:1 0.0%
*sync*_com.android.contacts_Account {name=jon**************m, type=com.google} (Google Services): 6 s (6 s) Count:125 0.0%
LocationManagerService (Android System): 5 s (5 s) Count:3546 0.0%
*sync*_com.android.contacts_Account {name=jri*******************m, type=com.google} (Google Services): 5 s (5 s) Count:147 0.0%
GOOGLE_C2DM (Google Services): 5 s (5 s) Count:783 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 5 s (5 s) Count:639 0.0%
StartingAlertService (com.handcent.nextsms.Handcent SMS): 5 s (5 s) Count:66 0.0%
Event Log Service (Google Services): 5 s (5 s) Count:797 0.0%
IdleScreen:event (com.htc.productivitylockscreen.Productivity): 4 s (4 s) Count:177 0.0%
DownloadManager (Media): 4 s (4 s) Count:11 0.0%
*sync*_com.htc.socialnetwork.flickr.provider.StreamProvider_Account {name=jon*********a, type=com.htc.socialnetwork.flickr} (UID): 4 s (4 s) Count:36 0.0%
*sync*_com.htc.task.dm_Account {name=Jon*******************************m, type=com.htc.android.mail.eas} (com.htc.android.mail.Mail): 4 s (4 s) Count:269 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 4 s (4 s) Count:1415 0.0%
*vibrator* (Android System): 4 s (4 s) Count:3885 0.0%
StartingAlertService (org.dayup.gtask.GTasks): 4 s (4 s) Count:9 0.0%
DP-Abort (com.htc.android.mail.Mail): 3 s (3 s) Count:440 0.0%
SCREEN_FROZEN (Android System): 2 s (2 s) Count:722 0.0%
show keyguard (Android System): 2 s (2 s) Count:21 0.0%
*sync*_com.google.android.apps.currents_Account {name=jon**************m, type=com.google} (com.google.android.apps.currents.Currents): 2 s (2 s) Count:7 0.0%
ScheduleNextAlarmWakeLock (UID): 2 s (2 s) Count:34 0.0%
BatteryServiceUpdateStats (Android System): 2 s (2 s) Count:708 0.0%
*sync*_com.android.chrome_Account {name=jri*******************m, type=com.google} (com.android.chrome.Chrome Beta): 1 s (1 s) Count:38 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:3935 0.0%
StartingAlertService (com.android.mms.Messages): 1 s (1 s) Count:6 0.0%
NetworkLocationCallbackRunner (Google Services): 1 s (1 s) Count:590 0.0%
keyguardWakeAndHandOff (Android System): 1 s (1 s) Count:3915 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 1 s (1 s) Count:367 0.0%
StartingAlertService (UID): 1 s (1 s) Count:4 0.0%
SCHEDULE:1 (com.htc.android.mail.Mail): 1 s (1 s) Count:115 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 1 h 36 m 19 s (5779 s) Cnt(c/wc/ec)1917/0/0 23.6%
"baseband_xmm_power" (): 1 h 19 m 30 s (4770 s) Cnt(c/wc/ec)1488/78/0 19.5%
"deleted_wake_locks" (): 43 m 37 s (2617 s) Cnt(c/wc/ec)35445/0/1485 10.7%
"AudioOutLock" (): 23 m 5 s (1385 s) Cnt(c/wc/ec)11/0/0 5.7%
"alarm_rtc" (): 8 m 3 s (483 s) Cnt(c/wc/ec)742/100/198 2.0%
"alarm" () 2 m 53 s (173 s) Cntc/wc/ec)1512/254/1 0.7%
"mmc_delayed_work" () 1 m 50 s (110 s) Cnt(c/wc/ec)561/323/0 0.5%
"radio-interface" () 39 s (39 s) Cnt(c/wc/ec)169/0/0 0.2%
"st_wake_lock" () 35 s (35 s) Cnt(c/wc/ec)2/0/0 0.1%
"RXNET_DRV_MSL_WAKELOCK" () 25 s (25 s) Cnt(c/wc/ec)174/0/0 0.1%
"HS_GPIO" () 12 s (12 s) Cnt(c/wc/ec)6/0/6 0.1%
"HS_MGR" () 12 s (12 s) Cntc/wc/ec)6/0/6 0.1%
"htc_battery_tps80032" () 9 s (9 s) Cnt(c/wc/ec)328/0/0 0.0%
"KeyEvents" () 6 s (6 s) Cnt(c/wc/ec)10086/0/0 0.0%
"event2-275" () 2 s (2 s) Cnt(c/wc/ec)257/4/0 0.0%
"vbus_present" () 1 s (1 s) Cnt(c/wc/ec)1/0/1 0.0%
"usb_udc_lock" () 1 s (1 s) Cnt(c/wc/ec)1/0/1 0.0%
"event8-275" 1 s (1 s) Cntc/wc/ec)4/0/0 0.0%
"proximity" () 1 s (1 s) Cnt(c/wc/ec)442/0/1 0.0%
"ApmCommandThread" () (0 s) Cnt(c/wc/ec)172/0/0 0.0%
"RXNET_MSL_LISTENER_WAKELOCK" (): (0 s) Cnt(c/wc/ec)111/0/0 0.0%
"port_list" () (0 s) Cnt(c/wc/ec)19070/0/0 0.0%
"power-supply" () (0 s) Cnt(c/wc/ec)71/0/0 -0.0%
======================
Alarms (requires root)
======================
Click to expand...
Click to collapse
Thanks in advance

Plain and simple. You have music that drains your battery, gmail that sucks your battery as well or gtalk if you use that, turn the sounds in settings off and just leave the notification one if you want and ringtone, switch the rest off and for gmail just use autosync. regarding maps if you do not use them uninstall or freeze them, poweramp make sure you always come out of the app when you finish listening to music
jonneymendoza said:
Hi All. i am trying to track down exactly whats hammering my battery as i am down to 8% now after 13hours only since last unplugged with only 1hour screen time
Click to expand...
Click to collapse

Goku80 said:
Plain and simple. You have music that drains your battery, gmail that sucks your battery as well or gtalk if you use that, turn the sounds in settings off and just leave the notification one if you want and ringtone, switch the rest off and for gmail just use autosync. regarding maps if you do not use them uninstall or freeze them, poweramp make sure you always come out of the app when you finish listening to music
Click to expand...
Click to collapse
ringtones is on mute though and gmail is already on autosync(can only be autosync or manual).
i will check poweramp as well and make sure i exit it properly(doesnt android take care of that automatically?)
i cant use taskKiller to kill poweramp though?

jonneymendoza said:
ringtones is on mute though and gmail is already on autosync(can only be autosync or manual).
i will check poweramp as well and make sure i exit it properly(doesnt android take care of that automatically?)
i cant use taskKiller to kill poweramp though?
Click to expand...
Click to collapse
yeah u can. or just go to settings-apps find poweramp and force close it. and it should but if you are using a widget it still kinda detects in the background from my own experience. and check if you have touch keypad tones as off, lockscreen tones as off and same for dialpad tones as off

what can i do about gmail?
also, i only sue poweramp maybe a maximum of an hour or two

jonneymendoza said:
what can i do about gmail?[/QUOT
leave it on autosync that is how i have it..or go into settings and accounts and sync and put everything on manual sync. that will save you bit of juice..plus if you do not use maps freeze it or uninstall it.
Click to expand...
Click to collapse

Goku80 said:
jonneymendoza said:
what can i do about gmail?[/QUOT
leave it on autosync that is how i have it..or go into settings and accounts and sync and put everything on manual sync. that will save you bit of juice..plus if you do not use maps freeze it or uninstall it.
Click to expand...
Click to collapse
yea gmail is on autosync . and yea i dont use maps
Click to expand...
Click to collapse

jonneymendoza said:
yea gmail is on autosync . and yea i dont use maps
Click to expand...
Click to collapse
well uninstall it or freeze it cause it is still working in the background. anyways up to you what you want to do mate..you have the readings you can see what is draining your battery down to you to take what actions are needed now

jonneymendoza said:
Deep Sleep (): 4 h 13 s (14413 s) Ratio: 58.9%
Poor Signal (): 3 h 27 m 15 s (12435 s) Ratio: 51.5%
Awake (): 2 h 42 m 16 s (9736 s) Ratio: 40.3%
No Data Connection (): 1 h 31 m 6 s (5466 s) Ratio: 22.6%
No or Unknown Signal (): 1 h 31 m 6 s (5466 s) Ratio: 22.6%
Good Signal (): 40 m 27 s (2427 s) Ratio: 10.0%
Screen On (): 24 m 54 s (1494 s) Ratio: 6.2%
Phone On (): 2 m 40 s (160 s) Ratio: 0.7%
Click to expand...
Click to collapse
Well, there's your problem. You were in a dead zone for an hour and a half, and you spent 3.5 hours in areas with poor reception.
Another part of it is the audio_out wakelock, but I doubt it would be using up as much power as having your phone blast out the max possible output to try and claw back reception for an hour or two. My suggestion is just to turn on airplane mode when you know you won't have any reception, you will notice a drastic spike in your battery life.

Hunt3r.j2 said:
Well, there's your problem. You were in a dead zone for an hour and a half, and you spent 3.5 hours in areas with poor reception.
Another part of it is the audio_out wakelock, but I doubt it would be using up as much power as having your phone blast out the max possible output to try and claw back reception for an hour or two. My suggestion is just to turn on airplane mode when you know you won't have any reception, you will notice a drastic spike in your battery life.
Click to expand...
Click to collapse
rigtone volume is off though and when i listen not music i do some for only a couple of hours a day using hedfones.
About poor signal, that is hard to know without keeping an eye on your phone all the time. im at work most of the day and the signal is usualy great

jonneymendoza said:
rigtone volume is off though and when i listen not music i do some for only a couple of hours a day using hedfones.
About poor signal, that is hard to know without keeping an eye on your phone all the time. im at work most of the day and the signal is usualy great
Click to expand...
Click to collapse
You still have bad signal. Specially if you are using 3g and the phone is trying to.find signal that causes drain alone from what you can read
Sent from my HTC Wildfire S A510e using Tapatalk 2

After getting AudioOut_3 Wakelocks for a couple of days running, I'm starting to think that it can be caused by playing games, listening to music and watching videos. AudioOut_1 might be to do with the lock sounds but I have no problem with that. Just noticed that the more I played games and watched YouTube clips, the higher AudioOut_3 wakelock is. Maybe the app is still draining if not exited properly?
Sent from my HTC One X using xda premium

bamboosensei said:
After getting AudioOut_3 Wakelocks for a couple of days running, I'm starting to think that it can be caused by playing games, listening to music and watching videos. AudioOut_1 might be to do with the lock sounds but I have no problem with that. Just noticed that the more I played games and watched YouTube clips, the higher AudioOut_3 wakelock is. Maybe the app is still draining if not exited properly?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I have been saying that all along my friend but no one seems to be listening so i gave up. pay a closer look at widgets. Specially music widget. When you do not use it to play a song the screen is empty and there is no title on the music widget. once you start listening to music though and you finish say after half an hour, once you finish still on the music widget you see that the song is still there on pause. my opinion it still thinks you have it paused and still would keep the phone awake even if you put the screen off. so best think do not have a music widget on your homescreen. just giving you an example. same goes with a game. if you exit a game make sure you do that properly..or else you still know it is running in the background

This is all a big red herring. The 'drain' people are seeing from media and audio is so trivial that it is worth ignoring (20 seconds of partial wakelock here and 30 seconds there).
In all the screenshots and dumps posted, the answer to what is causing the lion's share of the drain is staring the user right in the face. If people have issues correctly interpreting BBS output, they should post in a thread where they can be given appropriate advice.

nobnut said:
This is all a big red herring. The 'drain' people are seeing from media and audio is so trivial that it is worth ignoring (20 seconds of partial wakelock here and 30 seconds there).
In all the screenshots and dumps posted, the answer to what is causing the lion's share of the drain is staring the user right in the face. If people have issues correctly interpreting BBS output, they should post in a thread where they can be given appropriate advice.
Click to expand...
Click to collapse
True mate and i am not denying what you are saying. I only wanted to let people know what could be a cause for battery drain to their phones as i encountered it and it does suck your battery and it did mine. I only wanted to let people know about it hence why this thread. For more advice and better explanation yes i do send them to BBS thread. But for you to basically turn around and say i am talking BS and can not help people if i was you i would try and rearrange your post mate. It is informing people and helping out each other. Hence why this thread. Did not come out and say i can help people or i know better. And for you to say it is only a 20 to 30 second wakelock then you are clearly mistaken as people have faced this wakelock and i am not the only one. So if you want to preach go ahead. But learn on how to put it properly instead of saying i do not know what i am talking about
The guy who posted the screen shot had like 20m wakelock..so were you are getting the 20 to 30 seconds i think you might need glasses to read second there are links in the first page were people can read about it more and how to counter it. Third it is not that hard to use google to search the wakelock and find solutions..this thread is merely to inform people about this wakelock and how much drain i had just by having sounds on

Weird battery issues - determined to find out what the problem is

Let me start off by saying, at the moment, my battery is fantastic. Right now im over 9 hours off the charger and im only down 20%. (from 95 to 75%) (first image attached) (betterbatterystats dump at bottom)
Yesterday the same thing - after almost 5 hours only down 13% and for the day i was 21 hours on battery and down 55%. (screens attached)
I have been using android since i got my captivate a few years ago. I have struggled with inexplicable battery problems ever since.
I know which apps are good and bad, and i really only use the most necessary apps, but regardless of what is installed or what isnt, my battery seems to just completely tank sometimes.
The weird thing is that i had these problems with my last phone - which was an ATT sgs2 - running AOKP. Before i swicthed to my Gnex a few weeks ago, it was giving my absolutely awful battery life. It wouldnt last 12 hours with minimal use. So when i switched to the Gnex, i thought my problems would be solved. But even with that, i had the same battery life - 12 hours with minimal use - mostly idle.
Now randomly the other day the battery just starts being awesome again. this is the kind of battery life i expect, and i know these phones are capable of when working properly. At the very least i know my phones shouldn't be draining 8% when idle - should be more like 1 or 2 percent - like it is now.
Im absolutely dumbfounded why this happens, and my only thing that i think might be it is ATT somehow. Maybe its an MMS thats trying to some in and just cant or something? I can only guess.
What im doing though is posting these screens now, and my bbs dump so you can see what my phone does when its behaving like it should. When it tanks again (and i know it will), ill post screens and another bbs dump. Please help me make sense of the dump, because i really have no idea what any of the information means.
My only request is to please try not to just assume its something - that i defintely know it is NOT. For example (oh your wifi is on - wifi is a killer, etc, when i can clearly see wifi is NOT the problem)
Im trying to find FACTS about why this is happening to me, so please help me get to the bottom of this. Thanks!
BBS dump:
===================
General Information
===================
BetterBatteryStats version: 1.9.0.0
Creation Date: 2012-07-31 00:46:28
Statistic Type: (3) Since Unplugged
Since 9 h 20 m 49 s
VERSION.RELEASE: 4.1.1
BRAND: google
DEVICE: maguro
MANUFACTURER: samsung
MODEL: Galaxy Nexus
OS.VERSION: 3.0.31-g6fb96c9
BOOTLOADER: PRIMELC03
HARDWARE: tuna
FINGERPRINT: google/takju/maguro:4.1.1/JRO03C/398337:user/release-keys
ID: JRO03C
TAGS: release-keys
USER: android-build
PRODUCT: takju
RADIO: I9250XXLF1
Rooted: false
============
Battery Info
============
Level lost [%]: 74
Voltage lost [mV]: 3896
===========
Other Usage
===========
Wifi On (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Wifi Running (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Bluetooth On (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Awake (): 2 h 20 s (7220 s) Ratio: 21.5%
No Data Connection (): 59 m 37 s (3577 s) Ratio: 10.6%
No or Unknown Signal (): 59 m 37 s (3577 s) Ratio: 10.6%
Screen On (): 36 m 8 s (2168 s) Ratio: 6.4%
Good Signal (): 4 m 36 s (276 s) Ratio: 0.8%
=========
Wakelocks
=========
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 15 m 41 s (941 s) Count:163 2.8%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 11 m 35 s (695 s) Count:1286 2.1%
AudioOut_2 (1013): 7 m 20 s (440 s) Count:127 1.3%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 4 m (240 s) Count:4589 0.7%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 2 m 44 s (164 s) Count:165 0.5%
Sidekick_TrafficIntentService_onHandleIntent (com.google.android.googlequicksearchbox.Google Search): 2 m 24 s (144 s) Count:97 0.4%
[email protected]/android_talk5eb0a0d6167e (Google Services): 2 m 6 s (126 s) Count:215 0.4%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 4 s (124 s) Count:44 0.4%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 1 m 44 s (104 s) Count:153 0.3%
NLP PendingIntent client in com.google.android.googlequicksearchbox (com.google.android.apps.maps.Maps): 1 m 25 s (85 s) Count:725 0.3%
NetworkLocationSensorUploader (com.google.android.apps.maps.Maps): 1 m 14 s (74 s) Count:5 0.2%
AlarmManager (Android System): 1 m 2 s (62 s) Count:1569 0.2%
NetworkLocationLocator (Google Services): 60 s (60 s) Count:205 0.2%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 58 s (58 s) Count:2081 0.2%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 44 s (44 s) Count:33 0.1%
DownloadManager (Media): 44 s (44 s) Count:3 0.1%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 37 s (37 s) Count:2820 0.1%
SMSDispatcher (Phone): 36 s (36 s) Count:19 0.1%
LocationReportingService (com.google.android.apps.maps.Maps): 31 s (31 s) Count:6129 0.1%
RILJ (Phone): 31 s (31 s) Count:2756 0.1%
ActivityManager-Launch (Android System): 27 s (27 s) Count:499 0.1%
*backup* (Android System): 26 s (26 s) Count:831 0.1%
LocationPrivacyService (com.google.android.apps.maps.Maps): 25 s (25 s) Count:13 0.1%
*sync*_com.google.android.apps.currents_Account {[email protected], type=com.google} (com.google.android.apps.currents.Currents): 25 s (25 s) Count:7 0.1%
NfcService (com.android.nfc.Nfc Service): 22 s (22 s) Count:47 0.1%
LocationManagerService (Android System): 18 s (18 s) Count:416 0.1%
MMS Connectivity (com.android.mms.Messaging): 15 s (15 s) Count:8 0.0%
sleep_broadcast (Android System): 15 s (15 s) Count:759 0.0%
AlarmManager (com.levelup.beautifulwidgets.Beautiful Widgets): 12 s (12 s) Count:571 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 10 s (10 s) Count:10 0.0%
DropboxCpuOnlyWakeLock (com.dropbox.android.Dropbox): 10 s (10 s) Count:3 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 9 s (9 s) Count:15 0.0%
LocationReceiverService (com.google.android.apps.maps.Maps): 9 s (9 s) Count:3611 0.0%
GpsLocationProvider (Android System): 9 s (9 s) Count:625 0.0%
ActivityManager-Sleep (Android System): 8 s (8 s) Count:1610 0.0%
StartingAlertService (com.android.mms.Messaging): 7 s (7 s) Count:54 0.0%
AlarmManager (com.google.android.apps.maps.Maps): 7 s (7 s) Count:6119 0.0%
MMS PushReceiver (com.android.mms.Messaging): 6 s (6 s) Count:4 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 6 s (6 s) Count:2071 0.0%
show keyguard (Android System): 6 s (6 s) Count:39 0.0%
*sync*_com.google.android.music.MusicContent_Account {[email protected], type=com.google} (com.google.android.music.Google Play Music): 4 s (4 s) Count:2 0.0%
s (com.google.android.apps.maps.Maps): 4 s (4 s) Count:2143 0.0%
AudioOut_3 (1013): 3 s (3 s) Count:10 0.0%
ConnectivityService (Android System): 3 s (3 s) Count:1571 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 3 s (3 s) Count:5156 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:607 0.0%
SCREEN_FROZEN (Android System): 2 s (2 s) Count:813 0.0%
NetworkStats (Android System): 2 s (2 s) Count:101 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:362 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:801 0.0%
*sync*_com.google.android.apps.magazines_Account {[email protected], type=com.google} (com.google.android.apps.magazines.Google Play Magazines): 1 s (1 s) Count:3 0.0%
AudioIn_3B9 (1013): 1 s (1 s) Count:3 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1793 0.0%
*sync*_com.android.browser_Account {[email protected], type=com.google} (Google Services): 1 s (1 s) Count:45 0.0%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 1 s (1 s) Count:135 0.0%
AudioIn_3BB (1013): 1 s (1 s) Count:7 0.0%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cntc/wc/ec)1/1/1 100.0%
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
======================
Network (requires root)
======================
==========
CPU States
==========
1 kHz (): ---%

lourivellini said:
Please help me make sense of the dump, because i really have no idea what any of the information means.
BBS dump:
===================
General Information
===================
BetterBatteryStats version: 1.9.0.0
Creation Date: 2012-07-31 00:46:28
Statistic Type: (3) Since Unplugged
Since 9 h 20 m 49 s
VERSION.RELEASE: 4.1.1
BRAND: google
DEVICE: maguro
MANUFACTURER: samsung
MODEL: Galaxy Nexus
OS.VERSION: 3.0.31-g6fb96c9
BOOTLOADER: PRIMELC03
HARDWARE: tuna
FINGERPRINT: google/takju/maguro:4.1.1/JRO03C/398337:user/release-keys
ID: JRO03C
TAGS: release-keys
USER: android-build
PRODUCT: takju
RADIO: I9250XXLF1
Rooted: false
============
Battery Info
============
Level lost [%]: 74
Voltage lost [mV]: 3896
Click to expand...
Click to collapse
General information. Not really a whole lot more to say, unless you wanted to know what some of the specific lines mean.
lourivellini said:
===========
Other Usage
===========
Wifi On (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Wifi Running (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Bluetooth On (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Awake (): 2 h 20 s (7220 s) Ratio: 21.5%
No Data Connection (): 59 m 37 s (3577 s) Ratio: 10.6%
No or Unknown Signal (): 59 m 37 s (3577 s) Ratio: 10.6%
Screen On (): 36 m 8 s (2168 s) Ratio: 6.4%
Good Signal (): 4 m 36 s (276 s) Ratio: 0.8%
Click to expand...
Click to collapse
Also fairly self-explanatory. Wifi and Bluetooth were on for the entire 9h 20m duration. The phone was "awake" (active in some capacity) for 2 hours, and the screen was on for 36 minutes. You did, however, spend almost an hour without signal, which can hurt battery.
lourivellini said:
=========
Wakelocks
=========
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 15 m 41 s (941 s) Count:163 2.8%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 11 m 35 s (695 s) Count:1286 2.1%
AudioOut_2 (1013): 7 m 20 s (440 s) Count:127 1.3%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 4 m (240 s) Count:4589 0.7%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 2 m 44 s (164 s) Count:165 0.5%
Sidekick_TrafficIntentService_onHandleIntent (com.google.android.googlequicksearchbox.Google Search): 2 m 24 s (144 s) Count:97 0.4%
GTALK_ASYNC_CONN_<<REDACTED>>/android_talk5eb0a0d6167e (Google Services): 2 m 6 s (126 s) Count:215 0.4%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 4 s (124 s) Count:44 0.4%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 1 m 44 s (104 s) Count:153 0.3%
NLP PendingIntent client in com.google.android.googlequicksearchbox (com.google.android.apps.maps.Maps): 1 m 25 s (85 s) Count:725 0.3%
NetworkLocationSensorUploader (com.google.android.apps.maps.Maps): 1 m 14 s (74 s) Count:5 0.2%
AlarmManager (Android System): 1 m 2 s (62 s) Count:1569 0.2%
NetworkLocationLocator (Google Services): 60 s (60 s) Count:205 0.2%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 58 s (58 s) Count:2081 0.2%
*sync*_gmail-ls_Account {name=<<REDACTED>>, type=com.google} (com.google.android.gm.Gmail): 44 s (44 s) Count:33 0.1%
DownloadManager (Media): 44 s (44 s) Count:3 0.1%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 37 s (37 s) Count:2820 0.1%
SMSDispatcher (Phone): 36 s (36 s) Count:19 0.1%
LocationReportingService (com.google.android.apps.maps.Maps): 31 s (31 s) Count:6129 0.1%
RILJ (Phone): 31 s (31 s) Count:2756 0.1%
ActivityManager-Launch (Android System): 27 s (27 s) Count:499 0.1%
*backup* (Android System): 26 s (26 s) Count:831 0.1%
LocationPrivacyService (com.google.android.apps.maps.Maps): 25 s (25 s) Count:13 0.1%
*sync*_com.google.android.apps.currents_Account {name=<<REDACTED>>, type=com.google} (com.google.android.apps.currents.Currents): 25 s (25 s) Count:7 0.1%
NfcService (com.android.nfc.Nfc Service): 22 s (22 s) Count:47 0.1%
LocationManagerService (Android System): 18 s (18 s) Count:416 0.1%
MMS Connectivity (com.android.mms.Messaging): 15 s (15 s) Count:8 0.0%
sleep_broadcast (Android System): 15 s (15 s) Count:759 0.0%
AlarmManager (com.levelup.beautifulwidgets.Beautiful Widgets): 12 s (12 s) Count:571 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 10 s (10 s) Count:10 0.0%
DropboxCpuOnlyWakeLock (com.dropbox.android.Dropbox): 10 s (10 s) Count:3 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 9 s (9 s) Count:15 0.0%
LocationReceiverService (com.google.android.apps.maps.Maps): 9 s (9 s) Count:3611 0.0%
GpsLocationProvider (Android System): 9 s (9 s) Count:625 0.0%
ActivityManager-Sleep (Android System): 8 s (8 s) Count:1610 0.0%
StartingAlertService (com.android.mms.Messaging): 7 s (7 s) Count:54 0.0%
AlarmManager (com.google.android.apps.maps.Maps): 7 s (7 s) Count:6119 0.0%
MMS PushReceiver (com.android.mms.Messaging): 6 s (6 s) Count:4 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 6 s (6 s) Count:2071 0.0%
show keyguard (Android System): 6 s (6 s) Count:39 0.0%
*sync*_com.google.android.music.MusicContent_Account {name=<<REDACTED>>, type=com.google} (com.google.android.music.Google Play Music): 4 s (4 s) Count:2 0.0%
s (com.google.android.apps.maps.Maps): 4 s (4 s) Count:2143 0.0%
AudioOut_3 (1013): 3 s (3 s) Count:10 0.0%
ConnectivityService (Android System): 3 s (3 s) Count:1571 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 3 s (3 s) Count:5156 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:607 0.0%
SCREEN_FROZEN (Android System): 2 s (2 s) Count:813 0.0%
NetworkStats (Android System): 2 s (2 s) Count:101 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:362 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:801 0.0%
*sync*_com.google.android.apps.magazines_Account {name=<<REDACTED>>, type=com.google} (com.google.android.apps.magazines.Google Play Magazines): 1 s (1 s) Count:3 0.0%
AudioIn_3B9 (1013): 1 s (1 s) Count:3 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1793 0.0%
*sync*_com.android.browser_Account {name=<<REDACTED>>, type=com.google} (Google Services): 1 s (1 s) Count:45 0.0%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 1 s (1 s) Count:135 0.0%
AudioIn_3BB (1013): 1 s (1 s) Count:7 0.0%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cntc/wc/ec)1/1/1 100.0%
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
======================
Network (requires root)
======================
==========
CPU States
==========
1 kHz (): ---%
Click to expand...
Click to collapse
Wakelocks are things that keep your phone awake. Partial wakelocks are typically held by applications, such as receiving an email or your twitter client checking for updates. A kernel wakelock is done at the kernel level, so it's typically something more low-level, which could be things like the charging system (phone's plugged into a power source) or the phone's radio waking it. Alarms are another category of items that wake your phone.
For wakelocks and alarms, the big thing you're looking for is the amount of time that they kept your phone awake. In this case, your top wakelock is "SignalCollector.ScannerThread", which woke the phone for 15 minutes and 41 seconds (2.8% of total uptime). We can also see that it woke the phone 163 times. From some quick googling, it appears that this is part of Google Maps. In any case, though, 15 minutes over 9 hours and 20 minutes isn't a lot.
Once you've had the battery problem again and can give another bbs report, then we'd be able to see what is consistantly waking your phone, causing the battery to drain. All we have right now is a report that shows a phone working how it should.
If you wanted any more specifics about any part of the report, I can try to answer whatever questions you have, and I'm sure there's someone much more knowledgeable about the topic than I am anyway who might pop in.
Edit: I removed your email address from multiple different places within my quotes. If you'd like to hide your email, you may wish to do the same in your post. In any case, it's not my place to duplicate that information.

My phone has "No or Unknown Signal" for 8h today, pretty sure that's because I've been on WIFI for about 8hours
(I also have 6 hours 15 minutes of awake time in 10 hours on time, and trying to figure that out is why I'm looking at battery threads )

question before i do anything: I dont mind running stock, but i would like to start using AOKP again, as i liked the extra features. What i dont want is my battery to go nuts, and then have people stupidly say "oh thats what you get from running a custom rom"
I had the problem with this STOCK rom already, so if i flash, and end up having the problem in the future, i really doubt the rom has anything to do with it.

How do you get display on for that long...... ahhh. This is what I get.
{
"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"
}

exzacklyright said:
How do you get display on for that long...... ahhh. This is what I get.
Click to expand...
Click to collapse
i dont think my screen was on for that long. My phone was mostly idle in those screenshots, i think bbs said i had it on for like 36 minutes or something.
What i do know is that when these phones are working properly the battery is awesome. Or at least the 2 previous phones i had before this (captivate with 1800mh battery, and sgs2 with stock battery) Something happens that causes it to tank for me - and its not any app i install.

Battery problem. Please help

Hey guys,
I just got the international version of note 2, like 2 weeks back. Its my first android device, and i was quite happy with the battery life switching from an old blackberry. But after downloading loads of apps & removing most of them which i had no use for, i noticed my battery draining out pretty fast compared to what i was getting a week back.
I installed betterbatterystats and found out that my pphone is not going into deep sleep anymore. Pretty sure there's some rouge app that's causing it but i can't figure it out. Here's my logfile. I'm on 4.1.2 unrooted.
===================
General Information
===================
BetterBatteryStats version: 1.10.0.0b4
Creation Date: 2013-02-20 14:07:31
Statistic Type: (3) Since Unplugged
Since 5 h 53 m 47 s
VERSION.RELEASE: 4.1.2
BRAND: samsung
DEVICE: t03g
MANUFACTURER: samsung
MODEL: GT-N7100
OS.VERSION: 3.0.31-679347
BOOTLOADER: N7100XXDMB2
HARDWARE: smdk4x12
FINGERPRINT: samsung/t03gxx/t03g:4.1.2/JZO54K/N7100XXDMB2:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: se.infra
PRODUCT: t03gxx
RADIO: N7100DDDLK6
Rooted: false
============
Battery Info
============
Level lost [%]: 27
Voltage lost [mV]: 324
===========
Other Usage
===========
Wifi On (): 5 h 53 m 43 s (21223 s) Ratio: 100.0%
Wifi Running (): 5 h 53 m 43 s (21223 s) Ratio: 100.0%
No Data Connection (): 5 h 53 m 43 s (21223 s) Ratio: 100.0%
No or Unknown Signal (): 5 h 53 m 43 s (21223 s) Ratio: 100.0%
Awake (): 3 h 24 m 26 s (12266 s) Ratio: 57.8%
Screen On (): 58 m 31 s (3511 s) Ratio: 16.5%
Phone On (): 11 m 54 s (714 s) Ratio: 3.4%
Bluetooth On (): 11 m 20 s (680 s) Ratio: 3.2%
=========
Wakelocks
=========
NetworkLocationLocator (com.google.android.apps.maps.Maps): 13 m 26 s (806 s) Count:795 3.8%
*sync*_com.android.contacts_Account {name=xksb, type=fm.last.android.account} (fm.last.android.Last.fm): 7 m 38 s (458 s) Count:10 2.2%
BtOppObexServer (com.android.bluetooth.Bluetooth share): 5 m 15 s (315 s) Count:2 1.5%
AudioOut_2 (1013): 3 m 35 s (215 s) Count:81 1.0%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 3 m 4 s (184 s) Count:112 0.9%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 3 m 2 s (182 s) Count:2797 0.9%
MAIL_SERVICE (com.android.exchange.Exchange services): 1 m 49 s (109 s) Count:107 0.5%
ActivityManager-Launch (Android System): 1 m 39 s (99 s) Count:359 0.5%
AlarmManager (de.android.telnet.Network Signal Info): 1 m 32 s (92 s) Count:6876 0.4%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 1 m 13 s (73 s) Count:1528 0.3%
NetworkLocationLocator (Google Services): 1 m 11 s (71 s) Count:36 0.3%
*sync*_com.android.contacts_Account {name=EM, type=com.osp.app.signin} (UID): 1 m 9 s (69 s) Count:17 0.3%
GSM (Phone): 59 s (59 s) Count:12 0.3%
AlarmManager (Android System): 55 s (55 s) Count:1161 0.3%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 51 s (51 s) Count:12 0.2%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 49 s (49 s) Count:1275 0.2%
*sync*_com.twitter.android.provider.TwitterProvider_Account {name=SchecterWhore, type=com.twitter.android.auth.login} (com.twitter.android.Twitter): 44 s (44 s) Count:9 0.2%
LocationReceiverService (com.google.android.apps.maps.Maps): 36 s (36 s) Count:1893 0.2%
sendinactive (com.whatsapp.WhatsApp): 35 s (35 s) Count:12 0.2%
MediaScannerService (Media): 24 s (24 s) Count:1 0.1%
sleep_broadcast (Android System): 19 s (19 s) Count:592 0.1%
*sync*_com.soundcloud.android.provider.ScContentProvider_Account {name=kunalbatra, type=com.soundcloud.android.account} (com.soundcloud.android.SoundCloud): 18 s (18 s) Count:5 0.1%
LocationReportingService (com.google.android.apps.maps.Maps): 16 s (16 s) Count:3273 0.1%
PhoneWindowManager.mBroadcastWakeLock (Android System): 16 s (16 s) Count:399 0.1%
RILS (com.sec.phone.SecPhone): 15 s (15 s) Count:4 0.1%
FacebookService (com.facebook.katana.Facebook): 14 s (14 s) Count:4 0.1%
NetworkInitiatedService (com.google.android.apps.maps.Maps): 12 s (12 s) Count:434 0.1%
com.maxmpz.audioplayer.player.PlayerService temp (UID): 12 s (12 s) Count:3 0.1%
Poweramp scan (UID): 11 s (11 s) Count:9 0.1%
AlarmManager (com.google.android.apps.maps.Maps): 10 s (10 s) Count:3267 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 9 s (9 s) Count:1259 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 8 s (8 s) Count:2258 0.0%
fullsync (com.whatsapp.WhatsApp): 8 s (8 s) Count:40 0.0%
LocationPrivacyService (com.google.android.apps.maps.Maps): 7 s (7 s) Count:2 0.0%
VibratorService (Phone): 6 s (6 s) Count:4 0.0%
show keyguard (Android System): 6 s (6 s) Count:26 0.0%
ConnectivityService (Android System): 5 s (5 s) Count:1163 0.0%
SyncLoopWakeLock (Android System): 5 s (5 s) Count:1441 0.0%
RILJ (Phone): 5 s (5 s) Count:201 0.0%
*sync*_gmail-ls_Account {name=EM, type=com.google} (com.google.android.gm.Gmail): 5 s (5 s) Count:2 0.0%
Browser (com.android.browser.Internet): 4 s (4 s) Count:2 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 4 s (4 s) Count:215 0.0%
NetworkLocationCacheUpdater (com.google.android.apps.maps.Maps): 4 s (4 s) Count:113 0.0%
NLP PendingIntent client in com.google.android.googlequicksearchbox (com.google.android.apps.maps.Maps): 4 s (4 s) Count:433 0.0%
*sync*_com.infraware.provider.SNoteProvider_Account {name=EM, type=com.osp.app.signin} (UID): 4 s (4 s) Count:1 0.0%
*sync*_com.android.contacts_Account {name=EM, type=com.google} (Google Services): 4 s (4 s) Count:107 0.0%
VibratorService (com.whatsapp.WhatsApp): 3 s (3 s) Count:16 0.0%
AudioIn_793 (1013): 3 s (3 s) Count:10 0.0%
AudioIn_79A (1013): 3 s (3 s) Count:4 0.0%
C2DMService (com.twitter.android.Twitter): 3 s (3 s) Count:17 0.0%
AlarmManager (com.viber.voip.Viber): 2 s (2 s) Count:36 0.0%
NetworkStats (Android System): 2 s (2 s) Count:62 0.0%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 2 s (2 s) Count:94 0.0%
AudioIn_795 (1013): 2 s (2 s) Count:84 0.0%
AlarmManager (Google Services): 2 s (2 s) Count:276 0.0%
AlarmManager (com.android.exchange.Exchange services): 2 s (2 s) Count:140 0.0%
*backup* (Android System): 2 s (2 s) Count:625 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:200 0.0%
*sync*_com.android.calendar_Account {name=EM, type=com.osp.app.signin} (UID): 1 s (1 s) Count:2 0.0%
*sync*_com.android.contacts_Account {name=919899846944, type=com.sec.chaton} (com.sec.chaton.ChatON): 1 s (1 s) Count:1 0.0%
reset keyguard (Android System): 1 s (1 s) Count:601 0.0%
SyncManagerHandleSyncAlarm (Android System): 1 s (1 s) Count:446 0.0%
AlarmManager (com.sec.spp.push.Samsung Push Service): 1 s (1 s) Count:87 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 s (1 s) Count:4 0.0%
*sync*_com.android.contacts_Account {name=EM, type=com.android.exchange} (com.android.exchange.Exchange services): 1 s (1 s) Count:154 0.0%
BluetoothIncomingFileConfirmActivity (com.android.bluetooth.Bluetooth share): 1 s (1 s) Count:1 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:62 0.0%
*sync*_com.android.calendar_Account {name=xksb, type=fm.last.android.account} (fm.last.android.Last.fm): 1 s (1 s) Count:1 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:603 0.0%
AlarmManager (com.codingcaveman.SoloTrial.Solo Lite): 1 s (1 s) Count:21 0.0%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 1 s (1 s) Count:2687 0.0%
*sync*_com.android.browser_Account {name=EM, type=com.osp.app.signin} (UID): 1 s (1 s) Count:18 0.0%
GOOGLE_C2DM (Google Services): 1 s (1 s) Count:50 0.0%
================
Kernel Wakelocks
================
"wlan_rx_wake" (): 55 m 56 s (3356 s) Cntc/wc/ec)3121/0/3122 15.3%
"battery-monitor" (): 47 m 17 s (2837 s) Cntc/wc/ec)2887/0/2887 12.9%
"PowerManagerService" (): 43 m 6 s (2586 s) Cntc/wc/ec)8120/0/0 11.8%
"wlan_ctrl_wake" (): 41 m 43 s (2503 s) Cntc/wc/ec)2111/0/2111 11.4%
"l2_hsic" (): 31 m 28 s (1888 s) Cntc/wc/ec)4015/370/4015 8.6%
"alarm_rtc" (): 10 m 47 s (647 s) Cntc/wc/ec)881/0/196 2.9%
"wlan_wake" (): 8 m 12 s (492 s) Cntc/wc/ec)246592/1932/0 2.2%
"umts_ipc0" (): 5 m 12 s (312 s) Cntc/wc/ec)1041/0/1041 1.4%
"BT_bt_wake" (): 4 m 46 s (286 s) Cntc/wc/ec)11/0/11 0.2%
"BT_bt_wake" (): 4 m 41 s (281 s) Cntc/wc/ec)21/0/21 0.2%
"alarm" (): 4 m 38 s (278 s) Cntc/wc/ec)9774/4/0 1.3%
"AudioOutLock" (): 1 m 24 s (84 s) Cntc/wc/ec)89/0/0 0.4%
"battery-update" (): 60 s (60 s) Cntc/wc/ec)27/0/27 0.3%
"rpm_hsic" (): 36 s (36 s) Cntc/wc/ec)763/0/0 0.2%
"sensorhub_wake_lock" (): 27 s (27 s) Cntc/wc/ec)33/0/33 0.1%
"radio-interface" (): 15 s (15 s) Cntc/wc/ec)87/0/0 0.1%
"ssp_wake_lock" (): 13 s (13 s) Cntc/wc/ec)11/1/11 0.1%
"suspend_backoff" (): 9 s (9 s) Cntc/wc/ec)1/0/1 0.0%
"umts_rfs0" (): 8 s (8 s) Cntc/wc/ec)6/0/6 0.0%
"vib_present" (): 4 s (4 s) Cntc/wc/ec)39/0/0 0.0%
"sync_system" (): 2 s (2 s) Cntc/wc/ec)46/0/0 0.0%
"KeyEvents" (): 1 s (1 s) Cntc/wc/ec)40337/0/0 0.0%
"efsd-interface" (): (0 s) Cntc/wc/ec)12/0/0 0.0%
"secril_rfs-interface" (): (0 s) Cntc/wc/ec)6/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)2887/264/0 0.0%
"mmc1_detect" (): (0 s) Cntc/wc/ec)3492/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)1609/0/0 0.0%
"client-interface" (): (0 s) Cntc/wc/ec)384/0/0 0.0%
"tx_hsic" (): (0 s) Cntc/wc/ec)574/0/0 0.0%
"ApmCommand" (): (0 s) Cntc/wc/ec)892/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)3492/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.6 GHz (): 0.0%
1.5 GHz (): 0.0%
1.4 GHz (): 0.0%
1.3 GHz (): 0.0%
1.2 GHz (): 0.0%
1.1 GHz (): 15 m 37 s 4.3%
1 GHz (): 29 m 43 s 8.1%
900 MHz (): 60 s 0.3%
800 MHz (): 44 m 12.0%
700 MHz (): 1 m 27 s 0.4%
600 MHz (): 6 m 39 s 1.8%
500 MHz (): 5 m 54 s 1.6%
400 MHz (): 25 m 48 s 7.1%
300 MHz (): 0.0%
200 MHz (): 1 h 24 m 32 s 23.1%
Deep Sleep (): 2 h 30 m 56 s 41.3%
==================
Reference overview
==================
Custom: Reference custom_ref created 2013-02-18 15:37:25 (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
Since charged: Reference since_charged_ref created 2013-02-20 08:01:53 (Wl: 0 elements; KWl: 39elements; NetS: 0 elements; Alrm: 0 elements; Proc: null; Oth: 7 elements; CPU: 16 elements)
Since screen off: Reference since_screen_off created 2013-02-18 15:37:25 (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
Since unplugged: Reference since_unplugged_ref created 2013-02-20 08:01:53 (Wl: 0 elements; KWl: 39elements; NetS: 0 elements; Alrm: 0 elements; Proc: null; Oth: 7 elements; CPU: 16 elements)
Since boot: Reference since_boot created 2013-02-18 15:37:25 (Wl: 6 elements; KWl: 0elements; NetS: 0 elements; Alrm: 0 elements; Proc: null; Oth: 4 elements; CPU: 16 elements)
What can i do to stop the battery drain? I'm fairly new to android so any help will be appreciated. Thanks!

well first of all, have you updated from 4.1.1 to 4.1.2? if its not take a look at the new apps that you have instaled, for example LINE drains a lot of battery.
Moreover you cann switch off location if you don-t use it.
As it is known 4.1.2 have lots of battery draining issues so when a new updated will be available try to update it.
hope it helps

aka_sirok said:
well first of all, have you updated from 4.1.1 to 4.1.2? if its not take a look at the new apps that you have instaled, for example LINE drains a lot of battery.
Moreover you cann switch off location if you don-t use it.
As it is known 4.1.2 have lots of battery draining issues so when a new updated will be available try to update it.
hope it helps
Click to expand...
Click to collapse
Yes i updated from 4.1.1 to 4.1.2 the day i got the phone. Already removed the new apps i installed, but battery loss is still there. I'll try switching off the location. Thanks!

Yeah, try that. And also know that 4.1.2 drains around 15% more battery than 4.1.1.
'Swyped' from my GT-N7100

According to my calculations based on your data input on your first post. I suggest factory reset wipe and control yourself on what app to install and not to install and try to read reviews of the apps about battery issues etc. It took me few years to learn that I dont need every app on my phone from the market.
Sent from my GT-N7100 using xda app-developers app

Just turned off the location and BAM! Battery is back on track! Thanks guys

[Q] Note 2 ~ Terrible Battery Life

My note 2 is loosing 6.2% battery an hour while it is sleeping. i know this is not normal and i am looking for a solution to my problems i will provide the BBS Dump below if anyone can help me solve my issues it would be appreciated greatly!
Code:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-05-09 17:06:59
Statistic Type: Unplugged to Current
Since 7 h 6 m 3 s
VERSION.RELEASE: 4.1.2
BRAND: samsung
DEVICE: t0lteatt
MANUFACTURER: samsung
MODEL: SAMSUNG-SGH-I317
OS.VERSION: 3.0.31-1071214
BOOTLOADER: I317UCAMA4
HARDWARE: smdk4x12
FINGERPRINT: samsung/t0lteatt/t0lteatt:4.1.2/JZO54K/I317UCAMA4:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: se.infra
PRODUCT: t0lteatt
RADIO: I317UCAMA4
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -46% (66% to 20%) [6.5%/h]
Voltage lost [mV]: (3844-3639) [28.9%/h]
===========
Other Usage
===========
Deep Sleep (): 3 h 49 m 28 s (13768 s) Ratio: 53.9%
Awake (): 3 h 16 m 35 s (11795 s) Ratio: 46.1%
Screen On (): 23 m 38 s (1418 s) Ratio: 5.5%
Phone On (): 7 m 5 s (425 s) Ratio: 1.7%
Wifi On (): 6 m 51 s (411 s) Ratio: 1.6%
Wifi Running (): 6 m 51 s (411 s) Ratio: 1.6%
No Data Connection (): 9 m 23 s (563 s) Ratio: 2.2%
No or Unknown Signal (): 9 m 23 s (563 s) Ratio: 2.2%
Poor Signal (): 39 m 22 s (2362 s) Ratio: 1.6%
Moderate Signal (): 2 h 23 m 19 s (8599 s) Ratio: 33.6%
Good Signal (): 1 h 42 m 3 s (6123 s) Ratio: 24.0%
Screen dark (): 8 m 35 s (515 s) Ratio: 2.0%
Screen dimmed (): 3 m 7 s (187 s) Ratio: 0.7%
Screen medium (): 4 m 59 s (299 s) Ratio: 1.2%
Screen light (): 6 m 45 s (405 s) Ratio: 1.6%
Screen bright (): 10 s (10 s) Ratio: 0.0%
=========
Wakelocks
=========
*backup* (Android System): 29 m 32 s (1772 s) Count:538 6.9%
*sync*_gmail-ls_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.google} (com.google.android.gm.Gmail): 18 m 7 s (1087 s) Count:44 2.6%
NLP PendingIntent client in com.google.android.googlequicksearchbox (com.google.android.apps.maps.Maps): 9 m 19 s (559 s) Count:-1331 2.2%
EM/android_talk566e723b7583 (Google Services): 7 m 30 s (450 s) Count:25 1.8%
StartingAlertService (com.android.calendar.S Planner): 6 m 57 s (417 s) Count:100 1.0%
AlarmManager (com.levelup.beautifulwidgets.BeautifulWidgets): 6 m 50 s (410 s) Count:442 1.6%
AlarmManager (Android System): 6 m 21 s (381 s) Count:1087 1.5%
LocationManagerService (Android System): 5 m 3 s (303 s) Count:159 1.2%
LocationReceiverService (com.google.android.apps.maps.Maps): 4 m 51 s (291 s) Count:2463 1.1%
AlarmManager (com.google.android.apps.maps.Maps): 4 m 34 s (274 s) Count:3698 1.1%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 3 m 58 s (238 s) Count:1350 0.9%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 3 m 53 s (233 s) Count:-530 0.9%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 3 m 50 s (230 s) Count:2035 0.9%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 3 m 35 s (215 s) Count:3439 0.8%
com.google.android.music.leanback.AutoCachingService (com.google.android.music.Google Play Music): 2 m 46 s (166 s) Count:44 0.7%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 45 s (165 s) Count:107 0.6%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 2 m 41 s (161 s) Count:53 0.6%
GTALK_CONN (Google Services): 2 m 25 s (145 s) Count:735 0.6%
RILJ (Phone): 2 m 22 s (142 s) Count:3716 0.6%
AlarmManager (com.sec.spp.push.Samsung Push Service): 1 m 57 s (117 s) Count:318 0.5%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 1 m 52 s (112 s) Count:1882 0.4%
LocationReportingService (com.google.android.apps.maps.Maps): 1 m 50 s (110 s) Count:3710 0.4%
GSM (Phone): 1 m 50 s (110 s) Count:83 0.4%
ConnectMQTT (com.nuance.swype.beta.Swype Beta 1.4): 1 m 27 s (87 s) Count:14 0.3%
AlarmManager (Google Services): 1 m 27 s (87 s) Count:821 0.3%
SyncLoopWakeLock (Android System): 1 m 15 s (75 s) Count:1287 0.3%
Checkin Service (Google Services): 1 m 13 s (73 s) Count:175 0.3%
AudioOut_2 (1013): 1 m 6 s (66 s) Count:35 0.3%
Icing (Google Services): 58 s (58 s) Count:353 0.2%
NetworkLocationLocator (Google Services): 55 s (55 s) Count:331 0.2%
GpsLocationProvider (Android System): 51 s (51 s) Count:385 0.2%
Event Log Service (Google Services): 50 s (50 s) Count:421 0.2%
AlarmManager (com.google.android.googlequicksearchbox.Google Search): 37 s (37 s) Count:90 0.1%
ActivityManager-Launch (Android System): 32 s (32 s) Count:249 0.1%
AlarmManager (com.google.android.apps.plus.Google+): 30 s (30 s) Count:33 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 28 s (28 s) Count:37 0.1%
PhoneWindowManager.mBroadcastWakeLock (Android System): 27 s (27 s) Count:286 0.1%
sleep_broadcast (Android System): 26 s (26 s) Count:469 0.1%
AlarmManager (com.nuance.swype.beta.Swype Beta 1.4): 26 s (26 s) Count:52 0.1%
AlarmManager (UID): 25 s (25 s) Count:19 0.1%
Camera Monitor (com.google.android.apps.plus.Google+): 22 s (22 s) Count:12 0.1%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 20 s (20 s) Count:38 0.1%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 18 s (18 s) Count:2829 0.1%
show keyguard (Android System): 17 s (17 s) Count:17 0.1%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 15 s (15 s) Count:3304 0.1%
FastDormancy (Phone): 14 s (14 s) Count:19 0.1%
AlarmManager (com.android.providers.calendar.Calendar storage): 13 s (13 s) Count:5 0.1%
Checkin Handoff (Google Services): 10 s (10 s) Count:93 0.0%
reset keyguard (Android System): 10 s (10 s) Count:489 0.0%
StartingAlertService (com.android.mms.Messaging): 10 s (10 s) Count:4 0.0%
AlarmManager (Phone): 8 s (8 s) Count:143 0.0%
SMSDispatcher (Phone): 7 s (7 s) Count:5 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 7 s (7 s) Count:23 0.0%
*sync*_com.android.calendar_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.osp.app.signin} (Samsung Syncadapters): 5 s (5 s) Count:2 0.0%
b (com.sec.spp.push.Samsung Push Service): 4 s (4 s) Count:204 0.0%
GTALK_IDLE_ALARM (Google Services): 4 s (4 s) Count:467 0.0%
AlarmManager (com.android.chrome.Chrome): 4 s (4 s) Count:135 0.0%
SyncManagerHandleSyncAlarm (Android System): 4 s (4 s) Count:411 0.0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar storage): 3 s (3 s) Count:10 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 3 s (3 s) Count:13 0.0%
ServiceStateTracker (Phone): 3 s (3 s) Count:72 0.0%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 3 s (3 s) Count:65 0.0%
GOOGLE_C2DM (Google Services): 3 s (3 s) Count:403 0.0%
*sync*_com.android.browser_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.osp.app.signin} (Samsung Syncadapters): 2 s (2 s) Count:4 0.0%
Proximity Partial (Android System): 2 s (2 s) Count:30 0.0%
NetworkStats (Android System): 2 s (2 s) Count:79 0.0%
WifiStateMachine (Android System): 2 s (2 s) Count:539 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1315 0.0%
Event Log Handoff (Google Services): 1 s (1 s) Count:749 0.0%
*sync*_com.android.chrome_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.google} (com.android.chrome.Chrome): 1 s (1 s) Count:50 0.0%
PhoneApp (Phone): 1 s (1 s) Count:217 0.0%
*sync*_com.android.calendar_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 1 s (1 s) Count:4 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:493 0.0%
NetworkLocationCacheUpdater (Google Services): 1 s (1 s) Count:30 0.0%
PreventScreenOn Partial (Android System): 1 s (1 s) Count:288 0.0%
keyguardWakeAndHandOff (Android System): 1 s (1 s) Count:552 0.0%
multiplexing-gcm-listener:com.google.android.apps.chrome.snapshot.gcm.GcmReceiver (com.android.chrome.Chrome): 1 s (1 s) Count:174 0.0%
*sync*_com.android.contacts_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.osp.app.signin} (Samsung Syncadapters): 1 s (1 s) Count:3 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 2 h 10 m 10 s (7810 s) Cnt:(c/wc/ec)2556/0/0 30.6%
"mdm_hsic_pm0" (): 44 m (2640 s) Cnt:(c/wc/ec)3966/222/0 10.3%
"fast_dormancy" (): 33 m 3 s (1983 s) Cnt:(c/wc/ec)334/0/334 7.8%
"hsicctl0" (): 18 m 53 s (1133 s) Cnt:(c/wc/ec)2137/0/2137 4.4%
"battery-monitor" (): 14 m 42 s (882 s) Cnt:(c/wc/ec)906/0/906 3.5%
"radio-interface" (): 13 m 18 s (798 s) Cnt:(c/wc/ec)769/0/0 3.1%
"alarm_rtc" (): 7 m 26 s (446 s) Cnt:(c/wc/ec)849/0/121 1.7%
"alarm" (): 6 m 16 s (376 s) Cnt:(c/wc/ec)1691/1/5 1.5%
"battery-update" (): 1 m 52 s (112 s) Cnt:(c/wc/ec)45/0/45 0.4%
"sensorhub_wake_lock" (): 1 m 52 s (112 s) Cnt:(c/wc/ec)49/0/48 0.4%
"AudioOutLock" (): 48 s (48 s) Cnt:(c/wc/ec)35/0/0 0.2%
"ssp_wake_lock" (): 34 s (34 s) Cnt:(c/wc/ec)18/3/18 0.1%
"sync_system" (): 1 s (1 s) Cnt:(c/wc/ec)31/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)8527/0/0 0.0%
"qcril" (): (0 s) Cnt:(c/wc/ec)1308/0/0 0.0%
"ApmCommand" (): (0 s) Cnt:(c/wc/ec)283/0/0 0.0%
"qmuxd_port_wl_9" (): (0 s) Cnt:(c/wc/ec)5523/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)906/599/0 0.0%
"mmc1_detect" (): (0 s) Cnt:(c/wc/ec)1046/0/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)1046/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.6 GHz (): 2 h 56 m 29 s 41.4%
1.5 GHz (): 43 s 0.2%
1.4 GHz (): 40 s 0.2%
1.3 GHz (): 6 s 0.0%
1.2 GHz (): 2 m 35 s 0.6%
1.1 GHz (): 38 s 0.2%
1 GHz (): 30 s 0.1%
900 MHz (): 3 s 0.0%
800 MHz (): 12 m 55 s 3.0%
700 MHz (): 29 s 0.1%
600 MHz (): 27 s 0.1%
500 MHz (): 2 s 0.0%
400 MHz (): 53 s 0.2%
Deep Sleep (): 3 h 49 m 28 s 53.9%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 1 d 10 h 50 m 52 s (Wl: 86 elements; KWl: 30elements; NetS: null; Alrm: null; Proc: 26 elements; Oth: 15 elements; CPU: 15 elements)
ref_current: Reference ref_current created 1 d 17 h 56 m 56 s (Wl: 97 elements; KWl: 30elements; NetS: null; Alrm: null; Proc: 44 elements; Oth: 16 elements; CPU: 15 elements)

What kernel are you running. ..
Root=true
And your device ran for 2 hours 56 minutes at 1.6 ghz on 4 cores.(ouch that's bad)..
Your right. ..something is messed up. ...g

IF you are running a custom rom I would do a clean flash of whatever you are runnning if not I would root and flash a rom like clean rom or novella

envision said:
IF you are running a custom rom I would do a clean flash of whatever you are runnning if not I would root and flash a rom like clean rom or novella
Click to expand...
Click to collapse
i just flashed CleanROM 4.9 completely fresh

Kernel issue. ...it's gotta be a kernel related problem...imho....g

gregsarg said:
Kernel issue. ...it's gotta be a kernel related problem...imho....g
Click to expand...
Click to collapse
CleanRom uses the Perseus kernal right? any ideas on how i can fix this?

FluryKnox said:
CleanRom uses the Perseus kernal right? any ideas on how i can fix this?
Click to expand...
Click to collapse
Well...
Trying another kernel would certainly tell you what you want to know.
Cleanrom is a touchwiz rom isn't it?
Let me look at the rom and see if I can find an alternative....
Be back shortly...g

gregsarg said:
Well...
Trying another kernel would certainly tell you what you want to know.
Cleanrom is a touchwiz rom isn't it?
Let me look at the rom and see if I can find an alternative....
Be back shortly...g
Click to expand...
Click to collapse
i just fresh installed cleanrom again and installed BBS again gonna let it sit in sleep mode all night ill report back when the battery is 20%

Based on the reading i just did on kernels over on Scotts site, the Saber kernel will work also.
Users report good function, but most are using perseus.
I prefer Saber on a stock TW build. And I have not tested saber on Scotts builds.
Worst case, run a good backup before changes are made, and restore if needed...g

gregsarg said:
Based on the reading i just did on kernels over on Scotts site, the Saber kernel will work also.
Users report good function, but most are using perseus.
I prefer Saber on a stock TW build. And I have not tested saber on Scotts builds.
Worst case, run a good backup before changes are made, and restore if needed...g
Click to expand...
Click to collapse
Yeahh this problem started appearing out of the blue it seems like i just fresh installed gonna let my phone sit all night no usage only sleep mode ill report back with another BBS Dump in the morning. i made sure google did not restore my phone lets see if this will work......

Sounds good. .
I'm curious to see the log. And also interested in the rom.
I nearly loaded it up today, but I'm waiting pending the results you post.
Catch ya tomorrow. ..g

When I was running CleanRom I was burning huge amounts of battery, like 15-20% overnight vs 2-3% on stock. I was getting dozens of wakelocks throughout the night. I found the stock ATT kernel and went back to that and my battery drain was about 8% overnight. Now I'm running CM10.1 on their stock kernel and I'm burning 4% overnight.
I haven't found any rom/kernel combination that will give me the batter life of the stock setup. However, I'm loving my CM10.1 battery life at the moment, plus the whole bonus of vanilla android.

gregsarg said:
Sounds good. .
I'm curious to see the log. And also interested in the rom.
I nearly loaded it up today, but I'm waiting pending the results you post.
Catch ya tomorrow. ..g
Click to expand...
Click to collapse
Im getting WAY better results now are these pretty much normal for the note2?
i left my wifi connected connected all night while in sleep mode so thats probably the reason its 2.0/h power loss but overall i feel this is pretty much normal now right?
Code:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-05-10 12:59:49
Statistic Type: Unplugged to Current
Since 15 h 25 m 52 s
VERSION.RELEASE: 4.1.2
BRAND: samsung
DEVICE: t0lteatt
MANUFACTURER: samsung
MODEL: SAMSUNG-SGH-I317
OS.VERSION: 3.0.31-1071214
BOOTLOADER: I317UCAMA4
HARDWARE: smdk4x12
FINGERPRINT: samsung/t0lteatt/t0lteatt:4.1.2/JZO54K/I317UCAMA4:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: se.infra
PRODUCT: t0lteatt
RADIO: I317UCAMA4
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -32% (100% to 68%) [2.1%/h]
Voltage lost [mV]: (4275-3940) [21.7%/h]
===========
Other Usage
===========
Deep Sleep (): 14 h 17 m (51420 s) Ratio: 92.6%
Awake (): 1 h 8 m 52 s (4132 s) Ratio: 7.4%
Screen On (): 7 m 5 s (425 s) Ratio: 0.8%
Wifi On (): 15 h 25 m 52 s (55552 s) Ratio: 100.0%
Wifi Running (): 15 h 25 m 52 s (55552 s) Ratio: 100.0%
No Data Connection (): 15 h 25 m 17 s (55517 s) Ratio: 99.9%
No or Unknown Signal (): 15 h 25 m 17 s (55517 s) Ratio: 99.9%
Good Signal (): (0 s) Ratio: 0.0%
Screen dark (): 5 m 31 s (331 s) Ratio: 0.6%
Screen dimmed (): 1 m 10 s (70 s) Ratio: 0.1%
Screen medium (): 23 s (23 s) Ratio: 0.0%
=========
Wakelocks
=========
AlarmManager (Android System): 1 m 48 s (108 s) Count:1220 0.2%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 1 m 41 s (101 s) Count:131 0.2%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 1 m 39 s (99 s) Count:358 0.2%
com.google.android.music.leanback.AutoCachingService (com.google.android.music.Google Play Music): 59 s (59 s) Count:41 0.1%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 52 s (52 s) Count:135 0.1%
FastDormancy (Phone): 38 s (38 s) Count:362 0.1%
*sync*_gmail-ls_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.google} (com.google.android.gm.Gmail): 28 s (28 s) Count:17 0.1%
RILJ (Phone): 16 s (16 s) Count:345 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 16 s (16 s) Count:29 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 10 s (10 s) Count:3 0.0%
ActivityManager-Launch (Android System): 10 s (10 s) Count:152 0.0%
AudioOut_2 (1013): 7 s (7 s) Count:2 0.0%
Icing (Google Services): 7 s (7 s) Count:31 0.0%
ConnectMQTT (com.nuance.swype.beta.Swype Beta 1.4): 6 s (6 s) Count:88 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 4 s (4 s) Count:13 0.0%
AlarmManager (com.google.android.apps.maps.Maps): 4 s (4 s) Count:491 0.0%
GTALK_CONN (Google Services): 4 s (4 s) Count:339 0.0%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 3 s (3 s) Count:86 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 3 s (3 s) Count:161 0.0%
AlarmManager (Google Services): 3 s (3 s) Count:497 0.0%
AlarmManager (com.google.android.music.Google Play Music): 3 s (3 s) Count:50 0.0%
SyncLoopWakeLock (Android System): 3 s (3 s) Count:1324 0.0%
Event Log Service (Google Services): 2 s (2 s) Count:83 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 2 s (2 s) Count:82 0.0%
AlarmManager (UID): 2 s (2 s) Count:29 0.0%
sleep_broadcast (Android System): 2 s (2 s) Count:238 0.0%
show keyguard (Android System): 2 s (2 s) Count:13 0.0%
AlarmManager (com.sec.spp.push.Samsung Push Service): 2 s (2 s) Count:128 0.0%
GpsLocationProvider (Android System): 2 s (2 s) Count:216 0.0%
Checkin Service (Google Services): 1 s (1 s) Count:396 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:245 0.0%
AlarmManager (Phone): 1 s (1 s) Count:142 0.0%
EM/android_talk58c0594adc84 (Google Services): 1 s (1 s) Count:398 0.0%
NetworkStats (Android System): 1 s (1 s) Count:68 0.0%
================
Kernel Wakelocks
================
"battery-monitor" (): 28 m 8 s (1688 s) Cnt:(c/wc/ec)1706/0/1706 3.0%
"mdm_hsic_pm0" (): 20 m 35 s (1235 s) Cnt:(c/wc/ec)1972/456/0 2.2%
"wlan_rx_wake" (): 18 m 15 s (1095 s) Cnt:(c/wc/ec)1107/0/1106 2.0%
"PowerManagerService" (): 9 m 2 s (542 s) Cnt:(c/wc/ec)1518/0/0 1.0%
"alarm_rtc" (): 8 m 21 s (501 s) Cnt:(c/wc/ec)984/33/37 0.9%
"hsicctl0" (): 6 m 16 s (376 s) Cnt:(c/wc/ec)672/0/672 0.7%
"alarm" (): 6 m 3 s (363 s) Cnt:(c/wc/ec)1384/1/0 0.7%
"wlan_wake" (): 3 m 30 s (210 s) Cnt:(c/wc/ec)18569/732/0 0.4%
"wlan_ctrl_wake" (): 3 m 4 s (184 s) Cnt:(c/wc/ec)155/0/155 0.3%
"battery-update" (): 1 m 30 s (90 s) Cnt:(c/wc/ec)32/0/33 0.2%
"radio-interface" (): 1 m 1 s (61 s) Cnt:(c/wc/ec)64/0/0 0.1%
"fast_dormancy" (): 53 s (53 s) Cnt:(c/wc/ec)8/0/8 0.1%
"sensorhub_wake_lock" (): 21 s (21 s) Cnt:(c/wc/ec)21/0/22 0.0%
"AudioOutLock" (): 9 s (9 s) Cnt:(c/wc/ec)2/0/0 0.0%
"qmuxd_port_wl_9" (): (0 s) Cnt:(c/wc/ec)3123/0/0 0.0%
"qcril" (): (0 s) Cnt:(c/wc/ec)170/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)3990/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)1707/414/0 0.0%
"mmc1_detect" (): (0 s) Cnt:(c/wc/ec)1827/0/0 0.0%
"sync_system" (): (0 s) Cnt:(c/wc/ec)9/0/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)1827/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.6 GHz (): 1 m 49 s 0.2%
1.5 GHz (): 4 s 0.0%
1.4 GHz (): 40 s 0.1%
1.3 GHz (): 5 s 0.0%
1.2 GHz (): 27 s 0.0%
1.1 GHz (): 6 s 0.0%
1 GHz (): 13 m 2 s 1.4%
900 MHz (): 6 s 0.0%
800 MHz (): 24 m 13 s 2.6%
700 MHz (): 43 s 0.1%
600 MHz (): 1 m 40 s 0.2%
500 MHz (): 55 s 0.1%
400 MHz (): 7 m 6 s 0.8%
200 MHz (): 17 m 51 s 1.9%
Deep Sleep (): 14 h 17 m 92.6%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 2 h 56 m 14 s (Wl: 0 elements; KWl: 25elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 15 elements)
ref_charged: Reference ref_charged created 2 h 56 m 14 s (Wl: 0 elements; KWl: 25elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 15 elements)
ref_current: Reference ref_current created 18 h 22 m 7 s (Wl: 34 elements; KWl: 24elements; NetS: null; Alrm: null; Proc: 12 elements; Oth: 11 elements; CPU: 15 elements)

"MUCH" better. ..
That usage is in line with the average note2 I would think.
And if you flash a stock kernel it will get even better.
It is my belief, and of many others that this device needs no kernel changes.
The device runs it's best on the stock kernel. ..IMHO
Watch it for a few days, and see if you notice any other battery drain issues.
If you do, try the different kernel. ...g
Edit:
I also noticed the CPU usage in the upper levels has returned to normal range as well.
What ever you did, keep doing it. ..g

gregsarg said:
"MUCH" better. ..
That usage is in line with the average note2 I would think.
And if you flash a stock kernel it will get even better.
It is my belief, and of many others that this device needs no kernel changes.
The device runs it's best on the stock kernel. ..IMHO
Watch it for a few days, and see if you notice any other battery drain issues.
If you do, try the different kernel. ...g
Edit:
I also noticed the CPU usage in the upper levels has returned to normal range as well.
What ever you did, keep doing it. ..g
Click to expand...
Click to collapse
Yeah im beginning to think it was a wonky app that i had installed. i havnt installed anything on it yet besides BBS going to slowly re install apps and continue monitoring it.

Thank you. ..
It's great information on the rom...g

cell wont deep sleep / battery is draining

my cell is dead in hours and cant figure it out. i completely wiped it and restored to stock and then ran MD4 stock for sometime and have same problem as the MK3 stock.
installed better battery stats last night and here is the file
can anyone help me out with this. this is the phone sitting at night. rooted stock 4.3 stock kernel with cnexus tweaks even has juice defender to stop internet activity.
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2014-02-08 07:53:00
Statistic Type: Unplugged to Current
Since 11 h 51 m 24 s
VERSION.RELEASE: 4.3
BRAND: samsung
DEVICE: d2spr
MANUFACTURER: samsung
MODEL: SPH-L710
OS.VERSION: 3.0.31-g1ac4b4a-dirty
BOOTLOADER: L710VPBMD4
HARDWARE: qcom
FINGERPRINT: samsung/d2spr/d2spr:4.3/JSS15J/L710VPUCMK3:user/release-keys
ID: JSS15J
TAGS: release-keys
USER: se.infra
PRODUCT: d2spr
RADIO: L710VPUCMK3
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -91% (100% to 9%) [7.7%/h]
Voltage lost [mV]: (4203-3578) [52.7%/h]
===========
Other Usage
===========
Deep Sleep (): 1 m 12 s (72 s) Ratio: 0.1%
Awake (): 11 h 50 m 12 s (42612 s) Ratio: 99.8%
Screen On (): 29 m 38 s (1778 s) Ratio: 4.2%
Phone On (): 14 s (14 s) Ratio: 0.0%
Wifi On (): 34 m 4 s (2044 s) Ratio: 4.8%
Wifi Running (): 11 h 51 m 24 s (42684 s) Ratio: 100.0%
Screen dark (): 29 m 38 s (1778 s) Ratio: 4.2%
=========
Wakelocks
=========
AudioOut_2 (1013): 15 m 26 s (926 s) Count:41 2.2%
Starting CM_VnoteService (com.coremobility.app.vnotes.Voicemail): 10 m 27 s (627 s) Count:22 1.5%
NlpWakeLock (Google Play services): 8 m 53 s (533 s) Count:336 1.2%
ConnectivityService (Android System): 4 m 44 s (284 s) Count:1433 0.7%
JuiceDefender.Service (JuiceDefender): 3 m 25 s (205 s) Count:825 0.5%
AlarmManager (Android System): 3 m 23 s (203 s) Count:1427 0.5%
PushClient SystemStateMonitorService (com.sec.spp.push.Samsung Push Service): 1 m 11 s (71 s) Count:96 0.2%
SprintUpdater-UpdaterService (com.sprint.ce.updater.Sprint Installer): 58 s (58 s) Count:1 0.1%
ActivityManager-Launch (Android System): 33 s (33 s) Count:463 0.1%
GCM_CONN_ALARM (Google Play services): 17 s (17 s) Count:647 0.0%
SMSDispatcher (Phone): 16 s (16 s) Count:12 0.0%
NlpCollectorWakeLock (Google Play services): 14 s (14 s) Count:730 0.0%
(com.sprint.zone.Sprint Zone): 12 s (12 s) Count:68 0.0%
SmartFaceService (Android System): 12 s (12 s) Count:481 0.0%
FbClientConnManager (com.facebook.katana.Facebook): 11 s (11 s) Count:24 0.0%
AlarmManager (Google Play services): 10 s (10 s) Count:1289 0.0%
RILJ (Phone): 10 s (10 s) Count:125 0.0%
PhoneApp (Phone): 9 s (9 s) Count:3 0.0%
AudioIn_1D8 (1013): 9 s (9 s) Count:43 0.0%
StartingAlertService (com.android.mms.Messaging): 8 s (8 s) Count:13 0.0%
AlarmManager (com.facebook.katana.Facebook): 8 s (8 s) Count:94 0.0%
CM Message wakeup (com.coremobility.app.vnotes.Voicemail): 7 s (7 s) Count:69 0.0%
CleanupService (com.groupme.android.GroupMe): 7 s (7 s) Count:5 0.0%
NetworkLocationLocator (Google Play services): 7 s (7 s) Count:676 0.0%
Icing (Google Play services): 6 s (6 s) Count:672 0.0%
*sync*_com.google.android.apps.plus.content.EsProv ider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.apps.plus.Google+): 6 s (6 s) Count:7 0.0%
Event Log Service (Google Play services): 5 s (5 s) Count:757 0.0%
SCREEN_FROZEN (Android System): 5 s (5 s) Count:586 0.0%
LocationManagerService (Android System): 5 s (5 s) Count:408 0.0%
*sync*_com.sec.android.gallery3d.picasa.contentpro vider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.sec.android.gallery3d.Gallery): 4 s (4 s) Count:7 0.0%
MMS PushReceiver (com.android.mms.Messaging): 4 s (4 s) Count:17 0.0%
show keyguard (Android System): 4 s (4 s) Count:163 0.0%
NlpLocationReceiverService (com.google.android.googlequicksearchbox.Google Search): 4 s (4 s) Count:380 0.0%
SyncLoopWakeLock (Android System): 4 s (4 s) Count:1558 0.0%
DHCP (Android System): 4 s (4 s) Count:591 0.0%
AlarmManager (com.google.android.talk.Hangouts): 4 s (4 s) Count:22 0.0%
*backup* (Android System): 3 s (3 s) Count:634 0.0%
GCM_CONN (Google Play services): 3 s (3 s) Count:850 0.0%
AlarmManager (com.sec.spp.push.Samsung Push Service): 3 s (3 s) Count:173 0.0%
TimaService (Android System): 2 s (2 s) Count:142 0.0%
mResetWakelock (Android System): 2 s (2 s) Count:154 0.0%
StartingAlertService (com.android.calendar.Calendar): 2 s (2 s) Count:12 0.0%
AlarmManager (com.drclabs.android.wootchecker.WootWatcher): 2 s (2 s) Count:166 0.0%
SamsungPhoneWindowManager.mBroadcastWakeLock (Android System): 2 s (2 s) Count:491 0.0%
WootWatcherWakeLock (com.drclabs.android.wootchecker.WootWatcher): 2 s (2 s) Count:83 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Play services): 2 s (2 s) Count:734 0.0%
NetworkStats (Android System): 2 s (2 s) Count:243 0.0%
hangouts_rtcs (com.google.android.talk.Hangouts): 2 s (2 s) Count:13 0.0%
gum (com.google.android.googlequicksearchbox.Google Search): 2 s (2 s) Count:115 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 2 s (2 s) Count:3 0.0%
MMS Connectivity (com.android.mms.Messaging): 1 s (1 s) Count:21 0.0%
AlarmManager (JuiceDefender): 1 s (1 s) Count:107 0.0%
GpsLocationProvider (Android System): 1 s (1 s) Count:557 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 1 s (1 s) Count:2 0.0%
AlarmManager (com.sprint.zone.Sprint Zone): 1 s (1 s) Count:91 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 1 s (1 s) Count:8 0.0%
Checkin Service (Google Play services): 1 s (1 s) Count:437 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1442 0.0%
LocationManagerService (Google Play services): 1 s (1 s) Count:167 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats ): 1 s (1 s) Count:2 0.0%
AudioIn_1E6 (1013): 1 s (1 s) Count:4 0.0%
================
Kernel Wakelocks
================
"suspend_backoff" (): 5 h 37 m 1 s (20221 s) Cntc/wc/ec)2025/0/2025 37.7%
"mmc1_detect" (): 3 h 45 m 52 s (13552 s) Cntc/wc/ec)20275/0/20275 31.7%
"sec-battery-monitor" (): 2 h 53 m 5 s (10385 s) Cntc/wc/ec)20291/0/0 24.3%
"mmc0_detect" (): 2 h 46 m 1 s (9961 s) Cntc/wc/ec)20275/0/20275 23.3%
"PowerManagerService.WakeLocks" (): 35 m 56 s (2156 s) Cntc/wc/ec)2432/0/0 5.1%
"alarm_rtc" (): 13 m 57 s (837 s) Cntc/wc/ec)868/0/200 2.0%
"pm8xxx_adc_wakelock" (): 9 m 51 s (591 s) Cntc/wc/ec)40041/19684/0 1.4%
"sec-battery-measure" (): 9 m 46 s (586 s) Cntc/wc/ec)20307/0/0 1.4%
"wlan_ctrl_wake" (): 6 m 55 s (415 s) Cntc/wc/ec)321/0/321 1.0%
"bam_dmux_wakelock" (): 2 m 41 s (161 s) Cntc/wc/ec)128/0/64 0.4%
"power-supply" (): 1 m 44 s (104 s) Cntc/wc/ec)20291/0/0 0.2%
"wlan_rx_wake" (): 1 m 40 s (100 s) Cntc/wc/ec)666/0/666 0.2%
"smdcntl0" (): 1 m 33 s (93 s) Cntc/wc/ec)1794/1/163 0.2%
"radio-interface" (): 41 s (41 s) Cntc/wc/ec)60/0/0 0.1%
"alarm" (): 40 s (40 s) Cntc/wc/ec)1826/2/0 0.1%
"KeyEvents" (): 27 s (27 s) Cntc/wc/ec)61903/0/0 0.1%
"wlan_wake" (): 25 s (25 s) Cntc/wc/ec)52911/0/0 0.1%
"PowerManagerService.Broadcasts" (): 9 s (9 s) Cntc/wc/ec)24/0/0 0.0%
"vib_present" (): 9 s (9 s) Cntc/wc/ec)52/0/0 0.0%
"DS" (): 5 s (5 s) Cntc/wc/ec)13/0/13 0.0%
"LightsService" (): 3 s (3 s) Cntc/wc/ec)16/0/0 0.0%
"rmt_storage_-1205258928" (): 1 s (1 s) Cntc/wc/ec)5/0/0 0.0%
"PowerManagerService.Display" (): 1 s (1 s) Cntc/wc/ec)12/0/0 0.0%
"rmt_storage_-1205259776" (): 1 s (1 s) Cntc/wc/ec)5/0/0 0.0%
"MediaPlayerService_Decode" (): 1 s (1 s) Cntc/wc/ec)49/0/0 0.0%
"ipc00000001_rmt_storage" (): (0 s) Cntc/wc/ec)31/0/0 0.0%
"qmuxd_port_wl_0" (): (0 s) Cntc/wc/ec)1671/0/0 0.0%
"ApmCommand" (): (0 s) Cntc/wc/ec)162/0/0 0.0%
"msm_ipc_router_smd_xprt" (): (0 s) Cntc/wc/ec)51/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
384 MHz (): 11 h 15 m 1 s 94.9%
486 MHz (): 2 m 6 s 0.3%
594 MHz (): 1 m 18 s 0.2%
702 MHz (): 54 s 0.1%
810 MHz (): 3 m 47 s 0.5%
918 MHz (): 9 m 19 s 1.3%
1.03 GHz (): 1 m 18 s 0.2%
1.13 GHz (): 1 m 54 s 0.3%
1.24 GHz (): 27 s 0.1%
1.35 GHz (): 31 s 0.1%
1.46 GHz (): 10 s 0.0%
1.51 GHz (): 13 m 22 s 1.9%
Deep Sleep (): 1 m 12 s 0.1%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 1 m 5 s (Wl: 9 elements; KWl: 20elements; NetS: null; Alrm: null; Proc: 10 elements; Oth: 2 elements; CPU: 2 elements)
ref_unplugged: Reference ref_unplugged created 3 h 1 m 43 s (Wl: 0 elements; KWl: 33elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 5 elements; CPU: 12 elements)
ref_charged: Reference ref_charged created 3 h 1 m 43 s (Wl: 0 elements; KWl: 33elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 5 elements; CPU: 12 elements)
ref_current: Reference ref_current created 14 h 53 m 7 s (Wl: 61 elements; KWl: 32elements; NetS: null; Alrm: null; Proc: 137 elements; Oth: 7 elements; CPU: 13 elements)

The first thing is, uninstall Juice Defender. Until you know what is going on with the Battery Life, all you are doing doing is complicating the issue. You say you did a complete wipe before installing the Rom ? Does that mean you wiped: System, Data, Dalvik Cache, Cache, Factory Reset ? Did you restore any Data ? Have you tried a different Battery to rule out that the battery is defective ?

Did everything except battery...even an Odin restore to stock..same issue minimum 10 percent per hour drain
Sent from my SPH-L710 using xda app-developers app

New battery and same issues
Sent from my SPH-L710 using xda app-developers app

jalfonso119 said:
Did everything except battery...even an Odin restore to stock..same issue minimum 10 percent per hour drain
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
jalfonso119 said:
New battery and same issues
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That's very strange . Are you sure that there's not a wakelock going on ? What's your screen on time ?

Uninstall BBS.
Go and install GSam Battery Monitor from Play. Your phone certainly isn't sleeping. He was 11hrs awake.
Been the same problem within two different roms, can be mediaserver or a specific app.
With GSam you can see what app or process is really draining your battery. In the App Usage section.
Sent from my SPH-L710

I tried several roms without even installing apps and same thing. Tried several kernels too.. I even Odin to md4 stock up rooted and same thing... I have gsam and it's the kernel OS draining the battery and won't deep sleep... It even drains when there isn't any data connection... Also I got the zero lemon battery now so that's why it doesn't look like it's draining much but it still is
Sent from my SPH-L710 using xda app-developers app
Sent from my SPH-L710 using xda app-developers app

Sent from my SPH-L710 using xda app-developers app