Closed Mihara closed 5 years ago
Oh, and one more thing I noticed:
When a bluetooth device that is already paired connects, the output switches to this device, which is expected -- but Sound Switcher doesn't notice, and in the menu, neither output is shown as currently selected.
Hi, could you check if this is issue is still relevant with the latest release (2.2.0)?
When a bluetooth device that is already paired connects, the output switches to this device, which is expected -- but Sound Switcher doesn't notice, and in the menu, neither output is shown as currently selected.
There's a difference between sound stream mapping (which is where the sound is directed, this is what you're referring to) and fallback or server default (which is what the SSI is monitoring and displaying). So if when plugging a new device the fallback doesn't change, the indicator's behaviour is correct. This can probably be verified by starting another app and checking whether it outputs sound via the port indicated by the indicator menu.
Close for now, feel free to reopen should the problem reoccur.
I am not sure if this is a bug report or a feature request, however, cursory searching through the issues seems to indicate that profiles are supported, so it's probably a bug report.
There are no similar issues with switching the output stream, if only because the output stream works regardless of which mode the device is in.
Ideally, I would like the device to be in A2DP mode if its microphone is not in use and in HSP/HFP mode if it is -- and would prefer to be able to configure for this behavior if autodetecting which is the right thing to do is too much work -- but in any case, switching the input should work, shouldn't it?