19-12-2017 02:32 PM in
Since a few days now whenever I use voice recognition through bluetooth on my car stereo or bluetooth speaker there is a very loud beep sound coming through as well as the normal audio, if I start voice recognition directly from my phone it works fine.
Has anyone else experienced this problem or can anyone offer suggestions on what to try to resolve it?
I've tried a software upgrade and re-installing the google app but nothing has helped so far.
Thanks in advance
Solved! Go to Solution.
31-01-2018 01:31 PM in
Hi all. I had this problem too and it coincided with lots of new apps due to a home automation migration so I assumed it was that. Also a software update on tbe phone occurred in decemeber 17.
After much testing and app teeekimg and uninstalling I couldn't fix it. I spoke to Samsung and my network provider who didn't have knowledge of the fault or a solution .
In the end I backed everything up and did a phone factory reset. I connected Bluetooth to my car and the fault was gone. Next i did a Samsung restore , all my apps and data returned and the dodgy tone was still not back. So there's the solution.
I am noticing a few new tweaks on the OS now too, so I'm assuming December's software patch didn't apply properly and the factory reset allowed it to install fully.
Good luck and remember to backup your data ,passwords and photos at before doing a factory reset..
21-12-2017 08:47 AM in
I'm having a similar issue with bluetooth headphones on my Galaxy S7. Initiating Google assistant or tapping the keyboard mic for dictation, I get a loud beep like as if you're on the phone with someone and they pressed a number on the dial. I thought it might be related to my new Apple Airpods, but they worked fine for two weeks before this happened, and I noticed it happens now with my other Bluetooth headsets as well.
31-12-2017 01:13 AM in
I have the exact same problem with Apple's AirPods as well. Very loud beep telephone like noise but audio still coming through and AirPod's microphones working perfectly. Doesn't occur with other apps using their microphones (like making a call). Only occurs when Assistant is listening to my voice.
31-12-2017 07:27 AM in
It actually is doing this with any of my Bluetooth headphones. I have 3 different ones including the Air Pods, and it's the same thing with each of them... but, I still wonder if the Air Pods caused the problem somehow. I've tried unpairing all of my devices and then re-pairing just one of the headsets. Same result.
02-01-2018 11:09 PM in
exact same thing for me. I had the headphone with an S6 for 2 years with no problem. I got an S7 and using the voice button when connected to bluetooth produces a horrible buzzing sound. The funny thing is if I speak into the headphone microphone the voice activation/functions still work but the buzzing that comes through teh headsets is so loud and so bad I have to take the headsets off when i speak into them. I have tried various things as well. I am using bose bluetooth headsets.
15-01-2018 12:16 AM in
I have the exact same problem with Apple's AirPods as well.
I'm trying to figure out way your APPLE AirPods have time did with an Android Samsung phone?
I'm not entirely sure what you are talking about, but if you're talking about how I can use Apple's AirPods on an Android phone:
The AirPods work like normal Bluetooth devices, so they can be paired at the press of a button to any Bluetooth device, like a laptop or an Android phone. They're kinda an exception to Apple products' exclusivity to Apple. Mics work perfectly, as does other functionality. They're considered as a normal Bluetooth headset by Android.
17-01-2018 04:29 AM in
Did anyone ever find a solution to this issue?
I'm experiencing exactly the same problem on a new S7 edge, using Jaybird X3 BT headphones. Starting voice commands for google assistant plays an extremely loud tone, as if someone was holding down a tone dial button on a phone. Voice commands still work, but it's painful and annoying.
Never had this problem previously with the same earphones and my old S7 edge (new one was recently replaced on insurance), so I assume it's a new firmware or update from Samsung causing the issue.