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.
Related
Recently the end key button on my Titan has become a button that I need to press with a good amount of force on the very left or right side of it to have it work. I have ruled out a ROM problem (was using a prior DCD rom, now using 3.2.6) and I have never dropped my phone or had any extreme pressure/vibrations.
Has anyone else has this happen? The button still sounds like it clicks like all of the other buttons. Are there instructions out there for taking apart the Titan, or at least the front of it?
suprax said:
Recently the end key button on my Titan has become a button that I need to press with a good amount of force on the very left or right side of it to have it work. I have ruled out a ROM problem (was using a prior DCD rom, now using 3.2.6) and I have never dropped my phone or had any extreme pressure/vibrations.
Has anyone else has this happen? The button still sounds like it clicks like all of the other buttons. Are there instructions out there for taking apart the Titan, or at least the front of it?
Click to expand...
Click to collapse
how do you carry your phone? My VZW case would press my down arrow in and that caused alot of issues with the arrow. might be your case just wearing it out. remember, you dont have to drop it to wear out the metal contact underneath the button.
blksprk said:
how do you carry your phone? My VZW case would press my down arrow in and that caused alot of issues with the arrow. might be your case just wearing it out. remember, you dont have to drop it to wear out the metal contact underneath the button.
Click to expand...
Click to collapse
I carry is in my right side pocket in my pants, without anything else in there (keys, etc). I've had it since January of this year and babied it pretty well so I'm just surprised that with normal usage the button would become that hard to press.
I guess my options are taking it apart to look or bringing it to Verizon.
i posted a similar thread about the End key not to long ago... I had to press it extra hard to get it to register, then it just finally stopped working... i then had to use the touch screen end button... I got tired of it, so i took it back to sprint and they replaced my Mogul for free (as of 10/27/08). i also had issue with my keyboard, which keep repeating certain letters and having to type very hard to make them work. I searched and found a zip-file program that fixed that issue... but if you cant find a solution to the End Key problem, take it back to the store and let them handle it.
The Titan keyfix cab has fixed many of our problems with the keyboard and hard keys. Worth a shot I guess...
was your phone insured to be replaced?
My back button on the front capacitive screen won't respond the first time, I have to keep on hitting it until it registers. Anyone else have this issue?
I did some research and found out that the Vibrant was having the same issue with their home button.
Those buttons are my biggest gripe with the phone. You have to REALLY FREAKIN press on them. On the Evo, you just need to touch them lightly. I really love the bottom buttons on the evo. With the epic, touching them doesn't work. You need to press. Sometimes more than once. I also end up accidentally long pressing just to get it to work sometimes.
Samsung needs to learn from HTC and fix their buttons.
hydralisk said:
Those buttons are my biggest gripe with the phone. You have to REALLY FREAKIN press on them. On the Evo, you just need to touch them lightly. I really love the bottom buttons on the evo. With the epic, touching them doesn't work. You need to press. Sometimes more than once. I also end up accidentally long pressing just to get it to work sometimes.
Samsung needs to learn from HTC and fix their buttons.
Click to expand...
Click to collapse
N1s capactive buttons suck too, its HTC.
hydralisk said:
Those buttons are my biggest gripe with the phone. You have to REALLY FREAKIN press on them. On the Evo, you just need to touch them lightly. I really love the bottom buttons on the evo. With the epic, touching them doesn't work. You need to press. Sometimes more than once. I also end up accidentally long pressing just to get it to work sometimes.
Samsung needs to learn from HTC and fix their buttons.
Click to expand...
Click to collapse
I thought it was just me with the button thing. U actually have to press instead of just tapping it like on the evo
Sent from a FRESH EVO using xda app
It is not just you. Some are genuinely faulty. I see this being hte first major defect of this device. The back key on some seems to be worse than the search, home and menu keys. I had to replace my first Epic because of it.
I'm dealing with this, and the battery charging issue.
Ya I bought six epics for my whole family today. 4 are fine and 2 have back button issues. To the point where on one I have to push down severly hard. I am taking it back tommorow and going to see if they can swap it out.
I hope mune is not like this when I get it
My issue is with the MENU button and I notice that the feedback is the strongest on the HOME button. Sounds like the Epic is going back tomorrow.
This can probably be fixed with a software patch. If its common among all galaxy s phones, im sure samsung will issue a patch for this.
Gosh, reading all these post and trolling irc as the day wenton, I'm gad to only suffer the biggest problem of the epic, not being able to put it down! And maybe the spacebar, lol.
Sent from my SPH-D700 using XDA App
yea the ones that work are awesome... but the back button is unusable at all on 2 of mine so gotta get them replaced. Hopefully they still have a few left.
Yeah I noticed that too, it is inconsistent sometimes with almost all of them.
Sometimes you lightly tap it and it goes and than other times you will do it 3-4 times before it goes.
anyway to set the bottom buttons (back, home etc..) to be lid longer time?
Possible Solution: I do not have mine yet, but this is what I noticed from watching the reviews. If the lights are OFF on the buttons you need to press them more than once. If the lights are ON they will be responsive.
The light timer is linked to the keyboard backlight timer. Increase the keyboard timer(in settings) and the buttons will stay on longer as well, 30 seconds should be a good setting.
Again, I do not have my phone yet. Can someone with the issue please confirm this is a proper solution?
Pops_G said:
Possible Solution: I do not have mine yet, but this is what I noticed from watching the reviews. If the lights are OFF on the buttons you need to press them more than once. If the lights are ON they will be responsive.
The light timer is linked to the keyboard backlight timer. Increase the keyboard timer(in settings) and the buttons will stay on longer as well, 30 seconds should be a good setting.
Again, I do not have my phone yet. Can someone with the issue please confirm this is a proper solution?
Click to expand...
Click to collapse
"Increase the keyboard timer(in settings) and the buttons will stay on longer as well, 30 seconds should be a good setting."
worked like a charm, thank you
Back Button Issue
Got my Epic on 8/31 at about noon. I spent about 4 hours setting it up and did not even try making a call (except for one very short call). While working on the setup I noticed I had to hit the back button anywhere from 3 to 5 times and sometimes I really had to press hard.
Once I starting making calls with it I noticed that it had a lot of static and each call made it worse. Took it back to Sprint and got a new one. The new phone has NO issues with the back key!
Makes it seem like a hardware issue.
tsp
Pops_G said:
Again, I do not have my phone yet. Can someone with the issue please confirm this is a proper solution?
Click to expand...
Click to collapse
Unfortunately most people having this problem are having it when the lights are on. A lot of people have returned their epics already due to the buttons on the bottom....
I am having the same problem with the keys, they all need to be a lot more responsive. The back key is the worse.. Sometimes I have to press it 10 times for it to work.
vooman said:
I am having the same problem with the keys, they all need to be a lot more responsive. The back key is the worse.. Sometimes I have to press it 10 times for it to work.
Click to expand...
Click to collapse
I find that when i stop for a second and then press it good and hard, it works. I don't like that... but it never completely fails on me.
I hope they fan fix it so that you just need to slide your finger over it to make it work. That's how the Evo is. I think everyone would prefer that.
I'm about to exchange my phone, but I wanted to check here if anyone might have seen a similar issue, or have a clean solution to the problem.
If I press the volume rocker (up or down) and the power button simultaneously, then the screen will shut off, and then turn back on to show the lockscreen. The display doesn't timeout, but if I clear the lock screen, then the phone sometimes acts as if the volume rocker is held down. That means if the volume down was depressed, then the phone continuously vibrates.
I was able to recreate the problem at the Sprint store, but I haven't heard of anyone else on the forums being able to do so. Can anyone here recreate the bug?
It seems that this should be a software issue with the screen off procedure, and perhaps a wiping of the original rom might help. So far a factory hard reset using the built-in procedure hasn't cured the issue. Anyone have ideas?
I tried it and it doesn't happen on my phone. I did notice that if I held the volume down that the vibrate would stay on as long as the button was held down.
Ohh, that feels funny and tickles! Hey guys, tell your lady about this feature... Watch sprint get a bunch of shifts with burnt out vibrating motors. Lol
I read about this on the AndroidCentral forums, and I can't get mine to do that. It will sometimes stop the lock process, but it hasn't gotten stuck on vibrate. The other people I read about also said their phones didn't do it.
ah, I was looking for the link and realized that was you (or someone with the same screen name and problem haha) on the other forum, so I'm sure you already know that part.
Yeah, that's me. Just thought I'd try a different audience in case there were some different ideas. Thanks for responding though. Hopefully the exchange won't be for a bug worse than this one like the screen scrolling up while messaging.
The earlier post just made me realize that none of my other phones could ever continuously vibrate. haha. Maybe button free continuous vibration is a feature not a bug?
Did you try a factory reset on the phone?
I was just able to reproduce this easily.
Kinda funny.
Sent from my bathroom, with toilet paper.
Argh. I just exchanged my phone today and the new one does it too. I talked to an HTC person on the phone while at the store and they hadn't heard of the bug before. They also couldn't get the bug to reproduce, but I think it's just a matter of hitting the buttons enough times and at the right time. I also think the phone has to be in a ringer mode (at least two levels from the lowest setting).
I'm thinking I'm just going to have to get a case to make the rocker volume harder to hit. I think the size of my hands are just perfect for aligning my left thumb on the rocker when I'm powering off with my left index finger.
I did try the factory hard reset too, but no improvement other than it seemed like the odds of reproducing the bug went down a bit.
I don't see why this would be an issue, how often does one hit the volume rocker and the power button simultaneously? I've yet to come across this, and the thought of pressing the two buttons at the same time has never crossed my mind.
Sent from my PG06100 using XDA App
oboroninja said:
I don't see why this would be an issue, how often does one hit the volume rocker and the power button simultaneously? I've yet to come across this, and the thought of pressing the two buttons at the same time has never crossed my mind.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
It would be great if I could claim to be an awesome bug tester, but unfortunately that is not the case. I discovered the bug because I was inadvertently hitting both buttons at once when turning off the display. I have the fortune of my hand being perfectly sized that my left thumb lines up exactly on the volume down rocker when my left index finger is on the power button. Same is true for my right index finger and right ring finger. It actually took me some time to figure out the cause of the continuous vibrate mode.
It would have been nice to replace the phone with a non-buggy version, but for now I'll just have to have better finger coordination haha.
nth_79 said:
It would be great if I could claim to be an awesome bug tester, but unfortunately that is not the case. I discovered the bug because I was inadvertently hitting both buttons at once when turning off the display. I have the fortune of my hand being perfectly sized that my left thumb lines up exactly on the volume down rocker when my left index finger is on the power button. Same is true for my right index finger and right ring finger. It actually took me some time to figure out the cause of the continuous vibrate mode.
It would have been nice to replace the phone with a non-buggy version, but for now I'll just have to have better finger coordination haha.
Click to expand...
Click to collapse
Lol understood.
Sent from my PG06100 using XDA App
I've had this happen to me a few times too. It's probably a Sense (or HTC's Android build) bug not a problem with the hardware.
Makes me think of the old joke doc it hurts when i do this. Well dont do that lol
Sent from my PG06100 using XDA App
Having installed android just recently on my hd2, I started to use my hardware buttons more often. Now, whenever I push the windows-flag-button on the far left (still the button but close to its left rim), then the home-button is pushed too. Is this a general flaw of the hardware buttons or is it just my hd2. I would love to see some response, in order to see whether it makes any sense to send it in or to just live with it.
Thanks in advance!!
After I changed to the "Photon" style and use, I started using the hardware buttons extensively - that was already last summer.
Did never have any issue like you describe. Still everything working perfect for me.
erniepb said:
Having installed android just recently on my hd2, I started to use my hardware buttons more often. Now, whenever I push the windows-flag-button on the far left (still the button but close to its left rim), then the home-button is pushed too. Is this a general flaw of the hardware buttons or is it just my hd2. I would love to see some response, in order to see whether it makes any sense to send it in or to just live with it.
Thanks in advance!!
Click to expand...
Click to collapse
I have the same issue with my HD2 (also using an Android NAND). I believe, that it is a hardware-flaw, and not a ROM-Issue. I just made myself press more on the right of that button (closer to the middle of these two buttons (Flag and Back-button)) , and now it doesn't really bother me anymore.
I hope, I could help.
laerador
BTW: I own a O2 HD2 from Germany. (Might, that this flaw is connected to a specific model)
The hardware buttons begin failing on a lot of hd2s, this is a common problem since android makes you use hardware buttons more. There are several threads about it. Luckily, a dev from this forum created button savior for android, an app that creates soft buttons on the side of your screen that can pull out when you need them. Get Button Savior from the market... a needed app for the hd2 so you don't have to use your hardware buttons so much.
Just in case you don't know: there's a software alternative for hardware buttons on Android, SW Key.
http://forum.xda-developers.com/showthread.php?t=865525
Edit: oops sorry, previous poster also pointed you towards that. Well, here's the link ;-)
try not to use your nail to click on the key,, use the middle of your fingers to push slowly down.
Sent from my HTC HD2 using Tapatalk
is there any work around after a button has failed
marsbar 1 said:
is there any work around after a button has failed
Click to expand...
Click to collapse
Yeah, you read the whole thread
dio62000 said:
Just in case you don't know: there's a software alternative for hardware buttons on Android, SW Key.
http://forum.xda-developers.com/showthread.php?t=865525
Click to expand...
Click to collapse
My HD2 is about year old. I bought it (months 4 ago) with broken digitizer. Replaced it itself. What i finded inside is interesting. Buttons bar have clued some small plastic dots (see on pic). As i understand they fits to keypad excrescent plastic dots (dont have pic). And one of these on buttons bar was gone. I ordered then new button bar and now no more problems with buttons. Before i had too problems when i pushed home button accidently popped up calling or menu (windows logo button pressed).
Hope this helped you find right direction to resolve your problem.
Sorry, maybe the question was phrased incorrectly.
my home button has failed. in ASOP builds my phone boots into safemode.
in Sense builds it doesnt, but my battery ussage in both types of builds is above 50 ma
can I turn off the buttons to sort out the short in the rom.
Thanks for your response!!
I have sent it in for repair and got a 100% cash refund.
Well, let's see what little gadget I can buy for the money ...
This might be a relatively small problem but it can be a little annoying. The back button (right side of the menu button) seems to be a little less responsive and 'smaller' than the options button (left side of the menu button).
By smaller I mean I need to click it exactly at the right spot and the button reponsive 'area' seems to be very small compare to option button which seems to take up most of the left side allocated to it.
I am not sure if this is intented or some kind of software/hardware fault?
I read about upgrading touchpad firmware through *#*#2663#*#* but there are reports than this could brake the buttons completly.
If anyone has any information it will be greatly appreciated.
P.S phone is not rooted and I bought it from vodafone Ireland.
there are a few threads on the hardware buttons not working correctly try the search.
I found one about the back button, not a lot of info though.
http://forum.xda-developers.com/showthread.php?t=1057348&highlight=button
I have the same issue but also to another extent. Mine has an issue where sometimes it will double tap when I only press it once. This can get annoying. I do have a screen protector on and I'm not sure if that has anything to do with it.
Same thing happens to me ... but Its kinda rare(I am not using a screen protector). Does anyone know a solution? should updating firmware fix this?
I am thinking about asking for a replacement.
Replace it, same problem with my first unit, 20% of the presses didn't register
Sent from my GT-I9100 using XDA App
nomnompie said:
I have the same issue but also to another extent. Mine has an issue where sometimes it will double tap when I only press it once. This can get annoying. I do have a screen protector on and I'm not sure if that has anything to do with it.
Click to expand...
Click to collapse
I thought it was just me with the double tap when i press it once lol. Grrr its annoying man! :[email protected]
Sent from my GT-I9100 using XDA Premium App
So the only way to fix it is to replace it?
I would imagine someone can make a mod to the touchkeys for like a certain millisecond delay between presses to fix the double tap. People have patched hardware keyboards for stuff similar to that.
As far as the non-registering presses, that might have something to do with delay too. A smart developer would have to try and look at it though I'm just guessing here.
I haven't noticed the non-registered presses in a while, not sure if it went away with a new kernel or if I just got used to how to press it to make it work. The double tap happens more often to me now lol.
Happened to me on my first unit, back button was only responding about 50-60% of the time, on the 2nd phone back button was extremely sensitive ( as sensitive as the SAMOLED screen which is a huge plus) 3rd phone seems "normal"
Galaxy S2 back button getting pressed twice on a single press.
When I am in 2nd/3rd level screen of an app, back and menu button lights go off(but screen is on). While pressing back button sometimes it's going back 2 levels with one, single press! As if I have pressed it twice. It doesn't happen always though.
Is there any fix for this?
PS: I am using a screen protector. Will remove it and see if that's the culprit or not.
u shud b thankful mate..my home butoon stopped responding at all
Hi,
Sorry to hear that.
But how did it happen? And how old is your phone? It must be still under warranty. Did you try taking it to the service center?
Back button problem sgs 2
I was also having this annoying problem.....searched over XDA....and found some tricky (fishy) codes for updating touch firmware.....which may end up braking those keys....so i stayed away from those tricks..
i googled again and found one method which finally worked for me
To get sgs2 into sleep use power button...nd for waking up use home (centre) button...this worked for me
SGS 2/XWKF3/CF root
Odp: Back Button Problem
Sorry for digging it up. I have the same issue, sometimes back button is acting like it was tapped twice. Is there any sofware solution instead of replace any parts?
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
i had the same promblem and a full wipe did the job