Yes, I'm working on a new version

To validate the Bluetooth headset in Linux ARM platform. What and which are the binaries required from Bluez

Thanks to khvzak for responding and announcing an new up and coming version. I have been occupied by other coding projects, but I look forward to the new version and to contributing further to the project, as it does need a significant overhaul.

Any news regarding the audio?

Meanwhile, here's my current shim for bt-audio --connect= on Ubuntu Xenial:

  <<<"agent on
      trust $BT_DEV
       pair $BT_DEV
    connect $BT_DEV
    quit" bluetoothctl

Bash code, $BT_DEV is the MAC. Unusual indentation because additional spaces in the middle were parsed as part of the device name.

Output is misleading when you send all commands immediately because bluetoothctl doesn't have enough time to give good feedback. Nonetheless, a few moments after I run the above, audio playback works, so I don't care about adding delays. If you want that, e.g. to verify the success message, try something like ( sleep ; echo ; sleep ) | bluetoothctl.

Hi @mk-pmb , I'm using your bash and getting No agent is registered
Thanks

In that case, try running bluetoothctl manually, and enter each command only when bluetoothctl is ready, i.e. had no output messages for a few seconds. This way you should be able to see which of the steps worked, which failed, and why.

PS: Also see my note about misleading output above. Use a tool like pavucontrol to check whether your BT audio device appears within 10 (maybe 30) seconds after what had looked like a failure.

PS

pavucontrol worked for setting audio playback to my bluetooth audio device
anyone know how configure pulseaudio from command line?

anyone know how configure pulseaudio from command line?

You could use pacmd and/or pactl.

[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady

[bluetooth]# connect 0A:0A:BE:00:38:6C
Attempting to connect to 0A:0A:BE:00:38:6C
Failed to connect: org.bluez.Error.NotReady