Yes I was about to explain that it will not change anything for your examples.
I am still waiting for feedback to understand the behaviour of your phone, and I need to know if it's the same on the Nexus One or other phones. What you describe is just impossible with the stock keyboard if it has the same word list as mine, so I would say the Moto Droid has a smaller dictionary and probably a different autotext from the default one.
What is improved in 1.9.0 is prediction of short words when letters are missing (e.g "sloly" -> "slowly")
Bad predictions
- cyril
- Developer
- Posts: 2079
- Joined: Tue Feb 02, 2010 4:02 pm
- Phone: Nexus One 2.3
- Location: Nice, France
Re: Bad predictions
Cyril
Re: Bad predictions
when skpro was launched i had problems with the way it handled word prediction of smaller words like 'tje' wouldn't yield 'the' but i don't know what you did perhaps make the prediction algorithm suggest for a larger area of hits or something, but now it does a better job. if you flat out type 'tje' it yields 'tje' but if you are closer to the 'h' than the 'j', it renders 'the'. i am loving it!andyk wrote:another inconsistency:
some users have noted that sometimes you have to type the whole word to get it to work. i have noticed this too with random words. here is one example:
typing the word "screen"
stock keyboard: sc-SC, scr-screen, scre-screen, scree-scree, screen-screen
SKP: sc-Scot, scr-scree, scre-acre, scree-scree, screen-screen
motorola droid 2.0.1
the example quoted above is very true. would love to see it somehow working! keep up the great work!
Re: Bad predictions
btw i'm on the n1 and i'm seeing:
stock: "is", "tea" and "Deon"
skp: "is", "tea" and "dwindle"
stock: "is", "tea" and "Deon"
skp: "is", "tea" and "dwindle"
-
- Posts: 5
- Joined: Mon Mar 01, 2010 4:57 pm
- Phone: Nexus 1
Re: Bad predictions
If I try to type "testing," the stock keyboard suggests it after "testi" but SKP insists on resting.
-
- Posts: 5
- Joined: Mon Mar 01, 2010 4:57 pm
- Phone: Nexus 1
Re: Bad predictions
That's awesome, thanks Cyril. If I find any others, I'll let you know.
-
- Posts: 52
- Joined: Fri Feb 26, 2010 4:14 am
- Phone: Motorola Droid 2.0.1
Re: Bad predictions
in 1.12, i can definitely notice a significant difference in word prediction. frequently, i'd type "stipid" instead of stupid, and instead of having any corrections, it would just remain as stipid. now, it's "stupid" and also, the correction of words when missing a character has increased dramatically.
cyril, great work, and keep it up. i find myself checking my Downloads in the Market 4 times a day just to see "update available" next to SKP
cyril, great work, and keep it up. i find myself checking my Downloads in the Market 4 times a day just to see "update available" next to SKP

Re: Bad predictions
Does the prediction "learn" from word usage? It seems like the longer I use (and no, my accuracy hasn't improved), the better completions are.
- cyril
- Developer
- Posts: 2079
- Joined: Tue Feb 02, 2010 4:02 pm
- Phone: Nexus One 2.3
- Location: Nice, France
Re: Bad predictions
Well... I tried on a Android 1.5 phone and indeed it seems there are problems with suggestions. But on a Android 2 phone I don't see any regression compared to the previous version. "stupid" works for me
maybe you have added it by mistake in your user dictionary ? that would explain the problem
As for the learning, it is possible, as words are automatically added to the user dictionary if you type them more than 5 times. But I plan to work on a better learning method

As for the learning, it is possible, as words are automatically added to the user dictionary if you type them more than 5 times. But I plan to work on a better learning method
Cyril
- cyril
- Developer
- Posts: 2079
- Joined: Tue Feb 02, 2010 4:02 pm
- Phone: Nexus One 2.3
- Location: Nice, France
Re: Bad predictions
OMG !!
I just found a huge bug which is present probably since the beginning, regarding the detection of key presses, and causing wrong key detections.
I didn't see it with Android 2.1, but with Android 1.5 it is clear that it causes very bad suggestions
I will release a fix ASAP
I just found a huge bug which is present probably since the beginning, regarding the detection of key presses, and causing wrong key detections.
I didn't see it with Android 2.1, but with Android 1.5 it is clear that it causes very bad suggestions
I will release a fix ASAP
Cyril