Hello, so I installed gbhill's 1.6 rom and I went to the market to download better keyboards. Once it was finished I went to setting options and selected to enable the better keyboards but I can't use them when the keyboard comes up. Is there something else I need to do to get this working?
Randomly, maybe you need to go to the keyboard settings and check mark touch input?
(I have no idea if it works but can't hurt to try)
Better keyboards works very well on thistle Rom. To get it going u just need to long press in a text field and select it. Assuming u have it activated in the settings
i love better keyboard with the android skin.
Yea i was a bit daft, they gave me clear instructions i didnt read. You need to hold the ?123 in the bottom left corner
Related
I posted this in the other Auto Correct thread (found here). That thread got so long that it was requested that I start a new thread with this info so it is easier to find this fix and how to do it.
I have a FUZE and mainly ONLY use the actual physical keyboard and not the onscreen keyboard. The fact you can not set up normal Auto Word Correction words was driving me crazy. So through a lot of people a fix was found. Credit goes to a lot of people who suggested different things (like Bugsykoosh), and then I put a few different programs/tweaks together and it works very well.
Here is how you do it.
1) Disabled T9 completely by installing the cab found at http://forum.xda-developers.com/showpost.php?p=2914474&postcount=8 . After installing the T9 button will no longer work.
2) Change your onscreen keyboard to "keyboard" as the default. You will no longer be able to use the QWERTY keyboard, but that was fine for me since I mainly use the actual keyboard. For this to work you MUST switch your on screen default keyboard to "keyboard" or install the Happy Tapping keyboard.
3) Install DictMgr for Windows Mobile that can be found at http://mobile-sg.com/software/?p=DictMgr&platform=ppc . It is FREE. This program is the key to making this work.
4) Only parts of DictMgr works with our version of Windows Mobile. After installing open up the program and launch the Word Corrector part of the program. It looks exactly like the traditional word replacement entry screen you see on your PC. SEE ATTACHED PICTURE.
5) Add the words you want to auto correct and hit save. It requires a soft reboot.
10) After the reset try to type something using the actual keyboard and you will see the word correct work the way it is supposed to.
I am VERY positive right now about this working so far.
Some other Feedback/Notes:
1) I use MyMobiler so when connected to my PC I can view my phone screen on my desktop. This makes entering all the auto correct words I want MUCH easier since I can use my normal keyboard.
2) I entered as MANY as I could at one time because a soft reset is required each time you save the file.
3) I have started entering all the basic ones like
i --> I
monday --> Monday
mon --> Monday
tuesday --> Tuesday
tues ---> Tuesday
(and all the rest of the days)
jan --> January
feb --> February
(and all the rest of the months)
4) on the onscreen keyboard I did go to the Touch Input Setting and check all options. See attached image.
5) I also went to the Options-->Word Completion Tab and checked "Enable Auto Correct. See attached image.
Everyone, this SEEMS to be a real EASY fix for this issue I am happy to report.
There is a solution to still use the Full QWERTY Keyboard. The complete text is located here: http://www.fuzemobility.com/?p=1527
After disabling T9 you must toggle the T9-ABC button back on. To do it press the button then hit the ABC123 button and keep going until it stick. If that fails go into landscape mode and try toggling. Once you get it to change it will stay that way. The one downside is it only works for odd numbers so it works on the first, third and fifth letter you enter and on the second letter no autocompletion appears on screen. The autocorrection (ex spell check) still occurs either way that.
Thanks TVDinner -that was fun
sweet! This issue now has 2 solutions. I love when a plan comes together!!!
So with this fix can I still use the physical keyboard/Full QWERTY soft keyboard/Phone Keypad like normal?
NeroDan said:
So with this fix can I still use the physical keyboard/Full QWERTY soft keyboard/Phone Keypad like normal?
Click to expand...
Click to collapse
Hi NeroDan;
With bugsykoosh's fix you can still use the on screen Qwerty keyboard.
With my fix you have to choose the onscreen "keyboard" option, or install the happy tapping onscreen keyboard. You can not use the qwerty keyboard with the fix I described.
If you do not use the onscreen keyboard then either fix will work fine.
Hi,
I am just new to this pocket PC phone (just the old HTC Touch) and i tried out installing an IP Phone Keyboard program. When I wasnt happy about it, i uninstalled it but it messed up my SIP. The default standard input keyboard now is cut at the bottom (meaning i dont see the entire last row of Ctrl, space bar, etc.) but there's a black row appearing at the top of the input keyboard. It looks like the input keyboard was dragged down. Worse, the suggested words now appear at the bottom of the screen (where your normal Send or Cancel buttons are).
I really would appreciate your advise and help in getting this resolved. Dont know where to run to or whom to raise this to.
Thank you and looking forward to your response.
ailene said:
Hi,
I am just new to this pocket PC phone (just the old HTC Touch) and i tried out installing an IP Phone Keyboard program. When I wasnt happy about it, i uninstalled it but it messed up my SIP. The default standard input keyboard now is cut at the bottom (meaning i dont see the entire last row of Ctrl, space bar, etc.) but there's a black row appearing at the top of the input keyboard. It looks like the input keyboard was dragged down. Worse, the suggested words now appear at the bottom of the screen (where your normal Send or Cancel buttons are).
I really would appreciate your advise and help in getting this resolved. Dont know where to run to or whom to raise this to.
Thank you and looking forward to your response.
Click to expand...
Click to collapse
Restart your PPC. After that go to settings--> input---> select default input keyboard and try.
Hope it will help.
Are you using the default keyboard?
You can install any other SIP and it should work fine even if the default keyboard's having problems.
You can also hard reset incase you don't manage anything else.
I'm not aware of a bug concerning the default keyboard showing wrong except for something which goes away after a soft reset.
Thanks very much for your responses. Unfortunately, I did all that (set keyboard as default, try installing another keyboard software, soft reset and hard reset) but the problem still persists. I am almost in the vicinity of regretting why i had this PPC.
can you specify exactly which app caused this problem?
I have issues with the use of the OEM on-screen keyboard of the HTC HD2. It registers the keys next to the ones I press if my finger even begins to slide a little when pressing the desired key.
I would like something much more stable than what it's equipped with. Does anybody know of a better keyboard for the HTC HD2?
MartyLK said:
I have issues with the use of the OEM on-screen keyboard of the HTC HD2. It registers the keys next to the ones I press if my finger even begins to slide a little when pressing the desired key.
I would like something much more stable than what it's equipped with. Does anybody know of a better keyboard for the HTC HD2?
Click to expand...
Click to collapse
try finger keyboard or fingerkeyb...google the forum for it...it works great for me...tried it even on qvga..and still it kicks butt
farukb said:
try finger keyboard or fingerkeyb...google the forum for it...it works great for me...tried it even on qvga..and still it kicks butt
Click to expand...
Click to collapse
Excellent! Thank you. That worked out just fine. It is better than the OEM KB. It also looks better. Is there a touchscreen sensitivity setting somewhere for the HD2, do you know?
EDIT -
Unfortunately the Fingerkeyb has a bug in landscape mode. Pressing the spacebar often brings up the menu because it is so close to the bottom of the screen.
EDIT 2-
Eh...I spoke too soon. The landscape mode doesn't work properly. I thought it was limited to the same size as the portrait mode because that's what shows up when pulling up the keyboard while in landscape mode. But after tapping the small arrow beside the KB selector, and then choosing Fingerkeyb, the landscape mode comes up. Which isn't all that appealing because it separates the keyboard at the middle, putting the directional arrows in the middle, rather than providing larger keys like the OEM keyboard does.
Hopefully the creator of this keyboard will will see these issues and deal with them. I guess I'll just stick to the OEM board for now...much less complex to pull up.
Me thinks this is wrong forum...
And I suggest Swype. It should be on the forums here somewhere.
Well...All is well. I had the 2.0 version installed and found the 2.1 version from a post speaking about it. Googling fingerkeyb brings up a link to the thread in xda with the 2.0 version. After specifically Googling fingerkeyb 2.1, I was able to get it.
2.1 resolves the issues I had and is much nicer too.
I just can't get over how things go wrong when I speak of something working well.
The letter "b/B" is dead in the fingerkeyb. Tapping it does nothing. It doesn't register.
I suppose it's just in the default skin, red/black. I loaded another skin, gray/black, and it now works. Also, the "b/B" works in the default skin if the option to "Show bar" for landscape mode is selected. The "b/B" works fine either way in the default skin in portrait mode.
as already mentioned, google for Swype mate, trust me you'll never use another keybord again
One of the cooked ROMS has a cab for swype within it. Not sure on the legalities of it as it was only released for the Tmobile HD2, but if someone confirms its ok I'll tell you which ROM to save you digging about.
Actually if you are happy with the keyboard and its just the sensitivity issue then take a look at this post...
http://forum.xda-developers.com/showthread.php?t=604831
I had majoy issues with the keyboard and pressing of buttons etc but this CAB worked a treat!
Moved as not software release.
so has anybody else noticed that the word prediction (when having the phone keyboard set to regular touch input and not Swype) doesn't regularly show up when using the hardware keyboard?
I've noticed that, in order to get the word prediction going when using the hardware keyboard, I'll first have to close the keyboard, start typing with the on-screen keyboard to initiate the word prediction, and then open the keyboard and resume typing, at which point the word prediction continues..does anybody else have this issue?
I havent noticed that yet. Although most of the time I enter a program and after I get frustrated trying to type on screen I switch to keyboard.
I remember having a similar issue, although it only seemed to happen to me when entering into the messaging app sometimes. It was a mild annoyance. However, it completely went away when I installed swiftkey X. I highly recommend you get it. Imo more than worth the money. It's the fastest and most accurately predicting keyboard I've tried, particularly with hardware support.
It doesn't seem to be working for me very well, but do make sure you enabled correction by going to:
Settings > Language & Keyboard >Touch Input > Hardware Keyboard Settings > Prediction.
Sinfamy said:
It doesn't seem to be working for me very well, but do make sure you enabled correction by going to:
Settings > Language & Keyboard >Touch Input > Hardware Keyboard Settings > Prediction.
Click to expand...
Click to collapse
Hi Sinfamy, thanks, I did make sure that that setting was enabled. The prediction does show up, but again, only after I've first started typing with the touch keyboard in portrait mode first...if I start off an email or SMS with the hardware keyboard open, the prediction never kicks in.
I'm also gonna give swiftkey x a try and see if that helps.
swiftkey x is working great, and it seems like it'll be really good with its predictions too...thanks for the suggestion!
The best thing about SwiftKey is that it only gets better the more you use it! Keep in mind that although you cannot enter your personal dictionary and edit it like you can with other keyboards, if a prediction you don't like keeps popping up, you can press and hold the prediction to remove it.
napilopez said:
The best thing about SwiftKey is that it only gets better the more you use it! Keep in mind that although you cannot enter your personal dictionary and edit it like you can with other keyboards, if a prediction you don't like keeps popping up, you can press and hold the prediction to remove it.
Click to expand...
Click to collapse
nice, thanks for the tip napilopez..
is anybody else using keyboard manager to switch between keyboards for landscape and portrait, and finding predictions not showing up properly?
First, just want to say thanks for the development on the Note Pro. CM on this thing is awesome. That said, I still have a couple of lingering issues, hoping someone may have found some work arounds/solutions. Inevitably there will be someone that will reply with "USE THE SEARCH!". For those that do, I will offer you my sincere admiration. Your search foo is only exceeded by your wit. For those that are still willing to read on and assist, know that I've come up empty in my search attempts. Believe me, I'd rather have found a simple search result than to have typed all this up... In any case:
1. Hardware keys and navbar -
CM has a setting for "Enable on-screen navigation bar and disable hardware buttons". Checking this box enables the navbar, but fails to actually disable the capacitive and physical buttons. This causes me some grief when using the tablet in portrait mode. I've tried hacking around in the build.prop and the Generic.kl files, but haven't found that magical combination of new lines/commented out lines. Maybe CM does this differently than other roms? (I've not observed a difference in these files when toggling back and forth in the settings, so there must be something else I'm missing.) Any pointers?
2. Key Mapping -
I have the Logitech Pro Keyboard Case. Seems to work well, for the most part. (I'm typing on it now...) However, not all of the keys work. Example - there are keys on the top left row for "back", "menu" and "task switching". Nothing appears to happen when pressing these now. Again, probably something in a .kl file somewhere, but I'm coming up empty. There doesn't appear to be a Vendor-Specific.kl file, but Generic.kl doesn't seem to cut it either.
3. On-Screen keyboard still displays when using bluetooth keyboard.
Well, that about says it all really. I've tried using both the Google keybard, and SwiftKey. Both continue to show up on-screen, even though I'm typing on the bluetooth keyboard. Swiftkey even tells me that it cannot detect a physcial keyboard. Probably related to the key mapping issue from above, but...
Again, thanks for all the work on this. Having CM saved my tablet from it's date with eBay.
Thanks!
- Bri
1. i thought about it but now i haven't spare time to implement. next week maybe.. but i dont promise
2. and 3. try this programm https://play.google.com/store/apps/details?id=com.apedroid.hwkeyboardhelper
171
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
bribash said:
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
Click to expand...
Click to collapse
Hey, try going with Null Keyboard, enable all your keyboards, and switch between them depending on whether the device is connected or not