Related
Hey Guys,
Eversince moving to AOKP RR 1.2 there has been a massive battery drain from RILJ keeping a partial wakelock constantly so no deep sleep.
I had varying success at first with switching on airplane mode, rebooting and then switching it off again but that hasnt worked with 1.7 or 1.8.
Have also tried the suggestion of clearing cache, dalvik and battery stats then fixing permissions, which hasn't work either
I recently did a fresh install of 1.7 then 1.8 over the top and it didnt seem to be happening ( I was so relieved) so i went to the market and got the apps that I need and waited for the media scanner to finish running and theres the RILJ drain again.
EDIT of this post.
I have just noticed that the battery drain only happens when I use my Chinese SIM (currently studying in China) but when i put my UK SIM in the battery drain goes. It must be the radio so can anyone recommend a good radio to use for China?
Luke
use the right modem and check for signals. flashing some other modem will most probably solve it to you
Have tried different Modems
So I flashed KI3, KE7 and XXKP8 and still have the same battery drain will all.
I'm a bit stuck now, can anyone help?
bidoa said:
So I flashed KI3, KE7 and XXKP8 and still have the same battery drain will all.
I'm a bit stuck now, can anyone help?
Click to expand...
Click to collapse
Ask the rom dev or change the rom .
jje
Im not gonna bother the dev with this.. have gone back to RR v1.1, Will get the latest rom when i go back to England next month.
its quite nice to have call recording back actually and a working market with gapps
Which Modem do u suggest
bala_gamer said:
use the right modem and check for signals. flashing some other modem will most probably solve it to you
Click to expand...
Click to collapse
Hi
I have a similar issue where RILJ is eating up battery on my S2, I have installed CM9 20120514 build with LPS modem.
I have Vodafone as a carrier in Mumbai, can u suggest anything.
Regards
Kapil
Same problem for me.
Also AudioOut_1 also causes high wakelocks sometimes.
Anyone else with the same problem?
And yes I have those touch sounds disabled anyway.
Same problem here, RILJ is keeping my SGS II awake 100% of the time
I'll notify the ROM dev's but I'm definitely having to switch away from this version
I have two galaxy s2s. one is i9100 and the other one is i777 on at&t.
SoD happened once on each phone. The i777 was running stock gingerbread and the i9100 was running resurrection remix 1.9.1 with the siyan kernal I believe.
The screen just wouldn't turn on so I just pulled the battery out (is it safe for the phone?)
This doesn't happen often,well just once each on each phone as stated before, but it does bug me as it makes me think there's something wrong with my phones, and pulling the battery out doesn't seem like it's good for the phone.
I searched around the forum a bit and saw other people are having this issue as well. And not just the galaxy s2, but other phones too.
only sleep of death in almost 10 months of use is when i tried xwlp9.
so no its not common
It's fairly common yes, a lot of people running non-stock ROMs get this. I had this ~25 times on numerous Resurrection Remix ROMs, but since v1.9 I haven't had this issue fortunately. If it's causing you a big problem, try fixing permissions from CWM recovery, that seemed to make a big difference when I was having the problem.
SOD usually occurs when the kernel UV the CPU or GPU a little to much. Not every device is the same and not handle same kernels, UV values etc
Sent from my GT-P6810 using XDA Premium HD app
From the sound of it, it seems to be a software problem.
I got it on the i777 which wasn't running a custom rom. But I think it could be caused by that battery management app that I installed.
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
It's normally a firmware issue, or a conflict between an app & the firmware. You'd find it's pretty rare for an 'untouched' (I.E not modded) phone running stock firmware to have SOD's. And obviously if you're flashing custom firmware that's constantly evolving/changing, then sometimes you're going to get SOD's, tho with most well crafted firmware these are fairly rare.
I reckon I've probably had <10 in the 8 mths I've had my phone & I've been running non-stock firmware the whole time save for the week I got my phone, which is nothing when stacked up against all the mucking around I've with my phone.
Edit to add - One way you can test to see if SOD's you're having are possibly hardware related is to do a completely clean install of stock firmware & see if they still happen. If they don't, then it's obviously whatever firmware you were running. If they do, then it might be hardware-related. Re: your question about pulling the battery after a SOD, normally this shouldn't cause you any problems (it's sometimes the only way you can successfully reboot the phone).
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
victorator said:
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
Click to expand...
Click to collapse
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Ray_Grey said:
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Click to expand...
Click to collapse
Or just flash the newer build. No SOD there.
wanewon said:
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
Click to expand...
Click to collapse
How about this?
I answered your question. Read the edit I made to my post.
wanewon said:
How about this?
Click to expand...
Click to collapse
MistahBungle said:
I answered your question. Read the edit I made to my post.
Click to expand...
Click to collapse
Thank you for the answer.
Since it's kinda hard to recreate the SOD. I'll reflash the rom and kernal and do a wipe and see if the SOD still happen
victorator said:
Or just flash the newer build. No SOD there.
Click to expand...
Click to collapse
Victorator, forgive my ignorance, but are you saying i should just flash the latest build, XWLPD, onto my fone rather than re-rooting it using a different kernel (i.e. CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip) in order to stop the SOD?
Never faced such issues ever.
Sleep of death
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
MX 007 said:
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
Click to expand...
Click to collapse
bah bye
SOD
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
?
darkm1st87 said:
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
Click to expand...
Click to collapse
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
tkrokod said:
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
Click to expand...
Click to collapse
Hi,
I'm also trying to solve this problem, since weeks.
My observations:
SOD happens most on higher battery status (e.g. more SOD's at 80% battery then at 20%
The Phone gets hot after SOD and also before the SOD comes.
While loading the Phone SOD's happen more often
The battery status drains rapidly while SOD (cause of the resulting heat)
My SOD's are independent of kernel, rom, firmware or what ever.
I think it's a hardware problem, but I've no warranty and what to solve the problem without changing the mainboard. It couldn't be a really defective of an important part, cause the phone works apart of this SOD-problem.
Maybe we could find out together howto solve these anoying sod's
Hey. Im trying to solve the SOD problem myself cause its been happening every day and its really annyoing since the phone isnt even a month old.
I got the newest cyanogen mod running.
The phones model is GT-i9100
Android is 4,2,1
I still have warranty on it, do you think I should go back to stock, go exchange my phone where I got it and see if the new one has SOD too or should I just try fixing it first.
Also apps I use constantly : go launcher and dragonvale
I have a 8 gb micro SD inside as well, dunno if that could cause this.
This RILJ wakelock on the dialer seems to be impossible to remove. I've tried everything from disabling all apps, turning off the phone and turning it back on with airplane mode, TWO factory resets, turning off all GPS and location services, and even shutting off my mobile data. I even did all of those steps at once and to no avail. I'm running stock right now but I seriously can not use this phone when this wakelock is disrupting my phone every damn second. I don't know if this is the right section to post this, but is anyone else experiencing this issue? Is there even hope? I've tried what feels like everything. I feel like this will drive me crazy to the point where I will just exchange the phone and claim battery problems. Again, sorry if this is the wrong section to post this in.
coobot said:
This RILJ wakelock on the dialer seems to be impossible to remove. I've tried everything from disabling all apps, turning off the phone and turning it back on with airplane mode, TWO factory resets, turning off all GPS and location services, and even shutting off my mobile data. I even did all of those steps at once and to no avail. I'm running stock right now but I seriously can not use this phone when this wakelock is disrupting my phone every damn second. I don't know if this is the right section to post this, but is anyone else experiencing this issue? Is there even hope? I've tried what feels like everything. I feel like this will drive me crazy to the point where I will just exchange the phone and claim battery problems. Again, sorry if this is the wrong section to post this in.
Click to expand...
Click to collapse
Whats the count & percentage being used by the RILJ Wakelock?
coobot said:
This RILJ wakelock on the dialer seems to be impossible to remove. I've tried everything from disabling all apps, turning off the phone and turning it back on with airplane mode, TWO factory resets, turning off all GPS and location services, and even shutting off my mobile data. I even did all of those steps at once and to no avail. I'm running stock right now but I seriously can not use this phone when this wakelock is disrupting my phone every damn second. I don't know if this is the right section to post this, but is anyone else experiencing this issue? Is there even hope? I've tried what feels like everything. I feel like this will drive me crazy to the point where I will just exchange the phone and claim battery problems. Again, sorry if this is the wrong section to post this in.
Click to expand...
Click to collapse
I have the same issue.
Sent from my HTC One using xda premium
Lenunited said:
Whats the count & percentage being used by the RILJ Wakelock?
Click to expand...
Click to collapse
Percentage I am not sure. Count is 47 sec at x1136 (usually around 1000-2000).
Blue1k said:
I have the same issue.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I know that feel bro. Might exchange the phone soon at the AT&T device center.
I'm having the exact same issue. I really dislike HTC phones, I've been dealing with bull**** problems similar to this on my HTC Sensation XE and One X for the past few days and it's annoying the crap out of me.
Anyway, I'm having this problem on my HTC Sensation XE, I've tried several roms already (4.3, 4.2, 4.0.3) and even flashed RUU to get it to run stock ICS rom with Sense, and all of them have the exact same problems. They all have RIJL wakelocks caused by either the Phone or the Dialer. I did everything (same as you did) including disabling Google Service Framework services etc, none of them helped.
Even in airplane mode, the RILJ wakelock continues to run. It drains my battery and it pisses me off. I've tried asking for help by sharing my BetterBatteryStats dump and did everything that others have suggested, on ALL the roms I've tried. None of them helped.
I even tried flashing different firmware, radios and ril for my phone. None of them made the problem go away.
At this point, I'm thinking it's probably a hardware problem with my phone.
RILJ wakelock is because of Android not HTC
calanizzle said:
RILJ wakelock is because of Android not HTC
Click to expand...
Click to collapse
Well, yes it doesn't have anything to do with the brand of the phone itself. It's just that based on my experience, all the HTC phones I've used have had RILJ wakelock issues. I've tried different custom roms and they all shared the same problems. My Sensation XE and One X had RILJ wakelocks since day 1.
My Huawei U8800 and Xperia Z had no problem whatsoever. So it leads me to believe it's some sort of hardware issue with HTC phones, which isn't surprising considering there are many.
Hello everyone,
I have a galaxy s2 i9100p which i've undergone to several modifications in order to make it snappier.
I nave first changed, on JB stock the SYS partition to 5gb -8gb ad i had quite some apps slowing the phone down. I decided after to choose the way of rooting to have a fast experience on KK. I originally rooted and installed latest syiah kernel beta + paranoid last stable version. I then moved to beta5 but in all cases battery drain was massive even in deepsleep.
I moved then to slimsaber ROM with their own custom kernel, but several (i thought partial wakelocks) made me keep slimsaber until they removed all partial wakelocks with the latest 04062015 update. In the meantime i swapped to dorimanx which somehow worked (v10008) but noto always And didnt satisfy me so i now moved to apolo regular kernel. My problem was partially solved as now i have NO persistent partial wakelocks and now i have no drain in deep sleep. Yet with battery monitor widget, while when phone is in deep sleep And i use about 0,50-1% battery, the moment i turn WiFi on the usage is in the -500 or 700 range...which is HUGE. (about 40-50%). The aforementioned app says my liion battery is good, And since kernel wakelock detector does not trace anything suspicious i really have no idea on what to do to make WiFi drain acceptable. My router is fine as another gs2 stock JB does not drain so fast so i guess its stilo kernel related. I have twrp recovery And i literally ran out of options. What should i do? (I owned this phone for 3 Years And possibly dont want to change it)
Update: i tryed to change modem but without luck. Then i used wakelock detector And found this. Isn't the WLAN xNumber And WLAN awake one too high for such little time? I ran out of ideas by now.
Update. I think I found the reason of this massive drain. I downloades from gplay the app network log, And as 192.168.1.101.NETBIOS shows there is this little SYS packets process at the top that i cant understand. I tryed to swap to static IP bit I didn't see big improvements yet, its still here after all. What should i do?
(I am aware there are similar threads but none specified this except a big one which led me only to find the cause without a solution; please dont let this thread die forgotten)
mdm_hsic_pm0, the battery killing wakelock I have witnessed on every rom I have flashed lately.
Now it has come to this point where Im really asking myself why do I still use this phone when it can drain out the battery at any given time in my pocket without me noticing it until its too late...
I have tried every possible fix and at this point Im really about to give up and go back to my old Windows Phone which atleast worked.
Am I alone with this problem? I just cant be the only one who has to deal with this :crying:
Late night thread start in the wrong area, I was supposed to post this on the I9305 Q&A section...
Heatti said:
mdm_hsic_pm0, the battery killing wakelock I have witnessed on every rom I have flashed lately.
Now it has come to this point where Im really asking myself why do I still use this phone when it can drain out the battery at any given time in my pocket without me noticing it until its too late...
I have tried every possible fix and at this point Im really about to give up and go back to my old Windows Phone which atleast worked.
Am I alone with this problem? I just cant be the only one who has to deal with this :crying:
Click to expand...
Click to collapse
I feel your pain. About a year ago, I traded in my beloved Note 2 solely due to this wakelock, and got a Oneplus One. I will never buy another phone without an unencrypted bootloader, so that rules out any further Samsungs, it appears. But I otherwise loved the Note. I had the 1 and the 2, my wife still has the 2, and I have a 10.1 (which does not suffer this wakelock). But I could not stand my otherwise stellar Note 2 due to this wakelock appearing out of the blue and destroying my battery on a regular basis. I researched this for A YEAR and never found any solutions, and got to the point where I put a wakelock detector widget on my homescreen and whenever I noticed the wakelocks over 50%, I rebooted, which usually solved it for a day or two, but sometimes for only a few hours or not at all.
My wife still has a Note 2, though, and trying to renovate her phone, I put a Slim rom on it. thinking that perhaps the problem had finally been solved. These are the best battery roms for the Note, but they still suffer the wakelock, like every other rom and kernel I tried, and I tried all of them. But it seems the AOSP roms get the wakelock about twice as often as the Touchwiz roms - at least once per day instead of every other day. So she's stuck with a Touchwiz rom, and also has the wakelock detector widget on her homescreen and has to reboot every other day. My advice is to give up - if you are getting this wakelock, there is no solution, so don't think you are going to fix it.