when i press in my touchscreen sometimes i get random direction S**k particular when im typing suck sometimes i get wrong letter. . .what is my phone problem?did my touchscreen broke?sorry for bad english
Nope, it's because of the OC kernel. Underclock to ~800MHz or flash a non-OC kernel.
You're under CM7.2, aren't you?
Sent from my GT-S5830
TeachMePlz said:
when i press in my touchscreen sometimes i get random direction S**k particular when im typing suck sometimes i get wrong letter. . .what is my phone problem?did my touchscreen broke?sorry for bad english
Click to expand...
Click to collapse
Yeah, judging from your post in my thread your phone has issues with oc. Maybe you better off to not.
sat in my one piece devil outfit as I type. . . . . no. . . really!
I already spent a lot of time on that issue, spent boirs, and flashed tons of rom, scripts, and kernels...
It was fine with froyo, but every 2.3 roms had this issue, except kpy and further.
So the problemn has been solved on official roms.
But i get this problem on EVERY custom rom.... Every, except gingereal 1.4, don't know why...
I tried all the CM version, including 7.1 (grif and behrad), 7.2 rc0 and rc1, gingercrust, and all Jusada's rom...
And the problem is in every roop...
I deeply believe it's related to kernel: it's even worst with oc kernel, but trust me, the problem happened with every kernels including non oc.
For me at least, thiz iz the biggest issue on the Ace.
Maybe i will open a new detailed topic, including all what i've done.
I would really appreciate that some dev fix this major issue, poisonning my phone with every custom rom.
Sent from my GT-lS5830 using xda premium
Darvadouille said:
I already spent a lot of time on that issue, spent boirs, and flashed tons of rom, scripts, and kernels...
It was fine with froyo, but every 2.3 roms had this issue, except kpy and further.
So the problemn has been solved on official roms.
But i get this problem on EVERY custom rom.... Every, except gingereal 1.4, don't know why...
I tried all the CM version, including 7.1 (grif and behrad), 7.2 rc0 and rc1, gingercrust, and all Jusada's rom...
And the problem is in every roop...
I deeply believe it's related to kernel: it's even worst with oc kernel, but trust me, the problem happened with every kernels including non oc.
For me at least, thiz iz the biggest issue on the Ace.
Maybe i will open a new detailed topic, including all what i've done.
I would really appreciate that some dev fix this major issue, poisonning my phone with every custom rom.
Sent from my GT-lS5830 using xda premium
Click to expand...
Click to collapse
I have exactly the same issue and i made the same experiences as you.
KPY and later fixes that issue to a certain degree but it still happens sometimes.
I came to the point that it cant be software related. Because my friends ace doesn't have that problem, no matter what rom he flashes.
So either our cpus don't run stable at stock voltage or the touchscreen is defective.
I noticed that the problem is also related to how you charge your phone. Depending on if u charge it via usb or use the wall charger. It definately happens less frequently if i use the wall charger.
So could it probably be a defective battery?
I'm really thinking of bringing it to the service point but they will prolly just flash a kpy or later fw and say it's fixed
prodal said:
I have exactly the same issue and i made the same experiences as you.
KPY and later fixes that issue to a certain degree but it still happens sometimes.
I came to the point that it cant be software related. Because my friends ace doesn't have that problem, no matter what rom he flashes.
So either our cpus don't run stable at stock voltage or the touchscreen is defective.
I noticed that the problem is also related to how you charge your phone. Depending on if u charge it via usb or use the wall charger. It definately happens less frequently if i use the wall charger.
So could it probably be a defective battery?
I'm really thinking of bringing it to the service point but they will prolly just flash a kpy or later fw and say it's fixed
Click to expand...
Click to collapse
The manual book states that if the battery is plugged in to charge, there is a chance of the touchscreen malfunctioning. I have this charging-related issue with my friend's charger (which uses a microUSB adaptor, but the phone is an old Samsung phone): the touchscreen "touches" itself (no sexual reference there).
Another bug I got (which I discussed above) is the malfunctioning touchscreen on an OC kernel.
I can almost be certain that it has nothing to do with the battery, but more with the kernel.
Sent from my GT-S5830
can someone explain this in more detail? i didn't really understood what op meant
oFFoy said:
can someone explain this in more detail? i didn't really understood what op meant
Click to expand...
Click to collapse
Basically the OP says that he's having troubles with the touchscreen, and it's really annoyinng when typing.
I (and several other people) believe it's because of the OC kernel present in Axel's CM7.2 and other ROMs based on it.
Sent from my GT-S5830
Related
Turns out this is obviously an issue with my phone, and not the new kernels I have been using. All though it has only happened with Fserve's franco.Kernel.v19.3-gbs.v15 and franco.Kernel |.v19.4| 2.6.32.46. But the problem is the same between both of them, happens less often with v19.4. But rather than bother the kernel developers I will put a general post here. I'm sure that they already have their hands full, and I don't think it's a kernel issue anymore.
The issue:
My lockscreen keeps burning the image into my LCD when I put the screen to sleep. Always is the last image it was at when I shut it off, and it takes around 3-4 hours after flashing a kernel to start with the issue.
It's basically the same type of thing that happens if you leave a computer monitor on at the same screen for day or so, the image stays on the screen for a while because it has burned itself into the monitor.
I cannot take a Logcat as it is disabled in the franco kernel I am currently running. Current specs are in my signature.
Essentially I am trying to track down the cause of this issue, as it seems to happen across different setups, no matter the LCD sleep settings I set, and doesn't go away with lower overclock settings. But when I flash my phone back to OEM specs with KDZ updater it does not produce the problem at all.
It has to be software related because if it was my hardware, It would produce the same result when KDZ updated.
Anyone have this issue at any point? Any suggestions on how to fix it?
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
bigsupersquid said:
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
Click to expand...
Click to collapse
No luck, not supported in this kernel. I return the message
Code:
dmesg > /sdcard/dmesg.txt
klogctl: Function not implemented
Just returns an empty dmesg.txt file.
gahhh, i'm sorry. thought that'd work for sure.
maybe adb bugreport?
FOUND IT!!
Turns out the screen off animation in CM7 was the cause of my issues. For whatever reason, with the screen off animation disabled my screen no longer burns any images into the LCD. I have been burn free for 2 days now.
Weird. Oh well
EDIT: **** me it's back again, what the hell? This is truly a noggin scratcher of a problem here...
I have the bugreport:
Download the bugreport(report.txt)
Compiled through Terminal Emulator v1.0.29 and taken 5 min after screen burn was noticed.
Currently running franco.Kernel v19.3 CFS to see if the problem goes away, as I ran this kernel for a week with absolutely no issues.
Update: Logcat is working on v19.3 CFS version so I was able to take a look at what the phone was doing. Turns out the screen state is set to 0 when I turn it off, and it runs all the screen state off commands properly. But, with logcat not working on v19.4 CFS I am not able to compare notes. Going to look through the bugreports I have and see if there are any differences.
Aha! I have found something that might be of some help. In the battery history section of the bugreport, v19.3 does a Kernel wake_lock when turning the screen on and off, while v19.4 is doing just a wake_lock. They may be versions of the same thing, but maybe the difference in the process is what's causing my problems? I ran v19.3 for around 6 hours today and I had no issues with screen burning.
Well, after 8 hours of 19.3 CFS I still am facing the same screen burning problem. Nothing seems to be making the problem go away. My next step is going to KDZ flash my phone back to stock and run it like that for a day. If the problem persists I am taking it in to be serviced because it is definetly a hardware problem.
Update:
Day One of running stock V10V firmware, and no screen burning occurring at all. Going to keep it running like this for the rest of the week to see if anything will pop up. Maybe CM7 went on a fritz? I dunno, I'm no closer to finding the source, but it's looking like software right now.
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Okay, approximately 4 hours into CM7 with francokernel v19.4 BFS, I am experiencing the same LCD Screen burning issue. Nothing is making it go away in any settings. Going to try void forever and see if anything changes.
Download Bugreport HERE(log1.txt)
Shofire91 said:
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Click to expand...
Click to collapse
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
dancom96 said:
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
Click to expand...
Click to collapse
Not too sure, it's almost like the backlight LED turns off, leaving the lockscreen image there to burn into the LCD. Or maybe just a programming anomoly?
Either way, 2 hours into void forever's rom I am getting the problem once again (argh!!).
It only seems to do this with a custom ROM, the v10v firmware ran without any LCD issues whatsoever. Now why would it do that? I ran V10V rooted and clockworkmod recovery and no LCD issues. Only with a custom ROM.
Download the bugreport here(log2.txt)
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Shofire91 said:
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Click to expand...
Click to collapse
i dont know it it is cm7 6.5.7 issue cuz i never experienced ur problem with this rom or rom based on 6.5.7
I'm working on the assumption that my problem is just an anomoly that I have come across. Searches returned nothing, and I was able to run 6.5.7 without a single issue for weeks, across different kernels. It just came out of nowhere, maybe it will still turn up in 6.6.1, but at this point only time will tell.
This thread is essentially a record of my findings over time to help anyone who has had this issue(there are a few, but not many) figure out where to turn on fixing the problem.
Took a bugreport in 6.6.1 MIUI just for anyone to look through and see if any differences turn up. I have yet to find something that points to the cause.
Download the bugreport(log3.txt)
UPDATE:
3 days in and nothing so far, seems to have been a problem in CM7 6.5.7. Haven't had a single bug since.
Im also experiencing the lcd burn issue on cm7 6.5.7 with goldleaf kernel... doesnt happen on other kernels tho. Ive had this issue before with stock froyo when i got my phone. Since goldenleaf or whatever is based on stock kernel then i think it must be the kernels fault...
Wierd, I had the same trouble as soon as I tried fserve's kernel as well. Mind you it was 19.3 gbs v15 where it all began for me. But yet it went away when I flashed the phone back to stock with KDZ updater, but still came back after reflashing CM7 6.5.7 with franco's 19.4 kernel, and any other kernel after that, even the stock CM7 one. Even any ROM I used that is 6.5.7 based caused the problem to come back. CM7 6.6.1 seems to be the only answer for me at this point. Not sure what is causing the problem but it seems to be based from fserve's modded kernels, but yet it only manifests itself on a few number of devices. Is your O1 a P500 or a P500h?
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
ert69 said:
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Let me know how it turns out.
Shofire91 said:
Let me know how it turns out.
Click to expand...
Click to collapse
Nope. Still can see my lockscreen. I think it might be the roms fault as some have stated before. Plus, that kernel drained my batt like crazy so I went back to goldenleaf.
Sent from my LG-P500 using xda premium
Were you not having the same trouble with goldleaf as well? It has to be the ROM because I am running the setup in my signature since Sunday. No issues at all. Something about 6.5.7 and fserve's kernel don't seem to mix for certain phones. I wonder what the difference is that causes it? I wish I knew more about Unix and Java so I could figure it out. Any developers out there with a little free time?
Sent from my LG-P500h using XDA App
Hi everybody,
I'm trying to understand how to fix this problem that's affecting me since I have this device.
I've got it in my hands in the end of November, and I've quickly unlocked and rooted it to install CM7. I don't like motoblur, so I didn't use it until I had CM7 on it. After few hours of happiness, I suddenly started experiencing freezes with black screens (I had to remove battery to unlock it) and auto-reboots.
I've wiped, fastboot-wiped, re-flashed, many times but nothing.
Tried different Roms such as redpill hybrid and dark side...same!
Googling around out there I've found hundreds of users with these two bad issues, and after hours of reading, and observing my own Atrix I've figured out what follows:
There are mainly two different issues. Although they are often considered the same, I think they are separate and I have both:
GPU issue: after playing a game or any app that "stresses" the GPU I have my Atrix not waking up after screen-lock. Black screen but if you call it is up and running somewhere in the background. it appears death, and I have to remove the battery to wake it up again. Device heating at rear-bottom.
RADIO issue: when the signal isn't that good and it changes often spot it reboots all alone.
trying to understand if it is hardware related (not an issue, but maybe small differences in the hardware of different phones) yesterday I went back to stock froyo.
Since then everything seems to work properly. Incompatibility of some ROMs with my device?
I want to stay on stock for some days to a deep test, after that, I will search for a good stock gingerbread firmware to flash.
I hope to find a solution, 'cause since I don't have CM on my device I don't feel it really mine .
Sorry for my English, hope to have made myself clear.
Thanks.
What kernel are you using? Some phones can't handle a high overclock. As for a gb rom I suggest darkside.
Sent from my MB860 using XDA App
Standard kernel @ 1Ghz. I've tried Faux's kernel @1.3 and 1.4, but I did it trying to solve the issue.
After good stock froyo and stock gingerbread experiences, I'm now happily running Aura deblurred.
Thank you, now I'll stay with Aura until CM9...
If you are experiencing the same issue look here: http://forum.xda-developers.com/showthread.php?p=21277632#post21277632
Sent from my MB860 using XDA App
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.
A while ago I have a weird problem. When my phone is on charge and I turn on 3G it keeps turning off like I would removed the battery. Everything fine until I start an app which uses internet, but when I do it turns off almost immediately. Wi-Fi works fine just the 3G is the problem. I got this problem on two different ROMs (FXP 115, FeraLab v14) and two different kernels (basic FXP115, DoomKernel v6 - medium overclocked), so it must be hardware related, am I right? If not hardware, what else could it be?
Sent from my Xperia X10 using Tapatalk
I had the same exact problem with my Motorola Backflip stock. In fact, if I moved locations where 3G wasn't available to where 3G was broadcasted, it would reboot. I could not fix it with any rom I installed (even tried CM7 which made the phone excellent except for the 3G reboots). I tried full wipes, stock Motorola Motoblur kernel, and everything else. I'm no dev so I didn't try tweaking anything myself and ended up getting rid of it and going with the X10. You can try the SEUS method but it can very well be hardware unfortunately. I hope you have more luck than I!!
If your phone is overclocked that could be a problem. Have a good search though sure I seen this before and think u have to either change something in build-prop or alter/remove a certain process (don't quote me though)
Sent from my X10S using XDA
laneyofdeath said:
If your phone is overclocked that could be a problem. Have a good search though sure I seen this before and think u have to either change something in build-prop or alter/remove a certain process (don't quote me though)
Sent from my X10S using XDA
Click to expand...
Click to collapse
My phone has been overclocked since months, but I've never got this problem earlier, so I don't think that causes it, but I'll give it a try. And I'll search again maybe this time I find the answer. Thank you
Hi, I got a similar problem. Since a few weeks ago, flashed a ROM and when I've tried to use the phone, it keeps turning off randomly, sometimes after a few minutes, sometimes after hours. So, I tried to take it back to the clean original 2.3.3 ROM, but it keeps happening. ¿Any idea? ¿Any solution? Please, help me. Oh, something else, it only happens when the phone's used with the battery, when it's attached to my laptop as modem, the problem doesn't appear.
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.