[30-Nov-08] HTC EzInput Keyboard Suites - QVGA and VGA RC2 and Language Packs [Archive]

DupinBJK

14th September 2008, 09:02 PM

Welcome to the EzInput 1.5 Keyboard Suite project.

This app, as many of you already know, is the well known 'Diamond' keyboards suite shipped with the HTC devices since the Diamond release. HTC officially ships it with the Quartz and Touch HD (in WVGA), Diamond and Touch Pro (in VGA) and with the Touch Viva and Touch 3G (in QVGA).
The suite gives users the choice of a Keypad, a Compact Keyboard and a Full Keyboard:

http://i384.photobucket.com/albums/oo284/DupinBJK/keyboards.png

Thanks to Laurentius26, Noonski, Tupisdin, Alexx~ and - not least - the HTC programmers who have built this technology and are constantly improving it even by monitoring this thread, a project to patch, reconfigure, fix and repackage this keyboard suite for other HTC devices has born.

These are the main differences between the officially released version, made for phones without an Hardware keyboard, and the one you'll find here:

Added compatibility with 16keys Hardware keyboards.
Added compatibility with 20keys Hardware keyboards.
Added compatibility with Full Hardware keyboards.
Added full key remapping capabilities to Full Hardware keyboards.
Added T9/ABC functionality to Full Hardware keyboards.
Restored DeadKeys functionality to Full Hardware keyboards.

Added compatibility between 16keys Hardware keyboards and some apps extracted from the new Manila2D roms.
Improved compatibility with third-party browsers.
Fixed the "white items" issue in the list of available languages.
Added compatibility with French Qwerty, Hungarian, Romanian, Slovak and Turkish Language Packs.

Even phones with the official release will benefit from the added features found in these cabs.

In the following posts you'll find:

A Customizations section, with cabs to change the default settings of the Suite - Post #2.
All the QVGA Main cabs - Post #3.
All the QVGA Language Packs - Post #4.
All the VGA Main cabs - Post #5.
All the VGA Language Packs - Post #6.
A Special Requests section, for communications related to beta testing - Post #9.

A Very Special Thanks
goes to the members of this forum who have contributed with their donations to the research and development for this project:Users: Venelar, conflipper, maddoxik
Chefs: Laurentius26, dsixda
And to the members who have contributed to the beta testing for the Nike phones:
Users: mignonette, randomelements, wmn79

Donations

If you appreciate all the work and efforts made so far and would like to contribute, please consider a Donation.
Every amount will be deeply appreciated, thanks !

BJK

DupinBJK

14th September 2008, 09:02 PM

Customizations

ABC / T9 as default input methods

The EzInput main cabs enable T9 as default input method.
If you need to change this behaviour, you can install one of the cabs below:

[ABC as Default (http://www.4shared.com/file/68068288/2b08ce8e/BJK_HTC_EzInput_ABC_Default.html)] - Set ABC as default IME for hardware and software keyboards.

[T9 as Default (http://www.4shared.com/file/68068321/a9f9f497/BJK_HTC_EzInput_T9_Default.html)] - Set T9 as default IME for hardware and software keyboards.

A soft reset is recommended, even if not always necessary.

Both cabs are provided in case T9 will need to be set once again as default or vice versa.
Uninstall of the previous ABC/T9 cab is recommended to reduce clutter in the "Remove Programs" applet.

DeadKeys / T9 as default behaviour for the Fn+Space combo - Full HW Keyboard phones

The EzInput main cabs enable T9 as default behaviour for the Fn+Space combo on Full Hardware Keyboard phones.
If you need to change this behaviour, you can install one of the cabs below:

[DeadKeys as Default (http://www.4shared.com/file/72655566/5c35c642/BJK_HTC_EzInput_FnSpace_DKeys.html)] - Set DeadKeys as default Fn+Space behaviour for Full Hardware Keyboard phones.

[T9 / ABC as Default (http://www.4shared.com/file/72655564/b23ba76e/BJK_HTC_EzInput_FnSpace_T9.html)] - Set T9 / ABC as default Fn+Space behaviour for Full Hardware Keyboard phones.

Make a soft reset after that.

For those who choose the DeadKeys behaviour, the above ABC as Default Input Method is recommended.

Both cabs are provided in case T9 will need to be set once again as default behaviour or vice versa.
The previous DeadKeys/T9 cab will be uninstalled automatically.

DupinBJK

14th September 2008, 09:02 PM

Downloads - QVGA

Instructions:

Uninstall of all the previously installed third party keyboards and SIP changers is recommended.

Choose your hardware configuration and download the main application (the blue hyperlinks).
Choose the Language Packs from post #3.
Uninstall any previous beta, if installed.
Make a soft reset.
If you are using a Rom with EzInput 1.5 already included, you must terminate the "SipGT_app" process first, or you won't be able to install.
Install the Main cab you've chosen. After the install it won't be necessary to reset your phone.
Install all the Language Packs you've chosen.
Make a soft reset.
Go to Settings -> Input -> Options and choose your Language from the list. Only the languages for which you have installed a Language Pack will give you a working keyboard.
NOTE: The main cabs don't include any language. Even if they will let the full list appear in the settings listbox, you'll have to manually add the languages you need to use.

Due to the peculiarity of the CAB install technology and the way with which HTC has conceived the Language List configuration in the Registry (a single string for all available languages, which can't be parsed by the WM CAB engine), the full list needs to be created before you'll install even a single Language Pack.
After that, to remove all unneeded languages from the list, a simple edit of the registry will suffice.

The first post for RC2 is here (http://forum.xda-developers.com/showpost.php?p=2944558&postcount=593).

QVGA Main cabs - 0409
Note: These cabs are only meant for WWE 0409 roms.

[No Keyboard] - phones without HW keyboard (http://www.4shared.com/file/112390528/29099d60/BJK_HTC_EzInput_QVGA_NoKbd_0409-RC2.html)

[Keypad] - phones with 16keys HW keyboards (http://www.4shared.com/file/72571487/c74507f4/BJK_HTC_EzInput_QVGA_KPad_0409-RC2.html)

[Compact Keyboard] - phones with 20keys HW keyboards (http://www.4shared.com/file/72571409/e824a0fb/BJK_HTC_EzInput_QVGA_CpKbd_0409_RC2.html)

[Full Keyboard] - phones with full HW keyboard (http://www.4shared.com/file/72571446/1cf7786e/BJK_HTC_EzInput_QVGA_FullKbd_0409-RC2.html)

DupinBJK

14th September 2008, 09:02 PM

Language Packs - QVGA

These are the Language Packs add-ons specifically made for the 0409 - WWE main packages available in post #3. Not all languages are immediately available, but they will be added to the list as soon as they will be ready.
Please note that some Language Packs are not available for all devices, due to missing support files. You'll find detailed info for each language, below.

PLEASE NOTE:
RC1 Language Packs are 100% compatible with the RC2 Main cabs.
Language Packs from other packagers won't be compatible with the main cabs found in post #3, nor these ones will be compatible with Keyboard cabs made by other packagers.

[0#01 Arabic]
Some files are still missing and others need to be patched. Waiting for an Opal Arabic ROM.

No Keyboard: Not available
Keypad: Not available
Compact Keyboard: Not available
Full Keyboard: Not Available

[0#05 Czech (http://www.4shared.com/file/65653747/36e621f4/BJK_HTC_EzInput_QVGA_LPack_CS-RC1.html)]
Files from the VGA version, patched for QVGA release. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#06 Danish (http://www.4shared.com/file/66384048/a7745dc6/BJK_HTC_EzInput_QVGA_LPack_DA-RC1.html)]
Files from the VGA version, patched for QVGA release. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#07 German (http://www.4shared.com/file/65653752/5f97e43a/BJK_HTC_EzInput_QVGA_LPack_DE-RC1.html)]
As extracted from the Official Rom. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#08 Greek (http://www.4shared.com/file/71889498/84739d59/BJK_HTC_EzInput_QVGA_LPack_EL-RC1.html)]
Files from the VGA version, patched for QVGA release. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#09 English (http://www.4shared.com/file/65653754/b6f4410f/BJK_HTC_EzInput_QVGA_LPack_EN-RC1.html)]
As extracted from the Official Rom. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#0A Spanish (http://www.4shared.com/file/65653763/3bd876f/BJK_HTC_EzInput_QVGA_LPack_ES-RC1.html)]
As extracted from the Official Rom. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#0B Finnish (http://www.4shared.com/file/67304500/5d0f926e/BJK_HTC_EzInput_QVGA_LPack_FI-RC1.html)]
Graphics built from scratch. Layout files from the VGA version, patched for QVGA release. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#0C French (http://www.4shared.com/file/65653767/4d04376/BJK_HTC_EzInput_QVGA_LPack_FR-RC1.html)]
As extracted from the Official Rom. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#0E Hungarian (http://www.4shared.com/file/65653773/1aa6b62e/BJK_HTC_EzInput_QVGA_LPack_HU-RC1.html)]
Built from scratch and especially made and enabled for this release.

No Keyboard: Available
Keypad: Not available
Compact Keyboard: Available
Full Keyboard: Available

[0#10 Italian (http://www.4shared.com/file/65653778/8d746fa6/BJK_HTC_EzInput_QVGA_LPack_IT-RC1.html)]
As extracted from the Official Rom. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#13 Dutch (http://www.4shared.com/file/66383298/8c89cf5c/BJK_HTC_EzInput_QVGA_LPack_NL-RC1.html)]
Files from the VGA version, patched for QVGA release. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#14 Norwegian (http://www.4shared.com/file/67304537/e846540e/BJK_HTC_EzInput_QVGA_LPack_NO-RC1.html)]
Graphics built from scratch. Layout files from the VGA version, patched for QVGA release. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#15 Polish (http://www.4shared.com/file/65653784/35a3f42/BJK_HTC_EzInput_QVGA_LPack_PL-RC1.html)]
Files from the VGA version, patched for QVGA release. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#16 Portuguese (http://www.4shared.com/file/65653788/aec7369/BJK_HTC_EzInput_QVGA_LPack_PT-RC1.html)]
As extracted from the Official Rom.

No Keyboard: Available
Keypad: Not available
Compact Keyboard: Available
Full Keyboard: Available

[0#18 Romanian (http://www.4shared.com/file/65653790/1d2cca1a/BJK_HTC_EzInput_QVGA_LPack_RO-RC1.html)]
Built from scratch and especially made and enabled for this release.

No Keyboard: Available
Keypad: Not available
Compact Keyboard: Available
Full Keyboard: Available

[0#19 Russian]
Some files are still missing and others need to be patched. Landscape support needs to be created from scratch.

No Keyboard: Not available
Keypad: Not available
Compact Keyboard: Not available
Full Keyboard: Not Available

[0#1B Slovak (http://www.4shared.com/file/65653793/84259ba0/BJK_HTC_EzInput_QVGA_LPack_SK-RC1.html)]
Built from scratch and especially made and enabled for this release.

No Keyboard: Available
Keypad: Not available
Compact Keyboard: Available
Full Keyboard: Available

[0#1D Swedish (http://www.4shared.com/file/67304584/92bbdc7f/BJK_HTC_EzInput_QVGA_LPack_SV-RC1.html)]
Graphics built from scratch. Layout files from the VGA version, patched for QVGA release. Added compatibility with Keypad devices.

No Keyboard: Available
Keypad: Available
Compact Keyboard: Available
Full Keyboard: Available

[0#1F Turkish (http://www.4shared.com/file/65653799/64f072be/BJK_HTC_EzInput_QVGA_LPack_TR-RC1.html)]
Built from scratch and especially made and enabled for this release.

No Keyboard: Available
Keypad: Not available
Compact Keyboard: Available
Full Keyboard: Available

DupinBJK

14th September 2008, 09:02 PM

Downloads - VGA

Instructions:

Uninstall of all the previously installed third party keyboards and SIP changers is recommended.

Choose your hardware configuration and download the main application (the blue hyperlinks).
Choose the Language Packs from post #3.
Uninstall any previous beta, if installed.
Make a soft reset.
If you are using a Rom with EzInput 1.5 already included, you must terminate the "SipGT_app" process first, or you won't be able to install.
Install the Main cab you've chosen. After the install it won't be necessary to reset your phone.
Install all the Language Packs you've chosen.
Make a soft reset.
NOTE: The main cabs don't include any language. Even if they will let the full list appear in the settings listbox, you'll have to manually add the languages you need to use.

Due to the peculiarity of the CAB install technology and the way with which HTC has conceived the Language List configuration in the Registry (a single string for all available languages, which can't be parsed by the WM CAB engine), the full list needs to be created before you'll install even a single Language Pack.
After that, to remove all unneeded languages from the list, a simple edit of the registry will suffice.

The first post for RC2 is here (http://forum.xda-developers.com/showpost.php?p=2978204&postcount=689).

VGA Main cabs - 0409
Note: These cabs are only meant for WWE 0409 roms.

[No Keyboard] - phones without HW keyboard (http://www.4shared.com/file/73788500/84dd008c/BJK_HTC_EzInput_VGA_NoKbd_0409-RC2.html)

[Full Keyboard] - phones with full HW keyboard (http://www.4shared.com/file/73788536/4693f67a/BJK_HTC_EzInput_VGA_FullKbd_0409-RC2.html)

DupinBJK

14th September 2008, 09:02 PM

Language Packs - VGA

These are the Language Packs add-ons specifically made for the 0409 - WWE main packages available in post #5. Not all languages are immediately available, but they will be added to the list as soon as they will be ready.
Please note that some Language Packs are not available for all devices, due to missing support files. You'll find detailed info for each language, below.

PLEASE NOTE:
RC1 Language Packs are 100% compatible with the RC2 Main cabs.
Language Packs from other packagers won't be compatible with the main cabs found in post #5, nor these ones will be compatible with Keyboard cabs made by other packagers.

[0#01 Arabic]
Some files are still missing and others need to be patched.

No Keyboard: Not available
Full Keyboard: Not Available

[0#05 Czech (http://www.4shared.com/file/73787952/46dd7cd7/BJK_HTC_EzInput_VGA_LPack_CS-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#06 Danish (http://www.4shared.com/file/73787964/84938a21/BJK_HTC_EzInput_VGA_LPack_DA-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#07 German (http://www.4shared.com/file/73787980/1d7d63b6/BJK_HTC_EzInput_VGA_LPack_DE-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#08 Greek (http://www.4shared.com/file/73787997/9a02c754/BJK_HTC_EzInput_VGA_LPack_EL-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#09 English (http://www.4shared.com/file/73788001/f511f2f1/BJK_HTC_EzInput_VGA_LPack_EN-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#0A Spanish (http://www.4shared.com/file/73788011/ec0ac3b0/BJK_HTC_EzInput_VGA_LPack_ES-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#0B Finnish (http://www.4shared.com/file/73788030/a93b91a4/BJK_HTC_EzInput_VGA_LPack_FI-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#0C French (http://www.4shared.com/file/73788038/a7e01996/BJK_HTC_EzInput_VGA_LPack_FR-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#0E Hungarian]
Not yet available. Files need to be created from scratch.

No Keyboard: Not available
Full Keyboard: Not available

[0#10 Italian (http://www.4shared.com/file/73788044/e117c37a/BJK_HTC_EzInput_VGA_LPack_IT-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#13 Dutch (http://www.4shared.com/file/73788051/886606b4/BJK_HTC_EzInput_VGA_LPack_NL-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#14 Norwegian (http://www.4shared.com/file/73788057/6105a381/BJK_HTC_EzInput_VGA_LPack_NO-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#15 Polish (http://www.4shared.com/file/73788063/4d45345b/BJK_HTC_EzInput_VGA_LPack_PL-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#16 Portuguese (http://www.4shared.com/file/73788074/ca3a90b9/BJK_HTC_EzInput_VGA_LPack_PT-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#18 Romanian]
Not yet available. Files need to be created from scratch.

No Keyboard: Not available
Full Keyboard: Not available

[0#19 Russian]
Not yet available.

No Keyboard: Not available
Full Keyboard: Not Available

[0#1B Slovak]
Not yet available. Files need to be created from scratch.

No Keyboard: Not available
Full Keyboard: Not available

[0#1D Swedish (http://www.4shared.com/file/73787942/5fc64d96/BJK_HTC_EzInput_VGA_LPack_SV-RC1.html)]
Created with files extracted from the latest Official roms.

No Keyboard: Available
Full Keyboard: Available

[0#1F Turkish]
Not yet available. Files need to be created from scratch.

No Keyboard: Not available
Full Keyboard: Not available

DupinBJK

14th September 2008, 09:02 PM

Downloads - WVGA

Placeholder

DupinBJK

14th September 2008, 09:02 PM

Language Packs - WVGA

Placeholder.

DupinBJK

14th September 2008, 09:02 PM

Placeholder.

DupinBJK

14th September 2008, 09:02 PM

Placeholder

mbarvian

14th September 2008, 09:04 PM

ooh, sounds great!

can't wait...

eric2k

14th September 2008, 09:10 PM

Good stuff :)

blazingwolf

14th September 2008, 09:11 PM

I'll play once you post it. :)

klmsu19

14th September 2008, 09:12 PM

when you do test it, possible to get a screenshot, least see what its like and how/if its different than the diamond keyboard

Ather

14th September 2008, 09:14 PM

sweet..im in..i have an Htc Himalaya with WM 6.1 (yes it still Runs :p)

Noonski

14th September 2008, 09:39 PM

when you do test it, possible to get a screenshot, least see what its like and how/if its different than the diamond keyboard

It's the Same but with More QVGA graphics because it's supposed to be for QVGA

ayyu3m

14th September 2008, 09:59 PM

always wanted to play with graphics. lets see what can be done in mspaint....no seriously paint!! keke

:eek: did someone jus mention screenshot???

blazingwolf

14th September 2008, 11:08 PM

@Noonski,

Did you fall asleep? I know you have been burning the candle at both ends over the last couple of days but I wondered what happened. :)

Noonski

14th September 2008, 11:13 PM

@Noonski,

Did you fall asleep? I know you have been burning the candle at both ends over the last couple of days but I wondered what happened. :)

The Links been up there for a while.

blazingwolf

14th September 2008, 11:25 PM

Ok, obviously I fell asleep. Missed it completely. :o

gullum

14th September 2008, 11:30 PM

this look like something I can do something with :D

I've been bussy getting everything els working on my Phones as I alrady have the Diamond keyboards so I didn't pay to much atention to this keyboard.
I will be uploading the OEM for phonecanvas soon.

it looks like there are qvga files in the pack

lepsyfou

15th September 2008, 02:42 AM

thank you Noonski, I love this keyboard :p

TheChampJT

15th September 2008, 02:53 AM

Can anyone post a screenshot please?

friguy33

15th September 2008, 03:07 AM

Would love to see a screen shot too

vetvito

15th September 2008, 04:27 AM

Keyboards so far,

http://i142.photobucket.com/albums/r100/vetvito/kbs.png

They look complete, but they only type numbers as of now. Only the Full Qwerty types letters.

met3ora

15th September 2008, 06:26 AM

How is this keyboard different from the Diamond ones that gullum released?

1loudsvt

15th September 2008, 06:31 AM

this is the real one....

Kraize

15th September 2008, 06:44 AM

How is this keyboard different from the Diamond ones that gullum released?

That one was VGA graphics downsized.

THIS one is the QVGA original graphics that should work out of the box. No downsizing, etc. Perfect graphics.

Graphics wise though, Comparing those images with my kaiser that has gullum's keyboard, these ones seem to have bigger arrow keys lol. The black arrows are bigger in this one. That's about the only difference i could find that you'd probably notice.

Noonski

15th September 2008, 08:18 AM

That one was VGA graphics downsized.

THIS one is the QVGA original graphics that should work out of the box. No downsizing, etc. Perfect graphics.

Graphics wise though, Comparing those images with my kaiser that has gullum's keyboard, these ones seem to have bigger arrow keys lol. The black arrows are bigger in this one. That's about the only difference i could find that you'd probably notice.

Not Completly I screwed up some graphics.

BNut Vito has some correct ones.

But i figured some of us where concentrating on other stugf maybe other people would have time to work on th Keyboards resising for other languages.

Ameet

15th September 2008, 02:31 PM

Awesome development :D

Hey Vito & Noonski. Waiting to see the final version of this one :D

lepsyfou

15th September 2008, 02:36 PM

Awesome development :D

Hey Vito & Noonski. Waiting to see the final version of this one :D
+1 I cant' wait :D

thank you very much advance :p

blazingwolf

15th September 2008, 05:24 PM

Will not install on my Titan. Says I don't have enough system permission.

DupinBJK

15th September 2008, 05:38 PM

Will not install on my Titan. Says I don't have enough system permission.

Any previous keyboard installed ?

Noonski

15th September 2008, 06:36 PM

Well, here it is.

I was working on a modified version from Raphael, to add the missing keyboards in Landscape mode, so it's a fast task to make a cab.

Just to start, I post the five languages version - EN, FR, DE, IT, ES. I'll post the others later, after a bit of bug testing.

The bigger graphics that don't seem to be in QVGA mode are indeed bigger by design. The old code was cutting the image mask and then inflating it right before blitting it on the screen (remember the bad enlargement ?) but the new one directly gets the image from the enlarged mask bitmap, and the result is quite better.

Sadly, the new EzInput is still missing the other two keyboards in Landscape mode, and it's not just a matter of adding graphics and layout files: it's the code base that's wrong, and I'm still looking at the assembler code.

I've not been able to test the new SIPMenu so far, because I'm only using a Kaiser and it seems that several other bits apart from Manila2D need to be added to the device to make it appear. If someone has any suggestion, I'll greatly appreciate it.

Anyway, let's stop talking. It's debug time :)

The cab has been tested on a Kaiser with HTC 6.1 rom, and install/uninstall work. Uninstall of any previous keyboard cab from Touch Dual / Diamond is recommended.

Many thanks to Noonski for the package and .hv files and to Laurentius26 for the dump.

BJK

Download link:

http://www.4shared.com/file/63082791/9f8e8f7f/BJK_HTC_EzInput_5Languages.html

Okay Junior You Got The Job!

Guys Help Him Out as much as you can don't double post the same issues.

Get out your Registry editors and Shizzle.

blibble

15th September 2008, 08:07 PM

Keyboards so far,

http://i142.photobucket.com/albums/r100/vetvito/kbs.png

They look complete, but they only type numbers as of now. Only the Full Qwerty types letters.

With Gullums keypad/keyboard on my Atom Life they only type numbers until you select options and then return to the keypad/keyboard. Weird! Is it the same with these ones maybe. If you find a fix for this it would be great. I text a lot and the keypad is the best out there.

DupinBJK

15th September 2008, 08:26 PM

With Gullums keypad/keyboard on my Atom Life they only type numbers until you select options and then return to the keypad/keyboard. Weird! Is it the same with these ones maybe. If you find a fix for this it would be great. I text a lot and the keypad is the best out there.

I can't reproduce your issue with this one. Which language are you using ?
If you're using one from EN, FR, DE, IT or ES, you could go ahead and try the one linked in the first post.

goldengraham

15th September 2008, 09:19 PM

Hey damn, I just noticed I'm having this same stupid numbers only issue with the HTC Keyboard (not QWERTY). I just installed TF2D on my touch. let me play with a couple things and see if I can find some sort of temporary fix.

Note: going into options allows letters again, but only for that instance of using the keyboard, and there's no way im going to hit that every time as im quite the txtr

GG

blibble

15th September 2008, 10:06 PM

DupinBJK

15th September 2008, 10:22 PM

goldengraham - I find on my atom life I only need to do this after a soft reset.

As I say, I'm using Gullums Diamond keypad and I wondered (and now I know) if this keypad suffered the same.

A fix would be nice :)

Well, blibble, do you say you now know that this keyboard has that problem because you've tested it, or because you think goldengraham has installed it ?

Either case, I cannot reproduce your issues here with *this* cab. I would appreciate if anyone of you could give me a list of steps to help me reproduce the issue you're talking about.

Thanks.

blazingwolf

15th September 2008, 10:30 PM

Any previous keyboard installed ?

Yes and that was the issue. I reflashed my ROM and then tried your keyboard and it is working fine. Any plans for an OEM?

Thank you for the work. :)

DupinBJK

15th September 2008, 11:16 PM

Yes and that was the issue. I reflashed my ROM and then tried your keyboard and it is working fine. Any plans for an OEM?

Thank you for the work. :)

Priority goes to the cabs, now. The other languages will come first, in a multilanguage approach similar to the great idea used by Gullum for his cab, and then each one separately.

It shouldn't take long because it's just a tedious work, but I'm going to test an install in a separate folder, to reduce the clutter in \Windows, and I've to make some test for the east-european languages, because some files are still missing and I'm only halfway through with the patching of the files from Raphael.

Anyway, stay tuned, it might happen sooner than you think.

I have a question, however: how do you deal with the landscape layouts missing from the HTC code ? Are they an issue for you ?

Thanks for your help. :)

gullum

15th September 2008, 11:34 PM

I have a oem that is working perfect on my kaiser and I can maybe make it multilanguage as the diamond keyboard.. but I need some time to do that.
I'm also bussy with camera and phonecanvas. and I'm also tyrying to get TF2D to work on wizard and Prophet while I cook a rom for ELF, Kaiser and Herlad.
on kaiser I have TF2d(with everything in all tabs working), Volumcontrol, album, camera, keyboard, Large menu and titlebar, youtube and google maps all working.

blazingwolf

15th September 2008, 11:36 PM

Priority goes to the cabs, now. The other languages will come first, in a multilanguage approach similar to the great idea used by Gullum for his cab, and then each one separately.

It shouldn't take long because it's just a tedious work, but I'm going to test an install in a separate folder, to reduce the clutter in \Windows, and I've to make some test for the east-european languages, because some files are still missing and I'm only halfway through with the patching of the files from Raphael.

Anyway, stay tuned, it might happen sooner than you think.

I have a question, however: how do you deal with the landscape layouts missing from the HTC code ? Are they an issue for you ?

Thanks for your help. :)

Hasn't been an issue for me because my ROM is setup to keep the software keyboard closed and use the hardware keyboard.

The landscape full qwerty works fine but the phone and compact keyboard switch to the standard keyboard when chosen.

If you need more testing done let me know.

mokoboy

15th September 2008, 11:40 PM

hi

i install it on my Nike and it work very well except hardware keyboard...

hope it's an usefull information, and perhaps hardware keyboard work one day...

DupinBJK

15th September 2008, 11:46 PM

The landscape full qwerty works fine but the phone and compact keyboard switch to the standard keyboard when chosen.

This sounds good... I could use the same workaround with this one. Can you tell me how it has been implemented ?

Thanks !

Noonski

15th September 2008, 11:50 PM

hi

i install it on my Nike and it work very well except hardware keyboard...

hope it's an usefull information, and perhaps hardware keyboard work one day...

Weird I left the Nike KeyMap in there Specifically.

Gullum has an anwser.

Well there are some Reg Keys in there for Rapheal so that would explain forcing not to use the Keyboard in Landscape.

I have to say i'm not as scholar ed in the KeyBoard, just throwing up thought Bubbles.

I have a oem that is working perfect on my kaiser and I can maybe make it multilanguage as the diamond keyboard.. but I need some time to do that.
I'm also bussy with camera and phonecanvas. and I'm also tyrying to get TF2D to work on wizard and Prophet while I cook a rom for ELF, Kaiser and Herlad.
on kaiser I have TF2d(with everything in all tabs working), Volumcontrol, album, camera, keyboard, Large menu and titlebar, youtube and google maps all working.

GULLUM=HARDCORE, i will propably repeat this untill other people start getting it.

Isn't there any other Other Wizard Cook That can Help you Verify?

kudvu002

16th September 2008, 12:20 AM

Weird I left the Nike KeyMap in there Specifically.

Gullum has an anwser.

Well there are some Reg Keys in there for Rapheal so that would explain forcing not to use the Keyboard in Landscape.

I have to say i'm not as scholar ed in the KeyBoard, just throwing up thought Bubbles.

GULLUM=HARDCORE, i will propably repeat this untill other people start getting it.

Isn't there any other Other Wizard Cook That can Help you Verify?

how's it coming fellas?

Noonski

16th September 2008, 12:25 AM

how's it coming fellas?

Slowly Just As It Should be ;)

All this attention From the last days puts to much pressure on the kettle.

goldengraham

16th September 2008, 12:28 AM

Alright I got past my problem. Installed your cab everything seems to work fine tho the T9 is very slow on compact QWERTY... besides that seems to work very well... keep up the good work.

GG

bedaweed

16th September 2008, 12:32 AM

DupinBJK

16th September 2008, 12:41 AM

Weird I left the Nike KeyMap in there Specifically.

Gullum has an anwser.

Well, being a Kaiser user I've never been able to use t9 with the keyboard, so I didn't even know that it was possible.
Since the Touch Dual, the Polaris and the Diamond all use the Nike file, and only the Touch Pro uses a different Raphael file, I'm wondering what's wrong.

Tell me, is it possible to use t9 with the hardware keyboard of both the Touch Dual and the Touch Pro ?
Using the Raphael file or adding the "HasHardKeyboard" key to the Tegic subkey of the Registry doesn't change anything...

Well there are some Reg Keys in there for Rapheal so that would explain forcing not to use the Keyboard in Landscape.

I thought that on the Raphael it was possible to hide the missing layouts thanks to the new SIPMenu, isn't it ?

DupinBJK

16th September 2008, 12:59 AM

Alright I got past my problem. Installed your cab everything seems to work fine tho the T9 is very slow on compact QWERTY... besides that seems to work very well... keep up the good work.

GG

English t9 is quite fast here on the Keypad, I've not noticed a speed difference between Keypad and Compact Qwerty.
French T9 seems to have less words when in Compact Qwerty mode, but that's strange, because it still can suggest words and so it shouldn't point to a dictionary issue.
No particular problem on Italian too, and the German one is able to suggest those few words I know :)

Let's wait for other reviews, to get a better insight...

Thanks for your time !

gullum

16th September 2008, 01:13 AM

Tell me, is it possible to use t9 with the hardware keyboard of both the Touch Dual and the Touch Pro ?

the t9 is working on my girlfriend Touch dual hardware keyboard using my throttle danish rom.

DupinBJK

16th September 2008, 01:23 AM

the t9 is working on my girlfriend Touch dual hardware keyboard using my throttle danish rom.

What have you done to enable it ?

gullum

16th September 2008, 01:28 AM

What have you done to enable it ?

I had to add the dahpd.kdb in her case (danisk hardware keyboard file) to get it to work.
I'm shure if I find what file is for hardware keyboard in touch pro I can get t9 working with hardware keyboard on kaiser too

DupinBJK

16th September 2008, 01:58 AM

I had to add the dahpd.kdb in her case (danisk hardware keyboard file) to get it to work.
I'm shure if I find what file is for hardware keyboard in touch pro I can get t9 working with hardware keyboard on kaiser too

I agree, but I can't find *hpd.kdb files in the Raphael ROMS I have here.
I have an enhpd.kdb file that comes from a very old Touch Dual Keyboard cab, but on that registry it's used where now the spd.4x4.English.kdb is used instead...

Beside the file, what have you done on the registry, to allow the hardware keyboard use ? I've here your Diamond keyboard cab, and I don't see any particular setting different from what can be extracted from the default.hv file... Please share some light :)

kudvu002

16th September 2008, 03:08 AM

keeping this thread at top!

blibble

16th September 2008, 06:48 AM

Mikulec

16th September 2008, 08:12 AM

DupinBJK - Vetvito reported in post 16 that the keypad was typing only numbers.

I have not tried this cab myself because I have Gullums Diamond keypad working on my Atom Life.

My post was just to inform that with Gullums keypad, on devices that have this problem, pressing options and returning to the keypad would fix this until the next soft reset, so he could try this and see if the same is true for this keypad.

I know that some devices do not have this problem and some do, but nobody seems to know why. I did wonder if it is only non-HTC devices that are affected.

I had the same issue on Kaiser(typing only numbers). I installed this keyboard, but my hardware keyboard was unable to perform the fn+space function, so I had to install disable xt9 and after that the software keyboard typed only numbers. Before installing disable xt9 was all working correctly.

garsim

16th September 2008, 11:37 AM

the t9 is working on my girlfriend Touch dual hardware keyboard using my throttle danish rom.

on my touch dual(20keys) key mapping are wrong! :(

DupinBJK

16th September 2008, 11:38 AM

DupinBJK - Vetvito reported in post 16 that the keypad was typing only numbers.

Indeed, there's a bit of misunderstanding.
Vetvito posted earlier than me, talking about his version of the cab that had still that problem. But I was already completing my work on my version of the cab, which doesn't suffer from the same issue, and then I later posted it on this thread.

Noonsky has kindly moved my post to the beginning of this thread, so it seems that Vetvito is reporting an issue against my version of the cab, but he's not, he's just talking about his version.

Until Vetvito will be back online, maybe to update his post, I can update the first one to clarify the issue.

Thanks for letting me know !

DupinBJK

16th September 2008, 11:39 AM

on my touch dual(20keys) key mapping are wrong! :(

Hardware or Software key mappings ?

DupinBJK

16th September 2008, 11:51 AM

I had the same issue on Kaiser(typing only numbers). I installed this keyboard, but my hardware keyboard was unable to perform the fn+space function, so I had to install disable xt9 and after that the software keyboard typed only numbers. Before installing disable xt9 was all working correctly.

Yes, I can confirm that fn+space doesn't work anymore. I don't have here "disable xt9", so I will look for it on xda and I'll investigate a bit further.
Thanks for reporting it.

It would be interesting to know if the Raphael suffer from the same issue or not. Anyone out there ?

Mikulec

16th September 2008, 12:09 PM

Yes, I can confirm that fn+space doesn't work anymore. I don't have here "disable xt9", so I will look for it on xda and I'll investigate a bit further.
Thanks for reporting it.

It would be interesting to know if the Raphael suffer from the same issue or not. Anyone out there ?

I am at work right now so I cant attach it here, but u can download the cab here (http://www.4shared.com/file/36879118/89dc721f/duttythroy_Disable_xt9.html?s=1)

garsim

16th September 2008, 12:14 PM

Hardware or Software key mappings ?

hardware! :(

DupinBJK

16th September 2008, 12:19 PM

I am at work right now so I cant attach it here, but u can download the cab here (http://www.4shared.com/file/36879118/89dc721f/duttythroy_Disable_xt9.html?s=1)

Found, thanks!
It seems a problem caused by the XT9 IME package from Tegic, the registry settings are as "designed" by the HTC programmers. We have to find a workaround for it, and Touch Pro users could be really useful at this...

DupinBJK

16th September 2008, 12:25 PM

hardware! :(

Ok, I need a few more info:

Which kind of keyboard was previously installed ?

hardware mapping has worked right from the start, on your phone, or did you install anything to make it work ? Please detail.

garsim

16th September 2008, 01:26 PM

Ok, I need a few more info:

Which kind of keyboard was previously installed ?

hardware mapping has worked right from the start, on your phone, or did you install anything to make it work ? Please detail.

on my device i haven't install any keyboard. the software input are defaults of windows mobile (keyboard,block recognizer, letter recognizer).

DupinBJK

16th September 2008, 01:56 PM

I had the same issue on Kaiser(typing only numbers). I installed this keyboard, but my hardware keyboard was unable to perform the fn+space function, so I had to install disable xt9 and after that the software keyboard typed only numbers. Before installing disable xt9 was all working correctly.

I've just found this, about the Touch Pro keyboard and T9:

[...]turn off T9 assist when using the hardware keyboard. To do this, slide out the keyboard, and press function+space and choose ABC.

it's from the Touch Pro review at PocketNow.com.
This is quite interesting. Now, we have to discover how to remap this function on the Kaiser, and what kind of menu appears to allow the choice.

Any good soul with a Touch Pro device willing to let us know ?

Thanks !

DupinBJK

16th September 2008, 01:59 PM

on my device i haven't install any keyboard. the software input are defaults of windows mobile (keyboard,block recognizer, letter recognizer).

So you're using the default Touch Keypad and Touch Keyboard that come with the Touch Dual.

What language are you using ?

You say that you are using your own ROM, in your signature. Is it a production ROM, or is it cooked ?

garsim

16th September 2008, 02:28 PM

So you're using the default Touch Keypad and Touch Keyboard that come with the Touch Dual.

What language are you using ?

You say that you are using your own ROM, in your signature. Is it a production ROM, or is it cooked ?

i'm using my rom based on Niki Kitchen and i don't use(and haven't install) touch keyboard software input. i'm using only English (also for xt9)

DupinBJK

16th September 2008, 03:17 PM

i'm using my rom based on Niki Kitchen and i don't use(and haven't install) touch keyboard software input. i'm using only English (also for xt9)

Well, you don't use it, but it's part of the Nike Rom, as far as I know. I might be wrong, but I assume it by browsing the user guide of the Touch Dual, which clearly shows it. Perhaps it's no longer part of your cooked rom.

Anyway, since you don't use those SIPs, I can only assume that the hardware key mapping is conflicting with some of the soft key mappings of the Opal package. The registry keys are set for a main 0409 language, so this sounds strange... I will look into it, maybe waiting for some other reports from the other users. More than a hundred have downloaded it, they will post sooner or later.

Meanwhile, since you don't have a previous version installed, uninstall should be safe. But before you do that, have you downloaded the Hardware key fix straight from the HTC support site ? I've read that many mapping issues for the Nike have been solved by that fix, not even related to the Diamond/Opal keyboard cabs...

Here's the link:

http://www.htc.com/europe/supportdownloadlist.aspx?p_id=44&cat=all

garsim

16th September 2008, 04:09 PM

Well, you don't use it, but it's part of the Nike Rom, as far as I know. I might be wrong, but I assume it by browsing the user guide of the Touch Dual, which clearly shows it. Perhaps it's no longer part of your cooked rom.

Anyway, since you don't use those SIPs, I can only assume that the hardware key mapping is conflicting with some of the soft key mappings of the Opal package. The registry keys are set for a main 0409 language, so this sounds strange... I will look into it, maybe waiting for some other reports from the other users. More than a hundred have downloaded it, they will post sooner or later.

Meanwhile, since you don't have a previous version installed, uninstall should be safe. But before you do that, have you downloaded the Hardware key fix straight from the HTC support site ? I've read that many mapping issues for the Nike have been solved by that fix, not even related to the Diamond/Opal keyboard cabs...

Here's the link:

http://www.htc.com/europe/supportdownloadlist.aspx?p_id=44&cat=all

i already have this patch but with new rom doesn't install! :(

goldengraham

17th September 2008, 12:17 AM

DupinBJK

17th September 2008, 02:19 AM

Alright, I removed everything from my phone (HTC Vogue) and this keyboard still runs slow. Well maybe thats a bit harsh. Compact QWERTY with T9 on is verrrry sluggish. Besides that... GOOD WORK!

Hope you can make an improvement to that because I'm a big fan of the Compact QWERTY. Back to gullums diamond for now.

GG

Well, you're welcome. So far, as you see, you're the only one reporting a speed issue. Since you feel better with the one made by Gullum, of course it's the better choice for you :)

Anyway, if you want to go further and take a look at the differences between the registry entries of the two cabs, you'll notice that they are exactly the same, right because they come from the same base configuration.
The things that change are the layout and the dictionary files, but this doesn't explain your issue.

Even the Tegic libraries have the same version found in the latest Raphael ROMS, so what's left ?

It might be caused by the changes in the ezinput.dll file, then, which is newer than the one found in the latest available ROMs, but on all the devices where I've personally tested the cab so far, no speed issue exist. If I were you, I'd double check with a similar device but with a different rom - not all cookers are created equal ;)

Thanks for your time, anyway !

goldengraham

17th September 2008, 02:28 AM

DupinBJK

17th September 2008, 03:07 AM

Hmmmm well I cooked it with 20273 kitchen myself. and I actually prefer your keyboard because it works properly with TF2D... is that .dll in question coded into the rom? I'm going to try and buld a 20226 rom and see if that helps.

Any other hints would be good also, I'll always try anything with this phone.

GG

All the files of this package come from the actual leaked Opal ROM, exactly like the ones that are being used to build the Manila2D, but, as I've said, only the ezinput.dll is really new. The dictionary files are the same found in the Raphael and Diamond ROM, and the layouts have only been converted (where necessary) for QVGA, but this has been done by HTC right for the Opal, which is still in QVGA.
The Tegic libraries are the latest ones found both in the Raphael and Diamond, too.

The only thing still worth to mention is that the cab made by Gullum has been made with libraries coming from a pre-release version of the diamond, you can see it from the version of both the ezinput.dll and the tegic dll(s). I know it for sure, because I'm disassembling that dll for a particular purpose. The version of the tegic libraries used, moreover, is the latest compatible with the previous version of the Touch Keypad and Keyboard - remember the old ones with the black background ?

This could lead me to think that it's a Vogue issue, maybe because of it core speed - after all I'm mainly testing the cab on a Kaiser, so there's a chance that the speed problem could not appear here, but this afternoon I've personally tested the cab on a Touch Dual, and I've not noticed any particular speed issue. Right, I must add that it was a production HTC Rom, with nothing else installed, but a bare metal test is always a good test.

That said, since there could be many unknown factors to explain your issue, I'm waiting to get more speed reports, to compare each configuration with yours. As you see, here is almost a no-man's land. As we use to say - No news is good news :)

I'll PM you if I'll discover anything new about it.

BJK

goldengraham

17th September 2008, 06:38 AM

Hmmmm... well 20270 didnt help, so i built a 20273 with a 32mb page file and everything seems to be ok (and i installed the original HTC Touch keyboard from the kitchen as well) as long as i installed it before i install TF2D... I would have done more tests but i got a nice fun error 270 and had to deal with that... need phone for work tomorrow.

I'll try a couple other things tomorrow.

kristoff_sz

17th September 2008, 10:42 AM

I've installed this on my Kaiser

(Running Stock WM 6.0).

Then without testing installed SJ's XT9 CAB (attached with his Raphael Keyboard),

and I must say that I'm impressed.
Graphics are perfect.
Im using tapping method (without T9) and it works fantastic.
Landscape mode automaticaly set the QWERTY keyboard, and portrai automatic set's up previous defined keyboard.

Thanks guys. Have no problems so far!

DupinBJK

17th September 2008, 11:34 AM

kristoff_sz

17th September 2008, 11:40 AM

Thanks Kristoff_sz. If you don't mind I'll need your help once more a bit later on, right for the Polish cab.

No problem! I'm "open" for any suggestions and tasks ;)

1loudsvt

17th September 2008, 12:16 PM

DupinBJK

17th September 2008, 12:27 PM

someone else was reporting that it is very sluggish esp using the phone pad...I am having the same problem. As far as it being almost the same as gullums...the gullum keypad and compact qwerty will only output numbers after the installation of manilla 2d where as this one works like it should just very slow

At last, someone else reporting a speed issue !
Now, I'd need more details:

Model
Language
Previous keyboard installed
ROM version

I understand you are using gullum's cab, but all the other details are equally important, and we need a bit of standardization in bug reporting, if we have to overcome the issue... Thanks !

kristoff_sz

17th September 2008, 12:33 PM

At last, someone else reporting a speed issue !
Now, I'd need more details:

Model
Language
Previous keyboard installed
ROM version

I understand you are using gullum's cab, but all the other details are equally important, and we need a bit of standardization in bug reporting, if we have to overcome the issue... Thanks !

I've tested the T9 with phone pad and compact qwerty.
I have no speed issue, it run fast without any problems.

Model:
Kaiser,
Previous keyboard:
None (just the stock ones).

Mikulec

17th September 2008, 12:37 PM

I've tested the T9 with phone pad and compact qwerty.
I have no speed issue, it run fast without any problems.

Model:
Kaiser,
Previous keyboard:
None (just the stock ones).

I can confirm that, no speed issues on Kaiser.

DupinBJK

17th September 2008, 12:44 PM

I've tested the T9 with phone pad and compact qwerty.
I have no speed issue, it run fast without any problems.

And while it's good, it doesn't help to iron out the issue. GG, the first who has reported the speed issue, is using a Vogue - same processor speed.
That's why we need to build a reports DB.

Could you just add the info about the language of your ROM ?

Thanks for your contribution !

DupinBJK

17th September 2008, 12:46 PM

I can confirm that, no speed issues on Kaiser.

And not just because you're not complaining, a request for help for the forthcoming Slovak cab... :)

Can you just add the infos about your device ?

Model:
Language:
Previous keyboard installed:
ROM version:

Thanks.

Mikulec

17th September 2008, 12:59 PM

And not just because you're not complaining, a request for help for the forthcoming Slovak cab... :)

Can you just add the infos about your device ?

Model:
Language:
Previous keyboard installed:
ROM version:

Thanks.

Offcourse,

Model: HTC Kaiser(tytn II)
Language:WWE
Previous keyboard installed:none
ROM version: Kumara.DK.4 WWE (http://forum.xda-developers.com/showthread.php?t=426349)

I am looking forward to the slovak cab, if u need help just tell me.

thangkls

17th September 2008, 02:46 PM

Nice keyboard - I like it !
Can I have a question ? How can I type dot character ?

blazingwolf

17th September 2008, 02:59 PM

Nice keyboard - I like it !
Can I have a question ? How can I type dot character ?

Tap or press on the .,123 button. Now tap or press the button right under the number 1. It looks like a dash but it is actually the period or dot button.

I think it is just the way they made the keys as the colon button looks like 2 dashes.

goldengraham

17th September 2008, 03:01 PM

DupinBJK

17th September 2008, 03:18 PM

Nice keyboard - I like it !
Can I have a question ? How can I type dot character ?

Well, you should thank the designers at HTC for it. We're just here to repackage everything to let all HTC users use what the management at HTC doesn't care to give to owners of previous devices.

To type a dot character you can go to the symbol pad (the Sym button) or you can tap a bit longer than usual the button which shows in its upper part the symbol you need: for example, in compact qwerty - english, the button is the one which shows 'op'.

Would you please tell us the following info ?

Model
Language
Previous keyboard installed
ROM version

Thanks !

DupinBJK

17th September 2008, 03:38 PM

Here's what I found in my brief bit of testing yesterday

This setup worked well...
Model: Vogue
Language: English
Previous keyboard installed: HTC Touch Keyboard (original)
ROM version: Cooked 20273 w/ 32mb page file
The rom I made basically contained nothing but games, as I was going to be loading TF2D on there and it covers just about everything I used it for.

Model: Vogue
Language: English
Previous keyboard installed: none
ROM version: Cooked 20273 w/ 24mb page file
With this setup (same selections minus the keyboard) T9 with the compact QWERTY was sluggish...

Anyways, theres a new kitchen build out today 20748 so I'll be playing with that and reporting back.

Is there a possibility of getting an OEM package of this keyboard so I can cook it right into my ROM?

Thanks
GG

And this is a good report ! Thanks GG !

As you can see, another user has reported a speed issue, but we're still waiting to get the details for his device.
The details you give seems to bring us just to one conclusion: would it be possible to say that is a pagefile issue ? It would be good to compare with another Vogue...

For the OEM, you'll have to wait. The priority goes to cabs and to install/uninstall procedures, due to the peculiarity of the application. Many users would like to add/remove languages, and the actual configuration has not been made with this need in mind - remember the issues regarding the cab from Gullum ?
This issue will regard cooked roms, too, so the base package needs a bit more attention than usual. After all, it will end with a better OEM package, too.

BJK

darth maximus

17th September 2008, 04:22 PM

blibble

17th September 2008, 04:57 PM

darth maximus - try pressing options on the keypad and then quit out of that to return to the keypad.

DupinBJK

17th September 2008, 05:11 PM

darth maximus - try pressing options on the keypad and then quit out of that to return to the keypad.

Blibble, you still haven't installed this cab, do you ? :D

Well, your help is welcome, but I can assure you that this thread is not about the gullum's cab, and that I'm not gullum in disguise :rolleyes:

Credit given to his work, we're here to sort things out, not to talk about that cab...

Next time, could you install the newer one and report the details ? Thanks ! :)

thangkls

17th September 2008, 05:11 PM

@blazingwolf: thank for your help.

@DupinBJK: English keyboard works good on my Prophet (O2 Neo) with OS 5.2.20273 Build 20273 which I got from :
http://forum.xda-developers.com/showthread.php?t=418612
( I'm using only English keyboard )

DupinBJK

17th September 2008, 05:17 PM

hi guys,

i like the keyboard (all three) and it worked initially for me. however, after a day (when i soft reset it?), only the full qwerty works. if i use compact qwerty or phonepad, it just types in number or symbols. :(

would like to get this working since i'd like to use phonepad sometimes.

model: TyTN II
ROM: 3.28.405.0 WWE HTC stock 6.1 ROM
previous keyboard: non, installed after a hard reset. using sip change program though.
no speed issue though.

Believe me when I say that I'm using your *exact* configuration here, and that I've lost the count of how many times I've made a soft reset in these few days right before the first post and after.

I've not used any kind of SIP change, and I still have no issues with missing letters, numbers or symbols.

Could you make another hard reset and just install the cab, without any sip changer ?

Thanks, and welcome...

blibble

17th September 2008, 07:07 PM

venelar

17th September 2008, 07:27 PM

DupinBJK

18th September 2008, 12:35 AM

Thanks for the keyboard, very nice!

One thing i have noticed however, when sending a sms on my hermes, the slideout qwerty keyboard used to filter recipient names as i typed them. After installing this cab the hardware qwerty is no longer doing this.

Is there a regedit i need to change back?

You forgot the details: :)

Model:
Language:
Previous keyboard installed:
ROM version:

This is an open issue, and is mainly related to the compatibility between the Tegic XT9 IME used with the soft keyboard and the hardware keyboard of the device. A known workaround, from the times of the first HTC keyboard cabs, is to disable XT9 on the registry, but is certainly annoying.

On post #44 gullum reports that:

"the t9 is working on my girlfriend Touch dual hardware keyboard using my throttle danish rom."

but this all that is known at the moment. XT9 doesn't work with any of the previous Diamond keyboards cab I've tried so far, when using hardware keyboards, not even with his one, but I haven't received any other detail about that lucky phone :)

The only thing that I can add is that the Raphael solves the issue in a very good way: ABC/T9 can be toggled with the hardware keyboard, to enable T9 in text editing programs and enable context aware typing (the one that can be enabled by disabling T9) everywhere else.
We have to see whether there's a registry configuration to apply or not, or if it will be just a matter of changing the assignment of the hardware keys.
Well'have time to look for info later on.

In the meantime, it would be useful to get the details about your configuration, to build a good db of issues.

Thanks for testing !

BJK

venelar

18th September 2008, 12:44 AM

You forgot the details: :)

Model:
Language:
Previous keyboard installed:
ROM version:

This is an open issue, and is mainly related to the compatibility between the Tegic XT9 IME used with the soft keyboard and the hardware keyboard of the device. A known workaround, from the times of the first HTC keyboard cabs, is to disable XT9 on the registry, but is certainly annoying.

On post #44 gullum reports that:

"the t9 is working on my girlfriend Touch dual hardware keyboard using my throttle danish rom."

but this all that is known at the moment. XT9 doesn't work with any of the previous Diamond keyboards cab I've tried so far, when using hardware keyboards, not even with his one, but I haven't received any other detail about that lucky phone :)

The only thing that I can add is that the Raphael solves the issue in a very good way: ABC/T9 can be toggled with the hardware keyboard, to enable T9 in text editing programs and enable context aware typing (the one that can be enabled by disabling T9) everywhere else.
We have to see whether there's a registry configuration to apply or not, or if it will be just a matter of changing the assignment of the hardware keys.
Well'have time to look for info later on.

In the meantime, it would be useful to get the details about your configuration, to build a good db of issues.

Thanks for testing !

BJK

Hermes (Cingular 8525)
WWE
No previous keyboards installed
Dvha v19

Thanks for the reply, look forward to the finished product

DupinBJK

18th September 2008, 01:04 AM

DupinBJK - I'm sorry. I appreciate what you are saying, and yes, I have installed your cab (only just) and it works great on my Atom Life. :D

My comment to Darth Maximus was only intended to find out if this fixed his problem on a temporary basis as it was a known problem on someone elses release. I think you will agree (particularly as you follow the M2D thread) that sometimes users can have problems that others with apparently the same set up do not experience.

With Gullums keypad I could only ever type numbers when texting from within PocketCM, yet with WM texting it was fine. As a result I changed to iContact.

I shall re install PocketCM and test it as I really liked the app, and report back.

Thanks for the excellent work. I've tried many keypads in the past as I text a lot and this one is by far the best.

Tested with PocketCM and works perfectly. Great job DupinBJK! Plus the smaller buttons look better. Just have to get smaller thumbs now ;)

I understand your point of view, blibble, and it's right because I know very well the intricacies of bug testing and reporting, that even if I appreciate your help I need to avoid references to other keyboard cabs as much as possible. Even gullum is aware of the issues regarding his cab, but we are not trying to solve them. This is exactly the same technology, only packaged in a slight different way. Hey, you nearly stopped goldengraham from trying the cab... ;)

Jokes apart, the ezinput package from HTC - not from me or anyone else - has its merits and its defects; something will need to be patched, something will need to be repackaged in a different way. This is not going to be the best possible package for it, only a particular approach for making a package as it should have been done by HTC from the first day, for all its customers. I'm not building something for my roms, but something that won't be a thorn in our side for all of us. You know it well, people can be frightened quite easily, and there's already a user base represented by more than 20 thousand downloads which has been experiencing the issues of the gullum's cab that you know so well. I'd like to solve those issues, with your help, and so we must try to avoid any kind of misunderstanding.

You know, even the new Diamond and Touch Pro customers, which HTC still hasn't forgot, have several issues with their 'production' Diamond keyboards.
We're going to try to solve them as well, you'll see.

And now, let's keep on testing. Everyone that has a bit of his free time to share could browse through the threads, to discover who's reporting issues or workarounds on these topics somewhere else. I'll be quite busy in the next days... :)

Thanks for joining in !

darth maximus

18th September 2008, 03:27 PM

DupinBJK, thanks for the tip. did the hard reset and installed most of my apps except for sipchange. it works now! did a couple of soft resets throughout the day. so my conclusion is that sipchange and htc opal keyboard don't play well together. will let you know if i encounter any problems.

has anyone noticed that one of the opal keyboards becomes the default after a soft reset? or is it just me?

DupinBJK

18th September 2008, 05:04 PM

Noonski

18th September 2008, 05:06 PM

You're welcome, darth maximus !
And no, it's not just you, it's the startkey app working in the background... :)

BJK

And what happens when you remove Startkey?

(i always remove any and all redundant StartUp Apps)

But not in the position to test this one at the time.

DupinBJK

18th September 2008, 06:26 PM

And what happens when you remove Startkey?

(i always remove any and all redundant StartUp Apps)

But not in the position to test this one at the time.

The EzInput keyboard won't be selected as default. Just that.

It sets the default keyboard to Full QWERTY, but according to the assembly code it should be possible to change it with a custom key. I haven't tried so far, though.

Seems it should be safe to delete it, along with the SIPMenu, which should be useful only with the Manila interface :)

canadiankorean

18th September 2008, 06:34 PM

Also put on your latest cab and found it slow.

HTC Touch (Telus = Vogue)

DupinBJK

18th September 2008, 06:46 PM

Also put on your latest cab and found it slow.

HTC Touch (Telus = Vogue)

And that's why we'd need more details about your device:

Model
Language
Previous keyboard installed
ROM version

The Vogue seems so far to be the only one reporting speed issues, but it could be related to particular flavours of custom ROMs. Could you give us those details?

Thanks !

canadiankorean

18th September 2008, 07:31 PM

Too much work to get all that info.

Model: Touch
Language: English
Previous keyboard installed: Default HTC
ROM version: 3.07.661.1
Radio: 3.41.00
Windows 6.1

DupinBJK

18th September 2008, 07:57 PM

Too much work to get all that info.

Model: Touch
Language: English
Previous keyboard installed: Default HTC
ROM version: 3.07.661.1
Radio: 3.41.00
Windows 6.1

And you can't even imagine how much work is needed to collect it ! :D

By the way, if you have a Touch with a 6.1 ROM, then you're using a custom ROM. Who has cooked it ?

canadiankorean

18th September 2008, 07:59 PM

And you can't even imagine how much work is needed to collect it ! :D

By the way, if you have a Touch with a 6.1 ROM, then you're using a custom ROM. Who has cooked it ?

Touche!

It's not custom.
Telus has the official 6.1 rom out.
http://www.htc.com/us/supportdownloadlist.aspx?p_id=80&cat=all

DupinBJK

18th September 2008, 08:46 PM

Touche!

It's not custom.
Telus has the official 6.1 rom out.
http://www.htc.com/us/supportdownloadlist.aspx?p_id=80&cat=all

All right. I've just looked at the user guide of your device, and it says that you should have the old Touch KeyPad and Touch Keyboard installed. So far, this is the configuration which has been raising the speed issue.

But I'd need you to be more specific, then. You say it's slow, but exactly:

Where have you find it to be so particularly slow ?
With which keyboard ?
In which mode, ABC or T9 ?

And, not less important:

Have you made a soft reset, since you've installed the cab ?
have you already installed much other software on it ?
Could you tell me the amount of its free Storage and Program memory ?

It might seem an awful lot of questions, but since this issue doesn't appear on all Touch devices, it's awfully important to get as much details as possible.
Don't blame me, I'm only the packager :D

Thanks,

BJK

randomelements

18th September 2008, 10:56 PM

DupinBJK

18th September 2008, 11:03 PM

Nice keyboard - I'm not getting any speed issues, just getting the old hardware keyboard only giving numbers problem on my Niki. Must admit I never use the HW keyboard except for dialling so doesn't really bother me. Still, any ideas on a fix would be appreciated.

Thanks.

Your "the old hardware keyboard only givig numbers problem" makes me wonder. Could you give me more details ?

Did you experience it on the previous Keypad + Keyboard included on every Niki, or just on previous Diamond Keyboard cabs?

And, did it get solved ? If yes, how ?
I'd really appreciate if you could point me to some useful links.

Thanks,
BJK

randomelements

19th September 2008, 12:38 AM

Your "the old hardware keyboard only givig numbers problem" makes me wonder. Could you give me more details ?

Did you experience it on the previous Keypad + Keyboard included on every Niki, or just on previous Diamond Keyboard cabs?

And, did it get solved ? If yes, how ?
I'd really appreciate if you could point me to some useful links.

Thanks,
BJK

It's just the previous Diamond based keypads. Don't think I've ever seen a cab that works but I'm sure people have got them working when placed directly in to a rom. Maybe it's just mapping vonflicts.

Obviously the diamond based pads aren't going to cater for a hardware keyboard.

DupinBJK

19th September 2008, 01:13 AM

It's just the previous Diamond based keypads. Don't think I've ever seen a cab that works but I'm sure people have got them working when placed directly in to a rom. Maybe it's just mapping vonflicts.

Are you talking about any particular rom ?

And, have you tried disabling xt9 to see if the keyboard start typing letters again ?

I'd need these info too:

Model:
Language:
Previous keyboard installed:
ROM version / cooker:

Thanks !

Romeo_Beck

19th September 2008, 03:53 AM

Thank you very much
You're good man
Soft runs very good

My device
Atom Exec
Model: Atom
Language: English
Previous keyboard installed: gullum Diamond keyboard
Windows 6.1
XDA Atom Exec WM6.1 CE OS 20270 build 19209 by homer285

carlos_polanco

20th September 2008, 02:48 AM

DupinBJK

20th September 2008, 11:37 AM

Hi people!

Congratulation for your hard work on making this keyboard to work fine.

I'm not having any speed issue or other... [Spanish]

Is there a way to import/export ALL my own words to the dictionary??? I just saw on Settings "eT9 My Words" but that way is one by one... :(

You should backup your previous eT9Rudb.Rdb, eT9Cdb.Cdb and eT9AsDb.Adb files, remove the read only attribute and then copy them back after you've installed the new cab.

carlos_polanco

20th September 2008, 06:07 PM

Thanks my friend.

But I use the old HTC PhonePad and don't used the diamond or other keyboard. With T9EDITOR I'm able to import/export all those words easily.

Hope in a future we can do that with this beautiful keyboard!

kristoff_sz

22nd September 2008, 11:55 AM

DupinBJK

22nd September 2008, 12:26 PM

Hey Dupin!

I've tested the keyboard with HTC_eT9_Polish.cab.

The Compact QWERTY works perfect without any problems or lags.

But what i have noticed is:

The PhoneKeybad is messed up, I mean, the keys are disorted,
Full QWERTY in landscape mode don't show letters.

Cheers,
Chris

You can't wait, uh ? :D
Well, I don't even know the package you're talking about, and I wouldn't mix flavours if I were you ;)
Now, sadly, due to the nasty nature of cabs, you'll have to reinstall all over from scratch...

kristoff_sz

22nd September 2008, 12:32 PM

You can't wait, uh ? :D
Well, I don't even know the package you're talking about, and I wouldn't mix flavours if I were you ;)
Now, sadly, due to the nasty nature of cabs, you'll have to reinstall all over from scratch...

I won't reinstall for now, Im using only compact qwerty so its good for me as for now ;)

But I'll wait for your eT9 relase to test too!

DupinBJK

22nd September 2008, 01:20 PM

I won't reinstall for now, Im using only compact qwerty so its good for me as for now ;)

But I'll wait for your eT9 relase to test too!

And that's good... that et9_Polish cab has no files at all for full qwerty support. But you won't have to wait for too long :)

chongtw

22nd September 2008, 02:10 PM

DupinDJK,

Really like your keypad. Previously I was using P1Tater's keypad which is very good but because it was VGA, there were some slight distortion of the image. Recently I also encountered some problems with the T9 saved words which forced me to revert back to Touchpal. Hence, I was delighted to have discovered your keyboard. The other good news is that it automatically helps to remove the old P1Tater's keyboard, which according to some users, cannot be uninstalled properly. Your program automatically replaced the P1Tater's keyboard without any problem.

Now my question:- Is there a way to edit Saved Words in T9? Sometimes we might saved a word accidentally and instead of seeing it continously comes up (for example "oj" instead of "ok") during T9, a simple edit of the dictionary/saved words may suffice.

Any suggestions? Thanks,

I am using a touch cruise, with original ROM.

DupinBJK

22nd September 2008, 03:48 PM

DupinDJK,

The other good news is that it automatically helps to remove the old P1Tater's keyboard, which according to some users, cannot be uninstalled properly. Your program automatically replaced the P1Tater's keyboard without any problem.

That issue is common, on devices which already have the old Touch Keypad + Keyboard innstalled, and you have it in your rom. Uninstalling is always troublesome in these cases, and it's not a fault of P1Tater. As a matter of fact, now you'll probably have the same uninstall issue with my version of the cab. For the time being, we'll have to deal with these issues. We'll jump on the install/uninstall features on B2.

Now my question:- Is there a way to edit Saved Words in T9? Sometimes we might saved a word accidentally and instead of seeing it continously comes up (for example "oj" instead of "ok") during T9, a simple edit of the dictionary/saved words may suffice.

Any suggestions? Thanks,

I am using a touch cruise, with original ROM.

WWE Rom, I suppose, right ?

Anyway, if you go to the Programs folder, you'll find a link for eT9MyWords. I've put it there just for this purpose.

Thanks for testing !

BJK

canadiankorean

22nd September 2008, 07:11 PM

All right. I've just looked at the user guide of your device, and it says that you should have the old Touch KeyPad and Touch Keyboard installed. So far, this is the configuration which has been raising the speed issue.

But I'd need you to be more specific, then. You say it's slow, but exactly:

Where have you find it to be so particularly slow ?
With which keyboard ?
In which mode, ABC or T9 ?

And, not less important:

Have you made a soft reset, since you've installed the cab ?
have you already installed much other software on it ?
Could you tell me the amount of its free Storage and Program memory ?

It might seem an awful lot of questions, but since this issue doesn't appear on all Touch devices, it's awfully important to get as much details as possible.
Don't blame me, I'm only the packager :D

Thanks,

BJK

Sorry haven't had time to reply.

Where have you find it to be so particularly slow ? Everything is slow. Pressing a key would result in half sec delay before it shows up. The T9 words take half sec to display. It seems more a display issue imo.
With which keyboard ?
I tried the full qwerty
In which mode, ABC or T9 ?
Haven't tried ABC

I was typing in several areas like Opera, Youtube, Messages.

And, not less important:

Have you made a soft reset, since you've installed the cab ? Yes I soft reset it twice
have you already installed much other software on it ? Just the usual manilla 2d and a few other apps. C
ould you tell me the amount of its free Storage and Program memory ?
Sorage = 80.95MB Program 60.75MB free

DupinBJK

22nd September 2008, 08:17 PM

Sorry haven't had time to reply.

Where have you find it to be so particularly slow ? Everything is slow. Pressing a key would result in half sec delay before it shows up. The T9 words take half sec to display. It seems more a display issue imo.
With which keyboard ?
I tried the full qwerty
In which mode, ABC or T9 ?
Haven't tried ABC

I was typing in several areas like Opera, Youtube, Messages.

And, not less important:

Have you made a soft reset, since you've installed the cab ? Yes I soft reset it twice
have you already installed much other software on it ? Just the usual manilla 2d and a few other apps. C
ould you tell me the amount of its free Storage and Program memory ?
Sorage = 80.95MB Program 60.75MB free

Well, your issues are even worst than worst case detailed so far.
But since you've already installed the Manila2D beta, you should prepared to do it, if asked. You should make an hard reset and then reinstall just this cab.

So far, the Vogue(s) reports have been contradictory. Nothing, in both the latest 6.1 roms from both Sprint and Telus justifies the speed issues, and there's even a report involving custom roms.
The only strange thing worth to mention is that the official ROMs are using a Tegic XT9 release with a build quite different than the one used for all the other phones. The previous 'Diamond' keyboard cab reported as working is working just on some Vogue(s) and not on others.
So ? Conflicting applications ? Wrong settings in the custom ROMs ?
Only someone willing to make an hard reset would be able to make some light.

Let us know.

DupinBJK

24th September 2008, 07:11 PM

All the previous posts are related to the previous release of this package.
Discussions and reports about Beta1 will start after this post.

Thanks for joining in,

BJK

randomelements

25th September 2008, 12:15 AM

Just glad I could be of some help. Nice work :)

kristoff_sz

25th September 2008, 12:45 AM

I'm reserving the space here. Will report hmm... according to the hour I have - today ;)

iggy

25th September 2008, 05:11 AM

blazingwolf

25th September 2008, 05:16 AM

So far everything seems to be working perfectly on my Titan. This includes the FN + Space functionality. Very good job. :D

DupinBJK

25th September 2008, 11:26 AM

So far everything seems to be working perfectly on my Titan. This includes the FN + Space functionality. Very good job. :D

I'm glad you like it. You know, when noone answers to your help requests, you have to make it on your own ;)

And, about that, are there other key combinations missing from your Titan ?
We could try to fix them, if it's ok for you.

Thanks for reporting it,

BJK

DupinBJK

25th September 2008, 11:52 AM

BJK, amazing work. Really appreciate your efforts.

Quick question is it possible just to install the Full Keyboard or at minimum advise which files can be deleted that would not corrupt the Full Keyboard functionality.

I never use the Compact Qwerty keyboard or T9.

Yes, for the layouts it's possible. But then, a cab for each layout combination would have to be created, and different add-ons cabs for the languages would be necessary too. Too many cabs, too much confusion. Wouldn't it be better just to disable the keyboards you don't need ?

Unless, of course, you're trying to use as less space as possible...
But, taking English as an example, you would save no more than 200KB, by removing those two layouts. The bigger files are for the T9, and they can't be removed - unless you're a very big friend of device.exe stopping every once in a while... :)

BJK

vmax0505

25th September 2008, 12:03 PM

bnm7bnm

25th September 2008, 12:11 PM

Any chanse for Hebrew layout?

Thanx.

njakobs

25th September 2008, 12:20 PM

Works great on my vouge. Running Vetvito's 2.1 Kitchen rom. I am having no problems at all with the speed.

Works perfect.

Cheers

DupinBJK

25th September 2008, 12:26 PM

Hi,

After installing EzInput on my Elfin, the font size in the Cube APLauncher page decreased and is now quite ugly. If I uninstall EzInput, it returns to normal size and if I reinstall EzInput I have the same problem again!
Has this problem already reported? Is there a solution?

Model: Touch (Elfin)
Language: English
Previous keyboard installed: Default HTC
ROM version: 2.20.710.2B WWE
Radio: 03.07.90
Windows 6.1 (CE OS 5.2.2021)
ExtROM version: Blue Elves v5.0

No, you're the first to report it.
This EzInput package installs its fonts from the HelveticaNeue family, as introduced with the Diamond phones and now on the Opal rom. So it should not overwrite anything, since the original Elf rom didn't have those fonts.
The package then uses a special setting in the registry:

HKLM/Software/Microsoft/FontLink/SystemLink

whose purpose is clearly explained on MSDN:

Windows Embedded CE provides a font linking capability so that you can link one or more TrueType fonts to another TrueType font. Font linking is typically used to enable Roman fonts to display non-Roman characters.

This, too, should not produce any side effect as the one you're talking about unless, of course, there's already a configuration issue in the "Cube AP Launcher" you're referring to.
Could you uninstall the keyboard and make a list of all the fonts installed on your system ? A link to that "Cube" cab or OEM package would be appreciated, too.

Thanks for reporting.

DupinBJK

25th September 2008, 12:36 PM

Any chanse for Hebrew layout?

Thanx.

Well, unfortunately not.
The EzInput dll shows no support for the 0x040D locale (if you load the dll file into Notepad, you'll notice that even the language name is missing).
I know that Tegic should be supporting it, but this keyboards suite is actually a combination of a keyboards suite and of Tegic's T9, so HTC has the final word on this.

I once saw a Raphael ROM with Hebrew support on the Wiki, but it doesn't really have any Hebrew support file on it, too. Have you ever asked to HTC anything about Hebrew language support ? Could you point me to useful links on the net ?

Thanks,

BJK

gullum

25th September 2008, 12:46 PM

DupinBJK

25th September 2008, 12:48 PM

Works great on my vouge. Running Vetvito's 2.1 Kitchen rom. I am having no problems at all with the speed.

Works perfect.

Cheers

Thanks for reporting it !
It seems that the speed issue is related to apps compatibility only, then.
Users with light ROMs, or who have just made an hard reset, or who have not installed several keyboards at the same time, are not reporting speed issues.

If the other Vogue users who are experiencing those speed issues would like to get support on how to solve them, please be aware that more details about each Vogue configuration will be needed, along with a possible hard reset of their device.

Thanks for the cooperation, and especially to njakobs for this 'successful install' report.

BJK

DupinBJK

25th September 2008, 12:54 PM

Thanks for this keyboard I've also been working a bit with it but as I'm now cooking for 7 devices I havn't had much time to work on the keyboard.
so you have saved my a lot of time here.
The nike keyboard has always giving me problems and now you done it for me and I'm verry happy because otherwice I would have had to put the stock rom back on my girlfriends Nike because of the Keyboard.

if you need any help in adding regs for more languaes I'd be glad to help.

Very glad of being of any help to you :)
One user is still reporting a glitch on the 20keys, but I'm waiting for other details. As soon as I'll get them, I'll make a public post to let Nike users try to reproduce the issue.

I'll PM you by then, if you wish.

iggy

25th September 2008, 01:14 PM

Yes, for the layouts it's possible. But then, a cab for each layout combination would have to be created, and different add-ons cabs for the languages would be necessary too. Too many cabs, too much confusion. Wouldn't it be better just to disable the keyboards you don't need ?

Unless, of course, you're trying to use as less space as possible...
But, taking English as an example, you would save no more than 200KB, by removing those two layouts. The bigger files are for the T9, and they can't be removed - unless you're a very big friend of device.exe stopping every once in a while... :)

BJK

Thanks BJK, well one can only hope, yes I was trying to save some space. Way too many things installed but of course I want them all.

vcdwelt

25th September 2008, 01:16 PM

vmax0505

25th September 2008, 01:40 PM

No, you're the first to report it.

I am the first one to report to you but not the first one with this problem!
See at this link: http://forum.xda-developers.com/showthread.php?t=428481

Could you uninstall the keyboard and make a list of all the fonts installed on your system ? A link to that "Cube" cab or OEM package would be appreciated, too.

Where can I see the list of installed fonts?
The cube application is in fact the HTC TouchFlo application and I am referring to the applications' face of the cube !

namaste74

25th September 2008, 02:04 PM

* Model: Touch Cruise
* Language: WWE
* Previous keyboards installed: my ROM only had basic keyboard/letter recognizer
* Previous SIP changer installed: no
* ROM version (6.0/6.1 - HTC/Cooked): Cooked Swtos v6.1 WWE v.96 light
* Description of the issue: none, just letting you know it works well

DupinBJK

25th September 2008, 03:33 PM

* Model: T-Mobile Touch Plus (HTC Nike 200)
* Language: German Device / WWE ROM
* Previous keyboards installed: no (one Opal like is cooked into rom)
* Previous SIP changer installed: no
* ROM version (6.0/6.1 - HTC/Cooked): Cooked Mary v6.1 WWE
* Description of the issue: Couldn't install, get permission error
* Did this issue exist even before the cab was installed?: n.a.

Hi vcdwelt, and thank-you for the report.
A few users who reported your issue have been able to install the cab after a soft reset. Could you try and let us know ?

DupinBJK

25th September 2008, 03:35 PM

DupinBJK

25th September 2008, 03:48 PM

I am the first one to report to you but not the first one with this problem!
See at this link: http://forum.xda-developers.com/showthread.php?t=428481

Well, he can't expect to contribute if he asks for help in the wrong thread... ;)

Where can I see the list of installed fonts?

Connect to the windows folder through Activesync, and look for the files with a *.ttf extension. Those are the truetype fonts. I need their names, and if there's something other beside the tahoma and courier, rar them and give me a link to download the package.

The cube application is in fact the HTC TouchFlo application and I am referring to the applications' face of the cube !

As such, I should have already received more reports... Quite strange.
I need a bit of help from you. First, tell to that fellow that he should report his issue here: two testers are better than one :)
Then, since I don't have an Elf, I'd need to compare the graphics *before* the keyboard and *after* the keyboard. The pic he posted has no value, if I cannot compare it to something else.

Could you help us ?

Thanks.

vmax0505

25th September 2008, 03:57 PM

TomSe

25th September 2008, 04:45 PM

DupinBJK

25th September 2008, 04:49 PM

you mentionned that I should not have the "HelvetiaNeue LT 55 Roman" font in my HTC Touch (Elfin) but I have it! May be it came with the "Blue Elves v5.0" upgrade!

Assuming that the "cube" application uses also the "HelvetiaNeue LT 55 Roman" font and your application changing the font for the Tahoma one (if I understood well your explanation about the "fontlink" and its associated registry key), this could explain the problem if the "cube" is using now the "tahoma" font!

What is your opinion?

Well, at this point we can't yet talk about opinions. I need evidence, first.

Clearly, MSDN sounds a bit cryptic sometimes. The FontLink allow programs to revert to the Linked font, when a given character is not available in the Primary font. This means that the Helvetica might be replaced by the Tahoma, and not vice versa. But this is especially true for symbols, or non-latin characters, not for the ones you're looking at.

Taking into account the only piece of evidence that we have, the picture posted in that other lonely thread, a simple test can be made:

http://i384.photobucket.com/albums/oo284/DupinBJK/Cube_Fonts.jpg

Those are the two fonts we're talking about. If they seem equal, look at them once again: they are not.

Compare the pic of the cube to this one, and answer to this question: what's the font used on the cube ?

Now, as I've said, evidence is lacking. I don't know if the pic is a *before* or an *after*, so it can't be said which font has replaced the other.
If the pic is an *after*, then the Helvetica has replaced the Tahoma.

But let's stop it here... next time, send me the info I request, first.

BJK

eazy2001x

25th September 2008, 04:54 PM

DupinBJK

25th September 2008, 05:00 PM

Hi,

I'm using the OPAL keyboard as part of a ROM I flashed, and I like it alot. Only disappointment is that it lacks the dutch files. I tried using the official NL file from my touch but it seems it is not compatible with the keyboard.
Is there any way to download the files for the dutch T9 dictionary for this keyboard or is it planned in the near future?

Thanx alot,

TomSe.

As I write in the first post, other languages won't be available for download during the Beta1 phase. You should PM me for such info.

They will be available in the next phase.

You cannot mix cab from different packages or different packagers. They won't be compatible, and removal of the latter will render the former unusable.

BJK

DupinBJK

25th September 2008, 05:08 PM

Is there a way to get the buttons the same size as the gullum keyboard? your keys are a bt smaller and harder to use with my big thumb.. also did you have any luck with the Titan HW keyboard working with this?

This is not the format requested for posting in this thread. If you have requests, PM me.
This space is only for posting successful reports or issues, as clearly explained in the first post right above the download links.

Anyway, for the "1st mistake bonus" you'll get your answers, *this* time.

1] No, these are the layouts made by HTC for the QVGA version. Gullum used the VGA graphics resized.

2] "any luck" is certainly not a clear way to describe an issue. A Titan user who has followed the rules has reported no issue on his keyboard. You'd better check the previous posts, first.

BJK

TomSe

25th September 2008, 05:12 PM

As I write in the first post, other languages won't be available for download during the Beta1 phase. You should PM me for such info.

They will be available in the next phase.

You cannot mix cab from different packages or different packagers. They won't be compatible, and removal of the latter will render the former unusable.

BJK

Ok, sorry,

Thanks.

eazy2001x

25th September 2008, 05:29 PM

This is not the format requested for posting in this thread. If you have requests, PM me.
This space is only for posting successful reports or issues, as clearly explained in the first post right above the download links.

Anyway, for the "1st mistake bonus" you'll get your answers, *this* time.

1] No, these are the layouts made by HTC for the QVGA version. Gullum used the VGA graphics resized.

2] "any luck" is certainly not a clear way to describe an issue. A Titan user who has followed the rules has reported no issue on his keyboard. You'd better check the previous posts, first.

BJK

Model: Sprint Mogul
Language: English
Previous keyboards installed: Gullum
Previous SIP changer installed: NA
ROM version (6.0/6.1 - HTC/Cooked): Stock Sprint WM6.1 ROM from HTC

Description of the issue(s):

- When I installed this keyboard the word auto complete/spell check stoped working when using the standard on screen keyboard or using the hardware keyboard.

- I got use to using the Gullum keyboard since the buttons seem to be larger by aprox 10 pixels and its hard for me to press the letter boxes accurately since your keyboard is smaller. This slows down my words per minute drastically along with increased misspelled words.

Did this issue exist even before the cab was installed?:

I did not have this problem with any of the stock keyboards installed after a hard reset.

Maxxd01

25th September 2008, 05:48 PM

I'm trying to install the file but I have the information "instalation was unsucessful. the program or seting cannot be installed because it does not have sufficient system permissions.

And now...?

Mazz

25th September 2008, 05:52 PM

Same error on a 20 key Niki :(

vcdwelt

25th September 2008, 05:53 PM

Hi,

After a softreset the same problem occours :-(
no permission (round 80% installed)

Maxxd01

25th September 2008, 05:56 PM

Same error on a 20 key Niki :(

I have a 16 niki... So the problem is not the files (i think), anyone can help us?

Mazz

25th September 2008, 06:17 PM

I have a 16 niki... So the problem is not the files (i think), anyone can help us?

I tried several ROM from Niki forum as well as I tried to cook one from jerpelea's kitchen and I'm still not able to get hardware keyboard working. I thought I've made a mistake with the kitchen but I've the same issue with Gullum's ROM etc...

Maxxd01

25th September 2008, 06:21 PM

I tried several ROM from Niki forum as well as I tried to cook one from jerpelea's kitchen and I'm still not able to get hardware keyboard working. I thought I've made a mistake with the kitchen but I've the same issue with Gullum's ROM etc...

I have 16 key niki and by now in a lot a rom's i've used three where hardware keyboard works (but not the XT9 PTG).

anyone can help me with the instalation problem?

DupinBJK

25th September 2008, 06:26 PM

Same error on a 20 key Niki :(

Unless you'll follow the rules for reporting issues, Mazz, your post won't be counted, and you won't receive support.

BJK

DupinBJK

25th September 2008, 06:29 PM

I have 16 key niki and by now in a lot a rom's i've used three where hardware keyboard works (but not the XT9 PTG).

anyone can help me with the instalation problem?

There's no 'anyone' rushing to help you just because in a few minutes you've not received an answer. Please, avoid Panic mode.

You just have to post an issue report - following the rules, and you'll receive support. This is still a one-to-many relationship. You'll have to wait.

And believe me, so far everyone has received an answer.

BJK

DupinBJK

25th September 2008, 06:38 PM

Hi,

After a softreset the same problem occours :-(
no permission (round 80% installed)

Well, you reported that no previous keyboard or SIP changer was installed. Have you installed other projects in beta before this cab, on that device ?

DupinBJK

25th September 2008, 06:47 PM

Model: Sprint Mogul
Language: English
Previous keyboards installed: Gullum
Previous SIP changer installed: NA
ROM version (6.0/6.1 - HTC/Cooked): Stock Sprint WM6.1 ROM from HTC

Description of the issue(s):

- When I installed this keyboard the word auto complete/spell check stoped working when using the standard on screen keyboard or using the hardware keyboard.

- I got use to using the Gullum keyboard since the buttons seem to be larger by aprox 10 pixels and its hard for me to press the letter boxes accurately since your keyboard is smaller. This slows down my words per minute drastically along with increased misspelled words.

Did this issue exist even before the cab was installed?:

I did not have this problem with any of the stock keyboards installed after a hard reset.

Thanks for the report, eazy2001x. This is the way to go :)

Here are the questions:

1] A change to the T9 settings makes no difference ? Autocomplete / SpellCheck still don't work ?
2] Would it be possible for you to uninstall the cab made by Gullum, make a soft reset and then install this one ?
3] An hard reset would be a good idea, if you still get the error after the request at [2]. Any chance ?

Thanks for joining in,

BJK

itje

25th September 2008, 06:54 PM

removing it.

Was wrong place to post this.

lepsyfou

25th September 2008, 06:59 PM

Works good with my polaris
I install it under customization in my new rom. And I can for now not see any issues. But I will report back if any of those who use my rom reports anything.

I tried to make a OEM package, but it gives error building default.hv etc..
I tried to clean it up, but Im not a rgu expert, but there are something not correct somewhere in there, perhaps a cleanup could be good, If anyone would be so kind to look over the OEM package :)

And if you guys needs a tester for Norwegian language with this keyboard, do pm me.

cheers

thank you very much itje for your share :D

DupinBJK

25th September 2008, 07:30 PM

thank you very much itje for your share :D

lepsyfou, it's quite useless for me to ask people to follow rules and post only reports, if you jump here and post a message that has nothing to do with issue reporting, isn't it ?

So, if you have something to report, please do it, you'll be welcome.
OEM packages or other unrequested cabs don't belong to this thread. If everyone that has something to post arrives here and post a cab or a fix or whatever, everything will become a mess.

I'm sure many users are not interested. If you need a separate thread about an OEM package you're welcome, and you'll even receive support. But this is not the place.

Thanks for your cooperation

BJK

blazingwolf

25th September 2008, 08:34 PM

I'm glad you like it. You know, when noone answers to your help requests, you have to make it on your own ;)

And, about that, are there other key combinations missing from your Titan ?
We could try to fix them, if it's ok for you.

Thanks for reporting it,

BJK

I am more then willing to help out but honestly I don't know the keyboard combos that are available (I don't use the hardware keyboard very often). Is there a list somewhere of them? I look and see if I can find it also.

Maxxd01

25th September 2008, 08:37 PM

Zero|Cool

25th September 2008, 08:44 PM

DupinBJK

25th September 2008, 09:13 PM

Works great on my tytn although i still have a problem... Whenever i want the special caracters like "é à á ó" and I press the FN+Space i get a menu to enable and disable a lot of stuff :mad: Is there a way to remap this key to the special symbols again? :confused:

Glad to know it works on your phone, Zero|Cool, but could you post a detailed report as requested in the first post of this thread ?
All reports needs to be collected, successful ones and issues.
It won't be possible to give you any kind of support, without it.

This said, you have the "1st mistake bonus" as everyone else.
So, I'll re-explain something that I've already explained in the first post.

The Tegic T9 installed by EzInput replaces the standard IME that ships with nearly all the full keyboard phones made by HTC.
It's that standard IME, which gives the DeadKeys functionality on Fn+Space.
The new IME from Tegic doesn't have it, and all the users who have installed EzInput versions ranging from 1.0 to 1.5 have lost that functionality.

A know workaround is the DisableXT9 from Dutty, which removes the new setting from the registry and replaces it with the old one (it's just a matter of changing a key value in the registry). But you have to soft reset the device each time that you use it, if you then decide to restore the T9 IME.
So, I've remapped Fn+Space to make it work as in the new Touch Pro - the menu you see is the ABC/T9 menu, which lets you use T9 with the full hardware keyboard.

You might not like it, but sure, it's a first, at least on this forum.
If you don't like it, it can be removed, but you won't get the old behaviour unless you completely disable T9. The choice is yours.

I hope I made myself clear.
Next time, read the first post more carefully, and post a detailed report.

BJK

DupinBJK

25th September 2008, 09:19 PM

I dont know if there is a need of a ROM without any keyboard do .cab work. However, I told my brother (he has the pocket pc) to install a ROM without any keyboard, and the cab installed and worked sucessfuly.

When I reach home I'll try understand how this really works. Thanks for your posts.

Thanks.
This issue is most of the times related to running program on your device, or to conflicting apps. That's why it's always better to remove all the other installed keyboards and SIP changers, and then soft reset the device, before you install this cab.

So far, all the users reporting this issue for this cab and for a whole lot of others have been able to solve it. Be patient, and check your installed apps before reporting it.

This said, We still need the detailed info of your device, for the database.

Thanks for joining in.

BJK

eazy2001x

25th September 2008, 09:31 PM

Thanks for the report, eazy2001x. This is the way to go :)

Here are the questions:

1] A change to the T9 settings makes no difference ? Autocomplete / SpellCheck still don't work ?
2] Would it be possible for you to uninstall the cab made by Gullum, make a soft reset and then install this one ?
3] An hard reset would be a good idea, if you still get the error after the request at [2]. Any chance ?

Thanks for joining in,

BJK

I actually installed this right after a hard reset with nothing else installed. Just to clarify.. I am having the auto complete problem on the stock "keyboard" and when using the "hardware keyboard". When you start to type something out a box will appear with suggested words. So if I want to type in the work "enter" soon as I type en I get a popup box with "enter", "entered", "entrance", etc.. When I install your keyboard I lose this feature.

MY Thoughts: I think this happens because the file in the registry for the keyboard switches to a different dill file when your KB gets installed.

TomSe

25th September 2008, 09:46 PM

Ok, sorry,
Thanks.
These are my specs, if you can help me out on the dutch files, I would like to help testing them on my device.
I'm using the Opal keyboard already included in the Onyx ROM and I've updated it with the other languages to check if that would work, and it seems it does.
----------------------------------------------
HTC Touch (P3450 - ELF)
ROM: Onyx 2.1 (Manilla2D)
WM6.1 CE OS 5.2.20748 (Build 19214.1.0.4)
Radio: 03.21.90
Protocol: 4.1.13.61
ExtROM: Cooked by dsixda [74.93MB Free]
Memory: 4GB µSD
IPL 2.27.0002
SPL 2.28.0000
Language: WWE
Current keyboard: OPAL already present in the ROM
----------------------------------------------

DupinBJK

25th September 2008, 09:59 PM

I am more then willing to help out but honestly I don't know the keyboard combos that are available (I don't use the hardware keyboard very often). Is there a list somewhere of them? I look and see if I can find it also.

Well, that's not a good excuse. It's almost exactly the same thing I said when someone raised the first hardware mapping issue on his Nike. :D
But now my Fn+Space works, and I'm finally able to use T9 on the hardware keyboard of my Kaiser. And by the way, it seems we have the same layout. I might be wrong, but it seems that all the other combos work.
There other symbols menus that we could choose from, not just the usual one, but I'll look at it later and maybe post some pictures - these are included in the Tegic T9 dll(s)

Thanks !

DupinBJK

25th September 2008, 10:00 PM

Reserved for future use.

vcdwelt

25th September 2008, 10:12 PM

Zero|Cool

25th September 2008, 10:14 PM

Glad to know it works on your phone, Zero|Cool, but could you post a detailed report as requested in the first post of this thread ?
All reports needs to be collected, successful ones and issues.
It won't be possible to give you any kind of support, without it.

This said, you have the "1st mistake bonus" as everyone else.
So, I'll re-explain something that I've already explained in the first post.

The Tegic T9 installed by EzInput replaces the standard IME that ships with nearly all the full keyboard phones made by HTC.
It's that standard IME, which gives the DeadKeys functionality on Fn+Space.
The new IME from Tegic doesn't have it, and all the users who have installed EzInput versions ranging from 1.0 to 1.5 have lost that functionality.

A know workaround is the DisableXT9 from Dutty, which removes the new setting from the registry and replaces it with the old one (it's just a matter of changing a key value in the registry). But you have to soft reset the device each time that you use it, if you then decide to restore the T9 IME.
So, I've remapped Fn+Space to make it work as in the new Touch Pro - the menu you see is the ABC/T9 menu, which lets you use T9 with the full hardware keyboard.

You might not like it, but sure, it's a first, at least on this forum.
If you don't like it, it can be removed, but you won't get the old behaviour unless you completely disable T9. The choice is yours.

I hope I made myself clear.
Next time, read the first post more carefully, and post a detailed report.

BJK

I didn't quite understand the way to disable it. I went into that menu and disabled t9 but when i got back to the message editor whenever i pressed the FN+Space, it would show that menu again :(
In addition here is a report:

HTC TyTN (Hermes 200)
ROM: PC_Pro.V20
WM6.1 CE OS (Dont remember :rolleyes:)
Radio: 1.48.00.10
Protocol: 4.1.13.61
Memory: 2GB SD
IPL 2.10
SPL 2.10 Olipro
Language: WWE
Current keyboard: This one I installed for sms's texting and physical keyboard for word/net

Hope this helps :D

edit: Forgot to mention, Im loving the diamond style keyboard, since the "buttons" are bigger I can text while im walking or driving without needing to slide the phone for the physical one. In the perfect ROM we would have all the keyboard types (Yes i use the original ROM keyboard because it becomes handy in some ocasions cuz its smaller ^^).

DupinBJK

25th September 2008, 10:16 PM

These are my specs, if you can help me out on the dutch files, I would like to help testing them on my device.
I'm using the Opal keyboard already included in the Onyx ROM and I've updated it with the other languages to check if that would work, and it seems it does.
----------------------------------------------
HTC Touch (P3450 - ELF)
ROM: Onyx 2.1 (Manilla2D)
WM6.1 CE OS 5.2.20748 (Build 19214.1.0.4)
Radio: 03.21.90
Protocol: 4.1.13.61
ExtROM: Cooked by dsixda [74.93MB Free]
Memory: 4GB µSD
IPL 2.27.0002
SPL 2.28.0000
Language: WWE
Current keyboard: OPAL already present in the ROM
----------------------------------------------

Well, testing the cab with a rom which includes a pre-release of the keyboard made by another packager is not a good idea, as vcdwelt confirms below.
It might even work with the other cabs you've found, but if you have to test this Keyboards suite you should get the cabs from a single source.
That's because there could be conflicting issues between the settings used by the cooker and the ones I'm placing in the cabs you'll find here.
I'm not going to try to solve issues that might be related to mixed configurations, I hope you understand that it would be too much time-consuming.

About your need for the Dutch language add-on, as I've already told you, we'll have to deal with it in another way, during the Beta1 phase. You know you can PM me on that.

And then, thanks for all the infos you've posted about your device, but you should follow this format:

Model:
Language:
Previous keyboards installed:
Previous SIP changer installed:
ROM version (6.0/6.1 - HTC/Cooked):

Description of the issue:
Did this issue exist even before the cab was installed?:

Thanks,

BJK

Maxxd01

25th September 2008, 10:17 PM

Model: HTC Touch Dual 16 keys
Language: Portuguese
Previous keyboards installed: Touch keyboard
Previous SIP changer installed: No
ROM version (6.0/6.1 - HTC/Cooked): WM6 HTC PTG OEM

Description of the issue: keyboard only wrote numbers
Did this issue exist even before the cab was installed? With the instalation of the cab, it works good.

Honestly, I dont know how it worked. Is not possible to erase the Touch Keyboard, so I dont know how it was just replaced. I tought isn't not allowed overwrite Rom files. I'll do some tests and try do understand.

Thanks.
This issue is most of the times related to running program on your device, or to conflicting apps. That's why it's always better to remove all the other installed keyboards and SIP changers, and then soft reset the device, before you install this cab.

So far, all the users reporting this issue for this cab and for a whole lot of others have been able to solve it. Be patient, and check your installed apps before reporting it.

This said, We still need the detailed info of your device, for the database.

Thanks for joining in.

BJK

DupinBJK

25th September 2008, 10:20 PM

I didn't quite understand the way to disable it. I went into that menu and disabled t9 but when i got back to the message editor whenever i pressed the FN+Space, it would show that menu again :(

You can disable it it only by manually editing the registry, or using the Disable T9 cab from Dutty, that you can find on this forum.

Thanks,

BJK

DupinBJK

25th September 2008, 10:36 PM

@BJK

Ok tried a few things.

In Roms which have Opal Keyboard cooked in the Hardwarekeyboard didn't work. In Roms without cooked in an keyboard i can install opal keybard as cab file an all work fine :-)

My Result: Cooked in Opal Keyboard is the Problem, maybe something wrong with the oem version in the rom's.

Tried Mary'a and Lily's rom on my Touch Dual 16key

Your cab in a rom without cooked in opal is really Great!

Yes, testing these cabs on a ROM with a pre-release made from another packager is absolutely not recommended. First of all because there are important compatibility fixes introduced here for the first time, and then because different packagers could choose a different customization.

Using different customizations on the same technology would surely produce unpredictable issues and side effects. Would anyone install Manila2D cabs coming from different threads ? It could be a nightmare, for users and packagers.

This is the thread we we are going to build the cabs with different customizations for all the available layouts of the HTC PPC phones. It has not been done before, and if you check you'll see that only a few layouts have been considered so far by the other packagers, and that hardware compatibility has always been a big issue.

The cookers who'd like to build their OEM packages are obviously free to build whatever they want, but our priority here is not OEM Packages. When the cabs will be ready, better OEM packages will be made, and you will get them from your favorite cooker. In a way or another, you'll end with things that have been fixed here, and you can be sure of that because in the end this is the real purpose of this project.

Thanks for your update !

BJK

DupinBJK

25th September 2008, 10:43 PM

Model: HTC Touch Dual 16 keys
Language: Portuguese
Previous keyboards installed: Touch keyboard
Previous SIP changer installed: No
ROM version (6.0/6.1 - HTC/Cooked): WM6 HTC PTG OEM

Description of the issue: keyboard only wrote numbers
Did this issue exist even before the cab was installed? With the instalation of the cab, it works good.

Honestly, I dont know how it worked. Is not possible to erase the Touch Keyboard, so I dont know how it was just replaced. I tought isn't not allowed overwrite Rom files. I'll do some tests and try do understand.

So, it appears that the issue has been solved. Thanks for letting us know.

See it in this simple way: the file you see are not actually in the Rom, that's why you can overwrite them. It's when you make an hard reset, that you get back the files stored in the rom. So, when you install this cab, the new files with the old names overwrite the old ones, but not in the Rom. The same happen with the registry. The hard reset is always our last resort. :)

BJK

DupinBJK

25th September 2008, 11:04 PM

I actually installed this right after a hard reset with nothing else installed. Just to clarify.. I am having the auto complete problem on the stock "keyboard" and when using the "hardware keyboard". When you start to type something out a box will appear with suggested words. So if I want to type in the work "enter" soon as I type en I get a popup box with "enter", "entered", "entrance", etc.. When I install your keyboard I lose this feature.

MY Thoughts: I think this happens because the file in the registry for the keyboard switches to a different dill file when your KB gets installed.

Well, your Mogul should actually be a Titan, and Titan users are not reporting this issue. Have you tried pressing Fn+Space and select T9 from the menu which appears ?

BJK

Calkulin

25th September 2008, 11:21 PM

Is it a known issue that I can't disable the word suggestion box on this release? Because I don't have that problem with the EzInput version found in the Manilla2D install,

DupinBJK

25th September 2008, 11:46 PM

Is it a known issue that I can't disable the word suggestion box on this release? Because I don't have that problem with the EzInput version found in the Manilla2D install,

You're not following the rules of this thread. I can't give you any kind of support if you don't give us enough details. Please read the first post, and come back with the details we need.

To this, it must be added that:

Users who are going to install the Manila2D should install it first, and reinstall this cab over it.
I won't support issues arising from the misconfiguration caused by the install of the beta of Manila2D.

BJK

DupinBJK

26th September 2008, 12:22 AM

Support request for WWE Nike20Keys users

I'm looking for Nike20Keys users willing to test an issue reported by one user.
Please post your replies using the Title above.

Issue:
The user reports the hardware mapping on his Nike 20Keys as working, but is nonetheless experiencing a strange behaviour on his Backspace key.

The issue occurs when using the hardware keyboard.
He says that if the last letter he has typed is still selected, pressing the backspace key will delete it just momentarily, because it will suddenly reappear on the screen.

The only workaround he has found is to unselect the last letter using the arrow keys, and then use the backspace.

I don't have a Nike here to make the tests, and he's quite busy, so we can discuss about this issue no more than once or twice in a day.
He has kindly provided two videos, to help anyone better understand the issue.

I would really appreciate if the 20keys users who are testing the keyboard could download those videos and try to reproduce the issue on their phone, to give me more details.

Here's the link (http://www.4shared.com/file/64476035/3447c977/Nike20Keys_Backspace_issue.html)to the videos.

Many thanks in advance,

BJK

Zero|Cool

26th September 2008, 02:05 AM

You can disable it it only by manually editing the registry, or using the Disable T9 cab from Dutty, that you can find on this forum.

Thanks,

BJK

Which part of the registry should I edit m8? :confused:

rions3

26th September 2008, 05:16 AM

vmax0505

26th September 2008, 10:05 AM

Now, as I've said, evidence is lacking. I don't know if the pic is a *before* or an *after*, so it can't be said which font has replaced the other.
If the pic is an *after*, then the Helvetica has replaced the Tahoma.

But let's stop it here... next time, send me the info I request, first.

BJK

please find hereafter the cube before installation of EzInput:

http://img519.imageshack.us/img519/7596/cubebeforeezinputlf6.jpg (http://imageshack.us)
http://img519.imageshack.us/img519/cubebeforeezinputlf6.jpg/1/w417.png (http://g.imageshack.us/img519/cubebeforeezinputlf6.jpg/1/)

and after installation of EzInput:

http://img519.imageshack.us/img519/7701/cubeafterezinputay3.jpg (http://imageshack.us)
http://img519.imageshack.us/img519/cubeafterezinputay3.jpg/1/w417.png (http://g.imageshack.us/img519/cubeafterezinputay3.jpg/1/)

DupinBJK

26th September 2008, 10:39 AM

Model: Touch Dual (Niki100)
Language: WWE
Previous keyboards installed: EZinput 1.0 from this link (http://forum.xda-developers.com/showthread.php?t=398173)
Previous SIP changer installed: Not sure
ROM version (6.0/6.1 - HTC/Cooked): 6.0 from HTC website
Description of the issue: Hardware keypad doesn't work since installing Manilla2D
Did this issue exist even before the cab was installed?: Prior to Manilla2D, it was working.

I have tried using mutiple cooked ROMs like LILLY and Mary, but all had the same hardware keypad problem. Any help would be greatly appreciated, as I use my Niki to skype and MSN a lot!

Well, the issue is probably related to the fact that who's repackaging the Manila2D has included his own version of the ezinput suite. There are always conflicts, when mixing configurations, and the projects were initially meant to follow separate roads. Instead, now a 'general' version of EzInput has been included there.

I've asked him to remove it and just restore the old link to this thread, and I'm waiting for an answer, but in the meantime, if you want to install both, you should make an hard reset - recommended by him for the Manila2D, reinstall the Manila2D first and then this EzInput suite, which will overwrite the settings he has used.

I'm sorry for everyone of you who will experiencing this issue in the next days, but I can do nothing more beside politely asking him to remove his version from the Manila2D. There's no need to have more than one team work on the same technology. It's as if I would start the repackaging of my version of Manila2D, too, and include it with the keyboards suite.
It would just be a mess...

Thanks,

BJK

DupinBJK

26th September 2008, 10:42 AM

Which part of the registry should I edit m8? :confused:

Go here (http://forum.xda-developers.com/showthread.php?t=398575), you will find the link for the Disable XT9 cab. Inside, you'll find all the infos you need.

BJK

DupinBJK

26th September 2008, 11:02 AM

please find hereafter the cube before installation of EzInput:

[...]

and after installation of EzInput:

http://img519.imageshack.us/img519/7701/cubeafterezinputay3.jpg (http://imageshack.us)
http://img519.imageshack.us/img519/cubeafterezinputay3.jpg/1/w417.png (http://g.imageshack.us/img519/cubeafterezinputay3.jpg/1/)

Smaller pics next time, thanks.

As you see, it's the helvetica that has replaced the tahoma. And this cannot be caused by the FontLink key, but only by a 'sleeping' bug in the cube.
This means that something in the cube configuration makes him look for a Roman font (not necessarily the Helvetica - beware !), and that normally, not finding it, a default font like Tahoma is instead choosen.

In WindowsCE, like in Windows, is possible to configure and choose a font not just by giving it's name to a system call, but even by choosing special features, like Serif/SansSerif or Roman. It's just a question of flags used in the system call. In this case, the code is either looking for the helvetica font (and then it should be possible to see the name 'helvetica' by looking at the exe(s) or dll(s) of the cube using Cygnus Hex editor or even Notepad), or is asking the system for a font with given features, erroneously asking for a roman font.

In the first case, if the font of the cube can be modified by a registry setting, it will be easy to correct the issue. In the latter, the code of the cube will need to be patched.

I still wonder why you (and that user) are the only ones reporting the issue; someone should go, download an Elf rom, dump it and debug the cube code to fix this issue. I don't have too much time for this, but there are plenty of seniors here using an Elf, if they are reading this post I'd like to ask them to join in and tell us about their experience about this issue.

Thanks,

BJK

DupinBJK

26th September 2008, 07:39 PM

The download for the Compact Keyboard version has been suspended.

Since my post requesting help for an issue reported by one of you, more than twenty downloads of the compact keyboard version have been made, but no one of these new users or of the old ones has even downloaded the video that our fellow user has made to help us understand its issue.
The only answers I've received come from people I've contacted directly via a PM, and who didn't even know about the availability of this download.

Well. I have to tell you that this "get it and run" attitude won't work, in the long run. This is not a shop. You have to contribute.
Of all the users who have downloaded the files, no more than the 6% have completed a report.

So, listen to what we'll do. For the time being, download of the Compact Keyboard version will be suspended.

Now that I know that the issue appears on the 16keys version as well, I'll give to Keypad users a chance to show that they understand how to act.
But if I won't get enough reports, that one will be suspended as well.

All the other users will benefit from the fact that no particular issue has yet been reported, but this, too, will just be a temporary bonus.

I keep getting PMs asking for language add-ons. Well, wake up, this is not a candy shop. My kaiser is working quite good at the moment, I have no need to go on, if you don't need to cooperate. You'll see that by collecting the cabs from those who have downloaded them so far someone will publish something, sooner or later.

A few users have made their homeworks, and they'll receive support using PMs. But if the others won't change their attitude, this is going to be an end.

You've been warned. The choice is yours.

Support request for WWE Nike users

I'm looking for Nike users willing to test an issue reported by one user.
Please post your replies using the Title above.

Issue:
The user reports the hardware mapping on his Nike as working, but is nonetheless experiencing a strange behaviour on his Backspace key.

The issue occurs when using the hardware keyboard.
He says that if the last letter he has typed is still selected, pressing the backspace key will delete it just momentarily, because it will suddenly reappear on the screen.

The only workaround he has found is to unselect the last letter using the arrow keys, and then use the backspace.

I don't have a Nike here to make the tests, and he's quite busy, so we can discuss about this issue no more than once or twice in a day.
He has kindly provided two videos, to help anyone better understand the issue.

I would really appreciate if the users who are testing the keyboard could download those videos and try to reproduce the issue on their phone, to give me more details.

Here's the link (http://www.4shared.com/file/64476035/3447c977/Nike20Keys_Backspace_issue.html)to the videos.

Many thanks in advance,

BJK

Calkulin

26th September 2008, 08:06 PM

You're not following the rules of this thread. I can't give you any kind of support if you don't give us enough details. Please read the first post, and come back with the details we need.

To this, it must be added that:

Users who are going to install the Manila2D should install it first, and reinstall this cab over it.
I won't support issues arising from the misconfiguration caused by the install of the beta of Manila2D.

BJK

The cab was installed after Manilla2D but like I said, with version 1.0(or whatever version is included in Manilla2d), it's working perfect but contribute, here's what you wanted,

Model: Sprint Mogul/Titan
Language: English
Previous keyboards installed: None
Previous SIP changer installed: None
ROM version (6.0/6.1 - HTC/Cooked): Kaos Take 5 rom
Description of the issue: Word suggestion box can't be disabled
Did this issue exist even before the cab was installed?: No, earlier version works perfect

And so you know, I did a hard reset, installed manilla2D and then installed v1.5 and once I noticed the problem, I uninstalled and installed the earlier version and it's been working just fine since,

nothin

26th September 2008, 08:21 PM

i must say, it is very interesting keyboard.

need to know, how to make localized, PLK version...though.
i saw, that PLK kbd is on your todo list, but i need to try for myself, before.

DupinBJK

26th September 2008, 09:28 PM

The cab was installed after Manilla2D but like I said, with version 1.0(or whatever version is included in Manilla2d), it's working perfect but contribute, here's what you wanted,

Model: Sprint Mogul/Titan
Language: English
Previous keyboards installed: None
Previous SIP changer installed: None
ROM version (6.0/6.1 - HTC/Cooked): Kaos Take 5 rom
Description of the issue: Word suggestion box can't be disabled
Did this issue exist even before the cab was installed?: No, earlier version works perfect

There's an important thing that it's still not clear to you: The version of the EzInput technology included in Manila2D and this one are the same.
All the files have been extracted from the same Opal ROM, but to be used on other phones they need to be repackaged.

This is the thread where the official cab is being made. There was a link to this thread, on the thread where you have downloaded the Manila2D, to allow the download of the package I'm preparing, but something has changed, and now a 'general' version, without any compatibility fix, has been included on the Manila2D cab. The development of the version you can find here is at a more advanced step than the one you can find on the Manila2D cab, and a request has been sent to that thread, to remove that version and restore the link.

And so you know, I did a hard reset, installed manilla2D and then installed v1.5 and once I noticed the problem, I uninstalled and installed the earlier version and it's been working just fine since,

The suggestion box you don't want to see is just the box where you can get the dictionary words from Tegic. This means that T9 is enabled.
T9 cannot be enabled on the hardware keyboard on the version included with the Manila2D package you've downloaded, because it doesn' have any compatibility fix.

If you wish to remove it, press Fn+Space, and on the T9 menu choose ABC.
It has been said many times on this thread, and you can find the infos on the download page so, next time, you should read them more carefully.

BJK

DupinBJK

26th September 2008, 09:34 PM

i must say, it is very interesting keyboard.

need to know, how to make localized, PLK version...though.
i saw, that PLK kbd is on your todo list, but i need to try for myself, before.

I'll help you with something that I've written on the download page, which probably you have not noticed:

The main package will still be the five languages version (EN, FR, DE, IT, ES), but for special cases I will prepare other languages - PM me for those, I'll weigh up each case. Remember that a direct post in the thread will mean a NO - we're going to test the 0409 locale now.

Yes, the PLK is on the list. No, the fact that you need to try it for yourself doesn't change anything.

And next time, since the rules are quite clear, you should begin by giving us an installation report. That's the only way to receive support.

BJK

Maxxd01

27th September 2008, 01:02 AM

Model: HTC Touch Dual 16 keys
Language: WWE (updated)
Previous keyboards installed: Keyboard SIP_Diamond EzInput (updated)
Previous SIP changer installed: No
ROM version (6.0/6.1 - HTC/Cooked): Niki Rom Kitchen 1.1-20755(Build 20755.1.4.0)

Description of the issue: backpsace issue (see update below)
Did this issue exist even before the cab was installed? No, this issue has only appear after the instalation.

Well looks like you're right. There's an issue on the .cab for the 16 keys too. Sometimes when I press backspace, the problem is exactly that: I press backspace, and then, instead clear the digit, ok it clear, but also it puts another one. That "another one", I'm not yet able to understand if it's random or no. I'll try to understand next days. This happened in three Rom's I used, and one of them has manilla2D. Sorry my english is not the best to express myself.

EDIT: I detected two bugs connected to the backspace issue: For example, I press letter m (do not forget is a 16 keyboard), and then i do backspace and when I do m again it puts an "n". Other times, I do backpsace to the first letter just no erases nothing. EDIT again: Sometimes I press the second letter (for example "e" of the "3" key, and instead the "e", it puts an 3.

All these things only happens if we use backpsace. And, if we have to do a lot of backpsace, bigger the problem is.

Calkulin

27th September 2008, 01:25 AM

There's an important thing that it's still not clear to you: The version of the EzInput technology included in Manila2D and this one are the same.
All the files have been extracted from the same Opal ROM, but to be used on other phones they need to be repackaged.

This is the thread where the official cab is being made. There was a link to this thread, on the thread where you have downloaded the Manila2D, to allow the download of the package I'm preparing, but something has changed, and now a 'general' version, without any compatibility fix, has been included on the Manila2D cab. The development of the version you can find here is at a more advanced step than the one you can find on the Manila2D cab, and a request has been sent to that thread, to remove that version and restore the link.

The suggestion box you don't want to see is just the box where you can get the dictionary words from Tegic. This means that T9 is enabled.
T9 cannot be enabled on the hardware keyboard on the version included with the Manila2D package you've downloaded, because it doesn' have any compatibility fix.

If you wish to remove it, press Fn+Space, and on the T9 menu choose ABC.
It has been said many times on this thread, and you can find the infos on the download page so, next time, you should read them more carefully.

BJK

I thought they were different builds since the file size was different but I will tell you this, I did a hard reset today to install the new version of Manilla2D and after reading your post I decided to test it again and it did the samething, so my guess is that the version in this thread probably has a corrupt file or a registry key that's changed(I'm too lazy to look :rolleyes: because I can't even disable word suggestion through settings\personal\input and with the other version I can. Actually I don't even see the word suggestions like I do with the one in this thread, they are the regular windows way,

DupinBJK

27th September 2008, 11:40 AM

I thought they were different builds since the file size was different but I will tell you this, I did a hard reset today to install the new version of Manilla2D and after reading your post I decided to test it again and it did the samething, so my guess is that the version in this thread probably has a corrupt file or a registry key that's changed(I'm too lazy to look :rolleyes: because I can't even disable word suggestion through settings\personal\input and with the other version I can. Actually I don't even see the word suggestions like I do with the one in this thread, they are the regular windows way,

Well, you have a curious way to jump to conclusions.
You admit you're too lazy to check, but since you don't even know how to send useful details about how to repro your issue, there must be only a reason for you, to explain the issue: this cab is faulty.

Good point of view. I'm really lucky to get this useful report, since I - and the other 650 users who have downloaded this cab - are so dumb or lazy that we have not even been able to see what you're talking about.

So, please, I know that you are lazy and I wouldn't really like to ask for some details, but everyone here would really like to understand. Would you please be so kind to give us some details about which editing mode are you using, ABC or T9, if you're talking about software or hardware input, and if you are using hardware, if you have tried to use the Fn+Space OR NOT ??

We need detailed reproduction steps - without them your issue cannot receive support.

BJK

DupinBJK

27th September 2008, 12:44 PM

Well looks like you're right. There's an issue on the .cab for the 16 keys too. Sometimes when I press backspace, the problem is exactly that: I press backspace, and then, instead clear the digit, ok it clear, but also it puts another one. That "another one", I'm not yet able to understand if it's random or no. I'll try to understand next days. This happened in three Rom's I used, and one of them has manilla2D. Sorry my english is not the best to express myself.

The tests are going on, in a closed beta group.
We have discovered that it's not related to the ROMs used, because we've been testing the issue on stock roms, thanks to users who have been willing to share their time and even hard reset or reflash.
So, it seems that it's a bug in the Tegic libraries. The fact is that they have changed quite a lot, since the Touch Dual release, but so far HTC has not created a successor to the Dual - all newer phones don't have a keyboard or have a full one.
The registry settings I've bee using are exactly the same found in the Opal Rom, tweaked for the hardware mapping compatibility with the Nike versions, but since the issue happens on both versions (which are using different files), probably it's not even related at all to the hardware mapping.
The tests show that it has something to do with how the Spell check and the Auto Substitution work, and we'll have to found a workaround for it.

EDIT: I detected two bugs connected to the backspace issue: For example, I press letter m (do not forget is a 16 keyboard), and then i do backspace and when I do m again it puts an "n". Other times, I do backpsace to the first letter just no erases nothing. EDIT again: Sometimes I press the second letter (for example "e" of the "3" key, and instead the "e", it puts an 3.

You might think that they are bugs, but indeed they are not. It's just the way the auto prediction works. The letters you see are just the "next in sequence". The issue is still related to the backspace only.

BJK

Noonski

27th September 2008, 05:17 PM

No one is wrong in the above deleted Posts.

Opinions may vary as to how to get a good working version out.

But let's take a step back and breath.

We all want the same thing here.

Yes suspending the Download might be contra productive.
But there is a reason to it and i can only respect that.

If that causes a new thread to arise that will only raise the question of why there are two threads and it becomes Contra productive to unless the two thread holders Exchange information.

It's worth the time to think about it and discuss in private.

nothin

27th September 2008, 05:19 PM

I'll help you with something that I've written on the download page, which probably you have not noticed:

Yes, the PLK is on the list. No, the fact that you need to try it for yourself doesn't change anything.

And next time, since the rules are quite clear, you should begin by giving us an installation report. That's the only way to receive support.

BJK
dude, relax. i won't bother You anymoar, then. i can see what your attitude is, exactly.
i don't care, if you will do this, or not, i just wanted to know HOW to do this, right?
you may not waste your time for answer, good luck.

DupinBJK

27th September 2008, 05:39 PM

dude, relax. i won't bother You anymoar, then. i can see what your attitude is, exactly.
i don't care, if you will do this, or not, i just wanted to know HOW to do this, right?
you may not waste your time for answer, good luck.

No, not exactly enough. You can't get my attitude from that.

You posted on the thread, where I'm wasting a lot of time trying to explain users that a report *must* be filed, successful install or not. Every time, a "me too" syndrome starts.

If you had read the rules, you had known that you should have sent a PM, for personal requests. So, maybe you don't care, ok, but if you check the previous posts, you'll see that I've already talked about a Polish language pack. And even if your language has no support files at all, and I'll have to make all the layouts on my own, this is the FIRST language I've offered, and I've offered it to a Polish user.

People keeps asking me russian, dutch, portuguese, and so on. But it's Polish, the one I'm working on. Browse just a little bit more, and you'll find the post.

So, if you feel offended, just think about the time I'm spending for free. I'm not doing it for you since you've not ever requested it, but you should respect someone else's work - including the rules.

And no, time for giving answers is never wasted time. But the questions have to be made in the right way.

BJK

nothin

27th September 2008, 07:02 PM

damn, i did not read you posts carefully enough..
indeed, rules were clear..
sorry for everything..

jeiyuu

27th September 2008, 07:17 PM

I have had this keyboard installed on my HTC Vogue for a few days now. Installed over a clean hard reset (JD Clean rom), and Manilla 2D. No speed or lag issues, all 3 layouts work beautifully.

Maxxd01

27th September 2008, 08:05 PM

The tests are going on, in a closed beta group.
We have discovered that it's not related to the ROMs used, because we've been testing the issue on stock roms, thanks to users who have been willing to share their time and even hard reset or reflash.
So, it seems that it's a bug in the Tegic libraries. The fact is that they have changed quite a lot, since the Touch Dual release, but so far HTC has not created a successor to the Dual - all newer phones don't have a keyboard or have a full one.
The registry settings I've bee using are exactly the same found in the Opal Rom, tweaked for the hardware mapping compatibility with the Nike versions, but since the issue happens on both versions (which are using different files), probably it's not even related at all to the hardware mapping.
The tests show that it has something to do with how the Spell check and the Auto Substitution work, and we'll have to found a workaround for it.

You might think that they are bugs, but indeed they are not. It's just the way the auto prediction works. The letters you see are just the "next in sequence". The issue is still related to the backspace only.

BJK

But there are a solution?

DupinBJK

27th September 2008, 08:44 PM

I have had this keyboard installed on my HTC Vogue for a few days now. Installed over a clean hard reset (JD Clean rom), and Manilla 2D. No speed or lag issues, all 3 layouts work beautifully.

With the risk of being again called a Napoleon, even if I have really nothing to complain about him, I have to remember you that yes, I'm pleased to know that the cab works for you, but that you've forgot the rules, which clearly tell that reports are needed both for successful installs and issues.

I'll give you an example, to restore the "1st mistake bonus".
From your message, I get that you are using a Vogue. You tell me that you've made an hard reset, for which you deserve another thank-you, but you can't expect me to have detailed infos on all the custom roms around and so I still don't know if your rom already included a prerelease of these keyboards, or even if the Manila2D version you've installed is one of the version that includes a pre-release of this keyboard, too.

You might find all these informations not so relevant, after all, but I've been trying to iron out a specific issue on a Vogue for two weeks, with users that could not always answer to my requests or do an hard reset, just to discover on three devices, two with a Telus official rom and one with a custom one, that the speed issue was no longer experienced after removing some other keyboards or making an hard reset.

Successful reports allow me to better understand issues, when they are reported.

So, please, take a look at the first post, an give me a detailed report.

Thanks,

BJK

DupinBJK

27th September 2008, 08:53 PM

But there are a solution?

I am trying to change registry settings a bit, to see what changes. Obviously it will take time, because the users base of the Nike devices is the one who has sent less reports, and which is actually the less active. You are the only one who has made a public post regarding the request for help of that Nike user. All that has been discovered so far has been discovered only thanks to a bunch of users, who I've had to contact by PM.

If the attitude won't change, it will take time - quite obvious.

This said, we have new official files for the Tegic libraries that I'm going to add to the cabs. We'll have to try all over again, to see if anything changes.

BJK

Mikulec

27th September 2008, 10:14 PM

damn, i did not read you posts carefully enough..
indeed, rules were clear..
sorry for everything..

Respect man, there are only few people who can acknowledge their own mistake.

jeiyuu

28th September 2008, 12:41 AM

I'll give you an example, to restore the "1st mistake bonus".
From your message, I get that you are using a Vogue. You tell me that you've made an hard reset, for which you deserve another thank-you, but you can't expect me to have detailed infos on all the custom roms around and so I still don't know if your rom already included a prerelease of these keyboards, or even if the Manila2D version you've installed is one of the version that includes a pre-release of this keyboard, too.

You might find all these informations not so relevant, after all, but I've been trying to iron out a specific issue on a Vogue for two weeks, with users that could not always answer to my requests or do an hard reset, just to discover on three devices, two with a Telus official rom and one with a custom one, that the speed issue was no longer experienced after removing some other keyboards or making an hard reset.

No problem BJK, I'm only here to help. Here is the info fromt he first page as detailed as I can be:

* Model: HTC Vogue (Sprint)
* Language: English
* Previous keyboards installed: None
* Previous SIP changer installed: None
* ROM version (6.0/6.1 - HTC/Cooked): JD's Clean Hybrid Rom: The Rom is a hybrid between the 19960 and 19965 builds of Windows Mobile 6.1, The XIP CE Base is 19208 Sprint 3.03 Build, Stripped Clean, no office, no games.. (IMO, the best rom to start fresh from.. However, I updated the pagepool to 24mb)
* Description of the issue: None found as of yet.. Will keep you posted.
* Did this issue exist even before the cab was installed?: N/A

DupinBJK

28th September 2008, 01:38 AM

No problem BJK, I'm only here to help. Here is the info fromt he first page as detailed as I can be:

* Model: HTC Vogue (Sprint)
* Language: English
* Previous keyboards installed: None
* Previous SIP changer installed: None
* ROM version (6.0/6.1 - HTC/Cooked): JD's Clean Hybrid Rom: The Rom is a hybrid between the 19960 and 19965 builds of Windows Mobile 6.1, The XIP CE Base is 19208 Sprint 3.03 Build, Stripped Clean, no office, no games.. (IMO, the best rom to start fresh from.. However, I updated the pagepool to 24mb)
* Description of the issue: None found as of yet.. Will keep you posted.
* Did this issue exist even before the cab was installed?: N/A

That's it ! Thanks and welcome on board :)

BJK

Whosdaman

28th September 2008, 03:35 AM

which files do I need for it to work fully for my vogue?

jeiyuu

28th September 2008, 05:09 AM

which files do I need for it to work fully for my vogue?

just install this cab from the first post and give some feedback:
http://www.4shared.com/file/64276539/ed63a4aa/BJK_HTC_EzInput_QVGA_NoKbd_EN_FR_DE_IT_ES-B1.html

namhtc

28th September 2008, 09:11 AM

It works perfectly on my ELF / P3540 with the french full AZERTY layout ... I'm using it with great pleasure for 2 days.

Many thanks to you (as far as I'm concerned you can remove the "beta" status !) :D

PS : my Elf runs with the last custom ROM (Diamond V4b 1.2) from the impressive Seiya and his french Win Mobile Team members.

DupinBJK

28th September 2008, 11:27 AM

just install this cab from the first post and give some feedback:
http://www.4shared.com/file/64276539/ed63a4aa/BJK_HTC_EzInput_QVGA_NoKbd_EN_FR_DE_IT_ES-B1.html

Well, thanks.
If this means you'd like to help me in managing the NoKbd group - it's an unconditional yes :D

BJK

mokoboy

28th September 2008, 01:45 PM

* Model: niki 100 16 keys
* Language: WWE but frnech layout
* Previous keyboards installed: none (or just the basic windows mobile one)
* Previous SIP changer installed: none
* ROM version (6.0/6.1 - HTC/Cooked): 6.1 cooked by myself
* Description of the issue: actually none lol but i don't know what issues i can have
* Did this issue exist even before the cab was installed?:

m1nuss

28th September 2008, 08:25 PM

Hi all,

Can I be part of the beta test?
If yes, could you give me the link with the Niki 16keys, I will give you a feedback as sonn as I can.

Thank you and great job done down here !!

See ya.

DupinBJK

28th September 2008, 09:34 PM

All the previous posts are related to the previous release of this package.
Discussions and reports about Beta1.1 will start after this post.

Thanks for joining in,

BJK

graey

28th September 2008, 09:37 PM

Seems nice to try this, but I'm kinda reluctant as I've just after hours and hours found a working setup for my 16-key niki. Unless someone tells me this one 'just works' and has Dutch language files available...? :D :P

Mikulec

28th September 2008, 10:49 PM

All the previous posts are related to the previous release of this package.
Discussions and reports about Beta1.1 will start after this post.

Thanks for joining in,

BJK

Tada, requested file attached. I hope its the right one.

wmn79

28th September 2008, 11:00 PM

Tada, requested file attached. I hope its the right one.

Thanks, that was a file I was looking for quite a while. Now I can add Czech to the collection of XT9 packages for Niki (http://forum.xda-developers.com/showthread.php?t=395085). Unfortunately those packages aren't compatible with this wonderfull keyboard but only with the standard Touch Dual Keyboard.

Mikulec

28th September 2008, 11:04 PM

Thanks, that was a file I was looking for quite a while. Now I can add Czech to the collection of XT9 packages for Niki (http://forum.xda-developers.com/showthread.php?t=395085)

U r welcome.

DupinBJK

28th September 2008, 11:14 PM

Tada, requested file attached. I hope its the right one.

Wonderful, thanks !

BJK

DupinBJK

28th September 2008, 11:16 PM

Thanks, that was a file I was looking for quite a while. Now I can add Czech to the collection of XT9 packages for Niki (http://forum.xda-developers.com/showthread.php?t=395085)

Now, if only we could put our hands on the Portuguese... :)

BJK

petard

28th September 2008, 11:29 PM

DupinBJK

28th September 2008, 11:35 PM

I searched this thread but its become so long its hard to find an answer. Is it possible to disable T9 for the hardware keyboard on my Kaiser, but keep it functioning for the on screen keyboard? Or what about disabling it in landscape?

If you press Fn+Space, you'll be able to set ABC for the keyboard. Would it be enough for you ?

And, by the way, I'd need a successful install report, as detailed on the download page.

petard

28th September 2008, 11:38 PM

DupinBJK

29th September 2008, 12:10 AM

Fn+Space isn't disabling T9, it does the same thing as pressing space alone.

* Successful reports:
* Model: AT&T Tilt
* Language: English
* Previous keyboards installed: None
* Previous SIP changer installed: None
* ROM version (6.0/6.1 - HTC/Cooked): 6.1 AT&T 3.57.502.2

Is it possible to make it go to ABC by itself if it knows your phone is in landscape mode? It automatically switches to the keyboard you had set in that orientation (i have phone pad in portrait and full keyboard in landscape and it knows to switch between those)

The question is: which cab have you downloaded ? You should have choosen the Fullkbd one, the same that's on my Kaiser right now.

When I open the hardware keyboard and I start to type in Notes, the prediction box appears because t9 is now enabled by default. But if I press Fn+Space a T9 menu appears, and I can choose between T9 or ABC. If I choose ABC, the prediction box won't appear again, and the phone will remember this setting.

Could you try once more ?

randomelements

29th September 2008, 12:12 AM

Model: Nike 200 16 Keys
Language: EN
Previous keyboards installed: beta 1 (uninstalled prior to installing new build)
Previous SIP changer installed: none
ROM version (6.0/6.1 - HTC/Cooked): 6.0 T-Mobile stock ROM
Description of the issue: letter reappearing after backspace
Did this issue exist even before the cab was installed?: no
Detailed steps to reproduce the issue ?: when using abc mode (not xT9) a character will reappear after being deleted by backspace if deleted before the character selection has been completed

Just wanted to let you know that this still exists in 1.1 - don't know if you'd had the chance to look at it.

DupinBJK

29th September 2008, 12:21 AM

Just wanted to let you know that this still exists in 1.1 - don't know if you'd had the chance to look at it.

How could I ? You helped me to test it... :)
Anyway thanks, it shows that the new Tegic libraries haven't changed so much the whole affair. We'll have to tweak some values in the registry, and I guess you are eager to try... :D

BJK

randomelements

29th September 2008, 12:25 AM

I guess you are eager to try...

I am yours to command ;)

darth maximus

29th September 2008, 02:19 AM

All the previous posts are related to the previous release of this package.
Discussions and reports about Beta1.1 will start after this post.

Thanks for joining in,

BJK

Hi BJK, any release notes for 9/28 version?

Tried the previous with my WM device:
HTC Kaiser
English
No Kb
No SIP Changer
Garmin 4.2 Manila ROM WM6.1
working great for me.

Do you recommend existing users of beta 1 to install 1.1 over 1? downloading the new one anyway.

petard

29th September 2008, 02:52 AM

The question is: which cab have you downloaded ? You should have choosen the Fullkbd one, the same that's on my Kaiser right now.

When I open the hardware keyboard and I start to type in Notes, the prediction box appears because t9 is now enabled by default. But if I press Fn+Space a T9 menu appears, and I can choose between T9 or ABC. If I choose ABC, the prediction box won't appear again, and the phone will remember this setting.

Could you try once more ?

I downloaded the full keyboard beta 1.1. I have to open the keyboard up and toggle it to ABC for the T9 box to not come up. Fn+Space is like just pressing space. Having the T9 box makes it really lagy when typing.

It seems that it also knows to switch to ABC automatically in certain circumstances, like when you have to choose a file in the Notes program to load. Maybe there is some way to make it always set to ABC if its in landscape?

mbarvian

29th September 2008, 03:16 AM

EDIT:

disregard

WildSioux

29th September 2008, 04:18 AM

Hi, i just found this keyboard, it is awesome. Thanks for this. Here is my report...

Model: Srint Mogul PPC-6800
Language: English
Previous keyboards installed: Resco Keyboard Pro (installed), and PocketCM keyboard (uninstalled).
Previous SIP changer installed: sipchange (uninstalled before)
ROM version: Stock Sprint HTC WM 6.1

Issues:
In landscape with hardware KB, the software KB pops up now. It even knows to switch it to full QWERTY though.
Did this issue exist even before the cab was installed?: No, the SIP did not popup in landscape.
Detailed steps to reproduce the issue ?: Just slide hardware KB out. It will popup.

Also, T9 popup with hardware key input. Cool feature, kind of sluggish though.

DupinBJK

29th September 2008, 12:00 PM

I don't know about you guys, but I just dumped the opal rom and whipped this up in a few minutes:

http://www.4shared.com/file/64863343...ard_Suite.html

works 100% on my kaiser, with the keyboard and everything

Well, it's just a basic cab, with all the files of the latest Opal rom and the settings for phones without keyboards.

But since it doesn't have the fixes on which I've been working since the release of the pre-release rom, installing it would just be contra-productive.
If you'd like to contribute, it would be better to start with a report, first, and then with something more useful than that.

Thanks,

BJK

DupinBJK

29th September 2008, 12:06 PM

Issues:
In landscape with hardware KB, the software KB pops up now. It even knows to switch it to full QWERTY though.
Did this issue exist even before the cab was installed?: No, the SIP did not popup in landscape.

Known issue, and not related to the keyboard. Wait for the soft keyboard to appear, don't close it but start typing with the hardware keyboard. The soft keyboard will disappear and next time it will remember your choice.

Also, T9 popup with hardware key input. Cool feature, kind of sluggish though.

On my phone and on that of several other users who have not installed any other keyboard, is not sluggish at all. The difference is that you still have another keyboard installed, we can't be sure it's the one to blame, but you might try.

If you wish to remove the T9, you can press Fn+Space and choose ABC. Next time, the HW keyboard will remember your choice.

DupinBJK

29th September 2008, 12:11 PM

Hi BJK, any release notes for 9/28 version?

Tried the previous with my WM device:
HTC Kaiser
English
No Kb
No SIP Changer
Garmin 4.2 Manila ROM WM6.1
working great for me.

Do you recommend existing users of beta 1 to install 1.1 over 1? downloading the new one anyway.

The new Beta1.1 has just the new files from Tegic which have been extracted from the latest official rom. It would be useful to test it to see if there are regression bugs (you know when someone fix one thing and then a new problem appear and an old one comes out once again ? :))

Anyway, good question, I'll update the first page with the info as soon as possible.

Thanks,

BJK

DupinBJK

29th September 2008, 12:27 PM

I have to open the keyboard up and toggle it to ABC for the T9 box to not come up.
Fn+Space is like just pressing space.

Well, I don't understand. You say that you have to toggle it to ABC for the T9 box to not come up. But how you can do that, if then you add that Fn+Space is not working ?

Having the T9 box makes it really lagy when typing.

I see that you don't have other keyboards installed, so it should not be as slow as you say. On Kaisers with official or cooked roms, you are the first to report a speed issue.

It seems that it also knows to switch to ABC automatically in certain circumstances, like when you have to choose a file in the Notes program to load. Maybe there is some way to make it always set to ABC if its in landscape?

T9 is available only in some contexts. If you have an open notes file or Excel or Word, for example. And in those cases, you have to choose the ABC/T9 button on the software keyboard to have it remember your choice for the soft keyboard, and using Fn+Space - which you say that doesn't work - for the hardware keyboard. So, what you need is there, but we have to understand why the T9/ABC menu doesn't appear on your phone.

Is there any other AT/T Kaiser user who could contribute and give us an install report, to compare ?

Thanks !

BJK