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.
Related
I wanted to see if I can post something without getting ridiculed. Seriously doubt that now cause I accidentally posted this in the general Q&A first and did not know how to move it or delete it so i am posing again here. Hopefully a moderator can just take care of that stray posting I made in the general area.
I am on my second ATT SGS2. First one had a GPS issue. Tried everything and finally convinced ATT warranty services that the problem was hardware. They said they would advance replace the handset. So I got it back to stock in every way except the flash counter,this was in December so long before I was aware of mobile odin. Flash counter was at about 12 when I was done trying different ROMs,mostly just try to get the GPS to work. It was in perfect shape, bone stock except for the counter. I cannot imagine I will have an issue, but has anyone ever heard of someone getting charged on a return to stock phone that had a flash counter above stock? Ill update once I know for sure the outcome.
My real question, does everyones SGH-I777 crash on occasion? If so how often? I so happy with the current code that is running on the phone with the exception that it sometimes sleeps and wont wake up, and sometimes it just plain crashes hard, locks up and has to be hard rebooted. Usually this happens about twice a day one or the other. I wiped before installing current kernel. The only reason I am not stock is cause I wanted the CKK6, 2.3.6 update to work and to keep root privaledges, but also needed my wifi cause ATT is throttling me down to dial up speeds when I reach 2GB. So wrong!!! Anyway thats another thread.
I loaded shostock with siyah kernel 2.6.35.14. after wiping everything including both caches. The GPS is solid now, phone is fast, battery is egh, I keep a charger with me... but it crashes hard from one to three times a day. Locks up playing tunes, or wont wake up with out being plugged in or hard booted. Do I have another defective handset or should I just go back to 2.3.4 and UKH7 or should I just deal with it and consider the crashes, "excellent opportunities to reboot."?
Thanks for the all the hours of fun, u know who you are.
I honestly don't remember my phone crashing at all. If it's crashing, it aint stable. Did it crash when it was stock?
yeah I mean duh right? The new handset was updated, rooted, downreved and flashed with the custom rom before it was put under any load, so I do not know if it would have crashed before. I have wiped, re downloaded, checked with hashtab and re flashed my current kernel, so it seems like it has to be hardware, again... ugh. Especially since no one else is having issues with shostock and siyah. I wonder how hard it is going to be to get warranty services to replace the second phone in 3weeks!? Lol.
Try going back to stock and run it for a couple hours to see if it still crashes. If it still crashes then more than likely hardware issues.
Sent from my SAMSUNG-SGH-I777 using xda premium
If it's crashing on stock without SetCPU to set a screen-off profile, you have a hardware problem.
I haven't had a crash, freeze, or spontaneous reboot in ages - despite running kernels that a few others have reported stability problems with (and I have effectively halted my kernel until I can get to the bottom of those reports...)
Too often is when it happens regularly, period.
I'm running CyanogenMod 9 and have almost no crashes, despite it being experimental.
Sent from my GT-I9100 using XDA App
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
silashj said:
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
Click to expand...
Click to collapse
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
I had the same problem using the latest siyah kernel, but never with entropy's. I would suggest flashing a new kernel.
Sent from my GT-I9100 using Tapatalk
1. To answer the OP question, I have experienced ONCE that was when I tried to run the Andy's TI-83 emulator on my virgin stock ROM. The result is either my fault or the application isn't compatible with the running OS.
2. With bone stock, it shouldn't crash at all. If it does, RMA.
3. If the owner(s) have "some fun" around it such rip it off, hack it up, install different kernels, different ROMs, ...... then please DO NOT complain the device is suck.
I've seen a lot of knuckleheads who tried to mod their devices, screw them up then claim "they're suck".
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
Thanks this sounds like a plan. I have to do something things have gotten worse. About 3 out of ten times I go to put the phone to sleep now, instead of blinking out the phone takes a screen shot. My fingers are no where near any of the other buttons and it takes a screen shot over and over when I press the power button. I have to move around from screen to screen, hit the home button and then hit the power button to put it to sleep. Weird stuff, could be worse though. Did I say that I thought the phone sucks? I thought I read in one of the replies up there something like that. Aside from the GPS issue that was hardware related, and problems I have brought on myself because stock wasnt good enough, this is hands down the most awesome piece of electronics I have ever owned. iPhone smyphone. I just need to find the perfect turbo charged, rooted but as stock as possible configuration that is stable and I will be set. I really like where I am, hopefully the kernel you suggested does not change much but fixes the problems. Thanks again all.
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
axis01 said:
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
Click to expand...
Click to collapse
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
silashj said:
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
Click to expand...
Click to collapse
That recovery will work. After installing the DD kernel, CWM will change.
Sent from my Galaxy SII
I get a crash here and there everyday...
Sent from my SGH-I777 using xda premium
Have only ever crashed while messing with voltages or clock speeds. if it's crashing something is wrong.
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Mine crashes a few times a day if I'm cycling through a lot of apps or installing things. (Stock+root) the other day my phone would crash anytime I tried, to watch a video in web browser. (Either mxplayer or phone)
Sent from my SAMSUNG-SGH-I777 using XDA App
T90 said:
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Click to expand...
Click to collapse
With Siyah I crashed more often than I do know with DD...
Sent from my SGH-I777 using xda premium
Ok flashed the DD from 01-30-2012
Thanks for all the help. I will post again when I know if things are better.
Hello all,
I've been experimenting with custom roms lately. First I tried resurrection since it got lotsa attention and then I tried sensation, all causing the same problem.
I was lucky to have a NAND backup so I quickly went back to my stock rom. But now I am wondering why are these roms causing heating problems but not the stock rom? Interestingly, many people are using them without any complaints.
I thought this might be a problem with my phone. I contacted amazon and asked for a replacement, they were nice to replace the product even after 3 months! (kudos to them).
But now I'm wondering if this will solve my problem. Moreover, I sometimes had heating while charging the phone, bolstering my thesis that the phone is faulty. Any ideas anyone?
you returned your phone for no reason!
If it works fine on stock, phone is fine.
Learn how to use custom roms, read how to flash each Rom in their thread.
Basically, modem and kernel are related to heat. Plus one needs to wipe his/her phone completely at least once before going to custom.
atifsh said:
you returned your phone for no reason!
If it works fine on stock, phone is fine.
Learn how to use custom roms, read how to flash each Rom in their thread.
Basically, modem and kernel are related to heat. Plus one needs to wipe his/her phone completely at least once before going to custom.
Click to expand...
Click to collapse
Lol calm down! I've not returned it, I am going to replace it. I've had heating problems with stock rom as well, especially while charging. I've changed the battery, thinking the problem was the battery but it didn't help at all. Also today, after being back to stock rom, it still heats up even with simple tasks. So I assume there is some kind of fault.
It's normal for your phone to heat up. If it heats up its perfectly normal because the cores are working fine. If u got battery heating warnings or any other phone heating warning thats the problem and you should investigate =D
Went through this with my Captivate. Had it replaced 3 times before I got one that didn't do it. Upgraded to the S2 in 12/11 and didn't have any SOD issues at all. Had to have it replaced in 10/12 because of charging port issues, but replacement has worked fine with rooted stock 4.0.3. That is, until this week. Had a SoD 4 days ago. Thought it was just an anomaly until I had another one today. Nothing new installed, normal usage. Man, what a PITA these are. Is it just Samsung phones that suffer SoDs?:crying:
Did you do the update to 4.0.4?
Phalanx7621 said:
Did you do the update to 4.0.4?
Click to expand...
Click to collapse
Nope. Nothing new installed in weeks beyond normal app updates. When I restarted the phone the batt was down to 40%, so something was seriously draining it before it went dead because it had been at 92% an hour before.
Miami_Son said:
Nope. Nothing new installed in weeks beyond normal app updates. When I restarted the phone the batt was down to 40%, so something was seriously draining it before it went dead because it had been at 92% an hour before.
Click to expand...
Click to collapse
Double check your Android Version
122ninjas said:
Double check your Android Version
Click to expand...
Click to collapse
Still on 4.0.3. Just went to check it after unplugging it an hour and a half ago. Dead again. rebooted and it was down to 74% batt and looking at the stats Android System was using 40% before it cut off. I noticed the same thing last time. What in the Android System could be causing so much activity that the phone drains the battery so quickly and just suddenly shuts off?
Maybe you're just rough on phones. My S2 is a very early model. Brother had it first and rooted/flashed all the time. I've had it for months doing the same thing. I've never had sod or force closed or anything. Currently on Dirty Root box and I don't even recall ever having to pull the battery before. Mines even been naked for over a month now without a single scratch, looks as new as day one.
Rough on phones? How do you mean? I never carry it in my pocket. The last 3 have always had a TPU cover and carried in a leather case. Always have screen protectors, never gotten wet or dropped. Nope, I'm very careful with my phones. This particular one I was satisfied to simply root it and leave it alone. Previous phones have all manner of custom ROMs installed with all kinds of framework and other tweaks. I did notice that I had JuiceDefender installed, which had run fine on my first S2. I'm guessing it might not be as compatible with ICS as it was with GB. Have removed it and hopefully the problem, as well.
SOD's here too
My wife has the S2 and has been having SOD's since the ICS update. Thinking the update to 4.04 would fix it, I updated it for her, but no dice. Replaced the battery too. I know this issue has been present for many sgs2's for a while now. Unfortunately, I was never able to find a solution. Since it is not my phone, flashing another ROM is not a solution. However, if anyone knows a solution for this(even if root is required), I am all ears.
Btw, to the OP, never had juiced defender installed on her device so not sure if that would really be the cause of your issue.
My honest opinion is that either it is an issue with the stock kernel/OS or an issue relative to the battery components (charge circuits/motherboard) with some devices.
Since I tend to err more on issues usually being in the software, my thought is that if and when JB is released for the ATT S2, this might alleviate this along with other issues, more importantly for those that are stock only oriented.
mastergflash said:
My wife has the S2 and has been having SOD's since the ICS update. Thinking the update to 4.04 would fix it, I updated it for her, but no dice. Replaced the battery too. I know this issue has been present for many sgs2's for a while now. Unfortunately, I was never able to find a solution. Since it is not my phone, flashing another ROM is not a solution. However, if anyone knows a solution for this(even if root is required), I am all ears.
Btw, to the OP, never had juiced defender installed on her device so not sure if that would really be the cause of your issue.
My honest opinion is that either it is an issue with the stock kernel/OS or an issue relative to the battery components (charge circuits/motherboard) with some devices.
Since I tend to err more on issues usually being in the software, my thought is that if and when JB is released for the ATT S2, this might alleviate this along with other issues, more importantly for those that are stock only oriented.
Click to expand...
Click to collapse
Flash back to 4.0.3 or 2.3.4
Sent from my GS4 running CM11 Kandy Kane
Haven't had an SoD since ditching Juice Defender. Still not going to update to 4.0.4, though.
Miami_Son said:
Haven't had an SoD since ditching Juice Defender. Still not going to update to 4.0.4, though.
Click to expand...
Click to collapse
4.0.4 causes sods
Sent from my GS4 running CM11 Kandy Kane
Following the 4.0.3 update (summer 2012 or so), I had SoD episode once or twice a month. I lived with it. I updated to 4.0.4 via OTA AT&T and had SoD everyday (sometimes 2-3x a day). I just rooted and installed AOKP and have been SoD-free since. I wont go back to stock AT&T.
122ninjas said:
4.0.4 causes sods
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
I know.:silly:
I saw a post on the AndroidCentral forums that said that disabling the AT&T Smart WiFi app fixed the SoD problem. The poster thought it came along with the 4.0.4 update. He also disabled most of the other AT&T crapware, so you might want to try disabling some of the other AT&T apps if disabling Smart WiFi doesn't fix the SoDs.
mvi57 said:
I saw a post on the AndroidCentral forums that said that disabling the AT&T Smart WiFi app fixed the SoD problem. The poster thought it came along with the 4.0.4 update. He also disabled most of the other AT&T crapware, so you might want to try disabling some of the other AT&T apps if disabling Smart WiFi doesn't fix the SoDs.
Click to expand...
Click to collapse
Yep, this right here. After I updated to 4.0.4 I was having 2-3 SoD's a day. Disabled Smart WiFi and all the other AT&T crapware and haven't had one SoD since.
I have the clean version of the 4.0.3 ROM that has none of the AT&T crapware, so that wasn't the issue. Since uninstalling JuiceDefender I have had zero issues.
Miami_Son said:
I have the clean version of the 4.0.3 ROM that has none of the AT&T crapware, so that wasn't the issue. Since uninstalling JuiceDefender I have had zero issues.
Click to expand...
Click to collapse
Its been known that jd causes issues and doesn't help at all ics+ and barely helps on -gb
Sent from my GS4 running CM11 Kandy Kane
It did help a lot on GB, but the problems quickly developed when I enabled it on ICS. Never again.
Okay, so I have s2 i9100. I have installed neatrom lite version, it is jb 4.1.2. I have fully nuked phone before installing this rom and installed dorimanx kernel afterwards. By using stweaks i choose performance profile for my phone. Even though I have disabled animations from developers menu, and I do not use any applications which would eat a lot of processing power, my phone is very slow. It was not this slow before. I mean honestly, every single damn move is with at least a minimal lag, freeze or something. What the hell is going on here? Does JB 4.1.2 on S2 is supposed to be like that.
You guys, I need some tips from your experience write here. I really have like no time for testing roms and maybe you can help me out by recommending some kind of rom, which would not have **it load of bugs and would not lag as much as this one does. I heared about CM 10.2 4.3JB but I am afraid about bugs and all that, so I think it would be a better idea to stick with 4.1.2 or 4.2.2. So, any tips? I would really appreciate some. Thanks you guys.
I highly doubt it is caused by your rom, because almost every user is satisfied Neatrom (me included).
What kernel do you use? And what happens when you use another profile than Performance?
Donnie Sins said:
I highly doubt it is caused by your rom, because almost every user is satisfied Neatrom (me included).
What kernel do you use? And what happens when you use another profile than Performance?
Click to expand...
Click to collapse
Dorimanx kernel. Same things are happening.
Maybe my phone is damaged or something. A few days ago i dropped it and it was a little bit wet, but it did not turned of or anything and I can use it. About a few hours ago, something weird happened: phone was at idle, sleeping and out of nowhere that sound, when you start charging your phone appeared and backlight turned on... No reason, just happened.
Anyway, do you have any recommendations how to get rid of these issues?
Pull battery out now put in hot place in bowl of rice and leave it there for a week. Water damage...probably mb replacement now mate. Water and s2's dont mix.
I9100/I9300
Well, I used to have a rom that was causing me trouble after I dropped my phone. The battery for example was terrible after it. A full wipe and a fresh install of a new rom (although I'm pretty sure you've made a good choice with Neatrom) cleared these problems.. Maybe you can try that?
Edit: and if you try another kernel?
Hey guys, I'm currently using Samsung's 4.3 ROM (XXUGMJ9) with DerTeufel1980's Devil2 kernel.
After leaving my phone for a few hours, I return to it and notice that the phone lags a lot. It wakes up quickly but the entire UI is very laggy. CPU stats shows that the phone is using all cores at 1.4Ghz with usage typically above 80%. If I leave my phone on idle for just a hour or two, it does begin to lag but not as much as if I left it for 5+ hours. If I leave my phone overnight, I'll return to it switched off (I do believe that this is related to the lag issue). If I restart the phone, the problem disappears - is anybody else getting this or is this just me?
Samsung have just re-released fixed 4.3.
Gold_Diesel said:
Hey guys, I'm currently using Samsung's 4.3 ROM (XXUGMJ9) with DerTeufel1980's Devil2 kernel.
After leaving my phone for a few hours, I return to it and notice that the phone lags a lot. It wakes up quickly but the entire UI is very laggy. CPU stats shows that the phone is using all cores at 1.4Ghz with usage typically above 80%. If I leave my phone on idle for just a hour or two, it does begin to lag but not as much as if I left it for 5+ hours. If I leave my phone overnight, I'll return to it switched off (I do believe that this is related to the lag issue). If I restart the phone, the problem disappears - is anybody else getting this or is this just me?
Click to expand...
Click to collapse
Search google and u will know the first release of 4.3 by samsung for the gs3 is very buggy. Like JJEgan said, samsung is re-releasing a new one over time.
Sent from my GT-I9300
JellyYogurt said:
Search google and u will know the first release of 4.3 by samsung for the gs3 is very buggy. Like JJEgan said, samsung is re-releasing a new one over time.
Sent from my GT-I9300
Click to expand...
Click to collapse
I've heard about today's release, been trying to get my hands on it but it doesn't seem like anyone has posted anything reliable. But yeah, I know the current ROMs are very buggy, I was just wondering if this was one of the bugs or just me doing something that messed it up somehow
Gold_Diesel said:
I've heard about today's release, been trying to get my hands on it but it doesn't seem like anyone has posted anything reliable. But yeah, I know the current ROMs are very buggy, I was just wondering if this was one of the bugs or just me doing something that messed it up somehow
Click to expand...
Click to collapse
Its the rom's fault. Dun worry I always advise tat u wait for a week after samsung releases 4.3 to see if others reported bugs or anything.
Sent from my GT-I9300