For those experiencing the "failure to wake" issue...

[Laos101]

ive had it on my TP and TP2. it happens rarely, but i see it occur more commonly when you dont use your stock radio and try to flash a new radio.

[AZTECHKA]

Originally Posted by dalastone

glad to hear your replacement is working! wish i could duplicate it at will so i could show sprint. anyway, after yet anotehr hard reset, i the reflashed the stock 6.5, did another hard reset...so far it wakes everytime. and now it seems to wake instantly where before it wold take a second, or two...or not wake. so far so good though

That's so great to hear... Not to jinx you or anything. But when it first started happening to me I did have a few days when I thought the problem was solved... I restored OLD backups to before the problem started and then..... You know what happended.
But towards the end there I was soooooo ready to just throw the phone out the window of my car and watch it skid along the road.
I love my phone again.
p.

[KyleAsher]

I thought it was my SIM card, I took it out and it worked fine.


Until 24 hours later! when it started doing it again. Once screens off its OFF for good even though device is on! You can hear it chime with you hit end, or any keys.

[KyleAsher]

Originally Posted by AngelDeath

I posted about this problem over at XDA, there is a correlation with the weather, facebook, and twitter. What the correlation is I dont know, but one of the problems I can tell you I noticed is When the weather changes to Rain, and the today screen has alot going on, with rain, the wiper blade, and what not, it seems the screen goes black, and wont wake up. But the Rain animation does have a part to play in it along with your memory running low. It seems it goes into like a infinite loop, or crawls to where it wont wake up, but you dont have to take the battery out, you can hit the reset button on the side under the cover to reset it. But the weather definitely plays a part in it, search for the thread in XDA that was posted by me.

I formatted the phone back to original stock 6.5. Had not set up weather, facebook, twitter, nothing. just from turning on the phone. Even at the touch screen to start using your device screen if I did it it would be off permanently. Still was doing the same thing....

[vzihome]

Guys should check my thread out think I found a fix for this problem. SOD fix(Sprint confirmed)

[lefty11]

Originally Posted by vzihome

Guys should check my thread out think I found a fix for this problem. SOD fix(Sprint confirmed)

checked it out, sounds like clear storage, hard reset, reflash, etc. I think that a lot of people are looking to isolate the problemso they do not have to switch roms or hard reset ..

Also, to some experiencing issue, if possible, try having someone call phone or if you have another line avilable, call your phone. It seems to wake mine up, Sometimes its easier to do that than soft resetting and it gives me a bit of confidence that I am not missing calls

[PodexPerfectusSum]

I didn't have this "standby of death" problem until I applied Verizon's MR2 update. For a number of reasons, I flashed back to MR1 and I'm still having SoD problems.

I've read through this thread and the one on xda-developers and I've tried just about everything that's been mentioned unless it's clearly crazy. I've come to believe that this problem is definitely because the device becomes busy and ignores the backlight button. The behaviour I'm seeing just isn't predictable, sometimes sliding the keyboard open wakes up the device (usually only if it's locked), removing the stylus never does anything except turn on the backlight for the answer/start/back/endcall buttons...sometimes. Sometimes I can turn on a bluetooth headset, or plug in a charger, or connect it to a PC, and hit the backlight button and it'll turn on.

Usually, I have to either send it an SMS (google voice ftw) or call it to get it to wake up.

It'll always come back if I leave it for a few minutes.

This sounds to me like the button to turn on the backlight isn't being given a high enough priority on the CPU and the CPU is therefore allowed to ignore the button being pressed. Now, I have no idea how Windows Mobile works internally, but this seems like a simple software fix to raise the priority of backlight button events.

[aiiee]

Originally Posted by PodexPerfectusSum

I didn't have this "standby of death" problem until I applied Verizon's MR2 update. For a number of reasons, I flashed back to MR1 and I'm still having SoD problems.

I've read through this thread and the one on xda-developers and I've tried just about everything that's been mentioned unless it's clearly crazy. I've come to believe that this problem is definitely because the device becomes busy and ignores the backlight button. The behaviour I'm seeing just isn't predictable, sometimes sliding the keyboard open wakes up the device (usually only if it's locked), removing the stylus never does anything except turn on the backlight for the answer/start/back/endcall buttons...sometimes. Sometimes I can turn on a bluetooth headset, or plug in a charger, or connect it to a PC, and hit the backlight button and it'll turn on.

Usually, I have to either send it an SMS (google voice ftw) or call it to get it to wake up.

It'll always come back if I leave it for a few minutes.

This sounds to me like the button to turn on the backlight isn't being given a high enough priority on the CPU and the CPU is therefore allowed to ignore the button being pressed. Now, I have no idea how Windows Mobile works internally, but this seems like a simple software fix to raise the priority of backlight button events.

I don't understand why you're flashing VZW ROMs when you're on AT&T but whatever Flash Mr. X' 'fixed' MR2 ROM, no more SODs.

[TLJester]

I found BING navigation was causing SOD.
After yet another firmware install/wipe, this time I did not install BING and have had no problems!

Also try disabling contacts auto syncing with Facebook - that made a huge difference for me.

[eclone]

I've been having this problem for a few days. Had over 1k in text msgs, cleared up 700 and some random logs etc in my device folders. Problem have seem to gone away :fingers crossed: