On 4/3/23 18:29, Gregory Nowak wrote:

> See above. The way you're trying to do it won't work. From your list,
> you seem to have the necessary packages installed. Good luck.
>
> Greg


Thanks Greg (and all)..
Using the link you provided, I was able to get it connected.

After I posted my original question, I ran through the scan, pair, connect sequence and
suddenly the headset connected, but I did not know why. The link mentions having pulseaudio
running while trying to connect and I think that may be the trick.

The 'agent' command prompts me to connect now when I turn the headset on which is interesting.
I'll check out the rest of the info at the link. Maybe I won't need to issue all the commands
next time I reboot:

[CHG] Device 41:42:AC:26:6A:7B Connected: yes
Authorize service
[agent] Authorize service 0000110d-0000-1000-8000-00805f9b34fb (yes/no): yes
Authorize service
[agent] Authorize service 0000110e-0000-1000-8000-00805f9b34fb (yes/no): yes


It's almost impossible to find 2.4ghz headeset+mic anymore.
For anyone interested, the bluetooth adapter I'm using is
https://www.amazon.com/dp/B00OH09OXS/
and headset is
https://www.amazon.com/dp/B09SNQ6FQ2