Related
On previous phones including the S5 you could just change the build.prop or use gravity box to add them but every time I try on reboot I get system UI crashing non stop until I undo my changes.
Has anyone gotten them somehow?
What about the side key panel?
Sent from my SM-N910C using XDA Free mobile app
That's in the way and inconvenient. They should have just added pie
Use Xposed and install GravityBox and use Navigation Bar Tweak feature
pcboyy said:
Use Xposed and install GravityBox and use Navigation Bar Tweak feature
Click to expand...
Click to collapse
It doesn't work. My post says that It doesn't.
zgroten said:
It doesn't work. My post says that It doesn't.
Click to expand...
Click to collapse
Had same issue. Use dynamic navbar on playstore or lmt pie. I went for dynamic navbar it's amazing and can be customised to your absolute liking.
I've installed dynamic Navbar but can't seem to figure out how to make it work like a regular Navbar and not sit on top of items on the screen.
I am using lmt pie...loving it
Sent from my SM-N910C using Tapatalk
Nobody can get regular softkeys without system UI crashing?
nope, seems like there's some piece of code missing, so that every time you activate those softkeys it just bootloops. have tried a number of methods, haven't found one that works. missing that soft home button (
eydryan said:
nope, seems like there's some piece of code missing, so that every time you activate those softkeys it just bootloops. have tried a number of methods, haven't found one that works. missing that soft home button (
Click to expand...
Click to collapse
This is a shame. I figured this would be one of the first mods due to the popularity and convenience of on-screen buttons. The bezel on the Note 4 is so small at the bottom that it wouldn't even look like a waste of space to have a navigation bar. The capacitive buttons are so easily pressed due to the small bezel. I don't mind this, but I wish the option for on-screen was included by samsung. I also hate the "back" button on the right side because I'm left-handed and can't reach it with my dominant hand. That should be reversible as well. Is that possible?
I also recommend lmt. The back button is instant.
whittikins said:
but I wish the option for on-screen was included by samsung. I also hate the "back" button on the right side because I'm left-handed and can't reach it with my dominant hand. That should be reversible as well. Is that possible?
Click to expand...
Click to collapse
If device is rooted then you can remap back and menu key by editing generic.kl
Sent from my SM-N910G using xda premium
dr.ketan said:
If device is rooted then you can remap back and menu key by editing generic.kl
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
Did exactly that as soon as I got it. Although I actually prefer back key on right, just find note too wide to reach across, being left handed. Turned off the key light, not to cause confusion, and I guess it took a day to train muscle memory.
Sent from my SM-N910W8
dr.ketan said:
If device is rooted then you can remap back and menu key by editing generic.kl
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
Ah, thanks! What would I change to simply disable the Recent and Back keys completely? I have on screen keys now. I still want to keep the home button because I don't accidentally press it.
Actually, I just put a # in front of the line for app_switcher, which worked. What do I change or remove to disable the capacitive Back hardware key? Thanks!
EDIT: figured it out!
To disable the Recent and Back hardware keys (capacitive buttons), edit /system/usr/keylayout/Generic.kl and put a # in front of these 2 lines:
key 158 BACK
key 254 APP_SWITCH
Save and reboot!
whittikins said:
Ah, thanks! What would I change to simply disable the Recent and Back keys completely? I have on screen keys now. I still want to keep the home button because I don't accidentally press it.
Actually, I just put a # in front of the line for app_switcher, which worked. What do I change or remove to disable the capacitive Back hardware key? Thanks!
EDIT: figured it out!
To disable the Recent and Back hardware keys (capacitive buttons), edit /system/usr/keylayout/Generic.kl and put a # in front of these 2 lines:
key 158 BACK
key 254 APP_SWITCH
Save and reboot!
Click to expand...
Click to collapse
That's very useful!:good:
marvi0 said:
Had same issue. Use dynamic navbar on playstore or lmt pie. I went for dynamic navbar it's amazing and can be customised to your absolute liking.
Click to expand...
Click to collapse
What is this lmt pie?
kopkiwi said:
What is this lmt pie?
Click to expand...
Click to collapse
It's an amazing app here in xda developed by a recognized member that adds pie control to your phone
drmodify said:
It's an amazing app here in xda developed by a recognized member that adds pie control to your phone
Click to expand...
Click to collapse
The only thing about let and pie control in general is that it auto dissappear. When multiple back key is required, it is a pain.
Which is why I have resorted to using side key panel when I don't want to use capacitive. I edited settings database to add transparency to side panel menu as well as having a hint bar dissappear. I moved it to the comfortable zone for my thumb, and trigger it without fail. It says on till I press outside of the side menu.
It is working great for me. Although I would rather have standard nav bar for purely visual reasons as well as more modding options.
Sent from my SM-N910W8
I too am a lover of a static nav bar on my Galaxy Devices.
I now have a SM-N910P now and am frustrated as heck at not being able to get it functional here, on a rooted stock NK2. I used to run SlimKat 4.4.2 on my SPH-L710 and loved the navbar that they baked into the ROM. SlimLoli is maturing for the Note 4, but it doesn't yet have any S-Pen support baked in. This fact, when coupled with how well Samsung and Sprint have done with TouchWiz on the Note 4 have caused me to hold off on putting a custom ROM on the device.
So, what to do.?. Editing buildprop does indeed cause the looping system UI FC. UDN is an excellent solution barring one issue, and that it is doesn't have a means to dedicate a portion of the display to the nav bar. It just overlays on top of the launcher's/app's UIs. I'd be willing to pay for a solution that fixes this.
Pie controls have never really clicked with me. Not yet being willing to move away from NK2, I find that I am wondering if there is a way to force a portion of the bottom of the screen to be entirely dedicated to a specific app, all of the time. As depicted in this screeny, UDN overlays and it is frustrating as hell.
Anyone have any ideas yet?
-t
My device is S6 edge tmobile. There is a circle setting button always showed up when some app's open. It''s totally useless and sometime makes the screen not working. I know some Tom disable this feature but I just want to know how to do that. Screen shot is here. Anyone knows how ?
Michael_Meng said:
My device is S6 edge tmobile. There is a circle setting button always showed up when some app's open. It''s totally useless and sometime makes the screen not working. I know some Tom disable this feature but I just want to know how to do that. Screen shot is here. Anyone knows how ?
Click to expand...
Click to collapse
Tools toggle -swipe down, uncheck tools toggle.
S6 only has 3 buttons. Multi tasking, home and back.. Android has a 4th button for settings and the floating 3 dots is the 4th buttons and only appears when an app has it in its code for the 4 settings button.
Other android phones that have on screen buttons also has this as part of the navigation
freaksamael said:
Tools toggle -swipe down, uncheck tools toggle.
Click to expand...
Click to collapse
Thank you for the reply man. But I really dont get you. Can you explain it more specifically? I cant find the seeting of the tools toggle...
Ronaldo_9 said:
S6 only has 3 buttons. Multi tasking, home and back.. Android has a 4th button for settings and the floating 3 dots is the 4th buttons and only appears when an app has it in its code for the 4 settings button.
Other android phones that have on screen buttons also has this as part of the navigation
Click to expand...
Click to collapse
Thank you for.the reply man. But you get me wrong. What I am trying to disable is the button that flaoting when some apps open. You see that small wite button at left corner of the snapshort?
Michael_Meng said:
Thank you for.the reply man. But you get me wrong. What I am trying to disable is the button that flaoting when some apps open. You see that small wite button at left corner of the snapshort?
Click to expand...
Click to collapse
Are you sure you don't mean the white circle with 3 dots on the right of the screen
Yeah I mean it.. Sorry. But I know some rom can disable it. like VN 3.0. This button really buzzy me.
It's part of Lollipop for apps that haven't updated to the fact phones don't have hard menu button. App needs to be updated by Dev.
Sent from my SM-G925F using Tapatalk
Not possible
This button acts as a replacement for the hardware menu button on older devices.
thats the menu button
I've enabled the navkey, but the capacitive buttons are still working, i have tried editing the key layout settings but its still there.. Also tried gravity box but no luck.. Any help? Thanks
Use gravity box to disable backlight (under display section). Then use a file manager and editor with root access (I used ES File Explorer) and open the file synaptics_dsx.kl (it is located under system>user>keylayout) and then edit it by adding a # in front of the key entries. Save, reboot and your hardware keys should be off
kanagawaben said:
Use gravity box to disable backlight (under display section). Then use a file manager and editor with root access (I used ES File Explorer) and open the file synaptics_dsx.kl (it is located under system>user>keylayout) and then edit it by adding a # in front of the key entries. Save, reboot and your hardware keys should be off
Click to expand...
Click to collapse
Thanks mate, i have disabled the light though editing synaptics didnt work, but i figured it out by editing atmel_mxt_T100_touchscreen.kl,
Now, my problem is switching the back button and recent..
Why do you want to do that?
---------- Post added at 09:23 AM ---------- Previous post was at 09:19 AM ----------
I have enabled the soft keys via buildprop, disabled the hardware keys in the synaptic file, disabled the backlight and added double tap home key to sleep and long press home key for menu using gravity box. Looking good with the Pixel launcher, although unfortunately don't get the transparent white dock background.
Screenshot:
jlou0918 said:
I've enabled the navkey, but the capacitive buttons are still working, i have tried editing the key layout settings but its still there.. Also tried gravity box but no luck.. Any help? Thanks
Click to expand...
Click to collapse
hii can you tell me how u activated navigation bar i have tried several ways including cm13 and gravity box
how did you do it
thanks
[email protected] said:
hii can you tell me how u activated navigation bar i have tried several ways including cm13 and gravity box
how did you do it
thanks
Click to expand...
Click to collapse
You can do it manually if you have root, just need to change a value from 1 to 0 in the buildprop file (it's easy to find the relevant line as it has a description). However, I just use a free root app called Softkey Enabler from the Play Store. This makes it very quick to enable or disable the nav bar.
I leave the hardware keys on (because their long press functions are useful) but in accessibility settings I switch their layout around to match the nav bar. I use another root app called Keyboard Backlight Controller to disable their backlight.
kanagawaben said:
You can do it manually if you have root, just need to change a value from 1 to 0 in the buildprop file (it's easy to find the relevant line as it has a description). However, I just use a free root app called Softkey Enabler from the Play Store. This makes it very quick to enable or disable the nav bar.
I leave the hardware keys on (because their long press functions are useful) but in accessibility settings I switch their layout around to match the nav bar. I use another root app called Keyboard Backlight Controller to disable their backlight.
Click to expand...
Click to collapse
Which rom are u on?
I tried soft key enabler on official 16s and 19s it didn't work
I am on cm13 umbrella and it's really good
Far better fingerprint recognition
Better battery life I lost 3% over night
and finally i tried ur buildprop thing for soft keys it worked thanks for that BTW
Did u get to make the Navbar transparent by any chance
I have used the settings in cm13 to turnoff the backlit of capacitive buttons but there still functional can explain how u disable them or use them as u do for long press
Cheers for the help
[email protected] said:
Which rom are u on?
I tried soft key enabler on official 16s and 19s it didn't work
I am on cm13 umbrella and it's really good
Far better fingerprint recognition
Better battery life I lost 3% over night
and finally i tried ur buildprop thing for soft keys it worked thanks for that BTW
Did u get to make the Navbar transparent by any chance
I have used the settings in cm13 to turnoff the backlit of capacitive buttons but there still functional can explain how u disable them or use them as u do for long press
Cheers for the help
Click to expand...
Click to collapse
I am currently using 17S based Cuoco92. Fingerprint recognition has been just fine for me on Cuoco92, and on stock 16S, 17S and 19S - fast and accurate. The nav bar I have is transparent, just like in stock android. To disable the hard keys, go into system-usr-keylayout and edit the synaptics file (just add a # in front of the lines relating to the keys).
kanagawaben said:
I am currently using 17S based Cuoco92. Fingerprint recognition has been just fine for me on Cuoco92, and on stock 16S, 17S and 19S - fast and accurate. The nav bar I have is transparent, just like in stock android. To disable the hard keys, go into system-usr-keylayout and edit the synaptics file (just add a # in front of the lines relating to the keys).
Click to expand...
Click to collapse
Thanks for the info really appreciate it
I have found a small thing do u have any fix for it?
The notification panel doesn't fully open due to the nav keys
Some other elements get blocked as well
Any solution?
[email protected] said:
Thanks for the info really appreciate it
I have found a small thing do u have any fix for it?
The notification panel doesn't fully open due to the nav keys
Some other elements get blocked as well
Any solution?
Click to expand...
Click to collapse
No, don't think there's anything you can do about that I'm afraid. I have actually gone back to just using the hard keys as they come. The soft nav keys are nice, but bit of a waste of screen space when you have perfectly good hard keys there to use.
kanagawaben said:
No, don't think there's anything you can do about that I'm afraid. I have actually gone back to just using the hard keys as they come. The soft nav keys are nice, but bit of a waste of screen space when you have perfectly good hard keys there to use.
Click to expand...
Click to collapse
Yea your right about that but the screen is big so having on screen buttons help in using the phone with one hand
I am surprised how the hardware buttons completely disappears when not back lit better then even OnePlus one
I have put a request in the feedback app for a feature like OnePlus one for choice between on screen and off screen
[email protected] said:
Yea your right about that but the screen is big so having on screen buttons help in using the phone with one hand
I am surprised how the hardware buttons completely disappears when not back lit better then even OnePlus one
I have put a request in the feedback app for a feature like OnePlus one for choice between on screen and off screen
Click to expand...
Click to collapse
I would love them to add that feature. It was one of the best things about CM13 on my Zenfone 2.
Currently I am using the stock eui launcher (it's so smooth and light, and I don't really need an app drawer because I don't download so many apps) and the soft keys don't go so well with that launcher, but I also have the Pixel launcher installed, and I really like using the soft keys with that.
Sorry all if queastion was before (can't find answer and I'm really pissed off)...is it possible to remove this arrow under the keyboard on pixel 6 (pic in attach)?! I had pixel 6 pro few days ago (returned because fingerprint sensor didn't work) and I'm shure that I didn't had arrow there (gestures used too, all same as here). Tried to find option to turn off everywhere but no success...hope that this is not feature from todays jan update?!
You can't remove that arrow, it's used to hide and un-hide the keyboard.
Proday said:
Sorry all if queastion was before (can't find answer and I'm really pissed off)...is it possible to remove this arrow under the keyboard on pixel 6 (pic in attach)?! I had pixel 6 pro few days ago (returned because fingerprint sensor didn't work) and I'm shure that I didn't had arrow there (gestures used too, all same as here). Tried to find option to turn off everywhere but no success...hope that this is not feature from todays jan update?!
Click to expand...
Click to collapse
That's not a new feature. Has always been there. If rooted you can remove with a mod that removes navbar, gesture pill, etc..
It is different if using two button or three button navigation.
I use the three button navigation and the back arrow key in the navigation changes to a down arrow key.
Pixel's implementation of down arrow on the navbar (or at least the padding below) is actually better than not having anything (like Xiaomi did on MIUI). The OS cannot recognize smartly if you meant a swiping up gesture or just simply pressing the space button, hence this placement.
Lughnasadh said:
That's not a new feature. Has always been there. If rooted you can remove with a mod that removes navbar, gesture pill, etc..
Click to expand...
Click to collapse
Tnx for info mate. I'll search for it.
vandyman said:
It is different if using two button or three button navigation.
I use the three button navigation and the back arrow key in the navigation changes to a down arrow key.
View attachment 5508985
Click to expand...
Click to collapse
I know mate, but I'm using swipe last 3 years, can't go back on old commands...and this way I have more screen space to look at.
peter_betos said:
Pixel's implementation of down arrow on the navbar (or at least the padding below) is actually better than not having anything (like Xiaomi did on MIUI). The OS cannot recognize smartly if you meant a swiping up gesture or just simply pressing the space button, hence this placement.
Click to expand...
Click to collapse
Whell thats individual thing. This way I'm loosing about 1cm of screen size, on samsung (one plus) phones it works for me without any problem.
Anyway, now im certain that it is not to remove id witouth root...thanks all one more time.
Try this method (pictures attached) worked for my OnePlus 10 pro oxygenos13 beta.
1. Go to the settings
2. Open additional setting or direct search 3rd option
3. Keyboard & input method
4. keyboard location
5. Select hide
Romi007 said:
Try this method (pictures attached) worked for my OnePlus 10 pro oxygenos13 beta.
1. Go to the settings
2. Open additional setting or direct search 3rd option
3. Keyboard & input method
4. keyboard location
5. Select hide
View attachment 5688671 View attachment 5688673
Click to expand...
Click to collapse
you're awesome
it worked
i like getting my inquiry resolved fast
that was fast
Lughnasadh said:
That's not a new feature. Has always been there. If rooted you can remove with a mod that removes navbar, gesture pill, etc..
Click to expand...
Click to collapse
I am using gensture navigation in lineageOS 19, and I also meet this problem that my phone have a very wide bottom bar when I input something. My phone have a small screen so that I have a bad experience when I input, but I couldn't find related setting in my phone setting. However I have rooted so could you give me this module? Thank you very much!
A marinated egg said:
I am using gensture navigation in lineageOS 19, and I also meet this problem that my phone have a very wide bottom bar when I input something. My phone have a small screen so that I have a bad experience when I input, but I couldn't find related setting in my phone setting. However I have rooted so could you give me this module? Thank you very much!
Click to expand...
Click to collapse
HideNavBar/README.md at master · Magisk-Modules-Repo/HideNavBar
Contribute to Magisk-Modules-Repo/HideNavBar development by creating an account on GitHub.
github.com
Lughnasadh said:
HideNavBar/README.md at master · Magisk-Modules-Repo/HideNavBar
Contribute to Magisk-Modules-Repo/HideNavBar development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thanks very much!
Is there anyway to move the navigation buttons to the right?
My thumb just can't reach the back button
Thanks
it grinds my gears too!, here we are at the most advanced android 13, many years of it on smartphones and yet still so many things baked into oems, like navigation customisation
to me pixel phones must solve these issues since its stock, and not just root everything all the time, to me its meant to solve the android problem of baked in oem features, like one ui or else samsung just wins androids, and pixels are done, i wont keep it that long lol
pixel6wheresatmos said:
to me pixel phones must solve these issues since its stock...
Click to expand...
Click to collapse
They did. It's called "gesture navigation".
Get rid of nav bar, use XPosed Edge Pro, you can setup custom stuff
BarrettBear said:
Get rid of nav bar, use XPosed Edge Pro, you can setup custom stuff
Click to expand...
Click to collapse
Xposed is the Android equivalent of cancer. The Fullscreen Immersive Gestures module for Magisk and a launcher that has custom gestures, e.g. Nova Launcher, is more than sufficient.
"Xposed is the Android equivalent of cancer"
Lol okay
Well I've tried Fullscreen Immersive Gestures on Magisk, it didn't work, so I have my solution which does work. I have zero space taken up at the top of the screen, and zero space taken up at the bottom of the screen.
I have an invisible app-switch, home, and back button at the bottom of the screen, and the ability to add dozens more should I care to.
Robshr said:
Is there anyway to move the navigation buttons to the right?
My thumb just can't reach the back button
Thanks
Click to expand...
Click to collapse
Use Xposed Edge Pro, it allows you to designate your own invisible buttons. My setup is:
Lower left, swipe up to go into multi, long-press to bring up in-app menu
Lower center, swipe up to open Bottom Quick Settings, long press to go home
Lower right, swipe up to go back
But you don't have to use swipe up, you can tap, double-tap, long press, swipe up, swipe down, swipe left, or swipe right. You also have different areas, 3x per side (left/center/right, top/middle/bottom) for each of those, and each can be assigned to do a number of incredibly useful things.
If you have trouble reaching with your thumb, you can assign lots to the lower-right (near your thumb), long press to do one thing, swipe up to do another, swipe to the left to do something, etc.
Don't let anybody tell you it's bad, test it for yourself and make your own decision.
If you do use that setup, you can disable the nav bar entirely by:
Installing "MagiskHide Props Config", and a terminal emulator
Restart
Run the term emulator, give it superuser by typing su and granting, then run command props
Go to code 5 (add your own prop), type n for a new prop, call the new prop qemu.hw.mainkeys, give it a value of 1, press y to continue with defaults, press y to reboot again.
NavBar is now gone (like in my image).
If you want to bring the NavBar back, just run props again on the terminal, and delete the prop you made above.
BarrettBear said:
"Xposed is the Android equivalent of cancer"
Lol okay
Well I've tried Fullscreen Immersive Gestures on Magisk, it didn't work, so I have my solution which does work. I have zero space taken up at the top of the screen, and zero space taken up at the bottom of the screen.
I have an invisible app-switch, home, and back button at the bottom of the screen, and the ability to add dozens more should I care to.
Click to expand...
Click to collapse
If it didn't work you're doing it wrong. But then again I really only use it to ditch the hint at the bottom of the screen, so my use case may not be typical.
There is a reason why custom ROM developers don't accept bug reports with that crap you use in play, and that's because 9 out of 10 times the issue is Xposed itself. So Xposed and its derivatives needed to be put out to pasture years ago and just die already. Anything they can do can a root app can do just as effectively, and without the system instability penalty of the cancer that is Xposed.
At this point we are getting a little off topic, as the OP I do think was trying to avoid rooting to solve his problem. Of course, root may be the only solution to the problem.
I have my Back-Button on the bottom right, just old-school without rooting.
Sry for my english, Germany here.
BarrettBear said:
Use Xposed Edge Pro, it allows you to designate your own invisible buttons. My setup is:
Lower left, swipe up to go into multi, long-press to bring up in-app menu
Lower center, swipe up to open Bottom Quick Settings, long press to go home
Lower right, swipe up to go back
But you don't have to use swipe up, you can tap, double-tap, long press, swipe up, swipe down, swipe left, or swipe right. You also have different areas, 3x per side (left/center/right, top/middle/bottom) for each of those, and each can be assigned to do a number of incredibly useful things.
If you have trouble reaching with your thumb, you can assign lots to the lower-right (near your thumb), long press to do one thing, swipe up to do another, swipe to the left to do something, etc.
Don't let anybody tell you it's bad, test it for yourself and make your own decision.
If you do use that setup, you can disable the nav bar entirely by:
Installing "MagiskHide Props Config", and a terminal emulator
Restart
Run the term emulator, give it superuser by typing su and granting, then run command props
Go to code 5 (add your own prop), type n for a new prop, call the new prop qemu.hw.mainkeys, give it a value of 1, press y to continue with defaults, press y to reboot again.
NavBar is now gone (like in my image).
If you want to bring the NavBar back, just run props again on the terminal, and delete the prop you made above.
Click to expand...
Click to collapse
Are you running android 13 or 12
I'm running 13 and I don't think it's compatible with 13 as it won't install the Xposed framework
Robshr said:
Are you running android 13 or 12
I'm running 13 and I don't think it's compatible with 13 as it won't install the Xposed framework
Click to expand...
Click to collapse
I'm still on 12. I stick with what I know works
Robshr said:
Are you running android 13 or 12
I'm running 13 and I don't think it's compatible with 13 as it won't install the Xposed framework
Click to expand...
Click to collapse
Which is why Fullscreen Immersive Gestures - a Magisk module - is a better option than any Xposed crap. It at least works, if you set it up correctly.
mr73 said:
I have my Back-Button on the bottom right, just old-school without rooting.
Sry for my english, Germany here.
Click to expand...
Click to collapse
How did you done that?
I can't find anything that works on pixel 6
valyemil811 said:
How did you done that?
I can't find anything that works on pixel 6
Click to expand...
Click to collapse
I used "Navigation Bar for Android" from Wormhole Space, it works for me without rooting. IMO i like it because i use the back button more than the other ones, try it.
mr73 said:
I used "Navigation Bar for Android" from Wormhole Space, it works for me without rooting. IMO i like it because i use the back button more than the other ones, try it.
Click to expand...
Click to collapse
I thought you made some .xml or adb modification straight to phone
Sry no, i dont have the time and ability to learn new things like programming or something like that.
mr73 said:
Sry no, i dont have the time and ability to learn new things like programming or something like that.
Click to expand...
Click to collapse
Oki doki