GitLab

Consume the org.bluez.Adapter1 ConnectDevice() method [1] to
allow Chrome clients to connect to a remote device (via their MAC
address) which they know is available and nearby, but is not known
to the lower-level Bluetooth stack (likely because the device is
not discoverable).

This change is motivated by a core flow of the Nearby Share feature.
In this flow, Nearby Share discovers a remote device via a
non-connectable BLE advertisement, determines that remote device's
BR/EDR MAC address by deciphering the BLE advertisement with
previously downloaded certificates, and then connects via RFCOMM.
In this situation, Nearby Share knows a device with the MAC address
is available and nearby, but bluez does not -- hence the need for
this change. More details at go/nearby-chrome-bt.

1) https://source.chromium.org/chromiumos/chromiumos/codesearch/+/master:src/third_party/bluez/next/doc/adapter-api.txt;l=187

Bug: 1140471
Change-Id: Ibb67f5ca2def444799205394767892b8d651b539
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2491131
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Sonny Sasaka <sonnysasaka@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821461}