Hello, I have had this TYTN I for a long time without any major problems. It was originally with WM5 but then I upgraded to WM6. Lately I had a strange problem whereby the front buttons stop responding intermittently.
The below mentioned buttons stop working:
1. The Internet Explorer button.(Above on the right)
2. The Message button.(Above on the left)
3. The Call buttons. (The call picking and disconnecting button, below left and right) And the 4 keys along it.
During this time I have to resort to the pointer or the side wheel to use the phone, which is very frustrating.
If I press the reset button at the bottom, the keys work again for a few times, then stop to respond again.
I have tried to flash again with both WM5 and WM6 but did not help. I have opened the phone and reseated all connectors but did not help either. Do you think I should try replacing the ribbon cable?
I have searched the forum and found several threads with the same problem, but never a solution.
Your help is much appreciated. Thanks.
I have been struggling the last few months with the same exact problem. Sometimes the buttons work other times they don't, and in the last couple of weeks the frequency of button failure has increased (every couple of minutes).
I found a few users yesterday over on the HTC forum who were having the same problem and 1 user who actually reported a fix that worked for him.
Go to Start/Settings/System/Key Lock and select "Do Not Lock Buttons". Exit Key Lock and soft reset your device. You may know return to the Key Lock options and re-select your choice (I used "Lock all buttons except Power button").
Worked for the HTC user and is working for me as I have had no button failure now in the last 24-hours with repeated use of the device.
I hope this works for you because if you are like me I getting very close to trashing the unit.
Hi,
the problem could be the Xilinx chip (a BGA chip) on the pcb underneath the buttons.
As the buttons are pressed the board is flexed and some of the solder pads under the xilinx chip must have become detached from the xilinx chip itself.
I had the white screen problem. An while i got the white screen the front buttons where not working too.
In the whte screen threat i found that it could be the Xilinx chip, and figured out when pressing on this chip the white screen was gone and the buttons where working.
So i resoldered (refloated) the chip with a heatgun and some liquid flux last Sunday and since then i had no problems anymore.
I would suggest disassembling the phone down to the pcb and try starting it on with the ribboncables connected while keep some pressure on the Xilinx chip. And then trying the buttons if they work.
See
http://forum.xda-developers.com/showpost.php?p=2382665&postcount=134
in
http://forum.xda-developers.com/showthread.php?t=321163&page=14
Greets
jtf
I have the same problem with the same phone. The instructions above for "key lock" didn't fix it for me. I was assuming that it was hardware; but I just tried installing the Android port for this phone and under Android the buttons work fine.
I know that Android has some good stuff going for it, but I don't think it's awesome enough to circumvent a bad circuit... How exactly do these buttons work? Is there a process that should be running to handle them? Any other pointers?
hi there
i got a "small" problem with my touch hd. since im carrying the phone in my pocket, i installed "slide2unlock" to prevent the screen from unlocking itself in my pocket...
thing is - i got numerous complaints from people on my contact list, that i called them (sometimes multiple times in a row) without beeing on the phone... seemed to me that the screen unlocked (by accidently touching/pressing the botton on the top in my pocket) and the now unlocked phone started to do funny stuff like calling people...
problem is, that even with s2u installed AND active, my phone keeps calling people. one time, i held the phone in my hand, started the music player, locked the screen via the top button - and the next moment the screen lit up again (without me touching anything "touchable" like the side- oder top buttons - the screen was locked anyways) and my phone started to call a contact from my contact list.
there seems to be no real schema in what people are called. seems like the phone picks randomly one of my contacts on my list and calles him right away.
how do i stop this? im out of ideas here and this thing is really getting on my (and others) nerves...
According to your through description the problem might be even an exotic thing for WM - a virus. Try Kaspersky mobile
Have you installed any custom phone/dialer applications? Also any scripting applications like mortscript and a badly written script causing it... Also are you using AEButton plus. If so then may be a bug in one of those, still difficult to understand.
Otherwise looks like a real malware something not usually known in WM world
lefteyeclosed said:
hi there
i got a "small" problem with my touch hd. since im carrying the phone in my pocket, i installed "slide2unlock" to prevent the screen from unlocking itself in my pocket...
thing is - i got numerous complaints from people on my contact list, that i called them (sometimes multiple times in a row) without beeing on the phone... seemed to me that the screen unlocked (by accidently touching/pressing the botton on the top in my pocket) and the now unlocked phone started to do funny stuff like calling people...
problem is, that even with s2u installed AND active, my phone keeps calling people. one time, i held the phone in my hand, started the music player, locked the screen via the top button - and the next moment the screen lit up again (without me touching anything "touchable" like the side- oder top buttons - the screen was locked anyways) and my phone started to call a contact from my contact list.
there seems to be no real schema in what people are called. seems like the phone picks randomly one of my contacts on my list and calles him right away.
how do i stop this? im out of ideas here and this thing is really getting on my (and others) nerves...
Click to expand...
Click to collapse
it "might" be the stylus....
the default in s2u2 is to ulnlock on stylus removal if your stylus get caught in you pocket
and pulls far enough out it'll unlock
but anyway check the unock options out in the s2u2 settings
beter yet stick a reply in the s2u2 post and see if anyone else hase a silmilar problem
TC,
Or uninstall that screen-lock application and see if the problem still occurs. If it still occurs, you now know it's nothing to do with the App and perhaps indicates a bigger issue.
Cheers.
Stupid question, but are you locking your screen by pressing and holding the Hang Up key in the bottom right corner?
I find the only way to fully lock the screen to stop the kind of activation you are talking about is to press and hold Hang Up key to lock it.
Then pull out the stylus to unlock, or press the Answer Key followed by the then-displayed unlock key.
Hi,
I have exactly the same issue.
My version of s2u2 is 1.62.
I just changed the option in s2u2 to avoid the phone to turn on when removing the stilus...I will wait and see
Hi,
Even after I have changed the option in s2u2 to avoid the phone to turn on when removing the stilus it seams my phone is still makes some unwanted callings...
Any idea???
It first started with the blue light blinking, even with the phone turned off. The only way to stop it from blinking was to remove the battery for about 10 seconds.
Then, everything I typed staarted to ddoublle letteers raandomlyy.
Now, it's acting like the down button is stuck. I can't do anything on the phone because its always scrolling down, beating out any other input.
I can live with the first two, but the third one has made the phone completely unusable. It's never been around water, never dropped, just randomly doing this crap. Any ideas on how to fix it? Hard reset does not work, new rom does not work, its a hardware issue.
Yes it is probably a hardware issue. Time for a phone swap
I'm actually out of warranty, so the only thing I can do it either switch to a different phone or try fixing this one. Have nothing to lose by opening it up, just wanted to see if anyone else has fixed it by cutting any wires or connections on the inside of the phone.
You don't have insurance
drewcam888 said:
You don't have insurance
Click to expand...
Click to collapse
No phone insurance. Verizon completely screwed me on that phone purchase in more ways than one. By the time I figured that out it was to late.
TO bad I got mine added late. I just called the lady I bought the phone from and she added it.
Not sure about the blue-light.
I was able to fix my repeating-letters using the keyboard fix in this post:
For the constant-down input - it could either be the touchscreen digitizer or the hardware keyboard. YouTube has a series of videos on dismantling the Mogul - it may be worth some "exploratory surgery" to see what might be causing the problem (cookie crumbs, perhaps)...
Hope this helps. Good luck.
Htc mogul hardware button - issue
Dear XDA GURUS,
I am facing this very weird problem on my HTC MOGUL. All my Hardware button have stopped responding / Working. Please help me sort out this issue.
Waiting for your valued reply with solution.
Detail given on below link.
My HTC MOGUL HARDWARE Button Issue
Dear XDA GURUS,
yesterday i tried to do some RnD for this same problem. now the inputs. (Nothing technical)
* Even though my camera hardware button is not working, but, i can still enter the bootloader screen.
* Even though my both soft reset hardware button are not working, but, still i can do the hard reset.
This only means that, my buttons are working fine, but, according to my logic, they have lost there assignment.
After that i started searching web, if i can find a App / setting / hack / register setting, in which i can assign then there original key setting. So i found this on XDA forum as below.
Code:
[B]How to assign a shortcut to EndKey, SendKey, Power Button, PTT Button!![/B]
Hello
Since some of you guys asked about this , well there you go:
if you look inside the keyboard driver with a good disassembler (IDA Pro) you would see that you can create these link files :
Long_PTT.lnk (push to talk button+long press)
Long_End.lnk (the read key+long press)
Long_Send.lnk (the green key+long press)
Short_PTT.lnk (push to talk button)
Long_Power.lnk (Power button +long press)
Short_Power.lnk (Power button)
So basically all you need is to create these link files and put them in to windows folder. You can assign these keys to any shortcut you want .
Source: http://forum.xda-developers.com/showthread.php?t=356322
ok now, certain things are clear. now anybody out there can help get this thing sorted out.
Waiting for concrete solution.
Okay I wasnt going to post about this cause there have been way too many posts and alot of back and forth and debates and even flaming, but I stumbled across something that I think is the cause for MAJORITY of the issues with why we keep having this happen. It Happened to me Today, and I Found the cause.
Before ANYONE Flames me for bringing this up, READ the post, Remember I solved the cause of why it happens to most of us, I dont take responsibility if you choose to take it upon yourself to fix it! And I know 90% of the users are going to tell me I'm wrong or I dont know what I am talking about, so be it.
If you have nothing to add other then flaming the post, just hit the back button and be on your merry way and pretend you never saw it. But I am 98% sure I am right about why its happening!
So if your interested read on:
I actually for the first time had this, and I know this is going to get flamed but its not the Screen thats the problem. And I think (BIG IF) that the dreaded unresponsive screen issue that we keep reading about Majority of them I think is not the screen.
I have 2 HD2s and both have worked flawlessly without any problems, but today I was playing with my test phone that doesnt get used that much and I noticed after installing a new rom that my screen after I played with it for a bit went black (sleep) and when I woke it up it wouldnt respond, first thing that crossed my mind is I just lost my digitizier, and started wondering okay why, I went as far to re-flash WinMo stock HD2 rom, same issue, so I decided its time to find out exactly whats causing this, and I found it. I wasnt going to make a post again cause I figured people would be "Not another thread about this" but I know whats causing the screen issue, at least this is my suspicision and I have temporarily fixed mine.
The problem is HARDWARE, The Culprit: THE END KEY (Red Button)! The Answer to "How or Why": The "End" key is used to turn the phone on and off or to put it in sleep mode, it is the most used key out of all 5 keys, it is used probably 7x more then all the rest, Its used for just about everything, now how does this cause the unresponsive screen? Easy, the phone lock or sleep is associated with this key, Its the only way to make the screen go off other then waiting for the time out period. Because by habit we mostly hit the end key to turn the screen off the phone automatically associates this with locking the phone, once that happens the screen becomes unresponsive because of several reasons: 1) The contact under the actual key has dirt which causes the button to stick in the down position, 2) the contact is bent which the "end" key is pressing down on the contact which is making contact with the board and causing it to be unresponsive, 3) The contact is worn. This is the reason why if you press the end key a few times (anywhere between 2-10) and then try the screen responds, this is cause your "unsticking" the key which then lets the screen respond.
Most of us when we hit the end key press to the far right to avoid hitting the back key (The button with the left arrow) which causes the end button to lean toward the right. But you can wake the phone up with the other 4 keys to the lock screen which will allow you to unlock the phone. As a temporary fix for myself, on my test phone I now make sure to press on the left side of the key to prevent this from happening, since its a test phone I'm not worried, but the real solution is to take the phone apart and clean the underside of the end button, and the actual contact with alcohol to remove the build up of dirt and whatever else. And also if the contact frame is bent to GENTLY bend the right side back up alittle to stop it from happening, or sending it to htc and letting them fix it.
We have to RE-TRAIN ourselves to start using the other keys to wake the phone up and not rely on the end key so much.
Hope this helps anyone finally why we have this problem. And if it works for you then hit the Thanks button
I completely agree with you. I've had the "dead digitizer" since December. It was pretty apparent it was a hardware key problem, as I could generally solve the issue by pressing the "Off" button to turn the screen off, and then one of the other keys (usually the back button, but occasionally one of the others) to wake the screen up, and the digitizer would be alive again.
As I am still under warranty, I sent mine off last week, and expect to hear back within a few days. But if I had the confidence to open it myself, I was sure it would be fixed with a good clean.
Anyway, thanks for crystallizing all this into a post. Thanked!
THANK YOU SO MUCH FOR THE INFO. i have had so much trouble with unresponsive screen after installing typhoon 2.6.3 and it from holding down the red button all the time for install and the past millions times for everything else.
Thanks for the heads up
Sent from my HD2 using XDA App
U maybe be right about why this issue happens but if u rely on other key then will also wear out soon ...
What I did is I remapped my volume up n down keys to power and back button which I believe are the most used in android and then found a app to manage my volume in android that way I don't lose my sound on rhw phone
Also I went ahead and got a another app which places virtual buttons on ur screen so u can use then instead of the actual hardware buttons
For button remapping
get the BUTTONREMAPPER for android and for on screen android buttons get BUTTON SAVIOR
hope this helps
Sent from my HTC HD2 using XDA App
Good to know... will now wake my phone up with the green key as its hardly used in Android. Button Savior is a great app, been using it a while now. Took a bit to retrain myself to not use the back key.
Sent from my HD2 using XDA App
i'm going to agree with your hypothesis or at least suspect that dirt is probably a bigger factor than most people think in these cases. i just bought a non-responsive phone today and while i stuck my nail (yes, i should probably clip them) around the edge, in between the screen and housing, i was surprised to see just how much dirt was in between that crack. same with the area around the buttons; there's a lot of grime there.
since i just got the phone i haven't even opened it up but the first thing i'm planning to do is give it a good interior clean around the buttons for sure as that seems to be the sensitive spot. touch screen devices are very delicate and the micro particles of dirt which build up over time probably create a hazard that people really don't really anticipate. compound that with having to mash on those buttons all the time probably crams the debris in there even tighter.
i'll attempt to clean and check the contact as you suggested and will report back if it helped in my case.
About hardware keys:
I don't use them at all, only for wake up the phone (it can be wake up with any key)
There is an app in market called "button saviour" it's just excellent app to keep your hardware keys for a long time
AngelDeath said:
The problem is HARDWARE, The Culprit: THE END KEY (Red Button)! The Answer to "How or Why": The "End" key is used to turn the phone on and off or to put it in sleep mode, it is the most used key out of all 5 keys, it is used probably 7x more then all the rest, Its used for just about everything, now how does this cause the unresponsive screen? Easy, the phone lock or sleep is associated with this key, Its the only way to make the screen go off other then waiting for the time out period. Because by habit we mostly hit the end key to turn the screen off the phone automatically associates this with locking the phone, once that happens the screen becomes unresponsive because of several reasons: 1) The contact under the actual key has dirt which causes the button to stick in the down position, 2) the contact is bent which the "end" key is pressing down on the contact which is making contact with the board and causing it to be unresponsive, 3) The contact is worn. This is the reason why if you press the end key a few times (anywhere between 2-10) and then try the screen responds, this is cause your "unsticking" the key which then lets the screen respond.
Most of us when we hit the end key press to the far right to avoid hitting the back key (The button with the left arrow) which causes the end button to lean toward the right. But you can wake the phone up with the other 4 keys to the lock screen which will allow you to unlock the phone. As a temporary fix for myself, on my test phone I now make sure to press on the left side of the key to prevent this from happening, since its a test phone I'm not worried, but the real solution is to take the phone apart and clean the underside of the end button, and the actual contact with alcohol to remove the build up of dirt and whatever else. And also if the contact frame is bent to GENTLY bend the right side back up alittle to stop it from happening, or sending it to htc and letting them fix it.
We have to RE-TRAIN ourselves to start using the other keys to wake the phone up and not rely on the end key so much.
Hope this helps anyone finally why we have this problem. And if it works for you then hit the Thanks button
Click to expand...
Click to collapse
You just hit d nail on d head pal...My HD2's touchscreen also stopped responding and nothing i did (software-wise) worked...i flashed several WinMo ROMs and Android builds with no luck, till i read somewhere online dat some guy seemed 2 solve his touchscreen issues by installing "CleanRam", ran a level 3 clean up (use MyMobiler for this) and by pressing real hard on the red end key button..I did just dat and voila it works!!
I have a Tmobile HD2 which is no longer covered under warranty and i'm not willing 2 part with almost $200 here 2 have d whole lcd & digitizer replaced...I recollected dat in d forum i read the suggestion from, a lot of ppl came n posed their views on why it's not possible but i tell u it is cuz it worked for me..Nw i'm comfortably dual-booting WinMo & Android via sd. i use "button savior" and "extended control" to navigate and power down/reboot respectively.
Hweva i believe its not a permanent fix as it simply refuses 2 allow me run android full-time thru MAGLDR, & i think i know y..pressing down on d end button 2 launch MAGLDR/CWR options after install messes up d connection with d digitizer underneath and d touch screen thereby causing it 2 fail again when android boots up....I just might try opening it up myself n cleaning dat area up as u suggest but dat'll be when my current fix fails cuz as d saying goes "If it aint broken? then don't fix it"
Just installed Button Remapper, and not to sound like an idiot, but can someone tell me which one I would have to remap to make the volume up key or down key to put the phone to sleep and wake it up, and would that still be able to use the volume key to turn up and down the volume as well?
AngelDeath said:
Just installed Button Remapper, and not to sound like an idiot, but can someone tell me which one I would have to remap to make the volume up key or down key to put the phone to sleep and wake it up, and would that still be able to use the volume key to turn up and down the volume as well?
Click to expand...
Click to collapse
Hmm...i don't use d app but from wat i can gather on d dev's thread, you would have 2 remap ur volume keys to "Power"...Also checkout dis review 2 learn hw 2 mk d remapped button work even in sleep-mode.
I can agree but mine's been in twice on repairs with the same error but screen was replaced both times amongst the digitizer, backcover (Can't understand why) and 3 other things were replaced. Buttons weren't replaced.
CaCtuZ123 said:
I can agree but mine's been in twice on repairs with the same error but screen was replaced both times amongst the digitizer, backcover (Can't understand why) and 3 other things were replaced. Buttons weren't replaced.
Click to expand...
Click to collapse
If I'm to base how the HD2 is setup internally, they wouldnt replace the buttons, they would replace the contact or contact board under the buttons, remember the buttons are like a keyboard, they dont wear out, its what they push on that gets dirty or worn.
I was traveling and this happen t me and became desperate.
Following the instructions I come to the clear conclusion that our HD2 has this hardware problem.
If I do not use the end call button no issues with the screen, really, no issues.
Hope my feedback will be helpfull as well. Great job done here!
pauloviegas said:
I was traveling and this happen t me and became desperate.
Following the instructions I come to the clear conclusion that our HD2 has this hardware problem.
If I do not use the end call button no issues with the screen, really, no issues.
Hope my feedback will be helpfull as well. Great job done here!
Click to expand...
Click to collapse
Yeah HTC screwed up on dat...its just as said,1 has 2 be careful n avoid using d red end key button as much as possible 2 enable d device last much longer...And if u do ave 2 use it, press on d left-most part of d key (closer 2 d back arrow button) to get d job done.
I just had this issue happen to me and thought it was my build... But I found another way, I use Cyanogen Mod 7, and in the drag down menu (from the top) I added a sleep option, because thats the only thing I use it for... and I never have a reason to press the end button now.
This is the best thing I have found to fix it without having to remap the buttons
I guess I'm lucky because I have never had a problem with the responsiveness of the touchscreen and/or end button. I got my HD2 a month before TMO release date and trust me it has been thru alot (scratches all over, even a piece of glass missing next to the call button). So my question is how much pressure and wear 'n' tear are you all putting on your end button or phone for that matter?
big3d said:
I just had this issue happen to me and thought it was my build... But I found another way, I use Cyanogen Mod 7, and in the drag down menu (from the top) I added a sleep option, because thats the only thing I use it for... and I never have a reason to press the end button now.
This is the best thing I have found to fix it without having to remap the buttons
Click to expand...
Click to collapse
Can that be done with other roms? And wouldnt a shortcut or a widget on the main screen also work?
on1ydabest said:
I guess I'm lucky because I have never had a problem with the responsiveness of the touchscreen and/or end button. I got my HD2 a month before TMO release date and trust me it has been thru alot (scratches all over, even a piece of glass missing next to the call button). So my question is how much pressure and wear 'n' tear are you all putting on your end button or phone for that matter?
Click to expand...
Click to collapse
It all depends really Understand that not all HD2's go thru the same testing process when it comes out of the manufacturer. Also take into consideration that it also depends on how often you flash a rom, if your flashing a rom every day or every week expect that you will shorten the life of the end button, also it doesnt always mean that the button is bad, it could clearly be dirt underneath that could also be causing the issue. And I said the same thing when I saw posts about people saying that android killed their screen. I even responded to it but always maintained it was hardware, even though I didn have the problem, and I bought both my HD2's used in Dec. and the day it happened and I found out why I posted this, if I was to guess, I would say that I probably flashed both my HD2's close to 200 times with different roms, or upgrades, or testing fixes out.
So if your not a flash nut, then your probably safe. There are many factors that can play a role in the end button life cycle, And no two people use their HD2's the exact same way.
the non-responsive touchscreen problem happened to me this morning. I woke up trying to unlock my phone only to find that it would not respond to any touch gestures. I was however able to uninstall HSPL and Flash the stock WM6.5 rom since I was going to T-Mobile to get a replacement. When I took it to T-Mobile the employee resetted the phone by holding the 2 volume buttons and the power button then somehow the touchscreen started to respond to touch again. I was completely puzzled as I thought it was for sure a hardware problem. But now I'm going to flash Android and hopefully the problem will not arise again, if it does, back to T-Mobile I'll go!
What Android really needs is some sort of "X" button, or even a widget on the main screen that you can just tap and put it to sleep. The three most keys used in my opinion is the windows key (Apps that use it for a menu), the back key (Since there is no damn close button), and the end key (sleep, flashing, booting to magdlr).
Some one had a concept here of buttons that looked very similar to The desire HD, the greatest thing would be if someone could make the bottom of the htc sense (app drawer, phone, and the personalize) auto hide and have the desire HD buttons come up with a power button at the end and this way if you hit menu it would bring up the original 3 button screen.