Touch not waking up from Sleep Mode for Calls and TXT

[anticowboyism]

Here's a new thought, an attempt to find correlation between everyone having this issue:

How many of you who are experiencing this problem have dropped their phone on something hard (like the sidewalk, etc.) Or have received it in the mail with a noticeable damage to the box?

[dequardo]

I think you are reaching here

Mike

[VW]

I threw mine against the wall AFTER it happened... Does that count?!?

[anticowboyism]

well, because we know there is an issue with the battery level. And we know that dropping the phone or jarring the battery causes battery damage, or causes it to not hold a charge as well (common with all Lithium Ion batteries). So there is a link there that dropping the phone could cause increased chances of having this problem.

Also the obvious incidentals of damaging poorly constructed points on the pcb or loosening sockets on the pcb, creating the potential for an intermittent problem. Software/Rom problems don't usually manifest as intermittent problems. Either something is always broke or its not. And they can usually be debugged and are repeatable. There is another variable here that needs to be found. And if it is not software/rom/hacks/etc, then the next logical conclusion would be that the variable is physical. Seeing how not everyone experiences this problem, it can be shown that the problem is caused by an uncommon occurrance. So an uncommon physical occurrence, ie. physical or thermal shock.

[VW]

Originally Posted by anticowboyism

well, because we know there is an issue with the battery level. And we know that dropping the phone or jarring the battery causes battery damage, or causes it to not hold a charge as well (common with all Lithium Ion batteries). So there is a link there that dropping the phone could cause increased chances of having this problem.

Also the obvious incidentals of damaging poorly constructed points on the pcb or loosening sockets on the pcb, creating the potential for an intermittent problem. Software/Rom problems don't usually manifest as intermittent problems. Either something is always broke or its not. And they can usually be debugged and are repeatable. There is another variable here that needs to be found. And if it is not software/rom/hacks/etc, then the next logical conclusion would be that the variable is physical. Seeing how not everyone experiences this problem, it can be shown that the problem is caused by an uncommon occurrance. So an uncommon physical occurrence, ie. physical or thermal shock.

#1 we dont know there is an issue with the battery level
#2 The problem is not shown to be caused by an uncommon occurance, we are on page 22 of this thread
#3 I think it is software/rom/radio. Running s2u2, and not letting the phone go into sleep has fixed tjhe problem for me, albeit with the sacrifice of some battery life

[Exil3d]

I must be lucky. I never had this issue.

[Exil3d]

Im lucky, i never had this issue

[TyRaX]

Does anyone that has the problem always keep their activesync off?

I was having trouble this past weekend with missing calls, so I did a hard reset and that seems to have fixed the problem. I noticed that I forgot to change the setting to keep activesync from being on all the time after the reset. I'm going to leave it on for now (I don't want to change anything now that it wakes properly).

[jamesklyne]

I've had it happen once since I bought my phone back in december. I hadn't soft-reset my phone for like a month and a half...

[Jmoss]

Having the same problem. I haven't even customized my phone. Sometimes it even happens when i'm wearing my blue tooth. This is really frustrating.