Related
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
I will PayPal $10 to the first person who can fix the following issue. I'm having major wakelock problems that are killing my battery, even when the phone isn't in use.
I've posted my BBS log in several places, but nobody ever responds. Looks like the biggest wakelocks are under kernel wakelock. I've changed kernels, roms, and reduced my apps significantly, but these wakelocks never go away.
I'm pasting the dump file and hoping someone will take me up on my $10 offer. Thanks!
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-05-17 16:53:57
Statistic Type: (3) Since Unplugged
Since 1 h 44 m 17 s
VERSION.RELEASE: 4.0.4
BRAND: google
DEVICE: toro
MANUFACTURER: Samsung
MODEL: Galaxy Nexus
BOOTLOADER: PRIMELA03
FINGERPRINT: google/mysid/toro:4.0.2/ICL53F/235179:user/release-keys
HARDWARE: tuna
ID: IMM76D
TAGS: test-keys
USER: das7982
PRODUCT: mysid
RADIO: I515.09 V.FC04 / I515.FC05
Rooted: true
===========
Other Usage
===========
Wifi On (): 1 h 44 m 17 s (6257 s) Ratio: 100.0%
Wifi Running (): 1 h 44 m 17 s (6257 s) Ratio: 100.0%
Deep Sleep (): 1 h 45 s (3645 s) Ratio: 57.9%
Awake (): 43 m 31 s (2611 s) Ratio: 41.7%
Screen On (): 30 m 14 s (1814 s) Ratio: 29.0%
No Data Connection (): 15 s (15 s) Ratio: 0.3%
No or Unknown Signal (): 15 s (15 s) Ratio: 0.3%
Phone On (): 12 s (12 s) Ratio: 0.2%
=========
Wakelocks
=========
*overflow* (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 m 3 s (183 s) Count:102 2.9%
ActivityManager-Launch (Android System): 1 m 31 s (91 s) Count:188 1.5%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 1 m 25 s (85 s) Count:60 1.4%
[email protected]/android_talk77e9ae9f765e (Google Services): 1 m 22 s (82 s) Count:7 1.3%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 m 21 s (81 s) Count:21 1.3%
SyncLoopWakeLock (Android System): 46 s (46 s) Count:769 0.7%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 43 s (43 s) Count:24 0.7%
FacebookService (com.facebook.katana.Facebook): 42 s (42 s) Count:19 0.7%
com.ebay.mobile (com.ebay.mobile.eBay): 38 s (38 s) Count:3 0.6%
AudioOut_1 (1013): 31 s (31 s) Count:7 0.5%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 18 s (18 s) Count:8 0.3%
RILJ (Phone): 15 s (15 s) Count:107 0.3%
sleep_broadcast (Android System): 13 s (13 s) Count:272 0.2%
NfcService (com.android.nfc.Nfc Service): 11 s (11 s) Count:14 0.2%
AlarmManager (Android System): 11 s (11 s) Count:573 0.2%
CDMA (Phone): 11 s (11 s) Count:108 0.2%
My Tag (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 10 s (10 s) Count:121 0.2%
GTALK_CONN (Google Services): 6 s (6 s) Count:348 0.1%
com.mufumbo.craigslist.notification.android.service.WakefulIntentService (com.mufumbo.craigslist.notification.android.CraigsNotifica): 5 s (5 s) Count:1 0.1%
NetworkLocationLocator (Google Services): 4 s (4 s) Count:38 0.1%
*vibrator* (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 4 s (4 s) Count:110 0.1%
VLService (com.hourdb.volumelocker.Volume Locker): 4 s (4 s) Count:2 0.1%
StartingAlertService (com.handcent.nextsms.Handcent SMS): 2 s (2 s) Count:7 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 2 s (2 s) Count:4 0.0%
BackgroundRequestService (com.facebook.katana.Facebook): 2 s (2 s) Count:51 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 2 s (2 s) Count:2 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:275 0.0%
SMSDispatcher (Phone): 1 s (1 s) Count:1 0.0%
StartingAlertService (com.android.mms.Messaging): 1 s (1 s) Count:1 0.0%
*sync*_com.android.contacts_Account {[email protected], type=com.google} (Google Services): 1 s (1 s) Count:22 0.0%
show keyguard (Android System): 1 s (1 s) Count:9 0.0%
*sync*_com.android.chrome_Account {[email protected], type=com.google} (com.android.chrome.Chrome Beta): 1 s (1 s) Count:35 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 8 m 35 s (515 s) Cntc/wc/ec)819/0/0 8.2%
"modem_usb_suspend_block" (): 3 m 27 s (207 s) Cntc/wc/ec)663/0/0 3.3%
"modem_usb_gpio_wake" (): 2 m 51 s (171 s) Cntc/wc/ec)634/71/634 2.7%
"wlan_rx_wake" (): 1 m 18 s (78 s) Cntc/wc/ec)180/0/181 1.2%
"alarm_rtc" (): 1 m 6 s (66 s) Cntc/wc/ec)117/0/30 1.1%
"radio-interface" (): 58 s (58 s) Cntc/wc/ec)69/0/0 0.9%
"musb_autosuspend_wake_lock" (): 27 s (27 s) Cntc/wc/ec)213/67/0 0.4%
"event2-178" (): 16 s (16 s) Cntc/wc/ec)267/0/0 0.3%
"alarm" (): 14 s (14 s) Cntc/wc/ec)326/54/0 0.2%
"wlan_wake" (): 4 s (4 s) Cntc/wc/ec)4986/10/0 0.1%
"nfc" (): 4 s (4 s) Cntc/wc/ec)29/0/29 0.1%
"vibrator" (): 4 s (4 s) Cntc/wc/ec)668/0/0 0.1%
"max17040-battery" (): 1 s (1 s) Cntc/wc/ec)92/0/0 0.0%
"twl6030 adc" (): (0 s) Cntc/wc/ec)2335/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)22051/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)635/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)34/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)253/0/0 0.0%
"gpio_input" (): (0 s) Cntc/wc/ec)19/5/0 -0.0%
"client-interface" (): (0 s) Cntc/wc/ec)170/0/0 0.0%
======================
Alarms (requires root)
======================
android (): Wakeups: 53
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 94, Intent: android.intent.action.TIME_TICK
Alarms: 4, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 10, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 13, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
Alarms: 39, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 1, Intent: com.android.server.WifiManager.action.START_SCAN
com.facebook.katana (): Wakeups: 44
Alarms: 0, Intent: Orca.KICK
Alarms: 5, Intent: Orca.KEEP_ALIVE
Alarms: 0, Intent: com.facebook.katana.service.42
Alarms: 0, Intent: com.facebook.katana.service.12
Alarms: 0, Intent: com.facebook.katana.service.11
Alarms: 1, Intent: com.facebook.katana.service.22
Alarms: 0, Intent: com.facebook.katana.service.27
Alarms: 1, Intent: com.facebook.katana.service.10
Alarms: 6, Intent: com.facebook.katana.service.8
Alarms: 1, Intent: com.facebook.katana.service.31
Alarms: 0, Intent: com.facebook.katana.service.5
Alarms: 0, Intent: com.facebook.katana.service.4
Alarms: 1, Intent: com.facebook.katana.service.6
Alarms: 7, Intent: com.facebook.katana.service.3
Alarms: 7, Intent: com.facebook.katana.service.2
com.android.phone (): Wakeups: 36
Alarms: 34, Intent: com.android.internal.telephony.gprs-data-stall
Alarms: 1, Intent: com.android.internal.telephony.gprs-reconnect.1
Alarms: 1, Intent: com.android.internal.telephony.gprs-reconnect.0
Alarms: 0, Intent: com.android.internal.telephony.cdma-reconnect
ccc71.bmw (): Wakeups: 26
com.google.android.gsf (): Wakeups: 17
Alarms: 6, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 8, Intent: com.google.android.intent.action.SEND_IDLE
com.sec.android.internal.ims (): Wakeups: 12
com.paulish.widgets.stocks (): Wakeups: 7
com.google.android.apps.maps (): Wakeups: 4
Alarms: 2, Intent: com.google.android.location.ALARM_WAKEUP_PASSIVE_COLLECTOR
Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_SENSOR_UPLOADER
Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_ACTIVE_COLLECTOR
com.nitrodesk.droid20.nitroid (): Wakeups: 3
com.gau.go.launcherex (): Wakeups: 2
Alarms: 2, Intent: com.jiubang.intent.action.ACTION_TIDY_DATA
Alarms: 0, Intent: com.jiubang.intent.action.AUTO_CHECK_UPDATE
Alarms: 0, Intent: com.jiubang.intent.action.SCAN_APPS
com.ebay.mobile (): Wakeups: 2
Alarms: 2, Intent: com.ebay.mobile.service.DO_NOTIF_TRACKING
Alarms: 2, Intent: com.ebay.mobile.service.POLL_SAVED_SEARCH
com.handcent.nextsms (): Wakeups: 1
com.mufumbo.craigslist.notification.android (): Wakeups: 1
Sent from my Galaxy Nexus using XDA
Stockmoose16 said:
I will PayPal $10 to the first person who can fix the following issue. I'm having major wakelock problems that are killing my battery, even when the phone isn't in use.
I've posted my BBS log in several places, but nobody ever responds. Looks like the biggest wakelocks are under kernel wakelock. I've changed kernels, roms, and reduced my apps significantly, but these wakelocks never go away.
I'm pasting the dump file and hoping someone will take me up on my $10 offer. Thanks!
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-05-17 16:53:57
Statistic Type: (3) Since Unplugged
Since 1 h 44 m 17 s
VERSION.RELEASE: 4.0.4
BRAND: google
DEVICE: toro
MANUFACTURER: Samsung
MODEL: Galaxy Nexus
BOOTLOADER: PRIMELA03
FINGERPRINT: google/mysid/toro:4.0.2/ICL53F/235179:user/release-keys
HARDWARE: tuna
ID: IMM76D
TAGS: test-keys
USER: das7982
PRODUCT: mysid
RADIO: I515.09 V.FC04 / I515.FC05
Rooted: true
===========
Other Usage
===========
Wifi On (): 1 h 44 m 17 s (6257 s) Ratio: 100.0%
Wifi Running (): 1 h 44 m 17 s (6257 s) Ratio: 100.0%
Deep Sleep (): 1 h 45 s (3645 s) Ratio: 57.9%
Awake (): 43 m 31 s (2611 s) Ratio: 41.7%
Screen On (): 30 m 14 s (1814 s) Ratio: 29.0%
No Data Connection (): 15 s (15 s) Ratio: 0.3%
No or Unknown Signal (): 15 s (15 s) Ratio: 0.3%
Phone On (): 12 s (12 s) Ratio: 0.2%
=========
Wakelocks
=========
*overflow* (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 m 3 s (183 s) Count:102 2.9%
ActivityManager-Launch (Android System): 1 m 31 s (91 s) Count:188 1.5%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 1 m 25 s (85 s) Count:60 1.4%
[email protected]/android_talk77e9ae9f765e (Google Services): 1 m 22 s (82 s) Count:7 1.3%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 m 21 s (81 s) Count:21 1.3%
SyncLoopWakeLock (Android System): 46 s (46 s) Count:769 0.7%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 43 s (43 s) Count:24 0.7%
FacebookService (com.facebook.katana.Facebook): 42 s (42 s) Count:19 0.7%
com.ebay.mobile (com.ebay.mobile.eBay): 38 s (38 s) Count:3 0.6%
AudioOut_1 (1013): 31 s (31 s) Count:7 0.5%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 18 s (18 s) Count:8 0.3%
RILJ (Phone): 15 s (15 s) Count:107 0.3%
sleep_broadcast (Android System): 13 s (13 s) Count:272 0.2%
NfcService (com.android.nfc.Nfc Service): 11 s (11 s) Count:14 0.2%
AlarmManager (Android System): 11 s (11 s) Count:573 0.2%
CDMA (Phone): 11 s (11 s) Count:108 0.2%
My Tag (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 10 s (10 s) Count:121 0.2%
GTALK_CONN (Google Services): 6 s (6 s) Count:348 0.1%
com.mufumbo.craigslist.notification.android.service.WakefulIntentService (com.mufumbo.craigslist.notification.android.CraigsNotifica): 5 s (5 s) Count:1 0.1%
NetworkLocationLocator (Google Services): 4 s (4 s) Count:38 0.1%
*vibrator* (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 4 s (4 s) Count:110 0.1%
VLService (com.hourdb.volumelocker.Volume Locker): 4 s (4 s) Count:2 0.1%
StartingAlertService (com.handcent.nextsms.Handcent SMS): 2 s (2 s) Count:7 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 2 s (2 s) Count:4 0.0%
BackgroundRequestService (com.facebook.katana.Facebook): 2 s (2 s) Count:51 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 2 s (2 s) Count:2 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:275 0.0%
SMSDispatcher (Phone): 1 s (1 s) Count:1 0.0%
StartingAlertService (com.android.mms.Messaging): 1 s (1 s) Count:1 0.0%
*sync*_com.android.contacts_Account {[email protected], type=com.google} (Google Services): 1 s (1 s) Count:22 0.0%
show keyguard (Android System): 1 s (1 s) Count:9 0.0%
*sync*_com.android.chrome_Account {[email protected], type=com.google} (com.android.chrome.Chrome Beta): 1 s (1 s) Count:35 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 8 m 35 s (515 s) Cntc/wc/ec)819/0/0 8.2%
"modem_usb_suspend_block" (): 3 m 27 s (207 s) Cntc/wc/ec)663/0/0 3.3%
"modem_usb_gpio_wake" (): 2 m 51 s (171 s) Cntc/wc/ec)634/71/634 2.7%
"wlan_rx_wake" (): 1 m 18 s (78 s) Cntc/wc/ec)180/0/181 1.2%
"alarm_rtc" (): 1 m 6 s (66 s) Cntc/wc/ec)117/0/30 1.1%
"radio-interface" (): 58 s (58 s) Cntc/wc/ec)69/0/0 0.9%
"musb_autosuspend_wake_lock" (): 27 s (27 s) Cntc/wc/ec)213/67/0 0.4%
"event2-178" (): 16 s (16 s) Cntc/wc/ec)267/0/0 0.3%
"alarm" (): 14 s (14 s) Cntc/wc/ec)326/54/0 0.2%
"wlan_wake" (): 4 s (4 s) Cntc/wc/ec)4986/10/0 0.1%
"nfc" (): 4 s (4 s) Cntc/wc/ec)29/0/29 0.1%
"vibrator" (): 4 s (4 s) Cntc/wc/ec)668/0/0 0.1%
"max17040-battery" (): 1 s (1 s) Cntc/wc/ec)92/0/0 0.0%
"twl6030 adc" (): (0 s) Cntc/wc/ec)2335/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)22051/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)635/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)34/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)253/0/0 0.0%
"gpio_input" (): (0 s) Cntc/wc/ec)19/5/0 -0.0%
"client-interface" (): (0 s) Cntc/wc/ec)170/0/0 0.0%
======================
Alarms (requires root)
======================
android (): Wakeups: 53
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 94, Intent: android.intent.action.TIME_TICK
Alarms: 4, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 10, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 13, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
Alarms: 39, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 1, Intent: com.android.server.WifiManager.action.START_SCAN
com.facebook.katana (): Wakeups: 44
Alarms: 0, Intent: Orca.KICK
Alarms: 5, Intent: Orca.KEEP_ALIVE
Alarms: 0, Intent: com.facebook.katana.service.42
Alarms: 0, Intent: com.facebook.katana.service.12
Alarms: 0, Intent: com.facebook.katana.service.11
Alarms: 1, Intent: com.facebook.katana.service.22
Alarms: 0, Intent: com.facebook.katana.service.27
Alarms: 1, Intent: com.facebook.katana.service.10
Alarms: 6, Intent: com.facebook.katana.service.8
Alarms: 1, Intent: com.facebook.katana.service.31
Alarms: 0, Intent: com.facebook.katana.service.5
Alarms: 0, Intent: com.facebook.katana.service.4
Alarms: 1, Intent: com.facebook.katana.service.6
Alarms: 7, Intent: com.facebook.katana.service.3
Alarms: 7, Intent: com.facebook.katana.service.2
com.android.phone (): Wakeups: 36
Alarms: 34, Intent: com.android.internal.telephony.gprs-data-stall
Alarms: 1, Intent: com.android.internal.telephony.gprs-reconnect.1
Alarms: 1, Intent: com.android.internal.telephony.gprs-reconnect.0
Alarms: 0, Intent: com.android.internal.telephony.cdma-reconnect
ccc71.bmw (): Wakeups: 26
com.google.android.gsf (): Wakeups: 17
Alarms: 6, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 8, Intent: com.google.android.intent.action.SEND_IDLE
com.sec.android.internal.ims (): Wakeups: 12
com.paulish.widgets.stocks (): Wakeups: 7
com.google.android.apps.maps (): Wakeups: 4
Alarms: 2, Intent: com.google.android.location.ALARM_WAKEUP_PASSIVE_COLLECTOR
Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_SENSOR_UPLOADER
Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_ACTIVE_COLLECTOR
com.nitrodesk.droid20.nitroid (): Wakeups: 3
com.gau.go.launcherex (): Wakeups: 2
Alarms: 2, Intent: com.jiubang.intent.action.ACTION_TIDY_DATA
Alarms: 0, Intent: com.jiubang.intent.action.AUTO_CHECK_UPDATE
Alarms: 0, Intent: com.jiubang.intent.action.SCAN_APPS
com.ebay.mobile (): Wakeups: 2
Alarms: 2, Intent: com.ebay.mobile.service.DO_NOTIF_TRACKING
Alarms: 2, Intent: com.ebay.mobile.service.POLL_SAVED_SEARCH
com.handcent.nextsms (): Wakeups: 1
com.mufumbo.craigslist.notification.android (): Wakeups: 1
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
looks like facebook is the biggest culprit, and that makes sense. after some recent facebook updates, many are complaining about this. personally, i removed facebook from my nexus s and galaxy nexus just because it began sucking my batteries dry without me ever opening the app. everything else looks fairly normal.
What do you call bad battery life? Having a quick glance, 43 mins awake with screen on for 30 of that and a large portion in deep sleep, seems OK, not much keeping it awake unnecessarily. That allows 14 odd mins for sync ect. I have great battery life but still have 21 kernel wakelocks.
What screen on time are you getting on one charge?
Someone cleverer then me will be along in a minute to shoot me down...
Sent from my Galaxy Nexus using XDA
killyouridols said:
What do you call bad battery life? Having a quick glance, 43 mins awake with screen on for 30 of that and a large portion in deep sleep, seems OK, not much keeping it awake unnecessarily. That allows 14 odd mins for sync ect. I have great battery life but still have 21 kernel wakelocks.
What screen on time are you getting on one charge?
Someone cleverer then me will be along in a minute to shoot me down...
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I get roughly one hour of screen time per charge, having previously averaged 2 hrs. The culprit is clearly the kernel wake locks like:
"modem_usb_suspend_block" (): 3 m 27 s (207 s) Cntc/wc/ec)663/0/0 3.3%
"modem_usb_gpio_wake" (): 2 m 51 s (171 s) Cntc/wc/ec)634/71/634 2.7%
I don't have usb tethering turned on, but these two items are consistently among the top kernel wake locks. Several users have complained about the same issue, but nobody has ever responded with a clear answer. I have tried nearly everything, from changing the ROM to changing the kernel, to eliminating apps. My battery actually dies as bad with the screen off as with it on.
How do I fix these wake locks and get my phone back on track.
turn off sync on facebook if you havent already or force it to never sync with contacts
simms22 said:
looks like facebook is the biggest culprit, and that makes sense. after some recent facebook updates, many are complaining about this. personally, i removed facebook from my nexus s and galaxy nexus just because it began sucking my batteries dry without me ever opening the app. everything else looks fairly normal.
Click to expand...
Click to collapse
How did you make that assumption? If you look under wakelocks, Facebook barely accounts for any of them.
Also, I started by deleting the facebook app, and my phone still experienced the same drain. It's got to be the USB lock under kernel causing the problem. But I have no idea what it is or how to fix it.
Zepius said:
turn off sync on facebook if you havent already or force it to never sync with contacts
Click to expand...
Click to collapse
Again, I started to troubleshoot this issue by erasing all data, including facebook. It's not the culprit, and that's why it shows up lower down the list under partial wakelocks.
I'm almost certain it has something to do with those usb wakelocks, even though i'm not tethering and have turned that function off.
simms22 said:
looks like facebook is the biggest culprit, and that makes sense. after some recent facebook updates, many are complaining about this. personally, i removed facebook from my nexus s and galaxy nexus just because it began sucking my batteries dry without me ever opening the app. everything else looks fairly normal.
Click to expand...
Click to collapse
14 minutes for syncing? That's pretty bad. And if you look at your BBS, do you see USB kernel locks that take up, on the average, 13-14 min per day, and there are multiples of them? If the answer is no, then I have an issue.
Have you tried to return to stock to see if the issue is still there?
By the looks of it, it's Facebook that is providing the majority of the wakelocks. The Facebook app has a history of waking the device up, so getting rid of it is a good thing. I'd recommend FriendCaster instead, or use the touch interface for Facebook in your phone browser.
Another possible culprit could be the eBay app you have as well, although I'd personally check the battery and wakelock status after a day without the facebook app installed.
Finally, I'd recommend changing the sync preferences. It looks like you have Gmail set to immediate notification of messages. Try reducing the time between checks. I find 30 minutes is usually ample for me, but feel free to set it slightly lower if you get more urgent emails.
Hope I helped.
EchoVelocity said:
By the looks of it, it's Facebook that is providing the majority of the wakelocks. The Facebook app has a history of waking the device up, so getting rid of it is a good thing. I'd recommend FriendCaster instead, or use the touch interface for Facebook in your phone browser.
Another possible culprit could be the eBay app you have as well, although I'd personally check the battery and wakelock status after a day without the facebook app installed.
Finally, I'd recommend changing the sync preferences. It looks like you have Gmail set to immediate notification of messages. Try reducing the time between checks. I find 30 minutes is usually ample for me, but feel free to set it slightly lower if you get more urgent emails.
Hope I helped.
Click to expand...
Click to collapse
I started off this process by deleting facebook and all the other apps you mentioned altogether. That doesn't change the fact that I have a couple of giant kernel locks that appear to have nothing to do with facebook or ebay. How do I get rid of those?!
have you checked all your account syncs? is one of them being hung up?
imnuts said:
Have you tried to return to stock to see if the issue is still there?
Click to expand...
Click to collapse
No, but I've changed kernels AND roms. No reason why stock would be any different, and it's just a hassle to go reload the ROM altogher.
Have you done a full factory reset and re-installed things and set them up without restoring data for them? Odds are that through flashing various ROMs and kernels, something got "stuck" or messed up to cause the issue. I have seen several users experience this with the DROID Charge, and fully wiping everything and setting it all back up without restoring via Titanium Backup or similar fixed the issue.
My suggestion would be to use the fastboot files, restore to fully stock, let the phone boot, then go back and reinstall your rom/kernel/recovery of choice, and setup everything without restoring. If it still happens, then I would try the same apps on stock (again, don't restore data), and see if it is still there. If it is, then I would say try to get a new phone as it could be hardware related.
imnuts said:
Have you done a full factory reset and re-installed things and set them up without restoring data for them? Odds are that through flashing various ROMs and kernels, something got "stuck" or messed up to cause the issue. I have seen several users experience this with the DROID Charge, and fully wiping everything and setting it all back up without restoring via Titanium Backup or similar fixed the issue.
My suggestion would be to use the fastboot files, restore to fully stock, let the phone boot, then go back and reinstall your rom/kernel/recovery of choice, and setup everything without restoring. If it still happens, then I would try the same apps on stock (again, don't restore data), and see if it is still there. If it is, then I would say try to get a new phone as it could be hardware related.
Click to expand...
Click to collapse
Is there a .zip file I can use to restore to rooted stock? I'm not near a computer that can load fastboot files via odin.
Stockmoose16 said:
Is there a .zip file I can use to restore to rooted stock? I'm not near a computer that can load fastboot files via odin.
Click to expand...
Click to collapse
You don't need Odin to flash factory images, just fastboot.
nodstuff said:
You don't need Odin to flash factory images, just fastboot.
Click to expand...
Click to collapse
Ok, went back to factory and am still seeing the same kernel wake locks. I still can't get a clear answer to my question: what are the following kernel wake locks:
Modem_usb_gpio_wake
Modem_usb_suspend_block
I see others posting dump files with these same culprits,but nobody can answer the simple question: what's causing the KWs?
Screen on time about 5 hours for me, with lots of texting and music playing. Wifi on for 3 hours too.
Sent from my Galaxy Nexus running AOKP+Franco on Tapatalk 2
theking_13 said:
Screen on time about 5 hours for me, with lots of texting and music playing. Wifi on for 3 hours too.
Sent from my Galaxy Nexus running AOKP+Franco on Tapatalk 2
Click to expand...
Click to collapse
What does that have to do with the question I asked?
Stockmoose16 said:
Ok, went back to factory and am still seeing the same kernel wake locks. I still can't get a clear answer to my question: what are the following kernel wake locks:
Modem_usb_gpio_wake
Modem_usb_suspend_block
I see others posting dump files with these same culprits,but nobody can answer the simple question: what's causing the KWs?
Click to expand...
Click to collapse
It sounds to me like those wakelocks are part of the kernels themselves and probably not possible to remove them. I'm not an expert by any means but USB seems to be pretty important. Also I was having problems recently so I unrooted/relocked my phone and put stock 4.0.2 back on it. then rooted again and it seemed to fix most of the problems I was facing. maybe you could try that and if all else fails, unvoid the warranty and take it back to the store and tell them to give you a new one. take that one home and see if it gives you the same problems.
I've been mentioning this for some time now, and I finally got around to getting a couple BBS logs to show.
The problem:
If I do not reboot my phone before letting it idle all night, I experience significantly higher battery drain than I would if I reboot it, then let it idle all night. I'll address testing variables in a moment.
Normal battery drain for me is 0.9-1.3% per hour after a night where I let it reboot then idle. 3-5% an hour is normal if I do not reboot it first (ie. Tapatalk, reddit, Chrome, then let it idle for the night). Unknown if there is a memory leak, although ROM Toolbox's task manager is reporting that there are no rogue apps or services open, and I Greenify everything that I don't want notifications from (all the apps I listed are Greenified). It does seem to lose ~100MB-200MB of RAM to nothingness over time. This is pretty normal for most computer systems, however.
The logs will show roughly the same wakelocking. Yet, +2% drain per hour. Whatever the problem is, BBS isn't detecting it. I am unsure what "voltage lost" under battery info signifies. The second log also includes more information that the first log didn't include. Didn't look through the BBS options
Variables:
My BBS logs will show that I'm pretty much always running the latest nightly. This has been happening for weeks, it's not a new problem.
I usually use a custom kernel. LK or Ktoons, depending on which one is more up to date. Like them both. Before you accuse the kernel of being the problem, understand that the stock CM kernel does this as well, but worse. Up to 7% an hour without a reboot with that one. and 2-3% an hour if it's rebooted before idling through the night. If this is a kernel problem, then it's also baked into the CM kernel.
Using Banks' unofficial gapps. This was happening with the signed 20130301 gapps, also. That's part of the reason I changed them.
Testing times vary a bit, but it's about as close as I can get to "the same".
Everything else is the same between the two tests. Wifi, distance to router, etc.
BBS Logs:
These were taken over two consecutive nights:
2013-06-06 - when phone is rebooted before idle:
Code:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-06-07 05:00:37
Statistic Type: Boot to Current
Since 3 h 56 m 53 s
VERSION.RELEASE: 4.2.2
BRAND: samsung
DEVICE: d2tmo
MANUFACTURER: samsung
MODEL: SGH-T999
OS.VERSION: 3.4.47-leanKernel-att_aosp_43-6.2.3-+
BOOTLOADER: T999UVDMD5
HARDWARE: qcom
FINGERPRINT: samsung/d2tmo/d2tmo:4.1.1/JRO03L/T999UVDLJA:user/release-keys
ID: JDQ39E
TAGS: test-keys
USER: jenkins
PRODUCT: d2tmo
RADIO: T999UVDMD5
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -4% (93% to 89%) [1.0%/h]
Voltage lost [mV]: (4133-4142) [-2.3%/h]
===========
Other Usage
===========
Deep Sleep (): 3 h 39 m 15 s (13155 s) Ratio: 92.3%
Awake (): 17 m 38 s (1058 s) Ratio: 7.4%
Screen On (): 37 s (37 s) Ratio: 0.3%
Wifi On (): 3 h 56 m 54 s (14214 s) Ratio: 100.0%
Wifi Running (): 3 h 56 m 54 s (14214 s) Ratio: 100.0%
No Data Connection (): 3 h 55 m 49 s (14149 s) Ratio: 99.5%
No or Unknown Signal (): 3 h 55 m 49 s (14149 s) Ratio: 99.5%
Moderate Signal (): 20 s (20 s) Ratio: 0.1%
Good Signal (): 44 s (44 s) Ratio: 0.3%
Screen dark (): 37 s (37 s) Ratio: 0.3%
=========
Wakelocks
=========
RILJ (Phone): 58 s (58 s) Count:24 0.4%
AlarmManager (Android System): 33 s (33 s) Count:341 0.2%
AudioOut_2 (1013): 15 s (15 s) Count:4 0.1%
MediaScannerService (Media): 8 s (8 s) Count:1 0.1%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 7 s (7 s) Count:3 0.1%
AlarmClock (com.android.deskclock.Clock): 4 s (4 s) Count:20 0.0%
*backup* (Android System): 4 s (4 s) Count:77 0.0%
*vibrator* (com.android.deskclock.Clock): 3 s (3 s) Count:7 0.0%
Cleaner (com.oasisfeng.greenify.Greenify): 3 s (3 s) Count:2 0.0%
E (net.dinglisch.android.taskerm.Tasker): 3 s (3 s) Count:50 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 3 s (3 s) Count:5 0.0%
*sync*_gmail-ls_Account {name=xxxxxxxxxxxxxxxx, type=com.google} (com.google.android.gm.Gmail): 3 s (3 s) Count:2 0.0%
ActivityManager-Launch (Android System): 2 s (2 s) Count:32 0.0%
WeatherUpdateService (com.cyanogenmod.lockclock.cLock): 1 s (1 s) Count:8 0.0%
babel_rtcs (com.google.android.talk.Hangouts): 1 s (1 s) Count:7 0.0%
*vibrator* (Android System): 1 s (1 s) Count:55 0.0%
Icing (Google Services): 1 s (1 s) Count:8 0.0%
ReminderService (mikado.bizcalpro.Business Calendar): 1 s (1 s) Count:12 0.0%
GTALK_CONN (Google Services): 1 s (1 s) Count:93 0.0%
================
Kernel Wakelocks
================
"sec-battery-monitor" (): 8 m 53 s (533 s) Cnt:(c/wc/ec)1051/0/0 3.7%
"mmc1_detect" (): 5 m 40 s (340 s) Cnt:(c/wc/ec)1071/0/1 2.4%
"wlan_rx_wake" (): 3 m 24 s (204 s) Cnt:(c/wc/ec)882/0/882 1.4%
"wlan_wake" (): 2 m 45 s (165 s) Cnt:(c/wc/ec)3091/946/0 1.2%
"PowerManagerService" (): 2 m 13 s (133 s) Cnt:(c/wc/ec)368/0/0 0.9%
"wlan_ctrl_wake" (): 1 m 51 s (111 s) Cnt:(c/wc/ec)476/0/476 0.8%
"wlan_wd_wake" (): 1 m 24 s (84 s) Cnt:(c/wc/ec)1306/0/0 0.6%
"alarm_rtc" (): 26 s (26 s) Cnt:(c/wc/ec)111/69/1 0.2%
"sec-battery-measure" (): 18 s (18 s) Cnt:(c/wc/ec)1055/0/0 0.1%
"alarm" (): 10 s (10 s) Cnt:(c/wc/ec)353/0/0 0.1%
"radio-interface" (): 7 s (7 s) Cnt:(c/wc/ec)20/0/0 0.0%
"bam_dmux_wakelock" (): 3 s (3 s) Cnt:(c/wc/ec)4/0/0 0.0%
"power-supply" (): 2 s (2 s) Cnt:(c/wc/ec)1052/0/0 0.0%
"KeyEvents" (): 1 s (1 s) Cnt:(c/wc/ec)2363/0/0 0.0%
"rmt_storage_1089601432" (): 1 s (1 s) Cnt:(c/wc/ec)5/0/0 0.0%
"PowerManagerService.Broadcasts" (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
"rmt_storage_1089601256" (): (0 s) Cnt:(c/wc/ec)5/0/0 0.0%
"msm_ipc_read00000001:00000001" (): (0 s) Cnt:(c/wc/ec)15/0/0 0.0%
"smdcntl0" (): (0 s) Cnt:(c/wc/ec)282/3/0 0.0%
"qcril" (): (0 s) Cnt:(c/wc/ec)126/0/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)1071/0/1 0.0%
"qmuxd_port_wl_0" (): (0 s) Cnt:(c/wc/ec)289/0/0 0.0%
"smdcntl1" (): (0 s) Cnt:(c/wc/ec)90/0/0 0.0%
"qmuxd_port_wl_1" (): (0 s) Cnt:(c/wc/ec)91/0/0 0.0%
======================
Alarms (requires root)
======================
Boot event was not registered yet, it will at next reboot (): Wakeups: 0
======================
Network (requires root)
======================
0 (Wifi) (0): 149.0 KBytes 40.0%
10056 (Wifi) (com.android.vending.Google Play Store): 106.0 KBytes 28.6%
10111 (Wifi) (com.google.android.apps.googlevoice.Google Voice): 39.0 KBytes 10.6%
10068 (Wifi) (com.google.android.talk.Hangouts): 27.0 KBytes 7.5%
10036 (Wifi) (Google Services): 20.0 KBytes 5.5%
10089 (Wifi) (com.google.android.gm.Gmail): 11.0 KBytes 3.1%
10028 (Wifi) (com.cyanogenmod.lockclock.cLock): 9.0 KBytes 2.5%
1000 (Wifi) (Android System): 3.0 KBytes 1.0%
10100 (Wifi) (com.nuance.swype.dtc.Swype + Dragon): 3.0 KBytes 1.0%
0 (Mobile) (0): 972.0 Bytes 0.3%
10106 (Wifi) (com.lsdroid.cerberus.Cerberus): 300.0 Bytes 0.1%
==========
CPU States
==========
384 MHz (): 16 m 40 s 7.0%
486 MHz (): 9 s 0.1%
594 MHz (): 4 s 0.0%
702 MHz (): 3 s 0.0%
810 MHz (): 16 s 0.1%
918 MHz (): 0.0%
1.03 GHz (): 0.0%
1.13 GHz (): 6 s 0.0%
1.24 GHz (): 1 s 0.0%
1.35 GHz (): 1 s 0.0%
1.46 GHz (): 1 s 0.0%
1.51 GHz (): 12 s 0.1%
Deep Sleep (): 3 h 39 m 15 s 92.4%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 33 s (Wl: 2 elements; KWl: 0elements; NetS: 5 elements; Alrm: null; Proc: 0 elements; Oth: 5 elements; CPU: 12 elements)
ref_current: Reference ref_current created 3 h 57 m 27 s (Wl: 19 elements; KWl: 24elements; NetS: 12 elements; Alrm: 12 elements; Proc: 6 elements; Oth: 10 elements; CPU: 13 elements)
2013-06-07 - when phone is not rebooted before idle:
Code:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-06-08 05:00:55
Statistic Type: Custom to Current
Since 4 h 15 m 17 s
VERSION.RELEASE: 4.2.2
BRAND: samsung
DEVICE: d2tmo
MANUFACTURER: samsung
MODEL: SGH-T999
OS.VERSION: 3.4.47-leanKernel-att_aosp_43-6.2.3-+
BOOTLOADER: T999UVDMD5
HARDWARE: qcom
FINGERPRINT: samsung/d2tmo/d2tmo:4.1.1/JRO03L/T999UVDLJA:user/release-keys
ID: JDQ39E
TAGS: test-keys
USER: jenkins
PRODUCT: d2tmo
RADIO: T999UVDMD5
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -13% (97% to 84%) [3.1%/h]
Voltage lost [mV]: (4133-3967) [39.1%/h]
===========
Other Usage
===========
Deep Sleep (): 3 h 59 m 43 s (14383 s) Ratio: 93.9%
Awake (): 15 m 34 s (934 s) Ratio: 6.1%
Screen On (): 50 s (50 s) Ratio: 0.3%
Wifi On (): 4 h 15 m 17 s (15317 s) Ratio: 100.0%
Wifi Running (): 4 h 15 m 17 s (15317 s) Ratio: 100.0%
No Data Connection (): 4 h 15 m 17 s (15317 s) Ratio: 100.0%
No or Unknown Signal (): 4 h 15 m 17 s (15317 s) Ratio: 100.0%
Screen dark (): 50 s (50 s) Ratio: 0.3%
=========
Wakelocks
=========
AlarmManager (Android System): 48 s (48 s) Count:454 0.3%
AudioOut_2 (1013): 18 s (18 s) Count:3 0.1%
AlarmClock (com.android.deskclock.Clock): 9 s (9 s) Count:12 0.1%
*vibrator* (com.android.deskclock.Clock): 8 s (8 s) Count:1 0.1%
*sync*_gmail-ls_Account {name=xxxxxxxxxxxxxxx, type=com.google} (com.google.android.gm.Gmail): 7 s (7 s) Count:2 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:20 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 s (1 s) Count:4 0.0%
Icing (Google Services): 1 s (1 s) Count:9 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 1 s (1 s) Count:1 0.0%
WeatherUpdateService (com.cyanogenmod.lockclock.cLock): 1 s (1 s) Count:5 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:133 0.0%
ReminderService (mikado.bizcalpro.Business Calendar): 1 s (1 s) Count:7 0.0%
AlarmManager (net.dinglisch.android.taskerm.Tasker): 1 s (1 s) Count:76 0.0%
M (net.dinglisch.android.taskerm.Tasker): 1 s (1 s) Count:48 0.0%
================
Kernel Wakelocks
================
"sec-battery-monitor" (): 7 m 59 s (479 s) Cnt:(c/wc/ec)943/0/0 3.1%
"mmc1_detect" (): 5 m 11 s (311 s) Cnt:(c/wc/ec)961/0/0 2.0%
"wlan_rx_wake" (): 3 m 22 s (202 s) Cnt:(c/wc/ec)874/0/874 1.3%
"wlan_wake" (): 2 m 18 s (138 s) Cnt:(c/wc/ec)2069/805/0 0.9%
"PowerManagerService" (): 1 m 16 s (76 s) Cnt:(c/wc/ec)372/0/0 0.5%
"wlan_wd_wake" (): 1 m 1 s (61 s) Cnt:(c/wc/ec)984/0/0 0.4%
"alarm_rtc" (): 39 s (39 s) Cnt:(c/wc/ec)136/92/1 0.3%
"alarm" (): 20 s (20 s) Cnt:(c/wc/ec)371/0/0 0.1%
"sec-battery-measure" (): 20 s (20 s) Cnt:(c/wc/ec)943/0/0 0.1%
"wlan_ctrl_wake" (): 12 s (12 s) Cnt:(c/wc/ec)56/0/56 0.1%
"power-supply" (): 7 s (7 s) Cnt:(c/wc/ec)925/0/0 -0.0%
"radio-interface" (): 5 s (5 s) Cnt:(c/wc/ec)8/0/0 0.0%
"KeyEvents" (): 1 s (1 s) Cnt:(c/wc/ec)2047/0/0 0.0%
"rmt_storage_1104248552" (): 1 s (1 s) Cnt:(c/wc/ec)3/0/0 0.0%
"msm_ipc_read00000001:00000001" (): 1 s (1 s) Cnt:(c/wc/ec)6/0/0 0.0%
"rmt_storage_1104248728" (): 1 s (1 s) Cnt:(c/wc/ec)3/0/0 0.0%
"smdcntl0" (): (0 s) Cnt:(c/wc/ec)89/4/0 0.0%
"PowerManagerService.Broadcasts" (): (0 s) Cnt:(c/wc/ec)2/0/0 0.0%
"smdcntl1" (): (0 s) Cnt:(c/wc/ec)7/0/0 0.0%
"qcril" (): (0 s) Cnt:(c/wc/ec)46/0/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)961/0/0 0.0%
"qmuxd_port_wl_0" (): (0 s) Cnt:(c/wc/ec)93/0/0 0.0%
"qmuxd_port_wl_1" (): (0 s) Cnt:(c/wc/ec)10/0/0 0.0%
"ipc_rtr_smd_rpcrpy_cntl" (): (0 s) Cnt:(c/wc/ec)7/6/0 0.0%
=========
Processes
=========
kworker/u:0 (0): Uid: 0 Sys: 4 s (4 s) Us: (0 s) Starts: 0
kworker/u:2 (0): Uid: 0 Sys: 3 s (3 s) Us: (0 s) Starts: 0
kworker/u:3 (0): Uid: 0 Sys: 2 s (2 s) Us: (0 s) Starts: 0
kworker/u:1 (0): Uid: 0 Sys: 2 s (2 s) Us: (0 s) Starts: 0
mediaserver (1013): Uid: 1013 Sys: 1 s (1 s) Us: (0 s) Starts: 0
dhd_dpc (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
kworker/0:1 (0): Uid: 0 Sys: 1 s (1 s) Us: (0 s) Starts: 0
mpdecision (0): Uid: 0 Sys: (0 s) Us: (0 s) Starts: 0
surfaceflinger (Android System): Uid: 1000 Sys: (0 s) Us: (0 s) Starts: 0
com.asksven.betterbatterystats (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10075 Sys: (0 s) Us: (0 s) Starts: 0
======================
Alarms (requires root)
======================
com.google.android.gsf (): Wakeups: 26
Alarms: 16, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 9, Intent: {com.google.android.gsf
Alarms: 1, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 0, Intent: com.google.android.intent.action.GTALK_RECONNECT
net.dinglisch.android.taskerm (): Wakeups: 26
Alarms: 25, Intent: net.dinglisch.android.tasker.ANOFFCHECKORUM
Alarms: 1, Intent: net.dinglisch.android.tasker.ALARUM
android (): Wakeups: 13
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 0, Intent: com.android.server.WifiManager.action.START_SCAN
Alarms: 5, Intent: android.appwidget.action.APPWIDGET_UPDATE
Alarms: 4, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 4, Intent: android.app.backup.intent.RUN
Alarms: 0, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 0, Intent: com.android.server.action.UPDATE_TWILIGHT_STATE
com.android.providers.calendar (): Wakeups: 6
Alarms: 6, Intent: com.android.providers.calendar.intent.CalendarProvider2
com.cyanogenmod.lockclock (): Wakeups: 4
Alarms: 4, Intent: {com.cyanogenmod.lockclock
com.android.deskclock (): Wakeups: 1
Alarms: 1, Intent: com.android.deskclock.ALARM_ALERT
com.google.android.gms (): Wakeups: 1
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE
======================
Network (requires root)
======================
0 (Wifi) (0): 152.0 KBytes 67.7%
10089 (Wifi) (com.google.android.gm.Gmail): 53.0 KBytes 23.8%
10028 (Wifi) (com.cyanogenmod.lockclock.cLock): 9.0 KBytes 4.1%
10100 (Wifi) (com.nuance.swype.dtc.Swype + Dragon): 6.0 KBytes 2.8%
10036 (Wifi) (Google Services): 3.0 KBytes 1.7%
10079 (Wifi) (com.dropbox.android.Dropbox): 52.0 Bytes 0.0%
==========
CPU States
==========
384 MHz (): 14 m 56 s 5.8%
486 MHz (): 8 s 0.1%
594 MHz (): 2 s 0.0%
702 MHz (): 0.0%
810 MHz (): 7 s 0.1%
918 MHz (): 0.0%
1.03 GHz (): 0.0%
1.13 GHz (): 7 s 0.1%
1.24 GHz (): 1 s 0.0%
1.35 GHz (): 1 s 0.0%
1.46 GHz (): 0.0%
1.51 GHz (): 7 s 0.0%
Deep Sleep (): 3 h 59 m 43 s 93.9%
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
com.android.phone (com.android.phone.TelephonyDebugService)
Active since: 21 s
Last activity: 22 s
Crash count:0
net.dinglisch.android.taskerm (net.dinglisch.android.taskerm.MonitorService)
Active since: 31 s
Last activity: 4 h 9 m 33 s
Crash count:0
com.google.android.apps.googlevoice (com.google.android.apps.googlevoice.UpdateService)
Active since: 6 h 1 m 23 s
Last activity: 3 h 51 m 54 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pbap.BluetoothPbapService)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.android.location.fused (com.android.location.fused.FusedLocationService)
Active since: 22 s
Last activity: 22 s
Crash count:0
com.android.smspush (com.android.smspush.WapPushManager)
Active since: 21 s
Last activity: 21 s
Crash count:0
com.android.phone (com.android.phone.NetworkQueryService)
Active since: 7 h 18 m 27 s
Last activity: 2 h 54 m 46 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pan.PanService)
Active since: 16 s
Last activity: 16 s
Crash count:0
mikado.bizcalpro (mikado.bizcalpro.WidgetProvider$UpdateService)
Active since: 24 s
Last activity: 4 h 9 m 24 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkServiceProxy)
Active since: 32 s
Last activity: 3 h 10 m 46 s
Crash count:0
com.nuance.swype.dtc:SwypeConnect (com.nuance.swype.connect.ConnectClient)
Active since: 13 h 5 m 50 s
Last activity: 4 h 4 m 16 s
Crash count:0
com.google.process.location (com.google.android.location.NetworkLocationService)
Active since: 22 s
Last activity: 22 s
Crash count:0
com.google.android.talk (com.google.android.videochat.VideoChatService)
Active since: 1 h 38 m 48 s
Last activity: 1 h 38 m 48 s
Crash count:0
com.google.android.apps.googlevoice (com.google.android.apps.googlevoice.CallLogService)
Active since: 30 s
Last activity: 3 h 51 m 54 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.a2dp.A2dpService)
Active since: 24 s
Last activity: 24 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 20 s
Last activity: 20 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.hid.HidService)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.bel.android.dspmanager (com.bel.android.dspmanager.service.HeadsetService)
Active since: 27 s
Last activity: 4 h 4 m
Crash count:0
com.nuance.swype.dtc (com.nuance.swype.input.IME)
Active since: 13 h 5 m 49 s
Last activity: 3 h 50 m 50 s
Crash count:0
com.google.process.location (com.google.android.location.internal.server.NetworkLocationService)
Active since: 23 s
Last activity: 3 h 40 m 45 s
Crash count:0
com.teslacoilsw.launcher (com.teslacoilsw.launcher.NovaService)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.dropbox.android (com.dropbox.android.service.CameraUploadService)
Active since: 29 s
Last activity: 4 h 3 m 21 s
Crash count:0
com.google.process.location (com.google.android.location.GeocodeService)
Active since: 22 s
Last activity: 22 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 27 s
Last activity: 27 s
Crash count:0
com.android.nfc:handover (com.android.nfc.handover.HandoverService)
Active since: 21 s
Last activity: 21 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 20 s
Last activity: 20 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 21 s
Last activity: 21 s
Crash count:0
com.oasisfeng.greenify:service (com.oasisfeng.greenify.CleanerService)
Active since: 29 s
Last activity: 4 h 2 m 58 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 32 s
Last activity: 3 h 38 m 4 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.hfp.HeadsetService)
Active since: 22 s
Last activity: 22 s
Crash count:0
com.android.phone (com.android.phone.BluetoothPhoneService)
Active since: 22 s
Last activity: 22 s
Crash count:0
==================
Reference overview
==================
ref_boot: Reference ref_boot created 31 s (Wl: 0 elements; KWl: 0elements; NetS: 5 elements; Alrm: null; Proc: 0 elements; Oth: 0 elements; CPU: 12 elements)
ref_unplugged: Reference ref_unplugged created 14 h 7 m 11 s (Wl: 0 elements; KWl: 30elements; NetS: 32 elements; Alrm: 11 elements; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
ref_charged: Reference ref_charged created 14 h 7 m 12 s (Wl: 0 elements; KWl: 30elements; NetS: 32 elements; Alrm: 11 elements; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
ref_custom: Reference ref_custom created 14 h 14 m 29 s (Wl: 5 elements; KWl: 30elements; NetS: 32 elements; Alrm: 11 elements; Proc: 3 elements; Oth: 9 elements; CPU: 13 elements)
ref_current: Reference ref_current created 18 h 29 m 47 s (Wl: 17 elements; KWl: 30elements; NetS: 32 elements; Alrm: 13 elements; Proc: 11 elements; Oth: 9 elements; CPU: 13 elements)
Possible solutions:
I am unsure when this problem started. Which is what makes it hard to troubleshoot. The BBS logs look pretty similar to me.
Clean flash/factory reset? Tried it.
Bug in the ROM?
Bug in the kernel (stock, LK, Ktoons)?
Bug in the MD5 firmware?
Bad battery? Don't see how this one is possible.
Bug in an app that I'm using? Don't see how this one is possible.
I'm starting to suspect the MD5 firmware could be the culprit. More testing is needed. If you are having this issue, here is the LJC firmware for you to downgrade: http://db.tt/agQRnclf.
You have certainly done some pretty good investigative work on this so far! I don't know if I can be much help, as I never noticed this on my device when I was running MD5.
I have noticed something which may be related here on the forums though. Shortly after the MD5 custom roms started being released, a number of people complained about battery life (and signal if they flashed the modem). This only seemed to be reported by people who "updated" by flashing only the custom roms.
I vaguely remember at least two people who were reporting the issue, and then flashed the full firmware update. Shortly after they said they were now getting better battery life than before the MD5 release.
It kind of seems like it may have something to do with how the kernel, modem, system, etc all work together. So if you only have part of the MD5 update, you will actually take a hit on your power consumption, but if you fully updated, you will notice an improvement.
This can be further backed up by the numerous people who have reported better battery life after just updating via OTA or the full firmware.
I do not know if any of that info can help you at all, but thought Id share, just in case it can.
Also, I am getting close to being done with my need to be running the T999L rom I built and was planning to flash back to MD5 soon. If there is anything you would like me to check or do first to help out, let me know.
Otherwise good luck and Ill try to chime in whenever I have any thoughts on the subject.
I flashed the full MD5 package with Odin from the start. I do recall those having battery problems when they upgraded to stock MD5. But I am not active enough in the TouchWiz department to keep up with it, so thanks for reminding me, and the extra information.
You may be right about the "how everything works together" bit. I know for a fact Verizon users can't use their newest firmware on AOSP (until today - there was a commit for it), because it breaks the camera.
Not sure if there is anything you can do to help, unfortunately. But I appreciate the offer.
Battery life overnight was 0.9% an hour on LJC. The best I consistently saw on LK was 1.3%/hour on MD5. Saw 98.4% deep sleep while on mobile data this afternoon for over 2.5 hours (0.5%/hour). Testing again tonight. Will not be able to fully confirm this as the solution for probably a few more days (testing MD5 again, etc.).
I think the LJC firmware is the solution to this issue currently. Will keep post up to date with new information as it arises.
Just curious, as I know you don't usually run touchwiz based roms, when you refer to running MD5 and LJC are you referring to just the underlying firmware and still running PA for your rom?
The reason I ask is that the improvement you saw on LJC would lead me to believe that this may actually be related to how the firmware works. If so, this would mean that if someone wants to run on the MD5 firmware, they will have similar issues unless they are also using an MD5 based kernel. (Starting to sound like Sammy specifically built this kernel to work with this specific RPM).
If this is true, then I wonder if the CM/AOSP kernel devs could find the related code in the kernel source and somehow incorporate it into theirs. (I know it may not be possible, but you never know. And im betting this would be easier than attempting to reverse engineer the rest of the fw). Or perhaps a mixed MD5/LJC firmware setup could help.
I expect you probably thought about all of this already, but figured I'd post my thoughts in case it could end up helping. You never know!
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
Just curious, as I know you don't usually run touchwiz based roms, when you refer to running MD5 and LJC are you referring to just the underlying firmware and still running PA for your rom?
The reason I ask is that the improvement you saw on LJC would lead me to believe that this may actually be related to how the firmware works. If so, this would mean that if someone wants to run on the MD5 firmware, they will have similar issues unless they are also using an MD5 based kernel. (Starting to sound like Sammy specifically built this kernel to work with this specific RPM).
If this is true, then I wonder if the CM/AOSP kernel devs could find the related code in the kernel source and somehow incorporate it into theirs. (I know it may not be possible, but you never know. And im betting this would be easier than attempting to reverse engineer the rest of the fw). Or perhaps a mixed MD5/LJC firmware setup could help.
I expect you probably thought about all of this already, but figured I'd post my thoughts in case it could end up helping. You never know!
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I'm referring to aboot/non-hlos/rpm/tz/sbl2/sbl3. I'm not sure which one is causing issues with battery life on AOSP, but one of them is, I'm nearly certain of it. Since returning to LJC, I've seen better deep sleep and consistent battery consumption. The MD5 modem was a little better for me, but not worth all that hassle.
I do suspect it's got something to do with an incompatibility (probably in the kernel). They fixed the camera+tz issues for Verizon users a couple days ago (their cameras weren't working with their new firmware).
What I'm confused about, is why more people haven't been complaining?
My guess is the oroblem lies with the kernel+rpm (resource & power management).
TZ deals more with drm/allshare/media hub stuff.
The others are bootloader related (and sys apps related?).
These others could be contributors, but I'm not sure.
Anyway, not sure why others aren't complaining. Was it really noticable to you? (Obviously it was to you, but would it be to general users?)
Maybe they are blaming batteries since its a year old now. And I'm sure others believe its rom/kernel, but choose to just deal with it.
Just guessing.
Sent from my SGH-T999L using xda premium
Appreciate all that's been done to fix this. I duno if I'm actually facing this issue too because things for me didn't get better after flashing the "solution "
Nice work Aerowinder! This is awesome. I just flashed the LJC firmware after running MD5 for a couple days, I'd like to see if my battery life improves. Maybe I'll post up some BBS screenshots and you guys can help me track down any rogue apps or wakelocks that are causing me issues.
Just out of curiosity have you noticed an immense increase in temperatures on your phone as well? I made a thread about the issue in General Discussion but it seems that MD5 doesn't get along with non-TW ROMs. I'm not the only one to report very high temperatures when the phone is not doing anything (and I also did a "full" ODIN to get MD5 as well) - downgrading my modem to LI8 dropped my idle temperature from pushing 110 to less than 80F! There's something worth investigating here for sure.
I saw your post about that, as well as others', but I have not seen this particular issue. My phone is on my belt most of the day, but it's never been hot when I've grabbed for it. Did rebooting do anything? Or did you change basebands right away?
I've been running MD5 firmware on my phone for a couple days, and it is acting much better than it was when I flashed LJC to fix these problems, though I did note some weird drainage while idling yesterday. It stopped on it's own. Hot booted once while idle (per system uptime counter), and Chrome froze once. Chrome usually behaves nowadays. And my phone hasn't rebooted on it's own for quite some time. Poweramp sometimes crashes.
The problem must have been in CM (or it's kernel-there was an LK update a couple days ago). I figured as much, since based on the release cycle of these updates, I'm guessing that they are pretty thoroughly tested.
The fact of the matter is, I still do not trust MD5. And I know from experience, just because something is working right now, doesn't mean the next nightly won't break it again Bluetooth is a terrific example. Also MMS. And now I'm paranoid about overheating.
I will be using LJC firmware for the foreseeable future. MD5 modem performs better, but not worth the risk.
I actually had rebooted the phone twice because of the heat issues since flashing early this morning so yeah, it definitely was the baseband. I didn't do anything but download LI8, flash it, then I wiped cache and dalvik. Instant difference. I watched the temperature go down as soon as the phone came back up. It rapidly dropped down to 84 and I just checked and its sleeping at 76 right now.
It's starting to sound like we either need to run 100% MD5, or run LJC if using a different Rom/kernel/modem.
Sent from my SGH-T999L using xda premium
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
EtherealRemnant said:
Just out of curiosity have you noticed an immense increase in temperatures on your phone as well? I made a thread about the issue in General Discussion but it seems that MD5 doesn't get along with non-TW ROMs. I'm not the only one to report very high temperatures when the phone is not doing anything (and I also did a "full" ODIN to get MD5 as well) - downgrading my modem to LI8 dropped my idle temperature from pushing 110 to less than 80F! There's something worth investigating here for sure.
Click to expand...
Click to collapse
So were you totally stock MD5? Or were you running a different rom?
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
It's starting to sound like we either need to run 100% MD5, or run LJC if using a different Rom/kernel/modem.
Sent from my SGH-T999L using xda premium
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
So were you totally stock MD5? Or were you running a different rom?
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I ran the root66 MD5 for awhile and then went to Universe S4 which has the MD5 stock kernel... Didn't have heat or battery life issues with either. Did a full wipe (system, cache, data, dalvik) three times in TWRP and then installed LiquidSmooth 2.7. Let it sit for 20 minutes, rebooted and set everything up, went to pick the phone up a bit later because something finished in Tapped Out and felt how hot it was so I checked the battery temp in GSam... thought maybe it was a fluke so I restarted the phone but it did it again this morning and then the highest temp was when I was at the mall today which prompted me to just shut the thing off til I got home.
Turned it back on when I got home, it went right back up to 99 while I was downloading UVDLI8, rebooted to recovery, flashed LI8, wiped cache/dalvik and rebooted and watched the temperature go down with the screen on - its now sleeping at around 74 and hasn't hit 100 under full load even.
I'd say its a baseband issue for sure since there were no other variables to take into account.
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
I have a P5210 running this ROM: http://forum.xda-developers.com/showthread.php?t=2590713 Pimpdroid for Tab 3 10.1
Prior to that ROM, on a different one I was averaging 6 hours screen on time with power saving mode active. I only use my tablet for browsing the internet, Skype calls and emails. I do not use CPU intensive programmes, and most of the game my Tab is on 800mhz according to BetterBatteryStats. I have my screen brightness on about 15-20%.
That said, I still cannot figure out why I am losing 63% battery for a little over 2.5 hours screen time. This means that for a full charge, I will only get 4 hours 10 minutes of screen on time. Other users have said they get 8-10 hours, Samsung states 10 hours...what am I doing wrong?
BetterBatteryStats Log:
Code:
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2014-04-11 19:22:46
Statistic Type: Boot to Current
Since 8 h 16 m 28 s
VERSION.RELEASE: 4.2.2
BRAND: samsung
DEVICE: santos10wifi
MANUFACTURER: samsung
MODEL: GT-P5210
OS.VERSION: 3.4.34-850131
BOOTLOADER: P5210XXUAMFA
HARDWARE: santos10wifi
FINGERPRINT: samsung/santos10wifiue/santos10wifi:4.2.2/JDQ39/P5210UEUAMI8:user/release-keys
ID: JDQ39
TAGS: release-keys
USER: se.infra
PRODUCT: santos10wifiue
RADIO:
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -40% (77% to 37%) [4.8%/h]
Voltage lost [mV]: (3933-3673) [31.4%/h]
===========
Other Usage
===========
Deep Sleep (): 3 h 51 m 49 s (13909 s) Ratio: 46.7%
Awake (): 4 h 24 m 40 s (15880 s) Ratio: 53.3%
Screen On (): 2 h 5 m 47 s (7547 s) Ratio: 25.3%
Wifi On (): 8 h 16 m 29 s (29789 s) Ratio: 100.0%
Wifi Running (): 8 h 16 m 29 s (29789 s) Ratio: 100.0%
No Data Connection (): 8 h 16 m 29 s (29789 s) Ratio: 100.0%
No or Unknown Signal (): 8 h 16 m 29 s (29789 s) Ratio: 100.0%
Screen dark (): 30 s (30 s) Ratio: 0.1%
Screen dimmed (): 2 h 5 m 16 s (7516 s) Ratio: 25.2%
=========
Wakelocks
=========
AudioOut_2 (1013): 35 m 19 s (2119 s) Count:15 7.1%
NlpWakeLock (Google Services): 9 m 15 s (555 s) Count:1025 1.9%
ActivityManager-Launch (Android System): 6 m 35 s (395 s) Count:410 1.3%
NlpCollectorWakeLock (Google Services): 6 m 29 s (389 s) Count:2211 1.3%
DownloadManager (Media): 1 m 20 s (80 s) Count:4 0.3%
DHCP (Android System): 35 s (35 s) Count:594 0.1%
AlarmManager (Android System): 34 s (34 s) Count:1221 0.1%
AlarmManager (Google Services): 28 s (28 s) Count:3162 0.1%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 28 s (28 s) Count:1081 0.1%
UlrDispatchingService (Google Services): 25 s (25 s) Count:1516 0.1%
NetworkLocationLocator (Google Services): 24 s (24 s) Count:1511 0.1%
Icing (Google Services): 23 s (23 s) Count:1574 0.1%
WakefulIntentService[GCoreUlr-LocationReportingService] (Google Services): 17 s (17 s) Count:1033 0.1%
*backup* (Android System): 13 s (13 s) Count:645 0.0%
*sync*_gmail-ls_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.gm.Gmail): 11 s (11 s) Count:9 0.0%
GTALK_CONN (Google Services): 11 s (11 s) Count:2690 0.0%
NetworkStats (Android System): 9 s (9 s) Count:268 0.0%
AlarmManager (com.facebook.katana.Facebook): 8 s (8 s) Count:274 0.0%
LightsService (Android System): 6 s (6 s) Count:526 0.0%
MQTT (com.facebook.orca.Messenger): 6 s (6 s) Count:158 0.0%
AudioOut_3 (1013): 5 s (5 s) Count:4 0.0%
GOOGLE_C2DM (Google Services): 4 s (4 s) Count:2276 0.0%
SamsungPhoneWindowManager.mBroadcastWakeLock (Android System): 4 s (4 s) Count:537 0.0%
MQTT (com.facebook.katana.Facebook): 4 s (4 s) Count:74 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:8 0.0%
MediaScannerService (Media): 3 s (3 s) Count:0 0.0%
AlarmManager (com.google.android.talk.Hangouts): 3 s (3 s) Count:15 0.0%
*sync*_com.google.android.apps.docs_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.apps.docs.Drive): 3 s (3 s) Count:3 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 3 s (3 s) Count:3 0.0%
SCREEN_FROZEN (Android System): 3 s (3 s) Count:605 0.0%
AlarmManager (com.facebook.orca.Messenger): 3 s (3 s) Count:225 0.0%
show keyguard (Android System): 3 s (3 s) Count:14 0.0%
*backup* (com.google.android.googlequicksearchbox.Google Search): 2 s (2 s) Count:7 0.0%
com.joelapenna.foursquared.app.WakefulintentService.Static (com.quoord.tapatalkxda.activity.XDA): 2 s (2 s) Count:1 0.0%
GCoreFlp (Google Services): 2 s (2 s) Count:1965 0.0%
DocsSyncAdapter (com.google.android.apps.docs.Drive): 2 s (2 s) Count:1 0.0%
*sync*_com.google.android.ears.heard.EarsContentProvider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.ears.Sound Search for Google Play): 2 s (2 s) Count:4 0.0%
ActivityManager-Sleep (Android System): 2 s (2 s) Count:1252 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 1 s (1 s) Count:4 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:2295 0.0%
AlarmManager (com.viber.voip.Viber): 1 s (1 s) Count:48 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1371 0.0%
AlarmManager (com.quoord.tapatalkxda.activity.XDA): 1 s (1 s) Count:2 0.0%
AlarmManager (com.android.chrome.Chrome): 1 s (1 s) Count:116 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
======================
Alarms (requires root)
======================
com.google.android.gms (): Wakeups: 385
Alarms: 186, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION
Alarms: 183, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR
Alarms: 9, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 0, Intent: {com.google.android.gms
Alarms: 2, Intent: com.google.android.location.reporting.ACTION_UPDATE_WORLD
Alarms: 1, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVE_COLLECTOR
Alarms: 1, Intent: com.google.android.gms.recovery.WAKEUP
Alarms: 1, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_CACHE_UPDATER
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_CONTENT_PROVIDER
Alarms: 1, Intent: {com.google.android.gms
com.facebook.katana (): Wakeups: 199
Alarms: 174, Intent: com.facebook.push.mqtt.KeepaliveManager.ACTION_INEXACT_ALARM.com.facebook.katana
Alarms: 0, Intent: JewelCountFetcher.INITIATE_BACKGROUND_FETCH
Alarms: 12, Intent: com.facebook.analytics.service.AnalyticsEventUploader.ACTION_ALARM
Alarms: 13, Intent: com.facebook.common.executors.WakingExecutorService.ACTION_ALARM.com.facebook.katana
Alarms: 0, Intent: {com.facebook.katana
Alarms: 0, Intent: com.facebook.orca.database.ACTION_ALARM
com.google.android.gsf (): Wakeups: 75
Alarms: 35, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 9, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 16, Intent: {com.google.android.gsf
Alarms: 15, Intent: com.google.android.intent.action.MCS_HEARTBEAT
com.facebook.orca (): Wakeups: 67
Alarms: 47, Intent: com.facebook.push.mqtt.t.ACTION_INEXACT_ALARM.com.facebook.orca
Alarms: 11, Intent: com.facebook.analytics.service.b.ACTION_ALARM
Alarms: 9, Intent: com.facebook.common.executors.bi.ACTION_ALARM.com.facebook.orca
Alarms: 0, Intent: com.facebook.orca.database.ACTION_ALARM
android (): Wakeups: 49
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 10, Intent: com.android.internal.policy.impl.Keyguard.LANDSCAPE_WAKE_TIME_LIMIT_EXPIRED
Alarms: 19, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 9, Intent: android.net.wifi.DHCP_RENEW
Alarms: 4, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 7, Intent: android.app.backup.intent.RUN
com.viber.voip (): Wakeups: 48
Alarms: 48, Intent: com.viber.voip.action.KEEP_ALIVE_RECEIVE
com.google.android.talk (): Wakeups: 8
Alarms: 2, Intent: com.google.android.apps.babel.UPDATE_NOTIFICATION
Alarms: 5, Intent: com.google.android.apps.babel.CLEANUP_DB
Alarms: 1, Intent: com.google.android.apps.babel.RENEW_ACCOUNT_REGISTRATION
com.android.vending (): Wakeups: 5
Alarms: 4, Intent: {com.android.vending
Alarms: 1, Intent: {com.android.vending
com.google.android.location (): Wakeups: 2
Alarms: 1, Intent: com.google.android.location.nlp.ALARM_WAKEUP_LOCATOR
Alarms: 1, Intent: com.google.android.location.nlp.ALARM_WAKEUP_CACHE_UPDATER
com.andrew.apollo (): Wakeups: 1
Alarms: 1, Intent: com.andrew.apollo.shutdown
com.sirma.mobile.bible.android (): Wakeups: 1
Alarms: 1, Intent: com.youversion.mobile.android.ACTION_TELEMETRY_END_SESSION
com.quoord.tapatalkxda.activity (): Wakeups: 1
Alarms: 1, Intent: {com.quoord.tapatalkxda.activity
com.android.providers.calendar (): Wakeups: 1
Alarms: 1, Intent: com.android.providers.calendar.intent.CalendarProvider2
com.sec.esdk.elm (): Wakeups: 1
Alarms: 1, Intent: com.sec.esdk.elm.service.ACTIVATION_DEACTIVATION_RETRY_INTENT
======================
Network (requires root)
======================
10132 (Wifi) (com.google.android.youtube.YouTube): 1.0 GBytes 91.6%
10059 (Wifi) (com.android.vending.Google Play Store): 70.0 MBytes 3.4%
10145 (Wifi) (com.futuremark.dmandroid.application.3DMark): 48.0 MBytes 2.3%
10133 (Wifi) (com.phyora.apps.reddit_now.Reddit Now): 37.0 MBytes 1.8%
10123 (Wifi) (com.sirma.mobile.bible.android.Bible): 4.0 MBytes 0.2%
0 (Wifi) (0): 2.0 MBytes 0.1%
10121 (Wifi) (com.touchtype.swiftkey.SwiftKey): 2.0 MBytes 0.1%
10104 (Wifi) (com.android.chrome.Chrome): 1.0 MBytes 0.1%
10124 (Wifi) (com.facebook.katana.Facebook): 1.0 MBytes 0.1%
10134 (Wifi) (com.quoord.tapatalkxda.activity.XDA): 1.0 MBytes 0.0%
10146 (Wifi) (com.facebook.orca.Messenger): 970.0 KBytes 0.0%
10008 (Wifi) (Google Services): 684.0 KBytes 0.0%
10016 (Wifi) (com.google.android.apps.docs.Drive): 94.0 KBytes 0.0%
10028 (Wifi) (com.google.android.gm.Gmail): 65.0 KBytes 0.0%
10140 (Wifi) (com.skype.raider.Skype): 58.0 KBytes 0.0%
10143 (Wifi) (com.viber.voip.Viber): 52.0 KBytes 0.0%
10029 (Wifi) (com.google.android.syncadapters.calendar.Google Calendar Sync): 38.0 KBytes 0.0%
10074 (Wifi) (com.sec.android.gallery3d.Gallery): 34.0 KBytes 0.0%
10106 (Wifi) (com.google.android.ears.Sound Search for Google Play): 18.0 KBytes 0.0%
10092 (Wifi) (com.google.android.googlequicksearchbox.Google Search): 16.0 KBytes 0.0%
10049 (Wifi) (com.google.android.music.Google Play Music): 12.0 KBytes 0.0%
10105 (Wifi) (org.adblockplus.android.Adblock Plus): 10.0 KBytes 0.0%
1000 (Wifi) (Android System): 9.0 KBytes 0.0%
1014 (Wifi) (1014): 7.0 KBytes 0.0%
1013 (Wifi) (1013): 5.0 KBytes 0.0%
10034 (Wifi) (com.google.android.talk.Hangouts): 5.0 KBytes 0.0%
10017 (Wifi) (Media): 184.0 Bytes 0.0%
==========
CPU States
==========
1.6 GHz (): 20 m 52 s 4.2%
1.33 GHz (): 10 m 46 s 2.2%
933 MHz (): 9 m 33 s 1.9%
800 MHz (): 3 h 43 m 27 s 45.0%
Deep Sleep (): 3 h 51 m 49 s 46.7%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 2 h 43 m 51 s (Wl: 7 elements; KWl: 0elements; NetS: 30 elements; Alrm: 0 elements; Proc: 15 elements; Oth: 8 elements; CPU: 5 elements)
ref_current: Reference ref_current created 11 h 20 s (Wl: 46 elements; KWl: 0elements; NetS: 37 elements; Alrm: 14 elements; Proc: 104 elements; Oth: 9 elements; CPU: 5 elements)
gsrac3r said:
I have a P5210 running this ROM: http://forum.xda-developers.com/showthread.php?t=2590713 Pimpdroid for Tab 3 10.1
Prior to that ROM, on a different one I was averaging 6 hours screen on time with power saving mode active. I only use my tablet for browsing the internet, Skype calls and emails. I do not use CPU intensive programmes, and most of the game my Tab is on 800mhz according to BetterBatteryStats. I have my screen brightness on about 15-20%.
That said, I still cannot figure out why I am losing 63% battery for a little over 2.5 hours screen time. This means that for a full charge, I will only get 4 hours 10 minutes of screen on time. Other users have said they get 8-10 hours, Samsung states 10 hours...what am I doing wrong?
Hi;
I also experienced high cpu use with this rom (v2.50) on my tab 10.1. With no apps running and sitting idle, both cpu's were running at 60% ALL the time. I tried the v2.40 version and it did not have this problem. (As also the stock rom rooted).
This is too bad, as I really liked the 2.5 version of this rom.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
jonobee61 said:
Hi;
I also experienced high cpu use with this rom (v2.50) on my tab 10.1. With no apps running and sitting idle, both cpu's were running at 60% ALL the time. I tried the v2.40 version and it did not have this problem. (As also the stock rom rooted).
This is too bad, as I really liked the 2.5 version of this rom.
Click to expand...
Click to collapse
What I don't understand is, according to BetterBatteryStats, I am running on 800mhz the vast majority of the time. I have power saving mode activated. I don't see how it is using so much battery!
How many hours of screen on time do you get on version 2.40?
gsrac3r said:
What I don't understand is, according to BetterBatteryStats, I am running on 800mhz the vast majority of the time. I have power saving mode activated. I don't see how it is using so much battery!
How many hours of screen on time do you get on version 2.40?
Click to expand...
Click to collapse
Unfortunately, I have gone back to stock rom. (If you stay mostly at 800mhz, then I couldn't even guess why your battery is being sucked dry. Doesn't make sense.)
I can go days before having to charge my t3.
One thing that does use the juice, is WiFi, and adventure/highly graphical games. But still not as bad as my Coby 7" 7024. (< 2hrs)
I wish I knew why PD 2.5 uses a constant 60% CPU. Nobody else seems to have this problem, so I guess it is something to do with my tablet only!
John
jonobee61 said:
Unfortunately, I have gone back to stock rom. (If you stay mostly at 800mhz, then I couldn't even guess why your battery is being sucked dry. Doesn't make sense.)
I can go days before having to charge my t3.
One thing that does use the juice, is WiFi, and adventure/highly graphical games. But still not as bad as my Coby 7" 7024. (< 2hrs)
I wish I knew why PD 2.5 uses a constant 60% CPU. Nobody else seems to have this problem, so I guess it is something to do with my tablet only!
John
Click to expand...
Click to collapse
I had issues with apps not opening on PD 2.5 so was using 2.4 instead. I didn't have the CPU issue you described, just a large battery drain.
How do you find stock compared to a custom ROM? If it gives me the best battery life, I will have to flash back to it.
I too can go days without having to charge my tab 3 10.1 it all just depends on how much screen on time I have on the tablet. I would like at least 7 hours of screen on time from 100-0% battery.
gsrac3r said:
How do you find stock compared to a custom ROM? If it gives me the best battery life, I will have to flash back to it.
Click to expand...
Click to collapse
I only went back to stock because of the high cpu use of PD 2.5. I want to use PD 2.5! If I ever figure out why it uses so much cpu even when idle, then I'll re-flash it back in.
The stock uses very little cpu at idle. I never turn off my GT3. If I charge the tablet to 100% at night, the next morning, it is still at 100%, not turned off but in standby mode. I am impressed.
John
It is highly possible that there is an open app within the rom that is requiring a lot of energy to run. Even though one cannot see it, it could be a bug that was not caught by the developer. Of all the apps on my tab, the GPS Chart Plotting program uses the most power. Constantly updating my position on a nautical chart and keeping the GPS receiver active. I have never tested to see how long it will last, but I can say that for the few minutes I have it on to get a fix I see the power level drop.
jonobee61 said:
I only went back to stock because of the high cpu use of PD 2.5. I want to use PD 2.5! If I ever figure out why it uses so much cpu even when idle, then I'll re-flash it back in.
The stock uses very little cpu at idle. I never turn off my GT3. If I charge the tablet to 100% at night, the next morning, it is still at 100%, not turned off but in standby mode. I am impressed.
John
Click to expand...
Click to collapse
I flashed back to stock using Restl3ss's flashable zip (ie: not the Odin file) with the stock p2510 rom but many apps do not open. Things like Facebook, messenger, 2048...it is seemingly random and very annoying. So now I am back on Grevious 4 and suffering many wake locks and poor battery life :/ I can't seem to win!
Sent from my GT-P5210 using xda app-developers app
Battery drainage
I own a "SGT-P5210, that Ijust bought last week and my battery goes down in about 2 to 4 hours of use, internet, playing card games, "ect;". I also have a "Pipo max m9 10.1 tablet and that one has a quard core I play with it the same way and I can go for about "two days without charge, their is something wrong with 'samsung's battery in this tablet, I can charge it but it just goes down so fast.