https://bugs.kde.org/show_bug.cgi?id=410574
--- Comment #3 from staka...@eclipso.eu --- This is a very good question. When BT is pairing, shouldn't it give pulseaudio the necessary info about what profiles are supported? I think this is all about being able to force the right profile. If it would be a pulseaudio thing, why is pulseaudio offering the A2DP mode and the HSP one and why, when A2DP is set, the headset does not honor it? For my understanding, the request for change of profile does not arrive at hardware level. But I have no sufficient knowledge about the interaction between pulseaudio and BT. FYI: it may be of interest to know, that I have the very same problem on a phone (the Ulefone Armor mini) which is AFAIK linux based as firmware. Same same, it sees the headset, both profiles are indicated valid but only the HSP/HFP mode is selected. This makes me think that this is a BT related problem, more than pulseaudio. (I am aware that we shall not "guess" in bugreports, but I think the info might help to narrow down were to search. If not, well just disregard and take my apologies). -- You are receiving this mail because: You are watching all bug changes.
