Jabra Bluetooth microphone missing after Modern Standby on Surface/AX211
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- audio-video-rtc, operating-systems
Research direction
The issue names no repository files, tests, or entry points. Begin by reproducing the failure after Surface Modern Standby with the Jabra Evolve2 65 and AX211, then inspect HFP UUID 0000111e endpoint states and the listed Intel, Microsoft, and Surface components. Done means identifying the responsible integration boundary or documenting evidence that separates the competing causes.
Written by the indexing model from the issue text.
Description
Summary
After waking a Surface Laptop 6 for Business from Modern Standby, a paired Jabra Evolve2 65 intermittently reconnects as Connected audio rather than Connected mic, audio. A2DP playback works, but the HFP microphone is absent from Windows and Microsoft Teams.
Resetting the headset does not help. Toggling the PC's Bluetooth radio off for 10 seconds and back on restores HFP and the microphone without removing the pairing.
System
| Component | Version |
|---|---|
| Computer | Microsoft Surface Laptop 6 for Business |
| OS | Windows 11 Enterprise 25H2, build 26200.9106 |
| Wireless adapter | Intel Wi-Fi 6E AX211 160 MHz |
| Intel Wireless Bluetooth | Reproduced on 24.20.0.3 and 24.40.11.1 |
| Intel Bluetooth package | Reproduced after upgrading to 24.60.0.4 |
| Intel Smart Sound Technology for Bluetooth Audio | 20.40.11988.3 |
| Microsoft Bluetooth enumerator | 10.0.26100.8875 |
| Microsoft Bluetooth A2DP/HFP drivers | 10.0.26100.1 |
| Headset | Jabra Evolve2 65, firmware 2.9.2 |
| Jabra Direct | 8.1.14601 |
Observed failure
- The Bluetooth parent, AVRCP, A2DP, and HFP Hands-Free AG PnP nodes are present and report
CM_PROB_NONE. - The A2DP endpoint
Headphones (Jabra Evolve2 65)becomes active. - Windows retains HFP UUID
0000111eas enabled in the device's cached service list. - The HFP render and capture endpoints transition from
DEVICE_STATE_UNPLUGGED(8) toDEVICE_STATE_NOTPRESENT(4). - The Jabra microphone is consequently absent from Teams.
- Power-cycling only the headset reconnects as Connected audio and does not recover HFP.
Recovery
- Turn off Bluetooth in Windows Quick Settings.
- Wait 10 seconds.
- Turn Bluetooth back on.
- The existing pairing reconnects as Connected mic, audio.
- HFP Hands-Free AG and its render/capture endpoints become active with
CM_PROB_NONE. - The Teams microphone meter responds.
This recovery has been reproduced on both Intel Bluetooth driver versions without deleting the pairing.
Timeline and attribution
- 2026-08-10: Removing and re-pairing restored HFP. Pairing emitted BTHUSB Event 14,
bad service record (attribute identifier 9), but that event did not recur later and may be unrelated. - 2026-08-20: Failure reproduced on Intel Wireless Bluetooth
24.20.0.3. Cycling the Windows Bluetooth radio restored HFP. - 2026-08-20: Upgraded with Intel package
24.60.0.4; the AX211 device driver became24.40.11.1. - 2026-08-24: After approximately three days in Modern Standby, the identical failure recurred. Cycling the Windows Bluetooth radio again restored HFP.
Because the issue spans two Intel Wireless Bluetooth releases, it does not appear specific to 24.20.0.3. The unchanged Intel Smart Sound Bluetooth Audio driver owns the affected endpoints, and the failure correlates with Surface Modern Standby resume. The likely ownership boundary is therefore the Intel AX211/Smart Sound and Microsoft Surface/Windows Bluetooth-audio integration. Jabra firmware is a secondary possibility, but resetting only the headset does not recover the issue.
Requested investigation
Investigate HFP UUID 0000111e endpoint activation after Modern Standby, including the interaction among:
- Intel AX211 Wireless Bluetooth
- Intel Smart Sound Technology for Bluetooth Audio
20.40.11988.3 - Microsoft HFP AG
- Windows 11/Surface Modern Standby
Related Intel reports
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jaraco/world
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 1/5 Under an hour Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
bondybondbond/rushcut#238 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
TheSmokeDev/hermes-talk#236 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area:subtitles core-only enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:recording bug P3
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
transit-audio/transit#706 ·
Maintainers usually reply within 1 day