BlueZ: How to collect disconnect reason

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux