I initially noticed this on my Galaxy s6 a few weeks ago after an update. Google Voice typing stopped pausing the music player if I used the voice option to dictate a text message. It used to stop the music and continue after I was finished. Now it'll play the music in the background and it's making it hard to dictate because it will also pick up on the lyrics from the song. At first I thought my S6 was just going crazy and a factory reset would probably fix it but I just got the S8 and I am facing the same issue. Any advice?
Thanks!
Hmm... mine pauses anytime it's listening to a voice command. Never tried to text with it though.
I bet that makes for some really interesting conversations.
It does stop the music if I use the "Ok Google " command to use the assistant but it doesn't do it if I'm using it to dictate a text message.
Just did a test.....it works fine in version 6.12.25.21 which is the one that comes pre-installed on the s8. however when you update to the latest version in the play store you get the problem. i've downgraded back to the older version for now. anyone else experiencing this issue?
thechico1986 said:
Just did a test.....it works fine in version 6.12.25.21 which is the one that comes pre-installed on the s8. however when you update to the latest version in the play store you get the problem. i've downgraded back to the older version for now. anyone else experiencing this issue?
Click to expand...
Click to collapse
I'm having the same problem. This is when you activate voice within the google keyboard right? What app did you downgrade?
Well, I use the Samsung keyboard but yes, it's when you activate the voice option on the keyboard. I did try it with the Google keyboard but was getting the same problem too. The app that I downgraded was "Google". Just go into the playstore, type Google, "uninstall" the app and it should bring you back down to the version that came pre-installed with the phone. And then uncheck auto-update in the right top corner of the app screen in the playstore. That should fix it for now. Let me know if it works!
thechico1986 said:
Well, I use the Samsung keyboard but yes, it's when you activate the voice option on the keyboard. I did try it with the Google keyboard but was getting the same problem too. The app that I downgraded was "Google". Just go into the playstore, type Google, "uninstall" the app and it should bring you back down to the version that came pre-installed with the phone. And then uncheck auto-update in the right top corner of the app screen in the playstore. That should fix it for now. Let me know if it works!
Click to expand...
Click to collapse
I was able to uninstall updates for the google app and yea, I was able to fix the problem. Partially. It pauses the music now when voice is activated. But when I send the message, music will not resume. Does this happen to you?
Same problem with LG G5
I have had the same issue for the past couple of weeks. When using the Google Voice typing, all media apps are no longer paused (Spotify, RocketPlayer, Podcast Addict, etc) thus Google Voice is transcribing the words coming from these media apps. I uninstalled Google App today, but then Google Voice to Text worked very poorly. Does anyone have any thoughts on solutions or workarounds? Thanks.
try installing a previous version of the google app. The galaxy s8 comes with this build standard and it works fine.
Did you guys ever find a fix for this? its driving me nuts. Im on OnePlus 3 but yeah its a new issue for me started after nougat... It seems like lots of people have the issue but are just living with it. While driving it really sucks. Used to be so easy to voice reply and pod-kicker would resume play back. Now I gotta pause first then reply voice text then hit play again ...its MADDENING. Looking for a fix. The downgrade worked for me for a short while then it just started up again. I didn't auto update google app. Tried clearing every data cache...uninstall reinstall...even different keyboards!!! same issue. Thanks guys!!!! hope we can figure it out.
The downgrade still works for me.
I have the same problem in my Oneplus 3T, I can not send voice messages while driving.
Same issue on my LG G6, BUT, for me it only does it when I'm connected to Bluetooth in my car - which is of course when you need voice recognition most. I have to manually pause the music to use it. Driving me nuts. I'm surprised they haven't released an update to fix it. I guess not a lot of people on these latest devices using voice recognition.
The downgrade still works for me but it appears it also has been fixed for me with the newest Google app update 7.3.26.21. I tried it with spotify and google music with and without bluetooth connection and it works. Stops the music then automatically resumes. Let me know if it works for you guys too.
Related
With all of the settings correctly configured and several Google voice training programmings later, I am only getting about a 25% detection rate when saying "Ok Google" - especially when the phone is off or on the lock screen.
Anybody else have this issue?
For me OK, Google and the S Voice stopped working after an hour and never worked since then.
Magnesus said:
For me OK, Google and the S Voice stopped working after an hour and never worked since then.
Click to expand...
Click to collapse
Wow, really?
I'm very curious to see how others are fairing with this
Well, what is funny is that S Voice woke my phone a few times while I was playing games on my computer and once when I was watching a movie. I turned it off, something must be wrong with my voice pattern or something. :laugh: I never intended to use it anyway - was just playing with it - so it's not a huge loss for me. I think I might have blocked too many apps or I need to reboot or something because my fingerprint sensor also does strange things.
I just discovered Nova Launcher is causing this problem. When using TouchWiz home it works perfectly.
Anybody know how to get in contact with Nova Launcher?
Dissable svoice then go into google search app info and clear info. Now when you go into google now voice settings you can set it up with google recognition. It won't work when the screen off buy at least it works the rest of the time.
beno0055 said:
Dissable svoice then go into google search app info and clear info. Now when you go into google now voice settings you can set it up with google recognition. It won't work when the screen off buy at least it works the rest of the time.
Click to expand...
Click to collapse
I already have S Voice disabled, but I'm a little confused about what this would solve?
using hot boots causes this problem too. I had some problems with nova launcher but now it works just fine.
try to reboot and check you google now settings+ you can turn it on or off in nova's settings
I've encountered a really strange problem on my watch (Samsung Gear Live) lately. Not a single texting app will let me use the "reply" button with voice.
Example: Friend texts me, text pops up on my watch. I swipe it and click "Reply" and try to reply using my voice. The text will write out on my watch screen, but the red Google mic icon just sits there for about 10 seconds as if its still thinking it's receiving input, and then it takes me to the "disconnected/watch is offline" screen.
But the watch is obviously not disconnected: I can exit that app and tap the screen and say "Okay Google" and then say "Text friend 'hi how's it going'" and the text will send without a problem.
I've encountered this error when using Coffee SMS, WearResponses, and Google Messenger. I've reset the watch, and cleared Android Wear data, and the problem still persists. This makes no sense. Any ideas/suggestions?
I have the same problem on my LG G Watch R.
I received the Watch today, the reply function worked once or twice, but now it does the same as yours
My Gear Live is still under warranty so I've sent it in to Samsung. We'll see if they are able to fix it...
darnocs1 said:
My Gear Live is still under warranty so I've sent it in to Samsung. We'll see if they are able to fix it...
Click to expand...
Click to collapse
Update: So, Samsung just replaced the entire watch for me. I'm setting it up now to see if the problem is fixed. Has anyone with the same problem tried factory resetting their *phone*?
UPDATE 2: Well, crap. It still doesn't work. I'm going to try pairing the watch with a different phone sometime in the near future to see if it's my phone. It's obviously not the watch.
Out of curiosity, what version of the Google Search app do you have installed?
Solution
darnocs1 said:
Out of curiosity, what version of the Google Search app do you have installed?
Click to expand...
Click to collapse
Okay, I got it working. Obviously, there's probably some degree of magical Googleness that happened, too, but here's what I did:
Background: I had Google 5 installed from the Android M preview, and I had also previously sideloaded a newer version of Google Play Services (still compatible with my phone, of course)
1. Booted watch into recovery; factory reset several times.
2. Meanwhile, uninstalled updates to Google Play Services, and then download update from the Play Store
3. In the Play Store, uninstall updates for Google App (Google Search), then update from the Play Store
4. Turn on watch, pair with phone, and then pray over it
5. Test out an app (I use Coffee SMS), text yourself, and try replying to it. It might tell you that "Google Play Services must be installed" - I rebooted my phone and then manually connected the watch via the Android Wear app, and then tested it and it worked.
YMMV.
Thanks for keeping us up to date
I too, was finally able to get it corrected, but mine was a bit easier. The only real difference between what you first described and my situation - was that I am using the LG Urbaine Watch with the new LG G4. LIke you (and someone else) it worked a few times and I was thinking that would be my most used feature. Later - it stopped working and my research began. I thought it might have something to do w/ my loading up the LG Call companion app - but after taking that off - it still didn't work. Finally, a good friend of mine that is an Android lover - suggested I switch from the Verizon Message plus application - to the generic one provided by LG. As soon as we made the switch - the Text message response option appeared again. In fact, in addition the reply arrow - I also could see a full list of the conversation with that particular party. Very happy in making that little change.
Ever since I got my S7 Edge replacement from the Note 7, Google Voice is being troublesome. I can't get it to recognize my voice correctly, well sometimes. For example if I ask it to list "nearest restaurants near me" it will search for "Near Me" like if it didn't understand my first two words. Or other times It says "if you said something, I didn't understand you". I tried uninstalling and\or cleaning cache from Google apps, but doesn't fix the problem. Can this be a software problem or the phone Mic being defective?
dja2k said:
Ever since I got my S7 Edge replacement from the Note 7, Google Voice is being troublesome. I can't get it to recognize my voice correctly, well sometimes. For example if I ask it to list "nearest restaurants near me" it will search for "Near Me" like if it didn't understand my first two words. Or other times It says "if you said something, I didn't understand you". I tried uninstalling and\or cleaning cache from Google apps, but doesn't fix the problem. Can this be a software problem or the phone Mic being defective?
Click to expand...
Click to collapse
Are you saying "Ok google, nearest restaurants near me" or "Ok google..." *Wait for prompt* "nearest restaurants near me"?
I don't know if the wait would help, I know that I wait until I hear it make the noise before I continue to say anything. Give that a shot and see if it helps.
You can test out your microphone but I don't see a need to if you use the phone to talk to others and they don't have any problem hearing you.
What launcher are you using? I use Google now myself and I don't need the pause but am just used to waiting in case it didn't hear me when I say the command.
Also try going into Settings -> Applications -> Default Applications -> Phone Assistance App and see if you have Google App as the chosen app. Not sure if that would help but it's worth a shot.
I am definitely waiting until it gives the tone and then speak right after. I just noticed that the delay is on the Google app and not when using voice typing on the Samsung keyboard which brings up Google Voices well.
Simialar Issue
dja2k said:
I am definitely waiting until it gives the tone and then speak right after. I just noticed that the delay is on the Google app and not when using voice typing on the Samsung keyboard which brings up Google Voices well.
Click to expand...
Click to collapse
I am having a similar Issue on my S7 Edge. The "Ok Google" prompt works just fine but then the mic cannot hear me at all. If I am on a Bluetooth device it works just fine and all other voice apps including the Google Assistant in Allo work fine. I have done a factory reset, I have disabled S-Voice and all other apps that use voice work just fine. I am at a loss at this point.
rbdavis76 said:
I am having a similar Issue on my S7 Edge. The "Ok Google" prompt works just fine but then the mic cannot hear me at all. If I am on a Bluetooth device it works just fine and all other voice apps including the Google Assistant in Allo work fine. I have done a factory reset, I have disabled S-Voice and all other apps that use voice work just fine. I am at a loss at this point.
Click to expand...
Click to collapse
Make sure the Google App has permission to access your microphone. I would assume it does if the hotword detection works but still worth a shot.
I found a workaround that seems to work better on detection....
Have the phone at a distance and the top mic underneath your mouth level. Seems to give me less false positives this way, I have no idea why. Hope this helps.
What I did was uninstall the update for voice recognition and re download it. Helped immediately.
csstamatin said:
What I did was uninstall the update for voice recognition and re download it. Helped immediately.
Click to expand...
Click to collapse
can you explain how to do that. im having the same problem for a while now and it really irritating
ajkron said:
can you explain how to do that. im having the same problem for a while now and it really irritating
Click to expand...
Click to collapse
Sure, go into setting, then language and input. From there click on google voice typing then click offline recognition and u should be able to uninstall then reinstall the software for it. Hope that helps.
Has anyone received the Google Assistant update yet? It was suppose to role out yesterday. Just wondering since the default for this phone is Moto assistant if we will get it or not.
Love the Nougat update
Gary
I installed the "Play Services Info" app by weberdo and used it to download Google Play Services version 10.2.99 (440-148249840) from APK Mirror. After a couple of reboots and disabling Moto Voice, Google Assistant became active. I had to touch the microphone icon, and after a couple of tries, it went into "configure" mode and learned my voice. Now working fine.
rhickers said:
I installed the "Play Services Info" app by weberdo and used it to download Google Play Services version 10.2.99 (440-148249840) from APK Mirror. After a couple of reboots and disabling Moto Voice, Google Assistant became active. I had to touch the microphone icon, and after a couple of tries, it went into "configure" mode and learned my voice. Now working fine.
Click to expand...
Click to collapse
Didn't work for me. Oh well, I guess I'll just have to wait.
Gary
Interestingly, for me, even while running on play services 10.2.98, I had all the assistant settings in the google app, and even paired it with my smartthings account, but alas, voice search is still going to the old style search. Updated to 10.2.99 and still seeing the same behavior. I didn't even know we were getting assistant, and was quite excited when I saw the settings, so when it didn't work, of course I got unreasonably upset. oh well
astephon88 said:
Interestingly, for me, even while running on play services 10.2.98, I had all the assistant settings in the google app, and even paired it with my smartthings account, but alas, voice search is still going to the old style search. Updated to 10.2.99 and still seeing the same behavior. I didn't even know we were getting assistant, and was quite excited when I saw the settings, so when it didn't work, of course I got unreasonably upset. oh well
Click to expand...
Click to collapse
Alright, I let it sit for a couple hours, and it's working now. Though, still can't launch it from the microphone button in the google app or the google search bars on the home screens. That still launches the old voice search. Have to long touch the home button or use the "ok google" launch phrase. It's a shame it can't use the always-on mic from moto voice though.
I'm seeing some similar things. Google Assistant came down to my phone automatically. Set up the OK Google voice command. Seems to work fine when launching from the mic button on the assistant, but will not respond to always on mic when the phone is idle.
You do have to disable Moto Voice, or change the voice phrase to something other than OK Google. Phone still responds to Moto Voice command on idle, but not OK Google.
Yea, so unless there's a software update for Moto Voice, we're likely not going to get the always-on mic to work with assistant. There's a dedicated processor on the SoC that handles the always-on mic, and it's tied directly to Moto Voice. Moto voice really doesn't do a whole lot other than listen for the launch phrase. Everything after that point is basically handed off to Google Voice search. It really should be quite a easy fix (pass the requests onto assistant instead of voice search), but I doubt that will happen.
smiley4017 said:
Has anyone received the Google Assistant update yet? It was suppose to role out yesterday. Just wondering since the default for this phone is Moto assistant if we will get it or not.
Love the Nougat update
Gary
Click to expand...
Click to collapse
I woke up this morning and I finally got the assistant. just an FYI
I got it too. However, while it unlocks the phone when locked and the screen being on, it will not wake the phone when saying ok google. You hear the sound prompt that it heard you, but nothing ever follows up and the screen stays black
I'm using the NotSoStock ROM for the T-Mobile V20 version 6.5. I haven't had any issues this entire time but of recent randomly my Google app won't work. When I open it the wheel just spins with no message or indication of connecting to Google. Google Assistant will not respond to OK Google. Voice to text won't work on GBoard. The Google search bar won't work. My play store is fine Gmail is fine just seems to be everything related to the new installment of Google Assistant stops working. I'm not using greenify. I haven't installed anything different since getting this ROM running. It hasn't been updated since I've rooted. Only thing I've downloaded was a theme from the playstore. I thought maybe that was it so I removed it and went back to stock but it did it again later on in the evening after being perfect all day. Sometimes if I close all apps it will connect when reopening. But other times I have to reboot the phone. I've wiped cache and dalvik cache. Wiped app data and cache. I've tried changing the ignore status of Google services framework so it's never put to deep sleep in the settings baked into stock LG UI. I can't figure this out and it's frustrating. Can anyone help or at least let me know I'm not alone and maybe this is a Google server issue.
I have had similar behavior with Google assistant acting up, again just very recently and it used to be flawless. Must be Google update version issue. Maybe we can roll back to previous version?
I'm having the issue with the missing voice to text on Gboard. It's also missing from lgboard and I'm not able to add it to the board under settings because the mic icon doesn't exist. I know gapps is the issue, but I have no idea why. Looking for a solution.
What solved it for me was signing up for Google play services beta and the Google app beta. Been flawless since.
I'm on a stock Verizon Google pixel. W/ unlocked bootloader. I started having this issue as well. Will try to see about the beta thing you mentioned.
The only short term solution I've found is restarting my phone. But otherwise it's really inconvenient.
Hasn't seemed I've been happening as much. But my Google assistant and or Google Voice search would freeze I would have to reboot the phone to get it to work again. I'm stock Verizon v20
Gotta be an issue on Google end. Hopefully they fix it soon