Hi my qwerty keys a,q and menu keys are not working.. is there any app or adb way so that i can remap my keys to unused ones.. i searched google but i could not find anything.. Please can anyone help me.. i g1 is rooted 1.6 running cyanogen 4.2.15.1..
Same here, I really don't know whats up with my phone and why it randomly changed mapping but I can't use my phone at all anymore. Anyone know anything on this problem?
my right shift key is in the same situation as you for my g1.
Sorry to say, the only way to do this is to make a custom map for the keys and rebuild the kernel. :/
How can I do that?
Hi
i just found it in some forum , sorry i could not allowed to post the link.. I have tried it its working.. below are the steps to do.. You need to backup your existing keyboard layout.. then change the layout keys then re-upload the files..
below steps are for mapping search key to call key..
1. You have to be root.
2. backup all your files from /system/usr/keylayout/ by runing the following commands in ADB:
Code:
adb shell
mkdir /sdcard/KB_BK
mkdir /sdcard/KB_MODDED
cp -f /system/usr/keylayout/* /sdcard/KB_BK
3. Mount your sdcard as Memory card and COPY the folder /sdcard/KB_BK
4. Edit with notepad++ or wordpad such the keyboard files and change the second element of the key to your likings, CHANGE
Code:
key 127 SEARCH WAKE_DROPPED
key 217 SEARCH WAKE_DROPPED
TO for ex.
Code:
key 127 CALL WAKE_DROPPED
key 217 CALL WAKE_DROPPED
5. save your modification.
6. upload the modified files in /sdcard/KB_MODDED
7. Replace your files from /system/usr/keylayout/ with your modified files from /sdcard/KB_MODDED
Code:
adb shell
su
mount -o remount,rw /dev/mtd/mtdblock6 /system
cp -f /sdcard/KB_BK/* /system/usr/keylayout/
chmod 644 /system/usr/keychars/*
chmod 644 /system/usr/keylayout/*
mount -o remount,ro /dev/mtd/mtdblock6 /system
ATTENTION WATCH OUT FOR THE FILES PERMISSIONS AND BE SURE THEY ARE THE SAME AS THE ORIGINAL
8. Reboot
9. Enjoy
Hope this will help someone..
all credits goes to Geniusdog254 and jay..
nice find
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Related
RESOLVED
Dear developers,
I need to make send hardware button work for the menu, because the long press windows make me crazy recalling the current applications instead to give me the real useful menu for the app I use.
I currently use desire on hd2. So searching in the previous posts I found that I can change /system/usr/keylayout/qwerty.kl
No way, I opened Astro, did not change and save the modifications. Then I tried to download a terminal emulator. Do not give me #, but I thought was normal reading other posts(the phone is already rooted) so I tried chown and chmod, but I do not what I have to write to do the trick of edit with ASTRO the 2 lines I need to put the menu (for the apps) in SEND hw button. Furthermore trying using $ ls -latr I discovered that the qwerty.kl is a link that refer to etc/keymap directory. So I tried to use ASTRO to edit the file but also if tell me save, there are not modification, simply the file is not edited.
resolved --> I HAD TO COPY IN SDCARD THE FILE QWERTY BEFORE to MODIFY WITH ASTRO, no need of chmod && Chown
Here is a little guide on how to disable the screen from turning on in your pocket by accidentally clicking the home key. Which can set off unwanted calls/txts/homescreen changes/etc.
Perhaps there is an easier way, but this works for me, and sharing is caring
There I obtain a copy of Root Explorer, its easy for me to do. For those of you who are too cheap, scroll a bit further down this post, both methods require, obviously, root access:
I have no idea if there are free programs with the same usabilities as root explorer
Method with Root Explorer (or similar?)
Open Root Explorer
Go to /system/usr/keylayout
Click on the button ‘Mount R/W’ (upper right)
Locate, press and hold es209ra_keypad.kl file
Select ‘open in text editor’
Find this line:
key 102 HOME WAKE_DROPPED
Remove the WAKE_DROPPED, so that the end result is:
key 102 HOME
Save the file
Reboot
Done
Method without Root Explorer
You need a little understanding of adb.exe
Typ in cmd.exe:
adb pull C:\es209ra_keypad.kl /system/usr/keylayout/
Go to C:\ and open es209ra_keypad.kl in wordpad
Change:
key 102 HOME WAKE_DROPPED
to:
key 102 HOME
Save the file
Typ in cmd.exe:
adb shell
#su
#mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
(ONLY if you got an error, while trying to remount)
[*]Typ in adb shell:
[*]#cat /proc/mounts
[*]and search for 'system' in the mount list to check correct path for ‘/dev/block/mtdblock2 /system’. If it differs, alter the above line.
Typ in adb shell:
#exit
adb push C:\es209ra_keypad.kl /system/usr/keylayout/
Reboot your phone
This should work... if it doesn't, just leave a comment, and I'll probably try to help you.. that is, if I'm in a good mood..
I attached my es209ra_keypad.kl, just for reference purposes I guess, or for people who are too shy to pull stuff from their phone.
thanks for this!! i have been after a few key tweaks for a while!! don't suppose you have any idea how to make the back key "kill" foreground app!!
2.1 optimised 2.1.67
good idea
thanks for sharing this
[Q] Disable wakeup using home button? [SOLVED]
Use Search next time
prewed said:
[Q] Disable wakeup using home button? [SOLVED]
Use Search next time
Click to expand...
Click to collapse
Aren't you just mister friendly? Thank god we got guys like you on this forum, otherwise this place would be fun.
I did use search, so unfortunately for you. I could not find a correct guide explaining step by step how to do it WITHOUT root explorer
xx
[email protected] said:
thanks for this!! i have been after a few key tweaks for a while!! don't suppose you have any idea how to make the back key "kill" foreground app!!
2.1 optimised 2.1.67
Click to expand...
Click to collapse
no problem, ill try to find out if it is possible in 2.1, i think its in the framework though. It's already embedded in 2.2 and 2.3 (long press back), so you can try a custom ROM ?
Hi there!, first of all, I'm from Argentina, and my english is not so good (sorry!).
If you have a querty hardware keyboard (like all MS2 in Argentina) you must to fix the keyboard layout after updating from Froyo.
What we are goning to do, is replace the keyboard layout files with ones that came with Froyo. I'ts worked for me.
I assume that you are root.
Follow this steps.
1) Download the attachment file and unzip it.
2) Copy the two files to the SDCARD.
3) Open shell via adb and make /system/ writable.
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
4) Copy qwerty.kl to /system/usr/keylayout/
Code:
cp /sdcard/qwerty.kl /system/usr/keylayout/
5) Copy qwerty.kcm.bin to /system/usr/keychars/
Code:
cp /system/usr/keychars/qwerty.kcm.bin /system/usr/
6) Set /system back to read-only and reboot
Code:
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
7) That's it, I toked some things from [HOW-TOW] change hardware keyboard from the ms2ginger to qwertz (http://forum.xda-developers.com/showthread.php?t=1216299), thanks to schuck_norrisch.
Altlock working?
In "d alt" is ₤, or $?
Thanks
Sent from my Milestone 2 with GingerBread
PetrusDLX said:
Altlock working?
In "d alt" is ₤, or $?
Thanks
Sent from my Milestone 2 with GingerBread
Click to expand...
Click to collapse
I have the same problem.
I did http://forum.xda-developers.com/show....php?t=1216299 and all the keyboard seems to be ok except the ALT D, wich is £, not $.
Those files correct this?
levicm said:
I have the same problem.
I did http://forum.xda-developers.com/show....php?t=1216299 and all the keyboard seems to be ok except the ALT D, wich is £, not $.
Those files correct this?
Click to expand...
Click to collapse
For me its ok, alt+d is $. I don't now why in your case is diferent. I suppose that maybe the language, i use spanish (spain). Try change it and try again. Please post the results. Tnx
Im a galaxy s6 user here, I found out that the switch recent app button (the one on the left of the home button) quite annoying while playing game like vainglory because I misclicked it quite often. After doing some research I found out that it is possible to comment out the key 254 of generic.kl under system/usr/keylayout, then i come out with an idea of creating a new generic.kl which commented out the key 254, then with a click of button on my app it will move the file with the commented key to system/usr/keylayout to replace the old way, vice versa, I will make a restore button there to restore it will the original generic.kl when I wan the recent app switch to start working again. So my question here is what would be the code to move a file to system and replace it? I do have some basic android programming knowledge and my phone is rooted.
Thanks in advance.
if your phone is rooted.
step 1:get root permission
exec command : su
step 2:mount /system to writeable
exec command : mount -o rw,remount /system
step 3:replace file
Hi Folks!
I created a QWERTZ keylayout for the Logitech K830.
This works on every FireTV, every firmware and every android device IF YOU HAVE ROOT
DOWNLOAD
See Attachments
INSTALL
1. mount system Read-Write
2. copy Vendor_046d_Product_c52b.kl to /system/usr/keylayout
3. chmod 644 /system/usr/keylayout/Vendor_046d_Product_c52b.kl
4. if needed chown 0:0 /system/usr/keylayout/Vendor_046d_Product_c52b.kl
4. copy Vendor_046d_Product_c52b.kcm to /system/usr/keychars
5. chmod 644 /system/usr/keychars/Vendor_046d_Product_c52b.kcm
5. if needed chown 0:0 /system/usr/keychars/Vendor_046d_Product_c52b.kcm
6. reboot
NOTE
This Layout basically applies for the Logitech Unified Receiver so this keylayout will work for every keyboard using the Unified Receiver as for example the K400 from Logitech .
All the magic happens in the key character map and the layout file is just a cleaned generic one with two tweaked buttons. And because i use a cleaned keylayout file some buttons on other keyboards might be wrong or even missing.
If this is the case delete the layout file (Vendor_046d_Product_c52b.kl), reboot and try again. Most things should work now.
You can also use the tool "evtest" to debug the layout file if you wish to.
HINT
If you have a other keyboard and know the Vendor and Product ID you can rename the key character map / keylayout accordingly to get QWERTZ layout.
You could even use the kcm file as Generic.kcm and so on. I haven't done it this way because i just didn't want to.
Works great with my K400.
Thanks for the info.
Hi and thank you very much! The attached files seem to be missing, can somebody please reupload them?
Thanks,
Nico
@niggonet Reuploaded attachement in first post
WheelchairArtist said:
@niggonet Reuploaded attachement in first post
Click to expand...
Click to collapse
You are the man! My hero!
Been looking for this option since months!
Here are some 'ready to copy and paste' instructions (just replace the PATH_TO_FILE):
Bash:
adb push "C:\[PATH_TO_FILE]\Vendor_046d_Product_c52b.kcm" /sdcard/Vendor_046d_Product_c52b.kcm
adb push "C:\[PATH_TO_FILE]\Vendor_046d_Product_c52b.kl" /sdcard/Vendor_046d_Product_c52b.kl
adb shell
su
mount -o rw,remount /system
mv /sdcard/Vendor_046d_Product_c52b.kcm /system/usr/keychars/Vendor_046d_Product_c52b.kcm
mv /sdcard/Vendor_046d_Product_c52b.kl /system/usr/keylayout/Vendor_046d_Product_c52b.kl
chmod 644 /system/usr/keychars/Vendor_046d_Product_c52b.kcm
chown 0:0 /system/usr/keychars/Vendor_046d_Product_c52b.kcm
chmod 644 /system/usr/keylayout/Vendor_046d_Product_c52b.kl
chown 0:0 /system/usr/keylayout/Vendor_046d_Product_c52b.kl
reboot
Second block is not neccessary when using ADB over TWRP.
Thank you - much appreciated,
Nico