Any way to switch the IME? - G1 General

I'm on Rogers, and I was wondering if there's any way to switch the new HTC IME with the one included in, say, Cupcake.
I use the phone's actual QWERTY keyboard a lot, but once in a while if I need to type something fast I use the touchscreen.
However, the new IME included isn't like the other, the Prediction settings keep getting in the way of my QWERTY keyboard when it's out, and it's really annoying. I figured if the old IME could still work on this version, why not put it on?
Any ideas?

just turn off prediction
works great for me

That works, but unless you have prediction on..it won't auto-capitalize and auto-punctuate. It's a small fix, but it's really annoying. I'm not sure why it does this, and it will auto-punctuate/capitalize the qwerty keyboard IF the prediction is on, but it won't without it. Baffles me as to why.

Unicornasaurus said:
That works, but unless you have prediction on..it won't auto-capitalize and auto-punctuate. It's a small fix, but it's really annoying. I'm not sure why it does this, and it will auto-punctuate/capitalize the qwerty keyboard IF the prediction is on, but it won't without it. Baffles me as to why.
Click to expand...
Click to collapse
That's exactly my problem! I didn't know how to put it into words, that describes it perfectly though.
The only thing I've found that turns on auto-punctuation/capitalize is when you turn off Touch Input.
I don't know if this is related, but my messages aren't showing up either. I'll see a notification that I have a new text, but when I actually go to messaging/ChompSMS (I've tried both) it doesn't show that the person even sent me anything. :|

I've extracted the Latin IME from JF ADP Cupcake, I tried installing it like I would any other app from my SD card but it's giving me an error saying it just can't install it.
If anyone else would like to take a look and see if they can get it working, the file's attached to this post.
The apk is inside of the zip file.

Rogers Dream isn't rooted is it? If it is, just push the LatinIME.apk into /system/app. Also push libjni_latinime.so into /system/lib

jashsu said:
Rogers Dream isn't rooted is it? If it is, just push the LatinIME.apk into /system/app. Also push libjni_latinime.so into /system/lib
Click to expand...
Click to collapse
It's not, I'm using Cyanogenized Rogers to be specific. I'll try what you said though and let you know how it goes.
Edit: inside /system/app there only is HTC_IME.apk. Dunno what to do about that, should I rename LatinIME to that and try it?
Edit 2: tried installing it renamed as HTC_IME.apk, got a bunch of force closes every other second seems like it might still be missing something :/

Proxin said:
It's not, I'm using Cyanogenized Rogers to be specific. I'll try what you said though and let you know how it goes.
Click to expand...
Click to collapse
If you are using a custom build then you should have already gotten root access...
Edit: inside /system/app there only is HTC_IME.apk. Dunno what to do about that, should I rename LatinIME to that and try it?
Click to expand...
Click to collapse
I'm not sure what you're talking about. Leave HTC_CIME.apk in place and adb push LatinIME.apk (extracted from JF1.51 or wherever) into the system app folder. Then go into the settings and uncheck TouchInput. I'm not sure why you'd want to use LatinIME over HTC's IME though, since LatinIME won't automatically fix typos if you press spacebar, making it a lot slower to use.

I actually found a way to have the on screen HTC_IME keyboard auto correct NOT screw up the hardware keyboard. It is a bit odd, but run with me here...
Leave the Prediction features of the HTC_IME enabled.
Go to the Device Keyboard settings, and DISABLE "Auto-punctuate". It still will auto punctuate, and auto-correct the 's for you, but the on screen suggestions will go a way.
Except, they still seem to show up on occasion, I can not track down what causes it (seems when filling out forms online and such). But for the most part, it stops bothering you.

jashsu said:
If you are using a custom build then you should have already gotten root access...
I'm not sure what you're talking about. Leave HTC_CIME.apk in place and adb push LatinIME.apk (extracted from JF1.51 or wherever) into the system app folder. Then go into the settings and uncheck TouchInput. I'm not sure why you'd want to use LatinIME over HTC's IME though, since LatinIME won't automatically fix typos if you press spacebar, making it a lot slower to use.
Click to expand...
Click to collapse
Wait... so you uncheck Touch Input? I thought that would make it so that you couldn't use either IME, regardless of if the Latin one works.
The problem I've been having with HTC's IME is that the prediction works- all too well. It sets up prediction for when I'm using the hardware keyboard, and I don't need it for that. The prediction chooses words that I don't want to use sometimes -_- and if you turn off prediction, it stops auto-capitalizing and auto-punctuating for the hardware keyboard.
I will try pushing that and disabling the Touch Input.
@daveid: That sounds like a good solution as well, I'll try that first and if it doesn't work I'll try the other one
Edit: That was already disabled on mine and it still didn't work. What are the rest of your Touch Input settings?
Edit 2: Tried pushing the LatinIME and unchecking Touch Input, it didn't work either- when I touched the textbox it didn't give me any on-screen keyboard.

The rest of my Touch Input settings are disabled, only the first two "Prediction" and "Spell correction" under QWERTY.
Under Device Keyboard, I have the first two enabled as well only the "Auto-punctuate" is disabled.

daveid said:
The rest of my Touch Input settings are disabled, only the first two "Prediction" and "Spell correction" under QWERTY.
Under Device Keyboard, I have the first two enabled as well only the "Auto-punctuate" is disabled.
Click to expand...
Click to collapse
Tried that as well... you're on Cyanogenized Rogers?
Try going to Terminal and type
Code:
su
ls /system/app
Which of the following do you see in the files listed, HTC_IME.apk or LatinIME.apk?

I am on the Cyanongen ADP/AOSP 3.4.4 ROM, and I have both HTC_IME.apk and LatinIME.apk installed, I have the Android Keyboard disabled in settings though.

daveid said:
I am on the Cyanongen ADP/AOSP 3.4.4 ROM, and I have both HTC_IME.apk and LatinIME.apk installed, I have the Android Keyboard disabled in settings though.
Click to expand...
Click to collapse
So, when you go to settings>locale & text, what options does it show?
I guess I would need to somehow change my locale & text to show more options (Like enabling the Touch Input of LatinIME - not that specifically, but I remember Cupcake had more options for Touch Input than English and Chinese) because the only enabling I can see for Touch Input is Chinese and English.
I've pretty much run out of ideas of doing this or getting it to work though...

Mine shows Touch Input, Android Keyboard, and Device Keyboard.
When I enter Touch Input settings, I get "Keyboard types", "Keyboard language", and "Text Input".
Going into "Text Input" is where I get the prediction settings.
The Device Keyboard is where I unchecked "Auto-punctuate", which is how I kept the Auto Suggest for the on-screen keyboard, without having it on the hardware keyboard.

daveid said:
Mine shows Touch Input, Android Keyboard, and Device Keyboard.
When I enter Touch Input settings, I get "Keyboard types", "Keyboard language", and "Text Input".
Going into "Text Input" is where I get the prediction settings.
The Device Keyboard is where I unchecked "Auto-punctuate", which is how I kept the Auto Suggest for the on-screen keyboard, without having it on the hardware keyboard.
Click to expand...
Click to collapse
Ah, that's the difference.
Mine doesn't show Android Keyboard.
I have: Touch Input Chinese (unchecked), Touch Input Chinese (settings), Touch Input (checked), Touch Input (settings), Tutorial, and Device Keyboard (settings)
So what I think I mainly am looking for is to somehow get the "Android Keyboard" to show up...

Except that my Android Keyboard is disabled. In your /system/app you must have:
HTC_IME.apk & HTC_CIME.apk (the Chinese option you see) but no LatinIME.apk
So, if you want it to be like mine (for testing purposes it may help). Try some commands like these (assuming you have the sdk installed on your PC, place a copy of LatinIME.apk into your sdk/tools directory).
adb remount
adb pull /system/app/HTC_CIME.apk HTC_CIME.apk (this is to back it up in case you need it for something).
adb shell rm /system/app/HTC_CIME.apk (deletes the Chinese keyboard).
adb push LatinIME.apk /system/app/LatinIME.apk
adb shell reboot
now, when your phone reboots, you should have the same choices I have.

Except that my Android Keyboard is disabled. In your /system/app you must have:
HTC_IME.apk & HTC_CIME.apk (the Chinese option you see) but no LatinIME.apk
So, if you want it to be like mine (for testing purposes it may help). Try some commands like these (assuming you have the sdk installed on your PC, place a copy of LatinIME.apk into your sdk/tools directory).
adb remount
adb pull /system/app/HTC_CIME.apk HTC_CIME.apk (this is to back it up in case you need it for something).
adb shell rm /system/app/HTC_CIME.apk (deletes the Chinese keyboard).
adb push LatinIME.apk /system/app/LatinIME.apk
adb shell reboot
now, when your phone reboots, you should have the same choices I have.

daveid said:
Except that my Android Keyboard is disabled. In your /system/app you must have:
HTC_IME.apk & HTC_CIME.apk (the Chinese option you see) but no LatinIME.apk
So, if you want it to be like mine (for testing purposes it may help). Try some commands like these (assuming you have the sdk installed on your PC, place a copy of LatinIME.apk into your sdk/tools directory).
adb remount
adb pull /system/app/HTC_CIME.apk HTC_CIME.apk (this is to back it up in case you need it for something).
adb shell rm /system/app/HTC_CIME.apk (deletes the Chinese keyboard).
adb push LatinIME.apk /system/app/LatinIME.apk
adb shell reboot
now, when your phone reboots, you should have the same choices I have.
Click to expand...
Click to collapse
That puts the apk there but the phone's settings still do not recognize it as the Android keyboard. It did remove the Touch Input Chinese from locale&text, but I don't see Android keyboard in the choices.

Your rom may be missing some libraries needed for the Android keyboard. But I don't know what those would be. Is there a particular reason you are running the Roger's rom VS the 3.4.4. ADP/AOSP version?

Related

Where does this keyboard come from?

I have the 16 key touch dual.
So on input options, you have the touch keypad, when I select that sometimes this comes out (please see attached)
I like it thought better than the 20 key touch keyboard.
Yeh... Where?
I second this, it works really well but there is no option to bring it up on the dual... it just randomly appears sometimes when you need to input text.
Thirded.
And whats more, why does text input seem to vary on web pages?
I've got some where it defaults to numeric input when it should be alpha numeric (ie. passwords), others where XT9 seems to be off (the subject on mails in facebook).
Its so stupidly all over the place and inconsistent! If I could just get this one to pop up all the time I'd be happy.
Doesn't that keyboard show when there's no text entry field?
And yes, i want it too, why would they disable it for normal usage?
Yeh I have found the keyboard to be all over the place when it comes to deciding if it will give you tx9, abc, 123, etc.... Anyone know a way to set one of the two alphanumerics as a default at least?
ok ive had this appear a few times now but couldnt figure out why, as you have been asking for it i have been playing around and think i know what is causing it. you may not need everything listed below but these are the settings on my device if you play around with them you should be able to narrow it down.
I'm running Toms rom, found here
i have disabled threaded sms by using the second setting here
i have enabled the favourite people button on the htc home screen by deleteing the key here
the only other app i have that may have changed a setting is the HTC home customiser.
After making these changes tick the enable xt9 setting in romsettings app, exit the app, then go back into it and untick the enable t9 setting, after closing romsettings you should have the keyboard shown in the second screen shot
as far as i can see this changes the keyboard in all applications
Thats great! Still albeit of a noob so you lost me somewhere there, is there a way to this on the stock ROM?
short answer is i dont know. try looking for an applcation called rom settings after installing it there is a t9 setting. untick it and closethe application if this makes no dfference you may want to try altering the other settings and then trying again until it works.
kerrance76 said:
short answer is i dont know. try looking for an applcation called rom settings after installing it there is a t9 setting. untick it and closethe application if this makes no dfference you may want to try altering the other settings and then trying again until it works.
Click to expand...
Click to collapse
Ok will try that thanks. On the side, when you untick "T9" does this make "abc" default text entry as well?
I have confirmed that this keyboard layout come out when no text entry is needed.
muzikfreakah said:
On the side, when you untick "T9" does this make "abc" default text entry as well?
Click to expand...
Click to collapse
I wish, this has been a problem since the phones release - theres 7 pages on it here
muzikfreakah said:
I have confirmed that this keyboard layout come out when no text entry is needed.
Click to expand...
Click to collapse
thats the default action anyway, with the changes detailed the keyboard is available when entering text, if you look at the second image you will see that the cursor is actually in the message box, its the black line at the end of the word hello
muzikfreakah said:
I have confirmed that this keyboard layout come out when no text entry is needed.
Click to expand...
Click to collapse
Eh? Maybe I overdosed on the thick pills last night, but that doesn't make any sense? If I click on a password field in IE, sometimes the main phone keypad always seems to default to numeric entry. But clicking in the field itself pops up this lovely keyboard.
It really does make no sense at all. There doesn't appear to be any standard/global keyboard settings.
And this is in v6 of WinMo, you would have thought they would have got the basics right by now, but the darned sent items has the useless option of "order by from" - when all the sent items are sent from the same person.
Its got plenty of potential, but it just seems like lots of separate teams were implementing it, doing their own thing without any centralised discussion/design.
Has anyone managed to get this to work with the standard T-Mobile [UK] ROM ?
any updates on this as well? it would be nice to just get an option for this
I got it to work, rather by chance, but thing is after that, I could switch to back to the touchpad type anymore.
I installed POCKETCM KEYBOARD. After doing that, somehow it locked this keyboard in when I choose touchpad.
Its rather a workaround, but for those who to use it premanently, you can do it
it also shows up at times when you are entering a password
Ouch ! I read to quickly and did'nt see the word "permanently" !
It does the same for me after installing pocketpc keyboard and even after uninstalling it !!!
Did you find a way to get the classic keyboard back ? This one is nice but there are some important keys missing as "." and a key to hide the keyboard !
Thanks
EDIT : The installation of Resco Keyboard got all the original settings back + Resco Keyboard of course.
So if you need to use the famous "hidden HTC keyboard", simply install Resco Keyboard and then Pocketpc keyboard.
You will then have your classic "touch" keyboards replaced by the "hidden keyboard" (+Resco Keyboard installed of course).
But to my mind, Resco keyboard alone is better...

TouchPal wont show after a while

Hi folks
I love this forum and am so glad its here, it seems to be the only place where ppl can get support for the HD right now.
I am using the TouchPal keyboard 3.5. It installed fine and I started using it and configuring it grand etc. But after a while it stops responding.
If I click on the small keyoard icon at the bottom of my screen, no keyboard pops up whatsoever. If I go to settings and change the default keyboard from TouchPal to say - Full Querty and press OK, the change does not take place (If I go back into settings, the keyboard is reset to TouchPal).
So I am left wthout a keyboard and I have to do a full restart of the phone. If I uninstall TouchPal all is well and the keyboard system reverts back to working normally.
Has anyone else expereinced similar ?
Many thanks for any help
gt
iv got version 3.5 aswel, iv had no problems with it
the only problem i have is that, in landscape mode the key sizes dont increase, it appears small, but never the less a great keyboard
Hi xdaman85
Try running Remote Desktop and see if the keyboard behaves there, thats where it dies on me.
gt112 said:
Hi xdaman85
Try running Remote Desktop and see if the keyboard behaves there, thats where it dies on me.
Click to expand...
Click to collapse
just tried that, no problem what so ever
try this
uninstall, soft reset, install, soft reset, then go to settings, inputs, choose touchpal as default keyboard, then press ok, then soft reset
i know thats long but it should do the trick, seems to me as if that it wasnt installed correctly and theres some errors, so try what i said and let me know if it works
OK guys, it seems I am not alone in having prolems with TouchPal on the HD. See this thread on CoolTek's forum.
http://www.cootek.com/forum/forum_posts.asp?TID=742&PN=1
I have tried everything, I have uninstalled the kb, reinstalled it. Last night I completely reinstalled the entire phone (hard reset, wipe, reistall) but TouchPal still stops working after a while.
gt112 said:
OK guys, it seems I am not alone in having prolems with TouchPal on the HD. See this thread on CoolTek's forum.
http://www.cootek.com/forum/forum_posts.asp?TID=742&PN=1
I have tried everything, I have uninstalled the kb, reinstalled it. Last night I completely reinstalled the entire phone (hard reset, wipe, reistall) but TouchPal still stops working after a while.
Click to expand...
Click to collapse
just the thread, i guess your right, your not alone...but..its still wierd as iv been using touchpal since last wednesday and its still working fine for me
could it be that touchpal is conflicting with another keyboard on the device?
Have you gone to settings/inputs and selected touchpal as the keyboard?
I cant think of any other ideas because its working perfectly for me
Thanks xdaman
Just done a new re-install and it seems ok now. TBH I am now using the version from Cooltek so I may have had myself to blame.
On another note, I am having probs setting custom commands, I have the followig questions, can anyone offer any wisdom ?
You can setup custom commands such as Ctrl+z etc. They can be stored in place holders accessed by tab+downslide on the Control Tab button (the one with the 4 arrows). The instructions for creating custom command scan be found in the manual (section 4.2) here
Here are my questions
1. How do you create a combination command? e.g. They have a built in command called "Select All && Copy". This is 2 commands. How do you create this ?
2. After I mess up all my command buttons. How do I reset them to their defaults ?
3. When I create a command, Is Flag5 the ASCII key code? The manual is not specific on this. Also, if Flag5 is the ASCII code, why do I need to then enter the Alphabet index of the letter ?
4. I only seem to be able to edit the top Custom command button. If I try and assign values to the lower buttons, the edit appears in the top button. Is this a bug ?
cant install/wont install
downloaded the cab file..after it ran..it looks like explorer window pops up and tried to o something..anyway it says the page cant be found..tried loading in both card and local and get the same response..it does tell me the it was unsuccessful in loading
i gues its the lastest becuase i downloaded from the site
gt112 said:
Hi folks
I love this forum and am so glad its here, it seems to be the only place where ppl can get support for the HD right now.
I am using the TouchPal keyboard 3.5. It installed fine and I started using it and configuring it grand etc. But after a while it stops responding.
If I click on the small keyoard icon at the bottom of my screen, no keyboard pops up whatsoever. If I go to settings and change the default keyboard from TouchPal to say - Full Querty and press OK, the change does not take place (If I go back into settings, the keyboard is reset to TouchPal).
So I am left wthout a keyboard and I have to do a full restart of the phone. If I uninstall TouchPal all is well and the keyboard system reverts back to working normally.
Has anyone else expereinced similar ?
Many thanks for any help
gt
Click to expand...
Click to collapse

Keyboard input settings won't apply! And another question...

Hi there... I tried to change my keyboard input to the phonekeyboard, (don't exactly know the english name of this, since I'm running Danish OS), but it wouldn't apply. I'd press "OK", but nothing changed... It was still complete QWERTY, so I went back into settings, and saw it had been reset. So I tried again, OK, and back in, and it was back to Complete QWERTY... Then I downloaded TenGO Thumb, just thought it might help, but it didn't... The freaking settings won't apply! Help?
And the other issue I have is, that I can't run .exe files on my HD... It just comes up with a fail message. How to fix this? I'm desperately searching for .cab files since I can't use .exe files...
*.exe usually works only on the PC, so you have to use ActiveSync and then, after a syncronisation, launch app's setup on PC.
Oh okay. Thanks.
Any info on the keyboard settings not applying?
You can't change the keyboard settings from start->settings->input, its some sort of bug I think.
Instead you can change it doing this:
-go to any menu that allows keyboard typing and you will notice that near the virtual keyboard popup button there is a small arrow facing up, if you tap that arrow a menu will popup and you can change the keyboard settings there compact/full/etc , and it works!

Autocompletion/Autocorrection solved

For those of you frustrated with the autocorrect/autocompletion method of the Touch HD (who want the old Windows style back) here is the solution. It lets you still use the Diamond Keyboard and real autocorrection/autocompletion like the good old days. It was written for the Fuze but they have the same keyboard and software issues.
The complete solution with hyperlinks is located here: http://www.fuzemobility.com/?p=1527
Here is the text (the hyperlinks and photos were lost):
Many of you have seen my rants about the lack of traditional autocorrect and autocomplete on the Touch Pro (see here where I did it in a posting on editing the T9 dictionary, or here where I did it in our forums, and here where I did it at XDA (I’m BugsyKoosh)). Why was I so angry? For anyone who used an older Windows Mobile phone knows, the old method of autocompletion was far better than what the Fuze has. First off, when entering a contact the old method provided for a longer list of names that you can click on (whereas the Fuze guesses the single closest one and almost forces you into it). Then when actually typing words the Fuze gives you a few words but I always found it very finicky and ultimately turned it off because the space bar caused the word to complete and the spacing was off. Also, the Fuze wasn’t good at correcting mispelled words. It gave you a dictionary that would complete the words but if you spelled it wrong (because you didn’t use autocompletion and just kept typing) that meant you had a typo. The old style was a list of words as you typed in a drop down (you choose starting from 3 words) and it was both autocomplete and autocorrection so anytime I spelled the word ’spelled’ as ’spellde’ it will change it for me and it works a lot smoother. Also, the old style permits for word replacement using autocorrect so when I type the letters "pcm’ in the old style I edited it so it was replaced with ‘please call me if you have any questions’ and ‘tx’ was replaced with ‘thanks’. In fact I wrote a posting here on TiltMobility describing methods of changing the autocorrect files thinking I would port it over here just to get burned realizing that the Fuze simply wouldn’t do it…until now.
[Warning, this is a little long and filled with detail but I think the payoff is gigantic so please bear with me]
For definitional purposes, autocorrection is the ability to change a typo whereas autocompletion is guessing what I’m typing before or while I type. I cannot change the autocompletion dictionary at this time (the one that guesses as you type). This does propagate itself over time and it will get to know you. It also cannot be transferred from older devices. See this article for more information on why it is so hard but until DictMgr is updated we may be SOL (TVDinner was told by the author that an upgrade is in the works so lets all cross our fingers).
So the first step is to disable T9 (this is the method of autocompletion/correction I hate). The cab is posted here in our forums (I was provided this cab from a member at another forum). Don’t worry because you can uninstall this application and revert back (it’s a simply a single registry change actually). Once installed restart your phone for it to take effect. Then, go to Settings - Input and make sure all of the options for Word Completion are checked (you can change the number of words it suggests - I use three). OK now there’s one little glitch. My problem from the start was that the autocomplete method I like did not work with the Full QWERTY Keyboard (you know, the shiny onscreen keyboard that our Fuze comes installed with and is in the photo). It seemed like it would work and then stop and ultimately I was thinking I would be forced to install another keyboard (more on that later). After messing around with the keyboard I realized that I can get the Full QWERTY Keyboard to work with the old method. You have to make sure that the ABC-T9 toggle is set to T9 (look at the photo and you’ll see T9 is selected even though we disabled T9 entry). If you try to toggle it and it will not let you then try this: press the ABC-T9 button and try to toggle it, then hit the .,123 button and try that a few times until it flips over (if that doesn’t work do the same thing after going into portrait mode and toggle T9 and ABC). Have patience - it will toggle and once it does it stays that way. Now here’s the one flaw - the autocompletion with this keyboard only appears when there’s an odd number of letters (ex on the first, third, fifth) [note: autocorrection happens after you misspell a word so it works with this and any of the other keyboards]. Again, we can correct this with a different keyboard but we’ll get to that. What you’ll notice is that completion of contacts and words is instantly different and I think a lot better. Also, the library will build over time as it knows you and aside from correcting the words you type wrong it will get to know you and start to guess the next word before you even type it (it may even guess a few words at a time and by the time you make it to ‘tha’ it will give you an autocompletion option of ‘thank you very much’).
If you do not use the onscreen keyboard because you’re a physical keyboard kinda person then you’re in luck. Simply set the onscreen keyboard to the keyboard named ‘keyboard’ (it’s the crappy Windows default one) and you’re set. That one works like a charm with no nuances (but is miserable as an onscreen keyboard).
Before I let you all go on your editing ways, lets talk about one solution that gets rid of the nuance of only getting autocompletion on odd numbers (so it works on each letter you type) and that is by using a different onscreen keyboard (sorry, but I believe PocketCM uses T9 so it won’t work). If you use the onscreen keyboard and want to get past this nuisance then simply install freeware Happy Tapping Keyboard. In the attached photo I changed the skin to the iPhone skin (it is in that link provided - use the VGA skin). If you set Happy Tapping as your default keyboard it will not survive a soft reset even if you set it as the default input method. To do this install the Default IM cab and set it as the default keyboard (Settings - Input) and set it as the default keyboard in Default IM and it will stay with you. Happy Tapping is a great keyboard but personally I like the layout of the Full QWERTY Keyboard better, especially the shadowing of the buttons so you know its second function. And I learned that Happy Tapping is missing a ‘\’ key which was a burn when I was using Total Commander but I bet for the rest of you it’s meaningless. I will confess I used Happy Tapping for all of my 8525 and Tilt years and it is really very good.
So, in either event, lets change the dictionary so that typos are corrected (or in my case quick text can be created). You don’t need to do this but it’s a nice perk of using this method. There are two ways to do this - the application method and the Total Commander method. The first one is highly recommended for those of you who want simplicity. Simply install freeware DictMgr and go to the "word correction’ tab and you can begin to add words. The downside is that I only see the first few series of words (I don’t even get out of the A letters) but this doesn’t impact adding new words regardless of their first letter. If you use this method it make sense to use freeware MyMobiler so you can use your PC’s keyboard for ease. For those of you that want to see your entire dictionary and don’t mind a little Total Commander action then all you need to do is navigate to Windows and find a file named autocorrect.04…. You can open this in Total Commander (hit the pen/paper at the bottom) or move this file to your computer, edit it there and then move it back to your Fuze (change the settings to take it out of hidden/system). In either case, if you’re willing to use Total Commander there’s another benefit if you’re a former Windows Mobile user since you can get the file from your old phone and move it to your Fuze (I moved mine from my Tilt) but you can do both (move the old file using Total Commander and then edit it using DictMgr). For a step by step set of instructions on using Total Commander to modify the autocorrect file read the article I wrote here on TiltMobilty. In either case you MUST reset your phone for the changes to take effect (the file is read into ROM at startup). Be careful with autocorrection words (obviously you can change it later) but if you change ‘tx’ to ‘thanks’ that means in a text message you cannot use tx (it will correct itself to thanks) so think of variables like ‘thx’ changes to ‘thanks’ for emailing and ‘tx’ stays uncorrected for texting.
This will work for all versions of the Touch Pro, the Diamond and presumably the Touch HD as they all use the same keyboard configuration.
Wow, I feel like we’ve done a lot. I’m drained but relieved that my single biggest complaint is gone. A special thanks is owed to SCDavis who was the first person to try my disableT9 cab even though I warned him of a possible hard reset since I wasn’t sure what it would do and if it was uninstallable and of course to TVDinner who was with me for the autocorrection ride both in our forums and on XDA’s and brought DictMgr to my attention.
Thanks for the write-up. I must admit I tried the word completion for the full QWERTY keyboard and spotted a few bugs so I haven't used it since. Last night I decided to try the phone keypad as an alternative to the full QWERTY so I'm back in the world of T9 and word completion. If I have too many problems with it then I'll try your solution.
T9 is very very painful in my experience. The correction is poor and you don't have control over it and there's no autocorrect (spellcheck). I'm a fan of the old style a lot more... hope it helps - good luck
what is your post for? is there ia cab or file to autocorrect/autocompletion?
thank you.
Here's the cab and the quick version of what is needed. This all works tog et you back to the old style of autocorrection and autocomplete that Windows has and is much better than T9:
1) Disable T9 by cab and soft reset
2) either use the Windows keyboard (which is poor for onscreen use) or Happy Tapping (which requires the Default IM cab to be your default input) OR to use the Full QWERTY Keypad (the preset default keyboard) you need to toggle T9 to on (even though T9 was disabled) and to do this toggle it, hit the 123/abc button a few times until it sticks and you’ll get the old style completion/correction with that keyboard
3) to change the autocorrect dictionary find the autocorrect file in your Windows directory and change it using Total Commander (or other registry editor even though this is not in your registry) or DictMgr
it's interesting. But it seems that T9 use another dictionary that you can choose. Once T9 is disabled, the autocomplete dictionary is back to english, and I don't find the way to change it
any idea to do this ?
Sorry for OT, but I found touchpal to be much better.
It is commercial though, and does not support landscape properly as of version 3.5.

[Q] Multipress with CM10

Hi, I just registered here, but have been reading parts of the forums for some time. I first had Motorola Milestone, that I managed to successfully flash with CM7 using information found here. Thanks to all for sharing their knowledge .
Now I have switched to Milestone 2 (bought with CM10.1 by Engle_Mars nightly installed, and had some troubles upgrading to 10.2 but it finally worked, and I am happy ). Thanks Engle_Mars for the great job.
There is one feature that I really miss from the previous Milestone. That is multipress, which allows you to double-press a key in the physical keyboard to make a national character associated with this key. For my language (Polish) it is for example a -> ą. This is much faster than the default long pressing and choosing the wanted character from the list, and I very much liked it in CM7 (it was under System Settings -> Device Settings). But in CM10.1 and CM10.2 from Engle_Mars I cannot find this feature. Is it not there, or am I overlooking it? Is there an app that could add this functionality? (I searched, but couldn't find any). If no, is it possible you could add this, Engle_Mars? I found mentions of this feature in threads for other phones using CM10, so I suppose it is a part of CM10, but didn't make it to Milestone 2 port for some reason.
kaziq said:
Hi, I just registered here, but have been reading parts of the forums for some time. I first had Motorola Milestone, that I managed to successfully flash with CM7 using information found here. Thanks to all for sharing their knowledge .
Now I have switched to Milestone 2 (bought with CM10.1 by Engle_Mars nightly installed, and had some troubles upgrading to 10.2 but it finally worked, and I am happy ). Thanks Engle_Mars for the great job.
There is one feature that I really miss from the previous Milestone. That is multipress, which allows you to double-press a key in the physical keyboard to make a national character associated with this key. For my language (Polish) it is for example a -> ą. This is much faster than the default long pressing and choosing the wanted character from the list, and I very much liked it in CM7 (it was under System Settings -> Device Settings). But in CM10.1 and CM10.2 from Engle_Mars I cannot find this feature. Is it not there, or am I overlooking it? Is there an app that could add this functionality? (I searched, but couldn't find any). If no, is it possible you could add this, Engle_Mars? I found mentions of this feature in threads for other phones using CM10, so I suppose it is a part of CM10, but didn't make it to Milestone 2 port for some reason.
Click to expand...
Click to collapse
Czechop cm 10.2 version (4.3.1 jellybean) has polish characters. Have a try.
Fedroid said:
Czechop cm 10.2 version (4.3.1 jellybean) has polish characters. Have a try.
Click to expand...
Click to collapse
Thanks, but I am already using it
The problem is not in the Polish characters availability, because they are available with a long press (and touch), but in the far more convenient way of typing them by double pressing (no touching necessary).
kaziq said:
Thanks, but I am already using it
The problem is not in the Polish characters availability, because they are available with a long press (and touch), but in the far more convenient way of typing them by double pressing (no touching necessary).
Click to expand...
Click to collapse
Active metakeys and hit alt-lock and then the key asigned.
To access polish letters, choose Qwerty polish in Settings->Language & Input->Sholes keypad->Set up keyboard layout. Use ALT LOCK or ALT LOCK + SHIFT to get polish letters. ALT LOCK + '?' is mapped to pipe symbol('|').
To use META key you have to turn off android hotkey shortcuts. Unfortunately lately they made this option invisible in settings. To open it you have to type this in terminal (with root access):
su
am start -a android.intent.action.MAIN -n com.android.settings/.quicklaunch.QuickLaunchSettings
It is supposed that you can hit alt lock and another fisical key to get your polish characters (no double pressing but at least pressing two keys)
Greetings:highfive:
Fedroid said:
Active metakeys and hit alt-lock and then the key asigned.
To access polish letters, choose Qwerty polish in Settings->Language & Input->Sholes keypad->Set up keyboard layout. Use ALT LOCK or ALT LOCK + SHIFT to get polish letters. ALT LOCK + '?' is mapped to pipe symbol('|').
To use META key you have to turn off android hotkey shortcuts. Unfortunately lately they made this option invisible in settings. To open it you have to type this in terminal (with root access):
su
am start -a android.intent.action.MAIN -n com.android.settings/.quicklaunch.QuickLaunchSettings
It is supposed that you can hit alt lock and another fisical key to get your polish characters (no double pressing but at least pressing two keys)
Greetings:highfive:
Click to expand...
Click to collapse
Thanks. That feature would be a bit less convenient, but still cool. But I can't make it working.
I called the QuickLaunchSettings, and cleared all shortcuts (there was no option to disable the whole QuickLaunch). Then I entered the Sholes keypad -> Set up keyboard layouts, and chose QWERTY-polish. After that Alt-lock works like before (one Alt-lock + letter gives that letter, another one gives the blue symbol on the same key). Adequately Alt-lock + ? does not give the pipe, but ? or /.
Maybe I should have disabled the QuickLaunch thing as a whole, but I can't find a way to do that.
kaziq said:
Thanks. That feature would be a bit less convenient, but still cool. But I can't make it working.
I called the QuickLaunchSettings, and cleared all shortcuts (there was no option to disable the whole QuickLaunch). Then I entered the Sholes keypad -> Set up keyboard layouts, and chose QWERTY-polish. After that Alt-lock works like before (one Alt-lock + letter gives that letter, another one gives the blue symbol on the same key). Adequately Alt-lock + ? does not give the pipe, but ? or /.
Maybe I should have disabled the QuickLaunch thing as a whole, but I can't find a way to do that.
Click to expand...
Click to collapse
You need contact rabinhood, he will help you. He is the key master!:laugh:
kaziq said:
Thanks. That feature would be a bit less convenient, but still cool. But I can't make it working.
I called the QuickLaunchSettings, and cleared all shortcuts (there was no option to disable the whole QuickLaunch). Then I entered the Sholes keypad -> Set up keyboard layouts, and chose QWERTY-polish. After that Alt-lock works like before (one Alt-lock + letter gives that letter, another one gives the blue symbol on the same key). Adequately Alt-lock + ? does not give the pipe, but ? or /.
Maybe I should have disabled the QuickLaunch thing as a whole, but I can't find a way to do that.
Click to expand...
Click to collapse
Hello.
First thing for not to get lost in JB keyboard is that keyboard mapping seems to be done in several "layers":
the closest to hardware is /system/usr/keylayout/sholes-keypad.kl (the exact file name may be different in different ROMs, but this file is used to manage built-in hardware qwerty, there are more files here for other devices - mostly bluetooth keyboards)
This file is used to translate hardware key scan codes to system key names (ALT, SPACE, A, B, C, and so on)
/system/usr/keychars/sholes-querty.kcm (name may also be different ie. snoles-keypad.kcm, more files are for different hardware)
This file is used for telling system what character should be displayed (entered) after pressing a particular key with or without particular modifier keys (what to enter after pressing A, SHIFT+A, ALT+A, META+A, and so on).
Both of these are simple text files, and can be edited directly, to achieve effects you have to reboot system. Also beware! If you mess up with these files, you may disable hardware keyboard completely! Then rescue is overwriting bad files with originals from backup.
options found in android settings -> keyboard (Polish-QWERTY, AZERTY, QWERTZ) work like overlays, if you enable them, the system will use mixture of original kcm file, and the overlay - so depending on what an overlay contents, it may disable some keys you defined in your kcm
So if you want to modify keyboard, you have to disable these overlays, otherwise you will not get any effect (and may become a bit frustrated, like I was before I found this).
I attach my latest files with Polish letters entered with ALT_RIGHT modifier (obtained after holding ALT key), blue symbols entered with ALT (obtained after pressing, then releasing ALT key, and then pressing apropriate letter key), Greek letters with META key (mapped on ALT_LOCK). To have uppercase letters you have to press SHIFT release SHIFT, then ALT+key for Polish letters, or same with META for Greek letters.
To have CAPS, you have to press SHIFT twice. To have ALT_LOCK, you have to press ALT twice.
I'm wondering. Right now I have, let's say, multi-ALT (acting like ALT_RIGHT when held, and like ALT when held and released). Maybe it will be possible to code META in exactly same way, so we'll have another modifier key (META_RIGHT), but that's just an idea, and I haven't researched that yet.
I also wanted to encode arrow characters (right, left, up and down arrows) on META-left, META-right and so on, but also haven't had time to do that yet.
Regards!
Chris
[edit]
Added arrow characters (META+left, META+right, etc). Added not equals sign (ALT+META+G), equal or smaller (ALT+META+Z), qual or greater (ALT+META+X), double tilda (ALT+META+~), euro (META+~).
New files in attachment.
rabinhood said:
Hello.
First thing for not to get lost in JB keyboard is that keyboard mapping seems to be done in several "layers":
the closest to hardware is /system/usr/keylayout/sholes-keypad.kl (the exact file name may be different in different ROMs, but this file is used to manage built-in hardware qwerty, there are more files here for other devices - mostly bluetooth keyboards)
This file is used to translate hardware key scan codes to system key names (ALT, SPACE, A, B, C, and so on)
/system/usr/keychars/sholes-querty.kcm (name may also be different ie. snoles-keypad.kcm, more files are for different hardware)
This file is used for telling system what character should be displayed (entered) after pressing a particular key with or without particular modifier keys (what to enter after pressing A, SHIFT+A, ALT+A, META+A, and so on).
Both of these are simple text files, and can be edited directly, to achieve effects you have to reboot system. Also beware! If you mess up with these files, you may disable hardware keyboard completely! Then rescue is overwriting bad files with originals from backup.
options found in android settings -> keyboard (Polish-QWERTY, AZERTY, QWERTZ) work like overlays, if you enable them, the system will use mixture of original kcm file, and the overlay - so depending on what an overlay contents, it may disable some keys you defined in your kcm
So if you want to modify keyboard, you have to disable these overlays, otherwise you will not get any effect (and may become a bit frustrated, like I was before I found this).
I attach my latest files with Polish letters entered with ALT_RIGHT modifier (obtained after holding ALT key), blue symbols entered with ALT (obtained after pressing, then releasing ALT key, and then pressing apropriate letter key), Greek letters with META key (mapped on ALT_LOCK). To have uppercase letters you have to press SHIFT release SHIFT, then ALT+key for Polish letters, or same with META for Greek letters.
To have CAPS, you have to press SHIFT twice. To have ALT_LOCK, you have to press ALT twice.
I'm wondering. Right now I have, let's say, multi-ALT (acting like ALT_RIGHT when held, and like ALT when held and released). Maybe it will be possible to code META in exactly same way, so we'll have another modifier key (META_RIGHT), but that's just an idea, and I haven't researched that yet.
I also wanted to encode arrow characters (right, left, up and down arrows) on META-left, META-right and so on, but also haven't had time to do that yet.
Regards!
Chris
[edit]
Added arrow characters (META+left, META+right, etc). Added not equals sign (ALT+META+G), equal or smaller (ALT+META+Z), qual or greater (ALT+META+X), double tilda (ALT+META+~), euro (META+~).
New files in attachment.
Click to expand...
Click to collapse
Cześć
Thanks for the explanation. Only after Fedroid's suggestion to contact you I have checked the Czechop's CM10.2 thread (found some of your posts there), and found out that you were working on the Polish keyboard. The instruction Fedroid gave me was not working, because I was not using the latest Chechop's CM release. I have now upgraded, and the keyboard is working. However there are some very minor issues:
(I am not using the keys file you posted, but only the features in the rom (23.10.2013).
1. After installation there is no default on-screen keyboard (and you cannot set it). This makes the buttons (Menu, Back, and Search) and the physical keyboard not working at all. The solution is to switch the system to another language and back to Polish. It might be a bug (probably not yours), but I cannot post in the devel threads yet.
2. "Ń" does not work. I remember like 10 years ago I was making a charmap conversion feature for my program, and found out that there was a conflict (of char codes), that "Ń" could not be mapped. I don't remember the details, but I suppose it might be the case here too.
3. Pressing ALT(-Lock) + DEL or ALT(-Lock) and then DEL causes the whole SMS or sentence to be deleted. Since in the SMS app there is no indication of the ALT-Lock state, you can easily do that by an accident and there is no Undo. Is it possible to disable the ALT(-Lock) modifier on the DEL key (so that it will only delete the whole sentence when ALT(-Lock) is pressed together with DEL)?
Thanks for the work you are doing .
Hello.
Czechop has included in his ROM some older version of my files. Without META key, and with ALT_RIGHT mapped to "ALT LOCK" key. Honestly speaking, I cannot tell much about his implementation, since first thing I do after his ROM flash is I overwrite sholes-keypad kl & kcm files with my own (with more features). I also encourage You to do so, since my files seem not to be affected with at least bugs 1 and 2 You presented.
Ad1: I have no problems with on-screen keyboard - if hardware keyboard if closed, on-screen version pops up. Also four capacitive buttons under screen work flawlessly.
Ad2: I have no problems with Ń (right now I've entered it with my hardware keyboard). Czechop told me about some problems with Ń, that system is not able to recognize too big number of keys pressed simultanously, and somehow Ń was suffering, but as you can see I've just entered it for the second time with no problems.
Ad3: I don't know how to fix it. Del key doesn't appear in kcm file, and I don't know how to modify it. And yes, pressing Del+ALT removes whole line, which is quite annoying. I'll do some more investigation, and maybe I'll find something.
Regards! It's nice to see, that at least in the field of MS2 android development Poland has some real power! :-ł
rabinhood said:
Hello.
Czechop has included in his ROM some older version of my files. Without META key, and with ALT_RIGHT mapped to "ALT LOCK" key. Honestly speaking, I cannot tell much about his implementation, since first thing I do after his ROM flash is I overwrite sholes-keypad kl & kcm files with my own (with more features). I also encourage You to do so, since my files seem not to be affected with at least bugs 1 and 2 You presented.
Ad1: I have no problems with on-screen keyboard - if hardware keyboard if closed, on-screen version pops up. Also four capacitive buttons under screen work flawlessly.
Ad2: I have no problems with Ń (right now I've entered it with my hardware keyboard). Czechop told me about some problems with Ń, that system is not able to recognize too big number of keys pressed simultanously, and somehow Ń was suffering, but as you can see I've just entered it for the second time with no problems.
Ad3: I don't know how to fix it. Del key doesn't appear in kcm file, and I don't know how to modify it. And yes, pressing Del+ALT removes whole line, which is quite annoying. I'll do some more investigation, and maybe I'll find something.
Regards! It's nice to see, that at least in the field of MS2 android development Poland has some real power! :-ł
Click to expand...
Click to collapse
Thanks. I finally decided to try your files out, but I have hit a serious problem. When I tried to rename the file /system/usr/keychars/sholes-qwerty.kcm for a backup, I couldn't do it. I tried the ES File Explorer (root mode on), and it showed "the task did not succeed". I also tried typing su then mv sholes-qwerty.kcm sholes-qwerty-old.kcm while in the right directory, and got "Read-only files system".
How do I apply your files?
If czechops rom uses your key mapping files, i like to thank you rabinhood. Works well with german umlauts out of the box. And thanks to this thread I found out how to use them.
Greetings
hamu
kaziq said:
Thanks. I finally decided to try your files out, but I have hit a serious problem. When I tried to rename the file /system/usr/keychars/sholes-qwerty.kcm for a backup, I couldn't do it. I tried the ES File Explorer (root mode on), and it showed "the task did not succeed". I also tried typing su then mv sholes-qwerty.kcm sholes-qwerty-old.kcm while in the right directory, and got "Read-only files system".
How do I apply your files?
Click to expand...
Click to collapse
If you have problems with root access from file manager, I think the easiest and most reliable way to modify system files is:
1. Enter bootloader menu.
2. Select Tools -> USB Mount tools -> Share system
3. It should be recognized and mounted on your PC. (I'm running Linux, I think Windows won't be able to mount ext3/ext4 partition without some extra software.)
4. To copy files you have to be logged as root.
If I want to copy these files from running Android, I use ROM Toolbox Pro -> Root explorer.
---------- Post added at 09:53 AM ---------- Previous post was at 09:45 AM ----------
hamuchen said:
If czechops rom uses your key mapping files, i like to thank you rabinhood. Works well with german umlauts out of the box. And thanks to this thread I found out how to use them.
Greetings
hamu
Click to expand...
Click to collapse
Umlauts are Czechop's job. Say "thank you" to him.
rabinhood said:
If you have problems with root access from file manager, I think the easiest and most reliable way to modify system files is:
1. Enter bootloader menu.
2. Select Tools -> USB Mount tools -> Share system
3. It should be recognized and mounted on your PC. (I'm running Linux, I think Windows won't be able to mount ext3/ext4 partition without some extra software.)
4. To copy files you have to be logged as root.
If I want to copy these files from running Android, I use ROM Toolbox Pro -> Root explorer.
Click to expand...
Click to collapse
Thanks. I used the bootloader and a small linux pc (OpenPandora), and it worked .
But now only the Polish characters work with ALT-hold. Greek does not work (ALT-Lock + key does not produce anything), but ALT-Lock + arrows also work. It doesn't matter for me, because I don't use Greek letters, and this way is more comfortable for Polish chars.
A small quirk: Capital Polich characters work with Shift + ALT + key pressed as well as Shift press and release and then ALT + key. Except for... Ń, which works only with the latter . It's not an issue for me, just a funny notice.
Thanks again for this.
rabinhood said:
Umlauts are Czechop's job. Say "thank you" to him.
Click to expand...
Click to collapse
Ah, ok. Then, nevermind. But thank you anyway for not letting this device die.
Greetings
hamu
kaziq said:
Thanks. I used the bootloader and a small linux pc (OpenPandora), and it worked .
But now only the Polish characters work with ALT-hold. Greek does not work (ALT-Lock + key does not produce anything), but ALT-Lock + arrows also work. It doesn't matter for me, because I don't use Greek letters, and this way is more comfortable for Polish chars.
A small quirk: Capital Polich characters work with Shift + ALT + key pressed as well as Shift press and release and then ALT + key. Except for... Ń, which works only with the latter . It's not an issue for me, just a funny notice.
Thanks again for this.
Click to expand...
Click to collapse
Oh, yes, now I see what's going on with Ń. I haven't noticed it before, as I always press SHIFT, release it, and press ALT+key. Czechop told me that it is some kind of bug in keyboard hardware driver not dealing with too many keys pressed at the same time (but in particular N key).
My Greek letters are working, I don't know what might happen. Just in case I attach again latest version of kl/kcm files. Please copy them over files you have now, and remember to disable any keyboard overlays in CM10.2 settings.
Thanks.

Categories

Resources