For some reason lately, I'm finding that when using "OK Google," it'll only hear the first second or so of my query, and then stop listening and display results. So if I say
"OK Google, remind me to call Dave tomorrow"
the query will simply be "remind me" and it'll then prompt me what the reminder should be called etc etc.
Anybody know what's up with that? Running Android Nougat DP5 and the most recent Google App update.
I'm having the same problem!
Related
Hello there everyone,
when I ask my google voice stuff like what's the weather going to bve like, it does pick it up, but it doesn't respond, it just searches what I said on google, same for google now. Language is set to Dutch, however the language of my Voice search thing is said to english. It picks up everything I say like it should pick it up, the problem is it just ALWAYS searches.
Any help?
bump
Artego said:
Hello there everyone,
when I ask my google voice stuff like what's the weather going to bve like, it does pick it up, but it doesn't respond, it just searches what I said on google, same for google now. Language is set to Dutch, however the language of my Voice search thing is said to english. It picks up everything I say like it should pick it up, the problem is it just ALWAYS searches.
Any help?
Click to expand...
Click to collapse
There are certain keyword type questions that will cause it to reply to your question in a voice response like 'google define (whatever)' will get an audio response with a definition. I don't know all of the triggers that get audio responses but define is one of them. It's google now with audio that you are asking about, not google voice which is a separate app that does voicemail, etc through google..
Is everybody else's bluetooth voice dialing just god awful?
S voice is crap, so it's frozen. Google's Bluetooth dialer is just the worst thing I've ever seen. Has anybody found out how to get Bluetooth dialing working properly?
Why in the world can't they just make Bluetooth launch voice search?
Sent from my SAMSUNG-SGH-I337 using xda premium
switters1 said:
Is everybody else's bluetooth voice dialing just god awful?
S voice is crap, so it's frozen. Google's Bluetooth dialer is just the worst thing I've ever seen. Has anybody found out how to get Bluetooth dialing working properly?
Why in the world can't they just make Bluetooth launch voice search?
Click to expand...
Click to collapse
Old thread, but I'll revive it because I want to talk about the same subject. I agree with the OP, and I'm surprised how badly Android/Samsung handles blutetooth voice dialing. (My last phone was an iPhone 3GS, and voice dialing worked great from day 1 back with iOS 3 or 4, whatever it originally came with.)
I frequently use bluetooth voice dialing in my car, either from a headset or speaker phone. This is a must-have feature for me.
Svoice is completely unacceptable because it requires the phone to be unlocked. If you have to mess with the phone to unlock it, then that defeats the purpose of voice dialing. I do understand that Svoice can do other things besides voice dialing, things which should be restricted by the lock screen. What I don't understand is why they don't give the users the options to enable selected features such as voice dialing while the phone is locked. But they don't, so Svoice had to go.
With Svoice uninstalled or disabled, Google Search takes over the voice dialing duties. It works ok, or at least it used to with Google Search v2.x. One thing about it that I don't like is that it wakes the phone (activates the screen) when you initiate voice dialing, so you can end up with accidental screen touches while voice dialing (if you don't have a pass code, or if it hasn't timed out yet). The screen should remain locked.
In recent versions of Google Search (starting in v3.x?), they decided to make voice dialing worse! If a person has multiple numbers, you can not directly select one, you have to wade through a stupid menu every time.
Say for example I have a contact named Tim Brown who has 3 numbers: home, work, mobile
With Google Search 2.x, you can do this:
Me: Call Jim Brown Home (or I can even just say "Call Jim Home" if I only have one Jim in my contacts)
Phone: Do you want to call Jim Brown at home? Say OK or Cancel.
Me: Ok
Phone: dials
With Google Search 3.x it ignores the location and always presents a menu:
Me: Call Jim Brown Home (the word "Home" is ignored)
Phone: Say Select 1 for Jim Brown Home, Say Select 2 for Jim Brown Work, Say Select 3 for Jim Brown Mobile, or say Cancel
Me: (If I can remember which freaking number was Home) Select 1
Phone: Do you want to call Jim Brown at home? Say OK or cancel
Me: (Yes I do, you stupid phone, I just told you so!) OK
Phone: dials
What a pain in the butt that is. Ironically, if you open Google Search by launching the app (i.e. by interacting with the screen), then it will listen to the "Home" part. It just ignores it if you are voice dialing, which is where you really need it. Does anybody from Google actually use this stuff?
My solution is this. Since my phone is rooted, I have the option of uninstalling Google Search v3.x, find v2.8 on the Internet, and install it on my phone. Then be sure to ignore any updates in the Play store. This works good enough. I can select a specific number when voice dialing, and I can voice dial while the phone is locked. It still turns on the phone screen when I voice dial, but I can live with that.
Note that I don't use Google Now, so I don't care about any new features that are included in the newer versions of Google Search. If you do use Google Now, this solution may not be acceptable to you.
If anyone else has a better solution, please share it.
Thanks
I tried using the Bluetooth Launch app to activate google voice search instead of the voice dialer, but that didn't work while the screen was locked. So for now, I'm sticking with the solution mentioned above (i.e. using google search v2.8).
Hello XDA,
For some reason, I cannot seem to make calls using the ok google function anymore. When i say "ok google call john", it will correctly bring up john and the progress indicator for starting the call moves across the screen and then it goes to a transition animation as if opening the dialer, and then goes back to the google now screen with the call progress bar again. I've tried clearing the cache and data for the phone app and have tried clearing cache and reinstalling the google app. Has anyone encountered this issue? It was fine on kitkat but seemed to start having issues after i updated to lollipop. Does anyone have any suggestions on how i can fix? Thank you.
So I found out the reason, it is because I use google voice as my default number and have the setting turned on to use google voice for all calls. So it seems to bug out when you use the "ok google call" command with google voice. Sent in a bug report to google. not sure if this is a google thing or a samsung thing that needs to be addressed! but in case anyone else has his problem, this is why!
Hi,
I'm wondering if it's possible to make an app that will catch a specific number if called and route the audio to other apps like googe voice search or s-voice. My one pet peeve is when I'm driving I can't start google voice search without interacting physically with my phone as the majority of autos I've seen like ford sync and subaru's off label BT systems have no way for you to do this built in. My idea is to design an app that puts a contact in your phone so you can just say "Call Google" or something similar and your car will initiate a call with the phone, but to have the phone not actually connect to the cell network but after call has been placed you hear the familiar "beep" of voice search. You know, like on windows phone you can say "Call Cortana" and she'll pick up. Or is that a special API only in windows phone?
There is Google Now Launcher,developed by Google.You just need to install it,and use it as your launcher.When on the launcher screen just say "OK Google" and it will open the voice search.You can also set it to detect "OK Google" from any app,if your device supports that.
The problem is that your device's screen needs to be on,not for all devices,but there are not many that support detecting the "OK Google" phrase with the screen locked.For more commands you can simply install Commandr , also a free app.
Hope I helped.
I have a Nexus 6P running the latest version Android 6.0.1. However, it is very odd that I never had this issue with my Nexus 6.
I have a car that just has a simple phone button (Bluetooth) to press which makes a sound and at that point I can simply say something like "Call Tom Brady". The phone usually uses my Verizon network to call the contact without any problems. I have been noticing that for a lot of my contacts 'Google Now' is trying to call them via Google Voice. The phone literally says calling so and so via Google Voice and then never connects. I don't know if this is because these contacts have a Gmail account or what, but it is very annoying and it never ends up connecting.
I bet if I uninstall the Google Voice app everything would work, but I need it for my visual voice mail.
One thing I have already tried is in the Google Voice App settings change it to 'Do NOT use Google Voice for any calls'.
This did not fix the issue.
Is there any Google Now settings or Google Voice settings that anyone can think of that might help me here?