sleep of death related to SMS?

[ikediggety]

so, like many others, i've experienced the "sleep of death" many times.

basically, the phone won't wake up without a soft reset, either by poking the hole or doing a battery pull.

i could never quite isolate it to any one thing. it's happened with both BW and adryn roms. it's happened with both 6.1 and 6.5, although it happens much more frequently with 6.5. it's happened much less frequently since reformatting My Storage, but it still happens.

well, last night i think i got it narrowed down. i was sitting in bed, getting ready to go to sleep. catching up on twitter using pocketwit. i exited pocketwit, put the phone to sleep, and went to go put it down on the table. before i could put it down, i got an SMS. went to wake the phone up - nothing. poked the hole and reset.

figured i'd put this out there in case anybody is actually working on this issue.

is anybody else who has the "sleep of death" still using the original smstrigger?

[cg83]

which roms cause this problem? i have yet to be hit with it

[IamReady]

Originally Posted by ikediggety

...is anybody else who has the "sleep of death" still using the original smstrigger?

I have had this happen a few times and am just using the stock sms "stuff".

[volsmcfalls]

I've had this happen on both the stock ROM and some of Adrynalyne's. I honestly don't remember what I traced it back to, but I think it was g-alarm. That or it was the version of s2u2 I was using. On one of the versions I had a problem with one of the settings causing me not to be able to wake the screen. The phone itself would wake, but the screen would not. And it would happen when I received an SMS.

Have you toyed around with the phone to see if the phone itself is waking, just not the screen? I tested this by rolling my finger across the the optical mouse button. When it scrolls to a new icon, you will usually get the short vibrate, letting me know the phone itself was not locked, just the screen was off.

On a related note, I have removed g-alarm and updated s2u2 to a new version (and new settings) and am not having the problem anymore...

[IamReady]

Originally Posted by volsmcfalls

I've had this happen on both the stock ROM and some of Adrynalyne's. I honestly don't remember what I traced it back to, but I think it was g-alarm. That or it was the version of s2u2 I was using. On one of the versions I had a problem with one of the settings causing me not to be able to wake the screen. The phone itself would wake, but the screen would not. And it would happen when I received an SMS.

Have you toyed around with the phone to see if the phone itself is waking, just not the screen? I tested this by rolling my finger across the the optical mouse button. When it scrolls to a new icon, you will usually get the short vibrate, letting me know the phone itself was not locked, just the screen was off.

On a related note, I have removed g-alarm and updated s2u2 to a new version (and new settings) and am not having the problem anymore...

I do not have either of these installed and still have the issue. I will try your suggestion the next time it happens to me.

[volsmcfalls]

Originally Posted by IamReady

I do not have either of these installed and still have the issue. I will try your suggestion the next time it happens to me.

Hmmm...

And your phone will not wake if you press the power button once? Are you receiving any error messages when you restart the phone? I was having another similar issue where I kept getting a "MITsMAN Callback Exception" error. But, it too was related to g-alarm.

[fishingmedic]

I was having that issue a while back w/ Adryn's 6.5 but the problem ended up being Memmaid. Got rid of that and have never had the issue again, knock on wood...

[IamReady]

Originally Posted by volsmcfalls

Hmmm...

And your phone will not wake if you press the power button once? Are you receiving any error messages when you restart the phone? I was having another similar issue where I kept getting a "MITsMAN Callback Exception" error. But, it too was related to g-alarm.

It will not respond to anything when it does this and no errors upon reset. I agree . It has only happened a few times and only since going to a 230## ROM for me.

[ikediggety]

CG83: I don't know for sure. It's hit me with adryn vanilla 2 and 3, and BW night 1.2, which are the only custom roms i've ever flashed.

IAmReady: no, if you're running a custom rom, you've probably got the modified smstrigger. check and see.

volsmcfalls: i have neither g-alarm nor s2u installed... good idea about testing for haptic response, thanks. nope, no errors. just go to use the phone and it won't wake up.

fishingmedic: i don't have memmaid.

thanks for the feedback, everybody. the mystery deepens...

[IamReady]

Originally Posted by ikediggety

...

IAmReady: no, if you're running a custom rom, you've probably got the modified smstrigger. check and see.

How do I check?