After installing the new Google dialer (as of Feb. 2017), I can not tick "phone audio" in the Bluetooth menu anymore. The only way I found is to revert back to the old version of the dialer and reboot the phone.
Related
i updated my touch to 6.1 now it wont find my motorola S9 headset what do i do
my s9 works fine on my touch and titan wm 6.1....make sure when u first power on your s9 the blue light stays solid...this means its in pairing mode, then open up connections manager, click settings, bluetooth, find new device and it should find it in a few seconds
It should work just fine, upgrading to WM6.1 doesn't change the way your bluetooth functions.
i've had trouble pairing my bluetooth as well. instead of going to bluetooth explorer, go to settings > connections > bluetooth > add new device (even if its in the list still click this). after it finds the headset go through all the settings then when your done tap and hold where it says S9 (or whatever your headset is called) then choose set as wireless stereo, then it will say your device wants to connect. if it says the passcode is invalid try again and it should work. while this way of pairing my headset can take around 5 min. or more, its the only way it seems to be working.
i am not sure if your phone is showing the same symptoms as mine or not, but if this is a common problem then i hope someone smarter than me can fix it, becaue the way i have to set it up is a real pain.
Hi all,
So I have Blazer ROM 4.1 installed on my phone and my friend's phone. I did it for him. Both have Vlingo installed from the Play Store.
I have a Jawbone Icon headset and he has some Motorola model... Not sure which. When I hold down the button on mine, it launches Vlingo. When he does this on the Motorola, it just redials the last number.
How does he switch that to launch Vlingo instead?
Now, this might be a headset setting, but he said that on the original stock ROM, it would launch Vlingo.
Ideas?
muzicman82 said:
Hi all,
So I have Blazer ROM 4.1 installed on my phone and my friend's phone. I did it for him. Both have Vlingo installed from the Play Store.
I have a Jawbone Icon headset and he has some Motorola model... Not sure which. When I hold down the button on mine, it launches Vlingo. When he does this on the Motorola, it just redials the last number.
How does he switch that to launch Vlingo instead?
Now, this might be a headset setting, but he said that on the original stock ROM, it would launch Vlingo.
Ideas?
Click to expand...
Click to collapse
I have found Bluetooth and voice dialing to be problematic on all the ICS leaks. If you notice if your phone is in standby mode after the screen goes dark you will not be able to place a call at all. You will receive calls fine but you won't be able to place one. It may try to function the first time you pair up but after that it is a no go.
I became a pest at the local RadioShack trying different headsets and not a single one worked. I have since gone back to EL29 and all is working as it should.
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.
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.
Hi,
Couple weeks ago I update my device HTC One (M8) with 5.0.1 android version. After update I'm having issues with my built in car bluetooth device. It is older version 2.0 bluetooth. It connects as usual, but when I am trying to make a call, it connects and disconnect every second or so. It is not related voice, or "beep" sound. It just disconnects, and immediately connects to my car bluetooth.
Is there any way to fix this problem? Or maybe there's a way to rollback bluetooth device software (but not all system update)?
I have already tried standard issues - unpairing, changing device names, restarting. Nothing seems to work.
Thanks
try safe mod
just search for ./.how to enter safe mod on htc one m8?.,.,,./
if that fixed it then another application is making the problem