Bluetooth Headset Problems

I've tried these steps but they haven't made any difference.

When I unchecked "Handsfree Telephony", it just disabled the mic and headphones so just picked up audio from my webcam so it didn't resolve the issue.

I was unable to view the Bluetooth codec in settings.

I've checked all the bluetooth drivers and they appear to be up to date.

Thanks for following those steps and for the update—it helps narrow this down.
A few important points based on your results:

1. Disabling “Handsfree Telephony” disables the mic​

That’s expected—Bluetooth headsets on Windows can usually only use mic + audio together in “handsfree” mode, which severely degrades the audio quality. When this is disabled, Windows falls back to another input (like your webcam mic).

2. Codec information missing​

This suggests your Bluetooth adapter might not support higher-quality ("wideband") speech codecs, which are crucial for clear mic audio with Bluetooth headsets. Many built-in Bluetooth radios on PCs only support the old, muffled codec (CVSD), resulting in distorted or poor mic quality.

---

Next Optimization Steps​

A. Check if Your Bluetooth Adapter Supports Wideband Speech (mSBC)​

Most built-in adapters do not. If possible:

• Let me know the model/make of your PC or Bluetooth adapter (or post a screenshot of it from Device Manager).
• Alternatively, consider trying a USB Bluetooth 5.x dongle that advertises “mSBC support” or “wideband speech”—these are quite affordable and often resolve this problem completely.

B. Test the Headset with the Official Earbay USB Dongle (if included)​

If your Earbay BT68 headset came with a USB dongle, try using that instead of your PC’s built-in Bluetooth—it often uses its own drivers to sidestep Windows/driver limitations.

C. VDI (Virtual Desktop) Context​

If you experience this mostly in VDI/Teams, your employer/server settings might be restricting high fidelity audio redirection. This is a known limitation in some virtual desktop environments.

---

Short Summary​

• This is a common Windows limitation: Most Bluetooth headsets are forced into a poor quality mode when using the mic, unless you have a newer adapter with wideband/mSBC support.
• A $10-$20 USB Bluetooth dongle usually fixes the issue instantly if it supports wideband audio profiles.

---

If You Want to Share Logs or Screenshots…​

If you've uploaded new files with this thread, let me know what's in them (e.g., screenshots, logs, system info). I can review them for clues about your hardware or software, or you can mention which file to check.
Let me know how you'd like to proceed or if you want hardware recommendations for a suitable dongle. I know it's frustrating—Bluetooth and Windows are often at odds with how they handle headsets!

The model of my PC is Acer XC-885.

I've tested the headset with the official Earbay USB dongle and found the same issue.

Thank you for checking the Earbay USB dongle and confirming the same result. Based on your Acer XC-885 desktop model, here’s a focused technical explanation and next steps:

---

What’s Going On?​

Your symptoms—distorted Bluetooth headset mic audio on Windows 11 (even with an official USB Bluetooth dongle)—indicate a Windows Bluetooth audio stack limitation rather than a hardware driver or codec deficiency unique to your PC. This is particularly true for the Acer XC-885 series, which uses generic Intel/Broadcom Bluetooth radios and Realtek audio codecs.

Why Even the Dongle Fails​

Most USB Bluetooth dongles (even the manufacturer-supplied ones) rely on the Windows generic Bluetooth Hands-Free Profile (HFP) stack, which is infamously poor for microphone quality. The mic often reverts to "telephone quality" (narrowband, heavy compression) rather than the wideband it supports on mobile devices.

• Even dongles marketed as "wideband compatible" will often NOT deliver wideband/mSBC in Windows for communications apps—unless their drivers completely replace the Windows Bluetooth stack (which almost never happens).

Virtual Desktop Limitation​

When using Teams inside a VDI session, headset audio is often redirected with additional compression and latency, which can make mic issues even worse.

---

Concrete Steps and Workarounds​

1. Use a Separate USB Wired Mic (Recommended Workaround)​

• For the best voice quality in Teams, Zoom, etc., use your BT68 headset for audio output (pick the “Stereo” profile in Windows Sound Settings) and select a separate USB desktop mic/webcam mic for input.
• This is the only way to maintain high-fidelity sound in these apps without distortion on Windows.

2. Test with Third-Party Bluetooth Stack (BlueSoleil, Toshiba, etc.​

• Some users have had limited success installing third-party Bluetooth stacks (like BlueSoleil) that enable true wideband/mSBC mic support. Warning: Compatibility varies, and these are rarely fully supported on modern Windows 11 systems. Proceed only if you’re comfortable with deep driver changes.

3. Wait for Windows Bluetooth Audio Modernization​

• Microsoft has announced improvements for the Windows Bluetooth audio stack, aiming to bring proper wideband support for mics (especially for Teams/communications).
• Check “Windows Insider” update notes—if you see an update about broad-band HFP and you’re comfortable, you could try a preview version.

4. If USB Dongle—Try Manufacturer Software​

• If the Earbay dongle came with dedicated driver software (not just a generic “Bluetooth Audio” device in Device Manager), install it. Only a stack-replacing driver can potentially address this, but it’s rare for consumer products to include one.

---

Pro Summary​

This issue is a long-standing limitation of Windows’ default Bluetooth audio handling for communications microphones, not a failure of your headset, dongle, or PC.

• Your headset + dongle work perfectly with your phone because iOS/Android have robust wideband Bluetooth audio support.
• Windows routes comms mics via the HFP profile, offering poor quality and frequent distortion—something Microsoft is slowly addressing.

---

Bottom Line:

• For now, use a separate USB mic for your calls, continue to enjoy your headset for output, and keep Windows up to date for future improvements.
• Avoid investing more effort in driver or chipset changes, as the issue is at the OS stack level.

Let me know if you want a step-by-step on combining your Bluetooth headset with a higher-quality external mic, or how to check for upcoming Windows enhancements on your system!

Thanks for the advice received. I think I've managed to get my issue sorted now.

I restarted my PC and tried using the dongle that came with the headset for one last time. At first, there was no sound coming from the headphones but then it started working and sound was input without the distortion. Not sure what made it work but I'm happy now.

That’s great news! Sometimes, a full PC restart and a fresh dongle connection can “kick” Windows into properly initializing audio devices—especially after driver or device changes. Bluetooth headsets and Windows can be unpredictable, so don’t worry about not knowing precisely what fixed it; the important part is it’s working now.
A few quick tips to help keep things running smoothly:

• Leave the Dongle Plugged In: If things are now fine with the Earbay dongle, use it as your default connection.
• If Problems Return: Try removing the headset from Windows Bluetooth devices, rebooting, and then pairing/plugging in the dongle again.
• Windows Updates: Occasionally, feature or security updates can mess with device profiles. If you notice issues after a system update, repeat this restart and re-pair process.

If you ever need to revisit this, feel free to upload screenshots or logs, and I can do a deep-dive for you. Otherwise, enjoy your crystal-clear audio—and congrats on your persistence! If other tech headaches pop up, you know where to find help!