[Q] enabling capacitive buttons - Galaxy S III Q&A, Help & Troubleshooting

ive read on other threads that you can disable the capacitive buttons on the GT-i9300 by going inputting '#' in front of lines 'key 132 back' and 'key 158 menu'. however when i remove the '#'s my capacitive buttons still stay disabled. how to i re enable them?

remove the #, check the permissions and reboot

ive removed the '#'s but i dont know what you mean by the permissions. is that superSu? if it is ive rebooted the phone and still they wont work.

check the file permissions with a file manager and make sure they're so the same as the other files in the folder

Glebun said:
check the file permissions with a file manager and make sure they're so the same as the other files in the folder
Click to expand...
Click to collapse
Thank you sooo much!! it worked

Related

[Q] ICS Lockscreen missing

My lockscreen isnt there... I updated to ICS and it was there for a while but now whenever i press the button to turn my phones screen on it skips the lock screen.
I miss it ;(
anyone know how to get it back
Settings/security/screen lock
Im having the same issue, never get the lockscreen on any ICS Rom, do i need to odin to stock ICS and then root and reinstall the Rom?
Go to settings, security and then choose lock screen type you want.
oops! accidentally beamed from my awesome NEXUS S!
Che k to see if you have a timeout set. I have mine on immidiate so wheb i push the button it locks right away.
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
If u have 14 toggle in ur notifications bar, try swiping to the right and hit lock icon... Might have bumped it by accident ;-)
Sent from my SAMSUNG-SGH-I717 using XDA
nope tried both of those still getting nothing...ive tried reinstalling the ROM about 4 times already...everything works but i just cant get the lockscreen to come up...
deadbeatcocoa said:
I figured out my problem! Appears that when I was creating the keystr file, I added the extension .txt ...
So here is the solution that have been posted on other threads
i actually figured out a way to restore my lock screen back.
Note: This involves messing with the efs folder. So do this at you own risk
also, your phone must be rooted in order to do this.
Tools Needed:
1. Hex Editor
2. Root Explorer
Steps to restore:'
1. Using root explorer locate the /efs/imei/ folder. In that folder there should be a file called keystr. In my case the file was missing which is why the lock screen was missing and was causing my problems.
2. using root explorer create a new file called keystr
3. also in root explorer open the file keystr in text editor and type ON
4. now go into hex editor and locate the /efs/imei/keystr file.
5. using hex editor the first two values in green should be 4f and 4e. all others should be 00.
6. make sure you save the file.
7. reboot.
Click to expand...
Click to collapse
Here you guys are! this is the only method that works, i tried everything, do this and reboot your phone a couple times, make sure the file stays there and enjoy your lockscreen!

[Q] Tried every possible solution, home screen button and lock screen still broken

Hi guys, please help me
Home button, lock screen not working , and pressing the power button does not pops the menu . I know this is something to do with the keystr
but my keystr is there in imei folder.
I read the threads and found some solutions
1) I tried using the terminal emulator method. Doesn't work
2) Tried using the root explorer method (deleted the keystr, added new file and making sure the file is ON )
Help
3) I read in some forum about using Hex editor can anyone tell me how do I do this?
Please help. Thanks
P.s. I actually fixed the problem but it came back again after a few days.
extremeken said:
Hi guys, please help me
Home button, lock screen not working , and pressing the power button does not pops the menu . I know this is something to do with the keystr
but my keystr is there in imei folder.
I read the threads and found some solutions
1) I tried using the terminal emulator method. Doesn't work
2) Tried using the root explorer method (deleted the keystr, added new file and making sure the file is ON )
Help
3) I read in some forum about using Hex editor can anyone tell me how do I do this?
Please help. Thanks
P.s. I actually fixed the problem but it came back again after a few days.
Click to expand...
Click to collapse
If the file already exists and contains ON, also make sure the permissions on the file are at least 644, or rw-,r--,r--.
ctomgee said:
If the file already exists and contains ON, also make sure the permissions on the file are at least 644, or rw-,r--,r--.
Click to expand...
Click to collapse
how do i check this? thanks
extremeken said:
how do i check this? thanks
Click to expand...
Click to collapse
Root explorer, long click the file, permissions.

[Q] Changed Generic.kl file, power button and volume down button don't work, help?

I was trying to change some key configurations and someone had said to modify the system/usr/keylayout/generic.kl file so i did. Anyway after doing so i could no longer use my power button or my volume button. I tried to undo the changes set it back exactly the way it was but still nothing. I also asked someone to send me an untouched copy of the file and i pasted that back in but still to no avail. Any help at all would be extremely appreciated! Thanks!
OBO786 said:
I was trying to change some key configurations and someone had said to modify the system/usr/keylayout/generic.kl file so i did. Anyway after doing so i could no longer use my power button or my volume button. I tried to undo the changes set it back exactly the way it was but still nothing. I also asked someone to send me an untouched copy of the file and i pasted that back in but still to no avail. Any help at all would be extremely appreciated! Thanks!
Click to expand...
Click to collapse
Did you set the permissions on the file correctly?
tech_head said:
Did you set the permissions on the file correctly?
Click to expand...
Click to collapse
As i have no idea what that means I'm certain I didn't. How would I go about doing that?
Help
Did you ever fix this? I had the same happen to my cool pad and I even tried changing the permission to rw r r

[Q] .kl file issues

I've been running my xperia Z2 for a month or two now and one of the first things I did was disable the camera button, and attempt to rebind it to a different button in the .kl files within system/usr/keylayout. Initially, it worked great. I commented out the key 212 camera in a few files with a #, and added a new line.
It's been a month or so since then and I hadn't been using the camera button and all, and recently I've noticed that the kl file changed back in one of my restores to just being commented out, so the camera button is now non functional. I attempted to add a line of code to change the camera to media next like this: key 212 MEDIA_NEXT, but was getting no response after restarting my phone. I removed the line, deleted the comment on the previous line in every file that I had disabled it in, and restarted the phone. Camera is still non functional even after confirming it stayed unchecked.
After this, I attempted to copy all of the files to my SD card and mass edited every single camera key reference to media_next for the sake of testing, and the button was still disabled. I completely purged my .kl files, and uploaded notepad++ edited copies and restarted my phone. None of my buttons worked. I did a restore from my SD card backup, and nothing worked after restarting, still. I did a backup from a TWRP backup and everything is functional again... however, I'm left wondering why my .kl files might not be reading.
I apologize for the long post, but I'm trying to understand where I've went wrong. I'm on a stock bell rom(canadian) firmware 4.4.2 model D6503 build 17.1.A.2.55. I'm rooted, with only minimal modifications to the device(cydia substrate, xposed framework using rootcloak, youtube adaway, a radio modification to allow headphoneless scanning and xposed additions).
Does anyone know where I might've went wrong? My end goal is to rebind a controller's R2(simple button) controller to the R2 axis as well as button press, so if anyone has any information on rebinding a key to a maxed out axis I would appreciate information on that as well(Eg. R2 key 105 to RTrigger 1.0 + key 105).
Not sure
Perhaps copy a working existing file and try from there
I had trouble understanding your problem
Envious_Data said:
Not sure
Perhaps copy a working existing file and try from there
I had trouble understanding your problem
Click to expand...
Click to collapse
I've restored a CRM backup and the .kl files all work great, but when I attempt to modify the files they don't seem to update any system functions or buttons unless I'm just disabling the button. Even if I copy the file to another directory, break all the buttons then overwrite it with the copy and restart, the buttons stay disabled until I restore a CRM recovery.
I hope that's a little easier to read, the phone just doesn't seem to update its internal system with button definitions except to disable them, and I'm trying to figure out why.
Zarreck said:
I've restored a CRM backup and the .kl files all work great, but when I attempt to modify the files they don't seem to update any system functions or buttons unless I'm just disabling the button. Even if I copy the file to another directory, break all the buttons then overwrite it with the copy and restart, the buttons stay disabled until I restore a CRM recovery.
I hope that's a little easier to read, the phone just doesn't seem to update its internal system with button definitions except to disable them, and I'm trying to figure out why.
Click to expand...
Click to collapse
Just a thought, not pretty sure.
When you are copying files from sd-card, you should also check for correct permissions.
Your permissions must match with original files, otherwise it may create an issue.
mvv1277 said:
Just a thought, not pretty sure.
When you are copying files from sd-card, you should also check for correct permissions.
Your permissions must match with original files, otherwise it may create an issue.
Click to expand...
Click to collapse
I hadn't even thought of that, thank you, I'll try that out

[GUIDE] Customize Bixby button in custom ROMs

For whoever is using a custom ROM and the bixby button is either disabled or cannot customize with the usual Bixby remap app, I have found a solution: (Root needed for #1, #2 works without root)
>Solution #1 (First try this, if it doesn't work - it didn't work for me for some reason - try solution #2):
With tips from the community, I have found these possible locations to edit the bixby key. Use root file explorer:
- /root/system/usr/keylayout/gpio_keys.kl
- /system/usr/keylayout/Generic.kl
- /vendor/usr/keylayout/gpio_keys.kl (?)
Search for key 703 in each of these files. If it does not exist, try to add it manually. Effects take place after a reboot.
Use this guide here for more details: https://forum.xda-developers.com/t/...on-with-simple-double-and-long-press.3839544/
>Solution #2 - Button Mapper: Remap your keys (Not my app)
First, try to see if you can remap the bixby key with this app. For me, it did not work again, but I found a nice workaround:
In the app, instead of changing "Bixby Button", go to "Add Buttons". Now, press the bixby key. The app should detect the key, and finally you can set it to whatever you want.
(But keep in mind, for this option, it is necessary to purchase the pro version).
FoxTheLegend said:
For whoever is using a custom ROM and the bixby button is either disabled or cannot customize with the usual Bixby remap app, I have found a solution: (Root needed for #1, #2 works without root)
>Solution #1 (First try this, if it doesn't work - it didn't work for me for some reason - try solution #2):
With tips from the community, I have found these possible locations to edit the bixby key. Use root file explorer:
- /root/system/usr/keylayout/gpio_keys.kl
- /system/usr/keylayout/Generic.kl
- /vendor/usr/keylayout/gpio_keys.kl (?)
Search for key 703 in each of these files. If it does not exist, try to add it manually. Effects take place after a reboot.
Use this guide here for more details: https://forum.xda-developers.com/t/...on-with-simple-double-and-long-press.3839544/
>Solution #2 - Button Mapper: Remap your keys (Not my app)
First, try to see if you can remap the bixby key with this app. For me, it did not work again, but I found a nice workaround:
In the app, instead of changing "Bixby Button", go to "Add Buttons". Now, press the bixby key. The app should detect the key, and finally you can set it to whatever you want.
(But keep in mind, for this option, it is necessary to purchase the pro version).
Click to expand...
Click to collapse
I installed Magisk and Root Explorer. I don't have 703. Since I don't know English well, the instructions on the link are complicated for me. Can you briefly explain to me how to get Bixby to launch the desired application with one click? Thank you in advance.
ZmisiS said:
I installed Magisk and Root Explorer. I don't have 703. Since I don't know English well, the instructions on the link are complicated for me. Can you briefly explain to me how to get Bixby to launch the desired application with one click? Thank you in advance.
Click to expand...
Click to collapse
Same problem as me, I didn't find 703 anywhere.. you can try manually adding it though, maybe it will work. Like:
key 703 CAMERA
save, reboot device, check if works.
Remember to save file with .kl extension, not .txt, or buttons wont work
FoxTheLegend said:
Same problem as me, I didn't find 703 anywhere.. you can try manually adding it though, maybe it will work. Like:
key 703 CAMERA
save, reboot device, check if works.
Remember to save file with .kl extension, not .txt, or buttons wont work
Click to expand...
Click to collapse
I don't know how can try manually adding it though? What do I need to write to start Bixby button to save?
ZmisiS said:
I don't know how can try manually adding it though? What do I need to write to start Bixby button to save?
Click to expand...
Click to collapse
if as you said you cant find anywhere "703" in the file, write at the end just like the others, (you can open and edit the file straight away from the root explorer)
key 703 [desired command]
for example
key 703 CAMERA
then save file and reboot phone. If it works, after pressing the bixby key the default camera app should open.
Some people say it works, for me it didn't work though.
FoxTheLegend said:
if as you said you cant find anywhere "703" in the file, write at the end just like the others, (you can open and edit the file straight away from the root explorer)
key 703 [desired command]
for example
key 703 CAMERA
then save file and reboot phone. If it works, after pressing the bixby key the default camera app should open.
Some people say it works, for me it didn't work though.
Click to expand...
Click to collapse
It didn't work for me either. I worked like that, but I also typed something like this, but without success.
# input_fw Intelligent Key for Dream
key 703 CAMERA
When I change everything, I save it, after that I change the txt name to kl. It needs Check Permissions after that, and I don't see it in Root Explorer. Maybe you need to go to Settings, select the app and check the permissions? I do not know.
ZmisiS said:
It didn't work for me either. I worked like that, but I also typed something like this, but without success.
# input_fw Intelligent Key for Dream
key 703 CAMERA
When I change everything, I save it, after that I change the txt name to kl. It needs Check Permissions after that, and I don't see it in Root Explorer. Maybe you need to go to Settings, select the app and check the permissions? I do not know.
Click to expand...
Click to collapse
Weird - first check in Magisk that root explorer has root permissions. Second try to edit the file at once without first chaning to .txt - most editors support it, no need to change. If that still doesnt work, try a different root file explorer app. For me worked "root browser".
FoxTheLegend said:
Weird - first check in Magisk that root explorer has root permissions. Second try to edit the file at once without first chaning to .txt - most editors support it, no need to change. If that still doesnt work, try a different root file explorer app. For me worked "root browser".
Click to expand...
Click to collapse
Root Explorer works for me. The system is rooted, and I confirmed it when I opened Root Explorer. You say it didn't work for you. Neither did I. I did everything according to the instructions.
FoxTheLegend said:
- /vendor/usr/keylayout/gpio_keys.kl
Click to expand...
Click to collapse
FoxTheLegend said:
It Worked for me. Big Thank You!
Click to expand...
Click to collapse

Categories

Resources