Related
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 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.
I have the WP7 installed. No dual boot.
I have a password protected lock screen, and every once in awhile, the touch screen wont work, so I can't slide up and put in the password. If I hit the windows button in the middle, it kinda bounces for a second, then goes dark again.
It happened yesterday too, and the only way I fixed it was to turn it off, take out the battery and then turn it back on again.
When the touch screen works, it works fine. It's perplexing.
Anyone else have this problem?
Yes, but I only have to tap on the screen and the touch screen is working again and I can slide up the screen. Had this happen with both of the builds I've used so far.
This didn't work for me. My phone's been locked all night.
Hmm, not really sure what it could be. Check with whoever built the rom you are using, they may have a better solution. Sorry I couldn't help more.
Its a hardware problem, not software, i had the same problem the solution is to change touch screen, try to press touch near red button for same time it can help, but not for long time.
Sorry for me english)
Common problem. Your touch screen is fried (or is in the processing of frying). Start the warranty process now.
fried? dunno mate, when my touch screen goes on the blink i sweep a finger in the opersite direction to what i usually do then try again straight after, so forinstance, at the lock screen i try up and it doesnt work, so i try down then up and that usually fixes it, same for the tile screen, if it wont work as i sweepleft, i sweep right then left.
this doesnt happn on android which i would think rules out an overall hardware fault, at least for me anyway, it is however hardware related, the HD2 shouldnt have WP7, the drivers are not designed for our device so expect these odd happenings.
Of course its equally likely that this could be another sign of the pain in the arse SD card issues some of us suffer, reflash and try a new SD card and see what happens.
Man its realy problem of touch screen because it breaks in zone of red button, and when you press it some times it goes ok, and works wery well, but it die from now, replace the touch or it will die in few - weeks- days.
i would seriously get that accusation backed up by some proof before someone does something they didnt need to do.
I have random unresponsive screen issues that are directly related to the install of WP7 it does not happen on android or WM, there for its not hardware, at least in my case, its driver
I have the HTC HD2 Leo 1024 version, and I've encountered this strange problem with my phone recently. Whenever the phone is locked via the red button, and you try to unlock it with the same red button, the screen is almost non responsive. Sometimes it will work, sometimes it won't. To be more descriptive, what I mean by non responsive is.. if you try to wake the phone with the power button, the screen won't recognize any of your swipes. so you re-lock it.. wake it again with a different button, and it suddenly recognizes movement again.. just not with the power button, which is really annoying (especially on WP7 because you can only unlock with one button)
I was on CMYLXGO's Android NAND build when it first started happening. I figured, oh just a corrupt file somewhere, must need to reflash.
So I task29'd, Magldr 113, to WP7 (because I missed it ..) and I'm still encountering the same problem.
Was just wondering if anyone else has encountered this or has any solution for it.
On the android build you can bring up the lock screen with all 5 of the buttons on the bottom, the screen would be responsive with all of the buttons EXCEPT for the red power button.
On the WP7, the only button to unlock the phone is with the red power button, so it's a bit more annoying this time around considering I have to press it multiple times before the screen is responsive. I can't remember when this started happening, if I had to guess, I would say it started with a phone locking up so I had to remove the battery instead of doing a safe reset. Also I recently just got a DATA plan so that might have something to do with it (although I doubt it).
IF anyone has any idea what's going on please help , Much appreciated.
Search! I remember at least 4-5 different threads about the exact same problem u r describing.
You've done a great job at isolating any software side issues, but all the other threads conclude it is a hardware issue (red button is used more, wears out faster, causes it to mess with the touch digitizer circuitry that is located close to the "strip" under the buttons bar).
Sent from my HTC HD2 using XDA App
Ah I'm sorry man, I tried searching but I guess my search skills are still noobish haha.
Well I really appreciate it, I guess I'll start looking for some fixes now !!