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

[dumpringz]

Wirelessly posted (HTC Touch Pro 2 (Sprint): Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

sprint found a cure for mine ..... replacement phone . if i had a $1 for each time i had to restore my phones through history of tp & tp1 either from replacement or clear storage, i wouldnt be rich but id definetly have an extra 100 bux lol

[msh441]

Originally Posted by dumpringz

Wirelessly posted (HTC Touch Pro 2 (Sprint): Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

sprint found a cure for mine ..... replacement phone . if i had a $1 for each time i had to restore my phones through history of tp & tp1 either from replacement or clear storage, i wouldnt be rich but id definetly have an extra 100 bux lol

Based on your description sounds like youre describing a loose battery issue, not the failure to wake issue described here. Hopefully your new phone will be trouble-free on both accounts.

I can say that using Lumos is NOT a fix. Phone locked up twice today while playing a game.

On the up-side, I found a situation where I can lock it up on demand: playin Prison Tycoon... pause it and minimize it to the task manager. Shut off the screen and it's guarenteed not to wake. Good I guess if I have to pitch the replacement idea to Verizon.

Anyone else able to try this and see if it locks for you,too?

Frustrating.

[p-slim]

my fix is the same as above. I had to get the phone replaced, now everything works fine. Same programs and everything installed.

[msh441]

Originally Posted by p-slim

my fix is the same as above. I had to get the phone replaced, now everything works fine. Same programs and everything installed.

That sucks. I may be doing the same soon enough. Not sure.

Seems like this isn't limited to the TP2. Bunch of similar HD2 users experiencing the same thing over at XDA:

http://forum.xda-developers.com/showthread.php?t=596484

[lgmayka]

I thought I had worked around this problem by turning off Auto Adjust Backlight. But just today, it happened again:

I made a call while roaming. The screen turned off as it usually does when a call starts, but then would not turn back on again.

Here is my latest idea:

I have reinstalled the Quaint Reboot available in Windows Marketplace. This program has two Start Menu entries, Reboot! and Reboot! Now. Reboot Now! requires no screen interaction once invoked. Hence, I can run it from Voice Command.

In short, my solution is not to eliminate the failure-to-wake, but to make reboot much easier.

[ejdavis72]

Originally Posted by msh441

For those experiencing the "failure to wake" issue... where the device is on, the screen is off... but fails to turn back on with the switch at the top I have sort of a question/challange for you.

I'm experiencing this issue, too. Not very often (twice over two weeks now), but I'd still like to pinpoint what's causing it, or motivate those more skilled than I to discover a work-around.

There are many asserting that this is a hardware issue and that the button on the top of the phone controlling the backlight is somehow faulty. I would tend to disagree.

It's been my experiance (all 2 times), that the screen has turned off while ACTIVLY running some program (MemMaid once, and adding a new city on my weather tab w/Conflipper). Each time I've hit the red end/power button (Verizon) and confirmed that the backlight was on. Hit the top button again (since it's human nature to think "maybe I didn't press it hard enough"), but no go. I'd tap the screen with no responce, hit the "back" button for good measure and wait about 10-15 seconds without pressing anything. Hit the top button again after taking a deep breath and viola, the screen turns on. Odd. Maybe just dumb luck, I don't know.

So my preposal is this: If it's a hardware issue w/ the button... has anyone tried pulling out the stylus, as that should wake the device and turn the screen on. If it doesn't, it's a software/power management issue IMO, and NOT a faulty hardware button as some have suggested.

Secondly... If this is a reoccurring software/ROM issue, is there a work-around?


Remapping the "My Button" to wake the device?


Some registry tweek that allows ANY button to wake the device?


Any other ideas?

Again, I don't believe this is physical hardware issue and would like to find a solution rather than go through a handful of refubs trying to find one that works.

To the moderators: I apologize for starting another "my screen doesn't turn on" thread, as I know there are a few out there. I was hoping to start on devoted to finding a solution to this issue, rather than just keeping a running tally of those with the same problem.

I know this group is smart enough to figure this thing out if we put our minds to it (and if it is a faulty button and simply pulling out the stylus actually works, I expect to get about a thousand thank-yous from all of you! jk, of course. ).

Well I own a Diamond and have had this same issue.

The only way I have been able to stop this from happening is by using the program Diamond tweak to disable the fast asleep, sleep, and light sensor.

Then I install Touch in call screen tweak and voila problem solved. But I don't own a Pro and have no idea if the Diamond Tweak will work with it.

Hope this helps.

[BatMan01]

I to have been hit by this problem and until I upgraded to Leo's 23518 Jan 20 release I thought I was having problems flasing ROMS.

I have been trying different custom ROM's from the first week I owned my phone and can't remember how many I have tried. Every now and then I would have the problem where the backlight wouldnt wake up even on incoming calls which was a pain.

Everything was fine since I flashed Leo's 17 Dec Dusk version ROM. Friday I decided to flash Leo's 23518 20 Jan release and at first everything was fine. Then I started to expierence the backlight problem and it got so bad that I have to reset to do anything.

I wiped the device back to default and even flashed back to the OEM ROM that was delivered and the problem has not cleared.

I have flashed, wiped and reset without installing any applications and I agree with those who feel that this is a device failure not software. I just got off the phone with Verizon and they are sending me a new phone.

........

[funkbucket007]

Happened to me twice today for the first time (official WM 6.5) & removing the stylus did "wake" the screen.

[ManInCamo]

Originally Posted by dumpringz

Wirelessly posted (HTC Touch Pro 2 (Sprint): Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

sprint found a cure for mine ..... replacement phone . if i had a $1 for each time i had to restore my phones through history of tp & tp1 either from replacement or clear storage, i wouldnt be rich but id definetly have an extra 100 bux lol

Yup... replacement device from sprint for me as well. Stock rom, NO additional cabs loaded and it would still do it. tried numerous ROMS, locked, unlocked phone, every option. Finally took it in and they swapped it out after two visits for the issue. First visit the reflashed the device, second time (later that day) they swapped it out.

[helix139]

Originally Posted by msh441

Can you explain this function a little more? So you have to have the bluetooth connected all the time? Or at leaqse have bluetooth tuned on from the handset, ready to pair? Are you initiating/cancelling the voice command from the headset, or the device?

I don't use a bluetooth headset very often, and I'm just not sure I would like the tradeoff in battery life. I'm curious, though.

I nearly always have my headset connected, and I always have bluetooth turned on on my phone. As I said in my OP, I use the headset to initiate a voice command prompt then simply say cancel after it wakes up. Sometimes it takes a while, but 98% of the time the phone will wake up. If that doesn't work, I use the redial function from the headset and hang up immediately.