borine

@dr-ni I've raised a draft PR (#601) to add a new boolean property to the BlueALSA PCM1 interface. If you are able to test this to see if it can...

Ahh, sorry, it seems the lines ``` dbus.mainloop.glib.DBusGMainLoop(set_as_default=True) mainloop = glib.MainLoop() ``` must be placed **before** the call to ``` bus = dbus.SystemBus() ``` So just moving those 2 lines...

Hmm, that error indicates that bluealsa has not been informed by ofono that the call exists. I can't imagine how my patch could have caused that, so I'm hoping that...

> bluealsa: E: BT socket disconnected: Connection reset by peer OK, so that tells us that that the bluealsa PCM was created, and that the audio connection had been opened...

Quite a mystery here ! I don't have an explanation why arecord can't find the PCM at present. When the "Audio connection started" message appears, can you post the output...

late update: please can you modify the dial script to print the bluealsa pcm object path. Change the signal handler definition to: ``` def signal_handler(*args, **kwargs): running = args[1].get('Running') if...

The debug log, plus the `bluealsa-aplay` results, prove that the bluealsa daemon is working correctly and the `ndial` script shows that the new "Running" PCM property is also working as...

This issue has had no updates in the last 6 months, and appears to be more likely caused by either Bluez or the characteristics of the specific remote device. I...

I now feel this product would sit better outside of the bluez-alsa project, and so it is now maintained as a distinct project here: https://github.com/borine/bluealsa-hfp-ag-plugin

@Arkq This issue appears to have been forgotten. Although I haven't been able to reproduce the failure in my own system, I think there is clearly a race condition here...