SGSII Battery Drain - Galaxy S II Q&A, Help & Troubleshooting

Hi,
Since 6 months i have a big battery drain issue with my i9100. I have tried changing my kernel, ROM, baseband, battery, whatever, this f**king drain is still here.
I joined some screenshots of my battery usage, which is (for me) pretty stange because i haven't used alot my phone today.
And the Better Battery Stats log :
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0_RC1
Creation Date: 2013-11-18 18:39:38
Statistic Type: Unplugged to Current
Since 11 h 49 m 32 s
VERSION.RELEASE: 4.3.1
BRAND: Samsung
DEVICE: GT-I9100
MANUFACTURER: samsung
MODEL: GT-I9100
OS.VERSION: 3.0.64-CM-g7b9279e
BOOTLOADER: unknown
HARDWARE: smdk4210
FINGERPRINT: samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPQ:user/release-keys
ID: JLS36I
TAGS: test-keys
USER: jenkins
PRODUCT: GT-I9100
RADIO: I9100XXMS3
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -58% (100% to 42%) [4,9%/h]
Voltage lost [mV]: (4194-3728) [39,4%/h]
===========
Other Usage
===========
Deep Sleep (): 8 h 13 m 24 s (29604 s) Ratio: 69,5%
Awake (): 3 h 36 m 7 s (12967 s) Ratio: 30,5%
Screen On (): 28 m 4 s (1684 s) Ratio: 4,0%
Phone On (): 2 m 39 s (159 s) Ratio: 0,2%
Wifi On (): 2 h 32 m 21 s (9141 s) Ratio: 21,5%
Wifi Running (): 2 h 32 m 21 s (9141 s) Ratio: 21,5%
No Data Connection (): 34 m 21 s (2061 s) Ratio: 4,8%
No or Unknown Signal (): 34 m 21 s (2061 s) Ratio: 4,8%
Poor Signal (): 1 m 26 s (86 s) Ratio: 0,1%
Moderate Signal (): 2 h 54 m 42 s (10482 s) Ratio: 14,0%
Good Signal (): 7 h 48 m 10 s (28090 s) Ratio: 37,5%
Screen dark (): 9 m 7 s (547 s) Ratio: 1,3%
Screen dimmed (): 18 m 56 s (1136 s) Ratio: 1,5%
=========
Wakelocks
=========
NlpCollectorWakeLock (Services Google): 27 m 48 s (1668 s) Count:6854 3,9%
NlpWakeLock (Services Google): 13 m 3 s (783 s) Count:2651 1,8%
LocationManagerService (Système Android): 4 m 27 s (267 s) Count:777 0,6%
FbClientConnManager (com.facebook.katana.Facebook): 2 m 33 s (153 s) Count:111 0,4%
WakefulIntentService[GCoreUlr-LocationReportingService] (Services Google): 2 m 18 s (138 s) Count:6081 0,3%
WakefulIntentService[GCoreUlr-LocationReceiverService] (Services Google): 2 m 15 s (135 s) Count:7970 0,3%
PhoneApp (Téléphone): 1 m 45 s (105 s) Count:6 0,2%
AudioOut_2 (1013): 1 m 33 s (93 s) Count:21 0,2%
RILJ (Téléphone): 1 m 29 s (89 s) Count:5596 0,2%
AlarmManager (Système Android): 1 m 25 s (85 s) Count:2036 0,2%
ActivityManager-Launch (Système Android): 51 s (51 s) Count:869 0,1%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (com.google.android.apps.plus.Google+): 33 s (33 s) Count:10 0,1%
GsmConnection (Téléphone): 28 s (28 s) Count:139 0,1%
AlarmManager (Services Google): 26 s (26 s) Count:5353 0,1%
*sync*_com.evernote.evernoteprovider_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.evernote} (com.evernote.Evernote): 19 s (19 s) Count:15 0,0%
SyncService (com.evernote.Evernote): 15 s (15 s) Count:8 0,0%
StartingAlertService (com.android.calendar.Agenda): 15 s (15 s) Count:3 0,0%
NlpLocationReceiverService (Services Google): 13 s (13 s) Count:4139 0,0%
*sync*_com.android.calendar_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (com.google.android.syncadapters.calendar.Synchronisation de Google Agenda): 11 s (11 s) Count:5 0,0%
*vibrator* (Système Android): 11 s (11 s) Count:1181 0,0%
*sync*_subscribedfeeds_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 9 s (9 s) Count:2675 0,0%
*sync*_com.google.android.location.reporting_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 8 s (8 s) Count:2822 0,0%
show keyguard (Système Android): 8 s (8 s) Count:28 0,0%
Checkin Service (Services Google): 8 s (8 s) Count:6221 0,0%
LocationManagerService (Services Google): 7 s (7 s) Count:6060 0,0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Stockage de l'agenda): 7 s (7 s) Count:248 0,0%
AlarmManager (com.facebook.katana.Facebook): 6 s (6 s) Count:949 0,0%
*backup* (Système Android): 6 s (6 s) Count:1216 0,0%
ServiceStateTracker (Téléphone): 5 s (5 s) Count:134 0,0%
*sync*_com.android.contacts_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 5 s (5 s) Count:4141 0,0%
AlarmManager (com.android.providers.calendar.Stockage de l'agenda): 5 s (5 s) Count:124 0,0%
ezl (Services Google): 4 s (4 s) Count:8672 0,0%
fullsync (com.whatsapp.WhatsApp): 4 s (4 s) Count:24 0,0%
Event Log Service (Services Google): 3 s (3 s) Count:6910 0,0%
*sync*_com.android.browser_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 3 s (3 s) Count:5354 0,0%
GCM_CONN_ALARM (Services Google): 3 s (3 s) Count:2819 0,0%
*sync*_com.google.android.gms.people_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (Services Google): 3 s (3 s) Count:1 0,0%
NetworkStats (Système Android): 2 s (2 s) Count:73 0,0%
SyncLoopWakeLock (Système Android): 2 s (2 s) Count:2206 0,0%
ActivityManager-Sleep (Système Android): 2 s (2 s) Count:2067 0,0%
AlarmClock (com.android.deskclock.Horloge): 2 s (2 s) Count:128 0,0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 2 s (2 s) Count:7 0,0%
ConnectivityService (Système Android): 2 s (2 s) Count:2037 0,0%
WakefulIntentService[GCoreUlr-SettingsChangedService] (Services Google): 2 s (2 s) Count:2674 0,0%
GOOGLE_C2DM (Services Google): 2 s (2 s) Count:6864 0,0%
AlarmManager (Téléphone): 2 s (2 s) Count:243 0,0%
MQTT (com.facebook.katana.Facebook): 2 s (2 s) Count:139 0,0%
*sync*_com.google.android.ears.heard.EarsContentProvider_Account {name=7d38f97cfa71a0938b1fd1884aaa2f5e, type=com.google} (com.google.android.ears.Recherche audio pour Google Play): 1 s (1 s) Count:1 0,0%
GCM_CONN (Services Google): 1 s (1 s) Count:6951 0,0%
Checkin Handoff (Services Google): 1 s (1 s) Count:2815 0,0%
AlarmManager (com.whatsapp.WhatsApp): 1 s (1 s) Count:23 0,0%
SyncManagerHandleSyncAlarm (Système Android): 1 s (1 s) Count:904 0,0%
SCREEN_FROZEN (Système Android): 1 s (1 s) Count:936 0,0%
RingtonePlayer (com.android.systemui.IU système): 1 s (1 s) Count:17 0,0%
GpsLocationProvider (Système Android): 1 s (1 s) Count:912 0,0%
================
Kernel Wakelocks
================
"multipdp" (): 1 h 25 m 2 s (5102 s) Cntc/wc/ec)662/0/662 6,8%
"deleted_wake_locks" (): 1 h 19 m 30 s (4770 s) Cntc/wc/ec)98765/0/3176 6,4%
"PowerManagerService.WakeLocks" (): 53 m 53 s (3233 s) Cntc/wc/ec)6734/0/0 7,6%
"secril_fd-interface" (): 50 m 35 s (3035 s) Cntc/wc/ec)986/0/0 4,1%
"l2_hsic" (): 44 m 27 s (2667 s) Cntc/wc/ec)7098/530/7098 6,3%
"radio-interface" (): 30 m 44 s (1844 s) Cntc/wc/ec)1978/0/0 4,3%
"umts_ipc0" (): 27 m 28 s (1648 s) Cntc/wc/ec)3506/0/3506 3,9%
"alarm_rtc" (): 16 m 20 s (980 s) Cntc/wc/ec)1708/0/325 2,3%
"sec-battery-monitor" (): 10 m 25 s (625 s) Cntc/wc/ec)1826/1138/0 1,5%
"rpm_hsic" (): 8 m 40 s (520 s) Cntc/wc/ec)5039/0/0 1,2%
"alarm" (): 4 m 31 s (271 s) Cntc/wc/ec)2716/4/0 0,6%
"tx_hsic" (): 4 m 30 s (270 s) Cntc/wc/ec)31790/5/0 0,6%
"PowerManagerService.Display" (): 2 m 23 s (143 s) Cntc/wc/ec)47/0/0 0,3%
"power-supply" (): 15 s (15 s) Cntc/wc/ec)1800/0/0 -0,1%
"prx_wake_lock" (): 13 s (13 s) Cntc/wc/ec)8/0/8 0,0%
"PowerManagerService.Broadcasts" (): 12 s (12 s) Cntc/wc/ec)94/0/0 0,0%
"secril_fmt-interface" (): 12 s (12 s) Cntc/wc/ec)17916/0/0 0,0%
"sync_system" (): 5 s (5 s) Cntc/wc/ec)51/0/0 0,0%
"unknown_wakeups" (): 1 s (1 s) Cntc/wc/ec)4/0/4 0,0%
"mmc1_detect" (): 1 s (1 s) Cntc/wc/ec)2245/0/0 0,0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)2245/0/0 0,0%
"KeyEvents" (): (0 s) Cntc/wc/ec)13397/0/0 0,0%
"client-interface" (): (0 s) Cntc/wc/ec)20/0/0 0,0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1,2 GHz (): 9 m 2 s 1,3%
1 GHz (): 41 s 0,1%
800 MHz (): 20 m 32 s 2,9%
500 MHz (): 27 m 37 s 3,9%
200 MHz (): 2 h 38 m 13 s 22,3%
Deep Sleep (): 8 h 13 m 24 s 69,5%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 8 h 59 m 28 s (Wl: 0 elements; KWl: 27elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 6 elements)
ref_charged: Reference ref_charged created 8 h 59 m 28 s (Wl: 0 elements; KWl: 27elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 6 elements)
ref_current: Reference ref_current created 20 h 49 m (Wl: 55 elements; KWl: 29elements; NetS: null; Alrm: null; Proc: 22 elements; Oth: 13 elements; CPU: 6 elements)
Hope you can help me with this, i'ts pretty annoying and it never drained battery like that. I've powered it up only for checking hour/sending a SMS, not for playing games or stuff like that...
Thanks
(And sorry for my english, as you can see, i'm French )

---

Have you tryed to see if phone is going to deep sleep. It may be a cause for that. There are apps that can tell you that.

---

Yep, that seems correct (70% of deep sleep checked with CPUSpy) and that's also on the BetterBatteryStats log

---

11 hours seem pretty good to me, please take note that you are on a nightly ROM, battery consumption can increase or decrease, no one can know what will happen on a nightly ROM, if you want to watch your battery consumption you should flash a stock rom first because that will be your medium. That said, there are no problems with 11 hour battery life and still %41 at all.

---

How is the radio signal in your area? That has a massive influence on battery performance.

---

If you have a radio signal problem, you can try disabling fast dormancy, pretty easy with this app: https://play.google.com/store/apps/details?id=com.gokhanmoral.fastdormancytoggle.i9300&hl=en_GB

---

11 hours is yes, pretty good if I use a little bit my phone.
The problem is that my battery is drained even if my phone is locked and stay in my pocket.
I tried to let it locked for a night when I was sleeping, un-plugged it when he was at 100%, didn't set an alarm, and zero app loaded in RAM.
For 10 hours of sleep, my phone drained about 50 percents of battery.
So the problem is not my use, it's the phone itself.
Don't ****ing know where the problem can be, but today I saw this in BBS.

---

Something is keeping your phone awake. You can take a look at this app: https://play.google.com/store/apps/details?id=com.rootuninstaller.batrsaver
Or you can wipe everything and flash a new rom, since we have no idea what causes this.

---

6th time that I change my ROM, and does nothing. I'll try to get @Stock with the aaaa-weeee-sssooome (lulz) TouchWiz laggy stock rom, and i'll try to see if that changes something...

---

Dakura said:
Something is keeping your phone awake. You can take a look at this app: https://play.google.com/store/apps/details?id=com.rootuninstaller.batrsaver
Or you can wipe everything and flash a new rom,
Click to expand...
Click to collapse
These battery savers are less helpful. These just turn off radio on scheduled time and does not prevent culprit app from draing battery which actually is required to save battery. the apps which actually are helpful for conserving battery can be found here under battery section.
since we have no idea what causes this.
Click to expand...
Click to collapse
I agree because there are many factors which are responsible for drainage of battery and with couple of screenshots, one can hardly figure what exactly the problem is.
I could have described those factors in detail but this is not a correct place to do so.
crystaldabuu said:
11 hours is yes, pretty good if I use a little bit my phone.
The problem is that my battery is drained even if my phone is locked and stay in my pocket.
I tried to let it locked for a night when I was sleeping, un-plugged it when he was at 100%, didn't set an alarm, and zero app loaded in RAM.
For 10 hours of sleep, my phone drained about 50 percents of battery.
So the problem is not my use, it's the phone itself.
Don't ****ing know where the problem can be, but today I saw this in BBS.
Click to expand...
Click to collapse
Buddy from the information and screenshot you have shared, I would say network is one of the reason or main reason in drainage of your battery. What you can do to minimize this is, avoid keeping your device where strength of network is less. Fluctuations in network contributes very much in drainage of battery. Also if you will keep data mode on and turn off the screen then too it will awake your cpu at regular intervals. So no matter your screen is off, you will face battery drain. Also when not needed, stay at 2G as 3G with data mode on, drains battery very much.
There may be/may not be other factors but this network factor is certainly there. You should keep your device on flight mode and see if battery drains highly!
Hope this helps

---

Nobody who's posted to this thread so far has mentioned the ****load of wakelocks in the BBS stats (I.E the bleeding obvious). You have a ton of them. This is causing the drain you're seeing.
OP - If you really want to resolve this, post your BBS stats to the BBS thread on here & ask for help there, people who post to that thread regularly should be able to help you you. If you keep posting to this thread at the current rate, you'll still be running round in circles in a month's time.

---

Thank you, i'll try this
-> Tryed to switch off Fast Dormancy, didn't noticed any change... so... useless option with my carrier, who, I think, doesn't allow his antennas to be compatible with this thing

---

Hi,
I update this thread because i have resolved my problems... and they came back in two days.
I flashed a new Rom, Cyanogenmod 10.2, and my battery was fine on tuesday (It looked like this https://pbs.twimg.com/media/BawCU2pIUAAJyrj.png:large).
1 day after, tadaam! battery drain came back. https://pbs.twimg.com/media/BawCdu0IcAAHUmC.png:large
Help me please, i really need this phone working.
I have looked around baseband/RIL problems.
I want to test another baseband but I can't choose one, I live in a town where the reception is good, my actual baseband is the i9100XXMS3.
I'm in 10.2 with DorimanX kernel.
Can you advise me one please ?
Thanks