Related
New to the SG2 and first ROM I flashed is darkside evolution. I love it so far but had a question about the battery life. I usually unplug my phone around 7am and by the time I get home from work (5:45 pm) I am at about 30% battery. I only use the phone to chat, web, and email when I get the chance without being on wifi.
I am reading that people are getting good battery life from this ROM and want to know what your % battery you have remaining at the end of the day.
Over the exact same timeframe, I ended the day with maybe 60-65% yesterday with Bluetooth on the whole day and infrequent usage.
I was on the same ROM before and I can say that I had very similar battery life as yours, around 30% after around 10 hrs and 2 hrs display on time. Battery use is a very subjective matter and I have seen other posts where battery life far exceeded my experiences. I was overall very happy though as the battery life was the same, if not better than stock. With the added performance improvements from the ROM it is very reasonable.
Sent from my SGH-T989D using xda premium
Don't forget if you don't have good reception, it takes a huge toll on your battery life
Sent from my SGH-T989 using xda premium
I started having a problem yesterday, but I've been tinkering with my stuff a lot for my theme... The problem is it won't deep sleep and I can't figure out why...
this is my BetterBatteryStats log:
Code:
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-05-10 12:50:04
Statistic Type: (3) Since Unplugged
Since 56 m 11 s
VERSION.RELEASE: 4.0.3
BRAND: samsung
DEVICE: SGH-T989
MANUFACTURER: samsung
MODEL: SGH-T989
BOOTLOADER: unknown
FINGERPRINT: samsung/SGH-T989/SGH-T989:4.0.3/IML74K/UVLC8:user/release-keys
HARDWARE: qcom
ID: IML74K
TAGS: release-keys
USER: thederekjay
PRODUCT: SGH-T989
RADIO: T989UVLC8
Rooted: true
===========
Other Usage
===========
Awake (): 56 m 11 s (3371 s) Ratio: 100.0%
Good Signal (): 52 m 15 s (3135 s) Ratio: 93.0%
Screen On (): 13 m 43 s (823 s) Ratio: 24.4%
Phone On (): 24 s (24 s) Ratio: 0.7%
No Data Connection (): 7 s (7 s) Ratio: 0.2%
No or Unknown Signal (): 7 s (7 s) Ratio: 0.2%
=========
Wakelocks
=========
AlarmManager (Android System): 2 m 20 s (140 s) Count:285 4.2%
AudioOut_1 (1013): 1 m 6 s (66 s) Count:23 2.0%
SMSDispatcher (Phone): 41 s (41 s) Count:10 1.2%
ActivityManager-Launch (Android System): 32 s (32 s) Count:193 1.0%
RILJ (Phone): 24 s (24 s) Count:261 0.7%
NetworkStats (Android System): 17 s (17 s) Count:105 0.5%
MediaScannerService (Media): 14 s (14 s) Count:2 0.4%
DownloadManager (Media): 6 s (6 s) Count:3 0.2%
StartingAlertService (com.concentriclivers.mms.com.android.mms.Messaging): 5 s (5 s) Count:18 0.2%
sleep_broadcast (Android System): 5 s (5 s) Count:36 0.2%
GSM (Phone): 4 s (4 s) Count:22 0.1%
show keyguard (Android System): 4 s (4 s) Count:50 0.1%
FastDormancy (Phone): 2 s (2 s) Count:20 0.1%
GpsLocationProvider (Android System): 2 s (2 s) Count:3 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 1 s (1 s) Count:3 0.1%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 s (1 s) Count:23 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:309 0.0%
================
Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cnt:(c/wc/ec)1/1/1 100.0%
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0
Click to expand...
Click to collapse
Im stumped.
Teo032 said:
Don't forget if you don't have good reception, it takes a huge toll on your battery life
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
how so?
Akim1220 said:
how so?
Click to expand...
Click to collapse
The radios working a lot harder. It will drain a lot faster with bad reception
Well I have great reception and I just flashed blaze radio noticed my battery draining faster
Sent from my SGH-T989 using xda premium
peppersu812 said:
Well I have great reception and I just flashed blaze radio noticed my battery draining faster
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Generally, crappy reception means crappy battery.
Touch Recovery brakes the Deep Sleep
I had the exact same problem using DarkSide ROM.
I read that Touch recovery has a buggy that kills the Deep Sleep. So I went and flashed the ROM with Non-Touch recovery and Voilá...
Deep Sleep is back working like a charm.
I advise you all that are having battery issues to try to use Non-Touch recovery to flash this ROM.
This is where I read it:
http://forum.xda-developers.com/showpost.php?p=25771623&postcount=5
I had wifi and data on most of the time and i got my phone to go for 17 hours and I'm at 30% right now. I've had the rom installed for 2-3 days and gone through 2 charge cycles from 100 to 0 and then recharge.
how important is it too do the charge cycles and how do you check what type of recovery you have? also, what app did you use to see if your battery was sleeping?
im only getting 6 hours of battery life using juggernaut and darkside kernal. what could the problem be here guys?
Sent from my SGH-T989 using XDA
I have had great battery life. With light use right now(send text messages all day on the phone for 5 minutes) I am at 75% for 12 hours. Under moderate to heavy use after 12 hours I am at 50%. I keep wifi and GPS on the whole time and the screen to max brightness.
blkbltwrestler said:
I have had great battery life. With light use right now(send text messages all day on the phone for 5 minutes) I am at 75% for 12 hours. Under moderate to heavy use after 12 hours I am at 50%. I keep wifi and GPS on the whole time and the screen to max brightness.
Click to expand...
Click to collapse
are you running darkside evolution>?
Akim1220 said:
how important is it too do the charge cycles and how do you check what type of recovery you have? also, what app did you use to see if your battery was sleeping?
Click to expand...
Click to collapse
When you boot into cwm it will say what version you have. CPU spy to check CPU states.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Akim1220 said:
are you running darkside evolution>?
Click to expand...
Click to collapse
yep beta 2
phoenix6 said:
I started having a problem yesterday, but I've been tinkering with my stuff a lot for my theme... The problem is it won't deep sleep and I can't figure out why...
this is my BetterBatteryStats log:
Im stumped.
Click to expand...
Click to collapse
just saw this on my phone. go to system settings -> developr options and make sure stay awake is not checked.
Hey everyone,
About three weeks ago I noticed that my battery appeared to drain much quicker than before while running Calks 1.7 GB rom on EL26. I figured that this could just have been a bug so I upgraded to his 1.6 ICS 4.04 ROM flashing through recovery. However, this did not alleviate the issue. When I investigated this further it appeared that the phone is unable to efficiently enter a deep sleep. I have disabled all sync's and have no apps installed. After a full charge I get about 6 hours of battery life without using my phone once (and also in airplane mode). The Android OS kernel takes up 99% of the CPU usage. I downloaded Better Battery Stats and created a dump file here:
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-07-03 11:54:55
Statistic Type: (3) Since Unplugged
Since 5 h 24 m 31 s
VERSION.RELEASE: 4.0.4
BRAND: samsung
DEVICE: SPH-D710
MANUFACTURER: samsung
MODEL: SPH-D710
BOOTLOADER: unknown
FINGERPRINT: samsung/SPH-D710/SPH-D710:4.0.4/IMM76I/FE22:user/release-keys
HARDWARE: smdk4210
ID: IMM76I
TAGS: release-keys
USER: se.infra
PRODUCT: SPH-D710
RADIO: S710.10 S.FF18
Rooted: true
===========
Other Usage
===========
Awake (): 3 h 49 m 23 s (13763 s) Ratio: 70.7%
Deep Sleep (): 1 h 35 m 2 s (5702 s) Ratio: 29.3%
No Data Connection (): 1 h 19 m 46 s (4786 s) Ratio: 24.6%
No or Unknown Signal (): 1 h 19 m 46 s (4786 s) Ratio: 24.6%
Screen On (): 42 m 33 s (2553 s) Ratio: 13.1%
=========
Wakelocks
=========
AudioOut_1 (1013): 14 m 8 s (848 s) Count:158 4.4%
DownloadManager (Media): 1 m 24 s (84 s) Count:1 0.4%
ActivityManager-Launch (Android System): 47 s (47 s) Count:250 0.2%
Starting CM_VnoteService (com.coremobility.app.vnotes.Voicemail): 30 s (30 s) Count:8 0.2%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 29 s (29 s) Count:10 0.2%
sleep_broadcast (Android System): 22 s (22 s) Count:348 0.1%
AlarmManager (Android System): 19 s (19 s) Count:869 0.1%
show keyguard (Android System): 12 s (12 s) Count:34 0.1%
*sync*_gmail-ls_Account {[email protected]#[email protected]#%@@gmail.com, type=com.google} (com.google.android.gm.Gmail): 11 s (11 s) Count:4 0.1%
RILJ (Phone): 11 s (11 s) Count:373 0.1%
SCREEN_FROZEN (Android System): 6 s (6 s) Count:364 0.0%
*sync*_subscribedfeeds_Account {name=%^&%^@gmail.com, type=com.google} (Google Services): 6 s (6 s) Count:3 0.0%
GTALK_CONN (Google Services): 6 s (6 s) Count:183 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 3 s (3 s) Count:3 0.0%
SyncLoopWakeLock (Android System): 3 s (3 s) Count:926 0.0%
Browser (com.android.browser.Internet): 3 s (3 s) Count:1 0.0%
[email protected]#[email protected]#[email protected]/android_talk487cab5da65a (Google Services): 2 s (2 s) Count:16 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 s (2 s) Count:196 0.0%
keyguardWakeAndHandOff (Android System): 1 s (1 s) Count:422 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 1 s (1 s) Count:254 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:14 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:913 0.0%
NetworkStats (Android System): 1 s (1 s) Count:61 0.0%
NotificationService (Android System): 1 s (1 s) Count:380 0.0%
================
Kernel Wakelocks
================
"sec-battery-monitor" (): 1 h 56 m 52 s (7012 s) Cntc/wc/ec)5717/5271/0 36.0%
"event3-1954" (): 1 h 54 m 19 s (6859 s) Cntc/wc/ec)5524/0/0 15.1%
"event1-1954" (): 1 h 53 m 15 s (6795 s) Cntc/wc/ec)5592/12/0 34.9%
"event0-1954" (): 1 h 53 m 11 s (6791 s) Cntc/wc/ec)5465/0/0 14.9%
"event2-1954" (): 1 h 53 m 10 s (6790 s) Cntc/wc/ec)31772/0/0 14.9%
"radio-interface" (): 7 m 38 s (458 s) Cntc/wc/ec)620/0/0 2.4%
"alarm" (): 5 m 33 s (333 s) Cntc/wc/ec)464/3/0 1.7%
"PowerManagerService" (): 2 m 42 s (162 s) Cntc/wc/ec)1042/0/0 0.8%
"event7-1954" (): 1 m 27 s (87 s) Cntc/wc/ec)6064/0/0 0.2%
"alarm_rtc" (): 1 m 14 s (74 s) Cntc/wc/ec)115/0/36 0.4%
"AudioOutLock" (): 36 s (36 s) Cntc/wc/ec)245/0/0 0.1%
"KeyEvents" (): 24 s (24 s) Cntc/wc/ec)31310/0/0 0.1%
"DPRAM_PWDOWN" (): 17 s (17 s) Cntc/wc/ec)12133/111/0 0.1%
"sync_system" (): 7 s (7 s) Cntc/wc/ec)44/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)5536/0/1 0.0%
"client-interface" (): (0 s) Cntc/wc/ec)6908/0/0 0.0%
"event8-1954" (): (0 s) Cntc/wc/ec)357981/0/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.gsf (): Wakeups: 77
Alarms: 4, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 19, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 29, Intent: com.google.android.intent.action.SEND_IDLE
com.android.providers.calendar (): Wakeups: 29
Alarms: 27, Intent: com.android.providers.calendar.intent.CalendarProvider2
Alarms: 1, Intent: com.android.providers.calendar.SCHEDULE_ALARM
Alarms: 1, Intent: android.intent.action.EVENT_REMINDER
com.google.android.apps.maps (): Wakeups: 25
android (): Wakeups: 22
Alarms: 758, Intent: android.intent.action.TIME_TICK
Alarms: 25, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 75, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 1, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
Alarms: 1, Intent: android.app.backup.intent.RUN
Alarms: 21, Intent: android.content.syncmanager.SYNC_ALARM
com.coremobility.app.vnotes (): Wakeups: 5
Alarms: 5, Intent: com.coremobility.app.vnotes.SERVICE_DOPROCESS
com.android.phone (): Wakeups: 5
Alarms: 5, Intent: com.android.internal.telephony.cdma-reconnect
com.swype.android.inputmethod (): Wakeups: 1
Any ideas as to why I am only getting 5hr and 24 minutes from a full charge? I have tried different modems and ROMS but nothing has worked. Thanks!
Screen shots would of done the job......
Turn off sync and you can use juice defender pro to help you get better battery
Sent from my SPH-D710 using Tapatalk 2
daniel4653 said:
Screen shots would of done the job......
Turn off sync and you can use juice defender pro to help you get better battery
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Horrible reply for xda, your post looks like a Yahoo answers reply. You didn't even read what he wrote.
To op, if you are not using your phone as your post says, you definitely are installing a rogue app as your phone was awake for over 3 hours. Have you tried wiping? Also, battery monitor, whatever that is, appears to be significantly keeping your phone awake. Finally, it appears from the info above your phone was not in airplane mode the whole time as you suggest.
Also, on ics you can view data usage on a per app basis in the settings. Post a screen cap of that screen.
Sent from my SPH-D710 using Tapatalk 2
Duplicate
BetterBatteryStats is designed to help only if you leave the phone on battery for a minimum of 2-3 hours (overnight is better) without using it at all. This will give you & us an accurate reading of what the phone is doing while it is supposed to be sleeping.
tdunham said:
BetterBatteryStats is designed to help only if you leave the phone on battery for a minimum of 2-3 hours (overnight is better) without using it at all. This will give you & us an accurate reading of what the phone is doing while it is supposed to be sleeping.
Click to expand...
Click to collapse
So just let the phone die if I leave it unplugged during the night? It is only lasting 6 hours remember.
sweatynipples said:
So just let the phone die if I leave it unplugged during the night? It is only lasting 6 hours remember.
Click to expand...
Click to collapse
Ok, sorry forgot. LOL
Well, from a full charge, let it sit for 2-3 hrs (I know, its tough) without touching it and post the log then.
Is this a brand new phone btw and are you giving the roms a chance to settle in for a couple/three days before judging battery life? The first day or two typically suck after flashing a new rom.
Edit: Oh, and being on ICS is definitely not going to help your battery situation. The GB rom is way more efficient. You may want to consider going back (the proper way, by odin EL26 stock kernel by Chris41G) and doing a fresh format and install.
Well, it seems that my issue with the battery drain is resolved. It appears that the phone was constantly waking up because of a glitch in the USB, making the phone repeatedly turn on and think it is in car mode. This glitch also prevented the phone from recognizing the USB every so often for charging. I took a q-tip and gently wiped down the connectors inside the port and it seems to have made a more secure connection. I now get 20+ hours on a full charge with limited use, and the phone is going into a deep sleep.
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%
=========
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
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.