Hey guys, so I have a bose quietcontrol 30 that I wear around for work all day. It has a little button by the right earbud if you hold down it triggers google assistant which is great.
When I tell it to "Call John Smith, mobile", it works great up until the fact that it defaults to putting the call on speakerphone while my phone is actually still in my pocket. Assistant replies "Ok, calling John Smith mobile on speakerphone".
How in the world do I change this?
Thank you!
Related
I have the Incredible and will probably have to wait until the end of the year to see 2.2. I was hoping those of you lucky enough to have 2.2 could answer a question about 2.2.
Did Google fix the inability to hit the button on your bluetooth headset to trigger voice dialing?
Thanks!
Yes I believe so. Full Bluetooth support is now present which includes initiating from the headset. Can someone else confirm?
Sounds right. It also picks up the phone if it detects a bluetooth headset connect while the phone is ringing.
RogerPodacter said:
Yes I believe so. Full Bluetooth support is now present which includes initiating from the headset. Can someone else confirm?
Click to expand...
Click to collapse
Yes. Press the headset button and the screen shows sample voice dialing commands while the headset says, "speak now." You say "call John Smith", the headset says "calling John Smith" and dials.
It's a little different from the way it was on Windows Mobile, where the phone asked, "Call John Smith?" and you had to say "yes" or "no," but you can still abort the call using the headset button if the phone misunderstood your command.
I haven't used it much, but it's 2-for-2 for correct voice recognition on the test calls I made.
I searched and found only old information from last year on this...
Does anyone have bluetooth headset-initiated voice command dialing working with their Captivates?
If so, please tell me exactly how you are accomplishing this -- what bluetooth headset, what ROM, what apps, your procedure for initiating a call from your bluetooth headset.
I'm not interested in any procedure that involves looking at or even touching the phone itself. I need a solution that will let me place a call to the contact of my choice solely from my bluetooth headset -- just push the button on the headset, tell it who to call and reliably make the call to the contact and phone type (mobile, home, etc.) that I tell it.
I am currently using the new Andromeda ROM but would be very interested in hearing what new ROMs do this well.
Thanks!
I am running Paragon ROM and I am able to make calls through my car stereo via Bluetooth voice dialing. Leave the phone in my pocket, hold a button down on my stereo until the voice asks for a command, I then say "Call Contact". If they have more than one number it asks if I want to call them at home work or mobile. I say "Mobile". The voice then repeats "Call Contact mobile"
I am running Paragon RC5.1, but Bluetooth voice dialing has worked for me since I first flashed with RC3.
I thought I saw an app somewhere where you could activate voice search by saying "android" and then saying what you wanted to happen. I've been looking around and can't find it. anybody know the app or a similar one? I played around with vlingo earlier with their "hey vlingo" and didn't have great results.
Try this... https://market.android.com/details?id=com.pannous.voice.actions.free ...there's also Siri, Dragon, and Nuance...hope that helps a little...
Vlingo is nice. Works with headset and you can activate it by voice.
Sent from my GT-I9000
In a similar vein, I have bluetooth in my car and it uses the car mic to pick up my voice when I'm doing a phone call, but when I use voice search it just uses the phone mic and can't understand me. Any ideas why this could be happening?
Hello,
I have the Nexus 6 for the last month now. I was using the phone when I noticed that the headset buttons does not work.
If I press a headset button while I listen to music, it will not stop the music but instead it is going to open Google now commands.
Same issue when I try to answer a call.
I have tried several apps from the market, but none of the seem to fix the problem.
I have tried disabling the Google now, but when I hit the button, it goes to voice search again.
I think that the Google now only listens to the headset buttons and I want to fix it.
Can anyone help me fix it?
Thank you in advance.
PS: I have read and tried the things other threads was saying and nothing seem to work.
I can't really help but I am pretty sure it depends on the bluetooth device.
In 1 car when I push the call button (stand alone device) it forces you to make calls in a strange interface that only makes calls. It has a different put for play/pause
In my other car (built in bluetooth) it does google now (which in my opinion works a lot better) and then it has on screen play pause.
Sleeepy2 said:
I can't really help but I am pretty sure it depends on the bluetooth device.
In 1 car when I push the call button (stand alone device) it forces you to make calls in a strange interface that only makes calls. It has a different put for play/pause
In my other car (built in bluetooth) it does google now (which in my opinion works a lot better) and then it has on screen play pause.
Click to expand...
Click to collapse
I was referring for wired headset.
I have not tried it to a Bluetooth device .
Thanks for the answer.
I get this odd tapping/knocking sound when Ok, Google is listening for a command. It does NOT go away after I send a text via voice until I tap the mic icon again and tell it something like stop or **** off. It then says ok or whatever and the knocking noise that pulses with the mic listening .. will actually go away. It started after I updated Google App. I'm on the beta testers list.
I removed the Google App a cache and retrained the voice recognition again ... to no avail.
I'm using a Nexus 6P. It's got stock Android but is rooted with systemless root. Phone works fine except when attached to AA.
Beta testers list for what ?
I think "OK Google" on the phone is not intended to be compatible with AA.
When in AA you are expected to tap the headunit mic icon, or use the steering wheel control for mic to send a voice command through AA.
If "OK Google" works at all while in AA mode, that's more accidental than intentional.
mikereidis said:
Beta testers list for what ?
I think "OK Google" on the phone is not intended to be compatible with AA.
When in AA you are expected to tap the headunit mic icon, or use the steering wheel control for mic to send a voice command through AA.
If "OK Google" works at all while in AA mode, that's more accidental than intentional.
Click to expand...
Click to collapse
oops. Sorry. I meant tapping the icon and saying "Text <person>" .. the mic pulsates and makes this tapping or knocking sound. It was getting stuck. It like OK, Google seem to require a decent network connection to even function properly. I went back outside after I made this post and it worked fine. It still made the little annoying sound but didn't get stuck. I was driving down Highway 280 here in Northern California which runs between 2 mountain ranges and has always kicked me down to 3G/H from LTE. I think this was it but I'm not sure since the voice search is pulled from the phone through AA and it's done by Google App. And like I said .. I use the current beta so I thought maybe it was releated to the update for Google App from yesterday. I simply don't know. It was just irritating and I was hoping it wasn't just "oh .. you have a **** network connection in places so it's going to work kinda janky sometimes."
Thanks!!