Database Info

Disable predictive-like text thing

Posted this in HD2 general, might not have been the right section as no-one seems to be paying any attention, and I really want to sort this!
May be a stupid question, I've searched my phone and the net and couldn't find anything, though I'm not sure what I should be searching for anyway.
I'm hoping someone can tell me how to disable the box of words that pops up when typing something, trying to predict what you might be trying to say.
I'm sure it's only been showing up recently, possibly since I installed an application or something, as I don't remember it being there when I first got the phone, otherwise I would have asked this question by now.
I've attached an example of what I'm talking about.
I've tried going into Text Input Settings and enabling / disabling Spell Correction, Word Completion (XT9) and Word Complection (ABC) (all off at the moment) but it doesn't seem to make any difference, and it's really bugging me!
Any help would be really appreciated!

disabling those options and resetting the device does the trick for me.....
btw what kind of keyboard are you using there?
also you have an "options" when selecting the keyboard input, in that opting menu you need to disable them there too.

I've tried a number of different combinations of settings and resetting the phone in between, just doesn't seem to pay attention to the settings.
Also think there's something weird going on as the XT9 and ABC doesn't make any difference when using the normal keyboards, it no longer has the XT9 style text prediction instead of this blocky word suggestion. Though I don't care about the missing XT9 mode, I just want to hide this.
Also, I'm using Swype keyboard, which was installed after this happened in the hope it would hide the word suggestion, but no such luck

Anyone? Anything?
Really want to sort this, but need assistance!

Try going to HKCU\ControlPanel\Sip. If you have the key 'suggwords', change it from 4 to 0. You may need to soft reset. There are many other settings that can be tweaked in there as well. You could just change 4 to 2, so the suggestion panel doesn't take up as much real estate. Still, it will occasionally obscure a control, which is annoying.

Perfect! That's exactly what I wanted.
I knew someone would know!
Many thanks.

Issue with Keyboard

Hi all, been lurking for a while but thought I would finally post up.
Having an issue with my Nexus S on stock ROM v2.3.3. It isn't the same issues with the keyboard disappearing etc but it is an issue with the keyboard not inputting text when I type.
If I am typing a SMS reply to someone on my phone and I pause for a few seconds (to talk to someone for example) then I try to continue typing, the keyboard acts like its typing but does not actually type anything else into the message. The only fix I have managed to discover is exit the SMS so that a draft gets saved then once I go back into the message it works again.
Don't know if that is a clear enough description but if anyone else has any suggestions or even a fix for it then it would be greatly appreciated
Thanks

Yeah I have that too sometimes. What also happens to me about every week is, that the smiley sections' and the (particularly important for me since I'm from Austria and using the German keyboard ü-ö-ä) special buttons and symbols' pop up extension (hard to describe, but I mean the thing that pops up when you put your finger on the expandable tile for like 2 second and which let's you select the unusual symbols from a list) simply will not pop up. So it would make it impossible for me to choose from the pre-created smileys etc.
I have found out that changing your input method to another keyboard (I use SwiftKey in these cases) and then changing it back Android keyboard make the problems disappear. But they seem to come back regularly and I haven't found out what causes them to appear...
Any help?

[Q] Google Keyboard Prediction Problem in Lollipop?

I really hate what Google have done to the keyboard in Lollipop. The predictions have been changed for the current word to show suggestions that aren't what you are trying to type, (if you are typing accurately.)
On the face of it, this seems to be a logical decision. In practice though, your eyes have to keep going upto your message to check what you have just typed is correct. You then have to go all the way down to the space bar to get the next word prediction. :silly:
Under the old system, if you were typing accurately, you would just press the middle button without your eyes ever having to go up and find where you are typing. This would then prompt the next word prediction without ever having to look upto the message or down to press the spacebar.
Is there any way to get the Kit Kat keyboard into Lollipop. (Its a deal breaker for me and could influence the Moto X 2014 vs Nexus 6 decision!)
See attached Kit Kat and Lollipop. In the example, I'm trying to type, "The."

I just tried your scenario and it seems to be working fine on Lollipop.
As soon as I type 'T', the Google keyboard suggests the word 'The'. If I tap on that suggestion it then suggests the next predicted word.
If I type 'Th', it still suggests 'The' as the predicted word, but it also highlights or bolds the suggested word, indicating that I can hit the space bar to accept the suggested word 'The'.
If I go ahead and type the whole word 'The' without selecting the suggested word after either of the first two times it suggested it, it assumes I didn't want the word 'The' after all and suggests a different word.
Is that not the behavior you're seeing?

StringerE said:
I just tried your scenario and it seems to be working fine on Lollipop.
As soon as I type 'T', the Google keyboard suggests the word 'The'. If I tap on that suggestion it then suggests the next predicted word.
If I type 'Th', it still suggests 'The' as the predicted word, but it also highlights or bolds the suggested word, indicating that I can hit the space bar to accept the suggested word 'The'.
If I go ahead and type the whole word 'The' without selecting the suggested word after either of the first two times it suggested it, it assumes I didn't want the word 'The' after all and suggests a different word.
Is that not the behavior you're seeing?
Click to expand...
Click to collapse
It is also what I see in Lollipop. Whilst it seems logical, when you are swiping, you only tend to check the word when you have finished a swipe. In KK, this mean't always going to the suggestion bar and confirming which also mean't insert space and then mean't next word please. Your eyes need almost no movement.
In lollipop however, when you have finished the swipe, your eyes have to go all the way upto the text, find where you typed and check it is what you wanted, then go all the way down to the spacebar and press it to ask for the next word suggestion.
It just means you can swipe so much faster on KK than you can on LP as your eyes are having to work alot less. :crying:

For me, the L version seems to be better at determining what I'm trying to swipe without me having to check it. I usually go ahead and swipe out the 2-3 sentences I want in my text/reply/post/whatever and then go back and verify it says what I wanted to say. And I've found it has been more accurate on L than it was on KK. Any incorrect words I see at that point I click on and the suggested replacement is usually what I wanted. If I verified each word as I swiped it would definitely be slower.
In other words, I rarely select the suggested words. I just swipe out what I want to say without looking up and then go back and verify before sending. And it's typically pretty accurate.

Is anyone seeing really bad lag while typing? Maybe I just type too fast but after I think I'm done with a word I look at the screen and it's still spelling it. I have vibrate on key press on, popup on keypress on and the text correction on.

kgry said:
Is anyone seeing really bad lag while typing? Maybe I just type too fast but after I think I'm done with a word I look at the screen and it's still spelling it. I have vibrate on key press on, popup on keypress on and the text correction on.
Click to expand...
Click to collapse
I've had no problems with keyboard lag and I'm using 5 on the Nexus 7 2013, (Which is a much slower device.)

IDK about Swype type input but tapping is worse with white on white keys. I fixed it by switching to the older theme. I realized my eyes play a part in my accuracy apparently because muscle memory isn't enough. It's weird.

MrObvious said:
IDK about Swype type input but tapping is worse with white on white keys. I fixed it by switching to the older theme. I realized my eyes play a part in my accuracy apparently because muscle memory isn't enough. It's weird.
Click to expand...
Click to collapse
It's good that Google gave you the choice to switch back to the old keyboard look. I just wish Google would give me the option to switch back to the kit kat swipe functionality. I can't buy a nexus 6 until they fix this!

I faced the problem on android 5.0, did they solved on 5.1?

McGyver dei poveri said:
I faced the problem on android 5.0, did they solved on 5.1?
Click to expand...
Click to collapse
The keyboard still sucks in 5.0.2
I don't think 5.1 is out yet?

It's out but not for my note3... Only the LG keyboard is as fast and comfortable as this for me. A part the autocorrection problem, they also removed the option to remove the "change language button" it wastes space for nothing... Bah..
For example now I'm typing on the forum and I have to watch the super small text in the forum box ... I'm a lot slower than before that was in the center of the keyboard, and ofc I make more mistakes... Silly choice by google's engineers

For example now I'm typing on the forum and I have to watch the super small text in the forum box ... I'm a lot slower than before that was in the center of the keyboard, and ofc I make more mistakes... Silly choice by google's engineers
Click to expand...
Click to collapse
Exactly the problem I have. If Google don't sort it out in 5.1 I'm staying on kit kat for sure. I get what Google were trying to achieve but they need the option to do both kk and lollipop prediction methods.

Personally I hate it. I have had to type words like "complaint" dozens of times over even though my swiping technique hasn't changed because the software thinks I'm trying to type "composition". Now, mind you, I swipe over to the A and there is no A in "composition".

Any news from android 5.1?

McGyver dei poveri said:
Any news from android 5.1?
Click to expand...
Click to collapse
No change.

Argh!!! That really sucks. Looks like it's staying on kk for me. :crying:
Would be nice if someone could hack the Google keyboard :angel:

Just an update for people having the same issue as me in Lollipop.
On the Play store, there is an app called Jellybean Keyboard 4.3. :highfive:
This app pretty much gets around my issue with the Google Keyboard and has worked fine for the last week I've been testing it with only a few niggles:-
- Emotions requires a separate download.
- When the app updated a few days ago, it forgot what it had previously learned.
I still dont understand why Google Keyboard cant contain a tick box in the settings entitled, "Include typed word in suggestion box in Lollipop." :crying:

Oh dear god. I tried Lollipop once on my N4 - it was awful. Now I plan to switch to 5.1 and see how it is one more time (and check if there is better battery life) but that keyboard abomination still scares me and its sad to know that it still persists...
However I'll try to live with that - at least for one day - cuz I wanna try EuphoriaOS tommorow Maybe I'll try to install Google Keyboard from 4.4.4... Somehow.

Just go for the jellybean keyboard as above. :angel:

[Q] Double tap to select word stopped working?

The other day I softbricked my phone and spent hours trying to get it back. I was lucky enough to get back using Smart Switch to restore firmware, but it installed 5.1.1. Whatever, I'm living without root.
However, I noticed since then that I can no longer double tap on a word to select it. I have to long press on a word to highlight it. Anyone else experience this? Kind of annoying. I was so used to the double tap.

Finally, someone else noticed. I noticed the same thing. Ever since I updated to 5.1.1 on my s6, double tap to highlight is completely gone. Very annoying

supernaru428 said:
Finally, someone else noticed. I noticed the same thing. Ever since I updated to 5.1.1 on my s6, double tap to highlight is completely gone. Very annoying
Click to expand...
Click to collapse
What both of you mean? I have the 5.0.2 version and when I double tap some text it just zooming in, where does it highlight something?

When you're texting for example. Double tap any word you entered, and it will highlight and allow you to copy it or remove it.

JusTeN_ said:
What both of you mean? I have the 5.0.2 version and when I double tap some text it just zooming in, where does it highlight something?
Click to expand...
Click to collapse
supernaru428 said:
When you're texting for example. Double tap any word you entered, and it will highlight and allow you to copy it or remove it.
Click to expand...
Click to collapse
This. Sorry, I should've clarified that I meant when you're typing. Not just any text.

Yep, annoying as hell.
On a good note, though, now you can long press to highlight the word and then just swipe the new word and it replaces it. Prior to 5.1.1 it would not replace it with the new word, it would only grab letters from the new word that were not in the previous word and replace it with those letters, which was even more annoying and made absolutely no sense.

daewond3r said:
This. Sorry, I should've clarified that I meant when you're typing. Not just any text.
Click to expand...
Click to collapse
Oh, actually I use long press to highlight something, not double tap.

has anyone had any progress or a workaround for this issue? It's killing me - I've used this feature for years.
Swype's website still says that double tapping a word should select it. I tried other keyboards and none of them allowed me to double-tap select anything but I do not know if they supported double-tap select before the update. I'm also curious whether this applies to all devices or just Galaxy S6.
Pretty annoying.

deepfryerdan said:
has anyone had any progress or a workaround for this issue? It's killing me - I've used this feature for years.
Swype's website still says that double tapping a word should select it. I tried other keyboards and none of them allowed me to double-tap select anything but I do not know if they supported double-tap select before the update. I'm also curious whether this applies to all devices or just Galaxy S6.
Pretty annoying.
Click to expand...
Click to collapse
We're talking about the stock Samsung keyboard.. which is not Swype. So what Swype says, doesn't matter lol

ingenious247 said:
We're talking about the stock Samsung keyboard.. which is not Swype. So what Swype says, doesn't matter lol
Click to expand...
Click to collapse
Obviously the problem is bigger than just the Samsung keyboard. Samsung's site doesn't say anything about double-tapping to select text whereas Swype does mention it. So, what Swype says is very relevant to this conversation because it proves that the problem is not with the keyboards, it's with Android. lol

deepfryerdan said:
Obviously the problem is bigger than just the Samsung keyboard. Samsung's site doesn't say anything about double-tapping to select text whereas Swype does mention it. So, what Swype says is very relevant to this conversation because it proves that the problem is not with the keyboards, it's with Android. lol
Click to expand...
Click to collapse
Wish they hadn't changed it. double-tap is faster (to me) than long-press.
At least I've got a workaround.

deepfryerdan said:
has anyone had any progress or a workaround for this issue? It's killing me - I've used this feature for years.
Swype's website still says that double tapping a word should select it. I tried other keyboards and none of them allowed me to double-tap select anything but I do not know if they supported double-tap select before the update. I'm also curious whether this applies to all devices or just Galaxy S6.
Pretty annoying.
Click to expand...
Click to collapse
Don't know if you have this issue fixed, but it happens the same here with Note 4. Very annoying indeed.

Well, it works for me, both with Samsung's keyboard and SwiftKey.
Sent from my SM-G920I using Tapatalk

Left Samsung after Note 2 and came back to the S9 and yeah, it's annoying... My Android/Huawei phone didn't have this problem.

This is driving me crazy & I can't believe there's no fixes online! Upgrading from my Galaxy S3 of 3yrs to a GS7, so Kitkat to Oreo, & just whyyy did they nix the "double tap to select text typed"?? Siighh.. ;(
There MUST be a way to re-enable it..

Yeah, it's 2021 already yet Samsung still hasn't managed to fix a bug it introduced (many!) years ago.
If Samsung doesn't really know how Android works, we can only hope our devices don't just blow up one day as a result of Samsung's pure reliance on trial and error.
To be clear, it is stated by Android spec that while in a text field, upon a double-tap a word gets selected; hence current behavior is called a bug as the functionality is simply not there

Gboard - voice to text mic missing in messages

Hi,
Just got my unlocked Pixel 4a today. No custom roms or anything. Android 11. Build RQ1A.201205.008.
I'm a bit of a minimalist, and I went through the keyboard settings for messages (it had this little emoji bar thing that also did the predictive words I wanted to get rid of). Also in that bar was the microphone for voice to txt. When I shut off those unneeded options and turned the dedicated numerical row on, the microphone disappeared. I've tried resetting the options to the best of my memory, but it still isn't back to where it was, and the microphone is still gone.
There is another microphone in the preview box, but that is a tap-and-hold-to-send-a-recording microphone. Not what I'm looking for. That works.
I checked permissions, Gboard has permissions. I checked the keyboard settings, voice to text is enabled. Anyone know the 'magic combination' of options to get this back? I use it frequently!! I'd hate to have to reset-to-factory just to restore this one feature.
Thanks!

I finally found it after much headaches. It seems the voice to text microphone is part of the "suggestion strip" that is under "Text Correction". No idea why this isn't integrated into the keyboard as it's own icon as it's been in earlier versions of Android.
If anyone has any recommendations on how I can potentially make that integration and get rid of the suggestion strip, please let me know.

I tried to reproduce the missing voice2text mic that you reported and failed.
I went to Gboard settings > text correction then:
Disabled show suggestion strip
Disabled next-word suggestions
Disabled emoji suggestions
Disabled sticker suggestions
Going back to the keyboard, the suggestion strip/stickers/GIF/clipboard/settings and the mic were all gone.
I re-enabled all the above and the mic reappeared, along with the other stuff.
One thing you could try short of factory reset is to go to the App Info for the Gboard, force stop, and clear the cache. Relaunch the keyboard to see if it brought the mic back.
---
Looks like you resolved it. I think this design change was made a few cycles ago and am not aware of any way to re-integrate it. You could try SwiftKey to see if that has the feature you want.

I think installing a different keyboard can be helpful here. Have you tried to do it? To be honest, it was one of the most significant problems that made me change a model of my phone. I did have a Samsung Note, and the problem with the Gboard was repeating very often. I have been browsing different sites to find a solution, but was never successful in it. One day, one of my sisters visited me and took my phone while I was in the kitchen. She fixed the problem instantly, would you believe it? I came to the room and was surprised after she showed me it. She said she visited https://techplugged.com/5-best-solutions-to-fix-the-gboard-not-working-error/ and followed all the instructions given there. I have forgotten about the problems with Gboard for a long time, but there were other reasons for me to change my phone to the latest iPhone.