[Galaxy S II Q&A, Help & Troubleshooting] DaKiller147:
Hello

First of all, sorry of any bad or wrong english, it's not my native language.

I have a very annoying wakelocks problem with my I9100T.

My carrier is Pelephone (Israel), I bought the device about a year and a half ago.

A few months after I got it, I decided to root and to flash a different rom.

I've had many roms since them, mostly stock-based, but I've tried a few AOKPs too.

The problem is basically this:

No matter what rom or what kernel or what modem I install, battery is terrible. With the help of BBS I was able to learn that the cause of this is excessive wakelocks, mostly RILJ, radio-interface, l2_hsic and umts-ipc0. This causes an extreme battery drain, 25%-35% drain in a 7-hour sleep night with wifi/3g/bt/gps/background apps all off and no body touching the device. It is extremely frustrating and makes the phone useless as of the everexisting fear of battery running out.

I've tried tens of different roms, Stock-based (Villain, Neat, Litening, WanamLite, Alliance and a few others I can't remember), AOKP-based (The only one I remember by name is ResurrectionRemix 2.6/2.6.1 and a few JB releases too) across different versions of android.

Tried them with the default kernel, with CF kernel, siyah, phenomenal, dorimanx.

Tried 10+ different modems including 3 extracted from my carrier's official roms (JJKF3, JJKI2 JJLP8).

All of them have the same exact issue.

Only time I remember not having this issue is with old GB roms. CheckROM V4/V6 did not have any battery problems, battery was perfect.

Also Litening rom V6.1 XXKH3, dates as back as aug 11'. Battery was badass there.

I've tried using the phone without restoring anything, tried freezing everything that I don't need, tried even freezing anything that is not necessary for the phone to run (eventually had a phone with no SMS/phone abilities, no play store, no syching, no properly working bluetooth/wifi connections) and still wakelocks occured.

When I first switched to ICS, I also had a 'MediaServer' wakelock, fixed by deleting 'corrupt' files from sd/external. The RILJ, radio-interface, l2_hsic and umts-ipc0 remained and I can't find a conclusive cause/solution.

Fast dormancy is not supported so I always turn it off via *#9900#, or that app for AOKP roms.

I remember a rom in which turning on/off airplane mode would help for a few hours. Then the wakelock returns. Haven't tried it recently, it doesn't quite solve the problem anyway so why bother with it.

I've noticed BBS showing "No or unknown signal" and "No data connection" at 100% time, which is weird.

Recently tried WanamLite/VK based on XXLSJ 4.1.2 leaked stock firmware, same problem.

Finally after some more research here in XDA I've tried to fix RIL/modem mismatch with GetRIL. I have flashed WanamLite 12.8, installed RIL via GetRIL so now it says "RIL/Baseband is matching". A quick look at BBS and battery history still shows RILJ, radio-interface, l2_hsic and umts-ipc0 wakelocks, so I wiped battery history and charged it to a full 100%, currently waiting for BBS to collect data to present here.

I can see that the problem is something about the radio/modem, but since I've tried many of them, I figured it's something that has to do with my device/carrier and not the modem itself. That's why I've tried Pelephone's modems, and recently Wanam's default modem (UHLPH) with matching RIL.

I wanted to try Pelephone's modem with matching RIL but GetRIL tries to install RIL for a different modem since it can't find one for pelephone's, and after a reboot it shows "unknown" baseband and no reception. This isn't important anyway because if it was a 'drainy' modem, it would have been much less drain and would have been better with other modems.

This is clearly something bigger and more persistant, something I'm missing as of my limited knowledge in android modems/system.

I would very much appreciate help with this in any way, ideas of what to try, info about related subjects, perhaps even a cause or a solution.

A friend of mine has the same phone with the same carrier with similar issues (yet a bit different), but the info I'm getting from him is limited and not conclusive. Based on it I can't say it's 100% environmental, nor can I say I'm the only one with the issue.

I'm ready to try anything - ROMs, kernels, modems, apps, tweaks etc.

I will be posting BBS screens and logs here once they'll be more accurate, for now I've attached a 10-min history and BBS screens.

Thank you for any help or assistance.