[2.4] [Enhancement request] Choose wished device's profile on device connecting

[kuraga]

blueman: 2.4
BlueZ: 5.72
Distribution: Calculate Linux (Gentoo-based)
Desktop environment: XFCE 4.18

• I have consulted the Troubleshooting page and done my best effort to follow.

The AudioProfiles plugin doesn't show any status menu items until you connect to the device.

The RecentConns plugin shows one status menu item per device, i.e. one profile per device.

So, I can't choose the wished device's profile on device connecting.

Could it be improved? Thanks!

[cschramm]

🤔 Definitely not a super easy change but thinking out loud...

We could remember (device, audio profile) tuples and offer them in RecentConns. We can obviously not request the device to get connected with the profile active, but we can switch the profile accordingly after the device got picked up by the audio server.

I'm a little unsure about the use case. I do see that one wants to use (legacy?) headsets with different profiles for a) communication and b) listening and that it's a bit cumbersome to first connect the device and then change the profile. Then again, is RecentConns really relevant there at all? Isn't the typical flow for headsets that you power them on and they immediately connect to the previously paired device?

[kuraga]

I'm a little unsure about the use case.

Turning on the wished profile via two clicks instead of four.
(Thought AudioProfiles is exactly for this.)

[kuraga]

The RecentConns plugin shows one status menu item per device, i.e. one profile per device.

Could change this? With a setting, maybe.

[cschramm]

I'm a little unsure about the use case.

Turning on the wished profile via two clicks instead of four. (Thought AudioProfiles is exactly for this.)

Again:

Isn't the typical flow for headsets that you power them on and they immediately connect to the previously paired device?

It's not a use case for RecentConns at all if that's the case.

[kuraga]

Hm... I have a notebook, a smartphone and headsets.

For the smartphone, the mode is "mixed" every time.
For the notebook, it's either "audio" or "headset".

So, there are three different use cases:

1. Connect to the smartphone.
2. Connect to the notebook as "audio".
3. Connect to the notebook as "headset".

Note there is no the "Connect to the notebook" use case.

Don't know whether it's a standard case but want to connect quicker.

[kuraga]

It's not a use case for RecentConns at all if that's the case.

For a separate, the RecentConnProfiles plugin, then?
It will list the recent connected profiles.

Also, if RecentConns is about "recent connections" (i.e. "devices") not "recent profile-connections", IMHO <... profiles> on <device> should be renamed to Connect to <device>. The same as we already have Disconnect <device>.

[cschramm]

It's not a use case for RecentConns at all if that's the case.

For a separate, the RecentConnProfiles plugin, then? It will list the recent connected profiles.

You got me wrong there. I was questioning if a headset is a use case for RecentConns at all as it typically auto-connects when powered on, but of course it is if you use it with multiple devices.

Also, if RecentConns is about "recent connections" (i.e. "devices") not "recent profile-connections", IMHO <... profiles> on <device> should be renamed to Connect to <device>. The same as we already have Disconnect <device>.

Your mixing Bluetooth and audio device profiles. RecentConns is about connections to more or less specific Bluetooth profiles.

[kuraga]

Auto-connection could help me in half cases only as there are two options (profiles). And auto-connection doesn't know my current wishes.

P.S. Also, in most cases, auto-connection enables (adds to the menus) the HSP/HFP profile only for my headset. But that's another story.
And "auto-connection" is "from the device to the host" here, see #1709 (comment). (Even if AutoConnect plugin is on. The device does it first?)

P.S.2. The AudioProfiles doesn't seem to work, see #2331.