I've installed cyanogenmod 7 on my vibrant and the home button randomly stopped working. Now, it only works when all the buttons are lit up. In other words, if I click the back button first to light up the soft buttons and then click the home button, it works (I can keep clicking it repeatedly and get a vibration feedback until it goes dark).
This has happened to me on previous installations of cyanogenmod 7. I'm guessing if I reinstall it again it will work for awhile and eventually stop working.
Any suggestions on what's going on?
That sounds like a very interesting problem. I read somewhere that our capacitive buttons aren't very sensitive. One way to ensure you're pressing the button is if you slide your finger over the button.
Related
I didn't find anything about that, but it seems that I have a problem with Menu and back button... mainly the back button.
Normaly, when a I press menu or back button, both illuminate. Since today, sometime, only the menu or back button illuminate. The one that does not illuminate is not working.
I tried to press everywhere on the phone, shake it, removing sim, rebooting, etc... didnt find what cause that. Could be hardware or software (I have stock rom).
Anyone have seen this?
Thanks !
well... playing a bit with it today. I hold it flat in my hand, turning left or right... light were blinking on menu or back button... sound like hardware problems
I was wondering if theres a patch of some sort that would remove the longer vibration when holding down the capacitive buttons (home, menu, back) keys. its kind of annoying that when i hold home to multitask it goes zzz. ZZZZZZ. instead of just one vibration.
im on steve's 1.6 and when i hold home to go to recent apps, it only vibrates once, so not sure about you or what rom you are running
I'm on stock 2.2 318
iphonepimp said:
I was wondering if theres a patch of some sort that would remove the longer vibration when holding down the capacitive buttons (home, menu, back) keys. its kind of annoying that when i hold home to multitask it goes zzz. ZZZZZZ. instead of just one vibration.
Click to expand...
Click to collapse
mine does it one time as well, 1.6.1 dj steve's, try disabling the haptic feedback under spare parts
If you go to Settings, Sounds and disable Haptic feedback, only does the "ZZZZ" without the first zz, zz.
Still, would be nice if it just did short vibration (zz) instead of long ZZZZ.
Thx. Fixed
Ok, I now have it completely silence. Just lift your finger just before the buzz! So not even a second.
I was reading a book and the screen just stopped responding to finger touches, I think a reset might fix it but I can't switch it off. Long press on the off switch gives me the Android power options but of course I can't select any of them.
Any ideas? apart from waiting for the battery to go dead.
/edit solved it, long press of power and center button uintil you see the HP logo. I thought there might be some Android specific way.
For touchscreen not responding, I often just click power button to turn off the screen, then home to wake it up. That seems to fix it more often than not.
Next time you need to reboot, just hold down Home + Power for 10+ seconds
I'm not sure what the cause of it is, but perhaps you guys can help me out.
I've had my Optimus V for a while now and have flashed IHO-backside to it in December.
Recently, my camera button has been acting very strange. You see, it still functions as a camera button. Holding it down (completely) will launch the right app, hold it down (loosely) focuses the camera, and pressing it down completely will take a snapshot. That's all fine and dandy.
However... When I'm not in a camera app the camera button takes on a different set of functions. For some reason, lightly touching the button triggers a Volume Up, Volume Down, and/or Voice button press. I'm not sure why this happens. It's very strange. If you even so much as to come to physical contact with the button, it will send those "button presses" above. Clicking the button still works correctly, though.
I went into the ClockworkMod recovery to double check the key presses for it. It was VERY difficult because pressing the camera button to select an option will trigger the Vol up, Vol down and Voice presses making me select the wrong options in the recovery menu. Anyway, the following gets returned when lightly tapping the camera button:
key 115, key 114, key 216. (Vol up, Vol down, and Voice)
I checked the key file located here: /system/usr/keylayout/thunder_keypad.kl and found that everything is still mapping to the right buttons.
Can someone please tell me what's going on and how to make it stop doing this?
Anyone?
Is this possible? I just want it to not turn on the screen. I notice in my front pocket sitting down sometimes the power button gets pressed and turns on the screen. I would prefer the home button only cause it is flatter and more flush with the device. I am able to edit the home button to either wake or not wake the phone, but the power button wakes the phone even when I erase the fields in all the system/usr/keylayout files. There must be a backup file or something somewhere telling the power button to turn the screen on. I use WidgetLocker also.
Are you sure it's not the home button turning your screen on? Pretty common occurrence...
Sent from my Xposed Beans Note 2
Its TwiX said:
Are you sure it's not the home button turning your screen on? Pretty common occurrence...
Sent from my Xposed Beans Note 2
Click to expand...
Click to collapse
No. I have disabled that and will leave it disabled until I can figure out how to disable the power button.
i would like to see this as well, the power button is too easy to press accidentally. i tried editing the keylayout files but i couldnt get it to work either.... here's my ideal setup: the home button wakes the phone, the power button does nothing unless you long press it to bring up the power options menu. or press it while the screen is on to turn off screen.
I too have this problem.
The power button is easy to press when it's on my pocket and I even have a case on it. The case makes it a little harder to press but I can still hear the click of the button when so I know when it happens.