T9 Word Prediction is TERRIBLE for Better Keyboard

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use T9 with word prediction enabled.

What is the expected output? What do you see instead?
Examples:

2 key defaults to b instead of a
4 key defaults to h instead of i
4-3-9 defaults to hew instead of hey
4-4 defaults to Gil instead of hi

The system seems to pick a letter from the key for input, which ends up
with these weird selections. For example, 4-4 shows as gg which is
corrected to Gil instead of hi. This is fine for the full QWERTY keyboard,
but is a serious problem for T9, requiring me to select the proper issue
from the list.

It's possible to work off of prediction (HTC_IME does a much better job at
T9), so I'd really like to see this integrated into Better Keyboard. At the
very least, I'd like to see the 2 and 4 keys defaulting to a and i, since
those are stand alone words.


What version of the product are you using? On what operating system?
Latest version on Market, Cyanogen 4.2.5, was present on every version of
Cyanogenmod and stock T-Mobile 1.5 and 1.6 I tested on.

Original issue reported on code.google.com by draecas on 17 Nov 2009 at 8:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I found a way to help alleviate some of the problems, but it doesn't seem to 
work consistently.

Basically, whenever you find a really stupid prediction (and there are many), 
type in the word you wanted manually, and add it to your user dictionary, even 
if it already exists. The user dictionary entries typically get priority so 
will often become the default match.

HOWEVER, this doesn't seem to work in all cases. The most egregious is "of", 
where, exasperatingly, the Better Keyboard T9 will predict "nd" instead. (Yup, 
that's a real winner.) Even with "of" in the user dictionary, it will continue 
to choose "nd" as the obvious best choice.

Come on, BetterAndroid, your keyboard is almost the best on the market, and 
there's a significant market demand from people wanting a good T9 keyboard. But 
the current autosuggestion is leaving the product with a major limp. Even if 
you don't get into the business of adjusting suggestion ordering based on 
previous user choices, PLEASE have the user dictionary dominate, or allow the 
user to specify "least desired matches" for the worst cases, so that I could 
put "nd" on my match blacklist and have it shoved to the bottom of the 
suggestion rankings.

Original comment by [email protected] on 19 May 2011 at 9:36