Database Info

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] Odd classic voice dialer intermittently when using wired headset

Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3

bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.

joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3

take a screenshot of your classic looking dialer and post it here.

simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3

bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.

simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3

instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.

simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3

Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3

bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.

simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3

bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.

Issues with Autocorrect on Samsung Keyboard? Completely wrong word replacement

Hi all,
So, I'm having a bizarre issue with Samsung Keyboard on my Verizon Galaxy S7. I use the auto correct (auto replace) feature, and it normally does a very good job of catching typos and whatnot. But, it does something really strange when I end a sentence with an exclamation point (!) or question mark (?).
It replaces the entire word before this mark with something totally unrelated. Like for example, if I type "Yeah!", I hit the space bar, and it gets replaced with something like "The!", or "I!". My girlfriend has the same issue on her Galaxy S7. We never had this issue on our previous Samsung phones. This seems to only happen with Samsung Keyboard. But, I would like it if I didn't have to switch keyboards, or turn off Auto correct. Any ideas?
Here's what I've tried so far:
Clear cache and data on Samsung Keyboard
Disable Sync on Samsung Account
Disable various keyboard features, like Auto spacing and Auto punctuate
Factory reset
Thanks in advance!

OMG! Thank God someone else is experiencing this too because I thought I was going crazy LOL. I've been sharing the below post everywhere I can -- I sure hope Samsung fixes it soon because it's very irritating.
I have the s7 and I HATE the autocorrect. I use exclamation points a lot and every time you end a sentence with one it autocorrects the final word in the sentence to something completely random. For example, I typed "I don't understand how!" and it autocorrected how to "why." I typed "Why, does this phone?" and it autocorrected phone to "mean." I typed "Those poor kids are probably starving" and it autocorrect starving to "the." It's the most frustrating thing ever and happens every time I type a text message. I've never wanted to chuck a phone across the room more than when I'm texting on the S7. I've contacted Samsung support, twice, and they pretty much told me I was crazy. So, I figure I'll find every review post on the S7 and post about my issue to see if someone somewhere in the Samsung world can release a software fix for this stupid phone.

Yeah this drives me crazy as well. It's very inaccurate. Maybe a new keyboard like swift key? With the stock one you are better off just tapping
Sent from my SM-G930T using Tapatalk

Yes!! I'm so glad too that I'm not the only one experiencing this. I have been searching like crazy, and haven't found this issue listed anywhere.
So sounds like the only fix at this point is a custom keyboard. I hope they fix this soon. Thanks for the replies!

Ok, I have an update. I went into Settings > Language and Input > Samsung Keyboard > Add input languages. There was an "Update" button next to "English (US)". I downloaded this update. Since then, the problem seems to have diminished somewhat. I still see it, but it's kinda 50/50 now.
If somebody else wants to try this, let me know what kind of results you get. Thanks!

I managed to correct the problem! Under Settings > Language > Samsung Keyboard > Add Input Languages > More > Check for updates!!! So relieved!

Issues with Autocorrect on Samsung Keyboard? Completely wrong word replacement
Just use the Kii keyboard app. Free and does what you want.

I fixed it! I went to the Samsung keyboard in settings and changed the Keyboard Swipe to None. Boom! Instantly fixed!

i always loved the samsung keyboard but after the nougat update i move to gboard and think ill stay here for a while because i think the autocorrection works far better and love that you can have multiple languages at the same time rather then to switch between each one of the sammy.

I thought it was only me.... I used to save Roman Urdu words saved in my dictionary and it automatically used to replace the correct words as I zipped along.. no longer working right for me and I am so frustrated by it.. software update screwed my fav keyboard
Sent from my SM-G935F using XDA-Developers Legacy app

Airman1947 said:
Hi all,
So, I'm having a bizarre issue with Samsung Keyboard on my Verizon Galaxy S7. I use the auto correct (auto replace) feature, and it normally does a very good job of catching typos and whatnot. But, it does something really strange when I end a sentence with an exclamation point (!) or question mark (?).
It replaces the entire word before this mark with something totally unrelated. Like for example, if I type "Yeah!", I hit the space bar, and it gets replaced with something like "The!", or "I!". My girlfriend has the same issue on her Galaxy S7. We never had this issue on our previous Samsung phones. This seems to only happen with Samsung Keyboard. But, I would like it if I didn't have to switch keyboards, or turn off Auto correct. Any ideas?
Here's what I've tried so far:
Clear cache and data on Samsung Keyboard
Disable Sync on Samsung Account
Disable various keyboard features, like Auto spacing and Auto punctuate
Factory reset
Thanks in advance!
Click to expand...
Click to collapse
Sent from my Samsung SM-J510GN using XDA Labs

i get the same issues when i text on my Samsung s7 phone but mine does it anywhere in my text not necessarily at the end, im thinking about spending muy money on iphone instead cause this is driving me nuts! get tired of having tip go back and fix words on a constant basis or re-text because person reading it can't understand what i said.

Samsung Galaxy S7 Edge Predictive Text and Auto Replace
I was having the same problem (a word being suggested that was totally off from what was being typed and that wacky word replacing the correct word). The fix was keeping the predictive text on but turning the auto replace off. For my phone/software I got to these by:
1. Settings
2. General Management
3. Language And Time - Language and Input
4. Keyboards - Virtual Keyboard
5. Samsung Keyboard
6. Smart Typing - Predictive Text
The Predictive Text should be on, but the Auto Replace should be off
With the settings as described, the words I use a lot while texting (for instance "thanks" and "ok") show up under where I'm typing the text and I can tap them to save time, but the whole deal where some wacky word comes up and then replaces the word you wanted unless you hit the arrow goes away. I hope this is helpful.

it's 2018 and im still having this issue. I'll type in love and 100% of the time it switches to live. I mean, I use live too so i don't want to delete it. This issue makes me take atleast twice as long to type one message. I had it turned off for a long time and that was my solution, but if they have a feature, I want to ****ing use it. I NEVER had this issue on my previous Samsungs and i've only ever had Samsung "smart" phones.

Personalized notifications for contacts not working...

I posted this in the AT&T S8+ Forum, figured i'd post in here too, might get faster help. I did do a couple searches before posting, but if someone has already addressed this I apologize.
Hi all, I seem to be unable to get individual text notifications working on my S8+. That is, I go into the contact, I find where it says "Message Tone" and I set the tone I'd like to use. When I go in and look, everything seems to be correct.
Then when a text comes in, the default notification is still used. This is the case when both a tone that I added is used, or a built in tone. I had thought perhaps it was because I was using a 3rd party texting app (Textra, was not a fan of the default Samsung app), but even when I reset to the Samsung messages app, this was still the case (I even tried restarting the phone after setting messages as the default, just to make sure).
Anybody else having this issue? Anybody fix it? I've tried everything I can find, hopefully one of you can point out something obvious that I've missed.

Elbimster said:
I posted this in the AT&T S8+ Forum, figured i'd post in here too, might get faster help. I did do a couple searches before posting, but if someone has already addressed this I apologize.
Hi all, I seem to be unable to get individual text notifications working on my S8+. That is, I go into the contact, I find where it says "Message Tone" and I set the tone I'd like to use. When I go in and look, everything seems to be correct.
Then when a text comes in, the default notification is still used. This is the case when both a tone that I added is used, or a built in tone. I had thought perhaps it was because I was using a 3rd party texting app (Textra, was not a fan of the default Samsung app), but even when I reset to the Samsung messages app, this was still the case (I even tried restarting the phone after setting messages as the default, just to make sure).
Anybody else having this issue? Anybody fix it? I've tried everything I can find, hopefully one of you can point out something obvious that I've missed.
Click to expand...
Click to collapse
No issues here, after setting the message tone you want are you tapping save in the upper right of the screen?

ggrant3876 said:
No issues here, after setting the message tone you want are you tapping save in the upper right of the screen?
Click to expand...
Click to collapse
I am. I've attached a screenshot for a contact I'm using as a test (my GVoice number). It LOOKS like it's set up correctly (at least to me) just not working correctly. Personalized Ring Tones seem to work, but not text notifications.
The phone is doing a couple other quirky things. I'm wondering if it might be time to just say "F it" and do a hard reset.

Elbimster said:
I am. I've attached a screenshot for a contact I'm using as a test (my GVoice number). It LOOKS like it's set up correctly (at least to me) just not working correctly. Personalized Ring Tones seem to work, but not text notifications.
The phone is doing a couple other quirky things. I'm wondering if it might be time to just say "F it" and do a hard reset.
Click to expand...
Click to collapse
Here are the screens I get when changing a ringtone or messaging tone. Didn't get the screenshot low enough for messaging tone, it's right below ring tone.

ggrant3876 said:
Here are the screens I get when changing a ringtone or messaging tone. Didn't get the screenshot low enough for messaging tone, it's right below ring tone.
Click to expand...
Click to collapse
Yeah, I don't think I'm doing anything differently. Weird that ring tones work but not text messages. I had a couple different contact managers installed (don't really like the Samsung one) and thought maybe they were causing the issue, so uninstalled them and rebooted. Still no go.
I do like the look of the dark theme for the contacts app though, definitely gonna change it to that!

I also use Textra on my S8+, as I don't like the default one, and you set the personalized tones in Textra not contacts.
In Textra, go to one of the texts from someone that you want to customize and long press it, then go the three dot menu in the upper right corner and select customize. Then select Notifications, then notification sound and pick the one that you want.
Works perfectly...

larryk said:
I also use Textra on my S8+, as I don't like the default one, and you set the personalized tones in Textra not contacts.
In Textra, go to one of the texts from someone that you want to customize and long press it, then go the three dot menu in the upper right corner and select customize. Then select Notifications, then notification sound and pick the one that you want.
Works perfectly...
Click to expand...
Click to collapse
:victory: The files are IN the computer!! It's so obvious!! Thanks so much, this has been driving me nuts.
Still a little weird it wouldn't work when I reset the phone to the Samsung app, but now I don't care because this works!! Thank you so much.

Sometimes it is just the little things...

Text input unresponsive after unlocking phone?

Sorry for the weird title, I didn't really know how to concisely describe this issue. I still don't fully understand what triggers it but basically I've noticed that if I lock my phone while on a text chat (in either Textra or Facebook Messenger but probably includes all text chats), then unlock it to reply, I can't click on the text input box or hit the navbar back button for 3-5 seconds. This can also happen while my phone is unlocked when I'm switching through apps so I wouldn't directly blame the action of being locked. I know the phone isn't frozen because I can still hit the back button at the top left corner of the screen fine.
It almost looks as if though it's navbar-related because the pill is white when I unlock the phone, then after a few seconds when it's responsive again the pill is grey. My previous phone was a Oneplus 3 and it never had any issues like this (although it had physical buttons for navigation, not a navbar) so I'm wondering if this is an issue or if this is by design for some reason. I've tested each of the navbar options (traditional navbar, pill, and gesture) and none of them resolve the issue so maybe it really isn't.
One other detail I noticed is that the cursor also doesn't blink for those 3-5 seconds, and then when it starts blinking again I can start typing so it could be something else.
I just find it annoying to have to wait a few seconds whenever I want to unlock my phone and reply to a text and this doesn't seem like regular behaviour, has anyone else heard of or experienced this and know of a fix?
Videos of the issue:
In Textra:
https://imgur.com/X0lw47J
In Facebook Messenger:
https://imgur.com/1IrRfPY

It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?

ducted said:
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
Click to expand...
Click to collapse
I've had NFC disabled since I got the phone so that isn't it.
I don't think it's ghost touch-related since it doesn't happen sporadically, it just seems to be when I open a text chat app or something too quick which doesn't make sense. Perhaps I can record the issue and upload a video to more clearly show what happens.

I just added videos of the issue to the OP.

That looks weird, did you tried to use the gesture navbar only or the one with all the buttons? I would try also another keyboard just to discard any GBoard related issue.

I've tried every other navbar type (including the one with just gestures and no bar) and the results are the same. I have also tried a different keyboard (Fleksy) and again, same issue. I had essentially the exact same setup as far as apps go on my Oneplus 3 and its fine, so I'm thinking it has to do with either a new version of android or the new OxygenOS but I have no idea.