Database Info

[Q] Hardware buttons went crazy!

Hello!
I'm experiencing some problems with my o2 Touch Pro.
Hardware buttons on the bottom of the phone (d-pad, home, back, call, end call) are not working properly (they work fine only 20% of the time, it's random i guess).
When i press "call" button, device responds as if i pressed the "left" button. It's very annoying. The circle used to zoom in, and out around the "enter" button is problematic as well. It zooms - but but in a very chatoic way - a bit of of zoom in, then zoom out, another zoom in. Functions are just messed up.
Another time, it's all working...
How can i fix it? Is it a hardware problem?
I'm using the Energy Rom - titanium version.
Thanks for your help in advance...

Honestly, if you can't deal with it, get another device. Either that or stick with the stock ROM, less problematic (you can also keep the full function of the d-pad) but then again it may introduce other issues. Someone mentioned this being more a hardware than a software issue. Since I cannot reproduce this on my at&t Fuze, that is all I can suggest on my end.

I get some of that with my fuze; mostly, the d-pad doesn't read gestures properly. If I run compact heaps (from sk tools) periodically, it helps. Soft resetting obviously helps as well. I think it's more of a hardware issue. My problems have definitely gotten worse over time. You can also check out this tool (from an HTC test rom dump; can't remember where I got it). It's a debugger for the d-pad. At least you can see how accurately the button presses and gestures work.

Thanks.

[Q][Huawei U8150] End button behavior

Hi all, I want to try Cyanogenmod 7 (latest nightly of course), but I realized that the end button (red end call button) behavior is different from the stock rom. The stock rom behavior is:
if not in home screen -> go to home screen
if in home screen -> do nothing
if locked and screen turned on -> turn screen off
everything else -> do nothing
Notice that pressing the end button seems to be different than pressing the home button: if the current foreground activity does not respond, home button won't work (ANR window will show up); end button, instead, will simply go to home screen, like if it's killing the current activity. However, relaunching the closed activity restores its previous state (like when I use the home button to get away from an activity).
Cyanogenmod has stock gingerbread behavior (which should be fine, I know it's the android way), but I really would like to preserve my habits.
I already tried:
Spare parts: does not have the option I'd like
Remapping keys via keymaps: doesn't work since behavior cannot be defined using the available built-in commands
I'll get my hands dirty in the Android code if necessary (I'm a developer), but I really want to know if there is another way before looking at the source code.

[Q] Pantech Crossover Button Mapping Issues

Today I did a software reset so I could let me fiance use my phone since it was a little better than her outdated Huwei. Upon rebooting the Home button no longer funtioned. It will still wake the screen however it does not function in any other way (so obviously its not a physical issue).
I was able to pull up the files to view the mapped buttons and even tried the app on xda for button remapping. However the crossover comes with an extra function button in the top left corner which doesn't function at all any more. This tells me that the mapping file was over written with an incompatible file. Possibly an issue with a wrong file being assigned after a software reset. Not quite sure.
What I would like to happen is to see if anyone else here has a Pantech Crossover and can simply send me there button assignment files.
Another issue I ran into after the reset was the notification bar (still shows at the top) is not draggable. I am not able to pull it down or even hit the "notifications" button under the menu when you hit the menu button from the home screen.
I am no noob to technology so feel free to ask for anything. If you have a crossover and are unsure on how to get those files please let me know and I will direct you. (Please already be rooted.. there are plenty of great guides on these forums on how to do this for both firmware versions available)

Menu button does not work with CM10 or cm based roms

Hi there,
my HTC One S (ville) fall down and the display was broken completely.
I bought myself a new a one and have build it in. While replacing the screen I screwed the Flex cable which is responsible for the hardware buttons at bottom (and the sound however).
I also got a new flex cable and replaced the old one.
1) Problem
When I restart my phone the buttons at the bottom work, until I get into lockscreen. After that they won't work anymore, I don't know why. (Only restart helps, again they work only until I got into lockscreen).
2) Workaround-Problem
So, as a workaround a decided to install CM10 to use the navigation bar (I set qemu.hw.mainkeys=0 in prop.build before I flashed the rom).
Now I have the problem with the menu button. The 3-dot menu button shows up but has obviously no function. When I click on it nothing happens - I can't access any settings menu in apps.
I tried also Virtual Button App - either there the menu function does not do anything.
Of course I rooted my phone etc...
Is there something special with the HTC ONE S and the menu button function?
Thanks very much in advance,
Maik

[Q] Remap volume-up button to power button

Hello all,
Recently the power button on my Nexus 5 has been acting really weird. Sometimes it works flawlessly, others it requires pressing it really hard to work. In order to prevent it to stop working indefinetely, I am looking for a way to remap my volume-up button so it can work as a power button. I don't need it to turn my phone on or to work in the recovery mode (from what I read, it seems to be impossible), only when Android is running.
I've already tried some workarounds:
1) Volume Unlock Power Button Fix app: I tried it, but it just allowed me to turn on my phone with volume but not turning off. Also, it drains a LOT of power.
2) Buttonremapper app: It would theoretically do exactly what I wanted, but did not work at all.
3) Editing generic.kl: I tried switching volume-up and power buttons codes in generic.kl, but also did not work. Maybe I need to modify another file?
3) Xposed Framework + Additions: The installation of Xposed went Ok, but after installing Additions module I got stucked in bootloop. I am running Android 5.1 stock, maybe this module is not yet compatible.
So, can anyone help me? Do I need to install a custom ROM?
PS: I live outside US, so no warranty for me. Otherwise I would just use it
Thanks in advance for any help!
Cheers,
Humberto

Hi folks,
Just a heads up for anyone who might be facing the same issue. I decided to change from stock to Cataclysm ROM due to some specific features (listed below). After the installation, here's what I did to work around this problem:
1) Enabled "Volume wake" and "Sleep button on status bar" in "Cataclysm Settings / Miscellaneous".
2) Enabled "Swipe to sleep" and resized NavBar to 115% in "Cataclysm Settings / Navigation bar options". -> This way I can swipe in NavBar at any time (except lockscreen) to turn off screen. I raised it a little to facilitate the swipe gesture.
3) Changed Lockscreen Dialer shortcut to ""Turn off Screen" app shortcut (just search for it in the play store) in "Cataclysm Settings / Lockscreen options" -> This allows me to just swipe right and turn off the screen when my security settings are disabled (which accounts for most of the time). I found it way faster than pressing sleep button in status bar, especially when I'm driving and I can't look at the screen. Plus, I don't really use the dialer function of my phone so often since the invention of Whatsapp ;P
I realize this is not the perfect solution, but I don't see a better way to deal with this power button malfunction problem (except from a hardware fix).
Hope this helps!
Cheers,
Humberto
PS: I am really enjoying Cataclysm. It's a very nice ROM, completely stable and with a lot of other interesting features aside from the ones mentioned above. I strongly encourage anyone to give it a try!

I'm facing the exact same problem but I really need to eliminate the power button or I will need a power button fix soon.
The solutions you found hthiengo are good if not needing to turn off (or worst: running out of battery, something that happens me sometimes). I'm in the situation that next time I hit power button I will need to replace the button, or throw the nexus away
I did installed the xposed additions for lollipop but it is not working, and the Cataclysm trick is not enough in this case

Ok, after some research I've found a temporary solution:
For the power button you can remap modifying the file gpio-keys.kl under system/usr/keylaout (i wonder why anyone could figure out thise before, no that difficult). I would like to map power button leeaving it useless but I've found it impossible to remap the power button (probably because the key number is not 116). I would have liked to see xposed additions to help me map the keys but is not functional at least for me.
If the phone runs out of battery I've found that if I plug the power cable by pressing both volume buttons at the same time, eventually it starts up with the bootloader so I can plug the pc cable and it will reboot sucessfully.
So despite the phone know is pretty disfunctional (not the best phone for a hurry without battery), I can still use it for some weeks before I plan buying a new one or something (or I find a place for reparing). Its a shame I could not find a better solution for example, ADT when powered off so I could just reboot it by using ADT reboot command while powered off.
And It would be really amazing if the volume up button could also power it on from the powered off state.
In my case the power button is broken, but sometimes it gets stuck and puts the phone in a reboot loop: To avoid pressing the power button accidentally I've made a hole in the protective case so its pretty difficult to access it.
That's all for now. If anyone can make it better I will be glad to hear him/her