I'm running liquid smooth RC 5 and I was wondering if there is a way I can turn off the soft keys (including vibrations) I couldnt find it in the settings is there an app for it?
So your thread title says hardware keys then in the post you said softkeys...what do you want disabled?
sorry. softkey as in the menu and back button.
This adds on screen buttons (won't matter if rom already has it). 4 different zips, one will disable your soft keys.
http://forum.xda-developers.com/showthread.php?t=1918166
Boom! Jellybomb biatch!
Related
Is there a method of preventing the default android buttons: home, menu, search, and back from being active? Or locking the default android buttons while still able to use the device?It seems like I am constantly bumping these keys, as I'm always back on my home screen some how. I tried google with no luck. Currently running vegan tab beta 5.1 which of course has the soft keys to use instead.I am looking for either a permanent our semi-permanent method.Thanks in advance.
wacckkoo1 said:
Is there a method of preventing the default android buttons: home, menu, search, and back from being active? Or locking the default android buttons while still able to use the device?It seems like I am constantly bumping these keys, as I'm always back on my home screen some how. I tried google with no luck. Currently running vegan tab beta 5.1 which of course has the soft keys to use instead.I am looking for either a permanent our semi-permanent method.Thanks in advance.
Click to expand...
Click to collapse
As mentioned somewhere here, you can use Button Remapper to remap those four buttons to focus, effectively turning them off.
In addition, I would recommend the use of Button Savior to give you the ability to bring up soft buttons when needed (i.e. in apps where the task bar is not visible).
Use them both...problem solved
Which Button Remapper? Did a search in the market, found one for the hero and galaxy tab?
Soft Button Solution..
http://forum.xda-developers.com/showthread.php?t=865525
Hope this will help..
jaybob413 said:
As mentioned somewhere here, you can use Button Remapper to remap those four buttons to focus, effectively turning them off.
In addition, I would recommend the use of Button Savior to give you the ability to bring up soft buttons when needed (i.e. in apps where the task bar is not visible).
Click to expand...
Click to collapse
Thank you gonna give that a try now.
This works really well. Now I just have to train myself out of trying to use the capacitive buttons.
Just wondering if there is a mod similar to the Softkey Enabler for the International One X? http://forum.xda-developers.com/showthread.php?t=1797850
I tried that mod on CM10 on my One XL (AT&T) but hit hangs on boot.
Thanks
Ask your fav dev to enable it, I'm not sure why you would want this?
Sent from my HTC One XL using Tapatalk 2
superchilpil said:
Ask your fav dev to enable it, I'm not sure why you would want this?
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
for one. I replaced my screen so I have screen separation issues.
would be nice to enable softkeys (disable soft keys) so that the LEDs from the capacitive buttons don't shine through.
rubensun said:
for one. I replaced my screen so I have screen separation issues.
would be nice to enable softkeys (disable soft keys) so that the LEDs from the capacitive buttons don't shine through.
Click to expand...
Click to collapse
To each their own, I would just disable the backlight on the buttons
Like I said just ask a dev to make a patch, most will be happy to when they have time
Sent from my HTC One XL using Tapatalk 2
Thanks for the info. I'm coming from a Galaxy Nexus, and I like the soft bar. The rotation of the softkeys is nice, and I tend to hit the silkscreen by accident either when holding the phone.
Being a bit new on this forum, any suggestions a dev that may be amenable to requests
Thanks
The hugest reason for enabling soft keys are for iphone people. We are extremely used to having "safe" areas to grab a phone, esp in landscape. I have used an android phone for six months and I don't know where to grab the thing in landscape. I'm always accidentally touching the home or back button and going between apps, it's annoying. And it really hampers usability. This is something that I can't get used to. I definitely think Apple is right to have a hardware old-fashioned home button, or at least some bezel space. This is why I want the soft keys patch for the One XL.
lamenramen said:
The hugest reason for enabling soft keys are for iphone people. We are extremely used to having "safe" areas to grab a phone, esp in landscape. I have used an android phone for six months and I don't know where to grab the thing in landscape. I'm always accidentally touching the home or back button and going between apps, it's annoying. And it really hampers usability. This is something that I can't get used to. I definitely think Apple is right to have a hardware old-fashioned home button, or at least some bezel space. This is why I want the soft keys patch for the One XL.
Click to expand...
Click to collapse
decompile framework-res.apk for the ROM you are using.
I think softkey enabling is in bools.xml.. if not search through strings, arrays, or public.xml
When you find it and change it, recompile and push it to /system/framework
lamenramen said:
The hugest reason for enabling soft keys are for iphone people. We are extremely used to having "safe" areas to grab a phone, esp in landscape. I have used an android phone for six months and I don't know where to grab the thing in landscape. I'm always accidentally touching the home or back button and going between apps, it's annoying. And it really hampers usability. This is something that I can't get used to. I definitely think Apple is right to have a hardware old-fashioned home button, or at least some bezel space. This is why I want the soft keys patch for the One XL.
Click to expand...
Click to collapse
TUTORIAL: How to Turn Off the Hardware Keys - Function, Lights and Vibration
This will work for any AOSP ROM.
1) I used AOKP 4.2.1, you can disable your hardware keys(sort of) editing 2 files in you system/usr/keylayout folder: keypad_8960.kl & synaptics-rmi-touchscreen.kl
Edit these entries in both files, you must open then as a text file and be using a root explorer.
Set key 102, 139, 158, 217 to FOCUS, this will make them do nothing when you are in every app except in camera, when they make it focus.
Save each file after editing and reboot.
2) To turn off vibration go to settings/sound and turn off vibrate on touch.
3) To turn off other hardware key backlights use: AdjBrightness
In AdjBrightness turn off the buttons by pressing the button marked "buttons" under the light toggles. To lock then off so they dont come back on after locking and unlocking, press settings key in that app to bring up a menu, then press Option. Then, under buttons check the first one, "Lock off button lights".
That is it you are done. The only thing is you have it open AdjBrightness after a reboot so it can apply the settings.
superchilpil said:
To each their own, I would just disable the backlight on the buttons
Like I said just ask a dev to make a patch, most will be happy to when they have time
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Try this, worked for me!
https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness
Sent from my HTC One X using xda app-developers app
The soft key lights on this device seem to work differently then most other android devices with back light soft keys. I've been trying to figure this out for a while. When exactly does the phone decide to turn them off, and and why can't I turn them off using apps like screen filter, and even on the stock t mobile rom?
Is this a hardware or software issue?
What I know is that the soft key lights in kj6 (gingerbread) roms turn on every time you turn the screen on or touch the screen, and turn off after 3 seconds of inactivity (not touching the screen or pressing any buttons).
But it seems that in some situations the soft keys turn off and stay off, even when touching the screen, which is seemingly random. Why does it do this?
Does anybody know when exactly the soft key lights decide to turn off?
From what I can tell, the Team Acid ICS driver does what it is supposed to do -- turn on and off the lights when the magic number is written to the right sysfs location.
The control of the lights is supposed to happen in the Android world with PowerManager and LightsService. The "problem" is that it seems as though the chip that controls the touchkeys and their backlight have a mind of their own and turn on the lights when you touch them. This gets the Android world's idea of if they are on or not confused, resulting in LightsService not "turning off" the light as it thinks they are already off.
I'm working through a good way to resolve this. Messing with the framework code is not the best as it means that TeamAcid would have their own version, and keeping up with upstream changes would be more difficult. Unfortunately, how it was done in GB is something of a mystery as it isn't clear to me from the Samsung code drop.
https://github.com/teamacid/android_device_samsung_galaxys4gmtd/issues/32
Are the soft key lights on the sgs4g the same as the original us versions of the Samsung galaxy (the vibrant/captivate)? If they have a fix for this (I assume they might because they have a larger development community) , would it work for our device?
I'm looking into if I can find some dev information for the Cypress/Melfas key controller, and possibly the Atmel mXT224 and looking for other devices that use it (Motorola Atrix, for example). If I can disable the "LED on when touched" behavior, things are a lot easier.
i was wondering about this as well... my back button, is messed up and has no sensitivity at all so im trying to disable the whole bar and just use an onscreen nav bar. i know that paranoid as it in their settings but that rom eats up the battery like a mad man ill be down to zero by noon i dont get that problem with CM9 BUT CM9 doesnt have the onscreen Nav Bar
does any one know where i can find more info on adding this nav bar to CM9?
Aokp has it too
V1R3Z said:
my back button, is messed up and has no sensitivity at all
Click to expand...
Click to collapse
You might try Hefe Kernel Of Darkness (second post in that thread) to mainly turn off the touchkey backlight.
I'm curious as to what poor back-button sensitivity problems you are seeing. You can PM to keep the thread clean.
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
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