Start with a clean baseline
Input and output are separate paths. Prove left/right playback and microphone capture independently before blaming Bluetooth, the app or the entire headset.
Live evidence
Relevant checks
Gamepad Controller TestTest browser-detected controller buttons and analog axes.
→WebHID Device TestRequest a compatible HID device in browsers that support WebHID and display its browser-exposed product and vendor identifiers.
→Browser Hardware Feature CheckSee which hardware-facing browser capabilities are available before trying camera, gamepad, MIDI, USB, HID, serial, or Bluetooth diagnostics.
→First sequence
Do the high-signal checks before risky changes
- 1
Check the vendor runtime sees the headset
- 2
Test controllers separately
- 3
Use official headset diagnostics for tracking/display hardware
Decision points
What the result should change
If playback passes but microphone failsKeep the diagnosis on input selection, headset profile, mute/gain or microphone hardware.
If only one channel failsCompare cable/earcup/driver and balance settings rather than reinstalling all audio drivers.
If browser audio passes but conferencing audio failsPrioritize the conferencing app's device routing and processing.
Browser can help check
- Detect supported browser APIs
- Test some controllers/inputs
Browser cannot prove
- Run universal headset panel/tracking diagnostics
- Access vendor runtime calibration generically
Repair boundary
Know when to stop browser troubleshooting
- High playback levels can damage hearing; use moderate levels during tests.
- Bluetooth codec/profile negotiation is not fully exposed to websites.
- Battery swelling or heat in wireless audio devices requires service/disposal guidance.
Used-device inspection
What to verify before paying or signing off a repair
- Left/right and frequency sweep at safe level
- Microphone recording and mute controls
- Wired/wireless connection modes and charging behavior