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

[msh441]

Originally Posted by flapdrol

So my question: Are there people who have not installed .NET Compact Framework 3.5 but have their phone getting stuck in standby?

Can't answer that one. I've installed both NCF 3.5 and 3.7. A great question, though.

I can say that I've been combing through a ton of other info about this issue and I believe I've narrowed it down to a fairly specific set of circumstances:

*Device powers off the screen and goes into standby while a few particular programs are running in the background (either visible, or unseen during the start up process) .

Microsoft actually describes the circumstances/acknowledges the issue in it's testing guidelines for software developers who want thier products added to the Mobile Marketplace. It was an interesting read which stronly suggested that this is a known Windows Mobile issue vs. a specific device defect. Seeing reports of similar lock ups with users of Windows Mobile devices across the range of manufacturers and carriers supports this as well.

Out of all the applications I've installed (easily 40+), I've narrowed it down to 3 particular that will consistantly cause this to occur on MY DEVICE. Now I'm not saying these are the ONLY application that will cause it, or that removing these applications will solve anything. Just that on MY DEVICE, if left running in the background and the device goes into standby, it will consistantly fail to wake up when asked. All three programs are games that seem to consume a fair amount of availible memory.

Taking suggestions from other threads on this issue, I've started doing the following:

1) Scheduled MemMaid to run automaticlly once a day (4:00 AM) to clean RAM, check for registry errors and clear up duplicate notifications.

2) Set the backlight timer to turn the backlight off after 1 minute (as usual), but to go into standby after 3 minutes (gives me time to multitask, while avoiding the lock up if I let the device idel for a couple minutes while tending to some other operation).

3) Run Lumos Wizard 1.0 RC2 with minimum backlight of 1 and a maximum of 7, using a custom adjustment mode similar to "root" mode. NOT A FIX, and I no longer think the backlight adjustment has ANYTHING to do with this lockup... BUT it really seems to help battery life tremendously, and since I adjusted the device to remain on longer (as described in #2 above), squeezing some more battery life while increasing the duration of time it remains "on/awake" is a good thing IMO.

In summary: free up as much memory as possible, avoid confusing the device with clutter/duplicate notifications and conserve power while keeping the device from going to sleep with certain applications left running.

Again, none of these are fixes to the issue, but they don't hurt, either. Combined with a little knowledge as to what causes it on my device, I've gone more than a month now without it failing to wake up from standby.