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

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. :mrgreen:).

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

This happens to me across multiple ROMs, so I don't think it's a ROM issue. I have noticed a correlation with underclocking though. If I underclock too low in standby, it won't come back on a lot of the time.

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

Its a fairly random issue with Windows Mobile. It has happened on the 5 WM devices I have used. Thankfully, it has become rare.

I'm fairly sure the issue is related to running processes. From my testing a few years back, the screen would refuse to wake up when a process gets stuck in a loop (running cycles endlessly and making the device unresponsive).

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

i have been having this problem for the last 20 minutes, taking out the battery is the only thing i can get to work

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

ive been having this problem ever since i flashed juicys r8 rom. i just hit the sleep button like 10 times then it eventually wakes up! and now im on mightyrom and never had the problem anymore.

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

i hope mightyrom fixes it for me. downloading now, flashing when i wake up

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

That's somewhat consistant with my experience, too. A running program when the backlight timer shuts it off. But to my knowledge none of these programs were loked up. In fact they appeared to be working fine once the device actually woke back up. It seems to be a combination of a running program (possibly in the background, even) taxing memory as the timer shuts the screen down.

And I didn't mean to suggest it could be ROM-related...or sound like any one (carrier or cooked) ROM could be responcible. Only that somthing in the Windows Mobile general programming could be to blame. Seems like the issue crosses carrier, ROM, Windows Mobile version and even device lines.

That said, I don't think flashing a ROM, or even getting a new device would do any good. If its a situation of how you use the device (lots of multitasking, or running programs un-monitored etc.) which determines the frequecy at whichyou'll run into this issue.

OK... I don't know. Just sort of thinking out loud, I guess.

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

I had this problem on Mighty and Juicy's roms. As one said, you have to reset it by either taking the battery out manually then putting back in or using reset button. Very annoying

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

the only time I had this problem was after I installed the SRS WOW audio cab(or sumthin like that) that came out a month or so ago. it sucked because every WM phone I've had did this while stock except this one. hated to see it start , but after removing that audio cab it hasn't done it since

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

I had this problem with my girlfriends TP2. ANYTIME the screen turned off for any reason, it would not come back on until a soft reset. With this phone, it was not random, it was every time.

I played with it for quite a while before finally exchanging it for a new phone.

I have and use Pocket Controller, and if I was hooked up to the computer, I could tell the phone was working fine, would respond to screen presses, just the screen would not come back on until reset.

Stock Sprint ROM.

I did pull the stylus... No go.
I hard reset... No go.

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

Had this happen twice with a famous brand ROM from here and it scared the s... outta me. I have since switched to many many different ROMs and its never happened again. If your running stock with this issue then I don't know what to say.... Replace?

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

ya know I specifically opened this tab because I wanted to say the same thing. I got an SRS audio WOW cab from a friend. When I installed it, it failed to wake almost half the times. I uninstalled that cab and voila! it works fine.

Maybe those roms have some flavor of that cab installed?

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

I think this happened once on Mighty ROM (I ran it for like 2 days). Been on my own Kitchen ROM or Energy ROMs since and this has never happened in like 2 months. Or on my wifes Pro2 either (Same Energy and Kitchen ROMs). Never happened on Prior WM phones either. This the first phone I've run custom ROMs on. My wifes did suddenly drain battery real quick (in a couple hours once on the Energy ROM, not sure what caused that may have left something stupid running).

I do try to keep things simple in both customization and apps.

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

I've only start having this issue when I upgraded to the official 6.5 release. It appears to happen with apps that takes up a lot of memory. Sometimes the screen will come back on with a few toggles between the end key and backlight key...others, only w/ a soft reset..

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

happens to me .. if i slide off the back cover or put a little pressue on the back cover as if im gonna slide it off screen comes on .. if im not mistaken i hard reset the phone after the first time this happened but only cuz i wanted all of annoying SPB mobile shell the hell outta my phone

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

Can anyone replicate this situation on demand?

A specific situation or running program that does it every time when the backlight timer kicks in?

I, too have only experienced this since 6.5, and its pretty discouraging.

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

I am one who made a thread about this problem.

I flashed to Mal's 6.5.3 and haven't seen this problem yet.

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

Have never once had this happen since I started cooking my own.
(wm 6.1 build 21056.1.6.9)

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

OK. I must have jinxed myself by starting this thread... because last night my phone started doing this NON-STOP! Didn't matter which battery I used, or how snugly it fit in the device. Pulling the stylus, opening the keyboard or any combination of buttons. Whether the screen timed out automaticlly, or I turned it off. I tried resetting a couple dozen times and using the device for a bit and it would function just fine... but as soon as the screen went dark, IT WOULDN'T WAKE AT ALL UNDER ANY CIRCUMSTANCES!!!

So since this was happening EVRY TIME(!?!) I figured I had a good oppertunity to see if anything else would effect it, or if I could find a cause. And, well I think I figured somthing out:

Each time my device had failed to wake, I've been in the dark, or at least in less-than-ideal light (like last night running MemMaid or checking e-mail or whatever before I go to sleep). Ironiclly, I was going to log onto this thread and say my device had't done this all day (serves me right, I guess).

So after resetting and trying different things, here's what I found and would like others to try: Turn off the auto-adjust backlight

To do this, go to the HTC Settings tab and select "All Settings" button. From the next screen, select "System" and goto "Power". In the power settings, select the "Backlight" tab. Uncheck "Auto Adjust Backlight" and pick a brightness setting that works for you. Reset and see how things work for you over the next few days. As soon as I turned it off, my device worked flawlessly under conditions where it was consistantly failing to wake.

So for me it seems whether it's a hardware or software issue, it seems related to the light sensor determining the brightness of the screen.

I'll keep my fingers crossed, try it for a few days (or nights) and report back.

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

This was definately caused by the SRS Wow HD audio program. Once I un-installed, everything worked as it should.

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

mine seems to be hardware on my issue. it starts then after about 20 minutes it will finally go back to normal. It happens about once every 2 weeks. If i press on a certain spot on my screen when i try to turn it on, the screen will work but i have to press it in a certain spot.

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

yup, known issue with SRS

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

I hate to say it, but I don't think it's as simple as that. A single program can create that situation. But there are a ton of people experiencing this who don't have that program installed.

Pouring through this thread at XDA: http://forum.xda-developers.com/showthread.php?t=450318

...it sounds like there are some known issues with HTC's auto backlight that can cause this problem. So for now, I stick by the reccomendation to turn off the auto-adjust backlight and if it's a must-have, take a look at installing Lumos to control it instead of the stock HTC programming.

That said, if this issue continues on my device, I'll be the first to post here and say it didn't work and I was wrong.

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

you are correct, this is not software. the first time this happened to me i did a hard reset and the problem didn't go away. also when i went to change the backlight setting it would not adjust at all, even when i moved the display bar. i'm going to look into this further.

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

this wasnt bothering me as my little rig fix worked, everytime i would apply the pressure like i said in my earlier post in this thread but this mornning it wasnt working at all & i had to soft reset. i so dont want to exchange phones or even deal with any rude sprint employees so i am gonna try the auto adjust recomendation. hope it works in the meantime till its figured out

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

So far...this has only occurred to me on my Sprint Touch Pro 2 (stock firmware) after running tricky programs:

1) Internet calling, either Microsoft's own or Fring.

2) "Quaint" Reboot.

Both these programs may be diddling with the actual "phone" part of the device in ways that Sprint and HTC did not expect.

Nevertheless, I long for the days when a complicated device like this would have an easily accessible reset hole.

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

I never had this problem on Verizon stock 6.1 ROM... I now am on Verizon stock 6.5 and have this happen every once in awhile... I have been switching back and forth on internet browsers... and I noticed the only time this happens to me is if I lauch the new internet explorer in 6.5 ROM and leave it open... it does not happen everytime, but maybe 50-60% of the time... yesterday IE was open, and I used the top button to turn the screen off... it then would not come back on... kept hitting the button and then held it down for about 10+sec and it eventually came back on... who knows... :scratch: Just one piece of software I now close/exit all the time...

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

well the auto adjust idea doesnt work on my phone but i also use quaint reboot ... just uninstalled that so i shall report back.

edit- nothing works that ive tried ... every1 seems to be blaming it on a certain app or setting but maybe its just gonna be an annoying everlasting occurrance like tp1 keyboard issue. not 1 time today when my screen has shut off has it came back on without having to do it via soft reset.

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

One workaround I use is using my bluetooth headset to initiate a voice command prompt, then just hitting cancel.

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

Yeah, I originally thought it was memory-related, too. Screen turning off with a program activly running possibly increasing the chances of the device failing to wake up. Unfortunately I've learned that's just not the case.

When it really hit me hard this week (resetting time and time again then freezing each and EVERY time the screen turned off manually, or by time-out while in a dark room), I made a point to have absolutely NOTHING running (activly, or in the background using FDcSoft Task Manager). The repetative and persistant problem ended immediately after turning off the auto-adjust backlight.

I'll still stand by my assertion that it's not a result of any particular running program.

Oh, that's dissapointing news. I really thought I was onto somthing.

I just can't help but think this is a Windows Mobile power management/HTC backlight adjust/HTC backlight sensor issue. It would just make so much sense that a fault in this hardware/software relationship would be causing this issue.

Please do report back. I haven't had mine fail to wake since setting the manual adjust backlight, but now I'll be dreadding the inevitable, once again.:(

Once it happens again, I think I'll install and try Lumos. See if replacing the HTC backlight controlls helps anything (other than extending battery life).

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.

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

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

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.

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

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

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

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

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

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.

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

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.

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

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.

........

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

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

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

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.

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

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.