I just unloacked / rooted and installed CM9 on my HTC Status (US version of the Chacha) and everything is going fine with the exception of the "~" and the "@" are swapped on the keyboard (now the "@" is on ALT-P instead of ALT-Y). I could get used to it, but I'd rather try to fix it.
In other devices I had been able to reassign hardware keys by just editing the keypab.kcm and / or keypad.kl files, but that does not seem to work here.
Here is what I did:
Pulled the chacha-keybap.kcm from the directory /system/usr/keychars ("adb pull /system/usr/keychars/chacha-keypad.kcm"
Edited the kcm file to swap the "@" and "~"
key Y {
label: 'Y'
number: none
base: 'y'
shift, capslock: 'Y'
alt: '@'
shift+alt, capslock+alt: '@'
}
and
key P {
label: 'P'
number: none
base: 'p'
shift, capslock: 'P'
alt: '~'
shift+alt, capslock+alt: '~'
}
Remounted the /System directory as writable ("adb shell mount -o rw,remount /system")
Pushed the file back to the /system/usr/keychars directory ("adb push chacha-keypad.kcm /system/usr/keychars")
Rebooted ("adb reboot")
That didn't work, so I pulled the chacha-keychars.kcm file again to make sure that the updated one was correctly pushed (which it was).
Any suggestions on what I am doing wrong?
Thanks.
Same issues here but my toher keys are also messed up such as the m and n keys when pressing ATL as well as the v key and the question ? Mark key
Sent from my HTC Chacha A810 using Tapatalk 2
---------- Post added at 11:13 PM ---------- Previous post was at 11:07 PM ----------
Moe92 said:
Same issues but my toher keys are also messed up such as the m and n keys when pressing ATL as well as the v key and the question ? Mark key
Sent from my HTC Chacha A810 using Tapatalk 2
Click to expand...
Click to collapse
Sent from my HTC Chacha A810 using Tapatalk 2
---------- Post added at 11:19 PM ---------- Previous post was at 11:13 PM ----------
Moe92 said:
Same issues here but my toher keys are also messed up such as the m and n keys when pressing ATL as well as the v key and the question ? Mark key
Sent from my HTC Chacha A810 using Tapatalk 2
---------- Post added at 11:13 PM ---------- Previous post was at 11:07 PM ----------
Sent from my HTC Chacha A810 using Tapatalk 2
Click to expand...
Click to collapse
Sent from my HTC Chacha A810 using Tapatalk 2
I have a kind of the same problem in stock rom after s-off.
that is I cant switch between arabic and english languages of my keyboard. it is very necessary for to type with both languages.
can you help? the Lng key doesnt change the layout. it makes an space between words
SOLVED!!
Ok... since it doesn't seem that's a problem anyone's solved yet I did some extensive research and poking around and I was able to find the solution.
Turns out that I was right, but I was just editing the wrong .kcm file.
A little background:
First I expected to have to decompile / modify / recompile some kcm.bin file, but looking at the specs on the kcm files, the compiled kcm files have been dropped since Android 3.0 so editing the kcm files was the right thing to do.
After some research I found that the .kcm (and .kl) files that mattered are the chacha-keypad-aw.kcm and chacha-keypad-aw.kl files.
These can be found in the /system/usr/keychar and /system/usr/keylayout directories.
For more information on the .kcm and .kl file format look at http://source.android.com/tech/input/key-character-map-files.html and http://source.android.com/tech/input/key-layout-files.html
To fix the problem you need to modified the .kl file:
Dowload the "chacha-keypad-aw.kl" from the /system/usr/keylayout ("adb pull /system/usr/keylayout/chacha-keypad-aw.kl")
Make a backup copy of the .kl file
Edit the chacha-keypad-aw.kl and replace the line "key 15 STAR" with "key 185 STAR" (this will map the "*" key
Uncomment the line "key 184 EXPLORER" (this will map the Facebook button)
Mount the system as RW ("adb shell mount -o rw,remount /system")
Upload the modified file to the phone ("adb push chacha-keypad-aw.kl /system/usr/keylayout/"
Then modify the .kcm file:
Dowload the "chacha-keypad-aw.kcm" from the /system/usr/keychars ("adb pull /system/usr/keychars/chacha-keypad-aw.kcm")
Make a backup copy of the .kl file
Edit the chacha-keypad-aw.kcm to fix the key mapping (I don't remember the whole list, but most of my issues where with the ALT'ed keys didn't match - see original post)
Mount the system as RW ("adb shell mount -o rw,remount /system")
Upload the modified file to the phone ("adb push chacha-keypad-aw.kcm /system/usr/keychars/"
Then reboot your phone ("adb reboot").
There are still a fwe behavior that are annoying that I haven't been able to fix:
camera button ("alt+.") not working
Voice command not working
"Terminate call" button locks the phone when not in a call (where the standard on the stock Status is to go to the home screen).
But since this is a phone I use mostly when I travel this is ok for now.
Another useful resource (including a link to a program that will give your the keycode for every key press on the keyboard:
http://www.thriveforums.org/forum/t...layout-any-usb-bluetooth-keyboard-rooted.html
I have uploaded both chacha-keypad-aw file I modified (just remove the .txt extension since the forum doesn't like .kcm or .kl extensions).
I hope this help.
Related
I cant post in the real thread so im putting it here.
Upgrading from Eris ODEX GSB v3.4 to Eris ODEX GSB v3.5 has some issues which are making the phone not work well.
1) upgrade messes up radio and requires reactivation from verizon before you get signal
This would be ok except that the dial pad has been removed from the default activation 'app' that runs when you dial *228 so there is no way to press "1" to tell it you want to reactivate.
(work around is to just wait forever and it will default to activation)
(this problem exists in v3.4 as well making it impossible to update roaming capabilities)
2) ALL asian languages have been removed. This makes it very painful to search through asian websites. (They were still there in v3.4)
Could these be fixed please?
Thanks...
Holding down the menu button should bring up the keyboard where you can choose 1 to activate.
According to this thread, the asian language support can be restored by placing the missing DroidSansFallback.ttf font file into /system/fonts.
download the attached zip
place the contained DroidSansFallback.ttf onto your sdcard
run these commands in the terminal emulator:
Code:
su
mount -o remount,rw /system
mv /sdcard/DroidSansFallback.ttf /system/fonts/
chown 0:0 /system/fonts/DroidSansFallback.ttf
chmod 644 /system/fonts/DroidSansFallback.ttf
reboot
if not fixed: reboot into recovery-> wipe cache/dalvik-cache & fix permissions(called fix apk uid mismatches in amon-ra recovery) then reboot
Thanks so much for the help! Ill give it a try.
to change the physical keyboards layout rename/copy umts_milestone2-keypad.kl to umts_jordan-keypad.kl, edit it with an editor to change key 21 with 44 and rename/copy umts_milstone2-keypad.kcm.bin to umts_jordan-keypad.kcm.bin
i do this via windows comandline tool:
1. get the umts_milestone2-keypad.kl file
Code:
adb pull /system/usr/keylayout/umts_milestone2-keypad.kl
2. edit line 43 and 65, change Z and Y
3. push the file to the sdcard as umts_jordan-keypad.kl
Code:
adb push umts_milestone2-keypad.kl /sdcard/umts_jordan-keypad.kl
4. open shell via adb and make /system/ writeable
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
5. copy the edited file to /system/..
Code:
cp /sdcard/umts_jordan-keypad.kl /system/usr/keylayout/umts_jordan-keypad.kl
6. copy umts_milstone2-keypad.kcm.bin as umts_jordan-keypad.kcm.bin in ../keychars/
Code:
cp /system/usr/keychars/umts_milestone2-keypad.kcm.bin /system/usr/keychars/umts_jordan-keypad.kcm.bin
7. set /system back to read-only and reboot
Code:
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
not solved problem:
alt + z gets <
alt + y gets 6
Have you considered using files from qwertz froyo and renaming/pushing them with adb?
It may solve your alt+x problems.
I'm about to try this for my french keyboard. I'll keep you tuned.
I've been able to get the AZERTY layout.
First time i used the files from the azerty patch from argen2stone but my keyboard stopped working so i edited trough Root Explorer the files myself. Still got problems with the "." "<" "1" and "2"
atm i try to edit the umts_jordan-keypad.kcm.bin with a hex editior to change the bindings but if i restart with the new file the changed key´s don´t work^^
more or less we need the original *.kcm.bin ? Can't you take the kcm.bin for qwertz from the stock sbf?
Atomos33 said:
I've been able to get the AZERTY layout.
First time i used the files from the azerty patch from argen2stone but my keyboard stopped working so i edited trough Root Explorer the files myself. Still got problems with the "." "<" "1" and "2"
Click to expand...
Click to collapse
I've also been able to put my keyboard in AZERTY layout, but I have all the "2nd" (alt) keys that are melted
Could you send me your keypad files, please ? ([email protected] )
chibani said:
I've also been able to put my keyboard in AZERTY layout, but I have all the "2nd" (alt) keys that are melted
Could you send me your keypad files, please ? ([email protected] )
Click to expand...
Click to collapse
Which one do you need ? The one i modified or the originals? Right i'm on gingerbeta with symbol disorder...
I think i'm going to ask some people on a french forum to send me the original files from stock rom.
Sent from my MB722 using XDA App
yeah tried the original files but this ain´t help because the phone think that the keypad it is qwerty either. so the mapping is diffrent to the stock german one.
probably you get the same problems with azerty...
Atomos33 said:
Which one do you need ? The one i modified or the originals? Right i'm on gingerbeta with symbol disorder...
I think i'm going to ask some people on a french forum to send me the original files from stock rom.
Sent from my MB722 using XDA App
Click to expand...
Click to collapse
OK.
I think i'll try to fix my current file.
And if I succeed, I'll give it to frenchies
hi,
Did someone found a solution finally ?
I'm blocked with the same issues in CM7 and azerty...
You can try this http://forum.xda-developers.com/showthread.php?t=1729414
I have an HTC Status (U.S. AT&T version of Chacha) and, like some other users on this forum, have had some issues with the keyboard mappings changing after rooting the phone. After spending a lot of time browsing/searching these (and other) forums as well as Google, I've concluded a few things about this:
1) The files responsible for the keyboard mappings are chacha-keypad.kcm.bin and chacha-keypad.kl.
2) Changing chacha-keypad.kl will help with the main keys but can't be used to fix mappings of alt+
3) The completely correct chacha-keypad.kcm.bin doesn't seem to be posted anywhere (for U.S. English keyboard). I got one that is almost right, but mappings for alt+V, alt+B, alt+N, alt+M, alt+?, alt+camera, and alt+.com are still off.
Therefore, I will need to edit the chacha-keypad.kcm.bin file myself. I have no problem doing this, as the format of the kcm files seems pretty straight-forward, but I can't figure out how to open the bin file, which cannot be opened directly since it is binary.
I need to convert the kcm.bin to kcm, make the changes that are needed, and then recompile to bin. I found info on doing this here:
http://forum.xda-developers.com/showthread.php?t=837002&page=4
The above link includes a zip that has a Python script to decompile the bin and then an exe to compile kcm to bin. I'm stuck at the decompiling part. I tried running the unkcm Python script included in the kcm_utils.zip (from the post above), however I get an error message:
Code:
C:\Users\Maya\Downloads\HTC\kcm_utils>python unkcm.py chacha-keypad.kcm.bin chacha-keypad.kcm
Traceback (most recent call last):
File "unkcm.py", line 179, in <module>
decompileKCM(f, output)
File "unkcm.py", line 162, in decompileKCM
Out.write(kr.printKR()+"\n")
File "unkcm.py", line 143, in printKR
fmt = (rkeycodes[self.keycode],)
KeyError: 116
I'm attaching the kcm.py and chacha-keypad.kcm.bin files for reference. Can someone please help? Or does anyone know of another way of converting the .kcm.bin files to .kcm files? Or can someone that knows how to do it please provide me with the .kcm version of the attached .kcm.bin file?
Thank you so much in advance!
Hi,
You must add keycodes 116, 117 and 124 (QUECHAR) in unkcm, and also in the .h file used by kcm.
SuperOSR and my latest CM7 build don't use these keycodes but instead are based on the same keycodes as the vision/latte boards.
Code:
"USER1": 97, "USER2": 98, "USER3": 99, "FUNC_1": 116,
"HTC_SHARE": 117, "FUNC_2": 118, "QUECHAR": 124}
You may also need: http://forum.xda-developers.com/attachment.php?attachmentid=441092&d=1289759467
xdbg said:
Hi,
You must add keycodes 116, 117 and 124 (QUECHAR) in unkcm, and also in the .h file used by kcm.
SuperOSR and my latest CM7 build don't use these keycodes but instead are based on the same keycodes as the vision/latte boards.
Code:
"USER1": 97, "USER2": 98, "USER3": 99, "FUNC_1": 116,
"HTC_SHARE": 117, "FUNC_2": 118, "QUECHAR": 124}
You may also need: http://forum.xda-developers.com/attachment.php?attachmentid=441092&d=1289759467
Click to expand...
Click to collapse
Thank you so much for your help! Once I added those codes to the unkcm.py file, I was able to decompile the kcm.bin file and made the changes I needed (sure enough, as I'd expected, the ALT and ALT+SHIFT column had some incorrect values for some of the keys).
I also added the key codes that you mentioned to the kcm source code (KeycodeLabels.h file in the src folder of kcm_utils), and re-compiled the kcm.exe without errors. However, when I tried to run it, I got an error:
Code:
C:\Users\Maya\Downloads\HTC\kcm_utils>kcm chacha-keypad.kcm chacha-keypad.kcm.bin
chacha-keypad.kcm:60: not enough on this line: '?' 0x0 '?' '?'
'#' '#'
Line 60 is the last line in my chacha-keypad.kcm file and is exactly the same format as the other lines, so I'm not sure why I'm getting the above error. Looking at kcm.cpp, I see that the "not enough on this line: ..." message only appears when there is a '\0' (end of line) before it's expected, but I don't understand why that is happening, since the format is the same for all the lines and it only seems to have a problem with the last line.
I'm attaching my chacha-keypad.kcm file, as well as my modified kcm.exe along with the modified source of this kcm app (where I just added the key codes you mentioned in your post to the .h file). Any idea what could be wrong? Thanks again!
thanks
I am just looking for tools to change the "pound" into "~"...because i never use "pound"
Try this util:
http://wiki.androidteam.ru/tools
http://dl.dropbox.com/u/1134234/AndroidTeam/utils/kcmdecoder.jar
How to use:
java -jar kcmdecoder.jar chacha-keypad.kcm.bin chacha-keypad.kcm
vovkab said:
How to use:
java -jar kcmdecoder.jar chacha-keypad.kcm.bin chacha-keypad.kcm
Click to expand...
Click to collapse
Ermm please i am new to Htc and and Android (beginner). i have the same problem with my Htc (status) where alt keys don't work correctly. can u please give me a detailed instruction on how to install the java program.
anyway i ddnt find any java emulator for Htc (status)/chacha. thanks in advance
hello,
can we use this for the FB button?
Hi everyone i need someone help from expert.
From this post below it teach us how to root bluestack but i have a problem after step 3 i have no idea how to start adb and what is adb/
http://forum.xda-developers.com/showpost.php?p=24194320&postcount=3
This is the step i not sure after step 3.
1. Paying attention to the guidelines above, place the following files in their correct location – this includes initrd-betahack.img, ramdisk.img, and system.img.
2. After finding your GUID and making the appropriate changes to BlueRegistryMOD.reg in 2(two) places, run the registry file.
3. Start/restart BlueStacks – go to the Start menu>type Start Bluestacks
4. Start adb on your computer
a. Connect to bluestacks - #adb connect 127.0.0.1:5555
b. Ensure you have root access - #adb root
i. You should get message: “adbd is already running as root”
c. Mount system as read/write - #adb remount
d. Remove ‘dummy’ superuser - #adb shell rm /system/xbin/su
e. Push x86 superuser to BlueStacks - #adb push su.x86 /system/xbin/su
i. su.x86 must be in the same Windows directory you are running in the console
f. Correct the permissions for superuser - #adb shell chmod 6711 /system/xbin/su
g. Remount system read only - #adb shell mount -o ro,remount t-ext4 /dev/sdb1 /system
h. Exit adb by closing the console window
5. Restart BlueStacks – go to the Start menu>type Start BlueStacks
6. At this point you should have root and read/write access.
a. Verify root using a tool like Root Check. I suggest Root Check Pro because it will point you to what the problem is if you do NOT have root.
b. Verify read/write access using a tool like Root Explorer.
I am having problem in only this line..
Remount system read only - #adb shell mount -o ro,remount t-ext4 /dev/sdb1 /system
It's telling me that syntax is wrong and no matter how try by changing the parameters etc., it's still showing me wrong parameters..
@holybloods
There few links might help you.
http://forum.xda-developers.com/showthread.php?t=757233
http://forum.xda-developers.com/showthread.php?t=1474956
---------- Post added at 04:59 PM ---------- Previous post was at 04:47 PM ----------
oh., I may get the solution.. Here is the tip for anyone else who is having the same problem..
Remount system read only - #adb shell mount -o ro,remount -t ext4 /dev/sdb1 /system
i can't
ok.., I have finally managed to root Bluestacks.. but here comes a new problem.. after rooted it, I am no longer able to see my mounted windows folders in bluestack anymore..
/sdcard/windows folder is empty which was earlier showing me my mounted directory through a registry hack.. well then this is really useless for me..
where do i find the two places to change the GUID?
Hi,
I need Help by rooting Bluestacks here:
YOU MUST ENTER YOUR SPECIFIC USER ID BEFORE RUNNING BlueRegistryMOD.reg !!!
Where the registry key says ENTER-YOUR-GUID-HERE you need to enter the number (with dashes) which i founded already here:
[HKEY_CURRENT_USER\Software\BlueStacks]
“USER_GUID”=”SOME-NUMBERS-HERE”
ENTER-YOUR-GUID-HERE must be changed in 2(two) places in BlueRegistryMOD.reg
where can i find these two places to change the GUID?
i saw one one time, but i am not sure where i found it.
can somebody help me with this?
thx & sorry for my englisch
rooting Bluestacks
Staggi said:
Hi,
I need Help by rooting Bluestacks here:
YOU MUST ENTER YOUR SPECIFIC USER ID BEFORE RUNNING BlueRegistryMOD.reg !!!
Where the registry key says ENTER-YOUR-GUID-HERE you need to enter the number (with dashes) which i founded already here:
[HKEY_CURRENT_USER\Software\BlueStacks]
“USER_GUID”=”SOME-NUMBERS-HERE”
ENTER-YOUR-GUID-HERE must be changed in 2(two) places in BlueRegistryMOD.reg
where can i find these two places to change the GUID?
i saw one one time, but i am not sure where i found it.
can somebody help me with this?
thx & sorry for my englisch
Click to expand...
Click to collapse
_________________________________
If you right click on the BlueRegistryMOD.reg file and select edit, it will open in notepad. Find where it says ENTER YOUR GUID HERE and enter your GUID there. Save and exit. Continue with the tutorial.
I will Help him find what I know he is looking for.
Step One find the application run on your pc.
Step Two Run the Application run when it comes up type regedit into it then press the enter button this will bring up a program called Registry Editor.
Step Three you will see a folder with then name of HKEY_LOCAL_MACHINE double left click on that folder and you will see a lot of folders in that folder double left click on the one that says SOFTWARE double left click on that one you will see a lot of folders in that folder left click on the one with the name BlueStacks.
Step Four you will see on the left of the program Registry Editor some righting one of the things there is your guid your guid will have be next to USER_GUID.
Step Five right Click on The Words USER_GUID and a list will come up click modify... this will show you your guid and you can copy it from there like you can in a web page or Text file once you have it copyed past it where it says put your guid here.
Step Six after doing every thing else that it asks for you to do in there tutorial get check root it will tell you if your device is rooted right or not. Have a great day or better your Helping Friend ZepherZaper
---------- Post added at 10:49 AM ---------- Previous post was at 10:35 AM ----------
Staggi said:
Hi,
I need Help by rooting Bluestacks here:
YOU MUST ENTER YOUR SPECIFIC USER ID BEFORE RUNNING BlueRegistryMOD.reg !!!
Where the registry key says ENTER-YOUR-GUID-HERE you need to enter the number (with dashes) which i founded already here:
[HKEY_CURRENT_USER\Software\BlueStacks]
“USER_GUID”=”SOME-NUMBERS-HERE”
ENTER-YOUR-GUID-HERE must be changed in 2(two) places in BlueRegistryMOD.reg
where can i find these two places to change the GUID?
i saw one one time, but i am not sure where i found it.
can somebody help me with this?
thx & sorry for my English
Click to expand...
Click to collapse
Step One find the application run on your pc.
Step Two Run the Application run when it comes up type regedit into it then press the enter button this will bring up a program called Registry Editor.
Step Three you will see a folder with then name of HKEY_LOCAL_MACHINE double left click on that folder and you will see a lot of folders in that folder double left click on the one that says SOFTWARE double left click on that one you will see a lot of folders in that folder left click on the one with the name BlueStacks.
Step Four you will see on the left of the program Registry Editor some righting one of the things there is your guid your guid will have be next to USER_GUID.
Step Five right Click on The Words USER_GUID and a list will come up click modify... this will show you your guid and you can copy it from there like you can in a web page or Text file once you have it copied go to where BlueRegistryMOD.reg is located right click on the BlueRegistryMOD.reg file and select edit this will bring up a text window where you can edit the file
Step Seven paste your guid where it says put your guid here.
Step Eight after doing every thing else that it asks for you to do in there tutorial get check root it will tell you if your device is rooted right or not. Have a great day or better your Helping Friend ZepherZaper oh and p.s. your English is not that bad it is pretty good p.s.s I registered to be able to use this form just so I could help you because I am sure that Tacs did not help you because you were asking where to find it not where to put it and I hope you have a great day or even better
I've found that the caps lock and shift keys seem to be placed poorly and result in often clicking caps lock instead of shift and having to delete a bunch of CAPS text and type again. I've seen other reports of users having trouble adapting to this keyboard quirk. Shift should be next to the Z key, and caps lock is redundant because clicking shift twice enables caps lock. So I've modified the caps lock key to duplicate the shift key functionality.
ADB Instructions:
Extract keypad_8960.kl from zip file to external SD card, then open a command prompt and navigate to your ADB directory. Execute the following commands:
Code:
adb shell
su
mount -o remount,rw /system
mv /system/usr/keylayout/keypad_8960.kl /system/usr/keylayout/keypad_8960.bak
cp /mnt/external1/keypad_8960.kl /system/usr/keylayout/keypad_8960.kl
chmod 644 /system/usr/keylayout/keypad_8960.kl
reboot
Root Explorer or ES File Explorer instructions:
Extract keypad_8960.kl from zip file
Mount /system as read/write
Navigate to /system/usr/keylayout
Rename keypad_8960.kl to keypad_8960.bak
Copy keypad_8960.kl extracted from zip to /system/usr/keylayout
Change permissions to rw-r--r--
Reboot phone
Manual modification instructions:
Edit keypad_8960.kl and locate the following line:
key 58 CAPS WAKE_DROPPED
Change line to:
key 58 SHIFT_LEFT WAKE_DROPPED
Let me know how this works out for people, and if there are any other keyboard remapping requests!
Hi, I would be forever grateful if you could make voice the default action on the tab key. I usually use voice when driving so doing a shift-tab is difficult, and don't use the tab functionality anyway.
cmags said:
I've found that the caps lock and shift keys seem to be placed poorly and result in often clicking caps lock instead of shift and having to delete a bunch of CAPS text and type again. I've seen other reports of users having trouble adapting to this keyboard quirk. Shift should be next to the Z key, and caps lock is redundant because clicking shift twice enables caps lock. So I've modified the caps lock key to duplicate the shift key functionality.
ADB Instructions:
Extract keypad_8960.kl from zip file to external SD card, then open a command prompt and navigate to your ADB directory. Execute the following commands:
Code:
adb shell
su
mount -o remount,rw /system
mv /system/usr/keylayout/keypad_8960.kl /system/usr/keylayout/keypad_8960.bak
cp /mnt/external1/keypad_8960.kl /system/usr/keylayout/keypad_8960.kl
chmod 644 /system/usr/keylayout/keypad_8960.kl
reboot
Root Explorer or ES File Explorer instructions:
Extract keypad_8960.kl from zip file
Mount /system as read/write
Navigate to /system/usr/keylayout
Rename keypad_8960.kl to keypad_8960.bak
Copy keypad_8960.kl extracted from zip to /system/usr/keylayout
Change permissions to rw-r--r--
Reboot phone
Manual modification instructions:
Edit keypad_8960.kl and locate the following line:
key 58 CAPS WAKE_DROPPED
Change line to:
key 58 SHIFT_LEFT WAKE_DROPPED
Let me know how this works out for people, and if there are any other keyboard remapping requests!
Click to expand...
Click to collapse
If you flash the softkey mod that includes the search button, long pressing the soft search key opens voice search. Not exactly what you were asking, but one alternative.
Sent from my XT897 using xda app-developers app
I'm confirming, just did the manual way mod and Caps now works like Shift and that's really good for me because I have just switched from HTC Touch Pro2. Couldn't get used to new keyboard order, now I don't have to