Database Develop

Smart Dial: How to add international characters

Smartdial.dll can be edited to make Smart Dial search the contacts with non english characters.
I have found an explanation on how to edit this dll but not detailed enough for me to do. Can anybody give a more detailed explanation than below on editing smartdial.dll, I want to add Turkish characters and I'm sure many people can use this info to add their languages.
Here is the process explained by "Seff" (found on another site, thanks to Seff but not enouh for me to do this mod )
--> Dump your rom files
--> Get smardialing.dll
--> Lear about physical offsets in the .dll and raw offsets (use PE Explorer)
--> Find the tables and their offsets (the tables are in UNICODE)
--> Find all references (actully one only per each table) to the tables (use IDA Pro)
--> Relocate tables/modify current tables (using Hex Workshop)
--> Sign the modified library (using signcode.rar found on this site)
--> Replace the original smartdialing.dll
--> The thing is, there are different smardialing builds. One for T-Mobile, one for
--> K-JAM. We found that we can have one single dll for all T-Mobile builds, and
--> one for K-JAM. So it may be extra work for different Wizard types.
--> The tables (all UNICODE) are in brackets followed by 0000 word:
--> [.9.W.X.Y.Z.w.x.y.z.] 0000
--> [.8.T.U.V.t.u.v.] 0000
--> [.7.P.Q.R.S.p.q.r.s.] 0000
--> [.6.M.N.O.m.n.o.] 0000
--> [.5.J.K.L.j.k.l.] 0000
--> [.4.G.H.I.g.h.i.] 0000
--> [.3.D.E.F.d.e.f.] 0000
--> [.2.A.B.C.a.b.c.] 0000
--> [.-.1.`.=.{.}[email protected]\.$.%.^.&.\.*.(.).?.<.>.~.|.\._.:.;...,./.".'.] 0000

Mobilnaut SYM - typing accented characters on hardware keyboard of HTC Touch PRO

Hi,
I made this little program for typing accented characters on the hardware keyboard. It's simple SIP, which means it will be shown as standard input method, but when you click on the icon, no keyboard will be shown. That's useful when you are using hardware keyboard and you are trying to type something, with this SIP no software keyboard will pop up and cover half of the screen. And it's automatically activated only in landscape, in portrait mode you can use your favorite software input method. This program will remember the input method you used before, and when you slide your keyboard back, this method will be set as active.
So when this input method is activated, you can simply type on hardware keyboard for example letter 'A', then press "SYM" key (next to the Space key) and the letter 'A' will be changed to 'Á'. This depends on your \Windows\Sym.txt file, which you can change to whatever you want. When you want to show the Symbol screen (default behaviour when you press "SYM" key), simply press Shift + SYM, or when you press SYM key after typing some letter, which is not in Sym.txt file, this screen will appear as well.
Installation:
1) download CAB file from here:
Code:
http://www.mobilnaut.net/cz/mnsym.htm
(click on "Stáhnout")
2) copy it into your device and install it
3) perform softreset
4) if you want to change the accented letters, change file \Windows\Sym.txt or \Windows\Sym.0409.txt to your own file
Uninstallation:
1) you can uninstall this application via Settings -> Remove Programs
Known issues:
1) In landscape mode Volume buttons doesn't work - many applications have the same problem, it's because of the api function I used - but in portrait mode everything's ok
2) it seems to be not compatible with S2U2
3) during boot process (green windows mobile screen) black bar with "Mobilnaut SYM" text could be shown, but it will disappear in a moment
Warning: This application is provided "as is", without warranty of any kind. Use it at your own risk!

Thank you...
This solved my keyboard problems and hardware sym key issues... super....

Doesnt work for me with Elite RC2 and S2U2 installed. The program installs, but the SYM button still brings up the table.

Unfortunatelly it's not compatible with s2u2 application... I don't use s2u2, so now I don't know why it doesn't work.

spoke too soon
Somehow, when I press the / and sym, it doesn't change the symbol to \
just gets an é same with . and sym key..
Anybody know how to fix this?
This is so frustrating...

It should show the window with symbol list, because SYM key works only with letters, not with symbols. So when you press "/" button, the SYM key won't work and the list of symbols will appear. Mybe in the future I'll add the support for symbols...

that's my whole problem :-D
Jimm98y said:
It should show the window with symbol list, because SYM key works only with letters, not with symbols. So when you press "/" button, the SYM key won't work and the list of symbols will appear. Mybe in the future I'll add the support for symbols...
Click to expand...
Click to collapse
somehow, my symbol pad doesn't show up..
How can I map the sym key to do that?
I think I need the file symselector.exe out of my windows folder, but It's not in Da_G's rom.
Can you maybe post it here?
I think that's why I cant use the sym key.
Can you add support, that would be so great..
Same behaviour when I press e, I can't scroll through the e with the accents, it just ads the same e' symbol.
Do you know how to fix this?
I tried ezinput, that solved some of my problems, and your cab is helpful.
It's just the final bit that's frustrating. I want my \ key
Any help would be greatly appreciated.

not symselector...
Ok, got an answer from Sleuth255 (thanks for that) that the symselector is just an invalid registry key.
So all hope is on you now mate, can you help me get my \ back?
Thanks bunch...

Any news???
Hey Jimmy..any news on the development of this soft to include symbols???
That would make this soft truly awesome..
And exactly what doesn't work with S2U2?
Seems to be running quote well on my device...
What are the problems people are encountering?

Compatibility issues with S2U2 are solved by the newest version of S2U2. Now I'm trying to add some new features, but I don't have much free time, so please be patient.

No Problem...
Jimm98y said:
Compatibility issues with S2U2 are solved by the newest version of S2U2. Now I'm trying to add some new features, but I don't have much free time, so please be patient.
Click to expand...
Click to collapse
All good things in life are worth waiting for..
Glad you're on it..
Keep up the good work

MAybe this helps....
fixed the sym key
http://forum.xda-developers.com/showpost.php?p=3065204&postcount=604

Jimm98y said:
Hi,
I made this little program for typing accented characters on the hardware keyboard. It's simple SIP, which means it will be shown as standard input method, but when you click on the icon, no keyboard will be shown. That's useful when you are using hardware keyboard and you are trying to type something, with this SIP no software keyboard will pop up and cover half of the screen. And it's automatically activated only in landscape, in portrait mode you can use your favorite software input method. This program will remember the input method you used before, and when you slide your keyboard back, this method will be set as active.
So when this input method is activated, you can simply type on hardware keyboard for example letter 'A', then press "SYM" key (next to the Space key) and the letter 'A' will be changed to 'Á'. This depends on your \Windows\Sym.txt file, which you can change to whatever you want. When you want to show the Symbol screen (default behaviour when you press "SYM" key), simply press Shift + SYM, or when you press SYM key after typing some letter, which is not in Sym.txt file, this screen will appear as well.
Installation:
1) download CAB file from here:
Code:
http://www.mobilnaut.cz/?a/1753
(click on "Mobilnaut SYM pro HTC Touch Pro" and then on "Stáhnout")
2) copy it into your device and install it
3) perform softreset
4) if you want to change the accented letters, change file \Windows\Sym.txt or \Windows\Sym.0409.txt to your own file
Uninstallation:
1) you can uninstall this application via Settings -> Remove Programs
Known issues:
1) In landscape mode Volume buttons doesn't work - many applications have the same problem, it's because of the api function I used - but in portrait mode everything's ok
2) it seems to be not compatible with S2U2
3) during boot process (green windows mobile screen) black bar with "Mobilnaut SYM" text could be shown, but it will disappear in a moment
Warning: This application is provided "as is", without warranty of any kind. Use it at your own risk!
Click to expand...
Click to collapse
I have a Fuze, so the keyboard layout is a little different. The SYM key is actually a combination of pressing FN+Space bar. However, when you press that, you get just the symbol panel... I would love to have the application you developed working!

I installed Mobilnaut SYM and it works very well
If you add support for the symbols in the future I propose following:
/ => \ |
( => [ { <
) => ] } >
Thank you for this nice software

help for other keyboard layouts?
As posted, I have a FUZE. Any way you can remap the SYM key to the one to the left of the Spacebar? On the FUZE keyboard, the SYM is obtained by pressing Fn+Space. This doesn't work for you Mobilnaut....

I'm sorry for late response, I was having hard time at school, too many exams in past few days. Well that would be a problem, because I don't have fuze so I can't test it. I'll see what can I do, when I'll have some time...

fuze layout
This is the Fuze layout, as it appears in eT9.Raphael.wwe.atnt.kmap. Would this help?
//
// N O T E: This file must be saved as Unicode
//
// This file contains the virtual keys mapping table for the
// Raphael device World-Wide English QWERTY layout.
// The mapping table is defined as follows
//
// VK_TPOUND = 0x78
// VK_TSTAR = 0x77
// VK_TAB = 0x09
//
// We do not support escape value yet. So the key/char values should be
// entered explicitly or by encoding start with 0x
//
// Format:
// {VK VK1 VK2 CH1 CH2}
// VK -> value from keyboard driver
// VK1 -> key mapped, interpret by IME
// VK2 -> key to interpret when for press and hold
// CH1 -> symbols produced by Fn + key
// CH2 -> symbols in 123 mode
// CH4 -> Key Index
// Top Row
// {1 1 1 ! ! 0xff} // original layout
{@ @ @ % % 0xff}
{- - - ¢ ¢ 0xff}
{! ! ! $ $ 0xff}
{( ( ( & & 0xff}
{) ) ) # # 0xff}
{' ' ' 1 1 0xff}
{" " " 2 2 0xff}
{; ; ; 3 3 0xff}
{: : : * * 0xff}
{/ / / = = 0xff} // 0xBD = VK_OEM_MINUS
{- - - + + 0xff} // 0xBB = VK_OEM_PLUS
// Second Row
// {0x09 0x09 0x00 0x00 0x00 0xff} // TAB - 0x09 = VK_TAB
// {0x09 0x14 0x14 0x00 0x00 0xff} // TAB - 0x09 = VK_TAB, 0x14 = VK_CAPITAL
{Q Q Q Q Q 0x00}
{W W W W W 0x01}
{E E E E E 0x02}
{R R R R R 0x03}
{T T T T T 0x04}
{Y Y Y 4 4 0x05}
{U U U 5 5 0x06}
{I I I 6 6 0x07}
{O O O O O 0x08}
{P P P P P 0x09}
{0x08 0x08 0x08 0x2E 0x2E 0xff} // BACKSPACE - 0x08 = VK_BACK, 0x2E = VK_DELETE
// Third Row
// {0xEC 0xEC 0x00 0x00 0x00 0xff} // FN - 0xEC = FN
// {0x14 0xEC 0xEC 0x00 0x00 0xff} // CAPS - 0x14 = VK_CAPITAL, 0xEC = FN
{A A A A A 0x0a}
{S S S S S 0x0b}
{D D D D D 0x0c}
{F F F F F 0x0d}
{G G G G G 0x0e}
{H H H 7 7 0x0f}
{J J J 8 8 0x10}
{K K K 9 9 0x11}
{L L L L L 0x12}
{0xF2 0x0D 0x00 0x00 0x00 0xff} // ENTER - 0x0D = VK_RETURN
// Fourth Row
{0xA0 0x10 0x10 0x00 0x00 0xff} // SHIFT - 0xA0 = VK_LSHIFT, 0x10 = VK_SHIFT
{Z Z Z Z Z 0x13}
{X X X X X 0x14}
{C C C C C 0x15}
{V V V V V 0x16}
{B B B B B 0x17}
{N N N 0 0 0x18} // Zero
{M M M M M 0x19}
{? ? ? ? ? 0xff} // 0xBF = VK_OEM_2 = VK_SLASH
{0xF1 0x26 0x26 0x21 0x21 0xff} // UP - 0x26 = VK_UP, 0x21 = VK_PRIOR (PAGE UP)
// Bottom Row
// {0xA2 0x11 0x00 0x00 0x00 0xff} // OK, 0xA2 = VK_LCONTROL, 0x11 = VK_CONTROL
{0xEC 0xEC 0x00 0x00 0x00 0xff} // FN - 0xEC = FN
// {0xEB 0xEB 0x00 0x00 0x00 0xff} // SMS - 0xEB = SMS
// {0xEF 0xEF 0x00 0x00 0x00 0xff} // MSG - 0xEF = MSG
{0xE6 0xE6 0x00 0x00 0x00 0xff} // SYM - 0xE9
{0xEA 0x12 0x00 0x00 0x00 0xff} // T9 Menu - 0x12
{0x20 0x20 0x20 0x00 0x00 0xff} // SPACE - 0x20 = VK_SPACE
{, , , , , 0xff}
{. . . . . 0xff}
{0xF5 0x25 0x25 0x00 0x00 0xff} // LEFT - 0x25 = VK_LEFT
{0xF3 0x28 0x28 0x22 0x22 0xff} // DOWN - 0x28 = VK_DOWN, 0x22 = VK_NEXT (PAGE DOWN)

uninstalling?
[- removed]

here's a pic of the layout...maybe this helps
If you can fix it, perfect... I would be grateful for ever!

using mobilnaut sym on Fuze?
Jimm, any chance you can take a look at how to trigger your software with a key other than SYM? Thanks a lot!

Where to find HW KB scancodes

I'm trying to make proper keymaping for X1 HW keyboard, but i'm stuck at the beginning. How to get keys scancodes?
Is there any WM or Android app that can display scancode on key press?

I don't know anything about scancodes, but could this be useful?
http://msdn.microsoft.com/en-us/library/bb431750.aspx
I found this as well:
http://forum.xda-developers.com/showthread.php?t=326046

There is (i believe, according to the Kovsky Linux Wiki) a fully working keymap file here. i've had a quick look and it looks pretty complicated, but complete, just have to find a way to implement it in android i guess

We just need to replace /system/usr/keylayout/qwerty.kl with that I believe.

Apparently the filesystem is only in RO mode. Let me try to re-mount with rw.
Edit: Nope, doesn't allow me to go to rw mode... don't know how we can replace it.

you need to uncompress the squashfs or the zImage file systems, wherever the file is, overwrite the keyboard and recompress them
I tried messing around with the keyboard mapping as well but messing with the android files that haret is using is over my head

Edit: Read post below for information on how to mount and edit the 2 files (rootfs.img and system.sqsh)

I basically extracted and changed the file and recreated the sqsh, but it was 4.0 which the android kernel doesn't support. I'm going to install a lower kernel (2.6.29)- and install mksquashfs that does support making 3.1 sqfs'.
Edit: Got squash-tools 3.4.1 installed on CentOS 5.3. Changed qwerty.kl into the Xperia keymap. Remade squash file and booted up Haret. Kernel boots up squashfs fine. Time to try if the keys actually work like it should.
Edit2: Keys are even more messed up with this key layout than original qwerty. I looked at the both files and they look hugely different... the format is complete different as well. Also, its no point opening up and recompiling the sqsh, qwerty.kl is symlinked to /etc/keylayout/qwerty.kl, which is in /init.etc/keymaps in the rootfs.img.
How to uncompress/remake squashfs. You need squash-tools 3.4.1 to make a squashfs 3.1 filesystem needed for Fatsal's android kernel (assuming root access).
# unsquashfs system.sqsh; cd squashsh_root/
... do your changes to sqsh here ...
# makesquashfs ./ system.sqsh -le
Click to expand...
Click to collapse
Make sure you do not forget the -le flag, the -le flag was also used in the original file. Check the flags used in the compression of the original sqsh file for reference by going:
# unsqashfs -s system.sqsh
Here's how to mount rootfs.img and location of the keymap that's being called by a symlink in system.sqsh (qwerty.kl) (assuming root access):
# mkdir /mnt/rootfs
# mount -o loop rootfs.img /mnt/rootfs
# cd /mnt/rootfs/init.etc/keymaps
Click to expand...
Click to collapse
rootfs.img is writeable after mounting, so you can make changes and the unmount and copy the new img onto your sd card.
Here's the qwerty.kl included with fatsal's android build, if someone would be kind enough to look at this and modify this one according to it?
key 399 GRAVE
key 2 1
key 3 2
key 4 3
key 5 4
key 6 5
key 7 6
key 8 7
key 9 8
key 10 9
key 11 0
key 158 BACK WAKE_DROPPED
key 230 SOFT_RIGHT WAKE
key 60 SOFT_RIGHT WAKE
key 107 ENDCALL WAKE_DROPPED
key 62 ENDCALL WAKE_DROPPED
key 229 MENU WAKE_DROPPED
key 139 MENU WAKE_DROPPED
key 59 MENU WAKE_DROPPED
key 127 SEARCH WAKE_DROPPED
key 217 SEARCH WAKE_DROPPED
key 228 POUND
key 227 STAR
key 231 CALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 232 DPAD_CENTER WAKE_DROPPED
key 108 DPAD_DOWN WAKE_DROPPED
key 103 DPAD_UP WAKE_DROPPED
key 102 HOME WAKE
key 105 DPAD_LEFT WAKE_DROPPED
key 106 DPAD_RIGHT WAKE_DROPPED
key 114 VOLUME_DOWN
key 116 POWER WAKE
key 212 CAMERA
key 16 Q
key 17 W
key 18 E
key 19 R
key 20 T
key 21 Y
key 22 U
key 23 I
key 24 O
key 25 P
key 26 LEFT_BRACKET
key 27 RIGHT_BRACKET
key 43 BACKSLASH
key 30 A
key 31 S
key 32 D
key 33 F
key 34 G
key 35 H
key 36 J
key 37 K
key 38 L
key 39 SEMICOLON
key 40 APOSTROPHE
key 14 DEL
key 44 Z
key 45 X
key 46 C
key 47 V
key 48 B
key 49 N
key 50 M
key 51 COMMA
key 52 PERIOD
key 53 SLASH
key 28 ENTER
key 56 ALT_LEFT
key 100 ALT_RIGHT
key 42 SHIFT_LEFT
key 54 SHIFT_RIGHT
key 15 TAB
key 57 SPACE
key 150 EXPLORER
key 155 ENVELOPE
key 12 MINUS
key 13 EQUALS
key 215 AT
Click to expand...
Click to collapse
Hope this helps...

I try to relocate qwerty.kl
green code: Edit key code
orange code: Add key code (from other qwerty.kl file)
red: Add supposed key code
Edit: I try to edit system.sqsh but android stuck as boot animation.
key 41 GRAVE
key 79 1
key 80 2
key 81 3
key 75 4
key 76 5
key 77 6
key 71 7
key 72 8
key 73 9
key 82 0
key 158 BACK WAKE_DROPPED
key 230 SOFT_RIGHT WAKE
key 60 SOFT_RIGHT WAKE
key 107 ENDCALL WAKE_DROPPED
key 62 ENDCALL WAKE_DROPPED
key 229 MENU WAKE_DROPPED
key 139 MENU WAKE_DROPPED
key 59 MENU WAKE_DROPPED
key 127 SEARCH WAKE_DROPPED
key 217 SEARCH WAKE_DROPPED
key 228 POUND
key 227 STAR
key 231 CALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 232 DPAD_CENTER WAKE_DROPPED
key 108 DPAD_DOWN WAKE_DROPPED
key 103 DPAD_UP WAKE_DROPPED
key 102 HOME WAKE
key 105 DPAD_LEFT WAKE_DROPPED
key 106 DPAD_RIGHT WAKE_DROPPED
key 114 VOLUME_DOWN
key 115 VOLUME_UP
key 116 POWER WAKE
key 212 CAMERA
key 16 Q
key 17 W
key 18 E
key 19 R
key 20 T
key 21 Y
key 22 U
key 23 I
key 24 O
key 25 P
key 26 LEFT_BRACKET
key 27 RIGHT_BRACKET
key 43 BACKSLASH
key 30 A
key 31 S
key 32 D
key 33 F
key 34 G
key 35 H
key 36 J
key 37 K
key 38 L
key 39 SEMICOLON
key 40 APOSTROPHE
key 14 DEL
key 44 Z
key 45 X
key 46 C
key 47 V
key 48 B
key 49 N
key 50 M
key 51 COMMA
key 52 PERIOD
key 53 SLASH
key 28 ENTER
key 56 ALT_LEFT
key 100 ALT_RIGHT
key 42 SHIFT_LEFT
key 54 SHIFT_RIGHT
key 15 TAB
key 57 SPACE
key 150 EXPLORER
key 155 ENVELOPE
key 12 MINUS
key 13 EQUALS
key 3 AT
key 1 ESCAPE
key 55 MULTIPLY
key 58 CAPS_LOCK
key 118 PLUS
Click to expand...
Click to collapse
Hope this help

I won't have time to try it out X1iser, but I'll put this file into the rootfs.img, and upload it for you to try it yourself.
Edit: Here it is,
http://www.mediafire.com/?owzdrztko32
Replace that rootfs.img with your current one.

Thank, it seems the keyboard layout is like the same as fatsal rootfs.img
What command do you use for unmount /mnt/rootfs?
I use this, but nothing happenend on rootfs.img source file
Code:
umount /mnt/rootfs
I find this for keymaps of android

Make sure you're logged in as root.
When you mount the rootfs.img using:
Code:
mount -o loop rootfs.img /mnt/rootfs
You can edit the keymap file by going:
Code:
vi /mnt/rootfs/init.etc/keymaps/qwerty.kl
You can substitute vi with nano, gedit, or whatever texteditor you like.
When you're done, just go:
Code:
cd ~; umount /mnt/rootfs
OR
Code:
umount -l /mnt/rootfs
Changes should be persistent unlike the read-only squashfs where you have to extract and remake the image.
Then rootfs.img should be ready to be replaced on your SD card.

I use ubuntu and umount -l /mnt/rootfs (other command not work with me) not edit source rootfs.img file.
In propriety "Last modification" is 18 january 2010
Edit: I edit init file and finnaly we can certainly edit rootfs.img work
I try to copy tuttle2.kl into rootfs, qwerty.kl (and turtles2.kl) seems not be our keylayout file

Did you try remounting the image and looking at whether or not you have changed the file?

Yes and modifications are done
I added this in init
Code:
if /bin/grep -c 'keyboard-type=qwerty' /proc/cmdline >/dev/null ; then
echo "USING QWERTY KEYBOARD"
cp -f /init.etc/keymaps/tuttle2-qwerty.kcm.bin /etc/keymaps/tuttle2.kcm.bin
cp -f /init.etc/keymaps/tuttle2-qwerty.kl /etc/keymaps/tuttle2.kl
elif /bin/grep -c 'keyboard-type=azerty' /proc/cmdline >/dev/null ; then
echo "USING AZERTY KEYBOARD"
cp -f /init.etc/keymaps/tuttle2-qwerty.kcm.bin /etc/keymaps/tuttle2.kcm.bin
cp -f /init.etc/keymaps/tuttle2-qwerty.kl /etc/keymaps/tuttle2.kl
else
echo "USING QWERTY KEYBOARD"
cp -f /init.etc/keymaps/tuttle2-qwerty.kcm.bin /etc/keymaps/tuttle2.kcm.bin
cp -f /init.etc/keymaps/tuttle2-qwerty.kl /etc/keymaps/tuttle2.kl
fi
I try to find what keylayout is used and where he is stocked
In system.sqsh there are (with *.kcm):
-qwerty (link to /etc/keymaps)
-sapphire-keypad.kl
-trout-keypad.kl
-trout-keypad-qwertz.kl
-trout-keypad-v2.kl
-trout-keypad-v3.kl
-tuttle2.kl
And other *.kcm, but we don't care at this point

What is this init for? The init already copies /init.etc/ to /etc/ when Android starts, so if you want to replace tuttle2 for each selection, you should do an rm and then a mv.
Basically, assume that /etc/ already has the keymaps ready to go.
X1iser said:
Yes and modifications are done
I added this in init
Code:
if /bin/grep -c 'keyboard-type=qwerty' /proc/cmdline >/dev/null ; then
echo "USING QWERTY KEYBOARD"
cp -f /init.etc/keymaps/tuttle2-qwerty.kcm.bin /etc/keymaps/tuttle2.kcm.bin
cp -f /init.etc/keymaps/tuttle2-qwerty.kl /etc/keymaps/tuttle2.kl
elif /bin/grep -c 'keyboard-type=azerty' /proc/cmdline >/dev/null ; then
echo "USING AZERTY KEYBOARD"
cp -f /init.etc/keymaps/tuttle2-qwerty.kcm.bin /etc/keymaps/tuttle2.kcm.bin
cp -f /init.etc/keymaps/tuttle2-qwerty.kl /etc/keymaps/tuttle2.kl
else
echo "USING QWERTY KEYBOARD"
cp -f /init.etc/keymaps/tuttle2-qwerty.kcm.bin /etc/keymaps/tuttle2.kcm.bin
cp -f /init.etc/keymaps/tuttle2-qwerty.kl /etc/keymaps/tuttle2.kl
fi
I try to find what keylayout is used and where he is stocked
In system.sqsh there are (with *.kcm):
-qwerty (link to /etc/keymaps)
-sapphire-keypad.kl
-trout-keypad.kl
-trout-keypad-qwertz.kl
-trout-keypad-v2.kl
-trout-keypad-v3.kl
-tuttle2.kl
And other *.kcm, but we don't care at this point
Click to expand...
Click to collapse

Is for azerty key setting, in android we can't choose azerty keyboard, I just found what is the problem... it's me
I'm working on kovsky keylayout ^^

I'm done the keyboard layout in qwerty
It's an archive tar.gz, just delete .zip

Hello,
is there anyone, he porting the german layout into this file?
I try to change the Z to Y, but after i´ve done it, my right bracket don´t
work.
I only change the letters in the kovsky-qwerty.kl in the \init.etc\keymaps folder
I forgot anything to change?

External Bluetooth Keyboard Mapping with HTC Vivid

Hello,
I didn't know if there was already a post for this, my searches were coming up not matching anything.
If you happen to have an external keyboard (bluetooth in my case), you might have the problem that many of the key events from the keyboard do not map nicely to the HTC Vivid. I am running 4.0.3 in my case with 3.6 sense, and other than the alpha-numerics, many of the system level keys were not working for me. Since I often play HD video from my phone to the HDTV, it's handy for me to control things like Volume_UP/Down, HOME / MENU / BACK, Pause / Play, Select Movie title, reply to Text, etc. So I had to find a way to improve the keyboard mappings to make it functional, and I was curious if others may have done similar things as what I describe here. I am still stuck on a few mappings, so would glad to have any info from others who have succeeded or failed in a similar regard.
I went and spent about $35 for this G-Cube bluetooth keyboard model BK-30 at Frye's.
h t t p :// www .gggcube .com/ Upload/ ProImgs/ smaImg/ 201303101915016774.jpg
It was a nice weight with a good feel on the keys, and good enough for a test run. The bluetooth device was discovered and paired easily on my HTC Vivid, and some of the system functions from keyboard were working, like Volume UP/Down and Mute. But I noticed right away I had no way to open a MENU option, or to perform a BACK function from a given application or settings screen. In order to change the keyboard mappings, it's necessary to boot into Recovery, un-mount /system and use ADB to re-mount /system in order to be able to edit the file called Generic.kl (keyboard layout file) which lives in the /system/usr/keylayout/ directory. Here are the steps I used to update the file.
Before editing the Generic.kl file, it's helpful to gather some information using an APP called KeyEvent Display (free in Google Play store).
1. Download, Install and Run the KeyEvent Display application, it gives you a keyEvent monitor for the Bluetooth Keyboard
2. Pick a few keys on the Bluetooth which seem to do nothing, and press them, noting their SCANCODE values in the app. I chose the PrintScr, Pause/Break, Insert and Delete keys, just as a test. These 4 keys gave me scancodes of 99, 119, 110, and 111, respectively.
Now, you can reboot the phone into Recovery, and perform operations using ADB, providing your PC has the right USB drivers. Usually installing HTC Sync will give you these drivers, or from Ubuntu Linux, you may not need them. Google to install the ADB tool
1. Make sure your Vivid is rooted with a Recovery Image for bootup
2. Boot into Recovery, Connect your USB cable from the PC, and test that your ADB tool can properly communicate:
a) to use ADB, you need to have download these files (adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll)
b) from the directory where you have ADB, test the connection with a simple 'adb devices'
c) you should get a response from the phone device like this:
[C:\Users\JohnDoe\ADB_Tool] adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
FA27VVJ01452 device
Click to expand...
Click to collapse
3. Assuming you are successful, you can now send ADB commands to the phone as needed here below. (If you got nothing after List of devices attached, you can research this seperately - its usually and USB driver issue.) ADB commands are used to mount and unmount file systems (like /system), to send commands or open a shell to the phone, and to push and pull files back and forth.
a) adb remount (should see: remount succeeded)
NOTE: if this fails with an error, use your Recovery Developer options to un-mount /system first, then try again.
b) adb pull /system/usr/keylayout/Generic.kl
NOTE: Generic.kl is the file we want with all the mappings of keyEvents. If the file is pulled successfully, you see something like:
pull /system/usr/keylayout/Generic.kl
982 KB/s (9058 bytes in 0.009s)
Click to expand...
Click to collapse
c) Note with File Explorer in the folder with ADB, you should have a copy of the Generic.kl file.
d) Make a backup of this file, you can cause the keyboard and other items to fail with incorrect changes!
e) Edit the file with your favorite text editor, and look for sections that we want to change, for example:
key 109 PAGE_DOWN
key 110 INSERT
key 111 FORWARD_DEL
# key 112 "KEY_MACRO"
key 113 VOLUME_MUTE
key 114 VOLUME_DOWN
key 115 VOLUME_UP
key 116 POWER WAKE
Click to expand...
Click to collapse
f) Change keys 110 and 111 (for example) to now look like this, and then save the file:
key 109 PAGE_DOWN
key 110 BACK
key 111 MENU
# key 112 "KEY_MACRO"
Click to expand...
Click to collapse
g) adb push Generic.kl /system/usr/keylayout/ (this places the file back to the phone)
h) adb shell (need a shell to reset the permissions of the file)
i) chmod 644 /system/usr/keylayout/Generic.kl (should be read only to group/world)
j) ls -l /system/usr/keylayout/ (check to see ownership and permissions look correct)
ls -l /system/usr/keylayout/
-rw-r--r-- 1 root root 894 Jul 12 2012 AVRCP.kl
-rw-r--r-- 1 root root 9048 Nov 12 20:59 Generic.kl
-rw-r--r-- 1 root root 1293 Jul 12 2012 Vendor_045e_Product_028e.kl
-rw-r--r-- 1 root root 1027 Jul 12 2012 Vendor_046d_Product_c216.kl
Click to expand...
Click to collapse
k) exit (exit from the ADB shell)
l) adb reboot (reboot the phone out of recovery into normal mode)
3. Now when the phone is ready, test the new key functions you have defined. For me, I had success with the MENU, BACK, CALL and ENVELOPE functions, among others. It is very helpful that I can use ALT-TAB to toggle between running apps.
The main one which I am failing to define is the 'OPEN ALL APPS'. If anyone else is performing mappings such as these for an external bluetooth keyboard, I would be interested to know which functions you have gotten to work. I am now at a state where I can control most everything, provided it is already running in the background. But I can't swipe my Sense desktop left and right, and I have trouble toggling certain switches like Wifi and Mobile data. Any suggestions or thoughts on these functions are appreciated.
Darren
Troubleshooting TIP: You can also run ADB when the phone is running in Normal Mode and you have the USB cable connected from your phoe to the PC. Then you can test certain keypresses through functions that are formatted in this way:
adb shell input keyevent 5
Click to expand...
Click to collapse
On my phone, this function will send the CALL event with brings up the phone from the desktop.
Other examples (you can also launch then from a *.cmd file):
If you have a terminal open on the phone, will send "ls -l"(includes the space-62 and enter-66):
@echo off
adb shell input keyevent 40
adb shell input keyevent 47
adb shell input keyevent 62
adb shell input keyevent 69
adb shell input keyevent 40
adb shell input keyevent 66
Click to expand...
Click to collapse
If you have a terminal open on the phone, will send "env|grep PATH":
@echo off
adb shell input text "env"
adb shell input text "|"
adb shell input text "grep"
adb shell input keyevent 62
adb shell input text "PATH"
adb shell input keyevent 66
Click to expand...
Click to collapse

[KEYLAYOUT] Hungarian keyboard for Droid 4

Hungarian has 9 special characters: áéíóöőúüű. Using this tutorial I remapped the keylayout as follows:
1. 'sym' + 'a' = 'á'
2. 'sym' + 'e' = 'é'
3. 'sym' + 'i' = 'í'
4. 'sym' + 'o' = 'ó'
5. 'sym' + 'u' = 'ú'
6. 'sym' + '7' = 'ü'
7. 'sym' + '8' = 'ű'
8. 'sym' + '9' = 'ö'
9. 'sym' + '0' = 'ő'
Shift & capslock gives you the capital ÁÉÍÓÖŐÚÜŰ, of course. For the changes to take effect, you have to have root access, and replace the following 7 original files in the /system/usr folder to my 7 attached modified files (in zip) using Cyanogenmod / Lineage OS file manager app (or any other root explorer app, e.g. the premium version of File Expert):
1. /system/usr/keylayout/Generic.kl
2. /system/usr/keylayout/omap4-keypad.kl
3. /system/usr/keylayout/qwerty.kl
4. /system/usr/keychars/Generic.kcm
5. /system/usr/keychars/omap4-keypad.kcm
6. /system/usr/keychars/qwerty.kcm
7. /system/usr/keychars/qwerty2.kcm
Don't forget to set the permissions of all the 7 new files using the above mentioned tutorial as follows:
OWNER: READ & WRITE
GROUP: READ
ALL: READ
After that, restart your Droid 4 - you'll have a fully functional HUNGARIAN layout physical keyboard.