Hi all!
My wife's Gio has a problem with batterydrain. It needs to be recharged after 10hours, but she isn't using the phone very active.
I've made a logfile with BetterBatteryStats, but the only thing I see is, that deep sleep is working fine...
Can some-one help me to find the problem? (phone is rooted, ROM is GingerDX)
Thanx!
===================
General Information
===================
BetterBatteryStats version: 1.12.0.0RC5
Creation Date: 2013-01-15 20:21:17
Statistic Type: Charged to Current
Since 8 h 56 m 28 s
VERSION.RELEASE: 2.3.7
BRAND: samsung
DEVICE: gio
MANUFACTURER: Samsung
MODEL: GT-S5660
OS.VERSION: 2.6.35.7-px-based-Kernel
bootloader: unknown
HARDWARE: gt-s5660
FINGERPRINT: samsung/cyanogen_gio/gio:2.3.7/Gingerbread/eng.marcin.20120920.161855:user/test-keys
ID: Gingerbread
TAGS: test-keys
USER: dqib
PRODUCT: cyanogen_gio
Radio: unknown
Rooted: false
============
Battery Info
============
Level lost [%]: 82 Bat.: 82% (100% to 18%) [9,2%/h]
Voltage lost [mV]: 1 (4-3) [0,1%/h]
===========
Other Usage
===========
Deep Sleep (): 7 h 27 m 59 s (26879 s) Ratio: 83,5%
Awake (): 1 h 28 m 28 s (5308 s) Ratio: 16,5%
Screen On (): 33 m 21 s (2001 s) Ratio: 6,2%
Phone On (): 13 m 52 s (832 s) Ratio: 2,6%
WiFi On (): 8 h 56 m 28 s (32188 s) Ratio: 100,0%
WiFi Running (): 3 h 7 m (11220 s) Ratio: 34,9%
No Data Connection (): 2 h 54 m 53 s (10493 s) Ratio: 32,6%
No or Unknown Signal (): 2 h 54 m 53 s (10493 s) Ratio: 32,6%
Poor Signal (): 10 m 28 s (628 s) Ratio: 1,9%
Good Signal (): 26 m 16 s (1576 s) Ratio: 4,9%
Screen dark (): 7 s (7 s) Ratio: 0,0%
Screen medium (): 33 m 14 s (1994 s) Ratio: 6,2%
=========
Wakelocks
=========
MdmDataReporter (com.mobidia.Android.mdm.My Data Manager): 15 m 45 s (945 s) Count:255 2,9%
GTALK_ASYNC_CONN (Google Services): 3 m 36 s (216 s) Count:56 0,7%
ActivityManager-Launch (Android-systeem): 1 m 19 s (79 s) Count:290 0,2%
*sync* (Google Services): 1 m 9 s (69 s) Count:128 0,2%
*sync* (com.google.Android.gm.Gmail): 1 m 5 s (65 s) Count:4 0,2%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterB atteryStats): 53 s (53 s) Count:27 0,2%
*WiFi* (Android-systeem): 52 s (52 s) Count:182 0,2%
AlarmManager (Android-systeem): 49 s (49 s) Count:815 0,2%
GSM (Kiezer): 48 s (48 s) Count:3 0,2%
FacebookService (com.facebook.katana.Facebook): 42 s (42 s) Count:8 0,1%
*sync* (com.facebook.katana.Facebook): 32 s (32 s) Count:9 0,1%
sleep_broadcast (Android-systeem): 23 s (23 s) Count:117 0,1%
RILJ (Kiezer): 22 s (22 s) Count:482 0,1%
GTALK_CONN (Google Services): 21 s (21 s) Count:582 0,1%
Checkin Service (Google Services): 21 s (21 s) Count:645 0,1%
sendinactive (com.whatsapp.WhatsApp): 10 s (10 s) Count:6 0,0%
AlarmClock (com.Android.deskclock.Klok): 8 s (8 s) Count:4 0,0%
*vibrator* (com.Android.deskclock.Klok): 8 s (8 s) Count:2 0,0%
SCREEN_FROZEN (Android-systeem): 8 s (8 s) Count:210 0,0%
Event Log Service (Google Services): 7 s (7 s) Count:158 0,0%
show keyguard (Android-systeem): 7 s (7 s) Count:197 0,0%
GpsLocationProvider (Android-systeem): 7 s (7 s) Count:50 0,0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.Android.gm.Gmail): 5 s (5 s) Count:7 0,0%
*network-location-cell-update* (Google Services): 5 s (5 s) Count:126 0,0%
LocationManagerService (Android-systeem): 3 s (3 s) Count:217 0,0%
MQTT (com.facebook.katana.Facebook): 3 s (3 s) Count:46 0,0%
SyncManagerHandleSyncAlarm (Android-systeem): 1 s (1 s) Count:65 0,0%
ActivityManager-Sleep (Android-systeem): 1 s (1 s) Count:844 0,0%
================
Kernel Wakelocks
================
"DPRAM" (): 28 m 47 s (1727 s) Cntc/wc/ec)2890/18/2890 5,4%
"MULTI_PDP" (): 23 m 57 s (1437 s) Cntc/wc/ec)147/0/147 4,5%
"PowerManagerService" (): 14 m 41 s (881 s) Cntc/wc/ec)1117/0/0 2,7%
"ar6k_wow" (): 9 m 21 s (561 s) Cntc/wc/ec)148/0/148 1,7%
"Radio-interface" (): 4 m 12 s (252 s) Cntc/wc/ec)277/0/0 0,8%
"alarm_rtc" (): 1 m 10 s (70 s) Cntc/wc/ec)190/0/32 0,2%
"bluesleep" (): 21 s (21 s) Cntc/wc/ec)43/43/43 0,1%
"alarm" (): 12 s (12 s) Cntc/wc/ec)610/0/0 0,0%
"sync_system" (): 12 s (12 s) Cntc/wc/ec)26/0/0 0,0%
"audio_pcm" (): 9 s (9 s) Cntc/wc/ec)20/0/0 0,0%
"adsp" (): 9 s (9 s) Cntc/wc/ec)18/0/0 0,0%
"gpio_kp" (): 3 s (3 s) Cntc/wc/ec)1178/14/0 0,0%
"prx_wake_lock" (): (0 s) Cntc/wc/ec)3/2/3 0,0%
"rpcrotuer_smd_xprt" (): (0 s) Cntc/wc/ec)5815/15/0 0,0%
"ar6k_suspend" (): (0 s) Cntc/wc/ec)373/0/0 0,0%
"ApmCommandThread" (): (0 s) Cntc/wc/ec)36/0/0 0,0%
"rpc_server" (): (0 s) Cntc/wc/ec)51/0/0 0,0%
"KeyEvents" (): (0 s) Cntc/wc/ec)55890/0/0 0,0%
"rpc_reply" (): (0 s) Cntc/wc/ec)-455/0/0 -0,0%
"mmc_delayed_work" (): (0 s) Cntc/wc/ec)803/0/0 0,0%
"rpc_read" (): (0 s) Cntc/wc/ec)1237/0/0 -0,0%
"event4-255" (system, de.djnilse.gdxUpdateNotify): (0 s) Cntc/wc/ec)15/0/0 0,0%
"deleted_wake_locks" (): (0 s) Cntc/wc/ec)75/0/0 0,0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
122,88 MHz (): 2 m 3 s 0,4%
245,76 MHz (): 1 m 11 s 0,2%
320 MHz (): 24 s 0,1%
480 MHz (): 32 s 0,1%
672 MHz (): 28 s 0,1%
787,2 MHz (): 25 s 0,1%
800 MHz (): 1 h 23 m 24 s 15,5%
Deep Sleep (): 7 h 27 m 59 s 83,5%
==================
Reference overview
==================
custom: null
Since charged: Reference ref_charged created 1 d 10 h 36 m 27 s (Wl: 2 elements; KWl: 32elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 8 elements)
Since screen off: Reference ref_screen_off created 1 d 19 h 31 m 25 s (Wl: 28 elements; KWl: 33elements; NetS: null; Alrm: null; Proc: 14 elements; Oth: 12 elements; CPU: 8 elements)
Since unplugged: Reference ref_unplugged created 1 d 10 h 36 m 23 s (Wl: 0 elements; KWl: 32elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 8 elements)
Since boot: null
I think you turn on the wifi for so long. Wifi drains quite a lot of battery. For me, even I turn on wifi and do nothing, it can only stand for about 9 to 10 hours (it depends) and the battery level drops from 100% to less than 15%.
Also, it seems that quite often there is no signal. As I know, when there is poor or no signal, the phone will keep on searching for signal and it will drain battery.
Re: [Q] Battrydrain, analyse with BetterBatterijStats
If I disable Wi-Fi, Bluetooth and GPS, why should I have a smartphone? I also have a gio with the same rom but my battery isn't draining that fast...
Re: [Q] Battrydrain, analyse with BetterBatterijStats
Why would you turn it off?
Because Gio has the same problem as all other smartphones: a bad battery life.
If you leave your wifi, bluetooth and GPS on all the time; even when you're not using it, your battery will quickly get drained.
If your battery gets drained too fast,
You have 3 options.
1) Turn these things off when you're not using them.
2) Buy a bigger battery.
3) Buy a 'regular' phone
At the moment smartphone equals bad batterylife.
And it will stay like this for a while,
Until scientists come up with a better type of battery.
Sent from my GT-S5660 using xda app-developers app
Re: [Q] Battrydrain, analyse with BetterBatterijStats
I know it's just a cheap phone, but before flashing the rom the phone worked without charging for 14 hours. That is enough, but now it's hard to get 10 hours...
So I hope to find what causes the battery drain.
download setcpu so if you screen is of it you less battery the best setup : 245/245 or something like that
Re: [Q] Battrydrain, analyse with BetterBatterijStats
Wifi is not the problem. Im not a battery expert but it looks to me that the phone stays at top CPU 800MHz for way too long since the phone you said your wife doesnt quite use it that much.. Also signal might be your problem there buddy! Too much time without signal. And as someone here said it can burn your battery really fast!
From my experience even though my phone has great battery life i keep it running as slow as possible and as stable as it can get. I set my CPU to not pass 810MHz, i could use 1500MHz but my battery wont stay as long as it does on 810Mhz. And it runs the same just a liiiitlle laggier. Not that much of a big deal since my goal is to save battery.
Remember to turn off blutooth, gps, wifi WHEN NOT USED. You can use Wifi when ever you can. And it will save battery as your phone is not searching for 2g,3g signal
Try it and report back.
Sent from my SPH-L710 using xda premium
Re: [Q] Battrydrain, analyse with BetterBatterijStats
All you need to know do is:
- to switch to airplane mode when being in limited service areas
- you can install the cpu tweak mentioned above to set a costom freq when the screen is off
- use gps, bluethoot only when needed
- data network also drains battery in restricted or low signal areas
- watch the apps recently installed, maybe it drains your battery from background
- disable autosync, you can do it manual when using wifi.
Sent from my GT-S5660 using xda premium
warface123 said:
download setcpu so if you screen is of it you less battery the best setup : 245/245 or something like that
Click to expand...
Click to collapse
I downloaded setcpu, but don't know which setting to change Can you help me with that program?
mar.ioo said:
Wifi is not the problem. Im not a battery expert but it looks to me that the phone stays at top CPU 800MHz for way too long since the phone you said your wife doesnt quite use it that much.. Also signal might be your problem there buddy! Too much time without signal. And as someone here said it can burn your battery really fast!
From my experience even though my phone has great battery life i keep it running as slow as possible and as stable as it can get. I set my CPU to not pass 810MHz, i could use 1500MHz but my battery wont stay as long as it does on 810Mhz. And it runs the same just a liiiitlle laggier. Not that much of a big deal since my goal is to save battery.
Remember to turn off blutooth, gps, wifi WHEN NOT USED. You can use Wifi when ever you can. And it will save battery as your phone is not searching for 2g,3g signal
Try it and report back.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I don't think it's a good idea to lower the maximum CPU-frequency, because maximum is 800mhz. So it is a quite slow phone, lowering the maximum frequency will be to slow
GPS and Wifi is turned off, wifi stays on because my wife is mostly at home.
melch123 said:
All you need to know do is:
- to switch to airplane mode when being in limited service areas <-- mostly at home
- you can install the cpu tweak mentioned above to set a costom freq when the screen is off <-- see above
- use gps, bluethoot only when needed <-- already done
- data network also drains battery in restricted or low signal areas <-- normaly at wifi
- watch the apps recently installed, maybe it drains your battery from background <-- less apps than my Gio, so I think it can't be the problem
- disable autosync, you can do it manual when using wifi. <-- only sync gmail, facebook and whatsapp
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
See my answers in red above
Related
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
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
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