On 2022.05.07 13:02, Peter Humphrey wrote:
On Friday, 6 May 2022 08:59:33 BST Peter Humphrey wrote:
> On Thursday, 5 May 2022 21:37:12 BST Michael wrote:
I've never had speakers blowing the audio chips driving them. I
would have thought they would be protected electrically from such
events occurring.
>
The sound chips have failed on both my workstations' motherboards
over the last five years or so. They only seem to last a couple of
years. Each time I've plugged in a USB dongle instead, and both of
those have now failed. Or perhaps it's the speakers and their
amplifiers.
>
Anyway, more to the point, I had tried to configure a laptop to
connect over bluetooth to an AVR, but I couldn't get it to work
until I installed and used net-wireless/blueman. You may want to
give it a spin.
>
> I will. Thank you. And Jack too.
No joy. I get the same result:
"blueman.bluez.errors.DBusFailedError: br-
connection-profile-unavailable"
So far none of the remedies offered on the web have helped. What
would help is some idea of how the whole BT system works, but the
more I look the more complex it seems.
Not a direct help, but maybe it will trigger some ideas - the only time
I've seen any message about bluetooth profiles has been with a pair of
noise-canceling headphones. They work fine for either "High Fidelity
PLAYBACK (A2DP Sink)" or "Handsfree Head Unit (HFP)" but the last
profile is always "Headset Head Unit (HSP) (unavailable)". These are
all in the dropdown for the headset in the pulseaudio voluime control
app, once the device is connected. I just connected my BT speaker,
and it only shows the first two profiles, so at least it appears to
recognizes that it doesn't have a mic. You should be able to get
similar info from the bluetoothctl command.
Jack
