[GUIDE] Swap back and recent buttons - Fire HD 8 and HD 10 General

All of my recent devices have had the back button on the right of the navbar, or the option to move it. I'm so used to having mine in that configuration that I kept hitting the wrong button so decided to change it, using ADB we can achieve this.
Connect to ADB then use the following commands:
adb shell
settings put secure sysui_nav_bar "space,space,space,space,recent;home;back,space,space,space,space"
If you want the buttons spread out a little more, remove a space from either side

Related

[Q] Non-Touch compactible rom?

Hi guys,
My digitizer has died, and till the new one comes I was thinking of how I could use my T7272, I can write the SMS fine, but I can't send them out, cause the button is on the screen itself... is there a rom I could use freely w/o using the touchscreen?
P.S.
Is the digitizer hard to replace?
You could check out AE Button; it has some options like button presses that will activate soft buttons. I suspect you could send sms's using it. You could also try using mortscripts with AE button that will do stuff you need. There are some pretty simple scripts that will simulate screen taps, and you could assign them to a button push. I'd rather have a working touchscreen, though.
Here are some of the commands:
# 91: startmenu (on some devices it might be home button)
# 92: back key (not the backspace key but back key for closing applications which is available on some devices such as diamnd or blackstone)
# 93: menu key
#112: left softkey
#113: right softkey
#114: accept call (green button)
#115: hang up (red button)
#117: volume up
#118: volume down
#126: data disconnect
#127: toggle speaker
#133: devicelock
#223: power off
I use one to lock the device. Basically, you just put this:
Code:
sendspecial(133)
in a .txt file, and change the extension to .mscr. I call it Lock.mscr, and I have it assigned to a few different actions (like when a call comes in, a script locks the phone). So, sendspecial(112) and sendspecial(113) might help you out. There's also one for hitting 'Ok' in popups, which would probably work for you. I can't find it, though (google 'sendspecial' and you'll find it, it's all on msdn).
Anyway, if you install mortscript (maybe you already have it) as well as AE Button, you could assign button pushes to carry out those actions. Just stick the scripts somewhere easy, like the start menu, and it will be easy to set up.
If you want to get more complicated, there are also mortscript commands that simulate button pushes on the screen. You could set one up that would do just about anything. Also, SK Schema does similar stuff. You can write fairly simple sequences of button pushes that will do just about anything. This is one that I use that runs SK Tools Pim backup (I have it scheduled to run every night in the middle of the night).
#r(\windows\sktstart.exe) #p(STH:20)
#tap(146;602) #sleep(15000)
#tap(110;533) #sleep(500)
#tap(339;455) #sleep(500)
#tap(126;604) #sleep(500)
#tap(114;84) #sleep(500)
#tap(146;99) #sleep(5000)
#tap(310;254) #sleep(90000)
#tap(433;602) #sleep(10000)
#pwr() #sleep(10000)
Click to expand...
Click to collapse
Basically, the backup tool gets launched in line 1, then there are a bunch of screen taps (w/ delays, to make sure everything is ready) in the menus to get the right options selected, followed by turning the device off.
I`m not sure... But i saw somewhere app that emulate a mouse (cursor) and you will be able to control this mouse with your D-pad... But I can be wrong...
I can't install that mortscript w/o the touchscreen though..damn it..: )..
Get MyMobiler, and use it to run your device off of a pc. You should be able to get that working.

Broken Capacitive Button Workaround!

Alright, the Galaxy series, although awesome, suffers from some issues. None are as frustrating as when the damn capacitive (bottom) buttons stop working!
Normally it seems that all four bottom buttons don't fail at the same time, just one or two. This doesn't seem to be as much of a physical problem as a software one, probably an application running in the forefront that is blocking them. Now it is hard to do much of anything if the settings button (left side) fails, as you cannot access most settings for your apps. Both my outside buttons rarely work, the aforementioned settings button (left) and the search button (right). Search button doesn't matter to me, I can call up search on screen easily enough. The other two are home and back buttons. Back is more necessary than home. So to work around this Samsung-induced-pain-in-the-ass, I swapped the search button function for the home.
Here's how:
Make sure you are roted and have a rooted file manager. Root Explorer tends to work best.
1. Open Root Explorer, and make sure it is mounted r/w.
2. Navigate to /system, /usr, /keylayout.
3. Tap/hold Broadcom_Bluetooth_HID.kl, and select 'Open in Text Editor'. If you get a Warning message, that means you are mounted r/o so you just need to click the Mount R/W button above.
4. Change key 139 to read HOME instead of MENU.
Change key 102 to read MENU instead of HOME.
Hit the back capacitive button and choose to save. It will create a Broadcom_Bluetooth_HID.kl.bak file also so if you want to undo this then just erase the new Broadcom_Bluetooth_HID.kl file and then erase the .bak off the other file.
5. Now open the melfas_touchkey.kl file the same way by holding it until it allows you to select 'Open in Text Editor'.
Change key 139 to read HOME instead of MENU.
Change key 102 to read MENU instead of HOME.
Hit the back capacitive button and choose to save. It will also create a .bak file.
6. Open the qwerty.kl file by holding it until it allows you to select 'Open in Text Editor'.
Change key 102 to read MENU instead of HOME.
Change key 139 to read HOME instead of MENU.
Hit the back capacitive button and choose to save. It will again create a .bak file.
7. Back out of Root Explorer and restart your phone.
Now, when you push your home button it will bring up your settings menu in whatever application is open, and your settings button will do the home function (or nothing, as my outside buttons do as they don't usually work). I now use my back button to get me to home, it just takes a few more pushes as it goes one step at a time. Not as much of a pain as not being able to set program functions, that's for sure!
Note: Depending on your setup, the file names might be slightly different on other Android devices, but they will always be very similar. They'll all have a bluetooth.kl, touchkey.kl and qwerty.kl (or whatever your keyboard layout might be). You can also fool around with other key settings if you wish to experiment, depending on what is and is not working at the current time. Just save your original .bak files so you can put it back to normal easily. If you alter the .kl file more than once, it will overwrite the .bak file again (which is not used by the phone) so make sure you copy the .bak's to another directory (such as /sdcard/backups or your regular computer).
Hope this makes your lives easier and don't forget to thank me if I helped you.
Modified Home key acting up
So after using this mod for a little while, it has been working well except for some slight stalling of response from the capacitive buttons (which was happening before the mod) and an awfully annoying habit of backing out of programs by itself due to the modified left button which was originally Settings but I changed to Home with the above mod. When this happens, I can see the left button go dark as if it's been physically pressed, so obviously there is some electrical or software malfeasance happening there.
The fix to this problem is to navigate to your /system/usr/keylayout folder again and:
Delete: "key 139 HOME"
In each of these three folders we altered earlier:
Broadcom_Bluetooth_HID.kl
melfas_touchkey.kl
qwerty.kl
The result is that no action is associated with the leftmost capacitive button, which is fine because it wasn't working properly in the first place. This was becoming problematic as I typed in Terminal or while using my Ubuntu build on the phone.
Now, if there was also a problem with the search popping up by itself then you would just have to delete "key 217 SEARCH". Remember why I initially did this was because the outside capacitive buttons were not functioning properly and I needed the settings button more than home while in programs.
Fully Functioning Capacitive Button Workaround
I actually found a specific need for the home key.
When in Terminal Emulator, if I want to back out to the main screen and access another application, I have to use my back button. Trouble is, the back button also closes out the terminal session, which is a pain in the *ss if I want to just look up something in my browser and then go back to it. I have to then restart my session and retype on the small as hell keyboard. So I was thinking, how am I going to implement a home key function in my drop-down start menu which is always accessible and low-and-behold, here it is:
SoftKeys for Root Users
https://market.android.com/details?...EsIm5ldC5ob29wYWpvby5hbmRyb2lkLlNvZnRLZXlzIl0.
This is a great app. Solves the problem. Starts immediately on boot.
There's also this for just a home key in the start menu drop-down, no start on boot though:
BK Softhome
https://market.android.com/search?q=bk+softhome&c=apps
Problems solved! I now have disabled all 4 capacitive buttons while using Softkeys for Root Users for all functions. (Delete: key 102, key 139, key 158, and key 217 in all three folders listed in original post)

Software update 7/13 Sprint US

Idk if this, "software" update was from Samsung, or Sprint (in the US). But it updated something about the nav bar, and colors? Added a single dot to the nav bar to close it
But now the nav bar stays up on some games, and the new lil dot to close it, isn't there. No matter if I switch the full screen or any option in the gaming menu. Power off and back on etc, nothing. Some games it goes away, but Clash For Dawn, for instance, doesn't.
Sprint US S8+
How to hide nav and/or status bar
Traceamount said:
Idk if this, "software" update was from Samsung, or Sprint (in the US). But it updated something about the nav bar, and colors? Added a single dot to the nav bar to close it
But now the nav bar stays up on some games, and the new lil dot to close it, isn't there. No matter if I switch the full screen or any option in the gaming menu. Power off and back on etc, nothing. Some games it goes away, but Clash For Dawn, for instance, doesn't.
Sprint US S8+
Click to expand...
Click to collapse
What you can do is use the Android Debug Bridge (ADB) to help remove the nav bar from your screen. This will allow you to not see the nav bar until you swipe up from the bottom of the screen. I have also written instructions to remove the status bar also.
INSTRUCTIONS FOR HIDING NAV/STAUS BAR
1. Go to Developer Options in settings (on your phone) and turn on USB Debugging. If you don't know how to go to Developer Options, scroll down till you find the instructions I have written.
2. On your PC, navigate to the folder where ADB is installed (for me it is Documents > platform-tools). After that, open a Command Prompt window here (by holding shift and pressing right click in the blank space of the folder). If you do not have ADB installed scroll down till you find the instructions I have written.
3. When you have successfully opened a Command Prompt in the folder, connect your phone to your PC, then an option will appear (on your phone) if you want USB Debugging. Click accept.
4. Go back to the Command Prompt on your PC, and now you have these options: you can either get hide the nav bar, the status bar, or even both.
-If you want to just hide the nav bar, type: adb shell settings put global policy_control immersive.navigation=*
-If you want to just hide the status bar, type: adb shell settings put global policy_control immersive.status=*
-If you want to hide BOTH nav and status bar, type: adb shell settings put global policy_control immersive.full=*
5. As soon as you hit enter, your phone will apply the changes
6. Enjoy!
IF YOU WANT TO REVERT ANY CHANGES, TYPE: adb shell settings put global policy_control null* INTO THE ADB COMMAND PROMPT!!!!!
HOW TO TURN ON DEVELOPER OPTIONS ON YOUR PHONE
1. Go to Settings
2. Navigate to "About phone"
3. Tap the Build Number seven times
4. Go back and scroll all the way to the bottom
5. Developer Options have been turned on
HOW TO INSTALL ADB ON YOUR PC
1. Go to this link: tr.im/adb
2. Follow the instructions
IF YOU HAVE ANY QUESTIONS, FEEL FREE TO LET ME KNOW

Enabling 2 button navigation without ADB on Betas

I saw an article that described how to use ADB to enable the Two button navigation feature that doesn't show in the Betas.
I've also seen the posts about ADB way.
I was wondering if one has root. Is there a config file that the feature can be turned on from instead?
Here is the ADB command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Just didn't know if someone could tell from this what config file it might be.
paulsg63 said:
I saw an article that described how to use ADB to enable the Two button navigation feature that doesn't show in the Betas.
I've also seen the posts about ADB way.
I was wondering if one has root. Is there a config file that the feature can be turned on from instead?
Here is the ADB command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Just didn't know if someone could tell from this what config file it might be.
Click to expand...
Click to collapse
I just updated my op7pro to Android 10 and would like this option back too and this is all I can find about it
Sent from my OnePlus7Pro using XDA Labs
I love this - thank you. Do not like the Android 10 gestures at all. 2 button is my favourite !
Have you tried just omitting the adb shell part and bunging this into Termux?
cmd overlay enable com.android.internal.systemui.navbar.twobutton
Anybody finding that the back button puts the screen off if double tapped when on the launcher screen? I tried disabling double tap to sleep on the home button, but it still happens. Just curious to see if it happens everyone or if it's just mine. Thanks
hallo dare said:
Anybody finding that the back button puts the screen off if double tapped when on the launcher screen? I tried disabling double tap to sleep on the home button, but it still happens. Just curious to see if it happens everyone or if it's just mine. Thanks
Click to expand...
Click to collapse
Just tried and it doesn't happen for me.
The back button doesn't show if I'm on the home screen and if I tap the back button when the app drawer is open it tends to just open the app that's 'underneath' the button
skymera said:
Just tried and it doesn't happen for me.
The back button doesn't show if I'm on the home screen and if I tap the back button when the app drawer is open it tends to just open the app that's 'underneath' the button
Click to expand...
Click to collapse
Yep same as that, no back button displayed on home screen, but it's turning off the screen if i tap on it twice. Something my side so. O well. Thanks for confirming

How To Guide Android 13 OneUI 5.0 sideActions Logcat Fix and Workarounds

sideActions Workaround​Due to a logcat permission change with Android 13, apps that rely on the logcat like sideActions to get system events are broken. To get sideActions running like normal, it requires enabling one time log access after every reboot. To force the one time log access prompt for sideActions:
1. Download and install Power Button Remapper for Samsung - sideActions. Since the app is incompatible with devices upgraded to Android 13 on the Play Store, the apk will need to be sideloaded manually. Click here to download directly from Apkmirror
2. Launch the app and grant all on screen permissions to get to the Full Remapping setup screen.
3. Either connect to PC and run the .exe file or just run the following ADB commands to unlock full remapping:
pm grant com.jamworks.sidekeybuttonremap android.permission.WRITE_SECURE_SETTINGS
pm grant com.jamworks.sidekeybuttonremap android.permission.READ_LOGS
am force-stop com.jamworks.sidekeybuttonremap
IF Bixby is still installed or enabled on your device then also run:
pm disable-user com.samsung.bixby.agent
4. After running the ADB commands or the .exe file from a PC, you will notice Full Remapping is enabled next time you run sideActions. Force Stop sideActions and DISABLE all file access permissions! File access for sideActions is only needed to access the .exe file during remapping. Once you disable it, you shouldn't have to touch it again. Workaround doesn't work while app has file access.
5. Force stopping an app also disables accessibility services. While accessibility is disabled and file access denied/revoked, launch sideActions and enable the power button. You should get a prompt to enable one time access to logs. Accept the prompt and sideActions will be up and running at full. Accessibility services are turned on automatically when you enable power button and grant log access.
​NOTE: If the above step doesn't work, restart your device and that should fix it. Step 5 must be completed after every device reboot to grant one time log access. Force Stop the app to stop accessibility services, launch app, toggle button on, prompt: enable one time access. Doesn't take more than 10 seconds. If you don't get the prompt to enable one time access, verify all file access is disabled!
​ALTERNATIVE OPTIONS​If taking a few seconds to enable log access after every reboot isn't your cup of tea then your best options are using RegiStar (Good Lock Module) for side button long presses which is a decent alternative. The downside of RegiStar is no double tap action or haptic feedback to indicate when a long press is recognized (sideActions exclusive) which doesn't sound like much, but you'll be surprised by how much you miss it. In addition to side key long press remap, RegiStar also includes Settings Menu reordering and optional double/triple tap actions for back taps (doesn't work well with covers). Another side key remapping option is Routines+ (Good Lock Module) which adds long press and double tap button remapping to Modes and Routines. Routines+ is slow registering key commands and actions compared to all other options listed here. The easiest way to add custom double tap remapping of the side key is through the native Side Key menu under Advanced Settings which is great for launching the camera or any application. You can extend the actions available to you under the Advanced Settings Side Key menu to pretty much anything by launching the Tasker Secondary App on double press which will trigger a profile and launch a task of your choosing within Tasker. I don't know of any support for double tap and hold key combinations outside sideActions. To remap the volume buttons, any 3rd party app including Routines+ can accomplish that.
Is there any alternative application where you don't have to do step 5 after every reboot?
Thank you for the instruction. I think it should be Samsung standard.
_Floyd said:
I think it should be Samsung standard.
Click to expand...
Click to collapse
Agreed. I don't see how anyone who has tried it doesn't like it. Especially since they got rid of the "Bixby button".
Thank @Dougmeister and @bingblop for now its work perfectly, with the guide.
I am just a newb; @bingblop deserves all of the credit.
I should note for any other folks in my predicament... if you have experimented (and been disappointed) by Samsung's recent attempt to address this via "Good Lock" and "RegiStar", then make sure you have disbled that functionality or the above steps may not work until you do disable them.
(RegiStar: "Side-Key press and hold action", etc.)
Edit: also, I had to navigate to the folder where my adb tools were 'installed' to execute the commands. Plus, I had to add "adb shell " before each of them. Maybe that is obvious to everyone else, but it wasn't to me.
Unfortunately no. No other third party apps have come out that alter the power button on Samsung devices anywhere near as well as sideActions did.
The granting after every reboot is the best we have right now for Android 13 users. It's Googles way of being more privacy and security conscious and Samsung never provides decent alternatives with their software. I personally wouldn't mind using RegiStar if there was a way to speed up the activation time. I like being able to turn flashlight on and off in 350mS which is only that fast in sideActions. Otherwise, it's like a 1000mS.
In fact, if anybody knows how to control the Bixby button long press activation time without sideActions, I'm all ears. I'd love to understand how to alter that time for use with Samsung native apps.

Categories

Resources