http://forum.xda-developers.com/showthread.php?t=1535915
I tried this today, but instead of making walkman button as search button I tried to make it open POWERAMP.
But after that, I noticed that my home button stopped working
So I tried to replace the original file back, but it didn't worked
Then I tried to edit Generic.kl file, but after that now my keys doesn't work at all (including volume buttons, camera button, home button...)
I replaced all files back, made cache wipe, dalvik cache wipe, made settings reset but still nothing works.. :/
Can someone help me? (I don't want to wipe all data in my phone)
outoflock377 said:
http://forum.xda-developers.com/showthread.php?t=1535915
I tried this today, but instead of making walkman button as search button I tried to make it open POWERAMP.
But after that, I noticed that my home button stopped working
So I tried to replace the original file back, but it didn't worked
Then I tried to edit Generic.kl file, but after that now my keys doesn't work at all (including volume buttons, camera button, home button...)
I replaced all files back, made cache wipe, dalvik cache wipe, made settings reset but still nothing works.. :/
Can someone help me? (I don't want to wipe all data in my phone)
Click to expand...
Click to collapse
What ROM are you on? I doubt that simply putting Poweramp would do the trick for the Walkman button.
NOTE: On the WT19i, the only file you need to modify is pm8058-keypad.kl
1) Restore those files you modified : If you used Root Explorer to change those files, you can restore the originals simply from the .BAK files that RootExplorer creates by default. If not, simply copy those .KL files from your ROM's ZIP. (You may use some root explorer to copy the files that you modified. Make sure that permissions are properly set: rw-r--r--)
2) Goto: /system/usr/keylayout/ The only file you need to modify is pm8058-keypad.kl. Do not modify any other file. In front of key 200,(walkman key) write SEARCH. Save and exit. If you're on Cyanogenmod 7, from Cyanogenmod Settings, you can change the Search key behavior to launch a custom app(just look around the menus)
3)On CM9, this feature is not available(however you can still use predefined actions such as SEARCH or MUSIC(which will launch Apollo).
Related
I know im late but this is a bit confusing for me. I have rooted my x10 and according to "rootchecker" I also have busybox installed.(tho I can't find the busybox icon in my menu, it's just the superuser) Now I've seen some mods that requires me to flash the files via xrecovery. For example Bravia Engine, FPS Uncap, X-loud.
Now my question is when I open those file it has two folders "META-INF" and "System" now how do I put this into my phone?
Methods & Problems:
xRecovery - How do I flash the .zip file via xrecovery? Should I put it in my sd card and from the xrecovery mode press "Install update.zip from SD card"?? If yes then where in SD card? And Do I have to rename it as update.zip when I put it in my SD card?
Changing Value - There are some apps that requires changing value of my build.props. But when I change the value and try press tab to save, the save tab doesn't show (I mean I can't click on it). Then when I press back there's two option of "save" and "Discard" but when I save it and then re-enter into my build.props the value gets back to its original state. It doesn't change??
Unpacking - It says in a topic "Unpack all of the files to the relevant folders on your mobile" - What relevent folder? the folder it has in the zip file is not present in my sd card (I can see those folder via astro manager and I tried to copy/paste those folder into my sd and then via asto I tried to replace each original file that I have in my phone but it doesn't work, it doesn't let me paste it)
Sorry if this sounds stupid to you guys but I'm new to android and I'm having problem getting things right. So if any of you would help me through this issue step by step it'd be greatly appreciated.
To install those kind of things you have to use flashtool to add xrecovery to your phone, then you have to copy the .zip file in the sd card then turn off your phone and turn it back on when you get the sony ericsson logo start hitting the back key repeatedly till you go in xrecovery mode, use volume keys to go down and menu key to select, select the option install custom zip... then select install from sd card, then select the zip, and then select yes... let it install it and once is finish remove the battery and put back in, turn on your phone and the bravia, xloud or whatever zip you installed should be already running
Sent from my X10i using XDA App
To change the values in build.prop I recommend the use of Root Explorer,
Go to the folder \system\, tap on the grey button at the top of your screen, that says "Mount R/W", (after tapping it will read "Mount R/O". This will make the copying in root-folders possible, too.... you have to have changing-rights (read-write) to copy things into root-folders.
Then long-click on build-prop, scroll down and choose "Open in Text editor", change whatever you must change, and click left-hardware-button and after that choose "Save and Exit". The Root Explorer will make (and announce) a backup-copy named "build.prop.bak".
This should work.
Good luck, greetz,
kwarkje
And hey, it's not stupid, we all began as noobies, you know...
J!K said:
To install those kind of things you have to use flashtool to add xrecovery to your phone, then you have to copy the .zip file in the sd card then turn off your phone and turn it back on when you get the sony ericsson logo start hitting the back key repeatedly till you go in xrecovery mode, use volume keys to go down and menu key to select, select the option install custom zip... then select install from sd card, then select the zip, and then select yes... let it install it and once is finish remove the battery and put back in, turn on your phone and the bravia, xloud or whatever zip you installed should be already running
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Thanks mate!! it worked
kwarkje said:
To change the values in build.prop I recommend the use of Root Explorer,
Go to the folder \system\, tap on the grey button at the top of your screen, that says "Mount R/W", (after tapping it will read "Mount R/O". This will make the copying in root-folders possible, too.... you have to have changing-rights (read-write) to copy things into root-folders.
Then long-click on build-prop, scroll down and choose "Open in Text editor", change whatever you must change, and click left-hardware-button and after that choose "Save and Exit". The Root Explorer will make (and announce) a backup-copy named "build.prop.bak".
This should work.
Good luck, greetz,
kwarkje
And hey, it's not stupid, we all began as noobies, you know...
Click to expand...
Click to collapse
Thanx bro...um sure it will work but I can't get root explorer to work
when I install it it takes permission from superuser, I pressed yes and then it says "SORRY!! The application Root Explorer (processcom.speedsoftware.rootexplorer) has stopped unexpectedly. Please try again" [Force Close]
I've tried two different version....
Try es explorer from market.
Ishan Sardar said:
Thanx bro...um sure it will work but I can't get root explorer to work
when I install it it takes permission from superuser, I pressed yes and then it says "SORRY!! The application Root Explorer (processcom.speedsoftware.rootexplorer) has stopped unexpectedly. Please try again" [Force Close]
I've tried two different version....
Click to expand...
Click to collapse
Sent from my X10i using XDA App
Mod is working great but these touch wiz keys are disgusting looking especially when the menu key shows up. It moves all the buttons out of order.
Does anyone know of a way to flash the stock Android buttons. Thank you!!
Pretty sure all you have to do is replace tw_navigationbar back home menu and recent both pressed and hormal with the stock ones and recompile the apk then you could either put it on your phone and put it in with a file explorer or you could try making a flashable zip.
ok where would i find these files?
If you know how to use adb you can use the adb pull command to pull the framework-res.apk which is where you'll find the files if you don't you can use a file explorer to copy them to your sd card or somewhere that you can find them then you would need to decompile them then replace the files I mentioned above with the stock ones
ok so i did it through root explorer. inside the franwork apk. i went to res/drawable, res/drawable-hdpi and res/drawable-xhdpi. these three folders all contained the files u said like tw_navigationbar_back_normal and one that says pressed instead of normal. png files. Do I just replace these pngs with the stock ones or is there more to this? Thanks
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
Hello guys!
Can someone help me solve my problem?
I ported a ROM to my device. But there are stock button actions from port device.
I tried to replace whole Keylayout folder to fix it, but it's still the same..
How can I remap my buttons? I tried to edit Generic.kl, but the keys are still from port device.
my back button action is to go back.
my middle hardware button action is to go back (I want it to go home) and on long click is recentapp (I want search)
my recentapp button (on the right side) action is to go to the menu (apps menu) but I want it to see recent apps.
It strange that I replaced whole Keylayout folder from my stock ROM with all files inside and it's still the same..
Is there any other LIB or file that should I replace?
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