Hello,
My S5 got damaged and the HW bottom keys stopped working (only the center button with fingerprint works). Is there any good rom with default SW keys enabled? i have tried to install several roms but all have only hw keys and editing properties file to enable SW keys doesn't worked for me.
Asop Extended has soft keys and is pretty good
kjubu said:
Hello,
My S5 got damaged and the HW bottom keys stopped working (only the center button with fingerprint works). Is there any good rom with default SW keys enabled? i have tried to install several roms but all have only hw keys and editing properties file to enable SW keys doesn't worked for me.
Click to expand...
Click to collapse
You will find the option to enable sw keys in settings then extensions then buttons
kjubu said:
Hello,
My S5 got damaged and the HW bottom keys stopped working (only the center button with fingerprint works). Is there any good rom with default SW keys enabled? i have tried to install several roms but all have only hw keys and editing properties file to enable SW keys doesn't worked for me.
Click to expand...
Click to collapse
I can confirm that you can enable software navigation keys by editing the build.prop in lineageos 15.1
Just add the following line to the end of the build.prop
qemu.hw.mainkeys=0
Related
hello everyone, I would like to know how to configure the hardware keys in Gpe / AOSP / AOKP ROMs to only turn on when pressed and not all the time, for example, when the screen is touched. I have found ways to completely disable, but not exactly what I'm looking for.
biazoto said:
hello everyone, I would like to know how to configure the hardware keys in Gpe / AOSP / AOKP ROMs to only turn on when pressed and not all the time, for example, when the screen is touched. I have found ways to completely disable, but not exactly what I'm looking for.
Click to expand...
Click to collapse
Try it with the xPosed Moduls from here: http://repo.xposed.info/module/de.robv.android.xposed.installer
Than install the Modul GravityBox
Tkkg1994 said:
Try it with the xPosed Moduls from here: http://repo.xposed.info/module/de.robv.android.xposed.installer
Than install the Modul GravityBox
Click to expand...
Click to collapse
I already have installed Xposed and use several modules, including gravitybox, but what I seek is a way to configure them so that only light up when they are pressed, as is by default the official ROMs tw and some GPE like the kangakat. in all ROMs I have tested in recent days, by touching the screen, the buttons light up and not thought it was cool. In tested ROMs, as well as in gravitybox, there is only the option to permanently disable the lights of the buttons and that is not what I seek. maybe there is some file or script that can be changed to that setting?
Hey guys,
There have been a ton of people asking how to activate onscreen buttons and disable the capacitive buttons since CM12 builds have started rolling out. Obviously, at some point, these features will be rolled into the ROM, but until then, I figured it would be a good idea to simply present a step-by-step thread on the issue. There have been answers all over the place button nothing dedicated and centralized, so I figured I would help some guys out.
Things needed:
CM12 Build on any variety (currently K900 and bpear have "nightlies" available in development. Check em out.
Root access. Just flash SuperSU 2.16 (http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip) if you don't have it. Root is necessary.
Zip to turn of the backlights: http://www.mediafire.com/download/p385se5ia28cqab/noSoftkeyBacklight.zip (thanks @Moody for this)
1.) Activate On-Screen buttons
- Use a program such as BuildProp Editor (look it up on the Play Store) to create a new build.prop entry. Call it qemu.hw.mainkeys, and set it's value to 0. If you are doing this manually, just add the line "qemu.hw.mainkeys=0"
- Reboot.
2.) Deactivate Capacitive buttons
- Download Root Explorer or some other program that allows editing of system level files.
- Mount your system as R/W. In root explorer at least, when you get into the system, there is a button up top to do so.
- Navigate to /system/usr/keylayout. Open Generic.kl in with a text editor.
- Comment out the follow lines by inserting a pound sign (#) in front of the line:
key 158 BACK
key 172 HOME
key 139 MENU
After this, they will read:
# key 158 BACK
# key 172 HOME
# key 139 MENU
Therse are numerically ordered, shouldn't be hard to find within the document.
- Remount your system as R/O.
3.) Turn off the capacitve back lights
- Reboot into custom recovery and flash noSoftKey.zip file you downloaded earlier.
- Reboot.
That should do it! You should now have software buttons and your hardware buttons should seemingly not exist!
Any questions or comments, please leave them here.
Anyone know how to enable hardware home long press to get to Google now?
TjPhysicist said:
Anyone know how to enable hardware home long press to get to Google now?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures&hl=en
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Hi there, first of all, thanks. I am having a problem where after I disabled the capacitive buttons (Step 2) the power and volume buttons are not working. Thanks in advance.
You know how to enable menu key also?
Verstuurd vanaf mijn Nexus 7 met Tapatalk
Yes any chance of getting home button long press as search? Default is the menu button doing this.
Its not working bro
Tried and followed your steps , disabling capacitive keys works but enabling on screen keys not working even after changing build.prop , also i read in some post that enabling on screen key mod will not work in cm roms is that true can any one confirm me?
i am using following rom its CM12
http://forum.xda-developers.com/oneplus-one/development/devrom-cm12-scheduled-builds-t2938372
its very stable didnt experience any glitch till now , multi user and guest account works , all the other features are working too, try it out friends.
Pure awesomeness, many thanks for this guide. I'm back to my comfort zone, onscreen for me is just more intuitive.?
BTW, how to bring back the capacitive lights? I tried to remove the script at /etc/init.d and it only bootloops after reboot.
Edit: Nvm, found it, re-flashing the ROM brings back all to the default behavior including the capacitive backlights.
kmakiki said:
3.) Turn off the capacitve back lights
- Reboot into custom recovery and flash noSoftKey.zip file you downloaded earlier.
- Reboot.
That should do it! You should now have software buttons and your hardware buttons should seemingly not exist!
Any questions or comments, please leave them here.
Click to expand...
Click to collapse
For some reason this step isn't working for me. I tried wiping cache/dalvik and it didn't fix anything
Can anyone give a screenshot of the on-screen buttons?
Is this possible to do in hydrogen OS? I love that rom, but i switch back since there is no option to turn off hardwer keys and enable software key in system?
Sent from my A0001 using Tapatalk
How to add volume button onscreen by editing buid.prop
hey Everyone,
I tried to enable the on screen softkeys by editing the build.prop file to add the following line:
qemu.hw.mainkeys=0
This was suggested in many forums and found to be working, but not on the galaxy s4 i guess. When i reboot my phone after adding this line, the systemUI crashes and the phone is totally unusable.
Have anyone tried to do this, or have you ditched the HW keys and enabled the integrated on-screen softkeys on GS4?
Please let me know how...
Thanks!
Hello there,
As of now, Xposed is still not supported in LOS 14.1 as stated by the person maintaining it in this recent post. Is there a way to make the hardware buttons operate inverted? Right now the left button is "BACK" and the right button is "RECENTS" without any way to change it directly from the settings menu.
I have tried editing the file
Code:
/system/usr/keylayout/Generic.kl
directly from the TWRP terminal using VI, in the following entries:
Code:
key 139 MENU --> key 139 BACK
key 158 BACK --> key 158 MENU
But even after rebooting, the changes didn't happen. I checked the Generic.kl file and the changes persisted but no change whatsoever. Has anyone tried ButtonMapper ?? The pro version allows changing the button mapping but it seems like a temporal solution rather than a permanent, more elegant one.
Thanks for any help provided!
Flogisto said:
Hello there,
As of now, Xposed is still not supported in LOS 14.1 as stated by the person maintaining it in this recent post. Is there a way to make the hardware buttons operate inverted? Right now the left button is "BACK" and the right button is "RECENTS" without any way to change it directly from the settings menu.
I have tried editing the file
Code:
/system/usr/keylayout/Generic.kl
directly from the TWRP terminal using VI, in the following entries:
Code:
key 139 MENU --> key 139 BACK
key 158 BACK --> key 158 MENU
But even after rebooting, the changes didn't happen. I checked the Generic.kl file and the changes persisted but no change whatsoever. Has anyone tried ButtonMapper ?? The pro version allows changing the button mapping but it seems like a temporal solution rather than a permanent, more elegant one.
Thanks for any help provided!
Click to expand...
Click to collapse
The free version allows swapping back and recents. It doesn't require root and is less intrusive than using xposed.
flar2 said:
The free version allows swapping back and recents. It doesn't require root and is less intrusive than using xposed.
Click to expand...
Click to collapse
The free version doesn't allow it. Just wanted to confirm if anyone tried it and does it work properly?
Thanks for the reply!
Flogisto said:
The free version doesn't allow it. Just wanted to confirm if anyone tried it and does it work properly?
Thanks for the reply!
Click to expand...
Click to collapse
You are COMPLETELY wrong, Free version Does allow Swap of the hardware keys
Just toggle when it say " Swap Back and Recents " ,will stick at boot ,but will needs to be reenable when dirty flash a new build. Been using since the first LineageOS build.
DrakenFX said:
You are COMPLETELY wrong, Free version Does allow Swap of the hardware keys
Just toggle when it say " Swap Back and Recents " ,will stick at boot ,but will needs to be reenable when dirty flash a new build. Been using since the first LineageOS build.
Click to expand...
Click to collapse
You are COMPLETELY right, my bad! Thanks for the tip and to @flar2 as well. I completely missed that option. Thanks for your work with LOS 14.1!
DrakenFX said:
You are COMPLETELY wrong, Free version Does allow Swap of the hardware keys
Just toggle when it say " Swap Back and Recents " ,will stick at boot ,but will needs to be reenable when dirty flash a new build. Been using since the first LineageOS build.
Click to expand...
Click to collapse
Just in case, this has been posted, I can confirm it works just fine. POST. The difference is that @XblackdemonX edited the Synpatics.kl file instead of Generic.kl.
Redmi Note 2, Android 5.0.2, MIUI 9.6
Need to enable original soft keys. I`ve managed to edit build.prop (qemu.hw.mainkeys=0) from TWRP terminal and sed command. Keys showed BUT don`t response.
I`ve noticed a new menu option in Settings (can`t be not quite accurate, coz I have a translation enabled) - System and Device -> Advanced -> Buttons and gestures -> Screen buttons -> Change buttons positions. And if I change positions, it changed. But buttons are stil not responding.
Are there any MORE options in build.prop, that blocks it?
UPD:
[How To] Disable Capacitative Keys and Enable Soft Keys
Just in case anyone might find this useful, I've put together the instructions I found whilst trying to do this. Finally I can take photos without accidentally bringing up the Menu or closing the Camera App! First time I've ever posted here, so be kind! This works in CM11 M6 on Samsung Galaxy...
forums.androidcentral.com
I`ve found some article, that point to /system/usr/keylayout/ directory and need to comment key 139 and key 158. But there were no such filename from article. So I`ve just tried to edit Generic.kl and It doesn`t work.