I have a tilt and it seems that my fn is not working properly.
what i mean is that when i use the fn + another key it never corresponds to the key that is on my keyboard...
ex:
fn + E = ? in my case it always give me something different than what in blue on my keyboard.
can anyone help me fix this problem
thank you for your time in advance
Have you flashed a different rom to it? possibly one written for the Kaiser? is so look for the the keyboard fix there is one I've seen it I just don't know where it was but I know it was here.
This is where you want to go if you have an AT&T Tilt: http://forum.xda-developers.com/showthread.php?t=334911
For Example:
This will make my Fn + X to be "
Click to expand...
Click to collapse
ive intalled the cab fix you guys suggested and still no luck
btw ive flashed the duttys v3 rom
does anyone has the same problem???
it requires a soft-reset... have you done that?
Hi,
I just installed a german ROM on my english TyTN II, so the hardware keyboard is set to german. I've only found cabs to switch from english to german but not the other way...
I also found that:
changing HKLM|Hardware|DeviceMap|Keybd > CurLang to your CountryID
Click to expand...
Click to collapse
But in my registry there is no 'CurLang'-value at that path.
Have I to set value by my self, or is there an other way to switch the layout back?
Maybe someone got an ideae
Greetings Oli
P.S.: I use the "M-Diamond v1.4 Full with SqlCE Mobile 3.5" (WM 6.1) ROM
Hi, welcome to XDA !
This topic has be adressed already. Addtionnaly, it is recommended to post in the thread of your ROM, as this problem could ROM specific .
If you do not have CurLang, you could try to create it (DWORD) and set the Hexadecimal value to 407 (which is the value for German layout).
Then soft reset, worth the try . If it's still not working, try searching around, you may find quickly what you want!
Yea I've been studying the keyboard related posts here before I posted the message. I only found topics that dealt with us-layout->other-layout problems and for that, there are many fixes around.
But right now I found a workaround witch worked in that post.
THIS IS NOT A TILT KEYBOARD FIX SOLUTION but a workaround for people having an original TYTN II with QWERTY hw keyboard and ROM in a differnet language. Below sample is for a German ROM flashed into a US original KAIS130:
There are few registry entries you have to change.
First set:
[HKCU\MUI]
CurLang = 1033 (or HEX 0x409) - IMPORTANT, set this first!!!
Then go to
[HKLM\System\CurrentControlSet\Control\Layouts]
and - to be on the save side - go through all SUB KEYS and set all "00000407" values to "00000409" (Do not rename the keys themself!)
there is still one SUBKEY which has your language written as a string:
[HKLM\System\CurrentControlSet\Control\Layouts\0000 0407]
"Layout Text" = "German"
Change the above entry to "US", soft reset your device - done!
- - -
Just keep in mind: above sample is for a German ROM (407) - if you flashed a different language to an english device, then the "407" will be something corresponding to your language.
Click to expand...
Click to collapse
Greetings Oli
Having just seen an image of the AT&T branded TP2 at engadget, I see they messed with the keyboard layout compared to the HTC original. Other carriers have also tinkered, such as moving the FN key and including or not the Ctrl key.
I've only ever flashed roms before on an Athena (Dopod U1000) and Ipaq hx4700, which didn't have this issue, so I never thought about this before. If I get the AT&T version, will there be compatibility problems when flashing cooked roms for the unbranded version? I know that cdma versions need their own cooked roms. Will it be the same situation for users of the AT&T and T-MO USA versions?
Thanks.
evermore said:
Having just seen an image of the AT&T branded TP2 at engadget, I see they messed with the keyboard layout compared to the HTC original. Other carriers have also tinkered, such as moving the FN key and including or not the Ctrl key.
I've only ever flashed roms before on an Athena (Dopod U1000) and Ipaq hx4700, which didn't have this issue, so I never thought about this before. If I get the AT&T version, will there be compatibility problems when flashing cooked roms for the unbranded version? I know that cdma versions need their own cooked roms. Will it be the same situation for users of the AT&T and T-MO USA versions?
Thanks.
Click to expand...
Click to collapse
The same problem occured on the Kaiser, once Cooked ROM's appear I'm sure someone will make a CAB to set the keyboard layout right for your device. Just install the CAB after flashing each ROM and you'll be fine - put it in your UC / SASHMI script so you never forget .
Dave
Thanks very much, Dave. That's great news.
I think the Hardware Keyboard Layout is defined with that Registry entry:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME\KeyboardLayouFiles]
For german TP2's it is:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME\KeyboardLayouFiles]
"07FF"="eT9.Rhodium.0407.kmap.txt"
and for WWE TP2's it is:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME\KeyboardLayouFiles]
"07FF"="eT9.Rhodium.WWE.kmap.txt"
After dumping the official ROM and making Packages, I found some interesting files inside the IME Engine Western package:
eT9.Rhodium.0C0A.kmap.txt
eT9.Rhodium.040C.kmap.txt
eT9.Rhodium.0407.kmap.txt
eT9.Rhodium.0410.kmap.txt
eT9.Rhodium.0414.kmap.txt
eT9.Rhodium.0419.kmap.txt
eT9.Rhodium.Cingular_US.kmap.txt
eT9.Rhodium.swiss.kmap.txt
eT9.Rhodium.TMOUS.kmap.txt
eT9.Rhodium.wwe.kmap.txt
eT9.Rhodium.wwe_ara.kmap.txt
eT9.Rhodium.wwe_rus.kmap.txt
Thanks animelover! This works in the new 6.5 NRG ROM for my german layout!
In [HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME\KDBFiles] I changed the entry 07FF to "eT9.HQD_GER.kdb"
while in [HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME\KeyboardLayouFiles]
I changed the entry 07FF to "eT9.Rhodium.0407.kmap.txt" (as stated in the post above).
I'm not sure if the first step is 100% necessary, especially for other layouts, but it worked for me.
Note for users with the german layout: The kmap file needs to be edited by switching Z and Y in the VK column. My kmap is attached...
Has anyone gotten the T-Mobile TP2 layout to work?
brianb7590 said:
Has anyone gotten the T-Mobile TP2 layout to work?
Click to expand...
Click to collapse
no luck so far
I opened the eT9.Rhodium.TMOUS.kmap.txt from my \windows in notepad, but don't know how to fix it - the ALT key does not work (its called the FN key in the txt file - which makes sense since in Fuze and kaiser, it was FN key) and the CTRL key does not work - the txt file - leaves that as blank.
This is what it says:
___
// Row 5
{0xEC 0xEC 0x00 0x00 0x00 0xff} // FN - 0xEC = FN
{0x11 0x11 0x00 0x00 0x00 0xff} // CTRL
{0xF2 0xF2 0x00 0x00 0x00 0xff} // MSG - 0xF2 = MSG
___
Any ideas?
what did control do on the original tmobile keyboard because now the ctrl key at least works as the alt key i just found out.
hondamx525 said:
what did control do on the original tmobile keyboard because now the ctrl key at least works as the alt key i just found out.
Click to expand...
Click to collapse
Ctrl + C - copy
CTRL+V - paste
just like on a desktop
<post deleted; wrong thread, sry>
on tmobile touch pro2 US with any cooked ROM (Fursion Power or EnergyROM) - the ALT and CTRL are switched on the h/w keyboard - anyone know enough about kmap.txt to be able to switch it out?
would be a great help!
Thanks!
load stock ROM, use Remote Registry to export all settings that have to do with keyboard, load custom ROM, copy registry settings over and your control key should work. If anyone finds the right keys then post so everyone knows the fix.
brianb7590 said:
Has anyone gotten the T-Mobile TP2 layout to work?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=4371210
should ask some of the guys that already cooked ATT official rom and the leaked tmobile rom the keyboard set up should already be in there the should have it
Hi all,
I'm having problems getting my Sweish/Nordic keyboard to work as it should now that I've flashed the NRG ROM.
In my original stock rom the registry entries were [HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME\KDBFiles] 07FF as "eT9.HQD.kdb" and [HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME\Keyboard LayouFiles] 07FF as "eT9.Rhodium.0414.kmap.txt". Withese settings in NRG all that happens is that the FN and Shift keys stop working. The basic characters work fine but any capitals or "special" characters are shot.
Any ideas on what I should try next?
Thanks/McHan
McHan said:
Hi all,
I'm having problems getting my Sweish/Nordic keyboard to work as it should now that I've flashed the NRG ROM.
In my original stock rom the registry entries were [HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME\KDBFiles] 07FF as "eT9.HQD.kdb" and [HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME\Keyboard LayouFiles] 07FF as "eT9.Rhodium.0414.kmap.txt". Withese settings in NRG all that happens is that the FN and Shift keys stop working. The basic characters work fine but any capitals or "special" characters are shot.
Any ideas on what I should try next?
Thanks/McHan
Click to expand...
Click to collapse
You exported the wrong keys. These aren't what is the issue. Download my reg fix for the TMOUS TP2. I forget the exact location, but it is in that reg file.
gehzumteufel said:
You exported the wrong keys. These aren't what is the issue. Download my reg fix for the TMOUS TP2. I forget the exact location, but it is in that reg file.
Click to expand...
Click to collapse
Thanks gehzumteufel. Naive question, but do you have any idea where I might find the correct registry values for my Nordic keyboard?
Thanks/M
Hm, I had hoped that changing the [HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD] "CurLang" value to 414 (which was the local language I had on the original SW-KB) would do the trick. But no, no such luck The key that's in the T-Mobile"fix" but which I don't have now is "LayoutID"=dword:00000213. Any idea what this does?
Norwegian keyboard layout file
Hi, thanks to the guides on here, I made a norwegian layout file for the Rhodium. It worked perfect with the NRG 6.5 ROM.
It is attached, either copy it to the windows folder using Total commander and then change the registry value to "eT9.Rhodium.wwe-nor.kmap.txt" or simply rename the original wwe file first and then copy this file in using the standard name (eT9.Rhodium.wwe.kmap.txt) to avoid editing the registy.
Hi all, this will be my very first post
I've been flashing my kaiser for a few weeks now, trying out what I like best.
There is however one problem that keeps re-appearing and it's driving me crazy!!!
It's the keyboard, letters are OK but the FN key is weird and totally different than the problems allready posted (yes I can use the search option)
FN+ Q = 2
FN+ W = 1
FN+ E = /
FN+ R = /
FN+ T = 3
and so on!!! There is not 1 key that i can press to get me a ? or a !
1234567890 are doing fine and also the shortcut for file explorer
please help me!!
greetings
mtsharkbait1985 said:
Hi all, this will be my very first post
I've been flashing my kaiser for a few weeks now, trying out what I like best.
There is however one problem that keeps re-appearing and it's driving me crazy!!!
It's the keyboard, letters are OK but the FN key is weird and totally different than the problems allready posted (yes I can use the search option)
FN+ Q = 2
FN+ W = 1
FN+ E = /
FN+ R = /
FN+ T = 3
and so on!!! There is not 1 key that i can press to get me a ? or a !
1234567890 are doing fine and also the shortcut for file explorer
please help me!!
greetings
Click to expand...
Click to collapse
ok I am a lot further now.. I now am able to use the FN key as it should be...BUT!!!
By using the disable et9 utillity that shifu has included my keys work fine now, however I now have the most annoying autocomplete function EVERRR..
(example)
I'm dutch and we have a word " wel " but if I type this and hit SPACE after it, it changes to " we'll " ON IT'S OWN!
please help me...i'm getting desperate
Hello!
This may be an odd request, but I need a cab file that will change my phone's layout to the P4350's
What happened was, I flashed a ROM called f1rick's ROM v3.6, awesome ROM by the way! But I'm guessing it is for a T-Mobile Wing. I have an HTC P4350...
What the issue is, some keys are swapped around, for example the "atsign" is suppose to be Fn + Q ... but Fn + Q = (
I now have to Fn + L (which is actually for "=") to get the atsign sign!
The last thing I want to do is go performance ROM hunting and hours of flashing, so is there a cab file I can apply to correct the layout?
Thanks