After the latest updates that fixed GNOME Settings crashes when switching from A2DP to HFP/HSP, it became impossible to use profile auto-switching.
Previously, there were two options in the input device selector:
- Handsfree that switched my headset to HFP/HSP mode
- Some strange device that was named after my headset but didn’t enable HFP/HSP until explicitly requested by an app — this is how the auto-switching used to work
Now the second option is gone from the settings.
However, it’s still possible to enable it via wpctl by setting a corresponding filter (could it be the issue?) as a default device.
Settings
└─ Default Configured Devices:
0. Audio/Sink bluez_output.<redacted>
1. Audio/Source bluez_input.<redacted>
Then everything works as before, but I don’t see any input device in the settings:
I’d like to know if there is a fix for this, or at least if this is a known bug. And if it is something new, where exactly should I file a bug report? (not sure which package is responsible for this)
Additionally, there are other small annoying issues that are somewhat related and maybe someone knows a fix for:
- Switching the input device to Handsfree (HFP/HSP) manually doesn’t always switch the output device from Headset to Handsfree automatically, which used to be the cases in older versions of Fedora
- Sometimes the A2DP profile is missing until I restart pipewire+wireplumber and reconnect the headset
- Sometimes switching the input device from the built-in microphone to headset doesn’t work even though the correct device is displayed in Gnome Settings (in
wpctl statusit’s still the built-in) - Since the last update, pipewire seems to think that HFP/HSP mode supports stereo, even though it’s clearly mono