From 854b003fecb23426bc976e38d612ab8716b15179 Mon Sep 17 00:00:00 2001 From: Luiz Augusto von Dentz Date: Tue, 23 Aug 2016 13:14:21 +0300 Subject: [PATCH] doc/device-api: Document Connect behavior for dual-mode Adds description of how Device1.Connect behave with dual-mode devices. --- doc/device-api.txt | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/device-api.txt b/doc/device-api.txt index 087efb921..f5cac4926 100644 --- a/doc/device-api.txt +++ b/doc/device-api.txt @@ -21,6 +21,20 @@ Methods void Connect() If at least one profile was connected successfully this method will indicate success. + For dual-mode devices only one bearer is connected at + time, the conditions are in the following order: + + 1. Connect the disconnected bearer if already + connected. + + 2. Connect first the bonded bearer. If no + bearers are bonded or both are skip and check + latest seen bearer. + + 3. Connect last seen bearer, in case the + timestamps are the same BR/EDR takes + precedence. + Possible errors: org.bluez.Error.NotReady org.bluez.Error.Failed org.bluez.Error.InProgress -- 2.47.3