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.
Related
I just got a galaxy nexus a week ago, this is my first android phone coming from an iPhone so please excuse my ignorance if this a basic question.
I quite like the voice actions when you hit the microphone icon, however when I connect to Bluetooth and initiate the voice calling through my Bluetooth device, the voice action doesn't activate, but some other voice dialer that is nowhere near as accurate as the voice action starts up.
Is there a way to get the voice actions to work with Bluetooth. This is rather frustrating as I really needed the usability of this to work while I'm driving. I don't need the voice actions when I can type.
Please help....
Many thanks
This is the same as in Gingerbread, I wish they'd use the same voice search for both, the non-BT one is much more capable.
Thanks that really disappointing, seems like a rather obvious function to have. All the capabilities are there , yet now the hands free system is not usable. Still don't understand why google didn't put this in place.
Seems like bluetooth fixes and modifications are coming with 4.0.3 update (which seems to be coming soon). Hopefully these issues will be addressed.
Still nothing...
I'm on GNexus 4.0.4
Nothing!
I CANNOT believe that something I could do on Windows phone 5, before the G1 was released, is still not available in Android.
Love Android, love my GNexus, HATE the fact that they still can't get voice command/dial to work over the bluetooth mic.
I've been fighting with this for quite some time. If you're willing to spend some for a solution, try checking on AVX on the market. It's paid, and kinda high, but it has a longish, fully functional trial, and it works flawlessly with Bluetooth. It also uses Google's voice recognition engine.
I haven't fully tested out how it voices dials, as I got it to interface with Tasker, but it might do what you need, and a fair bit more. After installation, the first time you hit the voice recognition button on you Bluetooth, you get the "open with" prompt on your phone which will let you choose to always launch AVX with your button.
Kinda stinks to not have a free solution out there, much less built in to android, but for now, this works for me. (It was completely worth it to start my car from the middle of a store by touching my ear and talking to my android. )
Before this last week, I was able to connect my Galaxy Nexus (GSM model) to my XPLOD car deck, select BT Audio on the deck, press the button, and receive a voice prompt to make a call. It was very convenient for when I had to make a call while driving.
Some time during this last week, the feature stopped working. When I press the button on the deck to initiate a call, the screen flashes gray (like the background of the voice dialer prompt), then returns to the previous screen and I hear no audio prompt.
When I try to make a call using my Bluetooth headphones (LG HBS700), the phone does the same thing (flashes the Voice Dialer, returns to previous screen--like a force close), but I still hear the prompt and can respond and make a call. But when I try to make a second call, there's no response--no flash of gray, no prompt, nothing.
I installed the TeamSpeak open beta app recently, but thought I had made a call using my car audio deck after. It's worth noting that the TeamSpeak app includes permissions to pair with Bluetooth devices. Unfortunately, even after uninstalling the TeamSpeak app, I still experience the same issue.
I can't think of any other changes I've made that might affect voice dialing and all my searches (the last 45 minutes) don't turn up anything related to my issue.
Could someone here offer a fix or point me in the right direction?
Using the Voice Dialer prompt while driving is a wonderful convenience (and a major safety feature as well) and I really, really, really don't want to have to wipe and reload my phone to get it back.
Okay, so it turns out that a recent (April 3) Google Search update is at fault.
I uninstalled Google Search updates (Settings > Apps > Google Search > Uninstall Updates) and it fixed the issue (though it reverted it to the buggy but less buggy version of Google Search that came installed with my phone).
I had the same issue but nobody chimed in on my thread. At least I know I'm not the only one with Google search update issue with Bluetooth. Thanks for posting your issue. I ended up uninstalling update as you did. I actually ended up going back to stock ROM before I figured out it was search and not the ROM.
Sent from my Galaxy Nexus using xda app-developers app
I've got similar issues. Pressing the button on my earpiece results in the Voice dialer prompt but only through the phone's earpiece and not through the Bluetooth earpiece. Voice commands can only be spoken to through the phone's mic also and not the Bluetooth mic. If you have your phone in your pocket and you shout loud enough, the phone's mic will pick it up and the call will subsequently work through Bluetooth when it connects.
Things were fine before but something screwed it up.
I just tried uninstalling the Google Search/Now update like the OP and it works again. So definitely Google Search/Now is the culprit.
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.
I am having trouble getting my AppRadio 3 to issue voice commands through the car microphone to my Verizon Galaxy S8+. It works fine for during phone calls, but I cannot press the command button and speak instructions like I could with my LG G3. I've scoured the Internet and cannot find similar issues, so I don't know if I'm just being stupid or there is there a known issue that I just haven't found people complaining about.
Things to note:
* Hands-free is set to be allowed for Bluetooth devices
* Speech output is on
* Bluetooth headset is allowed to record audio
* OK Google detection is enabled any time with trusted voice, though that is not how I am enabling Google Assistant since the microphone will not work to transmit voice.
Is it possible that my car head unit is old enough that it is no longer compatible with all of the BT features that the Samsung phone requires? Perhaps Bixby is causing problems and I need to disable it entirely (I am not rooted at the moment, so I am not sure how I can disable it.) I'm nearing the 14-day return period with Best Buy, so I will have to return the phone if I cannot get this resolved to at least blame the head unit since it is a major deal breaker and basic phone function that does not work.