Develop Bugs

Keyboard Layout

Hello. I've seen some threads about this, but none has helped me. So, I've a TP2 that came with a French ROM and now I've flashed it with a Portuguese one and it's working just fine. The problem is that the QWERTY keyboard is totaly mixed up, because the layout as been changed.
Assuming that it is not possible to change the hardware (if it is please tell me how!!!!!!), how can I modify the layout back to the original one???
Hope someone can help me and feel free to use this thread for the same kind of questions!

There is an easy way to fix it. You can do exactly as I did. Reflash the stock rom. Open a registry editor and export this folder
Code:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD
Then flash the rom you want and import that folder and you will be good.

gehzumteufel said:
There is an easy way to fix it. You can do exactly as I did. Reflash the stock rom. Open a registry editor and export this folder
Code:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD
Then flash the rom you want and import that folder and you will be good.
Click to expand...
Click to collapse
So, changing the hardware keyboard is not possible, or is it?
By the way, if someone could get the folder for me, someone that has the French version, i wouldn't have to reflash the stock rom would I?
Is it is possible i would try to find someone that could get it for me...

credinho said:
So, changing the hardware keyboard is not possible, or is it?
By the way, if someone could get the folder for me, someone that has the French version, i wouldn't have to reflash the stock rom would I?
Is it is possible i would try to find someone that could get it for me...
Click to expand...
Click to collapse
I just don't see why you would go through the hassle. It takes 30 minutes to flash the stock, get the stuff, and flash back. It will take much more time to find manuals, wait for parts, etc to swap the hardware keyboard.
Yes, if you had someone else that can export that part of the registry, you would be good.

gehzumteufel said:
I just don't see why you would go through the hassle. It takes 30 minutes to flash the stock, get the stuff, and flash back. It will take much more time to find manuals, wait for parts, etc to swap the hardware keyboard.
Yes, if you had someone else that can export that part of the registry, you would be good.
Click to expand...
Click to collapse
Quite true... I only thought about it because I'm so used with the QWERTY. But probably it's better just change the layout. Thank you for your help!!!

No problem!

I made the changes needed and it worked, by changing:
- HKLM\HARDWARE\DEVICEMAP\KEYBD
CurLang = 1036
- HKLM\System\CurrentControlSet\Control\Keyboard Layout
Active = 0000040c
But there is still something wrong, like when I press:
FN + A... it should appears the "à" but it doesn't
FN + Z... should be "è"
FN + R... should be "é"
FN + S... should be "ê"
FN + D... should be "ô"
FN + F... should be "ù"
I think this are the only ones that doesn't work right... does anybody knows how to fix it?

How to make my own rootfs.img

Enlighten me please... I want to edit the keymappings and define my own symbols and whatnot. I already found the init.etc/keymaps but how would i go about rebuilding the rootfs.img?
Thx.

How are you accessing rootfs.img? If you simply mount it as a loopback device in Linux, I don't think you have to rebuild it. Thor_Asgard listed the necessary commands needed to mount rootfs.img, if you don't know how to mount it.

How did I get into it? WinImg, or something like that. Looks like I gotta boot up some linux. HMM I could just use Rhobuntu to do it couldnt i?
Thanks for the link

andershizzle said:
How did I get into it? WinImg, or something like that. Looks like I gotta boot up some linux. HMM I could just use Rhobuntu to do it couldnt i?
Thanks for the link
Click to expand...
Click to collapse
Is it an "official" keymap update? Is it more complete or better than what is currently being used? Or even maybe a keyboard that has not been mapped at all yet? Would you like to put it in the main build, so that everyone else can use it? Contact babijoee or phhusson, they have access to update the main rootfs git!

Oh no I'd be doing this because my T Mobile TP2's ALT key doesn't work so I'd be swapping shift + letters for symbols instead of capital letters as well as including my own custom symbols like a < and > so i can text <3's to my girlfriend HAHA.
But yeah. It wouldn't be like an official thing, just tinker with which extra symbols i want on the keyboard such as < > { } [ ] | \

Hi!
I would like to make keymap for Finnish layout (only difference are FN-key combinations really). I already found the mentioned files from rootfs.img, but have a few questions:
What's the difference between rhod100* and rhod210* files?
Only place I found relevant things to change, is rhod210_microp-keypad.kcm file; what do I have to do to get the changes in use when I put the modified file back in place and into my Touch Pro 2?
Do I need to name it something different after modifications?
I'd like to submit it to general use when I'm done, so if you could just help me with these, I'd really appreciate it!
EDIT:
andershizzle said:
Oh no I'd be doing this because my T Mobile TP2's ALT key doesn't work so I'd be swapping shift + letters for symbols instead of capital letters as well as including my own custom symbols like a < and > so i can text <3's to my girlfriend HAHA.
But yeah. It wouldn't be like an official thing, just tinker with which extra symbols i want on the keyboard such as < > { } [ ] | \
Click to expand...
Click to collapse
Did you manage to create or modify files in the img file? If so, could you advise me how to do it?

"What's the difference between rhod100* and rhod210* files?"
They're just different layouts for different models. Rhod210 is based on one of the North American models, I forget which; Sprint or T-Mobile I think. The rhod100 layouts are the European ones.
"Only place I found relevant things to change, is rhod210_microp-keypad.kcm file; what do I have to do to get the changes in use when I put the modified file back in place and into my Touch Pro 2?"
You have to compile it to produce rhod210_microp-keypad.kcm.bin and put that into the rootfs. The tool to do this is only available inside the Android source. I have a compiled version of it here for Linux 32-bit, I can send you the tool or you can send me the .kcm and I can compile it for you, up to you.
"Do I need to name it something different after modifications?
I'd like to submit it to general use when I'm done, so if you could just help me with these, I'd really appreciate it!"
If you want to submit it for general use, yes, you have to name it something else. You should also submit it with a patch for the file 'init' in the rootfs.img image; look down the bottom and you can see how the keymap stuff actually works. The files are not actually used under their 'rhod*' names, if you specify in the kernel command line that you want a particular Rhodium keymap, it is copied to the filenames which are actually used. So add a little bit for your layout that corresponds to the others in there.
"Did you manage to create or modify files in the img file? If so, could you advise me how to do it?"
On Linux, you can just mount the rootfs.img file:
mount -o loop rootfs.img /mnt/some_mount_point
then edit stuff, then umount it. Dunno how to do it on Windows.

AdamWill said:
"What's the difference between rhod100* and rhod210* files?"
They're just different layouts for different models. Rhod210 is based on one of the North American models, I forget which; Sprint or T-Mobile I think. The rhod100 layouts are the European ones.
"Only place I found relevant things to change, is rhod210_microp-keypad.kcm file; what do I have to do to get the changes in use when I put the modified file back in place and into my Touch Pro 2?"
You have to compile it to produce rhod210_microp-keypad.kcm.bin and put that into the rootfs. The tool to do this is only available inside the Android source. I have a compiled version of it here for Linux 32-bit, I can send you the tool or you can send me the .kcm and I can compile it for you, up to you.
"Do I need to name it something different after modifications?
I'd like to submit it to general use when I'm done, so if you could just help me with these, I'd really appreciate it!"
If you want to submit it for general use, yes, you have to name it something else. You should also submit it with a patch for the file 'init' in the rootfs.img image; look down the bottom and you can see how the keymap stuff actually works. The files are not actually used under their 'rhod*' names, if you specify in the kernel command line that you want a particular Rhodium keymap, it is copied to the filenames which are actually used. So add a little bit for your layout that corresponds to the others in there.
Click to expand...
Click to collapse
Ok, I made some changes and renamed my new files. If you could do the compiling, I'd be very happy. I renamed them after rhod100, if that's the european model then. The attached zip contains the kcm and kl files.
Here are the rows to put in init:
Code:
elif /bin/grep -c 'physkeyboard=rhod100_fi' /proc/cmdline >/dev/null ; then
echo "USING EXPERIMENTAL RHOD100 FI LAYOUT"
cp -f /init.etc/keymaps/rhod100_fi_microp-keypad.kl /etc/keymaps/microp-keypad.kl
cp -f /init.etc/keymaps/rhod100_fi_microp-keypad.kcm.bin /etc/keymaps/microp-keypad.kcm.bin
cp -f /init.etc/keymaps/rhod100_uk_navi_pad.kl /etc/keymaps/raph_navi_pad.kl
If you could add these changes to the rootfs.img, I'd be very grateful!

hey good work guys! us CDMA guys have been desperatley seeking a verizon tp2 keyboard port. The symbols are way unmapped.... i only have windows. If someone could give me some instrucitons i'd happily try and help
Matt

Jekku said:
Ok, I made some changes and renamed my new files. If you could do the compiling, I'd be very happy. I renamed them after rhod100, if that's the european model then. The attached zip contains the kcm and kl files.
Here are the rows to put in init:
Code:
elif /bin/grep -c 'physkeyboard=rhod100_fi' /proc/cmdline >/dev/null ; then
echo "USING EXPERIMENTAL RHOD100 FI LAYOUT"
cp -f /init.etc/keymaps/rhod100_fi_microp-keypad.kl /etc/keymaps/microp-keypad.kl
cp -f /init.etc/keymaps/rhod100_fi_microp-keypad.kcm.bin /etc/keymaps/microp-keypad.kcm.bin
cp -f /init.etc/keymaps/rhod100_uk_navi_pad.kl /etc/keymaps/raph_navi_pad.kl
If you could add these changes to the rootfs.img, I'd be very grateful!
Click to expand...
Click to collapse
How did it go? Did you get a cool rootfs.img? I need a swedish keyboard layout..

[ROM][2/12/11][CHINESE] MIUI for G2 (v1.2.11)

http://bbs.gfan.com/android-575451-1-1.html
ignore the link at the top that one is mostly chinese the english version is provided hear thanks to da900
DOWNLOAD LINK: http://www.multiupload.com/PVZRB1NRHK
P.P.S. All you do with this pack is on your own risk. I am not responsable for any damages of your phone.[/QUOTE]

please aware that this rom is only contain about 20% english , most of words are chinese

u should be able to change it to english in the language and input settings

Is this newer than the QnD 1.2.4 rom?

Look at the number lol. 1.2.11 > 1.2.4

no that one has chinese this one does to thou dnt flash nevermind

dictionary said:
Look at the number lol. 1.2.11 > 1.2.4
Click to expand...
Click to collapse
XD I was thinking 4 > 1.
here's the changelog:
MIUI 1.2.11 version update:
Phone:
Add in the phone settings to add "call from the sensors used in the process" of setting
Fix the call log to the Canadian people through IP numbers to send SMS / MMS will bring IP prefix, resulting in the issue could not be sent
Theme:
Add support for setting alarm
Ringing in the new system comes with the option "mute"
Optimize the system comes with the choice of ring tones
Repair some of the theme of the correct format does not show the problem package
System Update:
Add WIFI connection can support the Ad-Hoc (peer to peer) network
Press the Backspace key fixed the problem miscarriage of justice
Local Backup:
Installed on the sd card repair program can not be the problem with the backup and recovery
Click to expand...
Click to collapse

terrelltp said:
no that one has chinese this one does to thou dnt flash nevermind
Click to expand...
Click to collapse
What? Slow down and make sense lol. Are you saying that you screwed up, and there is next to no English in the build?

terrelltp said:
u should be able to change it to english in the language and input settings
Click to expand...
Click to collapse
i repeat :
this rom does contain 20% of english translation only !
Even you change to english language :
your 80% of menu still display "Chinese".

So, this is useless unless you understand simplified Chinese. I'll wait on g4rb4g3 to release a port.
Sent from my htc.desireZED

Weren't there language packs you could install
Sent from my HTC Vision

Device Specific Language Packs
I think that language packs are device specific.. I haven't been able to find a language pack on the net for the G2.. though I did manage to a how to guide but I'm green to this stuff..
If somebody out here is familiar with how to do this guide and create a language pack for the G2 for us.. that would be helpful.
djmcnz said:
Okay guys, there's a lot of demand for this rom and for language packs but not yet a lot of people who know how to make the packs. Whilst I set up the crowdin translation project I can not create or maintain language packs.
So, here's a summary of the instructions required to create a language pack for MIUI (indeed for any app/rom). You need a collection of tools and a little patience but the process isn't too difficult so do give it a go.
Also note that this summary includes generalisations for brevity. These instructions assume you have a deodexed rom.
Introduction
For the purposes of this post language information is stored in XML strings in files on the Android system. In the case of MIUI and these instructions we will be dealing with .apk files (applications).
Within the apk files is a resources directory (/res) and within this are various values directories, there is a default values directory (/res/values) and alternative language values directories (e.g. /res/values-DE and /res/values-IT).
If the rom is set to use it's default language it will read values from /res/values although these may NOT be in English. In MIUI, all of the common Android ASOP values in /res/values are English but the (additional) custom MIUI strings are in Simplified Chinese.
If you select a different language in the ROM than the default then the appropriate values directory will be searched. If a suitable string that matches your language selection is found in the alternative /res/values-xx directory then that string will be used instead. If an alternative does not exist then the default will be used.
Example:
Code:
/res/[COLOR="red"]values[/COLOR]/strings.xml
<stop_button_text>[COLOR="Red"]Stop[/COLOR]</stop_button_text>
/res/[COLOR="red"]values-DE[/COLOR]/strings.xml
<stop_button_text>[COLOR="red"]Halt[/COLOR]</stop_button_text>
/res/[COLOR="red"]values-IT[/COLOR]/strings.xml
<stop_button_text>[COLOR="red"]Basta[/COLOR]</stop_button_text>
In this example, if the language is set to the default the word "Stop" will be used, if it is set to German the word "Halt" will be substituted in, likewise "Basta" for Italian.
So, to add languages to a rom (or app) or to make an app multi-lingual you need to either change the default strings in /res/values/strings.xml to the ones you want to use or, and this is the preferable approach, add a /res/values-xx/strings.xml with the translations you want. The first approach will work (changing the default strings) but is not recommended because the Android Open Source Project and Android development in general, defaults to English. It's best to use the built in language substitution capabilities of Android rather than to work around them. Indeed, if the MIUI devs actually added their strings in English to /res/values/strings.xml and the Chinese equivalents in the appropriate directory this rom would already be in English!
Adding Languages
To add a translation file (strings.xml) to an apk you need to:
decode the apk
create a language directory
add the translation files
recompile the strings
add the new strings to the apk
Which all sounds a little daunting but it's really quite straight-forward, rewarding when you see the result and a good way to understand how parts of Android work. Here's how you can do it.
1. decode the apk
You will need the excellent apktool from brut.all which you can get from the link below. apktool is relatively easy to use but includes some little tricks so you will need to read the wiki and thread about it.
Do NOT just post problems about apktool if you can't get it to work. The tool DOES work so if it's not decoding (or encoding) your apps correctly then you're probably doing something wrong. If you start with this understand BEFORE you ask for support you'll get a lot more help...
apktool: http://code.google.com/p/android-apktool/
wiki: http://code.google.com/p/android-apktool/w/list
thread: http://forum.xda-developers.com/showthread.php?t=640592
Please make sure you run the following command to include the MIUI framework in apktool. You only need to do this once for each framework. If apktool works with one rom and not the next then (re)install the framework for that rom.
Code:
apktool if framework-res.apk
Where framework-res.apk is the one from the rom you are working with. Make sure apktool can find (the correct) framework-res.apk before you run this command.
This thread is not for apktool support.
Now, before you proceed, decode a simple app from MIUI (such as updater.apk) using apktool, do not make ANY changes, then re-encode it using apktool. For example:
Code:
apktool d Updater.apk ./decoded/
apktool b ./decoded/ new_updater.apk
Use the -v (verbose) flag in apktool if you have problems and need to diagnose further.
Remember, Android uses a case-sensitive file system, make sure your capitalisation is correct.
Typically you will not be able to install this apk because it is not signed so if you want to test the process further you can now just try step 5 below using the two apks you have.​
2. create a language directory
Assuming you can decode/encode now, this is the easy bit. For your decoded app, navigate to the directory it was decoded in, then to the /res/ directory and simply create an empty directory for your language (e.g. /values-FR/) - use international naming conventions.​
3. add the translation files
Again, not too difficult this. Download the appropriate language file for your apk from the crowdin project linked below and, using the same structure as exists in /res/values/strings.xml create a new file called strings.xml in your alternative language directory (e.g. /res/values-ES/strings.xml).
The news strings.xml may contain as many or as few translations as you like. Remember, if a translation does not exist the default value from /res/values/strings.xml will be used.
Crowdin: http://crowdin.net/project/miui-rom-translation/invite
The xml formatting and tag names need to match exactly with the default strings.xml in /res/values although the translated file does NOT need to be complete.
It is worth remembering here that unless your source apk is already translated to English then some of the default values in /res/values/strings.xml will still be in Chinese, it would pay to check these.​
4. recompile the strings
Now, if you've done everything carefully and correctly this step is really easy, all you need to do is recompile the apk with apktool using the b (for Build) switch.
Code:
apktool b ./<decoded_apk_dir>/ <output_apk_name>.apk
If this throws errors or does not work then use the -v switch to turn on verbose mode and diagnose your problem. If you did the test in step #1 and it worked then any problem at this step is likely related to your news strings.xml. Back out the changes one by one until you have found the problem and try again.
If you simply can't get it to compile with your changes then try just making a single change to the default strings.xml file in /res/values and see if that works for you.
Do NOT sign the apk!​
5. add the new strings to the apk
Easy. Open your new apk with a zip program (like 7Zip for Windows) and copy out the resources.arsc file in the root directory of the apk. Now take that file and copy it into the source apk from the rom overwriting the existing one. This process replaces the strings but keeps the integrity of the signatures on the files.
You can now push the modified file to your phone, replacing the stock one, reboot and you're translated. Push the file using "adb push" or copy it into place using a root file manager, do not "install" the new apk. Make sure you put it in the correct place (replace the original) and reboot.​
Conclusion
This process will help you add languages to any app including those in the MIUI rom. Because it's a rom the strings are contained in many different apps as well as framework-res.apk. To completely translate the rom you will need to edit every apk that has strings in it.
You will need to do this every time an apk in the rom changes. If a new version is released and say launcher2.apk is changed but updater.apk is not, then you can retain your updater.apk but you'll need to re-edit your launcher2.apk.
When an app changes the default strings.xml may also change. In this case you will need to make corresponding changes to your translations.
Good luck and if you get really stuck there's lots of people in this that have achieved success and may be willing to help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=789566

MIUI 1.2.11 for Vision ENG
Hi, all. I like the MIUI ROM and as most of you want to have latest version as soon as posible. But I am not a dev and my skills in android development are very very poor. So, i followed the versions of MIUI by g4rb4g3. They all are very stable and fast. And i want to say once more HUGE THANX to him for his work.
But when i found this thread today in the morning i decide to make it in english. So, putting together the ROM from 1st post and ENG pack for N1 from MIUI-DEV.COM with some additional editing of built.prop and adding some apps. I made a pack. Flashed it and it is working fine.
P.S. The only chinese words that i found are in MIUI account registration in Accounts&sync.
Adding: Facebook, Twitter, VoiceSearch, Google Search, gMaps, Street, GMail etc. (all apks are up to date).
DOWNLOAD LINK: http://www.multiupload.com/PVZRB1NRHK
P.P.S. All you do with this pack is on your own risk. I am not responsable for any damages of your phone.

ok cool so basically u made a english version for that latest update cool cool

terrelltp said:
ok cool so basically u made a english version for that latest update cool cool
Click to expand...
Click to collapse
Maybe, you could add the link to ENG version to 1st post of this thread. Could you?

da900 said:
Maybe, you could add the link to ENG version to 1st post of this thread. Could you?
Click to expand...
Click to collapse
i thought thats what u did isint that link u posted the english version

terrelltp said:
i thought thats what u did isint that link u posted the english version
Click to expand...
Click to collapse
I think he means add the link that HE provided to your first post, so that users will actually have an ENG version, instead of the one you posted.

dictionary said:
I think he means add the link that HE provided to your first post, so that users will actually have an ENG version, instead of the one you posted.
Click to expand...
Click to collapse
That's what i mean. Thanx.

lol yes i did that now

da900 said:
Hi, all. I like the MIUI ROM and as most of you want to have latest version as soon as posible. But I am not a dev and my skills in android development are very very poor. So, i followed the versions of MIUI by g4rb4g3. They all are very stable and fast. And i want to say once more HUGE THANX to him for his work.
But when i found this thread today in the morning i decide to make it in english. So, putting together the ROM from 1st post and ENG pack for N1 from MIUI-DEV.COM with some additional editing of built.prop and adding some apps. I made a pack. Flashed it and it is working fine.
P.S. The only chinese words that i found are in MIUI account registration in Accounts&sync.
Adding: Facebook, Twitter, VoiceSearch, Google Search, gMaps, Street, GMail etc. (all apks are up to date).
DOWNLOAD LINK: http://www.multiupload.com/PVZRB1NRHK
P.P.S. All you do with this pack is on your own risk. I am not responsable for any damages of your phone.
Click to expand...
Click to collapse
WOOOO..good job . it's perfect !!!!!!!! work very well ~!! thanks a lot

[Q] port Statusbar of CZLB4 to any other FW

is it possible to port the statusbar with PacketData of CZLB4 to any other Firmware?

flo2204 said:
is it possible to port the statusbar with PacketData of CZLB4 to any other Firmware?
Click to expand...
Click to collapse
Quick Panel (status bar) is controlled by many files:
1) Rsrc1 > System > Rsrc > Black:
- QuickPanelBmp.rbm
- VoiceMemoQuickPanel.rbm (?)
2) ShpApp > SystemFS > SHP > QuickPanelApp.so (and also code in GeneralSoInfo.so.sig)
3) CSC (this is the problem! ) > CSCrcs > SystemCSC > String > QuickPanel.rsr
So, I try to change those files, but I'm not able to change status bar, maybe because there are other files that I don't know, or maybe because it's not possible to change those files (Wave loop, restart again and again).
Someone can help us?
Thanks!

thx for testing
did you tried to replace these files with the files of the CZLB4
sry can't test it myself at the moment

Tested.It gives boot loop

I tested it too. No problem with RCS (QuickPanel.rsr), and RC1(*.rbm) files
the problem is code in QuickPanel.so is not compatible with some others libraries
We can compare so from with and without 5th option and then edit code to fitbut who dares?
For me better option would be GPS on/off

How ? Just waiting for you

thx for testing

b.kubica said:
I tested it too. No problem with RCS (QuickPanel.rsr), and RC1(*.rbm) files
the problem is code in QuickPanel.so is not compatible with some others libraries
We can compare so from with and without 5th option and then edit code to fitbut who dares?
For me better option would be GPS on/off
Click to expand...
Click to collapse
I prefer "Data" But thanks for your work!
Do you think it's possible to make compatible QuickPanel.so? Thank you so much b.kubika!

in the QuickPanel.rsr of zclb4 is the "Data Button" called "IDS_QP_BUTTON2_DATA_ON_OFF"
this file should be somewhere
if we find this file we could add this to another fw
and in any other file should be something which load the command for enable or disable these things
Edit1:
what about to replace in the customFW "GeneralSoInfo.so.sig" the signature of the Custom with the ZCLB4 and then replace the "QuickPanelApp.so" with ne ZCLB4?

.rsr file is not the problem
I edited that file to make it support my own language and got the boot loop too
So please be quite for a while and let b.kubica do his magic
Yes it is .so file issue & I don't have enough skills to deal with it
Best Regards

its not a file, just string ID
Some steps:
1. change RCS - QuickPanel.rsr from ZC work on XX - only strings are missed but phone works
2. change RC1 - 2 *.rmb files - phones works normally, only graphics are missed
3. change *.so file - phone won't start normally - boot loop
some libraries from XX are not compatible with QuickPanel.so from ZC
that's all for now

b.kubica said:
its not a file, just string ID
Some steps:
1. change RCS - QuickPanel.rsr from ZC work on XX - only strings are missed but phone works
2. change RC1 - 2 *.rmb files - phones works normally, only graphics are missed
3. change *.so file - phone won't start normally - boot loop
some libraries from XX are not compatible with QuickPanel.so from ZC
that's all for now
Click to expand...
Click to collapse
Thanks kubika I'm sad
However I've got two Samsung Wave, one is the tester! If you want you can use it.

ok thx

Any News ?

i'd like to try somethink but i need the wave of my friend
maybe in 1 or 2 days...

Still no solution?

I have seen some CFWs that already added it, anyone know?

{PRO} [Q&A] How to change physical keyboard layout on xperia mk16i

As I'm a newbie here, I'm not aloud to post this in the dev section.
So I'll explain how you can simply change you're physical keyboard layout on Gingerbread and ICS easily without flashing an appropriate kernel for the Xperia Pro mk16i iyokan.
-So first you need root access.
-second, you need to install a root explorer like ES file explorer.
activate the root access to /system in the option of ES file explorer.
-ones you're here, you need to identify all the layout you're rom got. they are listed as xml files in the directory:
/system/usr/keyboard-config/layouts
my rom contains almost all keyset imaginable.
-Now you've find the name of your keyset find the file :
/system/usr/keyboard-config/keyprint.xml
-edit it with the file explorer integrated file editor.
-you'll find a file formatted with a fanzy SE header and that:
HTML:
<Keyprint>
<Script name="arabic" keylayout="arabic"/>
<Script name="cyrillic" keylayout="cyrillic"/>
<Script name="greek" keylayout="greek"/>
<Script name="hebrew" keylayout="hebrew"/>
<Script name="latin" keylayout="qwerty"/>
<Script name="thai" keylayout="thai"/>
</Keyprint>
-Choose the alphabet you use and put the name of your layout without the xml file extension.
if you're europeen or american, I guest latin will be you're choice.
For arabic, greek, croatian russian... and every other languages using an another alphabet I let you choose
So for example if I want to change my latin layout from Qwerty to Qwertz
I replace the line
HTML:
<Script name="latin" keylayout="qwerty"/>
by
HTML:
<Script name="latin" keylayout="qwertz"/>
-so save the file and reboot you're phone, you should now get the right keyboard set for you're phone.
Or you can edit it with adb by pulling the file and pushing it after (but it's a bit more tricky
Have a good night and if anybody can move my thread in the good section I'll be very pleased
ps:
All credits and inspiration came from the original post of ameer1234567890 which provide a lot of flashable layout.

I think this works only on stock and stock based ROMs. Can someone please confirm if this works on a ROM like CM7 or CM9.

I'd like to know too, because i used to use cm7 on htc dz but as cm7 or 9 are still in dev for mk16i I never tried them on mine for now

Hey.can u be more specific? How to do this?
I got the file..and now what should i do?
Thnx
Sent from my MK16i using xda premium

anamul.quader said:
Hey.can u be more specific? How to do this?
I got the file..and now what should i do?
Thnx
Sent from my MK16i using xda premium
Click to expand...
Click to collapse
I had an example in the tuto, if you still don't understand, I'll try to explain it again ;-)
Good luck

This does not work in 3rd party apps (smart keyboard pro and swiftkey), also on some cases chrome will misbehave as well. I think chrome is bypassing the xperia keyboard when it's trying to be super-secure such as entering passwords.
Chrome won't show you virtual keyboard at all in such cases so I think it can be safely filed under BUG but that won't help if you can't sign in. Using opera mobile as a workaround works..
I'm pretty sure the stock gingerbread finnish firmware played nice with smart keyboard pro. There's a link in the "root" Xperia pro thread where you can download "hotfix" for Xperia pro. These claim to be keyboard layouts for various languages. These are NOT the text files you describe here but the actual android keymap files.
They did not work for me, though, boo. I'll have to try again. The files in keychars-folder (MAKE BACKUPS!!) are .kcm.bin while the originals are called .kcm. I would assume both are not used at the same time. In keylayouts (backup bro) the replacement files are .kl, same as original but smaller.

3rd party keyboard has never been my point.
Stock android is handling physical keyboard a certain way, and virtual keyboard such as slide it or swiftkey do as they want with that kind of thing.
Switft never works correctly for me with stock rom or with custom rom.
Sorry if it doesn't work.
but if every software interprete keyboard there own way, we're damn lost. I never use Chrome but I guest it can also interprets keyboard layout its own way.
the flash fix you talk about is interesting, I'll try it asap. thks

Those keyboard layout/keychars files just make the HW keyboard stop working properly. I think they come from mini pro. Or at the very least they'd need some configury thingy somethere.
As a positive note, they DO make HW keyboard behave differently but swedish/finnish one definitely does not produce local chars.
Meh, I guess I need to fork up 2€ for wotanserver to get authentic finnish firmware.
FWIW I'm pretty sure stock finnish gingerbread firmware didn't have a problem with smart keyboard pro. And android + keyboard is a bit of a odd-man-out, we don't even get a forum..
Ed: Chrome works ok 95% of the time, I should file bug about text boxes where it goes crazy.

That's too bad, that it doesn't work for you.
Fact is we are at the border of android with physical keyboard.
And ow with nexus 3 without physical button except for sound and power...
I think (not hope) that physical keyboard for phones is almost arrived at its end.
Regarding stock firmwares, my update to ICS made by official sony companion just put me a Qwerty layout :-D so don't be so sure about stock firmwares ;-)

Umlauts in quertz
anybody know how to fix the orders of the umlauts for qwertz layout in the pop-up and make the SYM-Button working?
flashing of files newer worked for me, or a could'nt more use the shortcuts like copy-paste...
see also this thread: http://forum.xda-developers.com/showthread.php?t=1658959&page=20

Search trough the web for solution. nothing.
Physical keyboard has a driver, or own FW or sumthing?
And can i have the stock xperia physical keyboard app?
My sym button doesn't work, my direction arrows are weird, qwerty-stroke keyboard layout. But i accept the latin one too
Or where is this "driver"-stuff in the ROM? Can i copy from old ROM (which one is working), to ICS .587 (which don't)?
Thanks in advance

I installed the arabic script from ameers collection and the language changed to arabic.. thing is my keyboard has the same layout as arabic version but I wanted the english characters.. I tried your method but whatevr script I keep for my keyboard layout, it still follows the same script even after rebooting.. pls help..
Sent from my MK16i using xda app-developers app

ilfunx said:
I installed the arabic script from ameers collection and the language changed to arabic.. thing is my keyboard has the same layout as arabic version but I wanted the english characters.. I tried your method but whatevr script I keep for my keyboard layout, it still follows the same script even after rebooting.. pls help..
Sent from my MK16i using xda app-developers app
Click to expand...
Click to collapse
I'm having the same problem, so if you found a solution over the last few months, could you share it with me, please?

Method not working
Kiwyxda said:
As I'm a newbie here, I'm not aloud to post this in the dev section.
So I'll explain how you can simply change you're physical keyboard layout on Gingerbread and ICS easily without flashing an appropriate kernel for the Xperia Pro mk16i iyokan.
-So first you need root access.
-second, you need to install a root explorer like ES file explorer.
activate the root access to /system in the option of ES file explorer.
-ones you're here, you need to identify all the layout you're rom got. they are listed as xml files in the directory:
/system/usr/keyboard-config/layouts
my rom contains almost all keyset imaginable.
-Now you've find the name of your keyset find the file :
/system/usr/keyboard-config/keyprint.xml
-edit it with the file explorer integrated file editor.
-you'll find a file formatted with a fanzy SE header and that:
HTML:
<Keyprint>
<Script name="arabic" keylayout="arabic"/>
<Script name="cyrillic" keylayout="cyrillic"/>
<Script name="greek" keylayout="greek"/>
<Script name="hebrew" keylayout="hebrew"/>
<Script name="latin" keylayout="qwerty"/>
<Script name="thai" keylayout="thai"/>
</Keyprint>
-Choose the alphabet you use and put the name of your layout without the xml file extension.
if you're europeen or american, I guest latin will be you're choice.
For arabic, greek, croatian russian... and every other languages using an another alphabet I let you choose
So for example if I want to change my latin layout from Qwerty to Qwertz
I replace the line
HTML:
<Script name="latin" keylayout="qwerty"/>
by
HTML:
<Script name="latin" keylayout="qwertz"/>
-so save the file and reboot you're phone, you should now get the right keyboard set for you're phone.
Or you can edit it with adb by pulling the file and pushing it after (but it's a bit more tricky
Have a good night and if anybody can move my thread in the good section I'll be very pleased
ps:
All credits and inspiration came from the original post of ameer1234567890 which provide a lot of flashable layout.
Click to expand...
Click to collapse
Good Post, i tried it but it does not work after i reboot.
So my keyboard is still the QWERTY layout instead of QWERTZ
Also, some detailed instructions on ES Explorer.
Once you open ES Explorer, Left Drawer --> Go to Tools --> Root Explorer --> Mount RW --> Set / to RW
Now you can follow the steps to edit the keyprint.xml
Again let me remind you, i tried this and it does not work. So if i have done it the wrong way, please let me know.