Related
Let me start off by saying, at the moment, my battery is fantastic. Right now im over 9 hours off the charger and im only down 20%. (from 95 to 75%) (first image attached) (betterbatterystats dump at bottom)
Yesterday the same thing - after almost 5 hours only down 13% and for the day i was 21 hours on battery and down 55%. (screens attached)
I have been using android since i got my captivate a few years ago. I have struggled with inexplicable battery problems ever since.
I know which apps are good and bad, and i really only use the most necessary apps, but regardless of what is installed or what isnt, my battery seems to just completely tank sometimes.
The weird thing is that i had these problems with my last phone - which was an ATT sgs2 - running AOKP. Before i swicthed to my Gnex a few weeks ago, it was giving my absolutely awful battery life. It wouldnt last 12 hours with minimal use. So when i switched to the Gnex, i thought my problems would be solved. But even with that, i had the same battery life - 12 hours with minimal use - mostly idle.
Now randomly the other day the battery just starts being awesome again. this is the kind of battery life i expect, and i know these phones are capable of when working properly. At the very least i know my phones shouldn't be draining 8% when idle - should be more like 1 or 2 percent - like it is now.
Im absolutely dumbfounded why this happens, and my only thing that i think might be it is ATT somehow. Maybe its an MMS thats trying to some in and just cant or something? I can only guess.
What im doing though is posting these screens now, and my bbs dump so you can see what my phone does when its behaving like it should. When it tanks again (and i know it will), ill post screens and another bbs dump. Please help me make sense of the dump, because i really have no idea what any of the information means.
My only request is to please try not to just assume its something - that i defintely know it is NOT. For example (oh your wifi is on - wifi is a killer, etc, when i can clearly see wifi is NOT the problem)
Im trying to find FACTS about why this is happening to me, so please help me get to the bottom of this. Thanks!
BBS dump:
===================
General Information
===================
BetterBatteryStats version: 1.9.0.0
Creation Date: 2012-07-31 00:46:28
Statistic Type: (3) Since Unplugged
Since 9 h 20 m 49 s
VERSION.RELEASE: 4.1.1
BRAND: google
DEVICE: maguro
MANUFACTURER: samsung
MODEL: Galaxy Nexus
OS.VERSION: 3.0.31-g6fb96c9
BOOTLOADER: PRIMELC03
HARDWARE: tuna
FINGERPRINT: google/takju/maguro:4.1.1/JRO03C/398337:user/release-keys
ID: JRO03C
TAGS: release-keys
USER: android-build
PRODUCT: takju
RADIO: I9250XXLF1
Rooted: false
============
Battery Info
============
Level lost [%]: 74
Voltage lost [mV]: 3896
===========
Other Usage
===========
Wifi On (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Wifi Running (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Bluetooth On (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Awake (): 2 h 20 s (7220 s) Ratio: 21.5%
No Data Connection (): 59 m 37 s (3577 s) Ratio: 10.6%
No or Unknown Signal (): 59 m 37 s (3577 s) Ratio: 10.6%
Screen On (): 36 m 8 s (2168 s) Ratio: 6.4%
Good Signal (): 4 m 36 s (276 s) Ratio: 0.8%
=========
Wakelocks
=========
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 15 m 41 s (941 s) Count:163 2.8%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 11 m 35 s (695 s) Count:1286 2.1%
AudioOut_2 (1013): 7 m 20 s (440 s) Count:127 1.3%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 4 m (240 s) Count:4589 0.7%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 2 m 44 s (164 s) Count:165 0.5%
Sidekick_TrafficIntentService_onHandleIntent (com.google.android.googlequicksearchbox.Google Search): 2 m 24 s (144 s) Count:97 0.4%
[email protected]/android_talk5eb0a0d6167e (Google Services): 2 m 6 s (126 s) Count:215 0.4%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 4 s (124 s) Count:44 0.4%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 1 m 44 s (104 s) Count:153 0.3%
NLP PendingIntent client in com.google.android.googlequicksearchbox (com.google.android.apps.maps.Maps): 1 m 25 s (85 s) Count:725 0.3%
NetworkLocationSensorUploader (com.google.android.apps.maps.Maps): 1 m 14 s (74 s) Count:5 0.2%
AlarmManager (Android System): 1 m 2 s (62 s) Count:1569 0.2%
NetworkLocationLocator (Google Services): 60 s (60 s) Count:205 0.2%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 58 s (58 s) Count:2081 0.2%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 44 s (44 s) Count:33 0.1%
DownloadManager (Media): 44 s (44 s) Count:3 0.1%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 37 s (37 s) Count:2820 0.1%
SMSDispatcher (Phone): 36 s (36 s) Count:19 0.1%
LocationReportingService (com.google.android.apps.maps.Maps): 31 s (31 s) Count:6129 0.1%
RILJ (Phone): 31 s (31 s) Count:2756 0.1%
ActivityManager-Launch (Android System): 27 s (27 s) Count:499 0.1%
*backup* (Android System): 26 s (26 s) Count:831 0.1%
LocationPrivacyService (com.google.android.apps.maps.Maps): 25 s (25 s) Count:13 0.1%
*sync*_com.google.android.apps.currents_Account {[email protected], type=com.google} (com.google.android.apps.currents.Currents): 25 s (25 s) Count:7 0.1%
NfcService (com.android.nfc.Nfc Service): 22 s (22 s) Count:47 0.1%
LocationManagerService (Android System): 18 s (18 s) Count:416 0.1%
MMS Connectivity (com.android.mms.Messaging): 15 s (15 s) Count:8 0.0%
sleep_broadcast (Android System): 15 s (15 s) Count:759 0.0%
AlarmManager (com.levelup.beautifulwidgets.Beautiful Widgets): 12 s (12 s) Count:571 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 10 s (10 s) Count:10 0.0%
DropboxCpuOnlyWakeLock (com.dropbox.android.Dropbox): 10 s (10 s) Count:3 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 9 s (9 s) Count:15 0.0%
LocationReceiverService (com.google.android.apps.maps.Maps): 9 s (9 s) Count:3611 0.0%
GpsLocationProvider (Android System): 9 s (9 s) Count:625 0.0%
ActivityManager-Sleep (Android System): 8 s (8 s) Count:1610 0.0%
StartingAlertService (com.android.mms.Messaging): 7 s (7 s) Count:54 0.0%
AlarmManager (com.google.android.apps.maps.Maps): 7 s (7 s) Count:6119 0.0%
MMS PushReceiver (com.android.mms.Messaging): 6 s (6 s) Count:4 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 6 s (6 s) Count:2071 0.0%
show keyguard (Android System): 6 s (6 s) Count:39 0.0%
*sync*_com.google.android.music.MusicContent_Account {[email protected], type=com.google} (com.google.android.music.Google Play Music): 4 s (4 s) Count:2 0.0%
s (com.google.android.apps.maps.Maps): 4 s (4 s) Count:2143 0.0%
AudioOut_3 (1013): 3 s (3 s) Count:10 0.0%
ConnectivityService (Android System): 3 s (3 s) Count:1571 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 3 s (3 s) Count:5156 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:607 0.0%
SCREEN_FROZEN (Android System): 2 s (2 s) Count:813 0.0%
NetworkStats (Android System): 2 s (2 s) Count:101 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:362 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:801 0.0%
*sync*_com.google.android.apps.magazines_Account {[email protected], type=com.google} (com.google.android.apps.magazines.Google Play Magazines): 1 s (1 s) Count:3 0.0%
AudioIn_3B9 (1013): 1 s (1 s) Count:3 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1793 0.0%
*sync*_com.android.browser_Account {[email protected], type=com.google} (Google Services): 1 s (1 s) Count:45 0.0%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 1 s (1 s) Count:135 0.0%
AudioIn_3BB (1013): 1 s (1 s) Count:7 0.0%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cntc/wc/ec)1/1/1 100.0%
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
======================
Network (requires root)
======================
==========
CPU States
==========
1 kHz (): ---%
lourivellini said:
Please help me make sense of the dump, because i really have no idea what any of the information means.
BBS dump:
===================
General Information
===================
BetterBatteryStats version: 1.9.0.0
Creation Date: 2012-07-31 00:46:28
Statistic Type: (3) Since Unplugged
Since 9 h 20 m 49 s
VERSION.RELEASE: 4.1.1
BRAND: google
DEVICE: maguro
MANUFACTURER: samsung
MODEL: Galaxy Nexus
OS.VERSION: 3.0.31-g6fb96c9
BOOTLOADER: PRIMELC03
HARDWARE: tuna
FINGERPRINT: google/takju/maguro:4.1.1/JRO03C/398337:user/release-keys
ID: JRO03C
TAGS: release-keys
USER: android-build
PRODUCT: takju
RADIO: I9250XXLF1
Rooted: false
============
Battery Info
============
Level lost [%]: 74
Voltage lost [mV]: 3896
Click to expand...
Click to collapse
General information. Not really a whole lot more to say, unless you wanted to know what some of the specific lines mean.
lourivellini said:
===========
Other Usage
===========
Wifi On (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Wifi Running (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Bluetooth On (): 9 h 20 m 49 s (33649 s) Ratio: 100.0%
Awake (): 2 h 20 s (7220 s) Ratio: 21.5%
No Data Connection (): 59 m 37 s (3577 s) Ratio: 10.6%
No or Unknown Signal (): 59 m 37 s (3577 s) Ratio: 10.6%
Screen On (): 36 m 8 s (2168 s) Ratio: 6.4%
Good Signal (): 4 m 36 s (276 s) Ratio: 0.8%
Click to expand...
Click to collapse
Also fairly self-explanatory. Wifi and Bluetooth were on for the entire 9h 20m duration. The phone was "awake" (active in some capacity) for 2 hours, and the screen was on for 36 minutes. You did, however, spend almost an hour without signal, which can hurt battery.
lourivellini said:
=========
Wakelocks
=========
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 15 m 41 s (941 s) Count:163 2.8%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 11 m 35 s (695 s) Count:1286 2.1%
AudioOut_2 (1013): 7 m 20 s (440 s) Count:127 1.3%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 4 m (240 s) Count:4589 0.7%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 2 m 44 s (164 s) Count:165 0.5%
Sidekick_TrafficIntentService_onHandleIntent (com.google.android.googlequicksearchbox.Google Search): 2 m 24 s (144 s) Count:97 0.4%
GTALK_ASYNC_CONN_<<REDACTED>>/android_talk5eb0a0d6167e (Google Services): 2 m 6 s (126 s) Count:215 0.4%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 4 s (124 s) Count:44 0.4%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 1 m 44 s (104 s) Count:153 0.3%
NLP PendingIntent client in com.google.android.googlequicksearchbox (com.google.android.apps.maps.Maps): 1 m 25 s (85 s) Count:725 0.3%
NetworkLocationSensorUploader (com.google.android.apps.maps.Maps): 1 m 14 s (74 s) Count:5 0.2%
AlarmManager (Android System): 1 m 2 s (62 s) Count:1569 0.2%
NetworkLocationLocator (Google Services): 60 s (60 s) Count:205 0.2%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 58 s (58 s) Count:2081 0.2%
*sync*_gmail-ls_Account {name=<<REDACTED>>, type=com.google} (com.google.android.gm.Gmail): 44 s (44 s) Count:33 0.1%
DownloadManager (Media): 44 s (44 s) Count:3 0.1%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 37 s (37 s) Count:2820 0.1%
SMSDispatcher (Phone): 36 s (36 s) Count:19 0.1%
LocationReportingService (com.google.android.apps.maps.Maps): 31 s (31 s) Count:6129 0.1%
RILJ (Phone): 31 s (31 s) Count:2756 0.1%
ActivityManager-Launch (Android System): 27 s (27 s) Count:499 0.1%
*backup* (Android System): 26 s (26 s) Count:831 0.1%
LocationPrivacyService (com.google.android.apps.maps.Maps): 25 s (25 s) Count:13 0.1%
*sync*_com.google.android.apps.currents_Account {name=<<REDACTED>>, type=com.google} (com.google.android.apps.currents.Currents): 25 s (25 s) Count:7 0.1%
NfcService (com.android.nfc.Nfc Service): 22 s (22 s) Count:47 0.1%
LocationManagerService (Android System): 18 s (18 s) Count:416 0.1%
MMS Connectivity (com.android.mms.Messaging): 15 s (15 s) Count:8 0.0%
sleep_broadcast (Android System): 15 s (15 s) Count:759 0.0%
AlarmManager (com.levelup.beautifulwidgets.Beautiful Widgets): 12 s (12 s) Count:571 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 10 s (10 s) Count:10 0.0%
DropboxCpuOnlyWakeLock (com.dropbox.android.Dropbox): 10 s (10 s) Count:3 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 9 s (9 s) Count:15 0.0%
LocationReceiverService (com.google.android.apps.maps.Maps): 9 s (9 s) Count:3611 0.0%
GpsLocationProvider (Android System): 9 s (9 s) Count:625 0.0%
ActivityManager-Sleep (Android System): 8 s (8 s) Count:1610 0.0%
StartingAlertService (com.android.mms.Messaging): 7 s (7 s) Count:54 0.0%
AlarmManager (com.google.android.apps.maps.Maps): 7 s (7 s) Count:6119 0.0%
MMS PushReceiver (com.android.mms.Messaging): 6 s (6 s) Count:4 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 6 s (6 s) Count:2071 0.0%
show keyguard (Android System): 6 s (6 s) Count:39 0.0%
*sync*_com.google.android.music.MusicContent_Account {name=<<REDACTED>>, type=com.google} (com.google.android.music.Google Play Music): 4 s (4 s) Count:2 0.0%
s (com.google.android.apps.maps.Maps): 4 s (4 s) Count:2143 0.0%
AudioOut_3 (1013): 3 s (3 s) Count:10 0.0%
ConnectivityService (Android System): 3 s (3 s) Count:1571 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 3 s (3 s) Count:5156 0.0%
GTALK_CONN (Google Services): 2 s (2 s) Count:607 0.0%
SCREEN_FROZEN (Android System): 2 s (2 s) Count:813 0.0%
NetworkStats (Android System): 2 s (2 s) Count:101 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:362 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:801 0.0%
*sync*_com.google.android.apps.magazines_Account {name=<<REDACTED>>, type=com.google} (com.google.android.apps.magazines.Google Play Magazines): 1 s (1 s) Count:3 0.0%
AudioIn_3B9 (1013): 1 s (1 s) Count:3 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1793 0.0%
*sync*_com.android.browser_Account {name=<<REDACTED>>, type=com.google} (Google Services): 1 s (1 s) Count:45 0.0%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 1 s (1 s) Count:135 0.0%
AudioIn_3BB (1013): 1 s (1 s) Count:7 0.0%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cntc/wc/ec)1/1/1 100.0%
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
======================
Network (requires root)
======================
==========
CPU States
==========
1 kHz (): ---%
Click to expand...
Click to collapse
Wakelocks are things that keep your phone awake. Partial wakelocks are typically held by applications, such as receiving an email or your twitter client checking for updates. A kernel wakelock is done at the kernel level, so it's typically something more low-level, which could be things like the charging system (phone's plugged into a power source) or the phone's radio waking it. Alarms are another category of items that wake your phone.
For wakelocks and alarms, the big thing you're looking for is the amount of time that they kept your phone awake. In this case, your top wakelock is "SignalCollector.ScannerThread", which woke the phone for 15 minutes and 41 seconds (2.8% of total uptime). We can also see that it woke the phone 163 times. From some quick googling, it appears that this is part of Google Maps. In any case, though, 15 minutes over 9 hours and 20 minutes isn't a lot.
Once you've had the battery problem again and can give another bbs report, then we'd be able to see what is consistantly waking your phone, causing the battery to drain. All we have right now is a report that shows a phone working how it should.
If you wanted any more specifics about any part of the report, I can try to answer whatever questions you have, and I'm sure there's someone much more knowledgeable about the topic than I am anyway who might pop in.
Edit: I removed your email address from multiple different places within my quotes. If you'd like to hide your email, you may wish to do the same in your post. In any case, it's not my place to duplicate that information.
My phone has "No or Unknown Signal" for 8h today, pretty sure that's because I've been on WIFI for about 8hours
(I also have 6 hours 15 minutes of awake time in 10 hours on time, and trying to figure that out is why I'm looking at battery threads )
question before i do anything: I dont mind running stock, but i would like to start using AOKP again, as i liked the extra features. What i dont want is my battery to go nuts, and then have people stupidly say "oh thats what you get from running a custom rom"
I had the problem with this STOCK rom already, so if i flash, and end up having the problem in the future, i really doubt the rom has anything to do with it.
How do you get display on for that long...... ahhh. This is what I get.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
exzacklyright said:
How do you get display on for that long...... ahhh. This is what I get.
Click to expand...
Click to collapse
i dont think my screen was on for that long. My phone was mostly idle in those screenshots, i think bbs said i had it on for like 36 minutes or something.
What i do know is that when these phones are working properly the battery is awesome. Or at least the 2 previous phones i had before this (captivate with 1800mh battery, and sgs2 with stock battery) Something happens that causes it to tank for me - and its not any app i install.
Hello everyone. I'll attach some relevant dump of better battery stats from last day:
===================
General Information
===================
BetterBatteryStats version: 1.11.0.0
Creation Date: 2012-12-07 09:42:23
Statistic Type: (6) Since Boot
Since 15 h 59 m 29 s
VERSION.RELEASE: 4.2.1
DEVICE: maguro
MODEL: Galaxy Nexus
OS.VERSION: 3.0.31-gd5a18e0
BOOTLOADER: PRIMELC03
ID: JOP40D
USER: android-build
PRODUCT: takju
RADIO: I9250XXLH1
Rooted: true
============
Battery Info
============
Level lost [%]: 42 Bat.: 42% (94% to 52%) [2,6%/h]
Voltage lost [mV]: 217 (3933-3716)
===========
Other Usage
===========
Deep Sleep (): 11 h 3 m 1 s (39781 s) Ratio: 69,0%
Awake (): 4 h 56 m 28 s (17788 s) Ratio: 30,9%
Screen On (): 56 m 55 s (3415 s) Ratio: 5,9%
=========
Wakelocks
=========
AudioOut_2 (1013): 24 m 54 s (1494 s) Count:315 2,6%
android.media.MediaPlayer (com.google.android.music.Google Play Music): 15 m 53 s (953 s) Count:275 1,7%
NetworkLocationLocator (Servizi Google): 15 m 15 s (915 s) Count:929 1,6%
AudioOut_EC (1013): 13 m 55 s (835 s) Count:326 1,4%
================
Kernel Wakelocks
================
"BTLowPower" (): 2 h 25 m 20 s (8720 s) Cntc/wc/ec)57/22/41 15,1%
"PowerManagerService" (): 53 m 58 s (3238 s) Cntc/wc/ec)3094/0/0 5,6%
"wlan_ctrl_wake" (): 26 m 22 s (1582 s) Cntc/wc/ec)1031/0/1031 2,7%
"mipi_link" (): 15 m 32 s (932 s) Cntc/wc/ec)2413/23/0 1,6%
"alarm_rtc" (): 15 m 28 s (928 s) Cntc/wc/ec)1445/0/436 1,6%
"wlan_rx_wake" (): 14 m 41 s (881 s) Cntc/wc/ec)884/0/884 1,5%
"radio-interface" (): 7 m 37 s (457 s) Cntc/wc/ec)552/0/0 0,8%
=========
Processes
=========
com.whatsapp (com.whatsapp.WhatsApp): Uid: 10088 Sys: 1 s (1 s) Us: 21 s (21 s) Starts: 3
mediaserver (1013): Uid: 1013 Sys: 6 s (6 s) Us: 14 s (14 s) Starts: 0
surfaceflinger (Sistema Android): Uid: 1000 Sys: 11 s (11 s) Us: 8 s (8 s) Starts: 0
*wakelock* (1013): Uid: 1013 Sys: 5 s (5 s) Us: 11 s (11 s) Starts: 0
com.facebook.katana (com.facebook.katana.Facebook): Uid: 10072 Sys: 2 s (2 s) Us: 11 s (11 s) Starts: 5
As you can see, I had a pretty bad ratio of Awake / Screen On.
Looking at user wakelocks, I have the correct android.media.MediaPlayer and the usual AudioOut_2 and NetworkLocationLocator. Let's say that those are ok...
Looking at kernel wakelocks, I have PowerManagerService which accounts for the previous user wakelocks, the usual nasty wlan_ctrl_wake, but a new BTLowPower.
This one I wasn't expecting!! Plus, I noticed that turning off the bluetooth didn't work, it got stuck on "turning off bluetooth".
This happened consistently, I mean, I get that wakelock and bt disabling issue almost every morning.
Is this a known bug?
Thanks all,
TD
Bluetooth on 100% of the time but this time it didn't bug out...
===================
General Information
===================
Since 13 h 44 m 22 s
VERSION.RELEASE: 4.2.1
MODEL: Galaxy Nexus
ID: JOP40D
============
Battery Info
============
Level lost [%]: 42 Bat.: 42% (97% to 55%) [3,1%/h]
===========
Other Usage
===========
Deep Sleep (): 11 h 28 m (41280 s) Ratio: 83,5%
Awake (): 2 h 16 m 21 s (8181 s) Ratio: 16,5%
Screen On (): 1 h 30 m 24 s (5424 s) Ratio: 11,0%
=========
Wakelocks
=========
AudioOut_2 (1013): 18 m 48 s (1128 s) Count:280 2,3%
PhoneApp (Telefono): 6 m 18 s (378 s) Count:7 0,8%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Servizi Google): 4 m 10 s (250 s) Count:330 0,5%
FacebookService (com.facebook.katana.Facebook): 2 m 5 s (125 s) Count:34 0,3%
================
Kernel Wakelocks
================
"PowerManagerService" (): 19 m 58 s (1198 s) Cntc/wc/ec)1336/0/0 2,4%
"wlan_rx_wake" (): 13 m 24 s (804 s) Cntc/wc/ec)1315/0/1315 1,6%
"mipi_link" (): 13 m 14 s (794 s) Cntc/wc/ec)2466/84/0 1,6%
"radio-interface" (): 6 m 21 s (381 s) Cntc/wc/ec)586/0/0 0,8%
"alarm_rtc" (): 5 m 11 s (311 s) Cntc/wc/ec)524/0/128 0,6%
"wlan_ctrl_wake" (): 2 m 33 s (153 s) Cntc/wc/ec)327/0/327 0,3%
"alarm" (): 1 m 30 s (90 s) Cntc/wc/ec)1347/524/0 0,2%
=========
My note 2 is loosing 6.2% battery an hour while it is sleeping. i know this is not normal and i am looking for a solution to my problems i will provide the BBS Dump below if anyone can help me solve my issues it would be appreciated greatly!
Code:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-05-09 17:06:59
Statistic Type: Unplugged to Current
Since 7 h 6 m 3 s
VERSION.RELEASE: 4.1.2
BRAND: samsung
DEVICE: t0lteatt
MANUFACTURER: samsung
MODEL: SAMSUNG-SGH-I317
OS.VERSION: 3.0.31-1071214
BOOTLOADER: I317UCAMA4
HARDWARE: smdk4x12
FINGERPRINT: samsung/t0lteatt/t0lteatt:4.1.2/JZO54K/I317UCAMA4:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: se.infra
PRODUCT: t0lteatt
RADIO: I317UCAMA4
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -46% (66% to 20%) [6.5%/h]
Voltage lost [mV]: (3844-3639) [28.9%/h]
===========
Other Usage
===========
Deep Sleep (): 3 h 49 m 28 s (13768 s) Ratio: 53.9%
Awake (): 3 h 16 m 35 s (11795 s) Ratio: 46.1%
Screen On (): 23 m 38 s (1418 s) Ratio: 5.5%
Phone On (): 7 m 5 s (425 s) Ratio: 1.7%
Wifi On (): 6 m 51 s (411 s) Ratio: 1.6%
Wifi Running (): 6 m 51 s (411 s) Ratio: 1.6%
No Data Connection (): 9 m 23 s (563 s) Ratio: 2.2%
No or Unknown Signal (): 9 m 23 s (563 s) Ratio: 2.2%
Poor Signal (): 39 m 22 s (2362 s) Ratio: 1.6%
Moderate Signal (): 2 h 23 m 19 s (8599 s) Ratio: 33.6%
Good Signal (): 1 h 42 m 3 s (6123 s) Ratio: 24.0%
Screen dark (): 8 m 35 s (515 s) Ratio: 2.0%
Screen dimmed (): 3 m 7 s (187 s) Ratio: 0.7%
Screen medium (): 4 m 59 s (299 s) Ratio: 1.2%
Screen light (): 6 m 45 s (405 s) Ratio: 1.6%
Screen bright (): 10 s (10 s) Ratio: 0.0%
=========
Wakelocks
=========
*backup* (Android System): 29 m 32 s (1772 s) Count:538 6.9%
*sync*_gmail-ls_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.google} (com.google.android.gm.Gmail): 18 m 7 s (1087 s) Count:44 2.6%
NLP PendingIntent client in com.google.android.googlequicksearchbox (com.google.android.apps.maps.Maps): 9 m 19 s (559 s) Count:-1331 2.2%
EM/android_talk566e723b7583 (Google Services): 7 m 30 s (450 s) Count:25 1.8%
StartingAlertService (com.android.calendar.S Planner): 6 m 57 s (417 s) Count:100 1.0%
AlarmManager (com.levelup.beautifulwidgets.BeautifulWidgets): 6 m 50 s (410 s) Count:442 1.6%
AlarmManager (Android System): 6 m 21 s (381 s) Count:1087 1.5%
LocationManagerService (Android System): 5 m 3 s (303 s) Count:159 1.2%
LocationReceiverService (com.google.android.apps.maps.Maps): 4 m 51 s (291 s) Count:2463 1.1%
AlarmManager (com.google.android.apps.maps.Maps): 4 m 34 s (274 s) Count:3698 1.1%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 3 m 58 s (238 s) Count:1350 0.9%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 3 m 53 s (233 s) Count:-530 0.9%
CheckinsNotificationService (com.google.android.apps.maps.Maps): 3 m 50 s (230 s) Count:2035 0.9%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 3 m 35 s (215 s) Count:3439 0.8%
com.google.android.music.leanback.AutoCachingService (com.google.android.music.Google Play Music): 2 m 46 s (166 s) Count:44 0.7%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 45 s (165 s) Count:107 0.6%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 2 m 41 s (161 s) Count:53 0.6%
GTALK_CONN (Google Services): 2 m 25 s (145 s) Count:735 0.6%
RILJ (Phone): 2 m 22 s (142 s) Count:3716 0.6%
AlarmManager (com.sec.spp.push.Samsung Push Service): 1 m 57 s (117 s) Count:318 0.5%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 1 m 52 s (112 s) Count:1882 0.4%
LocationReportingService (com.google.android.apps.maps.Maps): 1 m 50 s (110 s) Count:3710 0.4%
GSM (Phone): 1 m 50 s (110 s) Count:83 0.4%
ConnectMQTT (com.nuance.swype.beta.Swype Beta 1.4): 1 m 27 s (87 s) Count:14 0.3%
AlarmManager (Google Services): 1 m 27 s (87 s) Count:821 0.3%
SyncLoopWakeLock (Android System): 1 m 15 s (75 s) Count:1287 0.3%
Checkin Service (Google Services): 1 m 13 s (73 s) Count:175 0.3%
AudioOut_2 (1013): 1 m 6 s (66 s) Count:35 0.3%
Icing (Google Services): 58 s (58 s) Count:353 0.2%
NetworkLocationLocator (Google Services): 55 s (55 s) Count:331 0.2%
GpsLocationProvider (Android System): 51 s (51 s) Count:385 0.2%
Event Log Service (Google Services): 50 s (50 s) Count:421 0.2%
AlarmManager (com.google.android.googlequicksearchbox.Google Search): 37 s (37 s) Count:90 0.1%
ActivityManager-Launch (Android System): 32 s (32 s) Count:249 0.1%
AlarmManager (com.google.android.apps.plus.Google+): 30 s (30 s) Count:33 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 28 s (28 s) Count:37 0.1%
PhoneWindowManager.mBroadcastWakeLock (Android System): 27 s (27 s) Count:286 0.1%
sleep_broadcast (Android System): 26 s (26 s) Count:469 0.1%
AlarmManager (com.nuance.swype.beta.Swype Beta 1.4): 26 s (26 s) Count:52 0.1%
AlarmManager (UID): 25 s (25 s) Count:19 0.1%
Camera Monitor (com.google.android.apps.plus.Google+): 22 s (22 s) Count:12 0.1%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 20 s (20 s) Count:38 0.1%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 18 s (18 s) Count:2829 0.1%
show keyguard (Android System): 17 s (17 s) Count:17 0.1%
AsyncCollectorListener (com.google.android.apps.maps.Maps): 15 s (15 s) Count:3304 0.1%
FastDormancy (Phone): 14 s (14 s) Count:19 0.1%
AlarmManager (com.android.providers.calendar.Calendar storage): 13 s (13 s) Count:5 0.1%
Checkin Handoff (Google Services): 10 s (10 s) Count:93 0.0%
reset keyguard (Android System): 10 s (10 s) Count:489 0.0%
StartingAlertService (com.android.mms.Messaging): 10 s (10 s) Count:4 0.0%
AlarmManager (Phone): 8 s (8 s) Count:143 0.0%
SMSDispatcher (Phone): 7 s (7 s) Count:5 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 7 s (7 s) Count:23 0.0%
*sync*_com.android.calendar_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.osp.app.signin} (Samsung Syncadapters): 5 s (5 s) Count:2 0.0%
b (com.sec.spp.push.Samsung Push Service): 4 s (4 s) Count:204 0.0%
GTALK_IDLE_ALARM (Google Services): 4 s (4 s) Count:467 0.0%
AlarmManager (com.android.chrome.Chrome): 4 s (4 s) Count:135 0.0%
SyncManagerHandleSyncAlarm (Android System): 4 s (4 s) Count:411 0.0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar storage): 3 s (3 s) Count:10 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 3 s (3 s) Count:13 0.0%
ServiceStateTracker (Phone): 3 s (3 s) Count:72 0.0%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 3 s (3 s) Count:65 0.0%
GOOGLE_C2DM (Google Services): 3 s (3 s) Count:403 0.0%
*sync*_com.android.browser_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.osp.app.signin} (Samsung Syncadapters): 2 s (2 s) Count:4 0.0%
Proximity Partial (Android System): 2 s (2 s) Count:30 0.0%
NetworkStats (Android System): 2 s (2 s) Count:79 0.0%
WifiStateMachine (Android System): 2 s (2 s) Count:539 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1315 0.0%
Event Log Handoff (Google Services): 1 s (1 s) Count:749 0.0%
*sync*_com.android.chrome_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.google} (com.android.chrome.Chrome): 1 s (1 s) Count:50 0.0%
PhoneApp (Phone): 1 s (1 s) Count:217 0.0%
*sync*_com.android.calendar_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 1 s (1 s) Count:4 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:493 0.0%
NetworkLocationCacheUpdater (Google Services): 1 s (1 s) Count:30 0.0%
PreventScreenOn Partial (Android System): 1 s (1 s) Count:288 0.0%
keyguardWakeAndHandOff (Android System): 1 s (1 s) Count:552 0.0%
multiplexing-gcm-listener:com.google.android.apps.chrome.snapshot.gcm.GcmReceiver (com.android.chrome.Chrome): 1 s (1 s) Count:174 0.0%
*sync*_com.android.contacts_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.osp.app.signin} (Samsung Syncadapters): 1 s (1 s) Count:3 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 2 h 10 m 10 s (7810 s) Cnt:(c/wc/ec)2556/0/0 30.6%
"mdm_hsic_pm0" (): 44 m (2640 s) Cnt:(c/wc/ec)3966/222/0 10.3%
"fast_dormancy" (): 33 m 3 s (1983 s) Cnt:(c/wc/ec)334/0/334 7.8%
"hsicctl0" (): 18 m 53 s (1133 s) Cnt:(c/wc/ec)2137/0/2137 4.4%
"battery-monitor" (): 14 m 42 s (882 s) Cnt:(c/wc/ec)906/0/906 3.5%
"radio-interface" (): 13 m 18 s (798 s) Cnt:(c/wc/ec)769/0/0 3.1%
"alarm_rtc" (): 7 m 26 s (446 s) Cnt:(c/wc/ec)849/0/121 1.7%
"alarm" (): 6 m 16 s (376 s) Cnt:(c/wc/ec)1691/1/5 1.5%
"battery-update" (): 1 m 52 s (112 s) Cnt:(c/wc/ec)45/0/45 0.4%
"sensorhub_wake_lock" (): 1 m 52 s (112 s) Cnt:(c/wc/ec)49/0/48 0.4%
"AudioOutLock" (): 48 s (48 s) Cnt:(c/wc/ec)35/0/0 0.2%
"ssp_wake_lock" (): 34 s (34 s) Cnt:(c/wc/ec)18/3/18 0.1%
"sync_system" (): 1 s (1 s) Cnt:(c/wc/ec)31/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)8527/0/0 0.0%
"qcril" (): (0 s) Cnt:(c/wc/ec)1308/0/0 0.0%
"ApmCommand" (): (0 s) Cnt:(c/wc/ec)283/0/0 0.0%
"qmuxd_port_wl_9" (): (0 s) Cnt:(c/wc/ec)5523/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)906/599/0 0.0%
"mmc1_detect" (): (0 s) Cnt:(c/wc/ec)1046/0/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)1046/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.6 GHz (): 2 h 56 m 29 s 41.4%
1.5 GHz (): 43 s 0.2%
1.4 GHz (): 40 s 0.2%
1.3 GHz (): 6 s 0.0%
1.2 GHz (): 2 m 35 s 0.6%
1.1 GHz (): 38 s 0.2%
1 GHz (): 30 s 0.1%
900 MHz (): 3 s 0.0%
800 MHz (): 12 m 55 s 3.0%
700 MHz (): 29 s 0.1%
600 MHz (): 27 s 0.1%
500 MHz (): 2 s 0.0%
400 MHz (): 53 s 0.2%
Deep Sleep (): 3 h 49 m 28 s 53.9%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 1 d 10 h 50 m 52 s (Wl: 86 elements; KWl: 30elements; NetS: null; Alrm: null; Proc: 26 elements; Oth: 15 elements; CPU: 15 elements)
ref_current: Reference ref_current created 1 d 17 h 56 m 56 s (Wl: 97 elements; KWl: 30elements; NetS: null; Alrm: null; Proc: 44 elements; Oth: 16 elements; CPU: 15 elements)
What kernel are you running. ..
Root=true
And your device ran for 2 hours 56 minutes at 1.6 ghz on 4 cores.(ouch that's bad)..
Your right. ..something is messed up. ...g
IF you are running a custom rom I would do a clean flash of whatever you are runnning if not I would root and flash a rom like clean rom or novella
envision said:
IF you are running a custom rom I would do a clean flash of whatever you are runnning if not I would root and flash a rom like clean rom or novella
Click to expand...
Click to collapse
i just flashed CleanROM 4.9 completely fresh
Kernel issue. ...it's gotta be a kernel related problem...imho....g
gregsarg said:
Kernel issue. ...it's gotta be a kernel related problem...imho....g
Click to expand...
Click to collapse
CleanRom uses the Perseus kernal right? any ideas on how i can fix this?
FluryKnox said:
CleanRom uses the Perseus kernal right? any ideas on how i can fix this?
Click to expand...
Click to collapse
Well...
Trying another kernel would certainly tell you what you want to know.
Cleanrom is a touchwiz rom isn't it?
Let me look at the rom and see if I can find an alternative....
Be back shortly...g
gregsarg said:
Well...
Trying another kernel would certainly tell you what you want to know.
Cleanrom is a touchwiz rom isn't it?
Let me look at the rom and see if I can find an alternative....
Be back shortly...g
Click to expand...
Click to collapse
i just fresh installed cleanrom again and installed BBS again gonna let it sit in sleep mode all night ill report back when the battery is 20%
Based on the reading i just did on kernels over on Scotts site, the Saber kernel will work also.
Users report good function, but most are using perseus.
I prefer Saber on a stock TW build. And I have not tested saber on Scotts builds.
Worst case, run a good backup before changes are made, and restore if needed...g
gregsarg said:
Based on the reading i just did on kernels over on Scotts site, the Saber kernel will work also.
Users report good function, but most are using perseus.
I prefer Saber on a stock TW build. And I have not tested saber on Scotts builds.
Worst case, run a good backup before changes are made, and restore if needed...g
Click to expand...
Click to collapse
Yeahh this problem started appearing out of the blue it seems like i just fresh installed gonna let my phone sit all night no usage only sleep mode ill report back with another BBS Dump in the morning. i made sure google did not restore my phone lets see if this will work......
Sounds good. .
I'm curious to see the log. And also interested in the rom.
I nearly loaded it up today, but I'm waiting pending the results you post.
Catch ya tomorrow. ..g
When I was running CleanRom I was burning huge amounts of battery, like 15-20% overnight vs 2-3% on stock. I was getting dozens of wakelocks throughout the night. I found the stock ATT kernel and went back to that and my battery drain was about 8% overnight. Now I'm running CM10.1 on their stock kernel and I'm burning 4% overnight.
I haven't found any rom/kernel combination that will give me the batter life of the stock setup. However, I'm loving my CM10.1 battery life at the moment, plus the whole bonus of vanilla android.
gregsarg said:
Sounds good. .
I'm curious to see the log. And also interested in the rom.
I nearly loaded it up today, but I'm waiting pending the results you post.
Catch ya tomorrow. ..g
Click to expand...
Click to collapse
Im getting WAY better results now are these pretty much normal for the note2?
i left my wifi connected connected all night while in sleep mode so thats probably the reason its 2.0/h power loss but overall i feel this is pretty much normal now right?
Code:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-05-10 12:59:49
Statistic Type: Unplugged to Current
Since 15 h 25 m 52 s
VERSION.RELEASE: 4.1.2
BRAND: samsung
DEVICE: t0lteatt
MANUFACTURER: samsung
MODEL: SAMSUNG-SGH-I317
OS.VERSION: 3.0.31-1071214
BOOTLOADER: I317UCAMA4
HARDWARE: smdk4x12
FINGERPRINT: samsung/t0lteatt/t0lteatt:4.1.2/JZO54K/I317UCAMA4:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: se.infra
PRODUCT: t0lteatt
RADIO: I317UCAMA4
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -32% (100% to 68%) [2.1%/h]
Voltage lost [mV]: (4275-3940) [21.7%/h]
===========
Other Usage
===========
Deep Sleep (): 14 h 17 m (51420 s) Ratio: 92.6%
Awake (): 1 h 8 m 52 s (4132 s) Ratio: 7.4%
Screen On (): 7 m 5 s (425 s) Ratio: 0.8%
Wifi On (): 15 h 25 m 52 s (55552 s) Ratio: 100.0%
Wifi Running (): 15 h 25 m 52 s (55552 s) Ratio: 100.0%
No Data Connection (): 15 h 25 m 17 s (55517 s) Ratio: 99.9%
No or Unknown Signal (): 15 h 25 m 17 s (55517 s) Ratio: 99.9%
Good Signal (): (0 s) Ratio: 0.0%
Screen dark (): 5 m 31 s (331 s) Ratio: 0.6%
Screen dimmed (): 1 m 10 s (70 s) Ratio: 0.1%
Screen medium (): 23 s (23 s) Ratio: 0.0%
=========
Wakelocks
=========
AlarmManager (Android System): 1 m 48 s (108 s) Count:1220 0.2%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 1 m 41 s (101 s) Count:131 0.2%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 1 m 39 s (99 s) Count:358 0.2%
com.google.android.music.leanback.AutoCachingService (com.google.android.music.Google Play Music): 59 s (59 s) Count:41 0.1%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 52 s (52 s) Count:135 0.1%
FastDormancy (Phone): 38 s (38 s) Count:362 0.1%
*sync*_gmail-ls_Account {name=6b3f729aaa8832335b356e69756ebb7f, type=com.google} (com.google.android.gm.Gmail): 28 s (28 s) Count:17 0.1%
RILJ (Phone): 16 s (16 s) Count:345 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 16 s (16 s) Count:29 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 10 s (10 s) Count:3 0.0%
ActivityManager-Launch (Android System): 10 s (10 s) Count:152 0.0%
AudioOut_2 (1013): 7 s (7 s) Count:2 0.0%
Icing (Google Services): 7 s (7 s) Count:31 0.0%
ConnectMQTT (com.nuance.swype.beta.Swype Beta 1.4): 6 s (6 s) Count:88 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 4 s (4 s) Count:13 0.0%
AlarmManager (com.google.android.apps.maps.Maps): 4 s (4 s) Count:491 0.0%
GTALK_CONN (Google Services): 4 s (4 s) Count:339 0.0%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 3 s (3 s) Count:86 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 3 s (3 s) Count:161 0.0%
AlarmManager (Google Services): 3 s (3 s) Count:497 0.0%
AlarmManager (com.google.android.music.Google Play Music): 3 s (3 s) Count:50 0.0%
SyncLoopWakeLock (Android System): 3 s (3 s) Count:1324 0.0%
Event Log Service (Google Services): 2 s (2 s) Count:83 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 2 s (2 s) Count:82 0.0%
AlarmManager (UID): 2 s (2 s) Count:29 0.0%
sleep_broadcast (Android System): 2 s (2 s) Count:238 0.0%
show keyguard (Android System): 2 s (2 s) Count:13 0.0%
AlarmManager (com.sec.spp.push.Samsung Push Service): 2 s (2 s) Count:128 0.0%
GpsLocationProvider (Android System): 2 s (2 s) Count:216 0.0%
Checkin Service (Google Services): 1 s (1 s) Count:396 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:245 0.0%
AlarmManager (Phone): 1 s (1 s) Count:142 0.0%
EM/android_talk58c0594adc84 (Google Services): 1 s (1 s) Count:398 0.0%
NetworkStats (Android System): 1 s (1 s) Count:68 0.0%
================
Kernel Wakelocks
================
"battery-monitor" (): 28 m 8 s (1688 s) Cnt:(c/wc/ec)1706/0/1706 3.0%
"mdm_hsic_pm0" (): 20 m 35 s (1235 s) Cnt:(c/wc/ec)1972/456/0 2.2%
"wlan_rx_wake" (): 18 m 15 s (1095 s) Cnt:(c/wc/ec)1107/0/1106 2.0%
"PowerManagerService" (): 9 m 2 s (542 s) Cnt:(c/wc/ec)1518/0/0 1.0%
"alarm_rtc" (): 8 m 21 s (501 s) Cnt:(c/wc/ec)984/33/37 0.9%
"hsicctl0" (): 6 m 16 s (376 s) Cnt:(c/wc/ec)672/0/672 0.7%
"alarm" (): 6 m 3 s (363 s) Cnt:(c/wc/ec)1384/1/0 0.7%
"wlan_wake" (): 3 m 30 s (210 s) Cnt:(c/wc/ec)18569/732/0 0.4%
"wlan_ctrl_wake" (): 3 m 4 s (184 s) Cnt:(c/wc/ec)155/0/155 0.3%
"battery-update" (): 1 m 30 s (90 s) Cnt:(c/wc/ec)32/0/33 0.2%
"radio-interface" (): 1 m 1 s (61 s) Cnt:(c/wc/ec)64/0/0 0.1%
"fast_dormancy" (): 53 s (53 s) Cnt:(c/wc/ec)8/0/8 0.1%
"sensorhub_wake_lock" (): 21 s (21 s) Cnt:(c/wc/ec)21/0/22 0.0%
"AudioOutLock" (): 9 s (9 s) Cnt:(c/wc/ec)2/0/0 0.0%
"qmuxd_port_wl_9" (): (0 s) Cnt:(c/wc/ec)3123/0/0 0.0%
"qcril" (): (0 s) Cnt:(c/wc/ec)170/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)3990/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)1707/414/0 0.0%
"mmc1_detect" (): (0 s) Cnt:(c/wc/ec)1827/0/0 0.0%
"sync_system" (): (0 s) Cnt:(c/wc/ec)9/0/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)1827/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.6 GHz (): 1 m 49 s 0.2%
1.5 GHz (): 4 s 0.0%
1.4 GHz (): 40 s 0.1%
1.3 GHz (): 5 s 0.0%
1.2 GHz (): 27 s 0.0%
1.1 GHz (): 6 s 0.0%
1 GHz (): 13 m 2 s 1.4%
900 MHz (): 6 s 0.0%
800 MHz (): 24 m 13 s 2.6%
700 MHz (): 43 s 0.1%
600 MHz (): 1 m 40 s 0.2%
500 MHz (): 55 s 0.1%
400 MHz (): 7 m 6 s 0.8%
200 MHz (): 17 m 51 s 1.9%
Deep Sleep (): 14 h 17 m 92.6%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 2 h 56 m 14 s (Wl: 0 elements; KWl: 25elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 15 elements)
ref_charged: Reference ref_charged created 2 h 56 m 14 s (Wl: 0 elements; KWl: 25elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 15 elements)
ref_current: Reference ref_current created 18 h 22 m 7 s (Wl: 34 elements; KWl: 24elements; NetS: null; Alrm: null; Proc: 12 elements; Oth: 11 elements; CPU: 15 elements)
"MUCH" better. ..
That usage is in line with the average note2 I would think.
And if you flash a stock kernel it will get even better.
It is my belief, and of many others that this device needs no kernel changes.
The device runs it's best on the stock kernel. ..IMHO
Watch it for a few days, and see if you notice any other battery drain issues.
If you do, try the different kernel. ...g
Edit:
I also noticed the CPU usage in the upper levels has returned to normal range as well.
What ever you did, keep doing it. ..g
gregsarg said:
"MUCH" better. ..
That usage is in line with the average note2 I would think.
And if you flash a stock kernel it will get even better.
It is my belief, and of many others that this device needs no kernel changes.
The device runs it's best on the stock kernel. ..IMHO
Watch it for a few days, and see if you notice any other battery drain issues.
If you do, try the different kernel. ...g
Edit:
I also noticed the CPU usage in the upper levels has returned to normal range as well.
What ever you did, keep doing it. ..g
Click to expand...
Click to collapse
Yeah im beginning to think it was a wonky app that i had installed. i havnt installed anything on it yet besides BBS going to slowly re install apps and continue monitoring it.
Thank you. ..
It's great information on the rom...g
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
my cell is dead in hours and cant figure it out. i completely wiped it and restored to stock and then ran MD4 stock for sometime and have same problem as the MK3 stock.
installed better battery stats last night and here is the file
can anyone help me out with this. this is the phone sitting at night. rooted stock 4.3 stock kernel with cnexus tweaks even has juice defender to stop internet activity.
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2014-02-08 07:53:00
Statistic Type: Unplugged to Current
Since 11 h 51 m 24 s
VERSION.RELEASE: 4.3
BRAND: samsung
DEVICE: d2spr
MANUFACTURER: samsung
MODEL: SPH-L710
OS.VERSION: 3.0.31-g1ac4b4a-dirty
BOOTLOADER: L710VPBMD4
HARDWARE: qcom
FINGERPRINT: samsung/d2spr/d2spr:4.3/JSS15J/L710VPUCMK3:user/release-keys
ID: JSS15J
TAGS: release-keys
USER: se.infra
PRODUCT: d2spr
RADIO: L710VPUCMK3
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -91% (100% to 9%) [7.7%/h]
Voltage lost [mV]: (4203-3578) [52.7%/h]
===========
Other Usage
===========
Deep Sleep (): 1 m 12 s (72 s) Ratio: 0.1%
Awake (): 11 h 50 m 12 s (42612 s) Ratio: 99.8%
Screen On (): 29 m 38 s (1778 s) Ratio: 4.2%
Phone On (): 14 s (14 s) Ratio: 0.0%
Wifi On (): 34 m 4 s (2044 s) Ratio: 4.8%
Wifi Running (): 11 h 51 m 24 s (42684 s) Ratio: 100.0%
Screen dark (): 29 m 38 s (1778 s) Ratio: 4.2%
=========
Wakelocks
=========
AudioOut_2 (1013): 15 m 26 s (926 s) Count:41 2.2%
Starting CM_VnoteService (com.coremobility.app.vnotes.Voicemail): 10 m 27 s (627 s) Count:22 1.5%
NlpWakeLock (Google Play services): 8 m 53 s (533 s) Count:336 1.2%
ConnectivityService (Android System): 4 m 44 s (284 s) Count:1433 0.7%
JuiceDefender.Service (JuiceDefender): 3 m 25 s (205 s) Count:825 0.5%
AlarmManager (Android System): 3 m 23 s (203 s) Count:1427 0.5%
PushClient SystemStateMonitorService (com.sec.spp.push.Samsung Push Service): 1 m 11 s (71 s) Count:96 0.2%
SprintUpdater-UpdaterService (com.sprint.ce.updater.Sprint Installer): 58 s (58 s) Count:1 0.1%
ActivityManager-Launch (Android System): 33 s (33 s) Count:463 0.1%
GCM_CONN_ALARM (Google Play services): 17 s (17 s) Count:647 0.0%
SMSDispatcher (Phone): 16 s (16 s) Count:12 0.0%
NlpCollectorWakeLock (Google Play services): 14 s (14 s) Count:730 0.0%
(com.sprint.zone.Sprint Zone): 12 s (12 s) Count:68 0.0%
SmartFaceService (Android System): 12 s (12 s) Count:481 0.0%
FbClientConnManager (com.facebook.katana.Facebook): 11 s (11 s) Count:24 0.0%
AlarmManager (Google Play services): 10 s (10 s) Count:1289 0.0%
RILJ (Phone): 10 s (10 s) Count:125 0.0%
PhoneApp (Phone): 9 s (9 s) Count:3 0.0%
AudioIn_1D8 (1013): 9 s (9 s) Count:43 0.0%
StartingAlertService (com.android.mms.Messaging): 8 s (8 s) Count:13 0.0%
AlarmManager (com.facebook.katana.Facebook): 8 s (8 s) Count:94 0.0%
CM Message wakeup (com.coremobility.app.vnotes.Voicemail): 7 s (7 s) Count:69 0.0%
CleanupService (com.groupme.android.GroupMe): 7 s (7 s) Count:5 0.0%
NetworkLocationLocator (Google Play services): 7 s (7 s) Count:676 0.0%
Icing (Google Play services): 6 s (6 s) Count:672 0.0%
*sync*_com.google.android.apps.plus.content.EsProv ider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.apps.plus.Google+): 6 s (6 s) Count:7 0.0%
Event Log Service (Google Play services): 5 s (5 s) Count:757 0.0%
SCREEN_FROZEN (Android System): 5 s (5 s) Count:586 0.0%
LocationManagerService (Android System): 5 s (5 s) Count:408 0.0%
*sync*_com.sec.android.gallery3d.picasa.contentpro vider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.sec.android.gallery3d.Gallery): 4 s (4 s) Count:7 0.0%
MMS PushReceiver (com.android.mms.Messaging): 4 s (4 s) Count:17 0.0%
show keyguard (Android System): 4 s (4 s) Count:163 0.0%
NlpLocationReceiverService (com.google.android.googlequicksearchbox.Google Search): 4 s (4 s) Count:380 0.0%
SyncLoopWakeLock (Android System): 4 s (4 s) Count:1558 0.0%
DHCP (Android System): 4 s (4 s) Count:591 0.0%
AlarmManager (com.google.android.talk.Hangouts): 4 s (4 s) Count:22 0.0%
*backup* (Android System): 3 s (3 s) Count:634 0.0%
GCM_CONN (Google Play services): 3 s (3 s) Count:850 0.0%
AlarmManager (com.sec.spp.push.Samsung Push Service): 3 s (3 s) Count:173 0.0%
TimaService (Android System): 2 s (2 s) Count:142 0.0%
mResetWakelock (Android System): 2 s (2 s) Count:154 0.0%
StartingAlertService (com.android.calendar.Calendar): 2 s (2 s) Count:12 0.0%
AlarmManager (com.drclabs.android.wootchecker.WootWatcher): 2 s (2 s) Count:166 0.0%
SamsungPhoneWindowManager.mBroadcastWakeLock (Android System): 2 s (2 s) Count:491 0.0%
WootWatcherWakeLock (com.drclabs.android.wootchecker.WootWatcher): 2 s (2 s) Count:83 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Play services): 2 s (2 s) Count:734 0.0%
NetworkStats (Android System): 2 s (2 s) Count:243 0.0%
hangouts_rtcs (com.google.android.talk.Hangouts): 2 s (2 s) Count:13 0.0%
gum (com.google.android.googlequicksearchbox.Google Search): 2 s (2 s) Count:115 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 2 s (2 s) Count:3 0.0%
MMS Connectivity (com.android.mms.Messaging): 1 s (1 s) Count:21 0.0%
AlarmManager (JuiceDefender): 1 s (1 s) Count:107 0.0%
GpsLocationProvider (Android System): 1 s (1 s) Count:557 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 1 s (1 s) Count:2 0.0%
AlarmManager (com.sprint.zone.Sprint Zone): 1 s (1 s) Count:91 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 1 s (1 s) Count:8 0.0%
Checkin Service (Google Play services): 1 s (1 s) Count:437 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1442 0.0%
LocationManagerService (Google Play services): 1 s (1 s) Count:167 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats ): 1 s (1 s) Count:2 0.0%
AudioIn_1E6 (1013): 1 s (1 s) Count:4 0.0%
================
Kernel Wakelocks
================
"suspend_backoff" (): 5 h 37 m 1 s (20221 s) Cntc/wc/ec)2025/0/2025 37.7%
"mmc1_detect" (): 3 h 45 m 52 s (13552 s) Cntc/wc/ec)20275/0/20275 31.7%
"sec-battery-monitor" (): 2 h 53 m 5 s (10385 s) Cntc/wc/ec)20291/0/0 24.3%
"mmc0_detect" (): 2 h 46 m 1 s (9961 s) Cntc/wc/ec)20275/0/20275 23.3%
"PowerManagerService.WakeLocks" (): 35 m 56 s (2156 s) Cntc/wc/ec)2432/0/0 5.1%
"alarm_rtc" (): 13 m 57 s (837 s) Cntc/wc/ec)868/0/200 2.0%
"pm8xxx_adc_wakelock" (): 9 m 51 s (591 s) Cntc/wc/ec)40041/19684/0 1.4%
"sec-battery-measure" (): 9 m 46 s (586 s) Cntc/wc/ec)20307/0/0 1.4%
"wlan_ctrl_wake" (): 6 m 55 s (415 s) Cntc/wc/ec)321/0/321 1.0%
"bam_dmux_wakelock" (): 2 m 41 s (161 s) Cntc/wc/ec)128/0/64 0.4%
"power-supply" (): 1 m 44 s (104 s) Cntc/wc/ec)20291/0/0 0.2%
"wlan_rx_wake" (): 1 m 40 s (100 s) Cntc/wc/ec)666/0/666 0.2%
"smdcntl0" (): 1 m 33 s (93 s) Cntc/wc/ec)1794/1/163 0.2%
"radio-interface" (): 41 s (41 s) Cntc/wc/ec)60/0/0 0.1%
"alarm" (): 40 s (40 s) Cntc/wc/ec)1826/2/0 0.1%
"KeyEvents" (): 27 s (27 s) Cntc/wc/ec)61903/0/0 0.1%
"wlan_wake" (): 25 s (25 s) Cntc/wc/ec)52911/0/0 0.1%
"PowerManagerService.Broadcasts" (): 9 s (9 s) Cntc/wc/ec)24/0/0 0.0%
"vib_present" (): 9 s (9 s) Cntc/wc/ec)52/0/0 0.0%
"DS" (): 5 s (5 s) Cntc/wc/ec)13/0/13 0.0%
"LightsService" (): 3 s (3 s) Cntc/wc/ec)16/0/0 0.0%
"rmt_storage_-1205258928" (): 1 s (1 s) Cntc/wc/ec)5/0/0 0.0%
"PowerManagerService.Display" (): 1 s (1 s) Cntc/wc/ec)12/0/0 0.0%
"rmt_storage_-1205259776" (): 1 s (1 s) Cntc/wc/ec)5/0/0 0.0%
"MediaPlayerService_Decode" (): 1 s (1 s) Cntc/wc/ec)49/0/0 0.0%
"ipc00000001_rmt_storage" (): (0 s) Cntc/wc/ec)31/0/0 0.0%
"qmuxd_port_wl_0" (): (0 s) Cntc/wc/ec)1671/0/0 0.0%
"ApmCommand" (): (0 s) Cntc/wc/ec)162/0/0 0.0%
"msm_ipc_router_smd_xprt" (): (0 s) Cntc/wc/ec)51/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
384 MHz (): 11 h 15 m 1 s 94.9%
486 MHz (): 2 m 6 s 0.3%
594 MHz (): 1 m 18 s 0.2%
702 MHz (): 54 s 0.1%
810 MHz (): 3 m 47 s 0.5%
918 MHz (): 9 m 19 s 1.3%
1.03 GHz (): 1 m 18 s 0.2%
1.13 GHz (): 1 m 54 s 0.3%
1.24 GHz (): 27 s 0.1%
1.35 GHz (): 31 s 0.1%
1.46 GHz (): 10 s 0.0%
1.51 GHz (): 13 m 22 s 1.9%
Deep Sleep (): 1 m 12 s 0.1%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 1 m 5 s (Wl: 9 elements; KWl: 20elements; NetS: null; Alrm: null; Proc: 10 elements; Oth: 2 elements; CPU: 2 elements)
ref_unplugged: Reference ref_unplugged created 3 h 1 m 43 s (Wl: 0 elements; KWl: 33elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 5 elements; CPU: 12 elements)
ref_charged: Reference ref_charged created 3 h 1 m 43 s (Wl: 0 elements; KWl: 33elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 5 elements; CPU: 12 elements)
ref_current: Reference ref_current created 14 h 53 m 7 s (Wl: 61 elements; KWl: 32elements; NetS: null; Alrm: null; Proc: 137 elements; Oth: 7 elements; CPU: 13 elements)
The first thing is, uninstall Juice Defender. Until you know what is going on with the Battery Life, all you are doing doing is complicating the issue. You say you did a complete wipe before installing the Rom ? Does that mean you wiped: System, Data, Dalvik Cache, Cache, Factory Reset ? Did you restore any Data ? Have you tried a different Battery to rule out that the battery is defective ?
Did everything except battery...even an Odin restore to stock..same issue minimum 10 percent per hour drain
Sent from my SPH-L710 using xda app-developers app
New battery and same issues
Sent from my SPH-L710 using xda app-developers app
jalfonso119 said:
Did everything except battery...even an Odin restore to stock..same issue minimum 10 percent per hour drain
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
jalfonso119 said:
New battery and same issues
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That's very strange . Are you sure that there's not a wakelock going on ? What's your screen on time ?
Uninstall BBS.
Go and install GSam Battery Monitor from Play. Your phone certainly isn't sleeping. He was 11hrs awake.
Been the same problem within two different roms, can be mediaserver or a specific app.
With GSam you can see what app or process is really draining your battery. In the App Usage section.
Sent from my SPH-L710
I tried several roms without even installing apps and same thing. Tried several kernels too.. I even Odin to md4 stock up rooted and same thing... I have gsam and it's the kernel OS draining the battery and won't deep sleep... It even drains when there isn't any data connection... Also I got the zero lemon battery now so that's why it doesn't look like it's draining much but it still is
Sent from my SPH-L710 using xda app-developers app
Sent from my SPH-L710 using xda app-developers app
Sent from my SPH-L710 using xda app-developers app