Hi,
I would like to ask if someone knows which dll's needed in order to work the builtin keyboard?
Actually i have the original Greek rom which support to write greek letters in 160 charct. SMS and also in general with keyboard.i suppose that some custom specific dll's are used for this and now i needed to import in WM6.
Thanks
I don't understand, are you looking to change your keyboard layout? In this case, you just need to edit a registry key. I can't remember the exact key so you'll have to do a small search; one of those contains a list of values for the various layouts with it stating that the UK keyboards hava a "locale" value of 0809...
Hi,
Not the layout of keyboard.
I am looking to change the character of each english letter of keyboard
hardware of software keyboard?
Hardware keyboard.
Edit \Windows\sym.txt
Or just install AEKMap and put the Greek Keyboard .aek file. There is also one for 160 chars sms. Pm me if you want it
Does anyone know how to change the keyboard layout on the Vox/S710 to match the S730.
E.g. Shift the top row of letters (QWERTYUIOP.) to (.QWERTYUIOP) so that typing is more natural?
Hope that makes sense! Any help greatly appreciated.
Hmm... My Vox comes with .QWERTY layout. Anyway, I think you should change the locale in system registry. Try this key (make sure you've created a registry backup first):
HKLM\HARDWARE\DEVICEMAP\KEYBD
Set the value "CurLang" to 0x409 (1049) and reboot the phone. That will probably shift your layout.
wont this just complicate things as ur keys will be messed up. so the letters will be:
.qwertyuiop
but the buttons on the actual keyboard will say:
qwertyuiop.
way more trouble than its worth
Maybe... but I keep making mistakes when typing, as I'm assuming that the keyboard layout is as per a normal keyboard (or Hermes, which is what I used before).
The fix works nicely - for the top row.
But...
Now the number keys are not 'aligned', as per the layout on the keyboard. Is there a way to move these - bearing in mind that the numbers are used using the 'fn' lock?
You might want to try creating your custom layout. With AEKMap you can do most anything with hardware keys. Here it is.
It would take a lot of time to create a layout from scratch, so I suggest using my (Roan) or other people's layouts as templates.
Hope this helps.
Sounds like it's more trouble than it's worth. Depends on how much your personal (or work?) time is valued at I guess..
Just deal with it and get used to the keys. I'd expect it to be different to your Hermes, it's a different phone!
Is it somehow possible to add extra characters to on-screen keyboard of FouchFlo 3D? When you press and hold a button, list of extra characters pop up, but it does not contain characters specific to my language.
I am hoping that there is a configuration file somewhere or maybe some registry entrie. Wouldn't make sense to hard-code these characters.
Unfortunately HTC support was of no help. It's a pity that there is a specific version of Diamond 2 for Eastern Europe, but E-European languages are not supported.
Bumping in hope that somebody could help...
You may want to give some other 3rd party keyboards a try..there's a really great one I'm drawing a blank on, but search around a bit and you will find it.
hi,
after couple of searches the only way to change language at keyboard is 'Ctrl + Shift', but this combination worked only if i not in english language, otherwise its not and then i need to click on the button on buttom screen to choose another keyboard.
if i want to write at 2 language at same paper or document? i cannot change quickly like Alt+Shift at PC's ?
any help?
thanks
Edit Aug, 16: I have found out that the XT9 subsystem is used for specifically our docking stations. If you go to Settings -> Languages & Input -> ASUS Keyboard -> About, you'll see the big stupid XT9 icons. Therefore, our keyboards have to be using the XT9 database files and the only way to procure different languages seems to be via ASUS (that's what Nuance's site said anyway). The manipulation of the keyboard dock layout mentioned below seems to be our only way until 1) we procure these additional language files from a different source (might require tweaking), 2) someone with an XT9 license makes the files for us, 3) we find an editor that we can use to create / edit the XT9 files, or 4) we find out how to rework the keyboard framework to use different altogether.
Because of the way our system uses the XT9 subsystem, the JB keyboard update itself won't help us. Officially, it all depends on what ASUS gives us to enable additional langs/layouts for our keyboard docks.
---- Original
All right. Here is what I have collected thus far regarding the way that Androids handle keyboard layouts. I put it here in development as I'm sure only the people in this area would really have an interest/use for it. As I still have yet to satiate my own curiosity and preference for a different keyboard layout, I do hope that somehow someone can figure out how to get us proper alternative keyboard layouts.
----
Our keyboard layouts are spread into 2 separate data form categories: the buttons and the characters. The buttons are the real buttons (physical keyboard or virtual) that have a specific numerical identifier. The characters are the glyphs and their various states that can occur when using character modifier buttons (shift, control, alt, etc) when the associated key number button is pressed.
All of these values are found in "/system/usr" with those found in the "keychars" directory being for the glyphs and the "keylayout" for the arrangement of button number with associate character represented. Both types of files (".kcm" for characters and ".kl" for layours) are really just text documents and seeing the association between the two is easy during comparison:
Example: 'A'
in the "Generic.kcm", it is defined as
Code:
key A {
label: 'A'
base: 'a'
shift, capslock: 'A'
ctrl, alt, meta: none
}
while in the "Generic.kl", it is defined as
Code:
key 30 A
Therefore, Key 30 is Mapped to Key 'A' that can have the states 'a' or 'A'.
Unfortunately, these two files that constitute a layout are combined in the XT9 subsystem and not totally used "as is". There is a configuration text file for the XT9 database that can be found at "/system/usr/xt9/config/databases.conf" and in there you can see mappings of languages to database files (also note that all are derived from QWERTY format). You'll notice that the databases are of type ".kdb", ".ldb", or ".dat". A quick search on the 'Net will tell you that the ".kdb" is a keepass file and ".ldb" is a Microsoft Access file. These are wrong! I suspect they are both the same file type but I do not know of what type they are so I cannot view nor edit them. I have tried the "suggested" programs and I tried SQLite since that format is used for our "registry". I'm thinking that they might be T9 database files but I haven't found an editor to even verify that hypothesis.
The organization used to create our layouts is highly flexible and therefore really complex. There's some type of combination of format + language that is calculated in order to determine the correct layout to use. No wonder ASUS (and practically everybody else) has limited keyboard layouts. Additionally, this scheme also controls the majority of our hardware keyboard buttons as well.
For the physical keyboard dock, we have direct ways of manipulating the hotkeys or brute-forcing the layout within our grasp. The hotkeys are somehow contained in our "/system/app/keyboard.apk" and for the basic layout, all we really need to do is modify the "asusdec.kl" to shoehorn our preferences into the system.
An example to test if you want a DVORAK keyboard layout is to copy & paste this into the asusdec.kl and restart (back up the file first!) and it should now be in DVORAK format (though it will not be selectable from the menu). Same thing for the "Generic.kl" - edit the chars associated with the key numbers and the buttons will change values. I do not recommend this method as it is hacky/evil/dirty/bad and all sorts of other negative adjectives. However, until a better way is found, it may be our only real way of modding the keyboard the way we want.
I humbly ask if there are any of our beloved geniuses with further knowledge on how this system to please post additional information here in hopes that maybe we may create better keyboard options for our devices.
Thanks for reading
PS: Found out that Jelly Bean will have additional keyboard layouts. From this thread, "Android 4.1 includes 27 international keymaps for keyboards, including Dvorak." That's a good thing.
Wow, thanks. The information you've provided, is really helpful, and well layed out.
Sent from my EVO using Tapatalk 2
LMMT said:
Wow, thanks. The information you've provided, is really helpful, and well layed out.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I'm glad that you think so though I don't know how helpful this post will actually be. This is a rare topic to find information on and even rarer to find information that is directly useful. However, I hope that the information I provided would be at least enough to give us a direction when/if development for keyboard layouts start.
Maybe I'll go over to the Prime forums later to read up further on any advancements they have made.
alienedd said:
Edit Aug, 16: I have found out that the XT9 subsystem is used for specifically our docking stations. If you go to Settings -> Languages & Input -> ASUS Keyboard -> About, you'll see the big stupid XT9 icons. Therefore, our keyboards have to be using the XT9 database files and the only way to procure different languages seems to be via ASUS (that's what Nuance's site said anyway). The manipulation of the keyboard dock layout mentioned below seems to be our only way until 1) we procure these additional language files from a different source (might require tweaking), 2) someone with an XT9 license makes the files for us, 3) we find an editor that we can use to create / edit the XT9 files, or 4) we find out how to rework the keyboard framework to use different altogether.
Because of the way our system uses the XT9 subsystem, the JB keyboard update itself won't help us. Officially, it all depends on what ASUS gives us to enable additional langs/layouts for our keyboard docks.
Click to expand...
Click to collapse
I've already contacted ASUS regarding is_IS layout and they will not support it, so I would not hope for much change there. It would be great if ASUS would release some kind of remapping tool so we could map the keys correctly ourselves.
I'll be keeping a close eye on this thread, and will post if I find something interesting.
Okay, after googling a bit I found an app called External Keyboard Helper Pro that allows me to enable my layout perfectly on the dock.
I'd recomend people seeing if it has their layout of choice.
Edit: There is a thread here on xda: http://forum.xda-developers.com/showthread.php?t=1541916
Doing these changes after JB
alienedd said:
...
Example: 'A'
in the "Generic.kcm", it is defined as
Code:
key A {
label: 'A'
base: 'a'
shift, capslock: 'A'
ctrl, alt, meta: none
}
while in the "Generic.kl", it is defined as
Code:
key 30 A
Therefore, Key 30 is Mapped to Key 'A' that can have the states 'a' or 'A'.
...
PS: Found out that Jelly Bean will have additional keyboard layouts. From this thread, "Android 4.1 includes 27 international keymaps for keyboards, including Dvorak." That's a good thing.
Click to expand...
Click to collapse
I had modified the .kcm and .kl files in ICS and had successfully mapped Bluetooth->Mute to be F1-F12 while allowing Caps lock (when on ) to restore those buttons to their original function. I had also modified the Lock and Wireless buttons to function as Delete and ESC respectively. I had made a few other changes as well. After updating to Jelly Bean I made a backup of the new files that had overwritten my edits and then recopied my edits over the new files and rebooted. The edits no longer worked at all and most of the keys I had made changes to now did nothing. I then tried to restore the backups of the files I had changed and then rebooted but nothing changed even though they were seemingly back in their original configuration. Does anyone have any clue as to what might have happened?
Also, anyone else have any success in JB in changing their layouts?
daerwynn said:
I had modified the .kcm and .kl files in ICS and had successfully mapped Bluetooth->Mute to be F1-F12 while allowing Caps lock (when on ) to restore those buttons to their original function. I had also modified the Lock and Wireless buttons to function as Delete and ESC respectively. I had made a few other changes as well. After updating to Jelly Bean I made a backup of the new files that had overwritten my edits and then recopied my edits over the new files and rebooted. The edits no longer worked at all and most of the keys I had made changes to now did nothing. I then tried to restore the backups of the files I had changed and then rebooted but nothing changed even though they were seemingly back in their original configuration. Does anyone have any clue as to what might have happened?
Also, anyone else have any success in JB in changing their layouts?
Click to expand...
Click to collapse
No i'm in the same position you are in i managed to edit my kcm file exactly how i wanted it for ICS but now i have "upgraded" to JB and the changes have been lost it appears JB does not use the files in the XT9 folder at all and i cannot find out how to edit it with JB!!! Very frustrating.
All i want is the backslash key to be a backslash in UK "mode". It is producing a # unless i change modes which is very annoying each time i want it. Wondering if there is any other solution than to downgrade back to ICS?
Please help us someone!
Thanks