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

darkside evolution battery life

New to the SG2 and first ROM I flashed is darkside evolution. I love it so far but had a question about the battery life. I usually unplug my phone around 7am and by the time I get home from work (5:45 pm) I am at about 30% battery. I only use the phone to chat, web, and email when I get the chance without being on wifi.
I am reading that people are getting good battery life from this ROM and want to know what your % battery you have remaining at the end of the day.

Over the exact same timeframe, I ended the day with maybe 60-65% yesterday with Bluetooth on the whole day and infrequent usage.

I was on the same ROM before and I can say that I had very similar battery life as yours, around 30% after around 10 hrs and 2 hrs display on time. Battery use is a very subjective matter and I have seen other posts where battery life far exceeded my experiences. I was overall very happy though as the battery life was the same, if not better than stock. With the added performance improvements from the ROM it is very reasonable.
Sent from my SGH-T989D using xda premium

Don't forget if you don't have good reception, it takes a huge toll on your battery life
Sent from my SGH-T989 using xda premium

I started having a problem yesterday, but I've been tinkering with my stuff a lot for my theme... The problem is it won't deep sleep and I can't figure out why...
this is my BetterBatteryStats log:
Code:
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-05-10 12:50:04
Statistic Type: (3) Since Unplugged
Since 56 m 11 s
VERSION.RELEASE: 4.0.3
BRAND: samsung
DEVICE: SGH-T989
MANUFACTURER: samsung
MODEL: SGH-T989
BOOTLOADER: unknown
FINGERPRINT: samsung/SGH-T989/SGH-T989:4.0.3/IML74K/UVLC8:user/release-keys
HARDWARE: qcom
ID: IML74K
TAGS: release-keys
USER: thederekjay
PRODUCT: SGH-T989
RADIO: T989UVLC8
Rooted: true
===========
Other Usage
===========
Awake (): 56 m 11 s (3371 s) Ratio: 100.0%
Good Signal (): 52 m 15 s (3135 s) Ratio: 93.0%
Screen On (): 13 m 43 s (823 s) Ratio: 24.4%
Phone On (): 24 s (24 s) Ratio: 0.7%
No Data Connection (): 7 s (7 s) Ratio: 0.2%
No or Unknown Signal (): 7 s (7 s) Ratio: 0.2%
=========
Wakelocks
=========
AlarmManager (Android System): 2 m 20 s (140 s) Count:285 4.2%
AudioOut_1 (1013): 1 m 6 s (66 s) Count:23 2.0%
SMSDispatcher (Phone): 41 s (41 s) Count:10 1.2%
ActivityManager-Launch (Android System): 32 s (32 s) Count:193 1.0%
RILJ (Phone): 24 s (24 s) Count:261 0.7%
NetworkStats (Android System): 17 s (17 s) Count:105 0.5%
MediaScannerService (Media): 14 s (14 s) Count:2 0.4%
DownloadManager (Media): 6 s (6 s) Count:3 0.2%
StartingAlertService (com.concentriclivers.mms.com.android.mms.Messaging): 5 s (5 s) Count:18 0.2%
sleep_broadcast (Android System): 5 s (5 s) Count:36 0.2%
GSM (Phone): 4 s (4 s) Count:22 0.1%
show keyguard (Android System): 4 s (4 s) Count:50 0.1%
FastDormancy (Phone): 2 s (2 s) Count:20 0.1%
GpsLocationProvider (Android System): 2 s (2 s) Count:3 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 1 s (1 s) Count:3 0.1%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 s (1 s) Count:23 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:309 0.0%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cnt:(c/wc/ec)1/1/1 100.0%
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
Click to expand...
Click to collapse
Im stumped.

Teo032 said:
Don't forget if you don't have good reception, it takes a huge toll on your battery life
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
how so?

Akim1220 said:
how so?
Click to expand...
Click to collapse
The radios working a lot harder. It will drain a lot faster with bad reception

Well I have great reception and I just flashed blaze radio noticed my battery draining faster
Sent from my SGH-T989 using xda premium

peppersu812 said:
Well I have great reception and I just flashed blaze radio noticed my battery draining faster
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Generally, crappy reception means crappy battery.

Touch Recovery brakes the Deep Sleep
I had the exact same problem using DarkSide ROM.
I read that Touch recovery has a buggy that kills the Deep Sleep. So I went and flashed the ROM with Non-Touch recovery and Voilá...
Deep Sleep is back working like a charm.
I advise you all that are having battery issues to try to use Non-Touch recovery to flash this ROM.
This is where I read it:
http://forum.xda-developers.com/showpost.php?p=25771623&postcount=5

I had wifi and data on most of the time and i got my phone to go for 17 hours and I'm at 30% right now. I've had the rom installed for 2-3 days and gone through 2 charge cycles from 100 to 0 and then recharge.

how important is it too do the charge cycles and how do you check what type of recovery you have? also, what app did you use to see if your battery was sleeping?

im only getting 6 hours of battery life using juggernaut and darkside kernal. what could the problem be here guys?
Sent from my SGH-T989 using XDA

I have had great battery life. With light use right now(send text messages all day on the phone for 5 minutes) I am at 75% for 12 hours. Under moderate to heavy use after 12 hours I am at 50%. I keep wifi and GPS on the whole time and the screen to max brightness.

blkbltwrestler said:
I have had great battery life. With light use right now(send text messages all day on the phone for 5 minutes) I am at 75% for 12 hours. Under moderate to heavy use after 12 hours I am at 50%. I keep wifi and GPS on the whole time and the screen to max brightness.
Click to expand...
Click to collapse
are you running darkside evolution>?

Akim1220 said:
how important is it too do the charge cycles and how do you check what type of recovery you have? also, what app did you use to see if your battery was sleeping?
Click to expand...
Click to collapse
When you boot into cwm it will say what version you have. CPU spy to check CPU states.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Akim1220 said:
are you running darkside evolution>?
Click to expand...
Click to collapse
yep beta 2

phoenix6 said:
I started having a problem yesterday, but I've been tinkering with my stuff a lot for my theme... The problem is it won't deep sleep and I can't figure out why...
this is my BetterBatteryStats log:
Im stumped.
Click to expand...
Click to collapse
just saw this on my phone. go to system settings -> developr options and make sure stay awake is not checked.

Huge Battery Drain Problems

Hey everyone,
About three weeks ago I noticed that my battery appeared to drain much quicker than before while running Calks 1.7 GB rom on EL26. I figured that this could just have been a bug so I upgraded to his 1.6 ICS 4.04 ROM flashing through recovery. However, this did not alleviate the issue. When I investigated this further it appeared that the phone is unable to efficiently enter a deep sleep. I have disabled all sync's and have no apps installed. After a full charge I get about 6 hours of battery life without using my phone once (and also in airplane mode). The Android OS kernel takes up 99% of the CPU usage. I downloaded Better Battery Stats and created a dump file here:
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-07-03 11:54:55
Statistic Type: (3) Since Unplugged
Since 5 h 24 m 31 s
VERSION.RELEASE: 4.0.4
BRAND: samsung
DEVICE: SPH-D710
MANUFACTURER: samsung
MODEL: SPH-D710
BOOTLOADER: unknown
FINGERPRINT: samsung/SPH-D710/SPH-D710:4.0.4/IMM76I/FE22:user/release-keys
HARDWARE: smdk4210
ID: IMM76I
TAGS: release-keys
USER: se.infra
PRODUCT: SPH-D710
RADIO: S710.10 S.FF18
Rooted: true
===========
Other Usage
===========
Awake (): 3 h 49 m 23 s (13763 s) Ratio: 70.7%
Deep Sleep (): 1 h 35 m 2 s (5702 s) Ratio: 29.3%
No Data Connection (): 1 h 19 m 46 s (4786 s) Ratio: 24.6%
No or Unknown Signal (): 1 h 19 m 46 s (4786 s) Ratio: 24.6%
Screen On (): 42 m 33 s (2553 s) Ratio: 13.1%
=========
Wakelocks
=========
AudioOut_1 (1013): 14 m 8 s (848 s) Count:158 4.4%
DownloadManager (Media): 1 m 24 s (84 s) Count:1 0.4%
ActivityManager-Launch (Android System): 47 s (47 s) Count:250 0.2%
Starting CM_VnoteService (com.coremobility.app.vnotes.Voicemail): 30 s (30 s) Count:8 0.2%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 29 s (29 s) Count:10 0.2%
sleep_broadcast (Android System): 22 s (22 s) Count:348 0.1%
AlarmManager (Android System): 19 s (19 s) Count:869 0.1%
show keyguard (Android System): 12 s (12 s) Count:34 0.1%
*sync*_gmail-ls_Account {[email protected]#[email protected]#%@@gmail.com, type=com.google} (com.google.android.gm.Gmail): 11 s (11 s) Count:4 0.1%
RILJ (Phone): 11 s (11 s) Count:373 0.1%
SCREEN_FROZEN (Android System): 6 s (6 s) Count:364 0.0%
*sync*_subscribedfeeds_Account {name=%^&%^@gmail.com, type=com.google} (Google Services): 6 s (6 s) Count:3 0.0%
GTALK_CONN (Google Services): 6 s (6 s) Count:183 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 3 s (3 s) Count:3 0.0%
SyncLoopWakeLock (Android System): 3 s (3 s) Count:926 0.0%
Browser (com.android.browser.Internet): 3 s (3 s) Count:1 0.0%
[email protected]#[email protected]#[email protected]/android_talk487cab5da65a (Google Services): 2 s (2 s) Count:16 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 s (2 s) Count:196 0.0%
keyguardWakeAndHandOff (Android System): 1 s (1 s) Count:422 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 1 s (1 s) Count:254 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:14 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:913 0.0%
NetworkStats (Android System): 1 s (1 s) Count:61 0.0%
NotificationService (Android System): 1 s (1 s) Count:380 0.0%
================
Kernel Wakelocks
================
"sec-battery-monitor" (): 1 h 56 m 52 s (7012 s) Cntc/wc/ec)5717/5271/0 36.0%
"event3-1954" (): 1 h 54 m 19 s (6859 s) Cntc/wc/ec)5524/0/0 15.1%
"event1-1954" (): 1 h 53 m 15 s (6795 s) Cntc/wc/ec)5592/12/0 34.9%
"event0-1954" (): 1 h 53 m 11 s (6791 s) Cntc/wc/ec)5465/0/0 14.9%
"event2-1954" (): 1 h 53 m 10 s (6790 s) Cntc/wc/ec)31772/0/0 14.9%
"radio-interface" (): 7 m 38 s (458 s) Cntc/wc/ec)620/0/0 2.4%
"alarm" (): 5 m 33 s (333 s) Cntc/wc/ec)464/3/0 1.7%
"PowerManagerService" (): 2 m 42 s (162 s) Cntc/wc/ec)1042/0/0 0.8%
"event7-1954" (): 1 m 27 s (87 s) Cntc/wc/ec)6064/0/0 0.2%
"alarm_rtc" (): 1 m 14 s (74 s) Cntc/wc/ec)115/0/36 0.4%
"AudioOutLock" (): 36 s (36 s) Cntc/wc/ec)245/0/0 0.1%
"KeyEvents" (): 24 s (24 s) Cntc/wc/ec)31310/0/0 0.1%
"DPRAM_PWDOWN" (): 17 s (17 s) Cntc/wc/ec)12133/111/0 0.1%
"sync_system" (): 7 s (7 s) Cntc/wc/ec)44/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)5536/0/1 0.0%
"client-interface" (): (0 s) Cntc/wc/ec)6908/0/0 0.0%
"event8-1954" (): (0 s) Cntc/wc/ec)357981/0/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.gsf (): Wakeups: 77
Alarms: 4, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 19, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 29, Intent: com.google.android.intent.action.SEND_IDLE
com.android.providers.calendar (): Wakeups: 29
Alarms: 27, Intent: com.android.providers.calendar.intent.CalendarProvider2
Alarms: 1, Intent: com.android.providers.calendar.SCHEDULE_ALARM
Alarms: 1, Intent: android.intent.action.EVENT_REMINDER
com.google.android.apps.maps (): Wakeups: 25
android (): Wakeups: 22
Alarms: 758, Intent: android.intent.action.TIME_TICK
Alarms: 25, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 75, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 1, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
Alarms: 1, Intent: android.app.backup.intent.RUN
Alarms: 21, Intent: android.content.syncmanager.SYNC_ALARM
com.coremobility.app.vnotes (): Wakeups: 5
Alarms: 5, Intent: com.coremobility.app.vnotes.SERVICE_DOPROCESS
com.android.phone (): Wakeups: 5
Alarms: 5, Intent: com.android.internal.telephony.cdma-reconnect
com.swype.android.inputmethod (): Wakeups: 1
Any ideas as to why I am only getting 5hr and 24 minutes from a full charge? I have tried different modems and ROMS but nothing has worked. Thanks!

Screen shots would of done the job......
Turn off sync and you can use juice defender pro to help you get better battery
Sent from my SPH-D710 using Tapatalk 2

daniel4653 said:
Screen shots would of done the job......
Turn off sync and you can use juice defender pro to help you get better battery
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Horrible reply for xda, your post looks like a Yahoo answers reply. You didn't even read what he wrote.
To op, if you are not using your phone as your post says, you definitely are installing a rogue app as your phone was awake for over 3 hours. Have you tried wiping? Also, battery monitor, whatever that is, appears to be significantly keeping your phone awake. Finally, it appears from the info above your phone was not in airplane mode the whole time as you suggest.
Also, on ics you can view data usage on a per app basis in the settings. Post a screen cap of that screen.
Sent from my SPH-D710 using Tapatalk 2

Duplicate

BetterBatteryStats is designed to help only if you leave the phone on battery for a minimum of 2-3 hours (overnight is better) without using it at all. This will give you & us an accurate reading of what the phone is doing while it is supposed to be sleeping.

tdunham said:
BetterBatteryStats is designed to help only if you leave the phone on battery for a minimum of 2-3 hours (overnight is better) without using it at all. This will give you & us an accurate reading of what the phone is doing while it is supposed to be sleeping.
Click to expand...
Click to collapse
So just let the phone die if I leave it unplugged during the night? It is only lasting 6 hours remember.

sweatynipples said:
So just let the phone die if I leave it unplugged during the night? It is only lasting 6 hours remember.
Click to expand...
Click to collapse
Ok, sorry forgot. LOL
Well, from a full charge, let it sit for 2-3 hrs (I know, its tough) without touching it and post the log then.
Is this a brand new phone btw and are you giving the roms a chance to settle in for a couple/three days before judging battery life? The first day or two typically suck after flashing a new rom.
Edit: Oh, and being on ICS is definitely not going to help your battery situation. The GB rom is way more efficient. You may want to consider going back (the proper way, by odin EL26 stock kernel by Chris41G) and doing a fresh format and install.

Well, it seems that my issue with the battery drain is resolved. It appears that the phone was constantly waking up because of a glitch in the USB, making the phone repeatedly turn on and think it is in car mode. This glitch also prevented the phone from recognizing the USB every so often for charging. I took a q-tip and gently wiped down the connectors inside the port and it seems to have made a more secure connection. I now get 20+ hours on a full charge with limited use, and the phone is going into a deep sleep.

Why is my battery so bad?

I'm running a Custom JB TouchWiz ROM with stock kernel. Its only been 4 hours and I'm at 41% as I type this. What can I do to fix this issue? I'm using OEM battery
Sent from my SGH-I747 using xda app-developers app

Get better battery stats. That will show you anything that is holding wake locks and other battery drainers.
Sent from my SAMSUNG-SGH-I747 using xda premium

MrTenseJACOB said:
I'm running a Custom JB TouchWiz ROM with stock kernel. Its only been 4 hours and I'm at 41% as I type this. What can I do to fix this issue? I'm using OEM battery
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
From looking at your screen shots, it looks like you're losing signal for periods of time. Are you in a weak LTE area?

General Information
===================
BetterBatteryStats version: 1.12.0.0RC6
Creation Date: 2013-01-28 06:10:26
Statistic Type: Unplugged to Current
Since 7 h 31 m 36 s
VERSION.RELEASE: 4.1.2
BRAND: samsung
DEVICE: m0
MANUFACTURER: samsung
MODEL: GT-I9300
OS.VERSION: 3.0.31
BOOTLOADER: I9300XXBLH1
HARDWARE: smdk4x12
FINGERPRINT: samsung/m0xx/m0:4.1.2/JZO54K/I9300XXEMA1:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: se.infra
PRODUCT: m0xx
RADIO: I9300DXELK1
Rooted: true
============
Battery Info
============
Level lost [%]: 4 Bat.: 4% (98% to 94%) [0.5%/h]
Voltage lost [mV]: 81 (4264-4183) [10.8%/h]
===========
Other Usage
===========
Deep Sleep (): 7 h 15 m 26 s (26126 s) Ratio: 96.4%
Awake (): 16 m 9 s (969 s) Ratio: 3.6%
Screen On (): 38 s (38 s) Ratio: 0.1%
No Data Connection (): 7 h 31 m 36 s (27096 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 31 m 36 s (27096 s) Ratio: 100.0%
Screen dark (): 38 s (38 s) Ratio: 0.1%
=========
Wakelocks
=========
Genie (com.google.android.apps.genie.geniewidget.News & Weather): 2 m 21 s (141 s) Count:6 0.5%
AlarmManager (Android System): 31 s (31 s) Count:363 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 29 s (29 s) Count:10 0.1%
AudioOut_2 (1013): 11 s (11 s) Count:3 0.0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar Storage): 6 s (6 s) Count:20 0.0%
RILS (com.sec.phone.SecPhone): 4 s (4 s) Count:1 0.0%
ActivityManager-Launch (Android System): 2 s (2 s) Count:21 0.0%
FaceDetectionService (Android System): 1 s (1 s) Count:36 0.0%
AlarmManager (GO SMS Emoji Plugin): 1 s (1 s) Count:150 0.0%
AlarmManager (com.google.android.apps.maps.Maps): 1 s (1 s) Count:229 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 1 s (1 s) Count:23 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 1 s (1 s) Count:95 0.0%
Hi everyone.......is my phone behaving just fine?
Sent from my GT-I9300 using xda premium

To OP. Maybe try a different modem.
Sent from my SGH-I747 using Tapatalk 2

Did you just flash the ROM and have been using it for 4 hours? If so give it two power cycles ( just what I've read)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] Battery Drain with Samsung Galaxy S3

Hello everyone,
I bought a Samsung Galaxy S3 yesterday at company FIDO and right away I noticed problems with battery draining. I've been searching through forums and found out many people had the same problems. I'm not sure if i'm in the good forum but here is my problem: this is my first ever smartphone and I have noticed, in a few hours of use, that the battery would drop 1% every few minutes, even though I barely use it. I switched off all the battery-eating things (WIFI, GPS, Synchronisation,etc.), deleted apps I didnt need, turned down the screen at lowest brightness, restricted background data and stopped apps after each use. In the battery use section, Android System is at 42%, and screen 29%... I basically tried everything I saw on the forums but the battery is still going down quite quickly, and at some times it gets very hot. I also tried rebooting it and taking off the battery. Boy, I even did a factory reset but it still seems to be going down. I also heard about downloading loops problems but I don't know how to solve them. Shall I call Samsung ? I am thinking about changing to an Iphone if this problem persists, as I need a phone with good battery life for my job! Please help me, and if you need me to post screenshots, just ask.
Also, I deleted by mistake the Android OS ''app'' in the Settings/Application Manager/Running before doing the factory reset. It disappeared! How do I get it back?!!?!
Thanks
Louis

LouisLeonardo said:
Hello everyone,
I bought a Samsung Galaxy S3 yesterday at company FIDO and right away I noticed problems with battery draining. I've been searching through forums and found out many people had the same problems. I'm not sure if i'm in the good forum but here is my problem: this is my first ever smartphone and I have noticed, in a few hours of use, that the battery would drop 1% every few minutes, even though I barely use it. I switched off all the battery-eating things (WIFI, GPS, Synchronisation,etc.), deleted apps I didnt need, turned down the screen at lowest brightness, restricted background data and stopped apps after each use. In the battery use section, Android System is at 42%, and screen 29%... I basically tried everything I saw on the forums but the battery is still going down quite quickly, and at some times it gets very hot. I also tried rebooting it and taking off the battery. Boy, I even did a factory reset but it still seems to be going down. I also heard about downloading loops problems but I don't know how to solve them. Shall I call Samsung ? I am thinking about changing to an Iphone if this problem persists, as I need a phone with good battery life for my job! Please help me, and if you need me to post screenshots, just ask.
Also, I deleted by mistake the Android OS ''app'' in the Settings/Application Manager/Running before doing the factory reset. It disappeared! How do I get it back?!!?!
Thanks
Louis
Click to expand...
Click to collapse
Are you completely stock or are you running a custom ROM/Kernel?

Check out BetterBatteryStats. Make sure you read the 1st post there, and understand what you have to do to get a good dump. Enable root features, if your phone is rooted. Post in that thread & attach your dump file, and someone will help you analyze it.
The BBS dump file will show what processes are keeping your phone from going into deep sleep mode. Armed with that information, you can take appropriate action. If your phone is rooted, you'll have much more flexibility.

post-mortem said:
Check out BetterBatteryStats. Make sure you read the 1st post there, and understand what you have to do to get a good dump. Enable root features, if your phone is rooted. Post in that thread & attach your dump file, and someone will help you analyze it.
The BBS dump file will show what processes are keeping your phone from going into deep sleep mode. Armed with that information, you can take appropriate action. If your phone is rooted, you'll have much more flexibility.
Click to expand...
Click to collapse
Hello,
I have installed BBS and checked up how wakelocks work on this thread . However, I really am a newbie so I have no idea what rooted means, and since I'm still on warranty and do not want to risk bricking my phone, I prefer not to do it. However, I followed the instructions of different threads: for example, I basically turned all my sounds off, uninstalled useless apps, turned off syncing of pretty much all apps. I'm still not sure of how GPS works: I think I might have to use it (if i ever get lost somewhere), but I'm not sure if it should always been on. Same thing for WiFi.
Maybe without a rooted phone it's useless to share my dumpfile? What I did today was plugging it, let it charge fully, and used it right afterwards. If I understood well the instructions, I should've waited 1-4 hours to have a good dump. Next time I charge it, I will do so, and will come back to them. Thank you very much!!!

Isn't fido the same as rogers? I'm with rogers and my phone also had crazy battery drain, I couldn't do more than 16h even without using it, but was usually around 10h max. Sometimes I had 10%/h drain while the phone was in sleep.
I first compensated that battery drain with a ZeroLemon 7100mAh battery bought on Amazon (stock battery is 2100mAh) and I after decided to root my phone and change the ROM and kernel. I now get better battery life: around 60h (2days and 12h). I haven't tried my new setup with stock battery though. I saw a guy get 5days of battery life with the Zerolemon 7100mAh, link here: http://forum.xda-developers.com/showpost.php?p=43331093&postcount=458
I know you don't want to break your warranty but I think there's way to get back your phone to normal after you root it and flash custom ROMs.

GS3 dies in hours. betterb attery stats file is here
i realize this is for sprint but any help please
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.
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.EsProvider_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.contentprovider_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)

DarkFranX said:
Isn't fido the same as rogers? I'm with rogers and my phone also had crazy battery drain, I couldn't do more than 16h even without using it, but was usually around 10h max. Sometimes I had 10%/h drain while the phone was in sleep.
I first compensated that battery drain with a ZeroLemon 7100mAh battery bought on Amazon (stock battery is 2100mAh) and I after decided to root my phone and change the ROM and kernel. I now get better battery life: around 60h (2days and 12h). I haven't tried my new setup with stock battery though. I saw a guy get 5days of battery life with the Zerolemon 7100mAh, link here: http://forum.xda-developers.com/showpost.php?p=43331093&postcount=458
I know you don't want to break your warranty but I think there's way to get back your phone to normal after you root it and flash custom ROMs.
Click to expand...
Click to collapse
If the phone is running stock 4.3, rooting, flashing a custom recovery, or a custom ROM will trip the knox counter and void the warranty.
OP, did you check your battery usage on the day you got the phone? I find that battery life gets better as you continue to use the phone. I found this to be the case with many of the custom ROMs I have used over the years.

I see you use battery defender. This is pretty good to keep the WiFi and data to a level. I'm assuming your not rooted or cfw. Considering you said you don't even know what root is.
You can indeed root the phone and trick the flash counter to still be 0 but I doubt u wana risk a bricked phone. And that's another story.
What kind of keyboard do you use? I find the stock keyboards cause battery problems sometimes. There's also this tut that lists 15 ways to get ur battery up. au.ibtimes.com/articles/535287/20140121/15-ways-improve-battery-life-samsung-galaxy.htm#.UvZu2uqEjqA
Sent from my SAMSUNG-SGH-I747 using xda app-developers app