Fix a Bluetooth headset mic that records silence because the card snaps back to A2DP
Issue #9380, read in full with its comments, supports every claim. It describes the five-step policy cycle (autoswitch applies HFP, an EnumProfile change, select-profile, find-best-profile picks a2dp-sink, apply-profile overwrites). It records reproduction with device.restore-profile=false and with all three bluez5.auto-connect values, including Omarchy's drop-in, and silent 48 kHz capture. It also says the scripts are byte-identical in 0.5.15, 0.5.16 and master, and that MR !892 was merged as f5c3eb35 after 0.5.17 was tagged. The 0.5.18 NEWS carries the quoted autoswitch-bluetooth-profile line. On this workstation /usr/share/omarchy/bin/omarchy-audio-input-set-default contains no bluez or profile handling, PR #9638 is still open, and Omarchy's bluetooth-a2dp-autoconnect.conf exists at /usr/share/omarchy/config/wireplumber/wireplumber.conf.d/. Arch extra has had wireplumber 0.5.18-1 since 2026-09-30, and stable-mirror.omarchy.org still serves 0.5.17-1 as of 2026-10-05, so the Omarchy branch of step 3 is current. The pactl awk filters select column 2 of the short listings, which is the name. The manual set-card-profile workaround is the one the reporter verified. Not exercised: no Bluetooth headset here, and no profile change was made.
Symptom
You pick a Bluetooth headset's microphone in the Omarchy audio panel or in a call app and the headset stays on high quality music playback with a microphone that records nothing. Watching pactl list cards | grep -E 'Name: bluez_card|Active Profile' you may catch it flip to headset-head-unit for a fraction of a second and drop straight back to a2dp-sink. A recording from the bluez_input.* source is valid 48 kHz audio that is pure digital silence. Choosing the HFP profile by hand makes the microphone work.
Cause
A WirePlumber policy bug present in 0.5.15, 0.5.16 and 0.5.17. When a capture stream links to the headset's loopback source, autoswitch-bluetooth-profile.lua correctly applies the headset (HFP) profile. That profile change emits an EnumProfile change, device/select-profile.lua treats it as a fresh profile-selection request, find-best-profile.lua picks the higher-priority a2dp-sink, and apply-profile.lua overwrites HFP while the capture link is still active. It reproduces with device.restore-profile=false and with every bluez5.auto-connect value tested, including Omarchy's own bluetooth-a2dp-autoconnect.conf, so it is not an Omarchy configuration problem. The fix was merged upstream as WirePlumber MR !892 (commit f5c3eb35) and ships in 0.5.18, whose NEWS lists "autoswitch-bluetooth-profile ... no longer gets overridden by EnumProfile triggered profile selection". Omarchy 4.0.4's omarchy-audio-input-set-default does not switch Bluetooth profiles itself (confirmed by reading it on 4.0.4-1, the PR that would add this, #9638, is still open). This is the opposite failure to the one in bluetooth-headset-mic-hfp-a2dp-profile, where auto-switching works and wrecks playback quality.
Fix
**1. Check the version.**
pacman -Q wireplumber
0.5.15 to 0.5.17 have the bug.
**2. Workaround: switch the profile by hand before the call, then select the mic.**
card=$(pactl list short cards | awk '/bluez_card/ {print $2; exit}')
pactl list cards | sed -n "/Name: $card/,/Active Profile/p" | grep -E 'headset-head-unit|a2dp-sink'
pactl set-card-profile "$card" headset-head-unit
pactl set-default-source "$(pactl list short sources | awk '/bluez_input/ {print $2; exit}')"
If the listing shows only codec-suffixed names such as headset-head-unit-msbc or headset-head-unit-cvsd, use that exact name instead. After the call, go back to high quality playback:
pactl set-card-profile "$card" a2dp-sink
Do not turn bluetooth.autoswitch-to-headset-profile off to fix this. That setting stops switching into HFP, which is the opposite of what is wrong here.
**3. Permanent fix: WirePlumber 0.5.18 or newer.**
Plain Arch: 0.5.18 has been in extra since 2026-09-30, so a full system upgrade installs it.
Omarchy 4: omarchy update takes Arch packages from stable-mirror.omarchy.org, which as of 2026-10-04 still served wireplumber 0.5.17-1. Keep using the workaround and re-check after each update:
omarchy update
pacman -Q wireplumber
Verify
With a call app or pw-record --target "$(pactl list short sources | awk '/bluez_input/ {print $2; exit}')" /tmp/bt-mic.wav running, pactl list cards | grep -A0 'Active Profile' for the bluez card keeps reporting headset-head-unit for the whole recording, and /tmp/bt-mic.wav contains your voice rather than silence.