I'm curious if anyone thats actually completely stock on the 2.2.2 has had any SOD problems at all I've had the DX2 for about a week as a replacement for the fassy and have been reading all I can on this phone before rooting and anything else that gets put out once bootloader gets unlocked and I know this 2.2 is glitchy but never expected a factory stock phone to SOD thanks for any info out there
Care to explain what you mean by SOD. I assume you mean Screen of Death, and if that's the case explain what the screen is displaying. Then again perhaps you mean Sleep of Death, if so I had a few of those on stock un-rooted froyo myself. My suggestion would be to follow the guides posted here and upgrade to GB.
Sleep of death phone goes to to sleep and will not wake with either the power button our home button it just doesn't wake up. on the fassy I had the only time I ever got that was when I was running overclocked at 1600 and undervolted -50 I end up having to do a battery pull but I got the ota 2.3.3 haven't had it since so assuming it was just glitchy 2.2
Related
I recently went from the original leaked froyo rom to super clean 2.9. Ever since I flashed that rom I have had the sleep of death. When I say that my phone has the sleep of death that is Everytime my phone goes to sleep. I have tried many things...I have tried using odin and flashing back to the original and them putting 2.9 and even going to 2.9.1. I have also went as far as not even installing titanium period. I eventually gave up and tried installing DarkRevenge v3 and am having the same results. I guess my only option is to go back to stock non-froyo. I have read that it is a froyo issue, but can't understand why I never had a problem with the original froyo leak. I honestly believe that I had the same kernel every time. I believe that I first had the froyo leak with DL09 then upgraded to the EB01. Let me add that each upgrade I never used voodoo, nor have I ever used voodoo...to my knowledge. I also went into wifi settings and changed the sleep policy to the plugged in option in hopes of saving battery life and thought it might be what was causing the issue, but it is not after switching back and having the same results.
If anybody has any ideas it would greatly be appreciated. I have tried wiping everything and flashing all roms according to instructions to a "T". If my SOD problem with just once or twice a day it would be tolerable, but every time has got to be a pain, especially since I have to take the phone out of the case and do a battery pull. Of course my battery life sucks, but that is acceptable. I am hoping that someone can help me with this issue before I go back to stock. I really like SC 2.9 and DarkRevenge v3 these roms are sooooo awesome. There again I am scared when I go back to stock I will still get the SOD...I hope not.
Thanks,
Leroy \oo/
Having the EXACT same issue ... any success?
I had to go back to a non froyo rom. I went with dl05 super dark with voodoo5 kernel. It runs great with no sod and awsome battery life with no froyo though. I might do some experimenting this weekend and I will let you know if I find any solutions.
Sent from my SCH-I500 using Tapatalk
I have been having my phone shut off for no reason at least 5 times a day. Even when phone is in sleep mode. When I wake my phone I have the bamf toolkit in my notification bar that says unclean shutdown settings not applied, that's how I know it keeps rebooting while in sleep mode. Only reason I haven't made the jump to 1.7 is because I like the extras that are made for 1.6.3. I didn't wanna try and flash 1.7 and then apply 1.6.3 mods. Running stock kernel that came with Rom. It didn't used to do anything like this when I first installed it. It seems like it's getting worse over time. Anybody else having the same problem or similar? Any ideas or thoughts would be helpful. I'm actually thinking about putting GB back on. I just wish I knew what the odds of me ending up with a expensive brick were before i put it back on.
I had the same problem. Flashing the second radio on the radio thread finally solved the problem for me.
Hey everyone. My GTablet powers off when idle with all the 1.2 ROMs I have found. I have worked several days now trying to upgrade to something better than the stock 1.1 but everything I have tried will shut down when idle for a few minutes. I have found some GREAT ROMs out there!
Even though I have soft bricked it a few times, wiped the data several times, Had a few boot loops that were entertaining. I have wiped with nvFlash and installed:
Bottle of Smoke a6
Brilliant Corners 1.2
Illuminate 2.1
They all act the same. Is it just mine doing this? You can use it for an hour and it is fine but if you sit it down 5 minutes it shuts itself off and will take 3 minutes to boot back up.
Even though my gtablet over clocked is really fast. Instant on and off is what a tablet should be.. In the end I cannot get things accomplished while I am still booting up.
After a few google searches this looks like a common problem with gtablets, but mine did not start it until I upgraded to 1.2 BL. Odd...
All I can say is that with the latest CM7 with bootloader 1.2, my G Tablet does this sometimes, but not always.
Though it might be a false perception, it seems more prone to do this when I sleep the tablet too soon after I awaken it.
You didn't search hard enough. You need clemsyn custom kernel to resolve the sleep of death issue. I've been having my gtab on for almost a week now (most times in sleep mode) and never had any problem. I encourage you to go to my website in link.
goodintentions said:
You didn't search hard enough. You need clemsyn custom kernel to resolve the sleep of death issue. I've been having my gtab on for almost a week now (most times in sleep mode) and never had any problem. I encourage you to go to my website in link.
Click to expand...
Click to collapse
Great website. Many thanks! Were you having sleep of death problems on all Rom's before you installed clemsyn's kernal or only on 1.2? I've not had a problem but when I read of others it makes me hesitate about switching to a 1.2 rom
So after updating to the 1.2 bootloader and running a couple of different honeycomb roms i found that my gtab was not waking from sleep and had to be full restarted after a couple of mins with the screen off.
I thought it may be because of honeycomb so i recently switched to CM7 for BL1.2. However I am still having the same problem.
The only solution i found when i was running honeycomb, is to run a wifi lock app which keeps the wifi active and prevents the tab from going to sleep, but i can still turn off the screen. However this is terrible for my battery so i really want to find a proper solution to the problem.
On the 1.1 bootloader i ran the stock rom, TNT lite, CM7, Vegantab, Vegantab Ginger. and had no problem with any of them.
I have tried the following to fix the problem since updating to BL1.2:
wiping data/cache/dalvik
re-partitioning storage
NVFlashing
turning off wifi completely
turning off wifi and turning on bluetooth
using volume buttons to wake
adjusting CPU settings to lower and raise CPU speed when screen is off
lowering and raising voltage
leaving power plugged in vs. running on battery only.
Any other suggestions are very much welcome. I want to fix this problem but still be able to run 1.2 and have the latest best roms
bump anyone?
Some people report that Fancy Widgets causes sleep of death. My tablet has the sleep of death only when charging on the dock, Vegan 5.1.1 on BL 1.1.
Any chance you bought a dock or started using Fancy Widgets around the same time you switched to BL 1.2?
My computer is flaking out while installing updates, sorry if this is a double post.
mike_ekim said:
Some people report that Fancy Widgets causes sleep of death. My tablet has the sleep of death only when charging on the dock, Vegan 5.1.1 on BL 1.1.
Any chance you bought a dock or started using Fancy Widgets around the same time you switched to BL 1.2?
My computer is flaking out while installing updates, sorry if this is a double post.
Click to expand...
Click to collapse
nope. no fancy widgets and no other docks. Even on a total clean install with nothing else installed it will go into SOD
I run GtabComb 3.3 on the 1.2 bootloader and i don't have the SOD. mine goes to sleep and i can wake it up everytime. so i don't think it's the 1.2 bootloader unless the creator of GtabComb figured out how to fix it.
Sleep of Death, HC 3.3 BL 1.2
Just echoing the first note, and confirming that I have the same combination (HC 3.3, BL1.2) with no extras, clean install, and continue to bump into Sleep of Death. Sort of a nuisance. Tried most of the items listed in thread #1, but still no success.
So, in reply to the previos comment, I return to Bootload version 1.2 as the culprit, and not Honeycomb 3.3. Maybe some interesting combination? Will review the files and try to follow-up with a note.
Thank you.
Well that sucks I guess but I can assure you after wiping my device as I normally do when switching roms, all I did was load GtabComb 3.3, wiped data, wiped cache, wiped davalik and reboot. No sleep of death.... EVER nothing wrong with the 1.2 bootloader here
im thinking its just a random problem with a select few devices. If everyone had this issue with BL1.2 im sure we would have heard about it.
but from what i can tell a select few devices had SOD with 1.1 and some have had issues only with BL1.2 like myself
It could just be the hardware. I have had the SOD (or it just rebooting) since day 1 across different ROMs, bootloaders, and stock.
i will say i had the SOD when i was using CM7 on the 1.2 bootloader but when i switched to GtabComb it stopped. i also don't thing i had it when i was on Flashback either. it was just CM7
Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Seems like your system files might be corrupted. Wipe system partition from fastboot or cwm then reflash your rom. Any time I had weird stuff happen on a rom, I wipe the system then it goes away. Hope this helps you get rid of this issue. Good luck!
Sent from my MB860 on CM7.2.0 Stable
Doesn't work, just wiped system, cache and dalvik, then flashed rom and sod's still happen.
I have also tried flashing several radios, all with sod's. Any suggestions?
wakelock
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
affiatic said:
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
Click to expand...
Click to collapse
So you've had SODs since you got the phone? Wakelock seems to work, but kills the battery.
For anyone who does NOT have SODs what modem/radio are you using?
Yes had them since I got the phone. Wakelok fixed it for me. Battery life is not horrible. It still last me like 14 hrs moderate use. I have tried radios and everything else I could thing of. Think mine is hardware related. That is why I am sending it in. I was surprised to find out it was still under warranty
I've just noticed that when mine shuts down, it gives a green notification first, then when I try turning the screen it, it reboots.
Unfortunately, my phone is out of warranty, I bought it used
SODs still happen in airplane mode.
Try wakelock and post if that fixes it.
Call Motorola directly. I bought two used. Had the same problem. They replaced them both with new units.
Motorola Android Department
1-800-734-5870
Just don't say anything about buying it used.
Good luck.
As posted above, wake lock works but uses battery.
I live in Canada and am out of warranty, would I still be able to call?
It's worth a try. You have nothing to lose.
Sent from my MB860 using xda premium
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
javinavas said:
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
Click to expand...
Click to collapse
Is there something specific about 35C, and are you sure it is exactly that?
I have installed 2.3.6 Bell and I still get reboots, anyone have a link to stock 2.2.1 Bell SBF that I can try?
sometime 35 sometime 36.. but above that temp.. sod kills me.. under that temp phone runs smooth..
I'm a system enginner but I haven't program in years.. I'm thinking seriously in create just a services to read temp and launch a wake lock when temp reache some level..
I'm pretty sure I will help lot of people but aint sure when i can start doing some work
dancom96 said:
Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Click to expand...
Click to collapse
my phone would not actually reboot but in went into SOD (sleep of death) so every time this has happened to me i installed a new kernel or reinstalled the one i had.........always rectified the issue.
Same issue
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
jediknightbrodie said:
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
Click to expand...
Click to collapse
Tried several of them, this seems to happen on stock 2.3.6 as well.
I flashed a stock sbf to return to stock. Still had the sleep of death. Reboots after and during phone calls, and touch screen problems. I believe it is hardware related.