Hi, I have a Galaxy note 3 Sm-N9005 european version, I was trying to edit the gpio-keys.kl in order to disable the volume buttons, I tried adding a "#" before the text, with and without a space after it, I tried changing the "volume_up" to "UNKNOWN" , I tried deleting the "Wake_dropped" part of the line... It doesn't matter what I do, It does nothing.
I even deleted the file (I did a backup previously), rebooted the phone, and the keys still worked.
There is a bizarre problem also. In the process, I renamed gpio-keys.kl to gpio-kksks.kl in order to be able to copy the backup since I was having some trouble. Now I have 2 files, the original gpio-keys file and that renamed file, that if I try to delete, it does nothing. If I open it with a text editor it says "no such file or directory" as a text, and If I delete that text, the file weighs 0,00kb, but it still appears on the system folder.
So 2 questions, what do I do to definitely delete that gpio-kksks.kl file? and what do I do in order to dissable the volume keys? I hope someone can help me.
Thanks.
Related
Anyone else having this issue?
I have Root Explorer purchased and installed. I am trying to remove/rename the start up/start down sounds. It appears that root explorer is in r/w mode for the folder I am in (Sytem/etc) if I delete the file, it shows "file deleted succesfully". I refresh and it is still there. If I try and copy my new file from the internal sd, it says "file copied succesfully" but it does not show up. I have also tried renaming PowerOn.wav to PowerOn.wav.bak and it takes but I cannot rename it to PowerOn.wav. Then if I verify things with Linda file manager, it shows the file still named PowerOn.wav.bak. How come it's not letting me change the files? Also, hitting the button "Mount R/O" does nothing, it always says the same thing, it never changes to "Mount R/W".
I keep hearing people say it works for them but it's not working for me. I am using stock rooted firmware.
works perfect for me with root explorer... I renamed the original to "orig_PowerOn.wav" and then copy the one I wanted into the folder and named it "PowerOn.wav" (no quotes of course)
Well ****! now it's working. ????
Working well for me. I didn't delete default sounds, i moved them to backup on SD.
This same exact issue happened to me 3 nights ago while changing my shutdown animation. I had to re-boot my phone a few times before Root Explorer worked properly.
I am trying to edit the arrays.xml file in the framework-res.apk file to do the hotspot hack, however, when I copy the new framework-res.apk file to my system folder, change permissions to 0644, then move it to framework, the phone crashes and goes into soft brick. Even if I push it over by adb shell and issuing stop, it still soft bricks on reboot. Everything appears to be good, the APK file says completed with no errors, etc. Any thoughts?
NOTE: I know there's a different hotspot hack available, but I was wanting to try something new to me, which is editing the files myself.
rodin95 said:
I am trying to edit the arrays.xml file in the framework-res.apk file to do the hotspot hack, however, when I copy the new framework-res.apk file to my system folder, change permissions to 0644, then move it to framework, the phone crashes and goes into soft brick. Even if I push it over by adb shell and issuing stop, it still soft bricks on reboot. Everything appears to be good, the APK file says completed with no errors, etc. Any thoughts?
NOTE: I know there's a different hotspot hack available, but I was wanting to try something new to me, which is editing the files myself.
Click to expand...
Click to collapse
I don't believe it will work by pushing it into system via a file explorer or adb. I have flashed it using a zip in custom recover, i.e. safestrap. Glad to see someone trying to learn. I commend you for that.
I was able to copy the Verizon framework file over using the same method, and the phone works fine, except there are a few minor issues using that framework (items are not labeled correctly, incorrect ASCII characters in random places on screen, etc.
When I modify the framework file, it sits on the white ATT screen, and flashes "bright to dark" every 10 seconds or so..like it does when it does a normal boot, but it never boots.
Always willing to learn
I'm running the hyperdrive rom and would like to change the menu button to the recent apps button, and the longpress home to google now like S5. I found an xposed module that does this but only for the note 3. Anyone have a solution for this?
Jaydawgx7 said:
I'm running the hyperdrive rom and would like to change the menu button to the recent apps button, and the longpress home to google now like S5. I found an xposed module that does this but only for the note 3. Anyone have a solution for this?
Click to expand...
Click to collapse
I can change the menu key to recent apps but not sure about longpress home.
Using a root File Explorer open generic.kl in system/user/keylayout with a text editor.
Go to key 139 and replace 'MENU' with 'APP_SWITCH'. Reboot and you're done.
For google now it should just be a matter of finding the appropriate key.
marxses said:
I can change the menu key to recent apps but not sure about longpress home.
Using a root File Explorer open generic.kl in system/user/keylayout with a text editor.
Go to key 139 and replace 'MENU' with 'APP_SWITCH'. Reboot and you're done.
For google now it should just be a matter of finding the appropriate key.
Click to expand...
Click to collapse
Thanks for getting me in the right direction here. However, when I alter the generic.kl file at all, both capacitive buttons quit working after a reboot. I tried replacing the altered file with a backup i made, rebooted, and they still don't work. The only way to restore function of the buttons is to reflash the rom. Any idea as to why? This seemed like an easy change.... (also tried editing the file via notepad++ on the pc with the same result)
Jaydawgx7 said:
Thanks for getting me in the right direction here. However, when I alter the generic.kl file at all, both capacitive buttons quit working after a reboot. I tried replacing the altered file with a backup i made, rebooted, and they still don't work. The only way to restore function of the buttons is to reflash the rom. Any idea as to why? This seemed like an easy change.... (also tried editing the file via notepad++ on the pc with the same result)
Click to expand...
Click to collapse
What file explorer are you using? ES explorer?
After editing and especially if you're pasting in a back up you need to make sure the files permissions are set to rw-r--r--
I personally used the text editor from Rom Tool Box Lite . Make sure there aren't any extra spaces and there should be no # in front of the key.
I just remapped and put them back to normal a few times and I'm not having any problems.
Let me know how you get on.
marxses said:
What file explorer are you using? ES explorer?
After editing and especially if you're pasting in a back up you need to make sure the files permissions are set to rw-r--r--
I personally used the text editor from Rom Tool Box Lite . Make sure there aren't any extra spaces and there should be no # in front of the key.
I just remapped and put them back to normal a few times and I'm not having any problems.
Let me know how you get on.
Click to expand...
Click to collapse
Thanks! I was using ES file Explorer... I don't know what happened amongst text editors, but the rom tool box text editor did the trick... I appreciate your time and patience. Now it's time to figure out how to change long press home to Google now... Thanks again
Jaydawgx7 said:
Thanks! I was using ES file Explorer... I don't know what happened amongst text editors, but the rom tool box text editor did the trick... I appreciate your time and patience. Now it's time to figure out how to change long press home to Google now... Thanks again
Click to expand...
Click to collapse
All good, glad you got it sorted.
Another option is home2shortcut it uses double tap instead of long press, just tried it for kicks and it works really well, quite snappy
I'm on the stock rom and I tried following this guy but I'm too dumb to figure out how do anything passed installing a ROM. So instead of following that guy, I tried doing the Nexus 4 method in the link. I probably made a stupid mistake so that's on me. I copied the just the generic.kl file using ES File Explorer and pasted it into a folder outside the system files. I made another copy of the file and started editing one. I pasted the edited generic.kl file back into the root location and restarted my phone. Nothing happened except now my power button doesn't operate correctly. It doesn't wake or put my phone to sleep. What makes this worse is my Knock-On is sorta broken because I dropped my phone so I have to tap about 30~ times to get it to function once. I tried copying the backup I made back into the folder but it didn't change anything. What can I do that isn't a factory reset? Would a factory reset even work? I'm only rooted, no unlocked bootloader.
This is weird.
I bought a T95 box and have been using it with an external keyboard almost flawlessly for months. The only issue was that the Enter key was incorrectly mapped.
I found a guide to fix this, which involved using a root browser to edit a single word in a keyboard mapping file. I installed two root browsers, made the change to the file and then found it wouldn't save due to a "read only file system". I thought I'd change the permissions of the file and then the folder just to make this tiny change, but nothing would do it. Then I looked at the folder, and the file i had been trying to save had been completely blanked - 0kilobytes. Which is weird, as I thought this was a read only file system?
I found another copy of the file and tried to paste it into the folder, but exactly the same problem again -read only file system.
My keyboard is now useless as none of the keys are recognised and I have no way of restoring it to functionality as I can't restore the file that was overwritten on the allegedly "read only file system".
Any suggestions? I guess a factory reset might possibly help, but I've spent the best part of a year setting this device up just right so that has to be a very last resort. Tearing my hair out here...
I managed to delete the 0kb file and paste a replacement in its place, but it too instantly became 0kb. This is surreal.