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
Related
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!
National Lithuanian for standart HD2 keyboard (Ezinput) Full QWERTY Layout.
Cursor keys swaped (up, right etc..)
Cursor keys moved to left side of the keyboard
Vibro reduced to 1
National keys added (long press).
TAB key instead of XT9
Click volume reduced
No more need for FingerKeyboard or other if you do not demand much from the keyboard
Unistallable, so you can easily revert to original.
Haven't tested without policy disabled (unasigned apps). Perhaps you need to set this option with BsB Tweaks to install the cab.
v2.3 Landscape cursor keys on left side.
v3.1 Landscape cursor keys location something like on fingerkeyboard
Tool that helps to modify keyboard - XmlGui: http://forum.xda-developers.com/showthread.php?t=551813
If you like may work you can buy me some beer
Donate if you like my work.
.
Not that I would need it, cause I only use english keyboard for everything more or less, but good job anyway!
essensial said:
Not that I would need it, cause I only use english keyboard for everything more or less, but good job anyway!
Click to expand...
Click to collapse
It's not a problem to make better english version!!! If someone needs it is possible Just ask.
What I did - everything exept "national keys" are useful for everyone- lowered vibro, lowered sound, space moved to right, cursor key placed in first row. It is more comfortable for me.
I do not understand what the guys who made keyb were thinking about - in original layout space not reachable with right thumb, vibro too strong sound to loud - in 10 mins that things become anoying
And whats funny if i rotate screen 270 degrees - keyboard rotates also - but the keys that pop on press a not rotated, I mean they stay as on 90 degrees rotation layout ha ha ha
Why I'm telling that- on HD2 default layout would be more comfortable using 270 but not 90 as is .... Strange why cursor keys are on right side because that position is more comfortable to be on left..on 90 Try...
Is there anybody who can help/give me information about that damn HTC keyboard. I have some ideas but still didn't find out how to do (eg. how to make space of bigger width - where is the png that is used for space button ?)
Thanks in advance.
linuxis,
it's nice to see your work.
I'd like to know how did you make it, because I'd like to make something similar but I'd like to experiment a little ... and probably make a full Bulgarian layout.
What's required to accomplish this?
Updated to version 2.3 - cursor keys moved to left
I would be cool if you could make a keyboard with easy access to "æ, ø, å" for us danish users... I would seriously call you my god if you could pull that off
linuxis said:
Updated to version 2.3 - cursor keys moved to left
Click to expand...
Click to collapse
Nors ir nenaudoju LT kalbos, bet dekui anyway
Puiku. Bandysiu naudoti.
Thanks Linuxis ! Good job.
pankov said:
linuxis,
it's nice to see your work.
I'd like to know how did you make it, because I'd like to make something similar but I'd like to experiment a little ... and probably make a full Bulgarian layout.
What's required to accomplish this?
Click to expand...
Click to collapse
If you have a tool look inside the cab. Basically these files are modified.
0C09.xml
0D09.xml
1C00.xml
LQ_Bg.png
LQ_Bg_Inv.png
PQ_Bg.png
PQ_Bg_Inv.png
LQSym_Bg.png
LQSym_Bg_Inv.png
All layout is in xml files, they inside has links to the images.
By the images you can say what layout they represend.
LQ - Landscape
PQ - portrait
LQSym - numeric keyboard layout
xxx.xml xxx - code of the language you modify.
xml structure is very simple, just layout tag/ page tag (several pages eg in numeric layout)/ key tags with coordinates. You can find key by key ID, and change the key or the values on long key press.
I think that is enough to start.
pspbirte said:
I would be cool if you could make a keyboard with easy access to "æ, ø, å" for us danish users... I would seriously call you my god if you could pull that off
Click to expand...
Click to collapse
I just need to know what symbols shoud be placed where and what layout is the best for the danish symbols because I do not know danish . I mean - first row-long press (like lithuanian layout) or "æ" on "a" longpress ? And the symbols also needed.
linuxis said:
I just need to know what symbols shoud be placed where and what layout is the best for the danish symbols because I do not know danish . I mean - first row-long press (like lithuanian layout) or "æ" on "a" longpress ? And the symbols also needed.
Click to expand...
Click to collapse
Based on your information in this tread, I did make a Norwegian/Danish layout. Thank you very much to pull me in the rigth direction.
It's available here:
http://www.diskusjon.no/index.php?showtopic=1163736&st=2780&p=15366818&#entry15366818
Has anyone made a Swedish keyboard?
i'd like a german layout with the € symbol at the e key, the arrows in landscape on the other side, disabled xt9 key and the rest standard would it be possible?
or could you share the base files so i can mod them myself ?
nice i managed to do the mods for myself, at least the mods with changing the keys!
but as i saw the layout editing isn't that hard either, just redo all coords and the png file
nice linuxis for your inspiration!
but i asked myself, if it is possible to do smiles on a long press function, as i understood the xml code, it's not that easy cause a normal <char> tag prints all the keys while a <LP_char> tag gives the option to choose ...
Thanks mate for a long awaited LT keyboard.
endursa said:
nice i managed to do the mods for myself, at least the mods with changing the keys!
but as i saw the layout editing isn't that hard either, just redo all coords and the png file
nice linuxis for your inspiration!
but i asked myself, if it is possible to do smiles on a long press function, as i understood the xml code, it's not that easy cause a normal <char> tag prints all the keys while a <LP_char> tag gives the option to choose ...
Click to expand...
Click to collapse
One more tip for modders - check this tool XmlGui: http://forum.xda-developers.com/showthread.php?t=551813
It also helps for changing keyboard layout
One more tip:
index.xml in this file you can change vibro stregth and file to play (tick.wav)
Ačiū, linuxis, labai laukiau.
Thanks for a long awaited LT keyboard
Can somebody please upload 0C09.xml and 0D09.xml from a standard US keyboard, please? The files are located in the Windows directory.
Thanks... /TubGirl
I'm putting together a few alternate keyboard layouts (for the default Android keyboard) and wonder if the XDA community can give me some advice.
Colemak was pretty straightforward because the number of keys on each line is fairly similar to QWERTY, but Dvorak is giving me headaches.
For the Dvorak users out there, if you wanted to use it on your phone, what would you like the layout to look like?
My current design looks like so.
Code:
['][,][.][p][y][f][g][c][r][l]
[a][o][e][u][i][d][h][t][n][s]
[q][j][k][x][b][m][w][v][z]
There a few issues with this. First and foremost, there are no shift or delete keys.
Those can't be put on the top row, because you need to be able to long press those keys to get numbers. If users are willing to long press the middle row for numbers, I can put shift and del on top instead of [,] and [.], which you can always find on the bottom row anyways.
Suggestions, comments?
Here's what Colemak looks like.
http[:][//]i.imgur.com/PpH1pl.png
I'll upload a modified LatinIME.apk that you can push to /system/app once Dvorak is done. If you're impatient, the source is at https[:][//]github.com/dickfickling/android_packages_inputmethods_LatinIME (remove brackets... I can't post links)
Does anyone know what happened to the DVORAK keyboard layout in CM 10.1?
I'm using great CM10.2 port for Photon Q, but there is a thing that needs patching. If one set up more than one layout for the physical keyboard there is no means to switch them because key combination for layout switch is not user selectable and hard coded to "ctrl-space". There is no "ctrl" key on Photon Q physical qwerty keyboard so its impossible to switch layout. Please repost in mod thread (http://forum.xda-developers.com/showthread.php?t=2386684), because due to wise "10 posts" rule I can't post in dev threads by myself.
The asanti layouts that are included in CM 10.2 builds by Skrilax's buildbot map OK key to CTRL (and SYM to ALT key).
So OK+space can be used to switch the layouts.
The standard android layouts are not usable on Photon Q keypad because they are meant for the full PC style keyboards.
More asanti layouts for additional languages can be easily added, but someone has to create (or at least suggest) the desired key mapping.
kabaldan said:
More asanti layouts for additional languages can be easily added, but someone has to create (or at least suggest) the desired key mapping.
Click to expand...
Click to collapse
i would appreciate any links on documentation about how to create layouts with multipress. Unfortunately developer.android.com lacks multipress description (or I didn't found it).
I've originally implemented the multipress feature in CM for Motorola Milestone when I wanted to mimic the Motorola way of support for the Russian keypad on Milestone.
You won't find any documentation about it as it's not an official Android feature.
I'm currently still unsure about the future of the multipress implementation on Photon Q.
Anyway, the multipress function and the additional keyboard layouts are not necessarily directly related.
Please let me know which specific language do you want to support on the Photon Q keypad.
I guess I can help you to achieve what you want but I need to know your exact needs.
kabaldan said:
I've originally implemented the multipress feature in CM for Motorola Milestone when I wanted to mimic the Motorola way of support for the Russian keypad on Milestone.
You won't find any documentation about it as it's not an official Android feature.
I'm currently still unsure about the future of the multipress implementation on Photon Q.
Anyway, the multipress function and the additional keyboard layouts are not necessarily directly related.
Please let me know which specific language do you want to support on the Photon Q keypad.
I guess I can help you to achieve what you want but I need to know your exact needs.
Click to expand...
Click to collapse
I want support for both Ukrainian and Russian layouts on the Photon Q keypad. Attached here is two example layouts I've made.
Zixione said:
Attached here is two example layouts I've made.
Click to expand...
Click to collapse
Btw those layouts are in format of rukeyboard app. Because of its multipress support.
kabaldan said:
I guess I can help you to achieve what you want but I need to know your exact needs.
Click to expand...
Click to collapse
I'm sorry to ping you, but can you provide some info about how to proceed?
I would look at this section of the msm8960 tree for an indication of how the other files are built:
https://github.com/razrqcom-dev-tea.../tree/cm-10.2/unofficial/MSM8960Parts/res/raw
I've never done this before (never needed to mess with the language of the keyboard ) but I'd like to learn... looks pretty straightforward. Perhaps I will roll a build for you to test if I make good progress
Edit - OK I need your help... since I don't speak Russian or Ukrainian, I need to know which letters you want mapped where.
In fact, you might be able to do this yourself easier than I can do it for you. Look at that link I posted, and you basically want to make your own .kcm file. I need to know which characters you want mapped to what key - so for example the Croatian keyboard has C mapped to č with \u010d - the UTF8 character code for c with caron, or č.
I hope that makes sense. If you can't figure out how to build the file, perhaps at least find all the utf8 character codes you need, and then tell me which letters they should be associated to on the keyboard. I can do the rest .
I used http://www.utf8-chartable.de to help with the utf8 character codes...
Sorry, I've been too busy.
I've finally moved the alternate Photon Q keyboard layouts to a separate package and to the official CM repo:
https://github.com/CyanogenMod/andr...mmit/7f6a2c6a56aceca8505cfce97c5a2cf77612a791
I'd really like to add a Russian and Ukrainian map, only the lack of free time is holding me back.
Does this hw mapping look feasible?
http://mcgraver.ru/gravirovka_gallery/5-231/big/gravirovka_motorola_droid_4.jpg.jpg
kabaldan said:
Sorry, I've been too busy.
I've finally moved the alternate Photon Q keyboard layouts to a separate package and to the official CM repo:
https://github.com/CyanogenMod/andr...mmit/7f6a2c6a56aceca8505cfce97c5a2cf77612a791
I'd really like to add a Russian and Ukrainian map, only the lack of free time is holding me back.
Does this hw mapping look feasible?
http://mcgraver.ru/gravirovka_gallery/5-231/big/gravirovka_motorola_droid_4.jpg.jpg
Click to expand...
Click to collapse
Frankly, this is not the best variant. It's looks like layout from Droid 1/2 adapted to larger Photon Q keyboard. And original russian layout from Motorola was heavily criticised for combining frequently used letters and leaving alone some that should be combined. I'm attaching proposed layouts in pdf. I really would like to help, and can recreate them in format that is more convenient to you.
kabaldan said:
The asanti layouts that are included in CM 10.2 builds by Skrilax's buildbot map OK key to CTRL (and SYM to ALT key).
So OK+space can be used to switch the layouts.
Click to expand...
Click to collapse
I thought it will make sense to map CAPS key to CTRL. Double pressing SHIFT will act as if CAPS has been pressed, so dedicated CAPS key is not essential. Moreover, while pressing and double pressing SHIFT turns on CAPS LED, pressing actual CAPS doesn't.
In case if someone else will like this idea, you can change /system/usr/keylayout/keypad_8960.kl
from
Code:
key 58 CAPS WAKE_DROPPED
to
Code:
key 58 CTRL_LEFT WAKE_DROPPED
Also you can get changed file from attachment and upload to your phone.
kabaldan said:
The standard android layouts are not usable on Photon Q keypad because they are meant for the full PC style keyboards.
More asanti layouts for additional languages can be easily added, but someone has to create (or at least suggest) the desired key mapping.
Click to expand...
Click to collapse
Unfortunately, even after we make layout switching work, there is a little number of working "asanti" layouts, and no info about how to create more, so physical keyboard is still only partly usable.
The LG Optimus F3Q (D520) is a phone with "Five-Line Slide-Out QWERTY Keyboard with PC-Like Shortcuts" (LG website). Missing from the keyboard however, is the "Ctrl" key. This brief guide shall attempt to show how an arbitrary key may be remapped for it.
Root the phone. Saferoot by k1mu works for this phone, although I found that the phone did appear to hang should one try to reboot or power off using the hardware power button after rooting. Removing and replacing the battery boots up the phone without issue should that happen. Software-based rebooting works fine.
Install your favourite file explorer for root users. ES File Explorer File Manager worked well for me.
On the phone, navigate to the "/system/usr/keylayout" directory.
Make a copy of the "f3q-keypad.kl" file and put it somewhere safe in case you need to revert to it.
Edit the "f3q-keypad.kl" file using a text editor.
Look for the line "key 100 ALT_RIGHT WAKE_DROPPED". This corresponds to the fn key on the right side of the keyboard.
Replace "ALT_RIGHT" with "CTRL_RIGHT".
Exit the file and save. View it again to verify that your changes have been saved.
Reboot.
Try it out. Ctrl-C should work in a terminal emulator.
To have even greater control over the remapping, you would also need to edit the "f3q-keypad.kcm" file in the "/system/usr/keychars" directory.
Note! If you are using connectbot, please obtain at least version 1.8.1 from connectbot at GitHub. Version 1.7.1 of connectbot in the Google Play store did not recognise the Ctrl command when I tried. Thus, it may be possible that some other programs may also not recognise the Ctrl command.
Disclaimer: I mucked around a lot by trial and error as version 1.7.1 of connectbot was tripping me up, so I had changed a lot more things than what I had listed in the steps above. However, looking back at it, I doubt that any other changes I had made were truly necessary.
Helpful stuff:
appelflap has a button remapper app, which I installed, but didn't appear to be able to do what I wanted. However, the KeynrTracker.apk he linked is very helpful should you very quickly want to know which key corresponds to what.
References:
Key Layout Files
Key Character Maps Files
List of Unicode characters
Other thoughts:
I found Link2SD and Foldermount [ROOT] to be indispensible for this phone.
Thanks! I just might try replacing that pesky write and share app key with CTRL...
It would satisfy a request of mine for my F3Q ROM.
EDIT: Downloaded the app. Because pressing the key pushes the app to the background, it won't capture.
Last line of the file though says "WRITE_SHARE". Think I got somewhere.
Sure did, "WRITE_SHARE" now replaced with "CTRL_LEFT", and is working like a charm!
Glad this helped somebody !
joel.maxuel said:
Thanks! I just might try replacing that pesky write and share app key with CTRL...
It would satisfy a request of mine for my F3Q ROM.
EDIT: Downloaded the app. Because pressing the key pushes the app to the background, it won't capture.
Last line of the file though says "WRITE_SHARE". Think I got somewhere.
Sure did, "WRITE_SHARE" now replaced with "CTRL_LEFT", and is working like a charm!
Click to expand...
Click to collapse
Keth Tenderfoot said:
Glad this helped somebody !
Click to expand...
Click to collapse
how to deal with sticky keys?
Polish keyboard mapping on F3Q
Hi, I'm sharing my .kcm and .kl files of the F3Q used with the Polish characters mapped to the respective keys.
(Note to the German users of F3Q: you might edit my f3q-keypad.kcm file ,and map your äöüß characters to the aous keys, if you feel like having your language version of the mapping.)
Keyboard allocation modifications:
SEARCH key mapped to TAB
WRITE_SHARE key mapped to CTRL_LEFT
ALT_RIGHT key mapped to CTRL_RIGHT
PL layout: [ęąółżźćń] mapped on ctrl+[eaolzxcn]
PL layout: [„] mapped on ctrl+[k]
PL layout: [”] mapped on ctrl+[,]
The files have to replace /system/usr/keychars/f3q-keypad.kcm and /system/usr/keylayout/f3q-keypad.kl respectively to be active.
Hallo Pruszków,
Thanx for your polish Keymaps, great work!!!
At the moment I try to modfy them to German. It works fine so far, but now my question is, how can I use the right "fn" key (which is the new ctrl/alt key) without pressing at the same moment as the vowel/consonant, which I want to modify? With the left "fn" key I can first press the button, then release it and it holds its function.
Do you know what I mean?
Would be fantastic, if there is a solution too!
Best regards & dziękuję,
sÖren
fn/alt or ctrl?
Hi Sören,
Thanks for sharing your feedback. I'm glad my stuff could be of some help to you!
spacemoere said:
how can I use the right "fn" key (which is the new ctrl/alt key) without pressing at the same moment as the vowel/consonant, which I want to modify? With the left "fn" key I can first press the button, then release it and it holds its function.
Click to expand...
Click to collapse
Well, the "fn" labeled key was originally associated with the "alt" behavior. The "alt" keeps its mode when you press and release it. But I mapped the right "fn" to the "ctrl" bahavior, and... "ctrl" works just when you press and hold it. So, what to do in your case?
You might get back to the original "fn' mapping (in the .kl file) and keep the right "fn" as "alt", and then define äöüß (in the .kcm file) in combination with "alt" instead of "ctrl".
But...
there is a challenge with the special characters already mapped to the keys. E.g. let's take the key "u". Originally "alt" and "u" prints "+". When you'd map "alt" and "u" as "ü" then you'd loose any possibility to get "+". I have no good idea how to resolve that well. Maybe you'd map "+" to: "ctrl" and "u"? Then you'd use "ctrl" only from the key 59 (CTRL_LEFT), as the key 100 you'd map back to ALT_RIGHT.
The bottom line is: you'd need to choose between "alt" and "ctrl" stuff when deciding your settings.
In my case I took "ctrl" for my Polish mapping, as I'm used to press and hold the "fn" to print the Polish characters. If you're used to press and release, to print a German character, you might consider using "alt" instead.
I hope this helps.
Tschüs,
Bernard
Remapping IME
Thank you for the post Keth, very easy explained.
I am wondering about modifying not the standard character map, but the LG Keyboard IME.
I could not find any alternative input method with a good support for physical keyboard and good dictionaries, so I thought it may be better to modify the included input method than using a different one, correct me if I am wrong.
So I extracted the LGEIMEbin.apk from the system/apps directory, and opened it on the computer to figure out how to modify it.
Keyboard layout are saved in XML, so I supposed it should be easy to modify with a text editor like Notepad++, and just say for every key or combination of keys what kind of character do I want.
Well, I was wrong, as the xml do not contain any clear structure that is in any way possible to understand as it was for f3q-keypad.kcm and f3q-keypad.kl.
I tried to open all kind of xml files included in the LGEIMEbin.apk, and all of them presented non recognised characters, as you can see in the picture that can be found at this address:
img4web.com/i/D3RC42.png
Has anybody any hint of why notepad++ does not recognise those characters and how could I correctly visualise them?