Hi Bastien,
On 19/05/2025 21:22, Bastien Nocera wrote:
On Mon, 2025-05-19 at 12:44 -0400, Luiz Augusto von Dentz wrote:
Hi Frédéric,
On Mon, May 19, 2025 at 12:18 PM Frédéric Danis
<frederic.danis@xxxxxxxxxxxxx> wrote:
---
doc/org.bluez.Device.rst | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/doc/org.bluez.Device.rst b/doc/org.bluez.Device.rst
index 80501eddd..6229f95ad 100644
--- a/doc/org.bluez.Device.rst
+++ b/doc/org.bluez.Device.rst
@@ -155,6 +155,23 @@ array{array{byte}} GetServiceRecords()
[experimental]
:org.bluez.Error.NotConnected:
:org.bluez.Error.DoesNotExist:
+Signals
+-------
+
+void Disconnected(string reason)
+````````````````````````````````
+
+ This signal is launched when a device is disconnected with
the reason of
+ the disconnection.
+
+ Possible reasons:
+
+ :disconnection-unknown:
+ :disconnection-timeout:
+ :disconnection-local-host:
+ :disconnection-remote:
+ :disconnection-local-suspend:
Perhaps it would be better to use to the actual HCI code instead of
converting it to string, since I suspect application using this
signal
may want to recover the actual error to do some sort of reconnecting
policy, etc, or having them both in case the client just wants to
print it.
If there are applications using those signals (I'm guessing, Bluetooth
settings apps), whatever the format of the error, could we have an
expected behaviour associated with individual error types?
This could be used by client apps like Bluetooth setting to try to
reconnect to the device in case of timeout or unknown disconnection,
or to try to connect to another device depending on internal policy.
--
Frédéric Danis
Senior Software Engineer
Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, United Kingdom
Registered in England & Wales, no. 5513718
