* BlueZ: How to collect disconnect reason
@ 2016-10-12 16:36 Hieu Le
0 siblings, 0 replies; only message in thread
From: Hieu Le @ 2016-10-12 16:36 UTC (permalink / raw)
To: linux-bluetooth
Hello,
Currently, I can capture the disconnect event by listening to a
property_changed signal of "Connected" properties under
org.bluez.Device1 interface.
However, I need to find to way to distinguish disconnection due to
various reason which is similar to the output of bluetoothd daemon
(unknown, local_host, timeout,..).
I searched all the documents. Unfortunately, I cannot find any D-Bus
API to accomplish it.
Could you please suggest me some hint?
Many thanks for your valuable input.
Regards,
Hieu.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-10-12 16:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-10-12 16:36 BlueZ: How to collect disconnect reason Hieu Le
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).