Hi BlueZ maintainers,
Chromium OS has been working closely with Linux Bluetooth community to
improve BlueZ stack, and there are increasing needs from applications
building their features around Bluetooth. One of the major feedback
from these application is the lack of the detailed failure reasons as
return for D-Bus method call, and these failure reasons can be used in
metrics, optimizing retry mechanism, hinting the reproduce scenario to
improve BlueZ stack. The current org.bluez.Error.* are serving the
generic errors well. However,g given org.bluez.Error.* errors are used
across different interface context which does not serve the detailed
failure reasons well. (See https://github.com/bluez/bluez/issues/131)
Miao-chen Chou (3):
BR/EDR and LE connection failure reasons
Include BtdError code in Connect() return
Print error code for connect methods
client/main.c | 3 +-
src/device.c | 52 +++++++++------
src/error.c | 124 ++++++++++++++++++++++++++++++++++++
src/error.h | 171 ++++++++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 331 insertions(+), 19 deletions(-)
--
2.32.0.288.g62a8d224e6-goog