HTC TOUCH PRO 2 SCREEN GOING BLANK and Stays There - Page 7

**Tinkerbell** · #1 (**permalink**) 05-26-2011, 04:13 PM

Awesome!! Glad it is working now. That sounded like a dreadful issue...

jwm22222 · #2 (**permalink**) 05-26-2011, 11:53 PM

Had this problem last couple of days so checked here. Removed Gmail Account. So far no problem. Amazingly, noticed that the very poor responsiveness that has plagued my phone forever, is Gone! Phone responds like new. Removing Gmail is the only change I made.

Moguns22 · #3 (**permalink**) 05-30-2011, 09:58 PM

Google recognized the problem last week and issued this statement in response to all of the complaints:

Thanks to everyone for responding and confirming that things are back to normal with Gmail IMAP access.

We believe the issue was caused by a combination of changes we made to the way Gmail processes IMAP and the way some mail clients (such as Windows Mobile and Android) handled those changes*.

About 12 hours ago we rolled those changes back and we've patched things up to make sure it doesn't happen in the future.

Thanks for your patience while we got to the bottom of this and our apologies for any inconvenience this issue may have caused.

Ethan

*If you're interested in the technical explanation, check out the posts from Brandon, a Gmail Engineer:
IMAP Servers Down - Gmail Help

ppcgpirate · #4 (**permalink**) 06-01-2011, 09:52 AM

I'm experiencing a similar problem too. my screen won't display anything even though the touch works (I can change the volume level by touching the blank screen after pressing volume up/down button (because of the sound que i know its doing it)), which is really odd.

I have the Energy GTX rom for around 4-5 months so far. it was working fine till monday where after making a call i put it in my pocket and it stopped turning on afterwards. (if it makes any difference, i was overseas and had a sim in it but i had no problems using a sim for 2 weeks prior so yeah.)

I did the usual, soft reset, nothing. a hard reset, still nothing showing up. but after doing the following countless number of times, pressing the power button & the end button, taking the stylus out, sliding the keyboard, the display suddenly turned on expect after an immediate restart the display stopped working again. I even flashed a new version of the GTX rom in hopes of getting it to work, still nothing. dunno what to do. any suggestions?

the flash was done via usb cable and double clicking the customruu.exe file. the phone works as i mentioned above, i can receive calls and pick them up by pressing the phone button. it appears the screen works too, i can launch programs by touching the screen but dunno what's launching since the screen doesn't display anything. thanks.

oh, while i had a gmail account on the phone, i had it set to manual refresh and didn't refresh it in a long time.

#5 (**permalink**) 06-01-2011, 04:05 PM

I actually went so far as to factory reset my phone. I'm in a situation where I'm not allowed to run a custom ROM (company phone) and my phone was overheating and draining in a couple of hours (as posted before by someone else). I've also been running the stock 6.5 since it came out and haven't experienced the SOD until the 19th or 20th of May.

Gmail does seem to have been the culprit. Oh well. I was still having the issue today, oddly enough. I actually performed the factory reset today at lunch, about 12:30 EDT.

**Tinkerbell** · #6 (**permalink**) 06-05-2011, 11:44 PM

Since the display is not functioning, it should be fine to return as-is.

eric12341 · #7 (**permalink**) 07-17-2011, 06:00 PM

VINs Neo ROM had that problem too? interesting, I never experienced it past the stock 6.5 rom and the mightyROM.

**Recursion** · #8 (**permalink**) 07-17-2011, 10:44 PM

Quote:

Originally Posted by eric12341

VINs Neo ROM had that problem too? interesting, I never experienced it past the stock 6.5 rom and the mightyROM.

I think the SOD problem has more than one cause. My cause (USB Jack, whether a bent pin, loose solder point, etc.) was hardware related. I had been running 1.31Neo as my base since ... 1.31, really. Tried a few others since, only temporarily as I recall. Never had this issue before this morning. I think it's kinda funny that a simple bending of a jack (whatever it may do), completely fixed the most ambiguous error. I'm quite sure there are software sources for this same type of error, hell, weren't there like one or two kernels that had SOD problems? lmao...

jdwaic · #9 (**permalink**) 10-22-2011, 08:24 PM

It's got to be the software. Mine works fine with XDAndroid, but locks up with Energy rom.

**elesbb** · #10 (**permalink**) 10-26-2011, 01:53 PM

Quote:

Originally Posted by jdwaic

It's got to be the software. Mine works fine with XDAndroid, but locks up with Energy rom.

there are two types of SODs that I have experienced , hardware and software . Very 1st tp2 had the software one , where if manually powered off it would just hang there , but if allowed to go into standby through time delay , it would turn on . 2nd one no matter what rom or OS I was running , the second the device slept , it never woke up again .