A few headsets have issues if HFP HF profile connection is attempted before HSP HS profile connection is closed. Looks like this could happen because bluez bluetoothd alows to make simultaneous HSP HS and HFP HF peer connections.
One of affected headsets is WH-1000XM2
Until we find out how to prevent simultaneous HSP HS and HFP HF connections, disable HSP HS completely unless user request it via discovery modarg.
Do this by adding module-bluetooth-discover arg enable_native_hsp_hs, default to inverse of enable_native_hfp_hffalse.
Fixes #1187 (closed)
Quoting from there, the issue is very similare to pipewire issue commented here pipewire/pipewire#604 (comment 773590)
This proposed change is following pipewire resolution pipewire/pipewire#604 (comment 786306) until we know how to prevent simultaneous HSP HS and HFP HF connections (via bluez change or otherwise.)
EDIT: defaulting to inverse of enable_native_hfp_hffalse yields less surprising results.