Back to home
Support
Support
Troubleshooting, bug reports, and how to reach us.
Detection troubleshooting
If detection doesn't return a codec, try these steps in order before reporting an issue.
No codec event observed
Stop all audio playback first, then click Detect again. The short diagnostic tone opens a fresh A2DP stream. If your headset microphone is in use, Windows may have switched to HFP - disable the mic or set the headset to stereo mode.
Not a Bluetooth audio device
Your current default output isn't Bluetooth. Open Windows Settings > System > Sound, set your Bluetooth headset as the default output, then try again.
LE Audio is not supported
This device uses Bluetooth LE Audio with the LC3 codec, which isn't reported by the A2DP provider. A2DP tracing cannot detect it.
Administrator access required / UAC canceled
Detection needs administrator rights to read the Bluetooth ETW trace. Click Detect again and approve the UAC prompt. Canceling is safe and changes nothing.
Unable to inspect the codec
Make sure the headset is connected and set as the default output before detecting. Close other apps that may hold exclusive audio control, then retry.
Still no result
Reconnect the headset during the 30-second window, or run the command-line version from an elevated PowerShell for detailed output: dotnet run .\BluetoothAudioCodec.cs -- --json
Get in touch
What to include in a report
To help reproduce the issue, please include:
- App version (e.g. 1.0.0) - shown in the app.
- Windows version - press Win+R, type winver, and note the build number.
- Headset or speaker brand and model.
- Step-by-step reproduction - what you clicked and what happened.
- The exact codec shown, or the status message if detection failed.
Protect your privacy
Do not upload personal information, device serial numbers, or sensitive ETW trace logs. The codec name, codec IDs, default output device name, and a screenshot of the app are enough. Blur or crop anything private in screenshots.
Response time
This is a hobby project maintained in spare time. Expect a reply within 3-5 business days. Public bug reports on GitHub may be addressed sooner by the community.