Related
I did a DIY digitizer replacement a month or so ago, and its been working great up until a few days ago. Now, when I go to touch one of the soft buttons or type on the keyboard, the phone "flips out" and starts registering inputs in all random spots, sometimes getting stuck on that spot. I am totally stumped.
I double checked and all the ribbon cables are seated and such, and tried flashing over to Modaco rom from Cyanogen (thinking it might be software)... no luck. Can't even replicate it consistently, it seems to have a mind of its own.
Any thoughts as to what is going on?
Well I know that it has been an issue for some people and the general idea is that if you push the power button and put the screen to sleep and then wake it back up 20 seconds or so later it will work again. I have to say to also wipe your screen clean as well, build up on the screen can cause wonky behavior as well. Good luck.
Mike
this sounds exactly like the glitch that all nexus ones have, stock ROM. just lock then unlock the screen and it fixes itself.
the word is that it will be fixed with the 2.2 update. fingers crossed.
I thought it was that issue I read as well, but the power button glitch-fix everyone speaks of doesn't work.
I actually used my pry-tools to unseat the digitizer from the rest of the phone and kinda let it dangle, and 90% of the issues disappeared.
I am wondering if it might be the digitizer pressing up against the metal backing thats causing it to ground out and cause these issues, since the original phone was held in by a foam-type adhesive which I don't have on it now.
that's very possible. the power button resets my glitch 100% of the time. so sounds like something else is going on with yours.
RogerPodacter said:
this sounds exactly like the glitch that all nexus ones have, stock ROM. just lock then unlock the screen and it fixes itself.
Click to expand...
Click to collapse
I don't think its the famous touchscreen issue that we've heard because it was reported to register a click few centimeters below the touch point. Here in this case, the guy says that it randomly registers clicks at different spots.
AlexTheSquid said:
Now, when I go to touch one of the soft buttons or type on the keyboard, the phone "flips out" and starts registering inputs in all random spots, sometimes getting stuck on that spot.
Click to expand...
Click to collapse
I hope that reboot fixes this problem....
I've given up on the task for now, went back to my iPhone 2G till I can figure this out... its definitely not software though... and the digitizer still registers accurately when I don't have it seated into the phone...
No issues here on cyanogen 5. 0. 6 I love this Rom and have 0, yes I said it zero issues..... running solid for almost a month.... sorry ya have them issues I hope ya get em figured out...
As others says, just a quick lock & unlock fixes this. No need to wait 20 secs, I do it right away. Power, power, slide to unlock and I'm back in business.
For me I'd say it happens maybe a couple times a week? What about other people?
On stock it happened like once a week.... for me
none on custom so far after 3 weeks
yeah a couple times a week is it for me too. I wonder if view identified the issue and fixed it in the update. I'm sure some Google employees experience the bug.
17/9/2010 EDIT: With a lot of feedback from this thread and other threads, it has come out that, waking up the phone with the YES/CALL/SEND green button is BETTER than waking up with the NO/END/POWER red button for SOD reasons.
----
Hello guys,
You probably know I am actively in the Android HD2 porting community.
I am having the strangest touch screen problem. I am really experienced into winmo and android stuff. Please read carefully.There is a surprise at the end.
BOTH under Android AND Winmo my touchscreen works just fine after bootup.
It first started like this:
At first my touchscreen stopped responding when I hold no button to make a reboot/power off. I thought it was from the usual Android touch screen freeze related to g sensor. Then I realized that it was the same in Winmo! Holding no button ALSO caused touch screen to die even under winmo.
Then it started loosing touch after sleeping. My touch is ALWAYS working when I boot winmo OR android and works for hours if not put to sleep. But it stops working after putting it to sleep.
Frustrated,
I restored with spb backup. Didn't work.
I reflashed my winmo rom. Didn't work.
I made a hard reset. Didn't work.
I removed sd card. Didn't work.
I removed sim card. Didn't work.
I changed the date. Didn't work. (this was a strange fix for some blackberries)
I flashed original 1.66 Turkish rom, 2.07 original old radio, even original 1.42 SPL which makes this hd2 fully stock the day I bought it. Even made another hard reset. Still didn't work!
By this time it's obvious this is a hardware problem and needs warranty.
OK
THEN I FOUND THE STRANGEST THING:
If I wake up the phone with ANY hard button other than the NO/HANGUP button touch screen WORKS!!! (Yes/Send button under Android)
BELIEVE ME, I HAVE TRIED FLASHING REFLASHING RESETTING AND TESTED 100 TIMES and YES it is ALWAYS the same. This is not a random thing.
If I wake up my phone with No button under ANDROID OR WINMO, my touch doesn't work. But if I wake up with back button windows button home button yes button, the phone wakes up properly AND touch works. Android of course doesn't work with the original radio, so I wasn't launching Android with the last test.
HOW IS THIS POSSIBLE AT ALL?? It looks like hardware fault, but touch loss IS related to NO button!
I will send my phone to warranty anyway but it will happen after the holiday (not before mid september)
IF ANYONE have an issue like this, PLEASE post.
I just want to make sure this issue isn't related to Android porting. If it is, this might be an important info. Maybe it may help devs fixing the general touch screen and wake up problems. Also everybody TRY waking up Android with the yes/send button to see if it helps with your wake up or sod issues and provide feedback. Also it may help with the phone not responding after hangup in Android. There is something hardware going at the background with the no/hangup button. I know this issue is hardware fault but still may shed light to our problems with touch screen and wake up issues. Maybe there is something hardware or firmware inside the phone waking up the digitizer. I know that hangup/no/end button is internally different than the other buttons, something like it shares the power button function that is usually on the top of the device with other htc devices. (Mine is a european hd2 and the hangup button is not red) I also wasn't using an overclocking kernel.
Please think twice before posting, and don't post anything useless. I am absolutely no noob, you can search my previous 200+ posts. I wouldn't post anything unless I am definitely sure. And I have a feeling that this thread has the potential to help or make something come out. If it doesn't, no harm done.
since most of the time inwinmo or android the no or yes button pop up generally on the same side in both os's and , taking in consideraton it might be a hardware issue , i would say you issue might be a harsware issue undr the screen when you touch no...wild guess
I was the same problem.... but it is even worst for me now...
Before, at least work touch others buttons... now my touchscreen DON'T WORK. :-(
I suppose that it's a hardware problem :-(
memin1857 said:
Hello guys,
You probably know I am actively in the Android HD2 porting community.
I am having the strangest touch screen problem. I am really experienced into winmo and android stuff. Please read carefully.There is a surprise at the end.
BOTH under Android AND Winmo my touchscreen works just fine after bootup.
It first started like this:
At first my touchscreen stopped responding when I hold no button to make a reboot/power off. I thought it was from the usual Android touch screen freeze related to g sensor. Then I realized that it was the same in Winmo! Holding no button ALSO caused touch screen to die even under winmo.
Then it started loosing touch after sleeping. My touch is ALWAYS working when I boot winmo OR android and works for hours if not put to sleep. But it stops working after putting it to sleep.
Frustrated,
I restored with spb backup. Didn't work.
I reflashed my winmo rom. Didn't work.
I made a hard reset. Didn't work.
I removed sd card. Didn't work.
I removed sim card. Didn't work.
I changed the date. Didn't work. (this was a strange fix for some blackberries)
I flashed original 1.66 Turkish rom, 2.07 original old radio, even original 1.42 SPL which makes this hd2 fully stock the day I bought it. Even made another hard reset. Still didn't work!
By this time it's obvious this is a hardware problem and needs warranty.
OK
THEN I FOUND THE STRANGEST THING:
If I wake up the phone with ANY hard button other than the NO button touch screen WORKS!!! (Yes button under Android)
BELIEVE ME, I HAVE TRIED FLASHING REFLASHING RESETTING AND TESTED 100 TIMES and YES it is ALWAYS the same. This is not a random thing.
If I wake up my phone with No button under ANDROID OR WINMO, my touch doesn't work. But if I wake up with back button windows button home button yes button, the phone wakes up properly AND touch works. Android of course doesn't work with the original radio, so I wasn't launching Android with the last test.
HOW IS THIS POSSIBLE AT ALL?? It looks like hardware fault, but touch loss IS related to NO button!
I will send my phone to warranty anyway but it will happen after the holiday (not before mid september)
IF ANYONE have an issue like this, PLEASE post.
I just want to make sure this issue isn't related to Android porting. If it is, this might be an important info. Maybe it may help devs fixing the general touch screen and wake up problems. Also everybody TRY waking up Android with the yes button to see if it helps with your wake up or sod issues and provide feedback. Also it may help with the phone not responding after hangup in Android. There is something hardware going at the background with the no button. I know this issue is hardware fault but still may shed light to our problems with touch screen and wake up issues. Maybe there is something hardware or firmware inside the phone waking up the digitizer. I know that hangup/no/end button is internally different than the other buttons, something like it shares the power button function that is usually on the top of the device with other htc devices. (Mine is a european hd2 and the hangup button is not red) I also wasn't using an overclocking kernel.
Please think twice before posting, and don't post anything useless. I am absolutely no noob, you can search my previous 200+ posts. I wouldn't post anything unless I am definitely sure. And I have a feeling that this thread has the potential to help or make something come out. If it doesn't, no harm done.
Click to expand...
Click to collapse
BIt strange this one to be honest I think it may just be your device as there are now hundreds of users of android on the hd2 and this is extremely rare. Hopefully a dev will look into and find a possible solution but I doubt it. If I was you I would put it back to stock and send it off to HTC for a new one. Even if a dev manages to find the problem you will have a new or as new hd2
I have been trying and I must say that I sort of do share your experience. The most left button (referred to as yes) awakes the phone just right as where the most left (No) takes its time to start the phone. I haven't had any noticable touch issues that could be related to these hard buttons yet.. (I think)
But I do think you have a point.
Interesting, I had something similar. I was using elegancia rom v1 for the longest time, with all my android builds, no problems. Then I went to chunkydroid rom, and had a few issues, with multiple android installs (one of which was my original that was working before.)
Then I rebooted into chunkydroid, (windows), and had the same issue. It was strange. I tried a few other roms, same problem. Turned off the phone, next day, reflashed chunky again, and hyperdroid 1.1, no issues since. (Only difference, which I don't know if it's related, but again, might help, is that I was overclocking. I have since not let anything go above 998 in setcpu, and even removed all builds that were overclocking. I though it might have had something to do with it (and the phone wasn't warm at all.)
I have not been able to duplicate the problem since though (even with overclocking just to see). So I'm pretty stumped. I'm sure the devs will work it out.
I have taken to pressing the yes/send key to wake up my phone as it seems more consistent than pressing the end key. My theory is that multiple wake up/sleep messages are being sent on the end key and the system gets confused. Some sort of debounce might help.
Just my thoughts.
Running shui8 realstock rmnet with micyprima r9.
It seems waking up the phone with the Yes/Send button somehow seems better with current builds and kernels.
I am asking everybody reading this thread to try waking up their Android devices with the yes/send key and share their experience if it is making their Android wake up quicker with less SODs.
Note: I am still using yes key wake up as a workaround for my hardware touchscreen fault. Still absolutely works everytime. I found out that if I accidentally try to wake up with the no/hangup key I need to wait about 10-15 seconds before yes/send key does its magic again.
well, i tried there is absolutely no difference between any hard button. if i have sod, none of them solves... actually its not sod i think, when you try to put standby and wake up several times quickly, screen stops responding for a while. you need to wait at least 15 seconds between each standby and wake up. can i fix this? or this is the sod?
Waking up with the yes/send button would not make any difference if your phone can wake up good with the no/hangup button already. But we are trying to find out if yes/send button wakes up better in long term usage. (no/hangup button sometimes can't wake up and that is the sod refers to)
SOD happened to me few times too with the NO/Hangup button and if/when that happens, if you press NO/Hangup button for long(for the menu with the turn off the phone,reboot,plane mode,...etc options) screen comes back BUT sometimes it locks the screen brightness to lowest possible setting(with %0 actually it doesn't completely turns off as you know).
Other than that "bug" NO/Hangup button works fine for me but as the OP, YES button is more stable and no SODs happen with the YES button...
Btw there is no difference for me YES button vs NO/Hangup button by means of quickness... Both works the same speed unless of course there is no SOD with the NO/Hangup button...
Just wanted to share my experience...
This thread is awesome
Thanks for this thread. I have been trying to use any android build for at least a full day with no success. Ive used different winmo roms and radios such as chucky and miri roms. I still ran into sod's. After waking with the yes/button i have had no sod issues since then, Once again awesommmmmmmme thread.
After some time my digitizer died almost completely. (Issue became worse) It is currently being handled under warranty. (digitizer is replaced)
But at least with a lot of feedback from this thread and other threads, it has come out that, waking up the phone with the YES/CALL/SEND green button is BETTER than waking up with the NO/END/POWER red button for SOD reasons.
any solution to this issue yet because i just started having this exact same problem w/ my HD2 yesterday before that it was perfectly normal and all the suddon the Power/END/NO button wake up cause the screen to not respond to the touch at all however wake up w/ home,back,menu,call button the touch screen works is back to normal
still can't figure out if its a hardware or software problem cause i also tried flashing bunch of roms/radios/and android roms as well and even went back to stock rom in hope for a solution
waking with green is about 2s faster for me.
Same thing happens to me before 2 days.I tried many hard resets,roms,radios and my screen didnt work.I couldnt even login in wm.
My screen was completely dead.The last thing i did,before my screen goes unresponsive was to push no/hangup button in android to open it
At first also i thought it was a g-sensor issue,but then realise that it was much more than it.
Until the moment i read this thread
The way it worked for me
I open the device with no button of course,made a soft reset from red hole and i wait until the device goes to standy itself.Then i open it from send button and voila touch is back !!!!
Strange thing but it works.Thank you very much you are a genius
sure the touch comes back when it wakes up using all other buttons except the power/end button so why is that all the sudden the power/end button causes the screen to go unresponsive
like for say when i hold the power/end key to open the pHONES OPTIONS in windows or android once the PHONES OPTIONS shows up and i try to click on power off or reboot on the screen the touch doesn't respond so the only way to reset or power off the device completely is the either use the reset button in the back or pull the battery out
i'm going to be sending it under warrenty/insurance to t-mobile and hopefully get a replacement cause i'm so use to the power/end button to wake up my device...
Guys be extremely carefull when using hard buttons in android.Finally my problem with screen is not the end button but the back arrow button.This button is necessary for using android and i have pushed it many many times the last months as i am using android.Νοw every time i pushed it my touchscreen stops responding.Τhe last time i pushed it my screen stopped responding(i thought for ever) and didnt knew the exactly reason that this happens.Because i didnt want to send the device to htc (firstly i must send it to expansys in france and they will send it to htc) and take it back at christmas i decided to go to a local mobile service.I wasnot mind for warranty cause i wouldnt be able to live 4 weeks without hd2.I was ready to give 600euros to buy desire hd
Result from service
At firstly he said to me that hd2 have no touchscreen problem and it works ok
I paid 20euros for opening the device and took it back.At first 5 minutes my screen stopped responding again and didnt knew the reason.For my good luck i leave the device untouched 10 minutes and the screen come back again.Then i used it and the time i pushed the back button the screen stopped working,fortunatelly for little seconds.Now i know.My screen stop responding when i push back button.So i change the keylayout to my android build and now i push send key instead of back and volume up key for menu and volume down for power on-off and hd2 works perfect after 24 hours without touching the back button
Also in monday i will go to service again to fix the button problem
Same issue with me
Exactly same issue with me. I have been using Winmo and Android on and off in my HD2. couple of weeks back, touch didnt respond after waking up the device from standby by pushing endkey.
tried everything - flash/stock rom/removed SD card/ hard reset/clear storage/custom rom/ battery pull out etc...
touch worked suddenly and only when i slightly touch the end key instead of pushing it fully, the start menu opened..this happened for few days and when ever i push the end key...screen goes unresponsive. all other hardware buttons are working fine and if at all i push end key the issue starts.
unfortunately my friend pushed the end key once and the screen never responded after this....now am using my old p3450 htc touch...
i think if we change the AP BOARD (Flex ribbon-keyboard chip) everything will go back to normal coz its not the problem with digitizer or the lcd of the software for sure.
trying to order one in ebay, we can change this ourselves...no need to send it to service centers and waste money on it.
if any of you have done this already...let me know if it worked for you.
guys dont know if it is allready known but there is a app called sidebar style swkey
http://forum.xda-developers.com/showthread.php?p=9726110#post9726110 which puts software buttons in the screen.This app is definitely button saver
Alright, so here's my problem. My touchscreen won't response to any finger movement. I could press the hardware buttons like power, volume and talk and it response to that but my problem is mainly trying to get inside my rom. I tried flashing rom via NAND and via clockwork mod and nothing helps. The G Sensor seems to work just fine because it rotates the screen when I'm inside my ROM. I could go back into MAGLDR but I don't think anything there is going to help?
Has anyone else experience anything like this and if so, what did you do to solve it?
had same problem, found a FIX
i have had same problem past couple of days. i was running darkstones SuperRAM_FroYo_V1.5 build with oz 2 cleanex rom. i know that every now and again it would be a pain to unlock the device with the agonising wait for the lock screen to show up but this time the touch screen would not work at all not recognising any movement and not dragging the unlock button across. i would have to take the battery out and restart, even some times touch screen would fail completely when in winmo too, got to a point when 3 days of working then not working and taking the battery out a million times to boot back into android to unlock the device, then touch screen died completely.
FIX- Hard reset
will reset windows mobile. all data on device will be lost.
hold down up-vol key and down-vol key, soft reset button and then power button till it displays formatting screen. follow on screen instructions.
hope this helps.
tidygrant said:
i have had same problem past couple of days. i was running darkstones SuperRAM_FroYo_V1.5 build with oz 2 cleanex rom. i know that every now and again it would be a pain to unlock the device with the agonising wait for the lock screen to show up but this time the touch screen would not work at all not recognising any movement and not dragging the unlock button across. i would have to take the battery out and restart, even some times touch screen would fail completely when in winmo too, got to a point when 3 days of working then not working and taking the battery out a million times to boot back into android to unlock the device, then touch screen died completely.
FIX- Hard reset
will reset windows mobile. all data on device will be lost.
hold down up-vol key and down-vol key, soft reset button and then power button till it displays formatting screen. follow on screen instructions.
hope this helps.
Click to expand...
Click to collapse
well i have woke up this morning to be able to unlock my device to then locking it and not being able to unlock it again!!! i had notification to say it had managed to restore 16 apps whilst i had been asleep so i am thinking there is a dodgy app out there some were
mazdarider23 said:
Alright, so here's my problem. My touchscreen won't response to any finger movement. I could press the hardware buttons like power, volume and talk and it response to that but my problem is mainly trying to get inside my rom. I tried flashing rom via NAND and via clockwork mod and nothing helps. The G Sensor seems to work just fine because it rotates the screen when I'm inside my ROM. I could go back into MAGLDR but I don't think anything there is going to help?
Has anyone else experience anything like this and if so, what did you do to solve it?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA Premium App
I have this problem and have found no way to fix it, I have tried everything except possibly going to the clk loader instead of magldr. when i put the phone to sleep with the power button is when i have the issue of not being able to unlock my phone in Android. I have tried task 29, going back to original windows roms, sd and nandroid, it is a hardware issue related to the digitizer as far as I'm concerned. I love my HD2 and really need to fix or find another one. I know this doesn't help, but maybe a little more insite if nothing else
I had the same issue. With my 1st HD2 it started as an intermittent problem, then eventually completely stopped working. With my replacement it just started to happen again. I immediately flashed back to stock tmo windows and the touchscreen would work so long as I did not try and put the phone on standby or wake the phone using the end key. If the phone went to standby on its own, the touchscreen would not work either. I changed the settings so that the phone would not go into standby at all. I then learned that locking the phone from the windows menu and allowing it to go to standby that way somehow averted the touchscreen problem. After 2 days, the problem seemed to resolve itself, almost completely. If I try and wake it using the end key, the touchscreen still wont work, but every other button on wake works. Also, putting it in standby with the end key seemed to not cause the problem any longer.
I dont know if the issue varies per person, but what worked for me was going to stock windows for a couple of days, then starting over with android. I guess it depends on how far along the problem has progressed.
Look at my thread in my Sig about the Unresponsive Screen Solved. This sounds exactly as that. And there are various workaround solutions through out the post.
Hey guys, sorry for putting of "one-of-these" posts, but I've searched as many forms as I could to no avail regarding this particular problem: my lock-screen and my power/reboot screens are completely unresponsive when brought up. Well actually, the lock-screen will unlock with maybe 10-14 tries (by pressing the power button to turn the screen off and pressing it again to turn the screen on) but even thats kind of wonky.
I've flashed every Android Rom I could get my grimey hands on to see if that would fix the problem, and it doesn't, I've even tried dropping back to WinMo 6.5, nope. Now if I flash WP7, than the lock-screen is responsive, but I'm an Androidian and can't use WP7 for more than maybe 20 seconds.
I'm unsure as to whats causing the problem, at first I thought it may just be a hardware malfunction (as I use my HD2 to watch movies and TV shows quite a bit) but after flashing WP7 and finding that to work well I'm at a loss.
I'm running on Magldr 1.12
SPL-2.08 HSPL 8G
If there is anyone who could help, please do, as I love my HD2 flashed with Android....I'd really hate to have to flash WP7 to use my phone.
Thanks in advance!
I read this somewhere so it might work for you. Turn off auto brightness and screen rotation, it supposedly reduces the wakeup lag.
Huzzah! Thanks a bunch, that little trick helped out!
Nvrmnd, it worked maybe for about 4-5 unlocks and now reverted back to the old problem. Power-off/reboot still doesn't work.
I'm having the same problem.
Like you, I've been flashing many other roms (stocks, 6.5, and androids) and still same problem.
Have you fixed yours yet?
same problem
Same here... Any one able to find out the solution?
This exact problem happened to my phone today
If im understanding well, the screen is no more toucheble, i mean the bottons ( in the bottom) are working and the phone react to them but the screen does not react to the touches....
what can i do ?!?!?!??!??????
pls help me....
forza juve said:
If im understanding well, the screen is no more toucheble, i mean the bottons ( in the bottom) are working and the phone react to them but the screen does not react to the touches....
what can i do ?!?!?!??!??????
pls help me....
Click to expand...
Click to collapse
This seems more like a bad digitizer....try to press the power button down (kind a hard) and at the same time try to unlock your phone or touch the screen to see if it reacts to your touches and if it does, you have a bad digitizer because the minute you release the power button you are going to have the same issues again...the digitizer connector goes under the power button and it sometimes breaks causing that issue, you need to replace your digitizer, no way around it, sorry.
So for some reason, the last few days the touchscreen on my phone was being super slow, and id have to turn off the screen, then turn it back on multiple times and keep trying to slide it to unlock. I dont know how this started. Ive been using the NexusHD2-Gingerbread V2.9.
Ive tried other ROMs and restored previous backups and nothing is working. The screen is still not responsive. Ive never had this happen before and not sure what else to do. Its just stuck on the lock screen but everything is unresponsive....any ideas???
AEBobby912 said:
So for some reason, the last few days the touchscreen on my phone was being super slow, and id have to turn off the screen, then turn it back on multiple times and keep trying to slide it to unlock. I dont know how this started. Ive been using the NexusHD2-Gingerbread V2.9.
Ive tried other ROMs and restored previous backups and nothing is working. The screen is still not responsive. Ive never had this happen before and not sure what else to do. Its just stuck on the lock screen but everything is unresponsive....any ideas???
Click to expand...
Click to collapse
Unfortunately, your touchscreen digitizer is dying. This is related to the hardkey malfunction. The only thing you can so now is flash back to stock WM Tom and send it back for repair. The phone's touchscreen need to be replaced.
Good luck,
Sent from my HTC HD2 using Tapatalk
Try to install everything from scratch and how it goes.
Sent from my HTC HD2 using XDA App
10507 said:
Unfortunately, your touchscreen digitizer is dying. This is related to the hardkey malfunction. The only thing you can so now is flash back to stock WM Tom and send it back for repair. The phone's touchscreen need to be replaced.
Good luck,
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
Yeah thats what ive been reading, and right after i started this thread i was reading on another and read that you can fix it if you hold the power button down firmly (apparently the digitzier is right behind it)....that worked for me.
I think too much flashing and changing ROMS using the power button didnt help hehehe
AEBobby912 said:
Yeah thats what ive been reading, and right after i started this thread i was reading on another and read that you can fix it if you hold the power button down firmly (apparently the digitzier is right behind it)....that worked for me.
I think too much flashing and changing ROMS using the power button didnt help hehehe
Click to expand...
Click to collapse
Try using zMooth or Button Savior. This help your hardkey a lot. Since I have zMooth and Button Savior install on my phone, I no longer have to use the hardkey.
AEBobby912 said:
Yeah thats what ive been reading, and right after i started this thread i was reading on another and read that you can fix it if you hold the power button down firmly (apparently the digitzier is right behind it)....that worked for me.
I think too much flashing and changing ROMS using the power button didnt help hehehe
Click to expand...
Click to collapse
for how long (holding of power button) ????
{edit}
!!!!! FIND SOLUTION !!!!!
The digitiZer is under the hangup button. press the button bit hard till it nudges the digitiser a little. it worked for me.
(found it from : http://www.htcphones.net/htc-hd2-problems-with-touchscreen/ )
I'm so cool now!!
I have been living on this solution for almost 2 months now.
However I can't take it anymore not because I am lazy!
but because when sometimes you need to make a quick call or grab that
camera instantly I tend to waste a good 5 minutes trying to make that hardpress on the end key work with the digitizer cable.
My question is, would changing the digitizer work? or is it something else?
Ever noticed that T-Mobile HD2 has soldered digitizer connection to the LCD vs. flex-cable socket in standard Leo?