-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Poly Headsets
- Bluetooth Headsets & Earbuds
- Re: VOYAGER FOCUS 2 no Audio on mobile and sensor error

Create an account on the HP Community to personalize your profile and ask a question
01-27-2023 01:58 AM
I have a new VOYAGER FOCUS 2 in combination with the Voyager Base.
So I'm connected to my Laptop trough the Office base, and audio works
I'm connected to my Deskphone trough the Office base (DHSG) and audio works
My Samsung S10 says its connected, but I get no audio, and I can't answer incoming calls with the button on the headset.
The first few days, this was working correctly. Now every morning I'm trying al kinds of things to get it working, and eventually it will start working.
Disconnecting or powering down the base seems to work, sometimes
And sometimes the sensor reset (Power Off, charge, turn on while holding mute) seems to work.
I do see a LED error on the headset. Blinking red, left and right. If it works again, the blinking stops.
What can cause this?
01-27-2023 09:07 AM
Hi,
I have a very similar issue with my headset.
I've had it since december, worked fine for the first few weeks, but since January, I have trouble with audio from my phone (Iphone 11)
I can successfully connect my headset to both my computer and my phone and I do have audio from my phone, but as soon as there is a sound from the computer, the audio stops working from my phone. Before hand, the audio from my phone would pause when the was audio coming from my computer and resume after, but now, the only way for it to work again is to restart the headset. I tried to reinitialize my headset, reinstalled poly lens on my computer, PLT hub on my phone, but nothing fixed the issue.
I'm glad to know I'm not the only one having this issue. Hopefully someone has a fix for this.