HTC TP will not align - endless cycle

[Tilde88]

Originally Posted by bjesparz

My Verizon VX6850 HTC TP first began to inaccurately respond to touch commands that were so minor I thought it was my clumbsy pointing. Became progressively worse.

Tried soft reset, re-alignment no change. Finally and reluctantly did a hard RS. However, now after Win 6.1 start screen I cannot progess beyond the Align window. Endless cycle of screen tapping - I've tapped with and w/o sytlus, slowly, quickly, in lanscape mode, on and on.

Nothing works, other fuctions seemed to be predicated on the completion of Alignment. For now phone is useless. Any ideas?

This is caused by a tiny spec of dust or something inside the screen. If there is any... ANY applied pressure (even if not visible) on any part of the screen, then the place you touch will be misaligned due to the original applied touch. If you can't get it replaced, simply open up your TP (use the SEARCH feature there is someone here who wrote an "essay" on the subject.
After opening it up, remove the screens' plastic protector (what you touch when the phone is on) and clean it... Also, very very carefully clean the actual LCD screen...
Nothing else will fix this...
Unless of course you can get past the Align screen and then figure out (metrically) how many pixels you have to regedit... So that the phone can change its capacitive response... Mind you that the TP uses 4 corner dots to determine the center of the pressure being applied. This is a very big "unless of course"... lol

[bigirb2002]

Originally Posted by Tilde88

This is caused by a tiny spec of dust or something inside the screen. If there is any... ANY applied pressure (even if not visible) on any part of the screen, then the place you touch will be misaligned due to the original applied touch. If you can't get it replaced, simply open up your TP (use the SEARCH feature there is someone here who wrote an "essay" on the subject.
After opening it up, remove the screens' plastic protector (what you touch when the phone is on) and clean it... Also, very very carefully clean the actual LCD screen...
Nothing else will fix this...
Unless of course you can get past the Align screen and then figure out (metrically) how many pixels you have to regedit... So that the phone can change its capacitive response... Mind you that the TP uses 4 corner dots to determine the center of the pressure being applied. This is a very big "unless of course"... lol

^most likly the issue. i know with a instinct when a customer report touch screen problems we scrap dirt out the side of the screen.works like a charm

[wustehase]

Originally Posted by Tilde88

This is caused by a tiny spec of dust or something inside the screen. If there is any... ANY applied pressure (even if not visible) on any part of the screen, then the place you touch will be misaligned due to the original applied touch. If you can't get it replaced, simply open up your TP (use the SEARCH feature there is someone here who wrote an "essay" on the subject.
After opening it up, remove the screens' plastic protector (what you touch when the phone is on) and clean it... Also, very very carefully clean the actual LCD screen...
Nothing else will fix this...
Unless of course you can get past the Align screen and then figure out (metrically) how many pixels you have to regedit... So that the phone can change its capacitive response... Mind you that the TP uses 4 corner dots to determine the center of the pressure being applied. This is a very big "unless of course"... lol

Would this cause a screen to twitch rapidly and not respond to touch input at all (or if any, just sliding the screen one way and then snapping back)? My phone has been driving me nuts for the past couple days doing this. On the TF3D page, it'll twitch and hover between any of 2 tabs, or fling all the way to programs, or keep the home icon selected (over the top of the clock). On the start menu, it'll slide to the extreme top or bottom, and sometimes flings icons around.

Extremely irritating, lemme tell you. I had it apart but didn't think to check the back of the screen just figured it was a connector issue somewhere.