Forum Discussion
Solved
Issue with beeping when on mute...
Starting at the beginning of October when our users select mute, every few seconds there is a very loud double beep. Completely makes it hard to hear when you have your mic muted. I personally have ...
- UPDATE WITH FIX
I reached out to Aftershokz about the beeping, I was able to get to someone that was knew what the issue is. If you are using the headset directly with the Bluetooth built into your laptop or computer then there is an issue with the controls.
They sent me an Aftershohz Bluetooth USB Device and since then I have had ZERO issues. They sent it to me for free no change for it or for shipping.
One person in our office started having this problem on Monday. I ran updates and tried using the Shokz OpenComm headset with a different computer. The problem disappeared with the other computer, and no one else is having a similar problem with their Shokz Aeropex. The only difference I can find is that the computer with the mute beeping issue has Teams version 1.5.00.11163 while everyone else has version 1.5.00.9163, and Teams won't update to the latest version on those computers.
My computer updated to Teams version 1.5.00.11163 today, however, I can't recreate the mute notification and beeping reminders on it with the same OpenComm headset my coworker is using. I've tried removing the headset from the list of pared Bluetooth devices and resetting the headset before reconnecting, but that hasn't had any effect.
- Update.
I was hopeful that Microsoft would fix this problem in the next update, but nothing changed with version 1.5.00.14473. I gave up waiting on Microsoft to fix the problem and used two work-arounds mentioned earlier in this thread:
1) Use Teams on Office 365 online. This required turning off notifications for the Teams desktop application and turning on the online version's notifications. Otherwise two notifications popped up for a call, and the user often picked the wrong one. Uninstalling Teams would also have worked. Call options are in slightly different locations, so the user had to get reoriented to them.
2) Contact Shokz about the problem and get the Loop100 Bluetooth USB-A PC Adapter. They sent it without charge after the problem was explained, and it allowed us to use the Teams desktop application and Shokz OpenComm headset without any problems.- Is there any case with MS teams where they are solving this issue?
- Not that I have heard of. Even though it affects headsets other than Shokz OpenComm, it doesn't seem to be on Microsoft's radar. Given that they have been promising some features for over a year without delivering and not even looking at some extremely basic features, I would be surprised if they do anything at all about this other than saying we should all buy their certified headsets. It is worth noting that even their certified headsets don't always work. Given past experience, I wouldn't buy any certified headset from Poly.
- I am opening a Shokz support case now, hoping for same results.
