You are not logged in.
I'm using BT headphones that come with an integrated microphone, but I only want to use them as headphones.
Problem is, many applications (chrome, discord, audacity...) will detect their input capabiity and register it as "mic" which in turn automatically causes pavucontrol mixer to switch the headphones from a2dp to the really bad headset mode. To undo this, I have to manually in pavucontrol set the recording device for the affected apps back to the real mic, and then disconnect+reconnect the headset.
So I really want these headphones to not even register as offering "input" capabilities when I connect them via BT, so no app/mixer gets the idea to switch their audio profile on its own volition.
Last edited by millus (2025-04-05 16:41:06)
Offline
If you're using wireplumber it's fairly trivial to define a rule that only allows micless profiles. https://pipewire.pages.freedesktop.org/ … properties ... enable only the two -sink profiles so a2dp-sink and bap-sink
if you're using pulseaudio still, find the line that reads load-module module-bluetooth-policy line in your /etc/pulse/default.pa and add auto_switch=0 to it.
Last edited by V1del (2025-04-07 23:15:06)
Offline
Thanks, how do I know what I "use"? I see these processes running:
pipewire
wireplumber
pipewire-pulse
libpulseaudio-plugin.soLast edited by millus (2025-04-19 21:31:28)
Offline
wireplumber in that case.
Offline