Related
Maybe this should be posted on a car forum (actually tried that and never got a response). But i was hoping someone might know of a way where i can by pass the voice control built into the radio of my kia soul, and instead just use the voice control built into android but using the BT mic and speakers in the car? i.e. have the bt system in the car act like a bt headset
Not entirely sure its possible.
Your BT in your vehicle is trying to use voice commands to control your phone, and you would rather use the IN PHONE voice commands and not allow the KIA to control your phone.. right?
Aside from using the audio input feature and allowing the phones mic to operate.. i dont think its currently possible.
right - i want the car to be dumb and just relay everything to/from the phone without trying to do anything itself. Right now when i connect the phone to the car, it downloads a copy of the phone book and i dial by telling the car who i want to call and it then tells the phone to call them.
Man if there's no way to disable the car's voice controls, that's incredibly short sighted of whoever makes the BT system in the car. I guess it's too much to hope that they even considered making the controls updatable through USB or something huh?
Hey there!
Even though i don't use it, Google voice actions is tragic on my GN. And I'm assuming it's to do with my primary mic.
If i launch Voice Actions via the search bar or within Google Maps, it doesn't hear me unless i squash the phone right up against my face.
If i launch the voice feature via the keyboard (messaging app) it will listen and interpret me in an instant! (works so well!!)
I'm aware of the two mics in the GN and I'm assuming it's 2 different microphones being used for these two functions, respectively.
Is there any solution out the to get the better microphone to listen when launching Voice Actions?
(Note: I've received my GN as a long-distance present, and i doubt i can pull a warranty claim here)
jocalderone said:
Hey there!
Even though i don't use it, Google voice actions is tragic on my GN. And I'm assuming it's to do with my primary mic.
If i launch Voice Actions via the search bar or within Google Maps, it doesn't hear me unless i squash the phone right up against my face.
If i launch the voice feature via the keyboard (messaging app) it will listen and interpret me in an instant! (works so well!!)
I'm aware of the two mics in the GN and I'm assuming it's 2 different microphones being used for these two functions, respectively.
Is there any solution out the to get the better microphone to listen when launching Voice Actions?
(Note: I've received my GN as a long-distance present, and i doubt i can pull a warranty claim here)
Click to expand...
Click to collapse
I also just noticed this. I'm on AOKP ROM so I was wondering if it is a ROM issue or GN issue in general.. I use this feature a lot and have never had an issue with any of my phones in the past until now.
i highly doubt its a rom issue...coz if i remember correctly i had the same problem even when i was on the stock rom 4.0.2
I don't know if this will go anywhere, but I opened this bug report:
http://code.google.com/p/android/issues/detail?id=29092&thanks=29092&ts=1334760990
Please star it if you are experiencing this issue. (Only add a comment on there if you actually have new info - don't say "me too".)
I ahve this issue but during a call when i switch to speakers the person i speak can't here me...in normal mode all is ok he can hear me in good conditions but switching again in speakers mode can't hear me.
I'm on AOKP B32 with Franco Kernel 135 now but i try with others rom and kernels and same issue.
I love Android, but very often I also hate it. Recently I was interested in getting this Bluetooth receiver for my car. The ideal scenario would be to be able to make calls, play songs, and navigate to an address by only pressing the button on this device on my dash and speaking, not touching the phone at all. Sounds great, right? And isn't this what Google Now and its voice actions are all about?
Well, seeing what a sorry state Bluetooth is in on my GNex, I think a device like this would be just about worthless. I have experienced no less than FIVE separate issues in attempting to get this scenario to work with the regular Bluetooth headset I currently own.
1) Bluetooth device disconnects every time I turn screen off. So when I turn screen back on, I have to re-pair the device.
2) The basic functionality of using Google voice actions over Bluetooth at all only works once. After that, it beeps, and then reverts to the handset mic and speaker. If you force stop Google Search, it will work again, but only once.
3) Pressing the button on the Bluetooth device activates old-school voice dialing instead of Google Now voice search. What's the point of this now that Google Now exists? I believe I have fixed this with the Bluetooth Launch app, but we'll have to see if it keeps working.
4) Music quality sucks, as we all know.
5) Google Now voice actions themselves are spotty. Sometimes advertised voice actions just result in regular searches instead. Sometimes it keeps listening for more input even though I've stopped talking, a force stop is required to fix this.
About the only thing that does work over Bluetooth is just regular calls that you initiate via the phone.
Which of the above issues do you experience, and can you share any workarounds? At this point, I honestly don't know what justification Google could give me to use this junk over an iPhone. I seriously believe they do not test anything, and do not care at all about their customers' experiences.
I have my Gnexus running 4.1.2 connected directly to my car's Bluetooth. I use it mostly for music and GPS, then calls sometimes, but rarely Google Now.
1) Doesn't happen to me ever. My phone stays connected until I turn the engine off and pull the key out of the ignition. I heard Bluetooth connection issues started with 4.2, hence why I haven't updated.
2) Not sure about this one. Google Now has always been spotty in my car (takes over 30 seconds to start up) and I'm not sure if it's because of Bluetooth or T-Mobile.
3) I think that's normal. Pushing the call button on my car's steering wheel activates my car's voice recognition system, not the phone's.
4) I use BT most often for music via Pandora and it sounds sounds fine to me. Occasionally there is a subtle skip, which I attribute to the wireless nature of Bluetooth. I would say the quality is 90% compared to wired.
5) Agreed. That seems unrelated to Bluetooth though.
I don't think there is a Bluetooth command for starting Google Now. Don't forget Bluetooth is a generic technology that is supposed to work with all phones, not just Android ones. I used to connect a Sony Ericsson phone for calls.
Except for accepting incoming calls and changing tracks/volume, I still have to initiate most actions by touching my phone. It sucks. Let me know if you find a good solution.
Sent from my Transformer TF101
Yeah, it seems at least some of these issues (the disconnecting, music quality) started in 4.2. #3 might be "normal", but is definitely not how it should be. You mention Bluetooth is a generic technology - this is true, but there doesn't need to be a special command for Google Now, the phone can just choose to respond however it wants to the standard "call" button/command. For example, with an iPhone, pressing the button on the Bluetooth device will activate Siri. Then you can speak any command or query you wish. There's no reason Android couldn't activate Google Now voice search in the same way, instead of the voice dialer.
I've been doing things same as you, doing everything via the phone except for answering calls or redialing the last number. I finally realized how useful voice commands could be when able to be summoned via Bluetooth. A couple simple updates to the Google Search app, and an improved Bluetooth situation in 4.3 could easily clear all this up. But after the many mistakes they've made, I'm not exactly holding out hope.
The newest Google search has an option to listen over Bluetooth in settings not sure what it does.
Sent from my Galaxy Nexus using xda app-developers app
tshelby73 said:
The newest Google search has an option to listen over Bluetooth in settings not sure what it does.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah....all the issues I stated above are with that option checked.
xdp said:
Yeah, it seems at least some of these issues (the disconnecting, music quality) started in 4.2. #3 might be "normal", but is definitely not how it should be. You mention Bluetooth is a generic technology - this is true, but there doesn't need to be a special command for Google Now, the phone can just choose to respond however it wants to the standard "call" button/command. For example, with an iPhone, pressing the button on the Bluetooth device will activate Siri. Then you can speak any command or query you wish. There's no reason Android couldn't activate Google Now voice search in the same way, instead of the voice dialer.
Click to expand...
Click to collapse
Ah yeah, that's different then. None of the buttons on my car will activate any sort of voice recognition on my phone, because of the voice system in the car itself. Which sucks, because although it may have been advanced in 2009, smartphone voice tech has surpassed it by leaps and bounds, whereas my car software will never get updated.
So I think there's a better chance for an update to make this work for your setup than mine.
Sent from my Transformer TF101
tshelby73 said:
The newest Google search has an option to listen over Bluetooth in settings not sure what it does.
Click to expand...
Click to collapse
Thanks for the tip!
I also added a Google now voice command short cut to my lock screen and launcher, so when I'm in the car I can quickly (hopefully) say a command.
Kind of sucks still that the call button doesn't do this, even my old school slider Nokia launched voice commands over Bluetooth.
LOL
I use mine and will do voice commands by pressing button. It will not search though just make calls. On CM based ROM'si have to freeze the voice dialer the ROM comes with or the cm dialer is default. I don't have the listen over Bluetooth checked. Maybe that checked would give me search feature using button.
Sent from my Galaxy Nexus using xda app-developers app
Well, I dug myself a hole by allowing the OTA to 4.3.
On my AT&T S3, SGH I747, I was running 4.1.1 stock rooted, with a toggles mod, and the At&T update got pushed to the phone one night. It could not get past TWRP so I swapped back to a stock recovery. The update ran again, and failed at about 25%. I didn't think anything of it since the phone worked fine, until I discovered that I could no longer change the icons on the lock screen (settings would stop working). So, I installed Kies (which it turns out will not connect over a USB 3.0 port, but thats another wasted couple of hours and another story) and backed up my accounts, settings, etc.
I then flashed to a stock 4.1.1, and then allowed the OTA update to 4.3. This time it went (Yay..sort of).
So, I'm looking at the new features, and finding some useful and overall enjoying thew update, but ran into trouble with S-voice and bluetooth, specifically, the microphone in my car. This used to work. I could press the mic button on the cars Nav unit (Parrot BT) and I could say "call "X" mobile" or "play Concrete Blond" and the phone would do what I told it to, more or less.
Now, It will not connect to the mic, I get a brief message "Check in-car audio" and after 3 seconds the car reverts to playing music (it mutes when you press the mic button). The other BT functions work. My contacts are transferred, I can force music to the unit, I can place calls and we can hear each other, etc.
After a bit of reasoning, I began to zero in on S-voice as the culprit. I confirmed this by installing Bluetooth connect and pointing to Google search when the mic button is pressed. This allows me to make calls via voice command, but that's all.
I used this feature a lot., probably 3rd or 4th down on my priority list, after phone and camera. I'd like to use it again.
Here are my options as I see them.
-Leave well enough alone and wait for Sammy, or my Navs mfg to fix their stuff and use google search instead for now. (Will they do it faster if I hold my breath?)
-find a 3rd part app to make S-voice do what its frikken supposed to do. (Not sure if their is one)
-find an older version of s-voice and install it over the current one, which may or may not work. This would require that I have a working backup plan in place and since I understand that the bootloader I now have (MJB) is a one way trip, this limits my options. (can't flash back to 4.1.1 and don't have a 4.3)
So... does anyone have..
-any sympathy? (It's Christmas day)
-a solution to my problem?
-a recommended app to patch this?
-an older version of S-Voice form a S3 phone?
-info on any of the 4.3 roms floating around (can they be installed over a stock 4.3?)
I'm having the same problem. I didn't know S-Voice was broken until I did a factory reset last week to fix problems with T-Mobile wifi calling. I had been using Utter! for voice control, which has pretty good voice recognition, but randomly stops working with bluetooth. Since I hadn't tried S-Voice for a long time, I wanted to see if there had been any improvements. Once bluetooth is connected, the S-Voice mic button is disabled and the bluetooth button has no effect on it. I may end up going back to Utter!. Unfortunate, since almost every option except S-Voice is just too open-ended for use in the car. I don't want to ever be required to look at or touch the screen. For all the complaints I have seen, nothing can top Sync in my Ford. Voice recognition is excellent and everything can be done by voice.
well, I'm glad at least I'm not the only one. after some experimentation, I bought an app called Klets, which works with specific music players, Poweramp being one, so I got it as well. I had no luck with utter.
Klets works using google's voice recognition engine and works well. You can add custom commands to the already huge list it has. Well worth 2 bucks! Like all VR apps, it has issues with background noise. It is also written by an Italian, so some of the translations are a bit off. When calling a contact, you get "I'm starting to call towards (contact)"
Poweramp also has the advantage of boosting the volume a bit, which helps with the car since the input volume for BT is set so low, or BT output is low. Either way, it helps. Plays FLAC too.
Has anyone tested the microphone on their bluetooth sets yet with the Pixel 2 XL?
I'm scared I might have a defective phone. My bluetooth headset connects to my phone just fine, and even plays audio just fine, however, the microphone is not picking anything up. This means I can't use hands free calling, or hands free Google assistant.
I know it's not my bluetooth device because it works fine when connected to my older phone (Nexus 6P)
Has anyone else had trouble with doing microphone over bluetooth? I'm not sure if I need a replacement or just a software patch.
For reference, I use the LG HBS-1100 bluetooth headset.
http://www.lg.com/us/bluetooth-headsets-headphones/lg-HBS-1100-Silver-tone-platinum
Later today, I will try a different bluetooth device.
EDIT: I tried with my older pair, the LG HBS-750, same issue.
I've got a soundbuds tag headset, the connection speed is faster and my phone calls seem ok. I've only made like 2 calls so far though.
@Traceguy I've had several lg headsets and they all sucked. No could hear me or I was breaking up all over the place. Switched to the jaybird x3 and it's been perfect ever since.
Disclaimer: I'm on a Nexus 6. Waiting patiently for the 2XL to arrive next week...
I've talked with Google support, they helped troubleshoot, but nothing could be found out of the ordinary, and it's now being elevated to the next level support team. They have my phone number and will call me back when they find anything.
My Bluetooth version is up-to-date, but there is a update pending for my Pixel 2 XL, which hasn't made it to my phone yet. That may or may not help. IDK
I will get a friend later today to connect his bluetooth to my Phone and test the mic. Maybe it's a total LG issue.
I'm gonna say it's an LG issue. I went through 4 pair of the infinium headsets. All had issues with ppl hearing me. Even when paired to different phones.
Larzzzz82 said:
I'm gonna say it's an LG issue. I went through 4 pair of the infinium headsets. All had issues with ppl hearing me. Even when paired to different phones.
Click to expand...
Click to collapse
I don't know much about how Bluetooth works, do Bluetooth devices use drivers similar to USB devices? Maybe the Pixel 2 XL is missing the necessary drivers for the LG HBS sets. That is something that can be fixed with a software update.
It's not an LG issue. It's happening with my car's head unit and others are reporting it in the Pixel User Community. This is one of a few strings that include it. https://productforums.google.com/fo...pPfDGvkNw;context-place=forum/phone-by-google
robsw said:
It's not an LG issue. It's happening with my car's head unit and others are reporting it in the Pixel User Community. This is one of a few strings that include it. https://productforums.google.com/fo...pPfDGvkNw;context-place=forum/phone-by-google
Click to expand...
Click to collapse
I'll just wait patiently to see what happens. I'm hopeful it's not a hardware defect with the bluetooth chip in my phone. I never use bluetooth car's head unit, for whatever reason it drops every few seconds or minutes. I'm driving a 2013 Charger, so I'd expect better results. I use aux, and thanks to the USB-C Dongle, I am not stuck without a way to play my music in the car, though without the microphone input from my headset, I can no longer tell Google which song to play.
I just came here to check.
I can place calls and be hear over bluetooth both on the car and my Sol Republic headphones.
Assistant can not hear over either. Assistant does work over a wired headset.
Support had me boot into safe mode, spoiler: Assistant won't even launch in safe mode, and factory reset which did not fix the issue.
They have no resolution at this time, but are looking into it and wanted me badly to leave feedback on the problem. I'd suggest anyone with the problem leave feedback as well.
At least I'm not the only one. They said I'm the first to call. ut then again they also said it coud be a hardware issue which I just can't see.
Mine, too. I have a Pioneer head unit. Playing is fine, Assistant is fine when not connected to Bluetooth, but Assistant just will not work over Bluetooth. I use this all the time so it's already driving me crazy and it's only been one day. (Same head unit worked fine with previous phones... Pixel 1, Nexus 6p, and OnePlus One.)
I'll add myself here as a +1... Same symptoms. Seems like microphone over BT doesn't work.
I have a Plantronics v5200 and it works for calls. But not for assistant. Sucks......it will activate assistant on a long press. But registers no sound. Works perfect on my original xl. So it's not the headset.
Also confirmed that it WILL work just fine if I launch it with "OK Google" instead of a squeeze or button. So it can work... Starting to seem like a bug in Assistant, which makes me hopeful for a decent fix.
@Anaelith Yes, but did you enable bluetooth Mic input from settings? If not, saying "Okay Google" will use the internal microphone in the phone instead of using bluetooth.
Go to Google Now settings > Voice > Enable "Bluetooth headset". This option "Records audio through Bluetooth headset if available"
That aside. I have tried bluetooth mic in a phone call and it works. I also tried Bluetooth audio with my Car's head unit and have not received a single drop. So the drop problem was related to my Nexus 6p.
Seeing as the mic works for phone calls, the problem seems to truly be software related.
Using a Jabra Eclipse, all settings correctly enabled. Not only does the Google Assistant not work, but neither does voice texting.
Worked fine on my original XL, so I know the earpiece is good.
Guess they better look into this...
Works fine on calls, won't work on assistant.
Man, I'm just gonna get my phones six months after release. It sucks to have to debug all this stuff for Google.
[UPDATE] I wrote here and I have a smaller pixel 2, but I have this issue too.
I'm another one. None of my Bluetooth microphones work on the pixel 2 XL, but do on my 6P
Hi everybody I think I may have found a possible fix/workaround
Settings\search\voice\Ok Google detection
Turn on ok Google anytime turn on trusted voice
(May have to do voice training)
Now when I press the call button and say "OK Google" then the command I hear it in my headset and it works. If I don't say ok google it doesn't work. It may be that it's actually my phone picking it up and not the Bluetooth mic but I hear the audio in my headset and can use it to search Google and play music. And it also picks up my audio in calls
I am on a regular pixel 2
Nealian said:
Hi everybody I think I may have found a possible fix/workaround
Settings\search\voice\Ok Google detection
Turn on ok Google anytime turn on trusted voice
(May have to do voice training)
Now when I press the call button and say "OK Google" then the command I hear it in my headset and it works. If I don't say ok google it doesn't work. It may be that it's actually my phone picking it up and not the Bluetooth mic but I hear the audio in my headset and can use it to search Google and play music. And it also picks up my audio in calls
I am on a regular pixel 2
Click to expand...
Click to collapse
I tried that.no go.. quite frustrated with this right now. Never realized how much I use this feature.
Sent from my Pixel 2 using Tapatalk
I am facing the same issue. When connected to my BT headset or car BT, it's like my mic mutes after the hot word. Also, some phone calls can't hear me at all. Have to hang up and call back, then no issues. I've also contacted support and sent in feedback with system info to create a ticket.
I was having different issues as well, so I wiped my device and manually put all of my stuff back on (vs doing a restore), just to see if this fixes anything. Haven't retried BT yet, but will this evening. Other issues appear to be gone and the phone feels a lot smoother since doing this though. I think my restore from my OG Pixel didn't go so well.