yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] asak0:
INTRO

I've started this thread to port the EzInput Keyboard to QVGA resolution. The keyboard is now fully functional yet still has a couple of small glitches to be fixed in portrait mode.

I am doing all the testing on my elfin, so I cannot assure that it will work on other devices so you'll have to test it yourselves!

You can download it here:

http://www.sendspace.com/file/uxi3be

THANKS

I must thank

DupinBJK:

http://xdaforums.com/showthread.php?t=486227

nikoan89:

http://xdaforums.com/showthread.php?t=489032

and

Conflipper

for their hard work on the VGA port, since I have mixed parts of their ports to get this QVGA version working.

KNOWN BUGS

XT9 is not currently working: the keyboard seems to get the coordinates (size and position) of the VGA keys. E.g.: if you press "q", "a" or "w" the keyboard will write "q" on the screen, since the three letters are in the area of the "q" key in a VGA screen (double size).

Any help on this matter would be really appreciated!!!

XT9 UPDATE 05/01/2009:

I´ve managed to get XT9 working by replacing the xT9ime.dll of the EzInput 2 with the EzInput 1.5 dll supplied with the ROM I am using. The problem now is that I cannot change XT9 mode back to normal mode :(.

Anyway I encourage you to test this and see if we can get a solution to the XT9 issues.

To test it, just go to the windows directory, rename eT9ime.dll to something else (e.g. eT9ime.dll.OLD) and reset your device (this should restore the dll supplied with your ROM).

I´m waiting for your comments!!!!

VIBRATION/XT9 UPDATE 05/13/2009:

I managed to get vibration to work a couple of weeks ago, but I wanted to fix the T9 mode before releasing a new version.

I´ve been working on T9 and have not been able to find where the code responsible for calculating the key pressed (based on the coordinates) is.

OPTION A: If anyone is able to find such place in the code or just point me in the right direction, I´ll find the time to patch et9Ime.dll so that QVGA users can enjoy T9 in this keyboard.

OPTION B: Another possible option would be to patch the et9Ime.dll from ezinput 1.5, but the mappings of some important keys seem to be different (XT9/ABC switch for example), and also different registry keys need to be updated so that everything works as it should.

Sorry for the lack of feedback, but I need more time for fixing these issues since this is the first time I am dealing with SIP/IME/IMM and stuff and I´ve found it a little bit more complex than I thought it would be.

HOWTO

Additionally, I'm planning on writing a very simple "howto" to explain people what they can do to adjust/fix/change the layout of the keyboard.

PS: I cannot post any screenshot now, so if anyone of you can upload one I'd be grateful.
[Windows Mobile Software Development] chriscsh:
problem on XT9 mode, maybe is the key mapping, i dunno that :p

for example type q,w,a,s the result is --> qqqq

type e,r,d ---> www

thanks for your hard working :D
[Windows Mobile Software Development] asak0:
T9 issue

You're right (i did not test the XT9 :()

I'll have a look at it.

Thanks :)
[Windows Mobile Software Development] thorfr:
Nice :)

Just 2 questions :

- vibrate when keys are pressed : Don t work normal maybe ...

- Is there a way to change language to french? i see 40C file ...

ty
[Windows Mobile Software Development] chrisrc1985:
looks great, good to finally have EZInput for QVGA.

major bug I noticed it messes up the keyboard mapping..for example Caps does not function, nor does the light, just flickers on then off when caps is hit, I believe to turn caps on and off (at least for me) I would have to use function, which also works for function (if that makes sense) lol

also the function keys got incorrectly mapped, I will try the tilt keyboard fix, hopefully that will work, and you can post that Cab.

Minor Issue: no SIP image to open the keyboard on the phone. its a black square, hit the square to active SIP. Would be nice to get a cool new icon though ;P

other then that, I will continue to test this, because the spacing between the keys and the skin is very nice :)

Thanks for your hard work and the post
[Windows Mobile Software Development] ems275:
I installed this new version and the only major thing I see compared to all the rest of the one you have posted is that the SIP Icon for the Keyboard that shows between the softkeys is missing, if you press the empty space the Keyboard still pops up and is functional but the icon is gone.
[Windows Mobile Software Development] varanusvincent:
thanks man. Work great
[Windows Mobile Software Development] eoche007:
So I don't have the phone keypad...is this just a problem with me or does anyone else have this problem?
[Windows Mobile Software Development] mssmison:
XT9 is off, but that's fine cause I don't find a need for xt9 on a full keyboard anyways. Though like I said in the other thread I wish there was compact qwerty, or at least I could have the compact qwerty from my other keyboard as well.
[Windows Mobile Software Development] yandi3401:
Thanks a lot! Im at school now, but as soon as I get home, I'll install this on my phone.

- Thanks, your job is really appreciated.
[Windows Mobile Software Development] MarcoPolo78:
Great !!!

I've been waiting for this for sometime now and just say thanks for the Qvga version :D Just wondering if anyone is working on the xt9 bug, i have gotten accustom to using that but if not no worries still a great keyboard !!!
[Windows Mobile Software Development] natefish:
Well, this full qwerty is a huge improvement over the EZ-Input one. I installed the keyboard and used the full qwerty without any problems. HOWEVER, does the Compact QWERTY mode not work with this? Thanks.
[Windows Mobile Software Development] JoOoSs:
Thank you man, you are awesome !

I don't have any problems with it, except the reported bug of the SIP Icon.

But the keyboard on my Elf is a bit slow without O/C. (WM 6.5)

I love this keyboard !
[Windows Mobile Software Development] asak0:
XT9 bug

I've been looking at the XML files, the kdb files and the ldb files and I still cannot figure out the place where the XT9 keys size/position (x,y,h,w) is defined.

Does anyone know whether it's hardcoded in a PE module or it can be configured anywhere?

BTW, I'm afraid Compact QWERTY is not possible for the time being...
[Windows Mobile Software Development] littld:
Sorry if I'm repeating. If I switch to numeric and press a key and then go back to ABC then all the keys are screwed up and when I press them I get the wrong keys. Do others have the same problem?
[Windows Mobile Software Development] asak0:
littld, i'm not experiencing that behaviour, sorry :(
[Windows Mobile Software Development] ems275:
I have been trying to find this out too, I have looked everywhere and can't find the positions for XT9.

Side note, on all 3 previous versions you could use XT9 in ABC and it worked perfectly, but in the new version it just types normally in ABC and XT9 is still broke.
[Windows Mobile Software Development] asak0:
You mean in the previous versions I posted in the QVGA Rhodium Development thread?
[Windows Mobile Software Development] ems275:
Yes, all 3 you posted in that thread. If set to XT9 all key mapping was off as I had posted in that thread and others. But ABC worked as XT9 without a problem. It was weird. But I am running the last posted version which I downloaded from sendspace and it works as described above. When I installed the one when you opened this thread also from sendspace XT9 key mapping is still the same, totally off and ABC just functions as it should, regular typing with no text prediction.

Hope that makes sense? :)
[Windows Mobile Software Development] asak0:
Not really... :(

Anyway I'll play around a bit with the different modules to see what I can get.
[Windows Mobile Software Development] r1aven:
Changes Hardware Keyboard Mapping

I have installed and tried this and it seems to work well. I have a XV6800 with a hardware keyboard, but on occasion do use the on screen keyboard in portrait mode. I have found that the EzInput keyboard changes the mapping for hardware keyboard when trying to enter special characters.

For instance, the exclamation point is normally the "blue dot" + "w". However, with the EzInput keyboard installed, that combination gives a "1" instead of the "!". There are other combinations that no longer work properly too, the exclamation point was just one example. Uninstalling EzInput does restore the hardware keyboard to normal operation.

Cheers
[Windows Mobile Software Development] yandi3401:
I just installed it on my HTC Touch. It works fine.

- The only problem I found (and that has been mentioned before), is the keyboard icon on the bottom, and that is a little bit slow.

Besides that, the keyboard is great!

Thanks for the hard work.
[Windows Mobile Software Development] magicalan:
love it :D

fix the XT9 pleaseee :D

the rest is working :)
[Windows Mobile Software Development] sergiorus:
Found bug

When i use Caps Lock letters are still small

And have a suggestion. Can you make a basic version with only english language and other languages separately like in DupinBJK thread. It seems to be 20 languages in cab, i dont think people need it all.
[Windows Mobile Software Development] yandi3401:
I found out that if you select other keyboard, and then you go back to this keyboard (Ezinput), you'll get the icon of the previous keyboard you used.

- Is not the right icon, but it looks better than nothing... :D
[Windows Mobile Software Development] dsymbol:
Hi all,

I'm sorry that I dont understand all the technical terms here.

Will this program give me the COMPACT QWERTY on the Touch Diamond 2, & it works properly?

Thanks a bunch.

D
[Windows Mobile Software Development] ashmont:
An idle question for you. As a Touch Diamond 2 owner, can you tell me if they have fixed the bug with error correction on the full qwerty keyboard? On Ezinput 1.5 with XT9 enabled you don't get the same behaviour on Full Qwerty as with the other keyboards (eg the standard in built Microsoft one). With every keyboard except Full Qwerty, XT9 is really good and corrects for missed keys or keys in the wrong order. Annoyingly on Full Qwerty it works in a substandard mode and only corrects some errors like dropped vowels meaning that I have to press backspace for most mistakes. With the smaller keys you really need decent error correction.

Just idly wondering.

Cheers,

Ashley
[Windows Mobile Software Development] ruizit0:
hum installed on my kaiser... i have some bugs ..

1. the hardware keyboard special chars doesnt match with FN (ex. ! , ? , or the numbers)

2. the sip icon in bottom bar

3. the SHIFT and FN sometimes doesnt work properly

and where i can get that "20 langs cab" with portuguese ? i only see the english..

thanks good work
[Windows Mobile Software Development] sergiorus:
Any updates?
[Windows Mobile Software Development] havocnl:
I tried the version posted some time ago in this topic op my elfin and i didn't like the keyboard. It was just too slow for me.

I am a very fast typer (with the stylus) and the keyboard didn't record al my entries. Never had this problem with windows default or with EzInput 1.5....

So unless the speed of the keyboard can be improved i'm sticking with the old EzInput so i can type al my message a decent speed ;)
[Windows Mobile Software Development] ruizit0:
hum ... yes .. i think this needs some more work to make it work like 1.5
[Windows Mobile Software Development] asak0:
Some comments

For those of you having a hardware keyboard:

Sorry but I cannot help. I only have an elfin and I am not able to debug the hardware keyboard issues.

The SIP icon:

This issue is easy to solve, but I´m still more worried about T9. You can get the icon you want updating the registry:

[HKEY_CLASSES_ROOT\CLSID\{36BC8FF6-8241-4C36-ABDE-204885471FEE}\DefaultIcon]

"" = "\Windows\ezinput.dll,0"

This is suppossed to get the first icon from the ezinput.dll module, but the ezinput.dll supplied has no icon inside. You can either add an icon manually (with reshacker for example) to ezinput.dll or use an icon from another module (use whichever module you want).

For example, to get the first icon from shell32.dll:

[HKEY_CLASSES_ROOT\CLSID\{36BC8FF6-8241-4C36-ABDE-204885471FEE}\DefaultIcon]

"" = "\Windows\shell32.dll,0"

I will fix the icon issue myself when I manage to get T9 to work. Have a nice day!
[Windows Mobile Software Development] jeremy89632:
If we were to go with option B, like you mentioned, how is it gonna be done?

The possibility of Option A is low, right?

And, im using an elfin too!
[Windows Mobile Software Development] asak0:
Both options would include patching the et9ime.dll module where needed (injecting code in the PE module).

In option B we need to know (at least) when the "et9/ABC" switch key is pressed and change two values in the registry so that the mode change takes effect. The main problem here is that the "et9/ABC" switch key seems to be different than the one used in ezinput 2.

In option A we need to know where the XT9 key identification (based on the coordinates) takes place and fix such method so that keys are identified correctly.

OPTION C: use compime.dll instead of et9ime.dll and problem is gone! (is uglier though!).
[Windows Mobile Software Development] jeremy89632:
I dont think people will support option C.

mmm...

Option A is still the best, can we try to open every single file that this keyboard used to look for it?
[Windows Mobile Software Development] sgmbox:
thks for the update in progress
[Windows Mobile Software Development] yandi3401:
Thanks for the Updates! Is there any improvement in speed in this last update?

Here is a screenshot of the keyboard:

​
[Windows Mobile Software Development] jeremy89632:
How is the T9 going?

Is there anyway I can lend an helping hand (:
[Windows Mobile Software Development] jeremy89632:
Can you extract the t9 file from the vga thread?

http://xdaforums.com/showthread.php?t=506846

Thanks.
[Windows Mobile Software Development] yandi3401:
Is it possible to get the speed from the first release back (the one that only worked in XT9 mode?

I really love your work, but it would be nice not to have the speed problem.

Thanks for all the hard work!
[Windows Mobile Software Development] jeremy89632:
TS, Please keep me updated of the outcomes.

Thanks.
[Windows Mobile Software Development] lotherius:
Thanks

Thanks for the QVGA version of this - QVGA Still Lives!

Question: Can this co-exist on the same device with the 1.5 version? Thanks!
[Windows Mobile Software Development] jeremy89632:
no, it will over-write it.
[Windows Mobile Software Development] rukako:
There is any way to change the language and the type o f keyborad from qwerty to AZERTY or others???
[Windows Mobile Software Development] ryomahino:
I have a question? how I disable the predictive text because after install this version dont appear in start menu/settings/input the tap for word completion?

Thanks
[Windows Mobile Software Development] lboonchye:
Does it work on Touch 3G?

I try installing it to touch 3G but it tells me installation unsuccessful.

Has anyone got it to work on Touch 3G?
[Windows Mobile Software Development] nhatminh87:
anyone can make compact qwerty for QVGA:rolleyes:
[Windows Mobile Software Development] littld:
I am using PDAVIET rom on Elfin which has this input built in and seems (to me) to be working perfectly. Is there a way to extract files from my device to make a working cab so it can be shared?
[Windows Mobile Software Development] yandi3401:
Can anyone post the download link for the previous release (the one before 5/13/09), because I just installed the lastes release and the typing speed is unaceptable!

Does anyone have the same problem, or is just me?
[Windows Mobile Software Development] megapinky:
Hi Asak0

can you make a Wqvga version withs this image? i try to mod you cab but not successful :(

I try whit 0C09.xml

thanks
[Windows Mobile Software Development] asak0:
Hi littld!

Please check that T9 (predictive) is working and if so, send me the download link and I'll do the rest.

If T9 is working I'll pack everything up and release a new version with QVGA compact qwerty included.
[Windows Mobile Software Development] jeremy89632:
(erase this, accident)
[Windows Mobile Software Development] littld:
Do you mean the problem where you type q, a, w or something and always get "q"? If so then that's fixed, also compact version seems to me to work. I do know that the EZINPUT.DLL is a later version.

Link: http://pdaviet.net/showthread.php?p=734033#post734033
[Windows Mobile Software Development] xda2_haseeb:
its slow on WIzard and has no SIP icon of its own :( is there really such issue or i got the wrong CAB :o
[Windows Mobile Software Development] jonathan.handoyo:
on the contrary to some post before that says that the keyboard is not fast enough...

i think it's already fast... at lease fast for me...

but the fade away effect after you type a letter, is making the sense that the keyboard needs time to "restore" from the previous type...

but i think this is great...

found a bug though, i installed it on my kaiser... but it kinda screws up my hardware keyboard... i dunno if that has been posted here or not...

it kinda mix up my FN key...

i don't really use my hardware keyboard that much anymore, but it would've been great to still have the option to use my hardware keyboard.

but nevertheless, this bug didn't stop me from using your awesome keyboard...
[Windows Mobile Software Development] jonathan.handoyo:
i just realized another bug... sorry for double posting...

although i checked the option to vibrate, it didn't vibrate...

and on another note...

it would be great to come up with the other keyboard...

as in, compact qwerty and phone keypad...
[Windows Mobile Software Development] xda2_haseeb:
yes it screws my hardware keyboard too, sorry forgot to mention :o
[Windows Mobile Software Development] Tplpeters:
works fine

work like a charm on my old kaiser need som more lang to the x9
[Windows Mobile Software Development] chavonbravo:
Though it's a newer ezinput version in pdaviet rom, he doesn't include xt9 in it. So no difference really. I as well am going through the code to see where the mapping could be. Keep an eye out for subroutines with setrect, inflaterect, etc. anything to do with rect.

I am trying to see how I can debug through IDA the et9ime file, but don't know what .exe to strap on to. This would help as I could actually see the values passed to most set rect, then figure out which ones need to be traced back and see where the original values are set.

p.s. To get vibration working for you others:

[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\KeyState]

"UseService"=dword:00000001
[Windows Mobile Software Development] sinoo:
Will give it a try... Thanks for your work...

---------------------

QWERTY is working perfect... It looks really nice...

But this is the only input method that works. The other two are not working.

For XT9: don't we need a language pack like we did in v1.5?
[Windows Mobile Software Development] yandi3401:
Never mind! :D

The problem was caused because of the ROM I was using...

- Now it works good.

Sorry! :o
[Windows Mobile Software Development] vultron:
XT9 does not work for vogue

shame since this looks like a kick ass keyboard!
[Windows Mobile Software Development] sambalbij:
small cab

Doesn't work either with my herald. Also not after replacing the et9ime from ezinput 1.5. Here a cab without t9 (saves space).
[Windows Mobile Software Development] yandi3401:
Is it any faster?

Thanks! :)
[Windows Mobile Software Development] jeremy89632:
6.5 working?
[Windows Mobile Software Development] Snakehn:
anybody knows if the bug of mixed keys as a result of switching to numeric and back is fixed now?
[Windows Mobile Software Development] sambalbij:
I don't think so, i removed 4 mb of t9 languages but in original file they weren't loades so it isn't faster. Removing other t9 files could make it faster, but i don't think so.
[Windows Mobile Software Development] grega_slo:
I noticed that it is a little faster when u type...
[Windows Mobile Software Development] kdu:
Hello, can we set delay time when pressing a key, like in fingerkey?
[Windows Mobile Software Development] jeremy89632:
I think you have to play with the registry for that.
[Windows Mobile Software Development] kdu:
I thought of that too. But how?

I installed EZinput 2.33859 NoArrows.cab in my Touch HD, but it appeared only a small keyboard which is unusable. I had to reinstalled my previous one.
[Windows Mobile Software Development] sambalbij:
Because this program is qvga, your touch hd has got a bigger screen (wvga) so you have to use another version of ezinput.

This or this.
[Windows Mobile Software Development] yandi3401:
Ok! Thanks! :D
[Windows Mobile Software Development] adderz91:
Hows the progress going on this keyboard?

I would love this updated, the layout is much improved on the keypad compared to the 1.5 keypad.

*crosses fingers*
[Windows Mobile Software Development] thangkls:
I don't use T9 so I installed "disable xt9.cab" from XDA but every time I chose this keyboard - it also ticks in xt9 already - it's very annoyed with me.

Is there anyway to remove T9 permanently ?
[Windows Mobile Software Development] sambalbij:
You tried my cab from post 63?
[Windows Mobile Software Development] JoOoSs:
I have the same issue, you said you erased the T9 on this cab, but it's enable anyway :confused:
[Windows Mobile Software Development] sambalbij:
Under the settings menu in wm, you can change xt9 settings under the input-->touch input. Uncheck all boxes and look what happens. If nothing happens, i don't know (sorry, i'm not a programmer or so)
[Windows Mobile Software Development] alexinc:
with advanced config you can set word suggestion to 0 and the popups are gone...
[Windows Mobile Software Development] kdu:
Thanks so much. Can any one tell me how to increase delay time when pushing a key?
[Windows Mobile Software Development] chriscsh:
EZinput 2.0 Compact QWERTY mode

i working on it

(thanks all developer's for working the EZinput2, i just combine all of you creation :p)

english only

i post the cab for your test

but careful, try it at your own risk :p

and 1 question, anybody know how to edit the text size on the visual feedback (see the pict) :confused:
[Windows Mobile Software Development] atzaus:
anyone know how to get normal windows spell correction working with this?
[Windows Mobile Software Development] JoOoSs:
It's include the compact & full QWERTY, or not ?
[Windows Mobile Software Development] MarcoPolo78:
Works Great ... But

The only thing that needs work on it is the Font in the pop up is to big needs down sized and also would be nice to implement the Full qwerty with this so you have an option of the 2. Other than that works fine on my HTC Touch p3450 even the Xt9 works ! :D
[Windows Mobile Software Development] chriscsh:
this only Compact qwerty mode
[Windows Mobile Software Development] briggs81:
So far so good!
[Windows Mobile Software Development] philmayhem:
Is there a working keypad layout for this version yet?
[Windows Mobile Software Development] muhrizky:
Can i install this app into storage card?

Thanks.
[Windows Mobile Software Development] kane159:
hey my friend !!

I think you do grate job :)

can I ask you just a little question...

how to make this smallier??

It's too big :(

I'm just start working on it. it's for chinese

help me please :)
[Windows Mobile Software Development] roniez:
Is there any updates on this work?

Also is there anyway i can get a swedish layout of the keyboard?
[Windows Mobile Software Development] Biglia05:
Actually there's 2 versions of 2.1

http://xdaforums.com/showthread.php?t=542117

http://xdaforums.com/showthread.php?t=535326
[P3400 General] ankit360:
which phone you buy after using gene ?

did you happy with WM OS phone or switch to other OS or brand ?

which is feature you don't like of Your gene

I don't like to extusb port I cant use my own headphones even I can't find HTC acessories