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?
Related
Hi, all.
Not sure if this has been covered, trust me I've searched, but can I disable the wake on home button function? I've rooted, and tried various options that have been posted for earlier versions, but alas the S5 still wakes up when I press the home key.
Hate it, as I've pocket dialled the missus a few times already!
nicks75 said:
Hi, all.
Not sure if this has been covered, trust me I've searched, but can I disable the wake on home button function? I've rooted, and tried various options that have been posted for earlier versions, but alas the S5 still wakes up when I press the home key.
Hate it, as I've pocket dialled the missus a few times already!
Click to expand...
Click to collapse
Look into the 'Xposed' framework installer and then Wanam Xposed module (if your ROM supports it?). There's a tweak in Wanam's module to turn off the wake on home.
I've only just started using this myself with Omega v1.9 ROM (which has it built in if you pick it in the Aroma installer when flashing the ROM), so can't really tell you more than that... It's like being able to edit bits of the ROM but using a simple GUI instead of having to get into the code yourself.
Hope that helps!
Bisonator said:
Look into the 'Xposed' framework installer and then Wanam Xposed module (if your ROM supports it?). There's a tweak in Wanam's module to turn off the wake on home.
I've only just started using this myself with Omega v1.9 ROM (which has it built in if you pick it in the Aroma installer when flashing the ROM), so can't really tell you more than that... It's like being able to edit bits of the ROM but using a simple GUI instead of having to get into the code yourself.
Hope that helps!
Click to expand...
Click to collapse
Thanks for your reply, but I've already tried that. Also tried editing gpio-keys.kl and removing WAKE_DROPPED from key 172. Still no luck.
nicks75 said:
Thanks for your reply, but I've already tried that. Also tried editing gpio-keys.kl and removing WAKE_DROPPED from key 172. Still no luck.
Click to expand...
Click to collapse
Apologies if you do already know what you're doing with this (I didn't!), but this might help to get it working:
Do you know that you have to enable/install the framework and then enable the Wanam module all from within the 'Xposed installer' first?
I didn't and expected mods to work immediately having edited the settings in 'Wanam Xposed' but found I hadn't yet installed the framework or enabled the module!
There are some other tweaks in Wanam Xposed that I found didn't work (quite right/at all) with Omega v1.9, so not all options are supported on this ROM.
Bisonator said:
Apologies if you do already know what you're doing with this (I didn't!), but this might help to get it working:
Do you know that you have to enable/install the framework and then enable the Wanam module all from within the 'Xposed installer' first?
I didn't and expected mods to work immediately having edited the settings in 'Wanam Xposed' but found I hadn't yet installed the framework or enabled the module!
There are some other tweaks in Wanam Xposed that I found didn't work (quite right/at all) with Omega v1.9, so not all options are supported on this ROM.
Click to expand...
Click to collapse
OH....MY....GOD!!
Thankyou so much, that seems to have worked PERFECTLY!
deleted
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!
I have searched for these features without success not even for KK.
I try to find out how i can add move text cursor with volume buttons and adjust brightness with the notification bar as CM has but i want it on lollipop? Is it to early?
I know these features exist in gravitybox but it isn't sure if xposed will be released to ART/lollipop.
I loaded factory image and rooted, but don't want to flash CM12 just to get these two features.
Now for the question, is there any way to flash these features in recovery or do they need to be compiled within the rom?
Thanks in advance!
Still no change to this as it seems.
My Omni ROM doesn't support the Volume/curosr feature either.
GravityBox for LP does exist, although Xposed is still an alpha.
http://repo.xposed.info/module/com.ceco.lollipop.gravitybox
My new app Cursor Control lets you use the volume keys to easily move the cursor in text fields and works without Root.
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.
Any way to enable the onscreen navbar on Nougat?
I used Root Browser to edit the build.prop to change the 0 at the end of this to 1 and back again
qemu.hw.mainkeys=1
Click to expand...
Click to collapse
But had no luck after reboot either way.
Any way to enable them?
It didn't work in MM because ZTE took the on screen buttons out of the framework, rather than just from the build.prop line.
I'm guessing they did the same thing in N.
needs more than just build.prop to enable on-screen key......i'll be releasing Dmix7_N (Stock Base) but on-screen keys will be disabled by default via build.prop and re-enable via build.prop
That's odd cause when I went from lineage back to stock the nav bar followed. Full wipe, full stock zip.
I have on screen working but capacitive buttons still work as well. Does anyone know of a way to turn capacitive buttons completely off and only use on screen?
t2jbird said:
I have on screen working but capacitive buttons still work as well. Does anyone know of a way to turn capacitive buttons completely off and only use on screen?
Click to expand...
Click to collapse
Button mapper.
My stock Rooted B15 Nougat version just has an option to activate on-screen Navbar...
Setings->Features->Navigation Keys.
Is that what you meant?
iNaruX said:
My stock Rooted B15 Nougat version just has an option to activate on-screen Navbar...
Setings->Features->Navigation Keys.
Is that what you meant?
Click to expand...
Click to collapse
That's really weird, mine didn't have that? Only thing I had under "Navigation Keys" was the ability to swap them but not display them on screen?
I did, however, flash the vR26 Permissive kernel, and that automatically enabled the onscreen buttons......It also made Nougat much smoother
I'm running the B15 from DrakenFX.
Here's a screenshot from that setting.
http://i.imgur.com/3RvqIlY.jpg
DrakenFX said:
needs more than just build.prop to enable on-screen key......i'll be releasing Dmix7_N (Stock Base) but on-screen keys will be disabled by default via build.prop and re-enable via build.prop
Click to expand...
Click to collapse
you keep promise that... I'm still waiting on your ROM
iNaruX said:
I'm running the B15 from DrakenFX.
Here's a screenshot from that setting.
http://i.imgur.com/3RvqIlY.jpg
Click to expand...
Click to collapse
Been meaning to reply to this with a screenshot from "stock rooted".. There is no option to "Always show navigation bar" in stock. Not sure if DrakenFX added that, or what?
I do know the Beast Mode Permissive kernel will enable them, and I used it for a couple weeks, but while that kernel is really smooth and I had my on-screen navbar.... My battery took a fairly huge hit, and my stock camera didn't work. So I reverted back to pure, rooted, stock.
Bumping. I want to go back to the latest stock but I won't do it without onscreen nav buttons.
p4ch1nk0 said:
Bumping. I want to go back to the latest stock but I won't do it without onscreen nav buttons.
Click to expand...
Click to collapse
Fairly easy.
When rooted open build.prop (system/)
Change ro.config.navkeys=1 to 0 (ZTE kept it by default to 1 so you don't see the setting)
Leave qemu.hw.mainkeys=0 like it is
Save, restart and you'll have your enabled nav bar on stock devices.
Btw, you can disable it through settings so you can, if you want, swype down to not see it anymore.
raystef66 said:
Fairly easy.
When rooted open build.prop (system/)
Change ro.config.navkeys=1 to 0 (ZTE kept it by default to 1 so you don't see the setting)
Leave qemu.hw.mainkeys=0 like it is
Save, restart and you'll have your enabled nav bar on stock devices.
Btw, you can disable it through settings so you can, if you want, swype down to not see it anymore.
Click to expand...
Click to collapse
I changed the ro.config.navkeys=0 and i still haven't seen the on screen nav bar
nmk_123 said:
I changed the ro.config.navkeys=0 and i still haven't seen the on screen nav bar
Click to expand...
Click to collapse
First do check in settings/features/navigation keys/check always ON wether it works (you can disable it afterwards by putting it on "OFF" and have the possibility to swype up or down afterwards)
Second, try swype upwards from the bottom to see the navbar.
Check also if qemu.hw.mainkeys=0 is still 0.
It should work because these are simple build.prop scripts, so test out :good:
raystef66 said:
First do check in settings/features/navigation keys/check always ON wether it works (you can disable it afterwards by putting it on "OFF" and have the possibility to swype up or down afterwards)
Second, try swype upwards from the bottom to see the navbar.
Check also if qemu.hw.mainkeys=0 is still 0.
It should work because these are simple build.prop scripts, so test out :good:
Click to expand...
Click to collapse
Thanks, I double checked qemu.hw.mainkeys=0 is still 0.
Navigation menu doesn't have any new option.
Tried to swipe up and down as well, nothing
nmk_123 said:
Thanks, I double checked qemu.hw.mainkeys=0 is still 0.
Navigation menu doesn't have any new option.
Tried to swipe up and down as well, nothing
Click to expand...
Click to collapse
OK. Lets try to figure it out.
Have you rebooted phone ?
Have you a G version ?
Can you upload me your build.prop pls. I'll take a look on it.
raystef66 said:
OK. Lets try to figure it out.
Have you rebooted phone ?
Have you a G version ?
Can you upload me your build.prop pls. I'll take a look on it.
Click to expand...
Click to collapse
Thanks for trying to figure this out with me. I really appreciate it.
I have a U version but I'm actually using your [ROM][AROMA][A2017G][B08 7.1.1.][stock] SL!M³ DF!NR. I'm tempting to checkout ur [ROM][AROMA][A2017][V2.0.0B13 M!Favor 5.0 / 7.1.1.][stock] SL!M DF!NR to see if it makes any difference.
This is my build.prop
https:// drive . google . com/file/d/1pyEZtZxVONEiinIc9pNnv35VPwyno6Ij/view?usp=sharing
Sorry im not allowed to post outside links yet so have to do this
nmk_123 said:
Thanks for trying to figure this out with me. I really appreciate it.
I have a U version but I'm actually using your [ROM][AROMA][A2017G][B08 7.1.1.][stock] SL!M³ DF!NR. I'm attempting to checkout ur [ROM][AROMA][A2017][V2.0.0B13 M!Favor 5.0 / 7.1.1.][stock] SL!M DF!NR to see if it makes any difference.
This is my build.prop
https:// drive . google . com/file/d/1pyEZtZxVONEiinIc9pNnv35VPwyno6Ij/view?usp=sharing
Sorry im not allowed to post outside links yet so have to do this
Click to expand...
Click to collapse
No problem. We're here to help each other out :good:
I'll give a look at your build.prop later on.
But do try the Mifavor 5.0. As I'm not mistaken, the option is built in too. So nothing to change there. And this rom is quite smooth, fast and without force closes. Perhaps try it and let me know.
Tomorrow I'll take a look at your file.
nmk_123 said:
Thanks for trying to figure this out with me. I really appreciate it.
I have a U version but I'm actually using your [ROM][AROMA][A2017G][B08 7.1.1.][stock] SL!M³ DF!NR. I'm tempting to checkout ur [ROM][AROMA][A2017][V2.0.0B13 M!Favor 5.0 / 7.1.1.][stock] SL!M DF!NR to see if it makes any difference.
This is my build.prop
https:// drive . google . com/file/d/1pyEZtZxVONEiinIc9pNnv35VPwyno6Ij/view?usp=sharing
Sorry im not allowed to post outside links yet so have to do this
Click to expand...
Click to collapse
Looked into your build.prop and all should be ok. And since you installed the SLIM³ all files such as framework-res.apk and systemui.apk are overwritten in case the U models files could have been different. But as said, with all these files and your build.prop the nav bar should show up....
So for the moment i do not see an immediate solution for that matter.
As said and afaik , the Mifavor 5.0 from my rom has this nav bar build in