Anybody having issues with hey Google? When I say it my phone hears it and the little assistant pops up at the bottom.. but then I have to press the microphone picture to use it instead of just talking like I have with every other phone I've had since that feature came out. IDK what I can do to fix it.
Related
I don't know if this is done by design or if this is an annoying bug, but I was wondering if it happens to other people, too.
After completing a voice call using Google's Voice actions, does everyone else get a "Did you mean..." box left on the screen?
Am I the only person that has seen this?
Sup All,
forgive me for the easiness of this question but Ive been looking for a while and cant find an answer. Its definitely different on ICS, than other/all android builds. So, is there a way to prevent voice actions from being enabled when you press the button on a blutooth headset? Even a way/app to reprogram the button press shortcut? I was listening to a podcast, pressed the headset button to pause it but I guess I double pressed it or something and it opened the voice actions window, which I wasnt paying attention, mumbled one word and it called an ex. SWEET! I hung up and am pissed this is a "feature", as, Im sorry, the voice actions alone are not that up to par, and on bluetooth, theyre atrocious. Any ideas? I like and use the google search button but Im not very impressed with the dictation of text messages, etc. The voice recognition just does not seem to be up to par, Ive gotten some pretty "are you kidding me?" results when trying to text via voice. But of all things, I dont want to use the whole "call blah blah blah" feature, or any voice "actions" over bluetooth. I want to keep voice search (like only for web searches, etc) but I dont want my phone to interpret what I say and then dial the non-appropriate number. Any apps to reassign the voice actions button or just disable it as a whole? I love the GNex but this ruined my night and Ill die happily if I can have bluetooth in, press the one button and not be worried that its gonna dial someone. Also, Im using a bose BT2, so it doesnt have all the nifty apps like a jawbone or what not, but I like the call quality. Im pretty sure a jawbone has an app that can change the hotkey presses but thats not applicable to me.
Hola -
I love my 5X and it's been great until lately...I'm getting erratic behavior (or behaviour if you're in England).
The first issue is that when I have my earpiece connected (Samsung HM1300) and say "OK Google", the phone wakes up, the Assistant appears but then immediately stops listening .... the balls dance for maybe 1/2 second, then the Microphone icon appears instead and then I have to press Microphone , which ruins the hands-free paradigm of Google Now.
The second is that I once had the brilliant idea (when I forgot my earpiece) to say to the Assistant: "Call Stephanie on mobile, and put it on speakerphone". Google dutifully repeated "Calling Stephanie on mobile and putting it on speaker" and did so. Since then, half the time I make any phone call using Assistant, it puts it on speakerphone regardless of whether I ask it to. I won't even say a word remotely resembling "speaker", e.g. "Call Juliet on mobile" returns me "Calling Juliet on mobile and putting it on speakerphone". I then have to take my eyes off the road and switch from Speaker to Bluetooth.....
None of these problems existed a month ago. I've used the HM1300 for over a year.
I don't have trouble with the Assistant when Bluetooth is disconnected - the Assistant listens for a second or two before giving up.
Is there a cache I can clear or something?
TIA
I just noticed it earlier today and wondering why I'm not getting a chime when I say "hey google" or press the assistant button.
orlans21 said:
I just noticed it earlier today and wondering why I'm not getting a chime when I say "hey google" or press the assistant button.
Click to expand...
Click to collapse
Dude, i have the complete opposite opinion/Outlook of this. The chime is so incredibly blaringly loud. I have been wanting to mute it. But the only it appears to be mutable is of you turn off ALL and any sort of accessibility settings or options.
I guess I've answered your question lol. Enable some sort of accessibility option, and that horrendous ding will come back lol.
Burt Squirtz said:
Dude, i have the complete opposite opinion/Outlook of this. The chime is so incredibly blaringly loud. I have been wanting to mute it. But the only it appears to be mutable is of you turn off ALL and any sort of accessibility settings or options.
I guess I've answered your question lol. Enable some sort of accessibility option, and that horrendous ding will come back lol.
Click to expand...
Click to collapse
I know you can turn the chime volume down. I think it's the media volume but I turned mine up and still no chime
yeah, no chime for me either. I dont know how to feel about it. it is loud and annoying but without it i dont know if the assistant heard me
The Pixel 6 series support continued conversation, where the Google Assistant continues to listen (hence no sound cue while it continues to listen despite how many ever times you trigger the keyword since mic is already busy listening) for a brief period after you complete the first Hey Google + command sequence
miravision said:
The Pixel 6 series support continued conversation, where the Google Assistant continues to listen (hence no sound cue while it continues to listen despite how many ever times you trigger the keyword since mic is already busy listening) for a brief period after you complete the first Hey Google + command sequence
Click to expand...
Click to collapse
But what is it listening to if I'm not talking to it
Does anyone know how to make the Assistant do the chime when it starts listening? Not a single result of my searching has worked. The most promising says enable "Switch Access" which doesn't seem to be present on our devices.
I really need this so I know when my phone hears me while driving - half the time the "Ok Google" command isn't heard and I have to say it a second or third time. Obviously I'm not looking at the screen so an audio queue is needed.