[Q] Google Now still not listening on Bluetooth - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I'm hoping someone here has a bit of magic mojo that can help me get my S3 with the S3Rx 2.2 ROM (4.1.2) with the Faux123 kernel working with Google Now. I've read every thread I can find, but I still can't get GN to pick up commands via a Bluetooth headset. Using Bluetooth Launcher from the app store, I'm able to launch GN. The "beep" that signals GN is listening is coming through the headset, but it's not picking up what I'm saying. The circle around the mic icon doesn't move, which I'm assuming means it's not picking up any sound.
First, does anyone actually have this working, and please share how you did it.
I really like the TW interface along with motion, smart stay, the lock screen, and other features, so I would prefer to not switch to an AOSP ROM.
Help?
Best regards,
Mike

Related

[Q] BlueAnt V1 Headset + Evo

Trying to find some feedback from anyone using the BlueAnt V1 bluetooth headset with the EVO.
I'm having problems with the headset not answering calls maybe 85-90% of the time. It announces there is a call, but will not answer via voice command or hitting the button. I can answer via the phone but when I do it doesn't transfer voice to the headset. The headset thinks it is connected because when the call is ended it tells me.
Have done two factory resets on the phone and resets on the headset with no change. Also spoken to Blueant tech support and they weren't much help. All they said is they haven't heard of it having problems with the EVO and should be compatible with all Android devices. Their suggestion was to try it with another EVO and see if the problem still exists. Well, I don't have another to test it on so that does me no good. This headset worked great on both my Blackberry phones before I got the EVO and has the latest updates installed.
BTW...I'm running Myn's RLS4 w/ #17.
Thanks.
Well I don't think it is the Bluetooth , it is the Rom. I have problems with myns #4 with the sync in my email. I have a blue ant also and it does the same thing . I have tried other roms including virus and it works on them , try that .
sent from the phone that is EVO
Pretty sure I tried this headset when the phone was stock and with some other Sense and non-Sense roms. It has never worked properly.
Not sure if it has something to do with the lockscreen or not. The first time it is connected to the phone it works fine. But every time after that, it doesn't connect the call.
I haven't had any problems running anything on Myn's. But just to make sure, when I switch a rom again I will reset and try the headset.
yeah mine does the same thing, it works if i answer w/ voice command but if i press answer button most of the time the audio is route to phone speaker......Lame!
has anybody with a blueant tried it with cyanogenmod? i wonder if the different bluetooth stack yields different results. I'd like to see an app update for the blueant software too (had a cheaper headset that stayed connected way better)
When I pair the headset, it connects and works great the first call I get whether using voice command or button to answer. Then every time after that, it won't connect the call.
Maybe it has something to do with the lockscreen or the phone going to sleep. I will have to do some trial and error.
Currently I am trying out the headset with MikFroyo 4.2 (Sense rom) to see if it makes any difference. This rom is really close to stock so maybe it will work?
I will post back with my conclusion.
My headset works fine now. I have found there is a coding issue that exists in certain roms such as Myn's and CM that prevent proper operation. CM seems to have put together a fix for it. Myn's still does not work at this time. It has been requested as a fix for RLS5 final.
Running eVoKINGS Black Titanium with Mik's 4.2 base and my headset works good.
hey where is the fix for CM or is it just in some of the versions? cause i just flashed CM7 and some of the features i loved about the Blue Ant before are not working like it will not play my audio like it did before i use to be able to listen to my music and what not through the blue tooth. if there is a fix for it i would love to get that working again.
jbrazee said:
hey where is the fix for CM or is it just in some of the versions? cause i just flashed CM7 and some of the features i loved about the Blue Ant before are not working like it will not play my audio like it did before i use to be able to listen to my music and what not through the blue tooth. if there is a fix for it i would love to get that working again.
Click to expand...
Click to collapse
Sorry...it's been a while and can't remember where I read about the fix. If I run across again will let you know. Might try downloading "BT mono" from the Market to see if that helps. Not sure if it is effective on AOSP or not but worth a look.

[REQ] Fix for Call Audio through car speakers while docked

Very frustrating. I bought the Samsung OEM Navigation Vehicle Mount for the T989.
While docked, media (music and videos) play through the car speakers as expected. However, if a call comes in, the Call Audio only comes in through the phones speaker and not the car speakers.
From what I have been reading, it has to be fixed in the kernel somehow or baked in.
Currently, I am running Darkside Digital Warfare v2.4. I have tried all of the other roms including stock ones. I am open to using whatever rom has this fix or can flash the fix via kernel or whatever.
I am just requesting to see if someone has a fix. The purchase of the mount is very frustrating and annoying to use with the Call Audio problem.
Any help or point of direction would be greatly appreciated. You can reply here or PM.
Thanks for the consideration. ;-)
Have you tried any other kernels? There's faux's kernel, Mr X's stock based kernel...maybe one of those might adjust the issue you're experiencing.
Dfjcisnv
this is how it works with the desk dock as well, regardless of having external audio checked in dock settings. It worked this way using stock ROM as well I believe so it's a "feature". It would need to be hacked to have it perform otherwise I think.
Oh, and I think this should be in general also? Idk.
Sent from my SGH-T989 using xda premium
Saw your post and it gave me a laugh! I was ranting about this very thing yesterday while taking a call in my car. You can barely hear the caller through the built in speaker! why would they do that? If anyone figures this out I also would be very appreciative to see a fix.
18.4009

Voice Recognition Issues with my S3

I've been having issues with my S3 (sprint) for a little while now. Most of the time it's no big deal, but now that I want to play with Tasker AutoVoice, utter!, and voice commands in general, it's growing. I am running the 8/13 nightly of CM 10.1, but the issue has been going for a while now.
Here be the problems.
First, if I make a call, I have to use the speaker phone to be able to hear, the ear piece and mic don't seem to work quite right. BUT, if I get a call, there isn't a problem. Headphones with an inline mic work perfectly though.
Second, I cannot use the voice comands, Google Now, AutoVoice, or the like and I have ben talking directly into/at the microphone on the bottom of the phone. The phone doesn't register like it should, where the microphone flashes and shows that it "hears" you. The Google Sound Search lockscreen widget wil occassionally pick up sounds to identify the song, but that's hit or miss.
Third, the speaker doesn't work for media. YouTube, Play Music, what have you doesn't play from the speaker on the device. Well, I take that back, it has once, but only once. Headphones work perfectly though.
Now, I got my S3 from Best Buy and this is actually a replacement, and things worked out of the box. I don't know if it is a refurbished unit (my guess is that it is), so that could have something to do with it too. I'm tending to lean towards a software issue, maybe I just need to flash something to get those issues resolved? Any help I can get to resolve this, that would be awesome. I'd like to get it fixed rather than replaced as it takes forever to get a replacement, but I haven't removed that option. Thanks in advance and I'll try my best to offer up any and all information I can.

[Q] S3 4.3 AT&T S-voice no longer works with Bluetooth mic.

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.

[Q] Probem with Bluetooth on Cyanogenmod 11

Hello.
I have installed Cyanogenmod 11 on my HOX.
although everything looks to be working fine, I still have issues with my Bluetooth.
When driving in my car, and want to place a call, I used to be able to use Cyberon Voice Commander to place the call.
It still works when i use it on my phone without Bluetooth, but when I am connected to my car everything stays silent.
It worked with stock firmware, and I can recieve calls using bluetooth, and I also can use the car stereo to play music from my phone,
but just making a call with the Voice commander does not work.
Does anyone have similar experiences with this, or does anyone have a solution?
Search the thread, been mentioned a lot there !
Hello,
I have been searching, and also looked in the thread for the HTC (HTC One X CyanogenMod 11.0 nightlies, http://http://forum.xda-developers.com/showthread.php?t=2583037) but I could not find an issue which is matching my problem.
Unfortunately I am (yet) not able to post this issue in the HTC One Cyagenomod thread...
I don't own a BT headset so I can't properly debug the issue. I know that a lot of people complain about it but there is not much I can do unless they actively try to help. You could provide logs when pairing the device, turning it on and when doing a call.
I might by a BT headset in the future. So there is hope .
Hello,
I was not sure which logfiles you wanted, so I grabbed the output from dmegs and made a logcat and put it in a zip fie.
Here they are.
Thanks for your effort, though.
Thanks for the logs.
Can you describe the behaviour a bit more? What exactly does not work? Imitating the call through Bluetooth, hearing your partner through Bluetooth or recording through Bluetooth. And can you test other apps for me. Like Skype or the normal phone without cyberon.
Do you know if your car is recognized as a normal handsfree Bluetooth device or something special? If you happen to know it.
Also some apps (like Google Now) need to be told to use BT devices.
Hello,
Bluetooth itself is working normally, I can use it to play music on my car's stereo, and when I recieve a call it works fine, I can hear the other party, and they can hear me.
It's just when I want to make a call, I can see Cyberon Voice commander starting up, but I don't hear any sound, and it also does not respond on voice commands.
When I disable Bluetooth, the app works normal.
On stock HTC rom, the app also works fine.
I own a Ford Focus 2011, and it shows up in bluetooth as Ford Audio.
The profiles active are audio for telephone and audio for media (sorry, translated from dutch).
The default Voice Dialer at least I can hear on my headset, haven't tried in the car yet with this version of Cyanogenmod.
It does not seem to respond to the micophone though.
The previous version of Cyagenomod would also not play over my car speakers.
Will try again when I get back home, did not use my car today.
Please test tomorrows nightly. I fixed some issues and I think they address your problems.
Try this Kernel http://forum.xda-developers.com/showthread.php?t=2586808 On the latest Version is a fix for BT maybe it helps
Hello,
just tried to test the "Voice dialer" through my car stereo, I can hardly hear it, and it does not recognize anything I say.
At least not in a way it would be useful for me
With tomorrows version you mean CM-11-20140314-Nightly, or the one after that?
Could not see anything about Bluetooth in the changelog, but I'll wait for the next version.
Will report back.
charly_s said:
Hello,
just tried to test the "Voice dialer" through my car stereo, I can hardly hear it, and it does not recognize anything I say.
At least not in a way it would be useful for me
Click to expand...
Click to collapse
With the other kernel? You probably already had the BT fix when using the CM kernel.
charly_s said:
With tomorrows version you mean CM-11-20140314-Nightly, or the one after that?
Could not see anything about Bluetooth in the changelog, but I'll wait for the next version.
Will report back.
Click to expand...
Click to collapse
Yes, 20140314, see line 6.
http://www.cmxlog.com/11/endeavoru#cm-11-20140314-NIGHTLY-endeavoru.zip
Hello,
I tested it with yesterday Nighties, and it's working now.
Cyberon Voice Commander could now be used with the Car bluetooth set.
Thank you for solving this.
I hope the logs I uploaded were of any use.
btw, I did take a look at the change log, and the line "tegra3-common: system/audio.h: Use correct DEVICE_BIT_IN bits" didn't ring any bells in my head in combination with Bluetooth.
Anyway, it is solved for me (and maybe for several others as well), so I want to express my gratitude by saying: Thank you very much:highfive:.

Categories

Resources