How to add soft/virtual keys to tablet? - Samsung Galaxy Tab A series Questions & Answers

I've tried adding the build.prop in the system folder, but I can't get it to work even after a reboot. Any suggestions? I tried using the soft buttons app to add it for me, but no luck there either. I also don't want to use an app through accessibility if possible.

Related

[GUIDE] remap capacitive buttons

I know a lot of people out there are doing this already, but it didn't seem like there was a guide or anything out there for the NS. So, here we go.
(Please, make sure you know what you're doing BEFORE you apply this modification. I can't be responsible if you somehow manage to brick, or make brick-like your phone while following this guide.)
-You can do this using either adb, Terminal, or apps like Root Explorer. Since I'm trying to make this as easy as possible, I'll explain how to do this using the "File Manager" app, which can be installed via Market for FREE.
First, you need a rooted phone. If your phone is not rooted, there is extensive existing literature on how to get this done. (It's awfully easy on our Nexus S )
Run File Manager, hit Menu > More > Settings, scroll way~~ down, and make sure that "Root Explorer" and "Mount System Folders" are checked.
Navigate your way to
/system/usr/keylayout
(you'll have to move Up a step or two to find 'system' folder at root level.)
[BACKUP THE ORIGNIAL FILE WE'RE ABOUT TO MODIFY]
Long-press the file 'cypress-touchkey.kl'
Select 'Copy'
Hit 'Paste', on the upper left corner of app.
You'll be asked to rename the file. Rename it to something reasonable. (like, cypress-touchkey.kl.bakup)
Hit 'Ok'
Make sure the file you just created exists.
[START MODIFICATION]
Long-press 'cypress-touchkey.kl' (again)
Hit 'Permissions'
Make sure that ALL THREE boxed under "Write" are checked, and hit OK.
Hit 'cypress-touchkey.kl' (yet, again)
Select Text > Text Editor
Here, you'll see something like,
Code:
key 139 MENU VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 217 SEARCH VIRTUAL
as you've guessed, the first part,
Code:
key ###
is telling which key this command (event) is for.
So we can intuitively tell that the number for our capacitive 'Back' button is probably 158.
the next section, 'MENU, HOME, BACK, SEARCH' tells Android what these buttons should actually do.
And a pretty good list of what an Android CAN do on a key-press is listed here: http://goo.gl/vrCvJ
From the list, lookup anything that starts with KEYCODE_ and you'll find a pretty good description of what that command ('event') makes Android do.
Just add this keycode, WITHOUT the KEYCODE_ part of the code, to where the current cypress-touchkey.kl reads 'MENU, HOME, BACK, SEARCH' (according to what you want which button to do, that is)
So, for example, I've remapped my 'Search' button to bring up the App Switcher (Recent Apps). (Long-pressing the Home button just didn't cut it for me )
So, my 'cypress-touchkey.kl' looks like this:
Code:
key 139 MENU VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 217 APP_SWITCH VIRTUAL
Now, save your modified 'cypress-touchkey.kl' by selecting,
Menu > Save, and the exit by selecting Menu > Exit.
To be safe, let's set the permissions back to what they were.
From the File Manager App, long-press 'cypress-touchkey.kl' > Permissions,
and un-check the lower two check-boxes under the 'Write' column, and hit "OK"
Now, reboot your phone, and see if all went well
I actually tried this mod on a ICS rom, expecting the ICS app switcher to pop up, but somehow, the APP_SWITCH event seems to bring out the GB Recent App thingy.
Functionally, it still works pretty well for me. But if there's anyone out there who has any information on how to bring out the all-new ICS App switcher with a key-event, I'd really appreciate it
Hope this makes someone's life easier!
Thanks for the post.
I've tried to remap my search key as you described, but the APP_SWITCH command doesn't seem to work? Nothing happens for me. When I switch the value back to "search" that command works again, so I know the have edited the file correctly.
Any ideas? Does the kernel/rom affect this? I'm running oxygen + franco kernel.
Thanks!
Edit: Spelling.
Thanks for this, will definitely try out soon!
Follow the leader @corythug
Any idea what the app switch command is on ICS
Sent from my Nexus S 4G using xda premium
The ICS app-switch is, in my opinion, the best way to use search button key on Nexus S with ICS rom.
Hope someone will be able to find the correct command ot for that and someother creates a flashable zip to do the mod easily from recovery
Is there any way to remap the longpress on capacitive buttons?
Sent from my Google Nexus S using XDA App
cahir_cz said:
Is there any way to remap the longpress on capacitive buttons?
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
That's what were trying to figure out
Sent from my Nexus S 4G using xda premium
Thanks for the guide, I'll try it soon. My last few phones were from HTC and I love (or rather am so accustomed to) their button layout.
Sent from my Nexus S 4G using XDA App
Zorrich said:
Thanks for the post.
I've tried to remap my search key as you described, but the APP_SWITCH command doesn't seem to work? Nothing happens for me. When I switch the value back to "search" that command works again, so I know the have edited the file correctly.
Any ideas? Does the kernel/rom affect this? I'm running oxygen + franco kernel.
Thanks!
Edit: Spelling.
Click to expand...
Click to collapse
I don't think neither rom nor kernel should affect how this trick works ... unless maybe the rom dev. explicitly made changes to how the key events work ... which is highly unlikely ;;;;
are you sure you changed ONLY the key-event part? (HOME, BACK, etc.)
you shouldn't change the number that comes after the 'key' part of the script.
... I can't seem to think of any other reason this wouldn't work for you. :'(
Tried this, doesnt work on my kellmsking miui 2.8.1 with francos kernel :/ Changing the file does not change the button behaviour
olorin86 said:
I don't think neither rom nor kernel should affect how this trick works ... unless maybe the rom dev. explicitly made changes to how the key events work ... which is highly unlikely ;;;;
are you sure you changed ONLY the key-event part? (HOME, BACK, etc.)
you shouldn't change the number that comes after the 'key' part of the script.
... I can't seem to think of any other reason this wouldn't work for you. :'(
Click to expand...
Click to collapse
Yes, I've only changed the key-event to APP_SWITCH. Actually, I even tried copy/pasting your code into the file, still didn't work.
Thanks anyways. At least I now know how to do it, just have to figure out why it doesn't work, haha.
When using this the old recent apps comr up, meh.
Sent from my Nexus S using Tapatalk
we need to find the correct keyword for triggering the new ics app switch and it will be great
Anyone got a configuration to recommend to complement the ICS on screen buttons?
brrip said:
Anyone got a configuration to recommend to complement the ICS on screen buttons?
Click to expand...
Click to collapse
I tried logcat to see what happens when it's brought up but i'm not a dev, I know some code buy don't have a computer to try and implement for testing
Sent from my Nexus S 4G using xda premium
I tried alogcat from the market. It didn't show anything of worth after a key press.
Sent from my Nexus S 4G using xda premium
any news about that?
provolinoo said:
any news about that?
Click to expand...
Click to collapse
+1!!!
Sent from my Nexus S
Would be pretty sweet idd
Greenthy said:
Would be pretty sweet idd
Click to expand...
Click to collapse
Agreed, would love to get this working on ICS.

Hide soft keys on rooted stock

Hello,
Installed LMT Launcher and played with it briefly last night.
Seems to work well.
I'd like to know if it is possible to remove the soft keys on a stock ROM (rooted with busybox)
Thanks,
~Eric
Hi. I also tried LMT and loved it so much that I simply removed the navbar. Sometimes it would be more practical to have the navbar, but I'm getting more and more used to LMT and in time I feel I will never miss navbar again! I was looking and found some APKs that do this and also a MOD I beleive, but by FAR the easisest solution for me was to simply edit the build.prop file.
So, before you do this make SURE you have alternative way to navigate (such as LMT). Then simply open your build.prop file and add this line:
Code:
qemu.hw.mainkeys=1
Save, reboot and... Profit!
Navbar will be GONE. Cheers:good:
Thanks a bunch... This worked great. Would love to not have to reboot to take effect but still good that you can do this on the stock ROM.
Meeks a huge difference in landscape mode.
Sent from my Nexus 7 using xda app-developers app
tipsek said:
Hi. I also tried LMT and loved it so much that I simply removed the navbar. Sometimes it would be more practical to have the navbar, but I'm getting more and more used to LMT and in time I feel I will never miss navbar again! I was looking and found some APKs that do this and also a MOD I beleive, but by FAR the easisest solution for me was to simply edit the build.prop file.
So, before you do this make SURE you have alternative way to navigate (such as LMT). Then simply open your build.prop file and add this line:
Code:
qemu.hw.mainkeys=1
Save, reboot and... Profit!
Navbar will be GONE. Cheers:good:
Click to expand...
Click to collapse
hi how to execute that code and what app do i need?
You can now hide soft keys (and keep notification bar) without modifications and reboots. Just try my new app:
GMD Hide Soft Keys
It also adds Quick NavBar - soft keys that can be opened with simple swipe from bottom and then autohide when not needed :good:.
StupidIdea said:
You can now hide soft keys (and keep notification bar) without modifications and reboots. Just try my new app:
GMD Hide Soft Keys
It also adds Quick NavBar - soft keys that can be opened with simple swipe from bottom and then autohide when not needed :good:.
Click to expand...
Click to collapse
I Tried your app, but theres a huge red line on the bottom of the screen, so bad.
And also got a lot of errors messages on my logcat in the background, so i uninstalled it quickly oO

Hiding Nav soft keys without an application ?

Does anyone know how could I use a build prop edit to safely hide the bottom navigation bar without using unnecessary RAM? I use LMT so it isn't necessary.
I believe its in the build . prop file because when I replaced it to do a status bar mod, the bar disappeared momentarily when the file was missing.
However, I'm new to Android and I don't want to put myself into a boot loop or worse by blindly deleting things. I don't even know how to use a recovery yet. So does anyone know where this is? Thanks
LG G2
I just use an app. Auto hide soft keys. It's in the play store. Also use LMT myself. Let me ask you something, what setting do you set gesture input to?
Sent from my LG-D800 using xda app-developers app
chiballer20 said:
I just use an app. Auto hide soft keys. It's in the play store. Also use LMT myself. Let me ask you something, what setting do you set gesture input to?
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I find that app kind of bugging, and there are moments when my buttons are no longer being displayed and I have to reboot to get them back.
Sent from my LG-D801 using xda app-developers app
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
wy2sl0 said:
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
Click to expand...
Click to collapse
That is what do do with all of my phone using LMT, and not barely crash, I've had one during this year and s restart made it normal.
Sent from my LG-D801 using Tapatalk now Free
wy2sl0 said:
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
Click to expand...
Click to collapse
Thanks, i'll try it.. hopefully it will free up a good amount of RAM :fingers-crossed:
IamPro said:
Thanks, i'll try it.. hopefully it will free up a good amount of RAM :fingers-crossed:
Click to expand...
Click to collapse
sry for the stupid question....what is LMT?
energie said:
sry for the stupid question....what is LMT?
Click to expand...
Click to collapse
Gesture based launcher:
http://forum.xda-developers.com/showthread.php?t=1330150
wy2sl0 said:
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
Click to expand...
Click to collapse
IamPro said:
Thanks, i'll try it.. hopefully it will free up a good amount of RAM :fingers-crossed:
Click to expand...
Click to collapse
Softbricked my phone and had to restore to stock then re-root etc :crying:
what is LMT?
This is LMT, or one of its functions. Its a really customizable navigation bar that replaces the stock one, along with any of other gesture control you could think of. Its great, you should try it out
LG G2
It swipes in from the bottom, top or sides. You can hold the gesture and lift your finger on the button or just swipe through in the direction you want and the function will activate. It gets much more complex than my setup but I'm just keeping it simple for now
LG G2
IamPro said:
Softbricked my phone and had to restore to stock then re-root etc :crying:
Click to expand...
Click to collapse
Sorry, you softbricked after inserting the string in build.prop? I'm interested to this mod (hiding soft keys and activate LMT)
nimo182 said:
Sorry, you softbricked after inserting the string in build.prop? I'm interested to this mod (hiding soft keys and activate LMT)
Click to expand...
Click to collapse
Yea, maybe I did something wrong.. idk
Its pretty easy to get back to stock so not huge deal tho
wy2sl0 said:
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
Click to expand...
Click to collapse
How did you do this safely? Many people have been getting it wrong and I'd like to get it right the first time lol
LG G2
I have no idea.
Downloaded build.prop editor from the play store
go to VERY BOTTOM of build.prop
make a new blank line
enter what I said
save
...profit
The best app to hide soft keys is UDN (ultimate dynamic navbar),it can hide your keys without the need to modify them in build prop....And replace them with its soft keys that are not only customisable but you can also make them as tiny as you want in order not ot occupy as much space...
woof123 said:
The best app to hide soft keys is UDN (ultimate dynamic navbar),it can hide your keys without the need to modify them in build prop....And replace them with its soft keys that are not only customisable but you can also make them as tiny as you want in order not ot occupy as much space...
Click to expand...
Click to collapse
woof i tried UDN, to hide nav bar it requires xposed with it's module..i'm not too much interested to install other sw indeed, and IMHO it's the same of autohide
Then the build.prop string qemu.hw..... works??
nimo182 said:
woof i tried UDN, to hide nav bar it requires xposed with it's module..i'm not too much interested to install other sw indeed, and IMHO it's the same of autohide
Then the build.prop string qemu.hw..... works??
Click to expand...
Click to collapse
It worked for me.Without xposed,i just ticked the option in the settings.Also you can make the keys as tiny as you want,even if you want them visible all the time and not hidden it will help alot to make them tiny.
nimo182 said:
woof i tried UDN, to hide nav bar it requires xposed with it's module..i'm not too much interested to install other sw indeed, and IMHO it's the same of autohide
Then the build.prop string qemu.hw..... works??
Click to expand...
Click to collapse
can't make it working....it adds another bar above the stock one

Hide nav bar root required

Sideload and install gmd hide soft keys run it and select hide soft keys keys and setup your quick nav bar ..my suggestion is to use the pro version of gmd and set navigation control's to none and then use udn pro as your navbar which seems to work better for me
Sent from my KFAPWI using XDA Premium 4 mobile app
Works great, but how do you get the new nav bar to push everything up when on the bottom? Right now I have it set to 20px so it doesn't interfere with much, but it conflicts with my keyboard from time to time...
Sent from my KFTHWI using Tapatalk 4
Did you guys lose menu buttons on some apps after installing these? My menu buttons for Voice and Trillian for instance have vanished and the menu button for the bar doesn't work on most apps for me.
Edit: Never mind, my issue was related to a busybox installation that was fixed by installing with a different installer. Oops.
Thanks for the info on this, it's very useful and stock is kinda lackluster.
aimlessanomaly said:
Did you guys lose menu buttons on some apps after installing these? My menu buttons for Voice and Trillian for instance have vanished and the menu button for the bar doesn't work on most apps for me.
Edit: Never mind, my issue was related to a busybox installation that was fixed by installing with a different installer. Oops.
Thanks for the info on this, it's very useful and stock is kinda lackluster.
Click to expand...
Click to collapse
I just got the same problem.
You mean that re-install the busybox will solve this?
911sakura said:
I just got the same problem.
You mean that re-install the busybox will solve this?
Click to expand...
Click to collapse
I reinstalled with a different installer from the play store and it worked for me.
aimlessanomaly said:
I reinstalled with a different installer from the play store and it worked for me.
Click to expand...
Click to collapse
I tried many kinds of installers but all failed, could you tell me which one you used?
Sent from my KFTHWI using xda app-developers app
911sakura said:
I tried many kinds of installers but all failed, could you tell me which one you used?
Sent from my KFTHWI using xda app-developers app
Click to expand...
Click to collapse
I used the one from Faznx92's root tutorials, but I never had a busybox problem...
Something weird is going on, I got the menu problem again after rebooting I guess. Every time I uninstall busybox I get them back. I'll try the method OP used.
Edit: I keep getting the same problem. Each time I enable the auto hide soft keys app, I lose menu buttons in apps. Thr trick I found is to launch them all after booting then enable the auto hide. Just need to do that every time you reboot.
I would still love to be able to fix it for good
Freeze or uninstall stock "Soft Key Bar?"
Is it possible to remove it completly? I use auto hide soft keys but the stock Soft Key Bar interferes with it.
Atise said:
Is it possible to remove it completly? I use auto hide soft keys but the stock Soft Key Bar interferes with it.
Click to expand...
Click to collapse
This
Do you guys know any way of swapping the default navbar with an aosp navbar? I want it to stay without hiding. I am mainly missing the recent apps button in the default navbar.
Thanks a lot!
You can disable the navbar with gravity box and use pie controls. That's what I do
Use UDN lite. Its far better and has more customization in the free version.
Sent from my KFSOWI using Tapatalk
clear-all button in recent app
thx. btw, gravity box brings back the clear-all btn in recent app list.
peter_b93 said:
Do you guys know any way of swapping the default navbar with an aosp navbar? I want it to stay without hiding. I am mainly missing the recent apps button in the default navbar.
Thanks a lot!
Click to expand...
Click to collapse
I am wondering the same thing, also the clear all button in the recent apps.

"Virtual button" / On-screen buttons?

Has anyone figured out how to turn on on-screen buttons instead of using the capacitive/physical buttons? In the control center, there's option to turn on "virtual button" and it allows you to disable the capacitive/physical buttons, but nothing shows up on the screen.
It's under accessibility
LeEco Pro3
toanau said:
It's under accessibility
LeEco Pro3
Click to expand...
Click to collapse
That only allows you to disable the hard buttons though, doesn't enable soft ones (on screen nav buttons). There's a way to enable them by default editing the build.prop but people were saying it didn't work on emui for some reason. One guy said it works fine, so I don't know. Requires root too though. No root in sight for US variants so far.
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
4K2K said:
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
Click to expand...
Click to collapse
Are you rooted? Do you have the US model?
Sent from my SM-P600 using XDA-Developers mobile app
toanau said:
Are you rooted? Do you have the US model?
Sent from my SM-P600 using XDA-Developers mobile app
Click to expand...
Click to collapse
I can answer for him lol. Yes, hes rooted, otherwise it wouldnt be possible, and no, because us model cant be rooted atm
4K2K said:
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
Click to expand...
Click to collapse
Please remember, I'd like to extend the button backlight time
Klara Kaiser said:
Please remember, I'd like to extend the button backlight time
Click to expand...
Click to collapse
If I understood that correctly, then you don't need to use softkeys. After the latest update, if you go to accessibility, there is an option for enabling the button backlight as long as the phone screen is on. I attached a picture clearly showing the option if it might help.
p_pal2000 said:
If I understood that correctly, then you don't need to use softkeys. After the latest update, if you go to accessibility, there is an option for enabling the button backlight as long as the phone screen is on. I attached a picture clearly showing the option if it might help.
Click to expand...
Click to collapse
Was exactly what I'm looking for, but I haven't this setting option. Are you at 5.8.0.19S? I'm still on 18S.
So I have to wait
Yep I'm on 19S. I thought all US models had gotten the update, but I forgot that this phone came out in other countries previously ( -_- ). So I suppose you just have to wait a few more days/weeks and hopefully you get the update.
4K2K said:
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
Click to expand...
Click to collapse
DANG...WORK FOR ME, US VERSION CONVERTED TO CHINESE AND whammmmm.:good:
THANKS A LOT.
johnkchiu said:
Has anyone figured out how to turn on on-screen buttons instead of using the capacitive/physical buttons? In the control center, there's option to turn on "virtual button" and it allows you to disable the capacitive/physical buttons, but nothing shows up on the screen.
Click to expand...
Click to collapse
Like this?
Install SimpleControl
OR you can Flash CM13 rom they have option for on screen navigation key and disable the hardware one, or you can keep the hardware as stock rom.
This rom I was using it I found it best CM13 rom by far: CM13 LEX720 by Team Superluminal
Nova Launcher also can show the software buttons
Tonnex said:
Nova Launcher also can show the software buttons
Click to expand...
Click to collapse
Where is the option in Nova Launcher? I can't find it.
4K2K said:
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
Click to expand...
Click to collapse
so far this worked, did you remember what file the backlight keys are controlled by?
Klara Kaiser said:
Please remember, I'd like to extend the button backlight time
Click to expand...
Click to collapse
There isn't a file. He said "he cant remember" because he is lying
The backlight controls are driven by two files in /sys/class/leds/button-backlight. Files in the /sys folder are pseudo files created at runtime from the kernal. You would need to mod the kernal to permanently turn the lights off.

Categories

Resources