Arkadiusz Bokowy

When reviewing this PR and playing a little bit with it I thought about some simplification regarding control element names. Especially in regards to battery element. I really do not...

Just to let you know, I've resolved conflicts by rebasing this PR on top of master.

There was something wrong with control names for 'sofvol'. In your original PR (before I've rebased in on current master - before https://github.com/Arkq/bluez-alsa/commit/f37840621a8b3c57ece9b66e923c68cbfaee5ed5 there was a bug which allowed to...

> I do like the idea of ALSA simple controls attaching a priority to "A2DP" and "SCO" if you can persuade alsa-project to accept that. I think that such thing...

> I think such use case is likely to be very rare - the vast majority of remote devices are either headsets or phones/music players, not both at the same...

@borine, I've updated https://github.com/Arkq/bluez-alsa/tree/fs-rare-use-case branch. I think that I've made my mind how to handle name duplications for this PR and for FastStream case :D. I think that the lesser...

> So far I have been unable to achieve simultaneous SRC and SNK faststream Hmm, I'll check that on my own as well. Maybe there is some regression in current...

> So far I have been unable to achieve simultaneous SRC and SNK faststream connections from the same device. I've just tested that on Ubuntu 20.04 and indeed it seems...

> The GIO critical message was introduced by commit https://github.com/Arkq/bluez-alsa/commit/f7da96296bf1180b313d1fa3776c5506c977831f Yes, my bad... Recently I've been using bluealsa with systemd unit file and I've missed these warning messages.... :/ I've...

I've rebased this PR on top of current master. I still don't like the idea of sacrificing BT device name for " Softvol C" label :/ But maybe there is...