Related
I do a lot of texting , and the tiny little keyboard just aint as easy to use with my fingers with one hand.
My Artemis didnt have a Keypad , or T-9 input keypad, only had the keyboard, block recognizer, transcriber, & letter recognizer.
My old S200/Jamin had the Keypad dialer , made texting so much easier.
Anyone know where I can located a cab file for T-9 input??
Thanks in advance
Just copy over the cab file in your my documents folder and Launch, you should reboot the Artemis.
This one is international, so with different languages on board.
Greetings
Anyone who have the Norwegian langugae for T9 with PhonePad?
smilys said:
Anyone who have the Norwegian langugae for T9 with PhonePad?
Click to expand...
Click to collapse
Hei! Hvis det er det samme som på S100 kan jeg skaffe det, har en liggende å slenge...
In english: If it is the same dll file that was uesed in the Qtek S100 PhonePad, then I can provide it?
mvh
PK
Kjempeflott om jeg få teste om det fungerer på P3300.
Great
OK!
Norwegian DLL ripped from S100...
PK
Anyone who can help me to get the norwegian file into the program?
Hi Guy,
I have downloaded the file .ab and followed the instructions, but I do not find nobody icon in the device. someone can help me? thanks
German language does not work. I can select it, but when writing SMS it recognizes/proposes only English words. Any solution for this?
regards
Zonk76
Try a soft reset after choosing GERMAN language.
After that, my Phonepad writes T9 in german.
paalkr said:
OK!
Norwegian DLL rippet form S100...
PK
Click to expand...
Click to collapse
Where do I copy this dll ?? I dont have any map called dictionary.
My P3300 doesnt have transcriber, I only have keyboard. And now I've got phone pad.
How do I install transcriber??
Phone Pad WWE version
I have altered the cab and removed all the languages except for english leading to a smaller install - saving you 0.6 Mb
Does anyone else find that the Phonepad locks up sometimes (possibly due to lack of memory), leading to the inability to change SIPs, and the necessity to perform a soft-reset?
CJBS said:
Does anyone else find that the Phonepad locks up sometimes (possibly due to lack of memory), leading to the inability to change SIPs, and the necessity to perform a soft-reset?
Click to expand...
Click to collapse
Not on my wizard or artemis - what device are you referring to?
meschle said:
Not on my wizard or artemis - what device are you referring to?
Click to expand...
Click to collapse
I'm referring to my Blue Angel, but it's the Phonepad taken from the O2 Mini (it may not be the version that's been included with this post if it's a newer one for a WM5 device...).
I'm wondering how memory works for SIP input anyway, because sometimes when I have heaps of free memory, and I use PenPower, it won't change to another SIP (eg. Null Keyboard, which doens't use much memory). Is SIP memory specially allocated?
CJBS said:
I'm referring to my Blue Angel, but it's the Phonepad taken from the O2 Mini (it may not be the version that's been included with this post if it's a newer one for a WM5 device...).
I'm wondering how memory works for SIP input anyway, because sometimes when I have heaps of free memory, and I use PenPower, it won't change to another SIP (eg. Null Keyboard, which doens't use much memory). Is SIP memory specially allocated?
Click to expand...
Click to collapse
The version posted is 1.0 (Build 22364)
Maybe its your null keyboard thats causing the problems - i recall when i used it - it was a bit glitchy.
It's definitely not the Null Keyboard, which I've never had a problem with, as the problems occurred even before I installed the Null Keyboard.
The version I'm referring to is also 1.0, but build 18526. (I don't know why they don't increase the version number like every other software vendor).
I'll try the version posted, and see whether I continue to experience problems (that is if it works on PPC2003....)
Works on PPC 2003SE
Well.... so far so good. At least it works on PPC2003SE - many things these days seem only to work on WM5! Thanks for making this available.
Wrote too soon! It's already locked up on me. Managed to lock the whole device this time, though, rather than just the SIP. I had to do a soft reset. (I'm wondering whether it's a combination of using PenPower and the PhonePad together).
Anyone know where in the Windows Mobile 5 filestructure T9NorwegianLdb.dll resides?
The Phone Pad - International.CAB.zip seem to work fine on the HTC P-3300.
Just point and hold on the small up arrow on the right side of the keyboard icon when you write an SMS to choose it.
Norwegian is not included in the file posted in this thread however.
I guess we need to install the T9NorwegianLdb.dll for that. Anyone know where to copy it? I am unable to find the phone pad directory in WM5.
i have a cingular 8525 and i installed tnt rom but now the special characters of the hardware keybord are missplased. for example ! should be under letter w but when i press the dot and after the letter w i get @ and some other characters are missplased. does anyone have a solution? i installed something called, 8525 keyboard fix but nothing happend.. thank you
I'm going to answer your Q kinda fast, just don't tell anyone, guys around here don't like answering questions that can be easily found using google.
To the point, You can edit your registry and change it. But the easiest way is installing Schaps Advanced Config. and changing your Keybd. Layout to Cingular/AT&T (or something like that, it's the last option in the list). Current V. of Advanced Config. can be found under the Development subforum.
Good Luck.
thank you very much!
INTRO
I've started this thread to port the EzInput Keyboard to QVGA resolution. The keyboard is now fully functional yet still has a couple of small glitches to be fixed in portrait mode.
I am doing all the testing on my elfin, so I cannot assure that it will work on other devices so you'll have to test it yourselves!
You can download it here:
http://www.sendspace.com/file/uxi3be
THANKS
I must thank
DupinBJK:
http://forum.xda-developers.com/showthread.php?t=486227
nikoan89:
http://forum.xda-developers.com/showthread.php?t=489032
and
Conflipper
for their hard work on the VGA port, since I have mixed parts of their ports to get this QVGA version working.
KNOWN BUGS
XT9 is not currently working: the keyboard seems to get the coordinates (size and position) of the VGA keys. E.g.: if you press "q", "a" or "w" the keyboard will write "q" on the screen, since the three letters are in the area of the "q" key in a VGA screen (double size).
Any help on this matter would be really appreciated!!!
XT9 UPDATE 05/01/2009:
I´ve managed to get XT9 working by replacing the xT9ime.dll of the EzInput 2 with the EzInput 1.5 dll supplied with the ROM I am using. The problem now is that I cannot change XT9 mode back to normal mode .
Anyway I encourage you to test this and see if we can get a solution to the XT9 issues.
To test it, just go to the windows directory, rename eT9ime.dll to something else (e.g. eT9ime.dll.OLD) and reset your device (this should restore the dll supplied with your ROM).
I´m waiting for your comments!!!!
VIBRATION/XT9 UPDATE 05/13/2009:
I managed to get vibration to work a couple of weeks ago, but I wanted to fix the T9 mode before releasing a new version.
I´ve been working on T9 and have not been able to find where the code responsible for calculating the key pressed (based on the coordinates) is.
OPTION A: If anyone is able to find such place in the code or just point me in the right direction, I´ll find the time to patch et9Ime.dll so that QVGA users can enjoy T9 in this keyboard.
OPTION B: Another possible option would be to patch the et9Ime.dll from ezinput 1.5, but the mappings of some important keys seem to be different (XT9/ABC switch for example), and also different registry keys need to be updated so that everything works as it should.
Sorry for the lack of feedback, but I need more time for fixing these issues since this is the first time I am dealing with SIP/IME/IMM and stuff and I´ve found it a little bit more complex than I thought it would be.
HOWTO
Additionally, I'm planning on writing a very simple "howto" to explain people what they can do to adjust/fix/change the layout of the keyboard.
PS: I cannot post any screenshot now, so if anyone of you can upload one I'd be grateful.
problem on XT9 mode, maybe is the key mapping, i dunno that
for example type q,w,a,s the result is --> qqqq
type e,r,d ---> www
thanks for your hard working
T9 issue
You're right (i did not test the XT9 )
I'll have a look at it.
Thanks
Nice
Just 2 questions :
- vibrate when keys are pressed : Don t work normal maybe ...
- Is there a way to change language to french? i see 40C file ...
ty
looks great, good to finally have EZInput for QVGA.
major bug I noticed it messes up the keyboard mapping..for example Caps does not function, nor does the light, just flickers on then off when caps is hit, I believe to turn caps on and off (at least for me) I would have to use function, which also works for function (if that makes sense) lol
also the function keys got incorrectly mapped, I will try the tilt keyboard fix, hopefully that will work, and you can post that Cab.
Minor Issue: no SIP image to open the keyboard on the phone. its a black square, hit the square to active SIP. Would be nice to get a cool new icon though ;P
other then that, I will continue to test this, because the spacing between the keys and the skin is very nice
Thanks for your hard work and the post
I installed this new version and the only major thing I see compared to all the rest of the one you have posted is that the SIP Icon for the Keyboard that shows between the softkeys is missing, if you press the empty space the Keyboard still pops up and is functional but the icon is gone.
thanks man. Work great
So I don't have the phone keypad...is this just a problem with me or does anyone else have this problem?
XT9 is off, but that's fine cause I don't find a need for xt9 on a full keyboard anyways. Though like I said in the other thread I wish there was compact qwerty, or at least I could have the compact qwerty from my other keyboard as well.
Thanks a lot! Im at school now, but as soon as I get home, I'll install this on my phone.
- Thanks, your job is really appreciated.
Great !!!
I've been waiting for this for sometime now and just say thanks for the Qvga version Just wondering if anyone is working on the xt9 bug, i have gotten accustom to using that but if not no worries still a great keyboard !!!
Well, this full qwerty is a huge improvement over the EZ-Input one. I installed the keyboard and used the full qwerty without any problems. HOWEVER, does the Compact QWERTY mode not work with this? Thanks.
Thank you man, you are awesome !
I don't have any problems with it, except the reported bug of the SIP Icon.
But the keyboard on my Elf is a bit slow without O/C. (WM 6.5)
I love this keyboard !
XT9 bug
I've been looking at the XML files, the kdb files and the ldb files and I still cannot figure out the place where the XT9 keys size/position (x,y,h,w) is defined.
Does anyone know whether it's hardcoded in a PE module or it can be configured anywhere?
BTW, I'm afraid Compact QWERTY is not possible for the time being...
Sorry if I'm repeating. If I switch to numeric and press a key and then go back to ABC then all the keys are screwed up and when I press them I get the wrong keys. Do others have the same problem?
littld, i'm not experiencing that behaviour, sorry
asak0 said:
I've been looking at the XML files, the kdb files and the ldb files and I still cannot figure out the place where the XT9 keys size/position (x,y,h,w) is defined.
Does anyone know whether it's hardcoded in a PE module or it can be configured anywhere?
BTW, I'm afraid Compact QWERTY is not possible for the time being...
Click to expand...
Click to collapse
I have been trying to find this out too, I have looked everywhere and can't find the positions for XT9.
Side note, on all 3 previous versions you could use XT9 in ABC and it worked perfectly, but in the new version it just types normally in ABC and XT9 is still broke.
ems275 said:
I have been trying to find this out too, I have looked everywhere and can't find the positions for XT9.
Side note, on all 3 previous versions you could use XT9 in ABC and it worked perfectly, but in the new version it just types normally in ABC and XT9 is still broke.
Click to expand...
Click to collapse
You mean in the previous versions I posted in the QVGA Rhodium Development thread?
asak0 said:
You mean in the previous versions I posted in the QVGA Rhodium Development thread?
Click to expand...
Click to collapse
Yes, all 3 you posted in that thread. If set to XT9 all key mapping was off as I had posted in that thread and others. But ABC worked as XT9 without a problem. It was weird. But I am running the last posted version which I downloaded from sendspace and it works as described above. When I installed the one when you opened this thread also from sendspace XT9 key mapping is still the same, totally off and ABC just functions as it should, regular typing with no text prediction.
Hope that makes sense?
ems275 said:
Yes, all 3 you posted in that thread. If set to XT9 all key mapping was off as I had posted in that thread and others. But ABC worked as XT9 without a problem. It was weird. But I am running the last posted version which I downloaded from sendspace and it works as described above. When I installed the one when you opened this thread also from sendspace XT9 key mapping is still the same, totally off and ABC just functions as it should, regular typing with no text prediction.
Hope that makes sense?
Click to expand...
Click to collapse
Not really...
Anyway I'll play around a bit with the different modules to see what I can get.
I don't have the Touch Pro 2 yet but I am trying to help someone out to fix his issue.
Basically his problem is the suggested word feature doesn't work as well as the Original Touch Pro.
Here is his issue. If anybody could help I would greatly appreciate it.
The correct word "também" is correctly suggested if I type "tamb". So far, so good (although on Touch Pro I could type "tambem" and he would suggest "também" also). The problem is with small words like "olá", "não", "é", "há", "ás", etc...
The T9 only starts suggesting words after the third letter.
Does anyone know how to make the T9 start suggesting after the first typed letter? It would make things better, but it would not solve the problem. There are many words that are single lettered: "é", "à", "á", etc..
Click to expand...
Click to collapse
Maybe a registry setting? I don't have the TP2 so I am not able to browse the registry and find it but I figured you guys would be the best help for this issue. Thanks in advance.
Try this...
Dont know if its what you are after, but might be
http://forum.xda-developers.com/showthread.php?t=534126
hope this helps
I think most t9 starts after the third word because just by typing one letter, there are thousands of words that it can be. So when more letters are typed, it narrows down the selection in the dictionary. The only words that might show up quicker is if the TP2 actually stores newly added words into the dictionary.
dfootball56 said:
I don't have the Touch Pro 2 yet but I am trying to help someone out to fix his issue.
Basically his problem is the suggested word feature doesn't work as well as the Original Touch Pro.
Here is his issue. If anybody could help I would greatly appreciate it.
Maybe a registry setting? I don't have the TP2 so I am not able to browse the registry and find it but I figured you guys would be the best help for this issue. Thanks in advance.
Click to expand...
Click to collapse
Hi. I'm the one who wrote the quoted message
Thanks dfootball56!
Let me just add some more info: what madjsp wrote is indeed true. However, on Touch Pro, this never happened... If I typed "esta", the XT9 on Touch Pro would suggest "está", "esta", "estámos", etc... On TP2, "está" only is suggested if I type "est".
This is, if I type the full accented word (without the accent) it does not suggests the correctly accented word...
Hope I'm not being too much confusing...
Thanks for any help!
you've been clear enough! same problem here, very very annoying since in italian accented letters are very common too.. no solutions / hacks / tricks??
that would be great! thaks a lot!
Hi. I'm the one who wrote the quoted message
Thanks dfootball56!
Let me just add some more info: what madjsp wrote is indeed true. However, on Touch Pro, this never happened... If I typed "esta", the XT9 on Touch Pro would suggest "está", "esta", "estámos", etc... On TP2, "está" only is suggested if I type "est".
This is, if I type the full accented word (without the accent) it does not suggests the correctly accented word...
Hope I'm not being too much confusing...
Thanks for any help!
Click to expand...
Click to collapse
Hey man. Figured these guys on here were the best resource of new hacks and tweaks. I'm sure someone will get bored and try to figure something out...haha If I had one now I would search the registry for you but it hasn't came out in the U.S yet
Update: I mailed HTC and they understood and acknowledged my problem. Just hope it was worth the "effort"...
I'm quoting all the mails:
Me: (...) already described the problem
HTC:"Hi Nuno,
The T9 dictionary does not include words with special characters. You can add these words manually, and they will be remembered next time you need them. On the onscreen keyboards, tapping and holding on the letter assosciated with the special character will display all the extra characters for that letter, and you can drag and select them.
Best REgads"
Me: "Hi. Thanks for the fast reply. I'm afraid I disagree with you: the T9 does include words with special characters. I've never added words like "está", "também", "já", and they are there. The problem is that even if I add the word "olá" to the diccionary (not needed because it is already there), the T9 will not suggest it because the suggestions only start after the third letter. I type "ola" and it does not suggests me "olá". However, the T9 of the 'old' Touch Pro that I've got does this correctly: I type "estariamos" -the full word - and it suggests me "estaríamos". On the Touch Pro 2, I would have to type "estar" so it could suggest me "estaríamos". Are understanding what the problem is? I hope I'm not being too confuse. Thanks."
HTC:"Hi Nuno,
I understand the issue now, I do not think I can resolve this for you now, I have forwarded details to our developers for investigation and possible resolution. Please monitor our support pages for fixes and updates in teh future, and I will be back in contact once I have further news for you.
Best Regards"
I then closed the "support case". I think there's nothing much I can do...
Nuno, did you recieve any reply from their side?
great job nuno, so basically we have to wait and pray for them to fix it in a rom update or hotfix... wtf
fadimck said:
Nuno, did you recieve any reply from their side?
Click to expand...
Click to collapse
Yes, I did... you can see what they told me on my previous post.
Unfortunately we just have to wait for a hotfix...
at least they said they will do this hotfix.. it's a good start, now let's hope it doesn'take ages!
Today I found that the T9 word suggestion work's perfectly if I write the messages in portrait mode (without hard keyboard out) and with the "telephone numeric keys" selected...
This is indeed a bug somewhere on the T9 definitions...
Hi.
I worked out a solution!! ;D ;D ;D
I borrowed a Portuguese Touch Pro, copied the following files from \windows
eT9.HQD.kdb
eT9.SQR.Accented.kdb
et9.sqr.portuguese.kdb
eT9ime.dll
KbdNopAll.dll
and then placed them on the \windows folder of the Touch Pro 2
Reboot and DONE!
Good "old" XT9 with the correctly suggested words!!
I've placed the files here, in case someone needs it:
http://www.nunosilva.com.pt/nuno/outras/T9TouchPro.rar
Mind that this is for the Portuguese TP2; I don't know if there are differences from TP2 from other countries.
Thank you all for your help
Well... not that solved after all...
I found out that the Touch Pro has specific keys for these marks:
/ ? + = - _
Meaning: on the Touch Pro 2, I can't write them with the hard keyboard
I also found out that it is only necessary to replace the eT9ime.dll file; all the other are pointless as far as I figured out.
So, to put it back in it's original form, just re-replace the eT9ime.dll file.
Here is the link, in case someone forgot to backup the files before replace them with the files from the Touch Pro:
http://www.nunosilva.com.pt/nuno/outras/T9TouchPro2.rar
Because it is an .dll file I don't really know if it is editable in any way... is someone knows how to do it, please do tell me..
Thanks.
This thread will hopefully become a communal Work In Progress. I received my TP2 yesterday and have gotten to work right away on installing Japanese IME on my phone. Anyone who can offer useful tips or any help at all, I greatly appreciate it.
12:11 PM 8/21/2009
So far my first attempts have not proved fruitful. As a first step, I installed Olinex's HSPL. After that, I began installing the cabs from Zgembo's Touch Pro/Diamond Thread. I first installed the Let's Japan WM6.1 R07. After a soft reset, it seemed to be installed ok. I could see a few Chinese characters in the predictive text box above the SIP keyboard (although, there were some boxes too). Second step, I attempted to install the Japanese Advanced IME from the same thread. I should note, it clearly states that it's designed for VGA devices, and TP2 is WVGA. I went ahead with the install anyway. And that's when the trouble began. After soft reset, the HTC splash screen comes up, but after that- black. Nothing. No amount of button pressing or anything short of a hard reset resolved it. And that's as as far as I've gotten.
I'm going to do some more reading and then try again. If anyone knows a better way to go, let me know. Hopefully with more input this can become useful to other people living in Japan that require Japanese capabilities on their Touch Pro 2.
*****UPDATE*****
first off, my apologies, i realize that my solution to the problem wasn't clearly stated in my other posts below.
to get Japanese input/output working on your Rhodium/Touch Pro 2, do the following:
install Asukal LetsJapan6 and restart
install Asukal's IME_31J_FULL, but do not restart
install Asukal's Enable_IME and restart
that simple. romaji, kana, kanji, kensaku, tegaki (the handwriting recognition inputs) will all work. XT9/Predictive will be broken. And you will need to switch between かな カナ or 英数 on the soft keyboard to get the hardware keyboard to type in the language you want.
Try CE-Star Suite Chinese/Japanese enabler
http://www.mobem.com/products/cestarwm5.php
Mesquire said:
Try CE-Star Suite Chinese/Japanese enabler
http://www.mobem.com/products/cestarwm5.php
Click to expand...
Click to collapse
have you tried that on your TP2? what results did you get?
for anyone else trying Zgembo's cabs from the Touch Pro/Diamond thread, can you let me know your results? After installing LetsJapan, for my SIP icon, I'm getting an A4. In the dropdown menu where you select which keyboard to use, it has A4 智能输入 (i can't read those characters at all). anyone know the deal with this A4 menu?
No problem running CE-Star on my TP2 and the interface is in English, but I don't use or need Japanese input so I cannot comment on that.
yeh, I need Japanese input. and the A4 Chinese pre-installed in my ROM seems to conflict with it somewhat.
almost there... i hope
Ok, so here's the situation so far. After nearly 10 resets, I seem to be *almost* there.
I installed in the following order:
1. LetsJapanWM61r07.cab, then reset
2. KeyTouchJapIMEr07.cab
3. Enable_IME_2.zip, then reset
4. Softbank MMS
So far, I am able to send and receive with no problem. however, I'm still not able to type using any katakana, hiragana, nor kanji. even when i use the kensaku, it will recognize the characters, but when i choose the character, nothing shows up. Japanese input seems to be completely broken.
Is anyone on here able to type in Japanese on their device? if so, what program are you using? the relevant programs I have installed are:
Zgembo JapaneseIME
Asukal Enable_IME
Zgembo Lets Japan WM6.1
Zgembo Lets Japan WM6.1 Mincho
Zgembo Softbank MMS
The soft input keyboards available to me are:
A4 智能输入
Block Recognizer
Kana*
Kensaku*
Keyboard
KeyTouch*
Letter Recognizer
Romaji*
Tegaki*
Touch Input
Transcriber
* for the Japanese characters that don't show up when I type
CE-Star has some Japanese support (I need it to show Japanese song names, but not all words are displayed correctly) and Romaji input but since I don't know any Japanese I can't test the accuracy of inputs for you, but their Romaji input appears to work.
@mesquire: yeah, CE Star doesn't work for me. i think i'll need a bit of a more 'homegrown' solution.
Getting Japanese Input running
well, i finally managed to enable Japanese input. previously, i had been attempting to install Zgembo's KeyTouchJapIMEr07.cab. VISUALLY all the keyboards were there, but only a limited few functioned. i did a lot of trial-and-error installations to figure out what effect each cab file had.
after installing the softbank connection I began installing the IME piece by piece. I should mention that the ZTA4 (Chinese) IME is preinstalled in this stock ROM. the keyboards included in this IME are Touch Input, A4 智能输入, Block Recognizer, Keyboard, Letter Recognizer, Transcriber. i'll paste some of my edited installation/setup notes below. if you don't want to wade through that muck, just skip down to the Highlights section below it:
17. Install Keytouch (Zgembo JapaneseIME; 17.5mb) -> DON'T RESTART
18. Install Enable_IME_HTC_HD
19. Check Input (5 new: Kana, Kensaku, KeyTouch, Romaji, Tegaki)
20. Restart
21. Check input, Regional Settings (still no Japan)
22. test input
QWERTY Touch keyboard is fine (XT9 doesn't work)
Keypad only types numbers
small keyboard is fine
romaji broken (no kana)
kana broken (blocks)
KeyTouch broken (blocks)
Tegaki is fine
kensaku is fine
A4 is fine
block recognizer is fine (but sucks)
Letter Recognizer is fine
Transcriber is fine23. Install CEStar Japan (2mb); no change in SIP functionality; restart; no change in SIP functionality
24. Install Softbank MMS (5.2mb)
25. Install Asukal Lets Japan6 (4.25mb); restart; Regional Setting changed to Japan; Mapple functional; Kana is default keyboard; A4 智能输入 now reads A4 智能▯入; no change in SIP functionality
26. Install 2_IME_31J_FULL.cab (Ask IME 31J) (7.8mb); new input: Roma Ji, Kana, TagakiKensaku, restart, no change in SIP functionality
27. Install LetsJapan WM61r07 (Zgembo Lets Japan WM6.1; 4.25mb); restart
28. Install Enable_IME_HTC_HD again
29. Install 2_IME_31J_FULL.cab again; restart; No change
30. Install Enable IME2; restartl No change
31. Remove Asukal LetsJapan6
32. Remove Zgembo's LetsJapan6 (but didn't remove properly; still in Programs list); A4 is now A4▯▯▯▯; restart; problem occurred with cprog.exe
33. Install LetsJapan WM61r07 again (Zgembo Lets Japan WM6.1; 4.25mb); restart; problem occurred with cprog.exe; no regional setting change
34. Remove Asukal Enable IME; no change
HARD Reset
Highlights
if you have no desire to read through all that and decipher it, it basically says this:
ZTA4 natively allows you to view Japanese (Japanese characters are Chinese characters afterall, but it allows you to see Kanji and Kana)
ZTA4 does not allow you to write in Japanese nor display Japanese in software designed for Japanese OS.
LetsJapan6 (both Asukal's original and Zgembo's derivative) adds Japanese to the 'Regional Settings'. it also installs the font used for Japanese input/output. Of the two, only Asukal's LetsJapan allows software designed for Japanese OS to display Japanese properly (ie. Pocket Mapple). However, neither LetsJapan installs any keyboards (only fonts), so you still cannot write in Japanese yet.
LetsJapan6 (both Asukal's original and Zgembo's derivative) both appear to conflict with ZTA4. I don't know of any change in functionality, but A4 智能输入 in the list of keyboards will now read A4 智能▯入 (if anyone knows of a way for me to completely remove ZTA4, please share).
Zgembo's KeyTouch/JapaneseIME adds 5 new keyboards to your available inputs: Kana, Kensaku, KeyTouch, Romaji, Tegaki; of these 5 keyboards, only 2 work- Kensaku and Tegaki
Zgembo's KeyTouch/JapaneseIME doesn't allow Japanese input; it also breaks XT9 functionality in the English keyboards; Visually it's lovely and everything is there, but it does not function on this particular stock ROM. I should also warn: if you do install this IME, DO NOT RESTART immediately after installing. Immediately after installing, install one of Asukal's Enable_IME files (there's one from long ago and one he recently made for the Touch HD... although, i think they are exactly the same). If you do not install the Enable_IME before you restart your device, after your device boots up and the splash screen fades, you'll be stuck on a black screen, at which point, your only option is to Hard Reset.
Asukal's IME_31J_FULL is the alternative to Zgembo's KeyTouch/JapaneseIME. although Zgembo's is prettier, it unfortunately doesn't work on TP2 (if someone else has had a different experience, please share). Asukal's IME is rudimentary, no fancy stuff like a Japanese Touch Keypad or predictive text, but it allows you to write in Japanese.
Asukal's IME_31J_FULL adds 4 new keyboards: Roma Ji, Kana, Tegaki, and TagakiKensaku. All seem to function perfectly fine as touch keyboards. As touch keyboards though, they're not very finger friendly, so you'll be stuck using your stylus to tap. In hardware keyboard mode, at the moment there is no known Fn key combination that allows you to switch between English and Japanese. This must be chosen by first choosing either かな カナ or 英数 on the soft keyboard, then typing with the hardware keyboard. And again, if you do install this IME, DO NOT RESTART immediately after installing Same thing will happen as stated above. Immediately after installing, install one of Asukal's Enable_IME files. If you don't, you'll have lots of fun hard-resetting.
After setting up the IME, it should be relatively safe to install the Arcsoft Softbank program. I've been using that and have no problems sending or receiving SMS and MMS... although, I don't know how to use emoji since i think it was something that is inherent in the Japanese KeyTouch keyboard.
So that's my rundown. Hope it will be useful to others. What I want to do now is find a way to Isolate the Japanese KeyTouch keyboard, get rid of ZTA4, and get XT9 prediction working again on both English and Japanese keypad. I'd really love it if Asukal, Alcibiade, Zgembo, larsucks and the rest of the X01HT gang could get in on this and offer some suggestions. Anyone else who has discovered anything interesting, please don't hesitate to post!!
Ookii.org
You should look at Ookii.org:
http://www.ookii.org/software/japaneseinput/
mschaffer said:
You should look at Ookii.org:
http://www.ookii.org/software/japaneseinput/
Click to expand...
Click to collapse
thanks, i'm familiar with ookii.org. good stuff. i've been using his pocket dictionary for a few years now. but with regards to his japanese input, i don't imagine there will be added functionality over Asukal's IME, but I do imagine there will probably be less. And still, it's old, so the letters will still be tiny, there will be no keypad, and there will be no predictive text.
Did you try BeeGee_Tokyo's CAB for Topaz?
http://forum.xda-developers.com/showthread.php?p=4102158
I tried it on my Rhodium and it works quite well, though it seems to slow the system down. Only thing I found is that I can't use the physical keyboard to input Japanese.
Topaz and Rhodium are quite similar, definitely in terms of screen res and probably software I think.
e60202 said:
Did you try BeeGee_Tokyo's CAB for Topaz?
http://forum.xda-developers.com/showthread.php?p=4102158
I tried it on my Rhodium and it works quite well, though it seems to slow the system down. Only thing I found is that I can't use the physical keyboard to input Japanese.
Topaz and Rhodium are quite similar, definitely in terms of screen res and probably software I think.
Click to expand...
Click to collapse
thanks for the suggestion. i already got Japanese input working now, but i may try that one in a later configuration.
what i'd like to know now is if anyone else has been able to install HTC KeyTouch (the Japanese version from the X05HT) onto their Rhodium. That is the SIP keyboard I would really like to get functioning, as one-handed typing on the Rhodium would be lovely. Also, I think that the emoji are preset in that SIP, so presently, i can't get them working in my Softbank Mail program. anyone have any success with that?
btw e60202, if you follow the method i stated on the previous page, you can have Japanese input both software and hardware keyboard.
Cool...I'll give that a try and let you know if I have any trouble. Thanks.
@shunsai
I want to buy the HTC Touch Pro 2 here in Germany soon. But reading and writing Japanese is very important to me. So, I am glad that you found a solution for my problem.
But I still have some questions.
Could you tell me where I can download Asukal LetsJapan6, Asukal's IME_31J_FULL and Asukal's Enable_IME?
If it won't work the way I hope it will, how can I remove it from my device afterwards?
dkun said:
@shunsai
I want to buy the HTC Touch Pro 2 here in Germany soon. But reading and writing Japanese is very important to me. So, I am glad that you found a solution for my problem.
But I still have some questions.
Could you tell me where I can download Asukal LetsJapan6, Asukal's IME_31J_FULL and Asukal's Enable_IME?
If it won't work the way I hope it will, how can I remove it from my device afterwards?
Click to expand...
Click to collapse
asukal keeps a blog where he also includes his files. this entry he wrote is about the Touch HD, but the files work for the Touch Pro 2 as well. the 1_Enable_IME_HTC_HD.cab included in the zip seems to be the exact same as Enable_IME_2.zip
LetsJapan6 is available here
most of his other files are available here.
if things don't work out, hard reset will become your friend, so make sure to backup all your files and settings before you install just in case.
Thank you very much for the info, Shunsai!
Have you already found a way to change the input method with the hardware keyboard?
Somewhere I read something about pressing the Crtl and Shift at the same time. Does that work on your device?
Having trouble with text
First of all. I want to thanks to you Shunsai and Asukal!
I'm having trouble to input Japanese with Touch pro 2.
Now everything work good except text message.
When I text with Japanese it shows "????????????????".
It shows fine with email and web browser.
Do you have same problem? Or it is just for me?
dkun said:
Thank you very much for the info, Shunsai!
Have you already found a way to change the input method with the hardware keyboard?
Somewhere I read something about pressing the Crtl and Shift at the same time. Does that work on your device?
Click to expand...
Click to collapse
hey dkun, no, i still haven't found a way yet. hopefully someone with more knowledge can suggest something soon.
quickmo said:
First of all. I want to thanks to you Shunsai and Asukal!
I'm having trouble to input Japanese with Touch pro 2.
Now everything work good except text message.
When I text with Japanese it shows "????????????????".
It shows fine with email and web browser.
Do you have same problem? Or it is just for me?
Click to expand...
Click to collapse
no prob. i'm here to help people in the same boat as me if i can, but really i haven't done anything. i'm just benefiting from the fruits of asukal's labor like you. can you tell me more about your device (which ROM/region)? what order did you install the cabs in? was it on fresh install?
i'm still tinkering around trying to get japanese and english input where i want them, but japanese IME seems to be very tempermental in general. so far, its really only worked for me consistently when i installed in the order in the OP.
Have you guys tried this Japanese display and input app?
http://forum.xda-developers.com/showthread.php?t=445550
No need for separate installs - all in one cab, works on many different devices, also with hardware keyboard. Much smoother than LetsJapan or CE-Star IMO.