With our beloved HTC Desire devices getting a bit aged, I expect the wear-related problems will start to increase.
I am having an issue with the BACK button (the one with the arrow on, at the bottom, second from the right) that does not respond easily. It takes numerous "convincing" keypress attempts to get it to eventually perform the action. So I guess the switch is worn out?
What would be the easiest way to rectify this problem, or is a patient wait until upgrade-time the answer?
Sent from my GT-I9300 using xda premium
Highlander11 said:
With our beloved HTC Desire devices getting a bit aged, I expect the wear-related problems will start to increase.
I am having an issue with the BACK button (the one with the arrow on, at the bottom, second from the right) that does not respond easily. It takes numerous "convincing" keypress attempts to get it to eventually perform the action. So I guess the switch is worn out?
What would be the easiest way to rectify this problem, or is a patient wait until upgrade-time the answer?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
You can try a rom with on screen buttons like the one in my signature! It'll have the same buttons on screen like the galaxy nexus.
Or you could make the d-pad do the back function. System>usr>keylayout and edit the bravo-keypad. I made my search button act like the volume down button, since that one's broken.
Sent from my toaster.
abaaaabbbb63 said:
Or you could make the d-pad do the back function. System>usr>keylayout and edit the bravo-keypad. I made my search button act like the volume down button, since that one's broken.
Sent from my toaster.
Click to expand...
Click to collapse
Nice 1, worked a treat. I just made my search button volume down coz its almost completely not working and i never use search button soo now i have a perfectly working volume down button. Cheers
Sent from my HTC Desire
Highlander11 said:
With our beloved HTC Desire devices getting a bit aged, I expect the wear-related problems will start to increase.
I am having an issue with the BACK button (the one with the arrow on, at the bottom, second from the right) that does not respond easily. It takes numerous "convincing" keypress attempts to get it to eventually perform the action. So I guess the switch is worn out?
What would be the easiest way to rectify this problem, or is a patient wait until upgrade-time the answer?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
It could be the ROM issue too. After changing a couple of roms, I've found that key responsiveness changes, try CM10 based builds. I'm using elk759's
Thank you so much for the suggestions so far! I'll try them out . If anyone has other suggestions, please feel free to help :thumbup:
Sent from my GT-I9300 using xda premium
Related
Is there a mod out there that can be applied to the ota that let's us power on the screen with the trackpad? Reminds me of my old Eris.
Sent from my ADR6300 using Tapatalk
I'm pretty sure last time I checked that remapping the trackball was not possible
Sent from my ADR6300 using XDA App
It is possible. I do believe Chads kernel comes with it. That or CM7 has it. I can do it with my phone, at least. It doesn't always work on the first press, so you sometimes have to hold it down. I noticed when I'm charging it works first time, every time. Unsure why that is though.
Sent from my Droid Incredible running some random CM7 nightly.
You can use Button Remapper from the market or google it. Also Sky Raiders, OVO, Synergy, CM7 and most roms that are not stock have the option for trackepad wale
Sent from my OVO Community ROM using XDA App
if you poke around in /system/usr/keylayout you can find two files "incrediblec-keypad.kl" and "qwerty.kl" these two handle the mapping of the keys so that android OS knows how to handle they key events.
I don't have the OTA so I haven't tested it but back in the day you would find the DPAD_CENTER line and change it from WAKE_DROPPED to WAKE.
I played a lot with these files because I really wanted a decicated CAMERA button and the OJ was perfect for me. Hope this helps and I wish I could test this before I started making suggestions to you. Good luck.
SteveG12543 said:
It is possible. I do believe Chads kernel comes with it. That or CM7 has it. I can do it with my phone, at least. It doesn't always work on the first press, so you sometimes have to hold it down. I noticed when I'm charging it works first time, every time. Unsure why that is though.
Sent from my Droid Incredible running some random CM7 nightly.
Click to expand...
Click to collapse
As far as the why, it is because the phone screen is still "Awake" if I remember correctly. If you power your phone off then immediately press the optical button, your screen will come on but it won't if you wait say five seconds. I've noticed the same as what you stated occur in one of Nils' older gingersense roms.
SlimSnoopOS said:
As far as the why, it is because the phone screen is still "Awake" if I remember correctly. If you power your phone off then immediately press the optical button, your screen will come on but it won't if you wait say five seconds. I've noticed the same as what you stated occur in one of Nils' older gingersense roms.
Click to expand...
Click to collapse
Huh, weird lol. Never noticed that myself. I usually don't lock then unlock lol. Quite interesting, though.
Sent from my Droid Incredible running some random CM7 nightly.
Guys/gals
I have noticed that while in CWM, the up and down presses of the volume button are acting weirdly. Sometimes it will scroll through 3-5 lines while other times it is doing what it should and moving one spot at a time. I am rooted running gummynex and using the proper CWM version. Any others experience this also?
On a side note, this sometimes disables the functionality of the 'enter' button on the right side also.
Never had any problems with CWM navigation here ... maybe re-flash CWM?
Edit: Does your volume key act weirdly just adjusting the volume? If so it may be bad hardware
Mine does the same. Its when you hold the rocker down for a long period of time. Just tap one by one and you'll be good. I kinda like the ability. It allows for faster scrolling.
Sent from my Galaxy Nexus using Tapatalk
it is only in CWM... volume functionality is perfect in normal actions. it is extremely sensitive in CWM. sometimes i can choose carefully and get it to move one option at a time, but it is far too sensitive to be fun to use in this way.
maybe i'll try the touch version and see if that is any easier. it does not seem hardware related since I have seen 3 or 4 others with the same issue only in CWM.
Be careful with the touch version. I've seen a few zip files where the developer specifically states not to use the touch version. Just a Tuesday morning fair warning.
Sent from my Galaxy Nexus using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1428338
Fix.
I've never had a problem with the touch version. I'd recommend just using that.
Sent from my GalaxyNexus using XDA App
Hey everyone, I've been having a little bug that I noticed after I received the 4.0.4 update. I don't know what I exactly do to cause this but my nexus takes random screenshots whenever I press my power button to unlock my phone. I have the pattern lock that I use and when I hit power it randomly vibrates and when I go check my gallery it shows that I just took a screenshot. At times, when my battery is low it seems to randomly vibrate again and take a screen shot and gives me the prompt screen for which app I'd like to use to complete the action... No, I don't press the volume down key when this happens and no I don't have any screenshot apps. I'm stock, non rooted... Anyone else have this issue?
Stuck volume key?
adrynalyne said:
Stuck volume key?
Click to expand...
Click to collapse
I'm having doubts that it would be that...sometimes it does it even when I don't touch the power off key..
I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.
Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA
Do any of you guys run a rom that gives the ability to use the volume rocker to take screenshots? Have you tried reflashing your roms since you updated?
Sent from my Galaxy Nexus using Tapatalk 2
xterrain15 said:
I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.
Click to expand...
Click to collapse
Upload it somewhere and update your post with the link.
sent from my i9250
Posting the bug report
docs.google.com/open?id=0BxAJdhmCAyirSDU2UEU5dTRyQzg
There it is.
I am about to try flashing the 4.0.4 update again, as I just downloaded the zip of it.
Screenshots are Volume Down + Power. Bug Reports with screenshots are Both Volume Keys + Power. Do you have a case on? I've seen many people having these issues that were due to a tight fitting case.
Case
I do have a case on, but I know that's not the issue, as the power button is not covered, and this often occurs without me being anywhere near the power button. It can happen in the middle of typing out a text message. A prompt appears asking what application I'd like to complete this action with, and if I check the gallery later, there will be a new screenshot of my messaging app.
Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.
ceribaen said:
Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.
Click to expand...
Click to collapse
AOKP allows you to set up any functions/icons to softkeys
Sent from my Galaxy Nexus using xda premium
nirco68 said:
Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I have the exact same problem! No clue what's causing this. I'm on AOKP M5 on rooted Galaxy Nexus. I can't find any setting to disable bug report creation, nor can I find anything about bug reports in the settings at all. I really hope someone can figure out what's causing these spontaneous bug reports (plus screenshots) to be generated.
Same issue
I just received my 4.0.4 update on Galaxy Nexus, and I am having the same issue. It randomly takes a snapshot of the lock screen and generates a bug report. Have they added some new hardkey combination that is too easy to trigger? I do have a case on, but I have always had it on, way before the update.
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
chandradithya said:
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Click to expand...
Click to collapse
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.
ABQNM said:
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
No offence to you. Seriously.
was annoyed with this issue, google searched it , opened a lot of tabs, found many posts never had answers,
I agree it was copy paste, sorry for not mentioning the source.
I edited them and linked it to your post on rootzwiki,
I was in a hurry then and rushed up and pasted on the threads where there was no proper answers.
I have the same problem
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.
Drakonworld said:
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.
Click to expand...
Click to collapse
See my full explanation here http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123 (last post on the page). Simple answer, something is pressing all three buttons at once, be it a case or whatever. Either disable usb debugging to turn it off or see my link for instructions to disable just the bugmailer.
Sent from my brain using human to phone transport technology.
Hello. My haptic buttons (4 bottom touch buttons) are sometimes unresponsive. Sometimes when i'm using the browser I'll get stuck in it for a few seconds. And often after unlocking the phone they are also unresponsive. I just move my fender around the screen to make it come back. It's not a big issue but it is annoying.
Is there a fix? thanks!
running super galaxy 1.5 rom
bump. no one having this issue? =[
noahsarky said:
bump. no one having this issue? =[
Click to expand...
Click to collapse
Ive had it a few times when i start the phone back up in the morning, only seems to happen to me when in not usung it, i believe i read somewhere that this was an ics issue...ive found somewhat of a fix by going to settings/display and setting hardkeys to always on....drains a bit more battery but your problem will happen so rarely afterwards itll become a non issue..hope that helps! If it did, flash my rom and visit my thread!!!!
Sent from my SPH-D710 using xda premium
I've had this on ICS on occasion as well, after waking the phone up. I do the same thing - move my finger around to get them to come on.
I can't find hardkeys always on options. can be it same as tough key light always on?
noahsarky said:
I can't find hardkeys always on options. can be it same as tough key light always on?
Click to expand...
Click to collapse
This isn't an ICS issue. It happens on custom AND stock GB as well.
Often, you can make them responsive again by hitting one of the volume keys, too.
I doubt its a hardware issue... It must be a driver issue.
I'm new to Android and enjoying my Note 8, but one thing drives me nuts. I often accidentally hit the back "button" and have yet to find its mirror image--forward. This is really bad when I am on the web and lose my place and have to navigate back. What am I missing here? How do you undo the Back button?
jventola said:
I'm new to Android and enjoying my Note 8, but one thing drives me nuts. I often accidentally hit the back "button" and have yet to find its mirror image--forward. This is really bad when I am on the web and lose my place and have to navigate back. What am I missing here? How do you undo the Back button?
Click to expand...
Click to collapse
if by "on the web" you mean browser, then this arrow button might be helpful:
Sent from my GT-N5100 using xda premium
p107r0 said:
if by "on the web" you mean browser, then this arrow button might be helpful:
Sent from my GT-N5100 using xda premium
Click to expand...
Click to collapse
I was not very clear, sorry. It is hard for me to describe exactly since it always comes as a shock for the app to disappear and when I get it back from the app manager it is not always in the same state, and I have to click back to where I was. If you put in a back button, you need an undo, I think.
Sooner or later I'll learn how to hold the thing without hitting that button all the time.
jventola said:
I was not very clear, sorry. It is hard for me to describe exactly since it always comes as a shock for the app to disappear and when I get it back from the app manager it is not always in the same state, and I have to click back to where I was. If you put in a back button, you need an undo, I think.
Sooner or later I'll learn how to hold the thing without hitting that button all the time.
Click to expand...
Click to collapse
you could consider disabling capacitive keys: http://forum.xda-developers.com/showthread.php?t=2250941
Sent from my GT-N5100 using xda premium