WTF: Autocorrect always suggest "toy" instead of "you"

[GoodEnough]

How do I remove "toy" from the damn dictionary?
LG G2 running KitKat.

 

[s44]

Which keyboard are you using?

With Swype you can long-press the word on the suggestion list to add/remove it. Dunno about the others.

 

[eelw]

On iOS, autocorrect of well to we'll annoys me the most.

 

[GoodEnough]

I'm using the built in keyboard on KitKat.
I assume it's Google keyboard.

 

[mikegg]

I found Android's autocomplete unusable.

 

[dawheat]

I found Android's autocomplete unusable.

Androids? You mean Google Keyboard?

OP don't know about stock keyboard, but I've found SwiftKeys predictions pretty good and you can remove anything by long holding the word.

 

[mikegg]

Androids? You mean Google Keyboard?

OP don't know about stock keyboard, but I've found SwiftKeys predictions pretty good and you can remove anything by long holding the word.

Tried stock keyboard and swift. Both have unintuitive autocompletes. Last time I used it was 2012 though.

 

[Anubis]

how are you misspelling you to get it to suggest toy?

 

[iahk]

LG's stock keyboard is their own. Not the google keyboard.

http://youtu.be/FnNj3ZBVxMs

 

[gorcorps]

Tried stock keyboard and swift. Both have unintuitive autocompletes. Last time I used it was 2012 though.

Switfkey adapts and learns, so you have to use it for it to recognize how terrible you are at typing. After a while it's pretty solid though

 

[Dulanic]

Switfkey adapts and learns, so you have to use it for it to recognize how terrible you are at typing. After a while it's pretty solid though

^^^

It bases it's recommendations after the previous words also to increase it's accuracy. Swiftkey is prob the best one IMO. The Swiftkey cloud is nice too since it stores your recommendations between devices.

 

[s44]

Swiftkey may be the best at tap-prediction. Swype is the best at... swyping. Google's is decent at both. Samsung and LG's OEM keyboards have that nice number row.

 

[VashHT]

I replaced the LG keyboard with the google one pretty quickly, I gave it a try for about a day but it wasn't cutting it.

On a somewhat related note, why are some people so afraid to try anything other than stock on Android, my friend also picked up a G2 and no matter how much he complains about the stock keyboard/browser he refuses to use something else. Every time he complains about how shitty the keyboard is now I just tell him it's his fault, I've told him so many times to replace it that it's just weird how he keeps trudging through and forcing himself to use it.

 

[Suspicious-Teach8788]

Remember that autocomplete and autocorrect are two different things. I myself have not found autocomplete useful at all. I'm the type who just starts typing away, so I notice a lot of people talking about autocomplete and I'm in confusion. Do you guys stare at the keyboard and pause typing to look at the choices and then figure out which one works best? Basically a type, stop mid-word, look, choose the next word?

In terms of autocorrect, I've found the Google Keyboard to be atrocious compared to 3rd party keyboards like Swiftkey and Fleksy. In fact, sometimes the Android system spell-check will highlight a word in RED and whereas the Keyboard app will fail to autocorrect or find a suitable correction. The Android system spell check really needs to be integrated with the keyboard. Having two different dictionaries and/or autocorrect/suggestion systems is not only redundant but poor design.

Edit: Here's an example. I'm not sure if accommodations has two Cs and/or two Ms. So here I type it out with one of each. First off I'm a bit disappointed that Google's products can't pick this typo up and process it properly. Someone should test, but I'm willing to bet SwiftKey and Fleksy can process this typo. For the record iOS does this no problem.

Second of all, Google Keyboard's spell check versus the system's spell check are totally different. None of them seem to be able to correct my typo. I can't currently find an example now where the keyboard fails to correct my typo but the system does, but clearly given that the two are independent, there's a likely case where this could happen.

 

[cronos]

Remember that autocomplete and autocorrect are two different things. I myself have not found autocomplete useful at all. I'm the type who just starts typing away, so I notice a lot of people talking about autocomplete and I'm in confusion. Do you guys stare at the keyboard and pause typing to look at the choices and then figure out which one works best? Basically a type, stop mid-word, look, choose the next word?

I was going to post the exact same thing, that it seems that a lot of people are confusing the terms autocorrect and autocomplete (which is really 'next word prediction', what Swiftkey is great with).

Anyway, my answer to your question is yes, but the way you said it sounds terrible, while in my case with the help of Swiftkey, it's awesome.

Now that I have established my language pattern with Swiftkey for a couple of years (it has cloud sync so I don't have to reestablish it after a factory reset or phone upgrade), I only needed to type the first 2 or 3 letters of a word and then I just hit the space bar to complete the word. During typing, my eyes are mostly on the prediction bar instead of the keyboard (yes, Swiftkey accounts for inaccurate fingers). If the middle bar shows the exact word I wanted to use (which happens in most cases) then I immediately hit space bar to complete that word and move on with the next word. If it doesn't, my eyes automatically glanced to the left and right bar, and if it's one of those, I just tap that word manually. If none are there, then I type one more letter until I got it (at this point it's extremely rare that I get to type a whole word). Remember, this process is in a split of a second while I'm continuously typing without stopping, e.g.: tap tap space bar, tap tap space bar, tap tap tap left prediction bar, tap tap space bar, etc.

So, just like you, I also just 'type away', it's just that my eyes are on the prediction bar instead of the keyboard and I do not expect to have to type the whole word. Instead, I rely on Swiftkey's excellent word prediction and simply hit either the space bar or left/right prediction bar to complete my word before I move on to the next word. It's really amazing if you have gotten used to it.

Now, in addition to the above, the coolest thing about this is that I use dual language and switch languages extremely often. It is not uncommon for me to switch and use words from different language back and forth in the middle of a sentence. With Swiftkey you can activate both dictionaries at the same time, so it recognized when I tend to switch language and use words from other language, and when to switch back to English and provide me with the correct predictions almost all the time! This is what got me hooked and could not leave Swiftkey.

Of course, it is not for everyone and I understand that. I just wanted to give a description of what's going on when you type by relying on 'next word prediction'. The other way around is true to me as well, after I've gotten used to Swiftkey, typing on my iPod Touch with iOS autocorrect turned on is an absolute torture. I ended up turning off autocorrect and had to force myself to type really slowly, tapping every single letter carefully.

 

[Suspicious-Teach8788]

Now that I have established my language pattern with Swiftkey for a couple of years (it has cloud sync so I don't have to reestablish it after a factory reset or phone upgrade), I only needed to type the first 2 or 3 letters of a word and then I just hit the space bar to complete the word. During typing, my eyes are mostly on the prediction bar instead of the keyboard (yes, Swiftkey accounts for inaccurate fingers). If the middle bar shows the exact word I wanted to use (which happens in most cases) then I immediately hit space bar to complete that word and move on with the next word. If it doesn't, my eyes automatically glanced to the left and right bar, and if it's one of those, I just tap that word manually. If none are there, then I type one more letter until I got it (at this point it's extremely rare that I get to type a whole word). Remember, this process is in a split of a second while I'm continuously typing without stopping, e.g.: tap tap space bar, tap tap space bar, tap tap tap left prediction bar, tap tap space bar, etc.

So, just like you, I also just 'type away', it's just that my eyes are on the prediction bar instead of the keyboard and I do not expect to have to type the whole word. Instead, I rely on Swiftkey's excellent word prediction and simply hit either the space bar or left/right prediction bar to complete my word before I move on to the next word. It's really amazing if you have gotten used to it.

So here's what I don't get. You're not really just typing way because you are stopping and thinking and processing those suggestions that show up in the bar. To me at least, that slows me down. So instead of 100% typing speed, maybe I'm at 60%. It's kinda like my issues with Google Instant search. I might be searching "Best sushi in San Francisco" but as I type "Best sushi" I already see my result. However, I'm a 120wpm typer and by the time the Google result loads, I've typed to "San" already, at which point I take my hand off the keyboard, move to the mouse, and Google Instant Search processes the search result for "Best sushi in San" which gives me a different set of results. Maybe sushi restaurants for San Diego now start popping up, or my intended page now has shifted positions. What makes it worse at least for Instant Search is I instinctively hit back on the browser, but these aren't actual page loads, so back doesn't take me to the most recent instant search. I've learned to just type the whole damn query now and if my eyes caught something mid-search, I'd go back and trim my search down to where I think Google Instant tried to give me a mid-search result.

I'm digressing, but my point is you can't be 100% focused on typing and instead you're looking for intermediate results which throws off concentration. I suppose there's many schools of thoughts about how you type, but for keyboards like Fleksy, the idea is you just speed away and type as fast as you can and rely on the top notch auto-correct. Swiftkey can be used that way too. In many ways iOS is too. You're supposed to just trust it as it learns your typing, and surprisingly on a 3.5" screen it works decently well. Maybe I'm just too much of a power user to properly use prediction. Heh.

 

[cronos]

Like you said, it's just completely different way of typing. I don't think one is necessarily better than the other. It slows me down doing it the other way because I never expected to type a whole word, just like it slows you down because you have to 'think' while typing.

It's great that we have options on Android though, so nobody is forced to do it one way or the other

 

[cronos]

LOL just now Craig Federighi was introducing 'next word prediction' on iOS 8 at WWDC. I'm sure you're going to LOVE this feature now DLerium!

Edit: and apparently third party keyboards as well! grats

 

[Suspicious-Teach8788]

LOL just now Craig Federighi was introducing 'next word prediction' on iOS 8 at WWDC. I'm sure you're going to LOVE this feature now DLerium!

Edit: and apparently third party keyboards as well! grats

I probably will love it, although we have to see how well Apple implements it. I like their autocorrect so far, so I think offering 3 suggestions is only going to bolster the keyboard quality. Of course part of the limitations in the iOS keyboard is the phone size, but perhaps that will change in iOS6.

My complaint about Google is that their keyboard auto-correct is still piss poor, and while 3rd party apps exist, none of the 3rd party apps have really been that attractive IMO.

 

[gorcorps]

Swiftkey may be the best at tap-prediction. Swype is the best at... swyping. Google's is decent at both. Samsung and LG's OEM keyboards have that nice number row.

I've had this conversation before (and maybe with you) but I disagree. Even Swiftkey Flow in beta was superior to Swype at the time. I'm not sure if they've improved swype or not since then, but after Switkey introduced Flow I haven't looked back. I was a long time Swype user and it wasn't anywhere as good as Swiftkey was. I was constantly making corrections in swype that I didn't have to in Swiftkey because Swype just couldn't be trained. Add on to that the ability to change keyboard size now and I have no need to use anything except Swiftkey again.