[MOD][HOW-TO] Enable Software Keys - AT&T Samsung Galaxy Note II

I can not take full credit for this, I've gotten help from others and have two threads that have provided tons of information (both will be linked at the bottom of this). Samsung's big selling point for the GN2 was the S-Pen, one big gripe that some had was the fact that you couldn't use the S-Pen to interact with the physical buttons and the question of "why didn't they enable the software buttons the Nexus devices use?" So I searched around and found out how to enable the Software buttons on the GN2.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now I'm still tinkering with the Key values to disable the menu and back buttons and possibly re-map the home button...input on this would be great.
Step One: You must be Rooted to do this
Step Two: Use your favorite File Manager (I used Solid Explorer) to navigate to the build.prop file (sysytem>build.prop)
Step Three: Add the following to the bottom of your build.prop file (without the quotes);
"qemu.hw.mainkeys = 0"
Step Four: Save build.prop file, exit file explorer, and reboot the your phone
Step Five: Enjoy your new software buttons
You can turn off the backlight to the menu and back buttons in Settings>Display>Touch key light duration>Always Off. Again this will not disable the physical buttons, I'm still working to figure out what values need to be changed. I'll post the "known" values in the next post.
source info:
http://forum.xda-developers.com/showthread.php?t=1918166
http://rootzwiki.com/topic/29153-mod-411-jelly-bean-soft-key-mods-with-menu-and-search-stockbb/
For those that want "the bleeding edge" of things (like myself) I suggest giving PIE from ParanoidAndroid a try. Senior Member noname81 has created an app that can be sideloaded to your rooted device and enables the PIE style navbar and can be found HERE. For more on PIE check HERE. Check it out and let us know what you think.

From the info found in the SGS3 thread the values that need to be changed are;
key 172 Home
key 158 Back
key 139 Menu
found in these files;
/system/usr/keylayout/sec_touchkey.kl
/system/usr/keylayout/gpio-keys.kl
/system/usr/keylayout/sec_keys.kl
Now the GN2 does not have all of these files but the key values are the same. Instead we have;
/system/usr/keylayout/Generic.kl
/system/usr/keylayout/gpio-keys.kl
/system/usr/keylayout/qwerty.kl
/system/usr/keylayout/sii9234_rcp.kl
and the values I've found are (grouped as found in the above files);
Generic.kl (Only effected files need to be modified)
key 127 Menu Wake_Dropped (No effect)
key 139 Menu Wake_Dropped (Effect)
key 158 Back Wake_Dropped (Effect)
key 172 Home (Effect)
gpio-keys.kl (This file MUST be edited)
key 172 Home Wake (Effect)
qwerty.kl (This file can be left intact)
key 158 Back Wake_Dropped (No effect)
key 229 Menu Wake_Dropped (No effect)
key 139 Menu Wake_Dropped (No effect)
key 59 Menu Wake_Dropped (No effect)
key 102 Home Wake (No effect)
sii9234_rcp.kl (This file can be left intact)
key 10 Menu Wake_Dropped (No effect)
key 14 Back Wake_Dropped (No effect)
Step One: Disable the physical keys
Step Two: Making a flashable script to edit build.prop and change key values to disable physical keys
Step Three: Get popular key re-map ideas
Step Four: Make additional flashable scripts for popular key re-maps
Now I'm currently at work so disabling the physical keys might take me a little while of playing around but ill keep you posted. As for the flashable script I turn to the community to lend a hand on that, that's still a bit out of my league. Same goes for the key re-map scripts. Enjoy everyone.

I removed the above listed values completely from their respective files and have successfully disabled the physical buttons after a reboot. I'm going to re-input those values in one by one to see what the least amount of edit we need to make this work. I'll edit the second post with my findings.
edit: While testing values it seems something breaks the power/lock and volume buttons...battery pull turns phone off (obviously) and the power button will power on the phone but it won't lock it nor will it bring up the shut down/restart menu...replacing keylayout values and removing build.prop edit fixes those buttons...have to look into it further. Also it seems some modification to the size of the software buttons might have to be made as it overlaps the camera button when the camera is in use, this might be fixed by using an AOSP based ROM like CM10...once I get a port ill check it out.
For now if you want to play around with the software buttons to see what it feels/looks like just modify the build.prop file and turn off the backlight for the physical buttons, they will still work but won't be seen.
Apps that don't play nice with this mod;
Camera
Phone

Please note that the camera app doesn't quite play nicely with this mod. It cuts the buttons in half.

natboy said:
Please note that the camera app doesn't quite play nicely with this mod. It cuts the buttons in half.
Click to expand...
Click to collapse
stated in third post...I'll be going to an unoffical CM10 tomorrow so I can play a little more with this then

natboy said:
Please note that the camera app doesn't quite play nicely with this mod. It cuts the buttons in half.
Click to expand...
Click to collapse
also the phone dialpad/recent call log, and landscape softkeys are really screwy...

ScottRTL said:
also the phone dialpad/recent call log, and landscape softkeys are really screwy...
Click to expand...
Click to collapse
Thanx for that...I think once we get an AOSP ROM like CM that allows for a navbar some of these issues will go away. Haven't had the chance to try that out tho
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

any way to get the software buttons to appear only when the S pen is used?
great mod, but I don't need them out all the time.

jstrayy said:
great mod, but I don't need them out all the time.
Click to expand...
Click to collapse
The point of the mod is to eventually replace the physical buttons and be more like a nexus device
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Can I get some input on layout? How would you like to see the following options arranged?
MENU
RECENT APPS
HOME
BACK
SEARCH
Not all options need to be used. (eg. Recent Apps, Search, Home, Back)

Thanks for your work on this. I personally would love to see :
menu-home-back
I almost never use recent and don't need search, got a widget for that. If power is possible, I'd put it to the left of menu.
Btw, I got a nice (slightly lighter than ICS) blue theme I'm working on for the soft keys.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

Chronzy said:
Thanks for your work on this. I personally would love to see :
menu-home-back
I almost never use recent and don't need search, got a widget for that. If power is possible, I'd put it to the left of menu.
Btw, I got a nice (slightly lighter than ICS) blue theme I'm working on for the soft keys.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Click to expand...
Click to collapse
Cool...thanks for the input...just waiting on a "stable" enough AOSP ROM so I can look at the framework.apk and the navbar options that are baked in to CM.

If anyone figures out how to fix the recent call log please let me know. Having soft keys is amazing. I don't think that I could ever go back.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

-Sn1PeR- said:
If anyone figures out how to fix the recent call log please let me know. Having soft keys is amazing. I don't think that I could ever go back.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Right now I am just using rocketdial... not as good as aosp with softkeys... but pretty decent..
Sent from my Galaxy Note II on Rogers Wireless

Hey monster,
Where are you on this? I would love to have a fully working setup. As far as key layout I use cm10 on my t989 S2 and have the nav bar mimicking the hardware button layout. I however would not want to disable my hardware buttons on my note2 just incase something goes wrong.
Thx
Casperi
Sent from my SGH-T889 using xda premium

casperi said:
Hey monster,
Where are you on this? I would love to have a fully working setup. As far as key layout I use cm10 on my t989 S2 and have the nav bar mimicking the hardware button layout. I however would not want to disable my hardware buttons on my note2 just incase something goes wrong.
Thx
Casperi
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Kind of at a stand still at this point, some family stuff goin on, and im kind of waiting on a CM build so I can tie into the build in navbar settings. Ive been following the dev of cm for us very closely and it seems very close to being something...yay...so ill start looking at their framework.apk and the systemui.apk to see what I can do...then ill most likely build a script based off the s3 script thats already out...and we'll go from there...as far as layout I was kind of thinking menu, home, search, back...but I want to see the menu situation inside CM so menu might go away and it would be search, home, back but we'll see
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Ok thx alot I really appreciate you taking a look at it. I would offer to help but i can't code to save my life. If you need any other type of help like testing or place to host your dev files I can do that.
Take care
Casperi
Sent from my SGH-T989 using xda premium

I have done quite a bit of key re-mapping, including the home button on other devices, and there's usually smali coding involved, as well, so shoot me a pm if you want some info. Can't say I know it all, but more than nothing...
Steve
Sent from my SAMSUNG-SGH-I317 using xda premium

sk806 said:
I have done quite a bit of key re-mapping, including the home button on other devices, and there's usually smali coding involved, as well, so shoot me a pm if you want some info. Can't say I know it all, but more than nothing...
Steve
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanx dude once I get there ill def hit u up
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

ok so some great news...CM10 is "officially" running on the AT&T Note 2 (my phone) and I have gotten the navbar running, also CM has navbar settings/customizations built right in. I am currently looking at a navbar set up in the following manner Menu Home Search Back. If you love AOSP as much as I do and want CM on your phone, heres all you need to get this working:
- http://www.mediafire.com/?a6hl8qlv5v261q1 (the link to Madmack's CM10)
- gapps (optional and you'll have to get them yourself, im using 20121011)
- once you've booted into CM and gotten all your stuff set back up add "qemu.hw.mainkeys = 0" to the bottom of your build.prop file
- save changes and reboot
- you now have the navbar
- to edit go to system settings>system>NAVIGATION BAR (this only shows if you edit your build.prob)
- follow the on screen instructions and you're good to go
I'll try and post a screen shot later as well but I'm having some storage issues at the moment. Otherwise enjoy.

Related

Logitech Android Keyboard + Hacks and Fixes

So, I ordered one of these directly, and stupidly from Logitech and it just arrived yesterday. Stupidly because it has been in stock at Fry's for some time now... (The actual Android version, not iPad one).
Now that the keyboard is in my hot little hands, it is awesome, just pure pure awesome.
I did a couple typing tests on typingtest.com and scored 101wpm without errors (usual typing speed is 110-120wpm on a full-sized ergo keyboard); it could probably be better once I get used to it. (TypingTest.com itself is a pita, because the browser keeps trying to steal focus away from the flash typing test; I found a javascript one that I also scored 101wpm on) Although the UI lagged when typing that quickly. A negative of the keyboard: it might feel a bit too light when typing, but it is completely functional.
So... onto using it in applications... in connectbot none of the necessary keys worked at all, no esc, no tab, no ctrl nor alt. I couldn't stand that, so I wrote up a patch this morning to fix0rs it. I have a pull request open and hopefully it'll be integrated soon. The patch works generically across all keyboards that are compliant to the Android 3.0+ specs. The transformer dock kinda gets gypped here because their keylayout is so stupid (no esc, alt on right, etc).
Speaking of keylayout... that's where my next nits lie, most of the keys are pretty great, they're in the correct location. With a couple exceptions: 1) caps lock is left of a, and ctrl is in the bottom left; 2) the alt and search keys are swapped in position, alt should be adjacent to the space bar, and the search key, like the windows key, should be left of alt; 3) there's no recent apps/task switching button, there is a menu button, but I'll rarely use that.
Given those problems, I hacked up a new keyboard layout that: 1) swaps ctrl and caps lock (but the LED works a litte funky, ok otherwise); 2) swaps the search and alt positions; 3) puts the recentapps action on the menu key.
To install the keyboard layout, do the following:
1) have root on your device
2) unzip LogitechAndroiKeyboard.zip
3) adb push LogitechAndroidKeyboard.kl /sdcard/
4) adb shell
* $ su
* $ mount -o remount,rw /system
* $ cd /system/usr/keylayout
* $ cat /sdcard/LogitechAndroidKeyboard.kl > Vendor_046d_Product_b30a.kl
* $ mount -o remount,ro /system
* $ exit
* $ exit
5) Connect your keyboard and enjoy the new keylayout as described above.
This keylayout can be reverted at any time by removing Vendor_046d_Product_b30a.kl and reconnecting; this is a new file that will be created by following the above steps.
definitely something i will do when my keyboard arrives!
Did you also swap the keys physically? If so, was it hard to do?
Do you think it is possible to somehow to add other letters, like ÆØÅ, instead of hotkeys or any other keys I would find unnecessary? I'm really struggling to find a proper BT keyboard with Scandinavian/ Nordic layout.
paua__ said:
definitely something i will do when my keyboard arrives!
Did you also swap the keys physically? If so, was it hard to do?
Do you think it is possible to somehow to add other letters, like ÆØÅ, instead of hotkeys or any other keys I would find unnecessary? I'm really struggling to find a proper BT keyboard with Scandinavian/ Nordic layout.
Click to expand...
Click to collapse
No, I did not swap the keys physically--I only updated the keyboard layout to work as I wanted.
If you want to change the character mapping like you say, it will probably take a combination of the .kl file I included and editing /system/usr/keychars/Vendor_....same_as_I_said.kcm
I only need a US layout, so I didn't need to tweak any of that.
Cool. SERIOUSLY checking the keyboard now..thanks.
Sorry to ask this, but will this prevent the native keyboard from popping up when you start to type with a bluetooth keyboard?
Mr3G said:
Sorry to ask this, but will this prevent the native keyboard from popping up when you start to type with a bluetooth keyboard?
Click to expand...
Click to collapse
No. It doesn't
pfn said:
No. It doesn't
Click to expand...
Click to collapse
Thanks, its tough when the native keyboard takes up the whole screen.
Mr3G said:
Thanks, its tough when the native keyboard takes up the whole screen.
Click to expand...
Click to collapse
You might consider submitting a bug report(or feature request) to Google to have this fixed in a future version of Android. Probably won't make it into 3.2, but we can hold out hope for implementation in Ice Cream Sandwich. This behavior should at least be configurable.
Thanks for the review of this keyboard. I'm wanting to see how the Samsung Keyboard case turns out (and if it becomes available for a reasonable price from a third party), otherwise I might consider this Logitech keyboard. The bonus for this keyboard is that it would be useful with more than just my tab - on my HTPC for example, which has built in Bluetooth.
Question for you regarding the menu button: Did it work for you?
I have this keyboard and when I press my menu key I was hoping it would bring up the app drawer or something. It does nothing.
A similar samsung keyboard for the 10.1 tablet:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ccapasso said:
Question for you regarding the menu button: Did it work for you?
I have this keyboard and when I press my menu key I was hoping it would bring up the app drawer or something. It does nothing.
Click to expand...
Click to collapse
The menu button serves the same function as the menu button on an android phone--for most honeycomb apps, it'll do nothing (same as in the launcher, nothing) since the menu button doesn't invoke the actionbar. Only pre-honeycomb apps with a menu are activated by the menu button
On my tab, I have MENU set to pop up the recent apps list.
pfn said:
The menu button serves the same function as the menu button on an android phone--for most honeycomb apps, it'll do nothing (same as in the launcher, nothing) since the menu button doesn't invoke the actionbar. Only pre-honeycomb apps with a menu are activated by the menu button
On my tab, I have MENU set to pop up the recent apps list.
Click to expand...
Click to collapse
Can you tell me how to remap the buttons? I want to remap my menu key to do something. Also, the "Calendar shortcut" on the keyboard doesn't launch anything either and I'd like to remap it too.
***Edit***
I see I can open the .kl file in Notepad++ and it shows what the layout is. However, I'm not familiar with the key layout (which number corresponds with which key) nor am I familiar with which command to put to have the menu do something. I assume there is a list I could reference?
wow ....anymore info about this ....?
Akerfeldt said:
A similar samsung keyboard for the 10.1 tablet:
Click to expand...
Click to collapse
rainby said:
wow ....anymore info about this ....?
Click to expand...
Click to collapse
That's this one:
http://www.expansys-usa.com/samsung-bluetooth-keyborad-case-fo-galaxy-tab-10-1-219894/
Edit: Here's some pics:
http://reviews.cnet.com/2300-3126_7-10008260-4.html
ccapasso said:
Can you tell me how to remap the buttons? I want to remap my menu key to do something. Also, the "Calendar shortcut" on the keyboard doesn't launch anything either and I'd like to remap it too.
***Edit***
I see I can open the .kl file in Notepad++ and it shows what the layout is. However, I'm not familiar with the key layout (which number corresponds with which key) nor am I familiar with which command to put to have the menu do something. I assume there is a list I could reference?
Click to expand...
Click to collapse
The .kl file is somewhat self-documenting; simply: look at the key you want to change, in this case, the one that says MENU, and replace it with the action that you want it to do. Look through the .kl files (and any others) and see what actions sound interesting, put that name in there instead of MENU and you're good to go.
pfn said:
The .kl file is somewhat self-documenting; simply: look at the key you want to change, in this case, the one that says MENU, and replace it with the action that you want it to do. Look through the .kl files (and any others) and see what actions sound interesting, put that name in there instead of MENU and you're good to go.
Click to expand...
Click to collapse
Ok, I'll take another look. I did some searching yesterday and there are a variety of .kl files in the folder on my Tab. Any idea which one in particular to edit?
ccapasso said:
Question for you regarding the menu button: Did it work for you?
I have this keyboard and when I press my menu key I was hoping it would bring up the app drawer or something. It does nothing.
Click to expand...
Click to collapse
I'm having an issue with the Home button. My soft keys light up, suggesting that signals are being passed, but the app drawer doesn't open...
Grr!
I bought one of the Logitech Android keyboards from Best Buy last week and ended up returning it. I thought it was too big and heavy to carry around much. I have a Stowaway bluetooth keyboard thats works great with Android so I'll be sticking with that, much easier to tote with me.
esuohe said:
I'm having an issue with the Home button. My soft keys light up, suggesting that signals are being passed, but the app drawer doesn't open...
Grr!
Click to expand...
Click to collapse
The home button is not for opening up the app drawer. It does the same thing as the home soft button...
sweet keyboard
http://imgur.com/a/CPOnY
just wanted to chime in on this keyboard.
its pretty great. i use it for school when i need to take notes.
my only gripe about it is that it weights as much as the tab.
Also, if you use a case that can stand the tab up, such as pyro's or what have you then the extra carrier case that they keyboard comes with cannot be fully utilized. I rate the thing 4-out-5.
there is a new keyboard case thats out (ithink) but its 99 bux, i mean if money is no object get it I think its pretty sweet also.
u can get this keyboard for 30 bux online from Logitech. All you need is a logitech coupon that will give you 50% off.

[Guide] Change the user buttons to home and back

I was looking to change the user configurable buttons on my Desire Z but couldn't find a easy guide or simple solution. I started to experiment a bit. This is what I found out:
To change the layout you only need to things:
1. a rooted phone
2. A program like Root explorer with R/W permissions
Then do the following:
Go to system/usr/keylayout and open the file for the layout you are using in a text editor (in my case this was the WWE version)
I then changed 'user 1' to 'HOME' and 'user 2' to 'BACK'.
I did a soft reset and I now use the user 1 button to go to the home screen and the user 2 button to go back
note: This guide is problably written a 1000 times but I couldn't find it so I hope it's my first real (small) contribution
Grtz
___________
Thanks for the guide! And actually, this method can provide some neat tricks!
For example, I personally never use the search button. So instead, I can change the Search key to USER1 and now the search key is a User-Assignable button!
EDIT: It appears that the Search hardware key and the Search touchkey have different key mapping ID. But the virtual Search touchkey doesn't seem to be listed in keylayout at all. Weird.
There's an app for that
Also, AFAIK it should be possible to remap the capacitive search button.
Sh4d0w940 said:
There's an app for that
Also, AFAIK it should be possible to remap the capacitive search button.
Click to expand...
Click to collapse
The capacitive search button is 217, which is the same as the hardware search button. But my hardware button is doing what I assigned it, while my capacitive one is not doing anything.
It's either not linking, or my phone's capacitive search button is broken.
How can I make the search key to open recent app (the one where u hold home key and come out a recent app)? Thx
Sent from my HTC Vision using XDA
Steven How said:
How can I make the search key to open recent app (the one where u hold home key and come out a recent app)? Thx
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
I think it's a bit more difficult, you should look in Andromadus thread where someone did it, there's a zip to download...
edit: here http://forum.xda-developers.com/showthread.php?t=1516942 the zip is attached, don't know if it works with every rom, surely with andromadus, but we are OT, sorry.
virtualflyer said:
I think it's a bit more difficult, you should look in Andromadus thread where someone did it, there's a zip to download...
edit: here http://forum.xda-developers.com/showthread.php?t=1516942 the zip is attached, don't know if it works with every rom, surely with andromadus, but we are OT, sorry.
Click to expand...
Click to collapse
Well,it send my device to bootlop.. =\
Sent from my HTC Vision using XDA
Why didnt i think about this sooner :O going to try this right now =D

[TUT] Disable capacitive buttons stock Xperia S

1.Make sure you have on-screen buttons enabled i recommend: http://forum.xda-developers.com/showthread.php?t=1940842
2. Download a root file explorer. Root Browser Lite --> http://goo.gl/b9ISW This is what I will use.
3.Load up Root Browser and navigate to system>usr>keylayout. We will be looking for a file called "clearpad.kl".
4. Select it and hit "Open as..." then "Text file" then "RB Text Editor"
5. Now we see this:
key 139 MENU VIRTUAL
key 102 HOME VISUAL
key 158 BACK HOME
Click to expand...
Click to collapse
All you have to do is option out the keys you don't want to work with a #. So if you are like me and think the home button is fine, it will look like this.
#key 139 MENU VIRTUAL
#key 102 HOME VISUAL
key 158 BACK HOME
Click to expand...
Click to collapse
6. When you have the ones you want optioned out just tap the little disk icon in the top right. It will ask for root rights, grant it, saved.
7. Now just reboot and DONE!
tut copied from http://rootzwiki.com/topic/31065-tu...acitive-buttons-lights-and-use-on-screen-nav/ so i didn't have to rewrite it, but modified for xperia s....
peace out.
Thanks man,was looking for it
This is perfect for XZXperience 2!
Thanks for the tutorial man works like a charm.:thumbup:
Sent from my LT26i using xda premium
Can this work to remap the menu key to the app switcher key?
I find the appeal for the soft/screen buttons really inexplicable. I have an Xperia TX and, really, this is the only thing that puts me down in that phone - I really wish it had capacitive buttons, much like the acro S. The most annoying thing about software buttons is that it takes up valuable screen area, leaving me with a sub-HD area available for other stuff. The interference with screen size in some apps is extremely annoying.
I'm thinking of getting an acro S solely because of this. And you guys here trying to disable your capacitive buttons! Taste really is something funny, I guess.
DeathMetalDiamond, once you see how difficult to operate and unpredictable in behavior the capacitive keys on the Xperia S are; you'll wish you had on-screen buttons as well!
Same goes for Ion.. its simply a nightmare especially in the dark. I literally have to guess where the buttons are. If they are well built, they are an asset. If not, they just screw u up.
i just recently tried out the OSB and i found it appealing, albeit lessening the screen space but i'll live with the trade off..capacitive buttons on the Acro S is sometimes none sensitive as i find myself tapping the back button 2x or 3x before i get it right..thanks for this tutorial :good:
edit: i got systemui FC [im using @niaboc79 's tab-n-grid sysui] when trying to access options menu in CyberShot 5.7.2 mod..everything else is good

Q: Avoiding Hardware Home Key?

The Note 8 looks great except for the hardware Home key. It's annoying to need physical force for a frequent task that should only take a slight touch.
Is there some way to work around the hardware Home key and avoid using it? Some of the reviews have mentioned on-screen keys, is it possible to keep those enable in all orientations & applications? Alternatively, is it possible to remap one of the capacitive keys to become a Home button?
Any methods or tips about how to avoid using the hardware Home key would be appreciated.
My Galaxy S4 has an Assistant Menu which provides things like an on screen Home and menu button. It's not in my Note 8.0 yet but may be added in a future release I guess.
Sent from my GT-I9505 using Tapatalk HD
Button Savior from the Play Store may do what you are after. It's funny. l personally like the hardware home key.
Sent from my GT-N5110 using xda premium
If you are rooted it would be simple to change your back or menu button to act as your home. You can go to /system/usr/keylayout/sec_touchscreen.kl and edit the BACK or MENU to read HOME.
Sent from my GT-N5110 using Tapatalk HD
I am using GMD gesture control on note 2&8 to simulate hardware buttons and keeping full screen for applications
Envoyé depuis mon GT-N7100 avec Tapatalk
Same issue as the OP, I'm using LMT with a pie control right on top of the hardware home button.
MikeChelen said:
The Note 8 looks great except for the hardware Home key. It's annoying to need physical force for a frequent task that should only take a slight touch.
Is there some way to work around the hardware Home key and avoid using it? Some of the reviews have mentioned on-screen keys, is it possible to keep those enable in all orientations & applications? Alternatively, is it possible to remap one of the capacitive keys to become a Home button?
Any methods or tips about how to avoid using the hardware Home key would be appreciated.
Click to expand...
Click to collapse
I use Taskbar task switcher by gdroid, it places a Return to desktop shortcut along with a configurable number of recent apps in the notifications pull down.
sisterchick said:
Button Savior from the Play Store may do what you are after. It's funny. l personally like the hardware home key.
Sent from my GT-N5110 using xda premium
Click to expand...
Click to collapse
Button Savior looks helpful, I played with it a little using both auto-hide and permanent display modes. The only downside to hidden mode is it takes two motions, first to expand the menu, then to click the home button. That can be done pretty quickly though.
Why do you like having a hardware button? I don't see why they made 2 buttons compatible with S-pen, and didn't make the Home button usable with the stylus as well.
Sent from my SGH-T699 using xda app-developers app
ual4720 said:
If you are rooted it would be simple to change your back or menu button to act as your home. You can go to /system/usr/keylayout/sec_touchscreen.kl and edit the BACK or MENU to read HOME.
Sent from my GT-N5110 using Tapatalk HD
Click to expand...
Click to collapse
Thanks, that would be useful. Is it also possible to assign those actions to a long-press? For example, Menu goes to Home with long press.
Sent from my SGH-T699 using xda app-developers app
Handy Hardware Button
MikeChelen said:
Button Savior looks helpful, I played with it a little using both auto-hide and permanent display modes. The only downside to hidden mode is it takes two motions, first to expand the menu, then to click the home button. That can be done pretty quickly though.
Why do you like having a hardware button? I don't see why they made 2 buttons compatible with S-pen, and didn't make the Home button usable with the stylus as well.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
Habit would probably be the best answer. I came to the Note 8 from a hacked Nook Color running CM10. I got accustomed to waking the device with the "n" hardware button. Like my old Nook, I put a non-slip bumper case on my Note 8 which makes pushing the power button to wake a little tedious. I also like to read in the dark and like the hardware key as a landmark for orientation when I pick it up with the lights off. Finally, I use the tablet in the kitchen on a stand for displaying recipes. I use a cheapest of the cheap $5 stylus in the kitchen to wake it up by pushing the hardware key and for scrolling pages so I don't get the tablet or the S-pen all gunked up with cookie dough from my fingers.:silly:
MikeChelen said:
The Note 8 looks great except for the hardware Home key. It's annoying to need physical force for a frequent task that should only take a slight touch.
Is there some way to work around the hardware Home key and avoid using it? Some of the reviews have mentioned on-screen keys, is it possible to keep those enable in all orientations & applications? Alternatively, is it possible to remap one of the capacitive keys to become a Home button?
Any methods or tips about how to avoid using the hardware Home key would be appreciated.
Click to expand...
Click to collapse
Custom ROM
MikeChelen said:
The Note 8 looks great except for the hardware Home key. It's annoying to need physical force for a frequent task that should only take a slight touch.
Is there some way to work around the hardware Home key and avoid using it? Some of the reviews have mentioned on-screen keys, is it possible to keep those enable in all orientations & applications? Alternatively, is it possible to remap one of the capacitive keys to become a Home button?
Any methods or tips about how to avoid using the hardware Home key would be appreciated.
Click to expand...
Click to collapse
LMT Pie
MikeChelen said:
The Note 8 looks great except for the hardware Home key. It's annoying to need physical force for a frequent task that should only take a slight touch.
Is there some way to work around the hardware Home key and avoid using it? Some of the reviews have mentioned on-screen keys, is it possible to keep those enable in all orientations & applications? Alternatively, is it possible to remap one of the capacitive keys to become a Home button?
Any methods or tips about how to avoid using the hardware Home key would be appreciated.
Click to expand...
Click to collapse
If you use your Note 8 in landscape mode, you'll soon wish all keys were physical, not capacitive.
tokugawa said:
If you use your Note 8 in landscape mode, you'll soon wish all keys were physical, not capacitive.
Click to expand...
Click to collapse
This is my concern, Im hoping that by using a case that goes over the bevel rather than sits flush with it, my palm will be less likely to brush against the back and menu capacitive buttons when playing games or drawing. My device should be arriving this evening so I will have to experiment to find my best solution. I dont want to mod the software to disble the buttons and get the traditional menu bar on the screen. I value the screen real estate. If they were physical buttons I wouldnt have this issue
hertsjoatmon said:
This is my concern, Im hoping that by using a case that goes over the bevel rather than sits flush with it, my palm will be less likely to brush against the back and menu capacitive buttons when playing games or drawing. My device should be arriving this evening so I will have to experiment to find my best solution. I dont want to mod the software to disble the buttons and get the traditional menu bar on the screen. I value the screen real estate. If they were physical buttons I wouldnt have this issue
Click to expand...
Click to collapse
It's still a bit annoying to me in landscape mode, but in Portrait mode it's been actually quite fine (even drawing). Perfect would be an app that could just temporarily disable/toggle it (maybe via a small 1x1 widget). Then if I want to use it in landscape mode (or whenever Im going to use it in a way that could be annoying with the capacitive keys), I could simply turn it on.
I do like the physical/capacitive keys in general too, since I also value the screen real estate so I guess for me a toggle solution would be best. Maybe I'll investigate into it and make it myself...
Or you can add Home button as Multiwindow "app" with this
https://play.google.com/store/apps/details?id=com.t2.shome
Sent from my Nexus 4 using Tapatalk 4 Beta
Hi, there's a way for disabling the capacitive keys, just look under development here on this forum. The mod will disable the keys and require the S Pen to make them work (quite useful for landscape) to enable On-Screen Buttons you should try this (works on the Galaxy S3/Note/Note II) I haven't tested in the Note 8 but I will as soon as I get mine (by the end of this month).
Enable on-screen buttons:
You will need root access for this.
Install ES File Explorer File Manager on your Note from the Play Store. This is a file manager that will be used to edit those system files to enable/disable on-screen/soft buttons.
Open ES Explorer. Then, click the menu button on your device and click Settings. Here, tick the “Up to Root” option. Then go down and tick the “Root Explorer” option, then press Allow/Grant button when prompted to grant it root access. Then, tick the “Mount File System Option” as well. Once all three options are selected, press back to exit the settings.
Hit the Up on top in ES Explorer till you reach the outermost folder (till it says / at the top).
Go into the system folder, then scroll down to find the build.prop file (Copy this file to a Safe location!!).
Tap on this file to start editing it. If you get an “Open With” prompt, select “ES Note Editor”.
Now, at the end of the file (at the bottom after the last line), add the line “qemu.hw.mainkeys=0″ (without the ” quotes), then save the file (press the Menu button to see the Save option).
Then, reboot. After the boot up, you should have the virtual on-screen buttons on your screen.
Sent from my XT925 using xda app-developers app
EDIT
How-to: disable the home button
The thread that Samper was referring to is at: http://forum.xda-developers.com/showthread.php?t=2250941
I can't post there yet, so I would like to add here that after disabling the menu/back buttons as described there, I worked out how to disable the home button. Following the same instructions as in the above link, also edit the gpio-keys.kl, changing the last line by adding a # to the beginning, so it looks like this:
Code:
#key 172 HOME WAKE
Now that all three buttons are completely dead (though the pen will still activate the menu/back buttons), I use LMT Launcher to provide pie controls at the bottom of the screen. Get it here: http://forum.xda-developers.com/showthread.php?t=1330150. PieControl from the Play Store is an easier-to-configure but less powerful alternative to LMT.

Disable & Hide H/W buttons-- Enable Softkeys! HTC One M7

Update:
Hey everyone, I would like to update my project just incase anyone stumbles across this post in the future . I first set out asking if such a glass or plastic screen protector exists that is tinted at the bottom to "black out" the capacitive buttons. I couldnt find anything like it and instead followed synister's advice to use car tint. I used a paper slicer to cut 8.5mm off of the bottom of a plastic screen protector and used that as reference when cutting the vinyl tint. I then applied both pieces making sure the edges touched. It does feel pretty smooth when you glide your finger back and forth; you will feel the line but it is "natural" to overcome.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*If you use as a guide I cannot be held liable. If you edit the wrong files you can cause your device to function incorrectly. Device needs root.*
I enabled softkeys/onscreen buttons by adding the following line to build.prop. It's really easy to do and not intimidating. Use a file browser with root access (root file explorer). Navigate to />system>build.prop, click it to edit as text, scroll to the bottom, type the following, save and reboot.
qemu.hw.mainkeys=0
Click to expand...
Click to collapse
To disable the hardware keys is similar. This time navigate to />system>usr>keylayout>synaptics-rmi-touchscreen.kl. When you open this file as text, you will see it only has 2 small lines "key 102 HOME"and "Key 158 Back." Put a hashtag # in front of both lines or simply delete the lines, save and reboot. To disable the backlight I used the app capacitive buttons: https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness.
And Voila. Worked in both sense 6 4.4.2 and cm11 nightlies. m8 what?
alexjzim said:
Hey guys.
After almost a year I still cant get used to HTC's proprietary 2 button, and now that even HTC has gone virtual I've officially said "screw it."
Although I haven't put a ROM on my phone in a while, this one seems to allows the regular android onscreen virtual buttons in place of the 2 button layout: http://forum.xda-developers.com/showthread.php?t=2348415. Less screen estate doesnt bother me so much, but using the home button for home, recent apps,and google now does.
Here is where I need the Communities help!: I'm sure everyone values the beauty of their HTC One as much as I do, and I dont want to keep those ugly buttons around if I dont have to. Does anyone know of a plastic or glass screen protector for the m7 that will black out the bottom bar, to basically make those buttons disappear? I wouldn't mind the HTC logo, its just those buttons...
I'm willing to custom order, guinea pig, or bulk order if anyone else wants in on the bandwagon. I'll continue to research myself and will update accordingly, but hopefully I'm not the only one who has thought this .
Click to expand...
Click to collapse
with root, you can turn off the bottom buttons and turn off the back light.
but you can also go to the store and get car tint and cut some out and place it over the buttons too.
synisterwolf said:
with root, you can turn off the bottom buttons and turn off the back light.
but you can also go to the store and get car tint and cut some out and place it over the buttons too.
Click to expand...
Click to collapse
I ordered some tint online as per your recommendation. I would like to make it appear as if the buttons were never there, not just turn them off. I'll cut the tint into place and cut a screen protector to work together. Still open to more elegant options, but I will try to post pics when it comes.
Thanks for the advice!
bumping once for new info
Why would you want to eat up the screen using on screen buttons....makes no sense your cutting about a half inch of screen for this mod...shrugs....to each their own I suppose.
Wonders_Never_Cease said:
Why would you want to eat up the screen using on screen buttons....makes no sense your cutting about a half inch of screen for this mod...shrugs....to each their own I suppose.
Click to expand...
Click to collapse
Yes you lose some screen real estate but it is actually not as detrimental as you probably think.. With xposed and the sense 6 toolbox you can auto hide the dock in blinkfeed. Using the Fleksy keyboard massively reduces keyboard size. And the buttons auto hide when playing content from YouTube Netflix etc.
It's very doable and puts it more in line with the Moto x which is 4.7 with soft keys. hitting the home button is also less stressful on the thumb and let's you hold the phone higher up to hit that back corner
Can You put up some kind of video guide?
Thanks in advance
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Wonders_Never_Cease said:
Why would you want to eat up the screen using on screen buttons....makes no sense your cutting about a half inch of screen for this mod...shrugs....to each their own I suppose.
Click to expand...
Click to collapse
I was thinking the same thing, theres nothing wrong with the capacitive bittons and personally I would not not want to waste screen real estate,
plus even if you autohide the dock, which I know certain apps can do, you need to swipe up before you can use the back, home, task manager keys, adding another step ...
suppose some people prefer touch screen keys to capacitive ones, each to his own.
regards
I think it's still the lesser evil than always having at least one essential key missing. The One's design is total **** in that regard. I can't really reach the power button and often it doesn't respond. There is no menu button. Double tap and hold aren't reliable. I tried several configurations including Logo2Menu, the best one for me is a nav bar, where I have added two further buttons left and right. One menu button with double tap for auto rotate toggle and long press for quick settings. One for screen off and long press screen shot. To me that's the most usable configuration.

HTC One M7, S-On, TWRP 2.7.0.8, Cyanogen 11 20140621-NIGHTLY-m7, Xposed Framework, Flux Theme, Naxos Taz Icons
hmm. didnt work for me. i installed LMT launcher and disabled the keys. works for me.
Thanks for sharing this! I was hoping there was an Xposed or other root app that lets you enable the stock navbar without having to edit any files directly, but this isn't too difficult, and I've created a backup of my build.prop.
Btw, @psycho_maniac, I tried searching the settings of LMT to do this, and didn't see any options. :/
HitchslapHTC said:
I think it's still the lesser evil than always having at least one essential key missing. The One's design is total **** in that regard. I can't really reach the power button and often it doesn't respond. There is no menu button. Double tap and hold aren't reliable. I tried several configurations including Logo2Menu, the best one for me is a nav bar, where I have added two further buttons left and right. One menu button with double tap for auto rotate toggle and long press for quick settings. One for screen off and long press screen shot. To me that's the most usable configuration.

HTC One M7, S-On, TWRP 2.7.0.8, Cyanogen 11 20140621-NIGHTLY-m7, Xposed Framework, Flux Theme, Naxos Taz Icons
Click to expand...
Click to collapse
Which xpose module allows additional buttons ?
I'm on CM11S, navbar enabled but additional buttons are only menu and search. I would like to add the screen off one
alexjzim said:
Update:
Hey everyone, I would like to update my project just incase anyone stumbles across this post in the future . I first set out asking if such a glass or plastic screen protector exists that is tinted at the bottom to "black out" the capacitive buttons. I couldnt find anything like it and instead followed synister's advice to use car tint. I used a paper slicer to cut 8.5mm off of the bottom of a plastic screen protector and used that as reference when cutting the vinyl tint. I then applied both pieces making sure the edges touched. It does feel pretty smooth when you glide your finger back and forth; you will feel the line but it is "natural" to overcome.
*If you use as a guide I cannot be held liable. If you edit the wrong files you can cause your device to function incorrectly. Device needs root.*
I enabled softkeys/onscreen buttons by adding the following line to build.prop. It's really easy to do and not intimidating. Use a file browser with root access (root file explorer). Navigate to />system>build.prop, click it to edit as text, scroll to the bottom, type the following, save and reboot.
To disable the hardware keys is similar. This time navigate to />system>usr>keylayout>synaptics-rmi-touchscreen.kl. When you open this file as text, you will see it only has 2 small lines "key 102 HOME"and "Key 158 Back." Put a hashtag # in front of both lines or simply delete the lines, save and reboot. To disable the backlight I used the app capacitive buttons: https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness.
And Voila. Worked in both sense 6 4.4.2 and cm11 nightlies. m8 what?
Click to expand...
Click to collapse
This is an awesome mod! Could you put up higher resolution pics and/or a video? Thanks!
Given this mod is there any way to disable the virtual menu button that shows up in some apps? It seems that these apps thinks there is no menu button this phone. At least when using Sense-based roms.
Example: Battle.Net Authenticator
guy4jesuschrist said:
Thanks for sharing this! I was hoping there was an Xposed or other root app that lets you enable the stock navbar without having to edit any files directly, but this isn't too difficult, and I've created a backup of my build.prop.
Btw, @psycho_maniac, I tried searching the settings of LMT to do this, and didn't see any options. :/
Click to expand...
Click to collapse
What do you want LMT to do? I've been using it a lot lately on my nexus 6 so I'm curious.
psycho_maniac said:
What do you want LMT to do? I've been using it a lot lately on my nexus 6 so I'm curious.
Click to expand...
Click to collapse
I'm not looking for it anymore, but at the time, I was looking for a way of enabling the built in navbar, without modifying system files. Kinda like how an Xposed module could be used to enable the hidden heads up feature in KitKat.
guy4jesuschrist said:
I'm not looking for it anymore, but at the time, I was looking for a way of enabling the built in navbar, without modifying system files. Kinda like how an Xposed module could be used to enable the hidden heads up feature in KitKat.
Click to expand...
Click to collapse
oh i was referring to LMT because I just wanted them turned off completely since my new phone (at the time) had the nav bar (oneplus one) and it was hard getting used to only have 2 buttons on the bottom of the htc m7. Now that I use LMT for my main launcher I even turn off the navigation bar. Its pretty sweet. You can have up to 24 shortcuts. I have the nexus 6 now and love it!
It helped me alot my home button got stuck and was pressing it self all the time, Thanks dude
I use a black tape and some transparent tape to cover the buttons .. Lol its look very weird but anyways , its cool ..
Sent from the air
HTC One Max
hi good afternoon i want ask if you can update your project for htc one max ?

Categories

Resources