Tried EVERY rom, nothing fixes keyboard lag

[scrosler]

Originally Posted by YouMayLose

lol im with metropcs.. i love to text.. this is my 1st windows phone..i went with the 1 with a keyboard... i have to pay full retail for a phone.. why buy another?

Originally Posted by l2yangop

I have tried basically every rom listed on this site. No matter what I do, the hardware keyboard lags 2-3 words behind what i actually type. Sometimes it will even skip words. I have tried the reg edits, and the cabs. I have disabled tX9 or whatever that software keyboard is, but nothing helps. Is this just a windows issue? I am so frustrated that i ordered a Palm treo to replace this touch pro. At least i can text with that. I guess this is farewell to the forum, because this phone STINKS!

I think you answered your own question....

Slider phones with Keyboard by HTC running Windows mobile have terrible keyboard lag. Period. Thats all there is to say....

Some custom ROM's claim to improve it but I have not seen that yet. Even my own kitchen does.....

Thats why I have a Diamond now. A keyboard on a WinMo slider will surely lead to this fustration.

If you need a keyboard the Diamond is not for you. Look at the Treo Pro. Wife just got it a few weeks ago. No issues with KB lag because screen does not rotate.

Its not actually the KB lagging. Its the display I beleive.

BTW: the phone is simply amazing. It doesnt stink. Windows Mobile Stinks... Badly. Thats why there are custom ROM's.


Either way.... Good luck!

[iconeo]

Originally Posted by scrosler

Its not actually the KB lagging. Its the display I beleive.

I'm running a custom 6.5 rom on the 21501 build and I used to have lag. I found a solution while trying to troubleshoot my GBA emulator.

I too, at first, believed that is was the display that was lagging the input of text. However, delving further into it I have found that it is how winmo interprets key codes coming from hardware keyboard.

Winmo hardware keyboards typically come with a modified msim*.dll which tends to be labeled something like msim*.dll where * is some identifier with digits. The reg code that points to the file is:

[HKLM\System\CurrentControlSet\Control\Layouts\(the default value)]

Changing this to point to msim*.dll without any digits in it (which should still be on your phone even though it isn't being used) will change the hardware key codes back to normal.

!!! THIS WILL BREAK T9 or any advanced correction features !!!
This is most likely why turning off t9 lends to faster text input, but not as fast as this fix.

Props to dilta over at xda for the utility!

note: this hasn't been tested on foreign roms, use with caution.

[piranah]

i send 3-400 texts a day, and yea, disabling t9 and all the extras (auto correct, word suggestion) helps speed up the keyboard. Im using a custom rom from Calkus 21232 kitchen...and i dont have much of a keyboard lag..im really fast at texting so a .5 second delay is expected...especially when you dont know exactly what to say to the little woman...

[1999TL]

Originally Posted by iconeo

I'm running a custom 6.5 rom on the 21501 build and I used to have lag. I found a solution while trying to troubleshoot my GBA emulator.

I too, at first, believed that is was the display that was lagging the input of text. However, delving further into it I have found that it is how winmo interprets key codes coming from hardware keyboard.

Winmo hardware keyboards typically come with a modified msim*.dll which tends to be labeled something like msim*.dll where * is some identifier with digits. The reg code that points to the file is:

[HKLM\System\CurrentControlSet\Control\Layouts\(the default value)]

Changing this to point to msim*.dll without any digits in it (which should still be on your phone even though it isn't being used) will change the hardware key codes back to normal.

!!! THIS WILL BREAK T9 or any advanced correction features !!!
This is most likely why turning off t9 lends to faster text input, but not as fast as this fix.

Props to dilta over at xda for the utility!

note: this hasn't been tested on foreign roms, use with caution.

Finally, I found a way to disable text suggestion since i can't find it in the Calkulin rom I'm using. I posted in the upgrades section but noboyd could help. This cab got rid of it after i soft reset. Wow, lag IS IS IS IMPROVED! Just did some texting. Nuts. This is huge. Don't know why ppl haven't made a big deal out of this before.

[iconeo]

Originally Posted by 1999TL

Finally, I found a way to disable text suggestion since i can't find it in the Calkulin rom I'm using. I posted in the upgrades section but noboyd could help. This cab got rid of it after i soft reset. Wow, lag IS IS IS IMPROVED! Just did some texting. Nuts. This is huge. Don't know why ppl haven't made a big deal out of this before.

Probably because in adding functionality it also break functionality which is never a popular thing. Plus, I got lucky discovering this while looking into something else. We were only trying to fix key mapping for games not speed up the keyboard...

[nswenson]

Originally Posted by iconeo

I'm running a custom 6.5 rom on the 21501 build and I used to have lag. I found a solution while trying to troubleshoot my GBA emulator.

I too, at first, believed that is was the display that was lagging the input of text. However, delving further into it I have found that it is how winmo interprets key codes coming from hardware keyboard.

Winmo hardware keyboards typically come with a modified msim*.dll which tends to be labeled something like msim*.dll where * is some identifier with digits. The reg code that points to the file is:

[HKLM\System\CurrentControlSet\Control\Layouts\(the default value)]

Changing this to point to msim*.dll without any digits in it (which should still be on your phone even though it isn't being used) will change the hardware key codes back to normal.

!!! THIS WILL BREAK T9 or any advanced correction features !!!
This is most likely why turning off t9 lends to faster text input, but not as fast as this fix.

Props to dilta over at xda for the utility!

note: this hasn't been tested on foreign roms, use with caution.

Do not install this KforTouchPro.cab file unless you like doing hard resets frequently. The tool allows you to switch T9 on and off, but unfortunately causes the phone to hang at boot screen after the next soft reset when you forget to toggle T9 back on. There's no work-around other than to hard reset, or always remember to re-enable T9.

A better solution is to use the disablet9.zip patch to disable T9. This will not cause the boot issue. The only side affect is the SYM key does not work, which most people never use. You can alway uninstall the cab to get the default keyboard functionality back.

Nathan

[nswenson]

Originally Posted by iconeo

I'm running a custom 6.5 rom on the 21501 build and I used to have lag. I found a solution while trying to troubleshoot my GBA emulator.

I too, at first, believed that is was the display that was lagging the input of text. However, delving further into it I have found that it is how winmo interprets key codes coming from hardware keyboard.

Winmo hardware keyboards typically come with a modified msim*.dll which tends to be labeled something like msim*.dll where * is some identifier with digits. The reg code that points to the file is:

[HKLM\System\CurrentControlSet\Control\Layouts\(the default value)]

Changing this to point to msim*.dll without any digits in it (which should still be on your phone even though it isn't being used) will change the hardware key codes back to normal.

!!! THIS WILL BREAK T9 or any advanced correction features !!!
This is most likely why turning off t9 lends to faster text input, but not as fast as this fix.

Props to dilta over at xda for the utility!

note: this hasn't been tested on foreign roms, use with caution.

Do not install this KforTouchPro.cab file unless you like doing hard resets frequently. The tool allows you to switch T9 on and off, but unfortunately causes the phone to hang at boot screen after the next soft reset when you forget to toggle T9 back on. There's no work-around other than to hard reset, or always remember to re-enable T9.

A better solution is to use the disablet9.zip patch to disable T9. This will not cause the boot issue. The only side affect is the SYM key does not work, which most people never use. You can alway uninstall the cab to get the default keyboard functionality back.

http://forum.ppcgeeks.com/showthread...disable&page=5

Nathan

[Cobaltikus]

There is a beta rom from DCD which does not have any keyboard lag. It is Windows Mobile 6.1

It is bare bones and no kitchen but does have SDAutoRun

http://dcd1182.n715dp.com/index.php?dir=hermann/

[d94]

Originally Posted by nswenson

Do not install this KforTouchPro.cab file unless you like doing hard resets frequently. The tool allows you to switch T9 on and off, but unfortunately causes the phone to hang at boot screen after the next soft reset when you forget to toggle T9 back on. There's no work-around other than to hard reset, or always remember to re-enable T9.

A better solution is to use the disablet9.zip patch to disable T9. This will not cause the boot issue. The only side affect is the SYM key does not work, which most people never use. You can alway uninstall the cab to get the default keyboard functionality back.

http://forum.ppcgeeks.com/showthread...disable&page=5

Nathan

didnt work

[Darkjedi]

Originally Posted by nswenson

Do not install this KforTouchPro.cab file unless you like doing hard resets frequently. The tool allows you to switch T9 on and off, but unfortunately causes the phone to hang at boot screen after the next soft reset when you forget to toggle T9 back on. There's no work-around other than to hard reset, or always remember to re-enable T9.

A better solution is to use the disablet9.zip patch to disable T9. This will not cause the boot issue. The only side affect is the SYM key does not work, which most people never use. You can alway uninstall the cab to get the default keyboard functionality back.

http://forum.ppcgeeks.com/showthread...disable&page=5

Nathan

omg that's totally what happened to me. Thankfully it gave me an excuse to update to the new MR5 ROM when it came out a couple weeks ago. Now I need a new excuse to reupgrade to the most recent MR5, ahah.