Christopher Schramm

:thinking: 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...

> > 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:...

> > 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...

Cannot reproduce.

No idea. I'd tell you to gather the values and try the `set_card_profile` call manually, but it's exactly the same as in blueman-manager, so that seems pointless. You are absolutely...

Thanks for the data, @Staudey. Good catch and, ouch, I do have an idea what's going on. Checking e.g. `pactl list cards` what card indexes do you see? If I'm...

The issue is clear then. I'll look into a fix. It's probably PipeWire, not genuine pulseaudio, right? Does it count up or are indexes somehow random? I mean, even if...

Not sure I can follow. Aren't the items that you blurred your recent connections?

We moved the recent connections from the submenu into the toplevel applet menu and "Recent Connections" is a title to give them some context, yes. #1558 / #1652 Prefixing the...

That's not really an option. E.g. for a phone you typically can have entries like: * Auto-connect profiles (audio and input) * Some network profile * Some serial profile The...