EDIT: this has noting to do with a software upgrade, but is a hardware problem on my device. This post can be deleted.
After an upgrade, I noticed my capacitive buttons were not working after a little while.
Only after a power cycle, they are usable again, but not for too long.
I suspect Android disable them when the "Helicopter home button" occurs.
I found some solutions:
Solution 1: Install "Soft keys" from the Play Store. The buttons are set on top of the display, and for some uses, they sometime get in the way (while using keyboard for example), and you have to reduce the size and have small fingers. It is possible to switch long press to change location.
Solution 2: Tell the system to use Nexus-like Buttons. That way, the buttons are not displayed on top of the screen, but, the screen resolution is reduced and the buttons are set below it. No app to install. Pro: the buttons don't get in the way.
I found a guide here: https://mgeeky.com/how-to-get-nexus-like-buttons-in-any-android-phone/
Add "qemu.hw.mainkeys=0" at the end of /system/build.prop, and reboot. You need an file explorer with an editor and root access. I use Cyanogenmod 12.1, the File explorer has all what's needed.
Optional: Turn Capacitive buttons Back-light off in the system menu. On my system, it is in "buttons"->"backlight"
Maybe it can help someone here.
sadly this does't work on Sense roms
Related
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.
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)
I got my OnePlus One 64 GB, Indian edition (so no updates from CM) 2 days ago. I quickly switched to software keys (creature of habit, previous phone had them). My personal preference for software navigation keys is to place the back button on the right side and the multitasking one on the left, plus a rightmost toggle for search button/magnifying glass (I find this configuration very productive). I use the following process to change them:
1. Settings->Buttons
2. Software buttons layout->Lock icon
3. Make changes->Lock icon again to save changes
The said changes are reflected, and I'm able to observe them.... until the device locks. After unlocking, the software keys are reset to the default configuration: back key, home and multitasking button. I've tried rebooting the device and it doesn't help. Only thing I've changed in the device is switching to ART, everything else is stock. Can't wrap my head around the issue, so any help would be appreciated. Thanks!
Hello Everyone,
I don't know if I am missing something, but since the button on the Blu Pure XL do not light up... I wanted to add the bottom navigation bar with the back home and switch button but I can't!
I have installed Google Now Launcher... Nothing.
I have Nova Premium... Nothing.
Any suggestions?
Thank You
My buttons never light up even if I use another launcher .. if I hold the phone a certain way in the light - i can see them. But I have a general idea where they are so I just press the general area. Most times I hit it .. sometimes it takes a couple of taps.
jaybirdhawaii said:
My buttons never light up even if I use another launcher .. if I hold the phone a certain way in the light - i can see them. But I have a general idea where they are so I just press the general area. Most times I hit it .. sometimes it takes a couple of taps.
Click to expand...
Click to collapse
I am aware that the buttons do not light up... i am trying to add the navigation bar at the bottom of the screen (on screen, software), so I would not have to worry about the hardware buttons.
dkokkos said:
I am aware that the buttons do not light up... i am trying to add the navigation bar at the bottom of the screen (on screen, software), so I would not have to worry about the hardware buttons.
Click to expand...
Click to collapse
I have just done this so it is confirmed working. First off you need to be rooted and have busybox installed. And if you are rooted you have twrp installed so I would recommend doing a backup. Anyway download a app called soft buttons from the play store. Open the app, open menu go down to capacitive keys menu open that and click on disable capacitive keys. Once all the permissions stuff stops popping up on the screen open menu and click on virtual keys menu then click on enable virtual keys. Wait till all the permissions stop popping up on the screen then reboot your phone. Once your rebooted you will have virtual menu buttons and your regular capacitive keys will be disabled so you don't hit them on accident.
There are also options to reverse the process a far as re enabling capacitive keys and disabling virtual keys as I have decided to do because I'd rather have the 1/4 inch or whatever of screen that it takes up.
A little tip for the ones who hold the phone in their left hand and need to switch the .back button with the multitasking one. I am right handed but, as a long time user of Note series phones, I usually hold the phone in my left hand and the stylus with the right one...Now with the s7 edge I miss the stylus, but still the phone is in my left hand.
Root required..
With your favourite root browser navigate to /system/usr/keylayout and open Generic.kl as a text file.
Move to key 158 and replace BACK with APP_SWITCH, then look for APP_SWITCH , that is key 254, and replace APP_SWITCH with BACK.
Just save and reboot.
Obviously it is fully reversible.
Please note that this is not the same result you can get with all in one gestures app, both because it continuously runs in the background (while my tip remaps the keys once forever) and, once you switch the two keys with such app, you loose the screen you usually get when you long press the multitasking button. I mean the screen that displays the app you are using in the upper part of the screen and the choice for the other apps in the lower part.
Not to mention that this solution still is cleaner than installing xposed framework and any dedicated module.
Simple and useful
If your rom settings don't have the choice to remove keys backlight, look for galaxy button lights 2.
For lazy people.
Flash in recovery.
lucaoldb said:
A little tip for the ones who hold the phone in their left hand and need to switch the .back button with the multitasking one. I am right handed but, as a long time user of Note series phones, I usually hold the phone in my left hand and the stylus with the right one...Now with the s7 edge I miss the stylus, but still the phone is in my left hand.
Root required..
With your favourite root browser navigate to /system/usr/keylayout and open Generic.kl as a text file.
Move to key 158 and replace BACK with APP_SWITCH, then look for APP_SWITCH , that is key 254, and replace APP_SWITCH with BACK.
Just save and reboot.
Obviously it is fully reversible.
Please note that this is not the same result you can get with all in one gestures app, both because it continuously runs in the background (while my tip remaps the keys once forever) and, once you switch the two keys with such app, you loose the screen you usually get when you long press the multitasking button. I mean the screen that displays the app you are using in the upper part of the screen and the choice for the other apps in the lower part.
Not to mention that this solution still is cleaner than installing xposed framework and any dedicated module.
Simple and useful
If your rom settings don't have the choice to remove keys backlight, look for galaxy button lights 2.
Click to expand...
Click to collapse
Thanks this working perfectly