Related
I've seen that a lot of people have unresponsive back buttons, but mine seems to be the opposite.
Several times now, with seemingly no easy way to reproduce it, I've been able to activate the back button without touching it. With the keyboard out, and without touching the screen or the back button on the keyboard, I'm able to tap the lower right hand corner of the case (I have a Seidio case on it) that protects the screen and it triggers the back button. It's to the point where if I can do it once, I can do it multiple times.
Not sure if any of that made sense, but I'm sure people who are experiencing similar problems have also seen it and might have an idea of what's up.
Possible answer for unresponsive back button on Epic
I need help with this possible answer to the unresponsive back button problem.
1. If I use my right index finger to tap and sometimes multi taps to get the back button to work.
2. But if I use my right thumb the back button works everytime. Only a light tap with my thumb is all that it takes.
Please try and post if this works for you.
lordcyrus said:
I've seen that a lot of people have unresponsive back buttons, but mine seems to be the opposite.
Several times now, with seemingly no easy way to reproduce it, I've been able to activate the back button without touching it. With the keyboard out, and without touching the screen or the back button on the keyboard, I'm able to tap the lower right hand corner of the case (I have a Seidio case on it) that protects the screen and it triggers the back button. It's to the point where if I can do it once, I can do it multiple times.
Not sure if any of that made sense, but I'm sure people who are experiencing similar problems have also seen it and might have an idea of what's up.
Click to expand...
Click to collapse
jstine671 said:
I need help with this possible answer to the unresponsive back button problem.
1. If I use my right index finger to tap and sometimes multi taps to get the back button to work.
2. But if I use my right thumb the back button works everytime. Only a light tap with my thumb is all that it takes.
Please try and post if this works for you.
Click to expand...
Click to collapse
That's... got nothing to do with my question. Again, my back button is perfectly responsive. If I click it, it works, end of story. The problem is that it seems to click itself or activate when I touch various parts of the screen portion of the phone without actually touching the back button.
Unfortunatly this is a known issue and one of the reasons I switched away from the Epic. I had 2 that were bad the first one having issues similar
Best of luck...
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.
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
Hi
Ive posted this over on the Android Forum however not so many replies yet so thought I'd post here too.
Please can you check your home button operation and reply with the following:
- Does your home button work regardless of how soft you press the button ?
I almost have to deliberately apply a 'little' extra pressure on the button to get it to operate, if I press it softly it doesn't work.
I tried a demo model in the local phone shop and it worked every time regardless of how soft I pressed the button (i couldn't get it NOT to work), but the sales guy's own phone was more like mine in that it needed a slightly harder press.
I would be interested to see what the majority are like so i can make a decision on whether to exchange it or live with it.
Thanks.
On my S4, as long as the pressing is registered (click sound can be heard) then it work, I don't need to press it hard.
Change it. Mine works everytime.
How do i get rid of the image verification? Does everybody have to do it everytime you want to reply to a post?
The moment it clicks, it activates. I've tried to click it as lightly as possible.
Change it mine works perfectly
Sent from my GT-I9500 using xda app-developers app
Bully74uk said:
Hi
Ive posted this over on the Android Forum however not so many replies yet so thought I'd post here too.
Please can you check your home button operation and reply with the following:
- Does your home button work regardless of how soft you press the button ?
I almost have to deliberately apply a 'little' extra pressure on the button to get it to operate, if I press it softly it doesn't work.
I tried a demo model in the local phone shop and it worked every time regardless of how soft I pressed the button (i couldn't get it NOT to work), but the sales guy's own phone was more like mine in that it needed a slightly harder press.
I would be interested to see what the majority are like so i can make a decision on whether to exchange it or live with it.
Thanks.
Click to expand...
Click to collapse
My vote goes with everyone else, change it! I've tried mine, both soft and hard, as soon as there's a click, the phone responds. I've tried demo ones too before purchasing mine and they too were easy to press, even with the hoards of people constantly having a bash at it!
Perhaps you got unlucky and got a dodgy one.
Good luck though either way.
Trick:
Open S Voice app > Settings > disable "Double Tap to open S Voice" its in the menu somewhere > restart phone > see if its more responsive.
AMDPOWERFIST said:
Trick:
Open S Voice app > Settings > disable "Double Tap to open S Voice" its in the menu somewhere > restart phone > see if its more responsive.
Click to expand...
Click to collapse
Ye this should make a difference, if you still find the home button lack responsiveness after preventing s-voice action on home button then take the device back you have a bad button
Bully74uk said:
Hi
Ive posted this over on the Android Forum however not so many replies yet so thought I'd post here too.
Please can you check your home button operation and reply with the following:
- Does your home button work regardless of how soft you press the button ?
I almost have to deliberately apply a 'little' extra pressure on the button to get it to operate, if I press it softly it doesn't work.
I tried a demo model in the local phone shop and it worked every time regardless of how soft I pressed the button (i couldn't get it NOT to work), but the sales guy's own phone was more like mine in that it needed a slightly harder press.
I would be interested to see what the majority are like so i can make a decision on whether to exchange it or live with it.
Thanks.
Click to expand...
Click to collapse
Demo model will have been pressed hundreds of times so is probably worn in
Thanks for the replies.
Had phone exchanged today, replacement is much better.
On mine, i can hear and feel a slight crackling noise with light touch without pressing the key all the way down. The button feels solid, tight and works just fine, but it bothers me that it does that. The shop people wouldn't consider this as a defect since it's so minor, but minor enough to annoy a fussy tech person like me.
Does anyone else have this problem?
Hey there,
I've a big issue for a few months already.
My S4 jflte always wakes up whenever the screen turns off.
I tried to figure out where it's caused by and when I cut off the soft buttons (home/menu/back) and started the phone, the screen didn't wake up anymore.
As far as I know there is no way to repair this w/o damaging the screen itself.
So could I block the buttons from waking up the screen?
As you can see when a app is opened and the screen turns off automatically and turns on again, the home screen appears and puts the app in the background.
youtube(.)com/watch?v=Bhul9UMJ8l4 (I don't have 10 posts yet so I have to post it this way. Sorry)
Could anyone help me? I've been researching for a long time and found no solution.
Says video not found.
Are you on a stock rom?
The Video is working fine for me. Did you copy the whole link and did you remove the brackets? ( )
I'm on AOSP 6.0.1 Kernel 3.4.110-Alucard-PWR-CORE from JDCTeam.
I tried different ROMs so far (including the Stock) and it's definitely a hardware issue.
http://www.youtube.com/watch?v=Bhul9UMJ8l4
have you been doing full wipes inbetween roms ? if you have then maybe it's a hardware issue.
Yes, I've always done full wipes. I'm pretty sure it's a hardware issue. Is there any way to block the keys from waking up the phone? I usually use the power button anyways to wake up the phone.
You can probably disable the keys altogether. Or maybe just the menu and back key, and leave only the home button functional.
There is no way to do it with that rom yet, but you could use Xposed and Gravity Box.
Most apps nowadays offer inbuilt menu and back options anyway.
Before you try to disconnect any buttons, try to clean the phone. That has solved many problems in the past.
Look for disassemble S4 videos on youtube, and for cleaning use a small paintbrush, or a very soft toothbrush, and Isoprophyl Alcohol(70% clean alcohol, 30% pure water), you can buy that in the Apotheke.
Clean the board an all other reachable electronics. Let it dry, reassemble and see if it helped.
Thanks for the tips, but I've already done that before (twice) without success.
I'm looking for a way to disable the keys from waking up the screen. I've tried it with the key configuration files in the system, but it didn't work.
Example: When I press the home button the screen wakes up. I just want to disable the wake up for all buttons except for the power button.
Does anyone know a app for this? Or a mod for xposed?
There is no actual "wake up" function assigned to the back and menu key. Only the home button has one. So there's nothing you can disable, except for the keys altogether. I already suggested you how to do that in the 5th reply to this thread.
I've found a work-around. I disabled the keys with 'Xposed Additions' while the screen is turned off or locked.
Thanks alot for your help guys!