Related
Just got a s/h exec and I think it is faulty. Whats happens is it starts up ok and works for a while and then for no reason that I can think of it goes into a loop which stops it from working.
When I say a loop I'm not sure thats the right terminology but imagine if you tapped the start button and the start menu opens... and then imagine you tapped the tab button , the next item would highlight. If you tapped the tab button again the next item would highlight and so on. Well its as if the tab button is being hit over and over because all the items in the start menu will be highlighted one after the other over and over again.... it just goes round and round in a loop.
Its possible to escape from this and go to another screen but the same looping will go on in that screen too.
If you switch off and leave for a while and come back to it it works ok for a short time and thens starts the carry on again.
Sometimes if you just wait a while it stops, but will start doing it again even if you dont touch anything.
I've noticed one way to force it to stop is to slide the volume button... this seems to stop the loop and allows normal function for a while.... then the crazy looping starts again.
Has anyone seen this or know anything about it.
Nope sorry, maybe you can have it replaced where you bought it as from your post, you can recreate the problem easily.
Side Note : Have you tried Hard Resetting? Or installing another ROM?
I have tried hard resets and factory reset... problem remains.
Will try new ROM.... just trying to figure out how to do it !
weegee said:
I have tried hard resets and factory reset... problem remains.
Will try new ROM.... just trying to figure out how to do it !
Click to expand...
Click to collapse
Just download a new ROM form imate or something, unpack all the files in the ROM update to a directory, put the attached file in same directory.
Enter bootloader mode (Backlight + Power + Reset Hole) you will see SERAIL on the screen but not backlight so look hard.
Plug into PC, the SERIAL will change to USB
Run the attached file. You will see a photo of an S100 but continue anyway....
Hard reset when finished... DOne
ok have installed latest rom... but exec still doing loop loop
Just for arguments sake, can you try installing Imate's newest ROM?
yea thats the one i have just put on.
It seems to be doing the problem less than before. I notice that it does stop if i press the backlight key or move the sound slider.
I'm wondering if there is dust or dirt got in behind the buttons or something like that... although I would have thought other people would have come across this b4 if that was the problem. The machine is one of the first to come out, although I just got it a couple of days ago.
weegee said:
yea thats the one i have just put on.
It seems to be doing the problem less than before. I notice that it does stop if i press the backlight key or move the sound slider.
I'm wondering if there is dust or dirt got in behind the buttons or something like that... although I would have thought other people would have come across this b4 if that was the problem. The machine is one of the first to come out, although I just got it a couple of days ago.
Click to expand...
Click to collapse
If you have tried different ROM flavors and still get the same problem, then it is definitely hardware related. Send your unit in and demand for a new one not a repair
Just been playing around with it again and notice that I can make the problem happen if i press any of the keys on the navigation pad except the top one.... and i can stop the loop by pressing the light button.
Weird or what.
My initial thought on this is maybe its got wet at some point
I have opened the xda up and stripped it down to all its parts. No sign of any dampness or dust dirt etc. Dont see anything missing or broken.
Put back together, but still doing this.
Driving me nuts.... its a great machine but is very tiresom to use with this going on.
Another think I notice about this machine, I have never used it as a phone, but I tried putting a sim card in and There is no sound through the earpiece. Only sound comes from the speakers when you set it to speaker phone.
I suggest just return it and have it replaced. It's probably a faulty button. Probably gets stuck whenever you press it.
Doesnt need a button to be pressed for it to start.. just starts by itself... and can stop by itself too.
Sometimes it can for ages without doing it, other times it does it all the time.
Cant figure if its hardware or software problem
GHOST-IN-THE-MACHINE
Yea... maybe I should get a priest !
I had this problem when i first got mine, if you move the sound slider down, then up, it seems to stop doing it for a while, and it hasn't happened in the last couple of weeks atall, maybe its because its new, and just needs to settle in?
Jay
Well at least I'm not the only one to have it.
My sound slider does stop it happening but only for a while and then it starts up again.
The machine is perfect in every other way, its just an annoyance I could do without.
I've tried everything, even stripped it down and left parts out, like buttons, to see if they are the source, but no difference.
I have the same problem!!!!!!!!!
Someone help please!!!!!!!!!!!!!!!!!!!!!!!
I have same problem. I send to service but until today they can't repair that problem.
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
this is a new problem for me. I have been using the most recent Dutty ROM together with Mdeejay Android ROM without any problems. All of a sudden, when I try to unlock the screen after STANDBY, it just wont register my touch, as if I am not touching it. It boots up fine, and on the first unlock works fine, but when the screen lock goes on again (after every standby) it just wont unlock. So I am stuck (I use Exchange and our policy forces the lock after standby, so I have to use it - and its worked fine for ages).
If I boot into Android, it works fine, the unlock works fine, yet strangely when I try to shut the power down, THAT screen also doesnt register me touching it.
I have hard reset but even before I load an app or do anything, the problem exists.
I also reflashed a DUTTY ROM. Same problem.
I tried CHT lockscreen - same issue. After Standby, screen doesnt register my touch.
Anyone have any ideas?
Same problem for me.. Restoring a backup image after being forced to hard reset this morning and now suddenly my HD2 won't wake up after sleeping. Pressing my end key only lights up my buttons but I have to pull the battery to reset. I'm thinking it's related to me having CHT installed, yours however might be a different problem.
I had something similar. It was right after I had installed CHT 2.0 and was looking to make the top and bottom bars transparent. I found a cab that claimed it would do this and installed it. Sorry, I don't recall what cab it was and I have deleted it. When I rebooted Sense would hang and if it got into a lock it would only move the slider a little where it would stop. Luckily, I had done a backup that morning right after I installed CHT 2.0 with Sprite so I restored and all was well.
I don't know if this is of help but I figured I'd throw it out there.
it wakes up, but wont register when I try to swype the unlock screen.
ekerbuddyeker said:
it wakes up, but wont register when I try to swype the unlock screen.
Click to expand...
Click to collapse
Your lucky you get that far lol.. I don't get any waking up. Plus I now uninstalled S2U2 and still no change. Disabled all locks of any kind and still frozen with sleep of death with in 1 min of hitting power to sleep it. I REALLY don't want to to a hard reset and install everything from scatch.. UGH.
weird update...
It has something to do with which key i witch the device on with. If I use the phone key, I can swype the unlock. If I use the power key, it doesnt register.
Another related issue: when i hold the power key to switch off, it wont register me touching power off or reboot etc. so I have to take the battery out to switch off. Its the same in Android.
Anyone know? Hardware issue?
ekerbuddyeker said:
weird update...
It has something to do with which key i witch the device on with. If I use the phone key, I can swype the unlock. If I use the power key, it doesnt register.
Another related issue: when i hold the power key to switch off, it wont register me touching power off or reboot etc. so I have to take the battery out to switch off. Its the same in Android.
Anyone know? Hardware issue?
Click to expand...
Click to collapse
bump this is horrid
same
im having the exact same issue. I have flashed 3 different roms and flashed to the newest radio (2.15).
I started out using energy rom, didnt help. Flashed a newer energy rom, didnt help. Now im using the dusk rom, same issue.
SOMEONE PLEASE HELP!!!!
It's a quite common digitizer problem lately... it seems the HD2's digitizer is failing on some units, possibly because of usage with android? my father's device acted the same way, only it sometimes did register touch and other times, not.
My device doesn't have these problems, yet. But seeing that a lot of people here are experiencing these issues, and with the notion that I use android pretty much all the time since I first booted my device, i'm pretty sure i'll experience it soon as well..
Make no confusion thou, the assumption that android effects the digitizer are purely my own thoughts on this matter, no such thing has been proven and the conclusion that android is effecting our HD2s is based purely on the statistics of touch screen failures in the last few months since android has been made publicly available in a working form.
EDIT:
Those seeking A solution, as far as I know, the only solution is sending your unit to HTC for repairs, you'll get it back with a note that says that they replaced your digitizer or your screen, at least these are the reports I heard from the other folks whom followed this procedure.
Good luck.
HTC HD2 Screen Lock
I have only used Android a few times on this 'phone and it has a standard HTC/O2 ROM installed so it must just be a problem with the top part of the digitiser. With android running the unlock is at the bottom and is unaffected.
Is there any way of testing the digitiser before deciding whether to get a repair sorted,
Ta,
link:
htcphones.net/htc-hd2-problems-with-touchscreen
short version :
change digitizer
ekerbuddyeker said:
weird update...
It has something to do with which key i witch the device on with. If I use the phone key, I can swype the unlock. If I use the power key, it doesnt register.
Another related issue: when i hold the power key to switch off, it wont register me touching power off or reboot etc. so I have to take the battery out to switch off. Its the same in Android.
Anyone know? Hardware issue?
Click to expand...
Click to collapse
A friend was complaining to me about something like this since last week. I could not figure it out so I went ahead and installed Android cm7 and still have the same issue.
Until I read this post after searching through the forums all over Screen now unlocks perfectly fine but only using the green Phone icon. If I try to wake the screen with the red Power button, the screen is unresponsive.
Thanks for the info.
Already happened tome its a hardware issue can't be fixed so if you still have warranty on ur phone send it to htc for repairs b because it tends to get worse n worse soon other keys will start to give in I think that's one reason why most android phone been switching to capacitive buttons because hardware causes this sorta issues and send it in for repairs to get it fixed
Sent from my SGH-T959 using XDA App
the same issue with me , is there is any solution for that .
Wakeup the phone using the send button.it will work
Hey my lovely XDA-ers, I'm really hoping for some magic here...
Yesterday my HD2 digitizer just stopped working... the Touchscreen will not respond to any inputs. It was bitterly cold outside so I was half hoping that an overnight stay in a warm room would help, but no avail...
The thing is, on one in every 5 restarts, I get a small amount of life from it. One one in 15 restarts, I get full use. So there's still life in there.
I could understand if it broke because I dropped the phone/squashed it, but at the time I was just playing Robo Defence, completely normal use, when all of a sudden it stopped responding.
I've uploaded a video, which shows how, occasionally, the bottom fifth of the screen works. However, as shown, when I'm using the top half of the screen, the digitizer appears to be receiving input from the bottom of the screen, as though I'm trying to perform a multi-touch action. For this reason I'm hoping there still be some way to rescue the phone without an expensive repair job. I bought it in March from XDA Marketplace, and it's served me faithfully since, but because of that I do not think I have the manufacturer's guarentee, or insurance
I've hard-reset, I've reflashed my ROM, I've tried in both WM and Android (my usual OS at the moment), I've reflashed over WM ROMs, and the problem stays the same... (also read all related threads!)
Sorry for inverted nature of vid!
So does anyone have any suggestions to try? Otherwise I might go through a £130 repair service on htcrepairs.co.uk - they do not show up on a forum search so I was wondering if anyone had used their service before?
Thanks all, appreciate any ideas.
Edd
Very odd indeed. I don't have a solution for your problem, but a suggestion. It is a long shot, but might help.
Whenever i had similar problems with my Wizard (i know, kind of old but one of the best older devices every made by HTC), i opened it and cleaned it from the inside and checked all the connections of keyboard, touchscreen, etc. to the mainboard. Sometimes it helped...
In the end, if you buy the replacement kit, you anyway have to open the HD2, so why not try this in prior to buying the kit...
A lot of people seem to have this problem. There's a lot of information on it here. Do a search. But the short answer is its a hardware problem. If your phone is still under warranty send it back. I think HTC will fix it for free if It's less than a year old. But try your carrier first.
Sent from my HTC HD2 using XDA App
BAD NEWS...
i had EXACTLY this happen to me. eventually it totally stopped responding. Only option is to replace the digitizer.
GOOD NEWS..
After a month of searching, I found a really good guy to do it. www.iexpertstudio.com . The owner is VINCE. you can email him on his site. He charged $110 including mailing it back to me. He replaced the LCD and digitizer and sent it back. All works perfectly now.
I see you are in the UK so dont know if it makes sense to send it to the US. Alternative is to go on ebay and buy the screen/digitizer and replace it yourself.
(BTW normally i would have chucked the device, but even after 1 year I still dont think there is as versatile a device as the HD2. Had the DHD been 3G useable in the US I would have bought one.)
Thanks for the feedback guys, I've been doing some investigation my end (and you're right, there are similar threads on here, but none which had a "half-screen working" problem.)
I've narrowed the culprit down to my "Back" button. It's somehow exerting pressure on the screen, leading to either a non-responsive digitizer or an input at the bottom of the screen.
I might add this to an entry in the "ANDROID KILLS YOUR BUTTONS" thread
My choice is to live manually with it, or get the company mentioned in the first post to give it a good clean, but whether it's worth £80 just yet is a question for me.
Anyway, thanks for your input, guess this thread will close, but to any readers in future, if your screen seems to die, see if it's pressure on the screen caused by the buttons!
I can totally support your reasoning.
I haven't had any problems whatsoever with the touchscreen in almost a year of honoured career of this phone, while this morning I was trying to unlock it with no success (nothing special happened, I even used it 10 minutes this morning already). At first I thought it was the usual "sleepy" behaviour of the screen right after waking up, butafter sliding down the hdmini style unlocker at least 10 times with no effect I really started freaking out :O
I have longpress endkey set on instant reboot, and after that it seemed working... just not for too long.
To cut to the chase, what in my opinion supports your idea of hardware buttons interfering is:
sometimes, as I have LMT installed, with the tap&hold option enabled, swiping with just one finger triggered double swype instead (as if the screen detected a second, firm press on the screen elsewhere even if I sure as heck was swyping with one finger)
using mymobiler didn't work as well; if it was a hardware touchscreen problem, mymobiler should work, as it simulates touches, so it will just do its job even if the touchscreen is totally dead... while, IF the hardware touchscreen detected a firm press somewhere, mymobiler wasn't able to actively simulate another press
repeatedly pressing on the end key (which seems to be the culprit in my case) apparently solves the problem, as I can use the touchscreen again; also, a prolonged cycle of hibernating with end key, waking with end key, swyping down the hdmini lock (repeat at libitum) seemed to work, as if I dislodged something by activating the button so often
What I don't understand anyway is: HOW can a button pressing on the digitizer be exerting a touch action? If this was a resistive screen, I'd understand, but it's capacitive, and not even capacitive pens are so good as fingers in activating the touch. The buttons are just plastic with a metal contact underneath, and this metal contact shoudl by no means be anywhere near the digitizer.
Bah.
I know I have 2 years warranty on this device, but being far from my phone during the warranty processing gives me the creeps, so I'll just go on using it and pray this to be the defaillance of one sunday morning not to be seen again... after several soft resets (and fantasizing about a new rom flash, which I need anyway for other reasons) the problem seems to have settled by delicately bashing on the end key. The unlock slider is responsive after every wake up now... FOR now.
Praying...
My screen also died. So the only thing I have to do is press on the end key for a couple of times to make it work again?
lol, that's ONE possibility.
Just saying, in my case it worked, and still does since it happened once more this evening, so it's definitely got something to do with the hardware keys messing around (and hopefully dislodging themself for good, or I'll have to send it back for servicing), anyway in your case it could also be a dead digitizer, so no go
let's put all this about touch screen in 1 sticky thread pls.
I've been living for the problem for about three weeks now. It's never got worse, but never got better. It's a livable situation so for the moment I'll deal with it. I might check with HT about warranty, but it's not yet bothersom enough to make me want to flash back to stock, send it off etc. etc.
smeddy said:
I've been living for the problem for about three weeks now. It's never got worse, but never got better. It's a livable situation so for the moment I'll deal with it. I might check with HT about warranty, but it's not yet bothersom enough to make me want to flash back to stock, send it off etc. etc.
Click to expand...
Click to collapse
ditto.
Actually, I don't like having paid good money for a defective phone, but being without HD2 for up to a couple of weeks to one month (maybe? have no idea how fast HTC servicing is) is troublesome. I may buy for a deal a blue angel as a spare, yet, no GPS...
The most problematic event is if you get the "stuck" screen during a call.
In my case, it's the end key that messes it up; if the screen's dead, pressing twice the end key, firmly enough (once for screen off, then again for screen back on) wakes up the screen, and apparently, during a ringing incoming call, you can press the hardware end key without rejecting it, so it's a viable option (not taking into consideration the fact that trying to wake up the screen takes time, and the caller may give up after a while if you're not fast enough).
But if for any reason the screen gets stuck while the call is connected, I am stuck too, as to wake it up I should press the end key thus hanging on the other party.
Sad story.
EDIT: forget what I wrote, pressing end key while phone is ringing WILL reject the call. I tried it before during a real incoming call and apparently it didn't do it, but now it just did.
I also have a HD with a dead screen....
Only thing here is I have sent it back twice already to TelSuck here in Australia only to have it returned after the tech has wiped it over and reflashed it for me... What helpful little imps they are!
Code:
http://www.youtube.com/v/T6ssqmpRIB0
Its drivin me nuts sending it away for 3 weeks at a time to have someone with just enough grey matter to be able to wield a screwdriver tell me nothing is wrong.
Happy to try any suggestions!
@insinr8
this thread is just for half-dead screens where the screen sometimes actually works. Unless you can resurrect it by firmly pressing on the hardware keys, but if it's dead on a regular basis, then it's not our same problem I'm afraid :-(
@OP
while having an "attack", did you try plugging out the microsd to see if it magically solved the problem?
I mean, if it did, it would still be a hardware problem related to the microsd slot, since there is no point for a faulty microsd to mess up the touchscreen, and let it work from time to time
ephestione said:
@insinr8
this thread is just for half-dead screens where the screen sometimes actually works. Unless you can resurrect it by firmly pressing on the hardware keys, but if it's dead on a regular basis, then it's not our same problem I'm afraid :-(
@OP
while having an "attack", did you try plugging out the microsd to see if it magically solved the problem?
I mean, if it did, it would still be a hardware problem related to the microsd slot, since there is no point for a faulty microsd to mess up the touchscreen, and let it work from time to time
Click to expand...
Click to collapse
I will try that - it seems to happen more frequently when plugged in and charging, and now more buttons seem to be the cause/fix (e.g. now the home-button, or when I am on home-screens the phone will swipe "left", whereas before it would swipe "right". I'll keep playing.
I may check out HTC as I reckon my warranty, if I have one, will run out soon... Will still wait til after Xmas as I need my toy for the boring bits of Xmas!
I'm having same trouble now whit my phone except problems started mouth ago. After some period I again power up my phone and suddenly everything worked perfectly. Unfortunately this last only for two days and then exactly same problems happened, partially function screen.
As far as I know only good solution is replacing digitizer... I already ordered one for me.
exactly the same problem for me.. I sent it back with warranty yesterday
smeddy said:
I may check out HTC as I reckon my warranty, if I have one, will run out soon... Will still wait til after Xmas as I need my toy for the boring bits of Xmas!
Click to expand...
Click to collapse
Ditto.
Actually, my warranty lasts two years, which means until 2012, anyway I cannot stand risking to lose calls because the screen dies on me in the wrong moment, and the only way to wake it up is pressing the endkey (which by the way is the only "cure", and apparently never the cause).
I will be uploading a video on youtube regarding this, also to show it to the guys at the HTC support who will be asking me to hard reset and reflash until annoyed to death (as if that will solve anything)
Bump
This is the video that I just uploaded to youtube:
http://www.youtube.com/watch?v=C3-PNYwpYeI
EDIT: One day after, the problem has become way more frequent, 1 out of three times I wake up the phone, diugitizer is dead and I need the " on the end key to make it work
Uploaded another video on youtube with problem showing on vanilla lockscreen so HTC support doesn't try and tell me it's CHT lockscreen's fault
Last bump.
Screen has ben promoted from "hardware key problem" to "permanent death".
Now I can use the phone with mymobiler, but I can't anymore with touch, I seem to not be able even to wake it up even by pressing on end key
Re-flashing last official rom upgrade now to see if anything changes... yeah,sure
Ouch - good luck, hope mine doesn't go that way...
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.