GitLab

Nearby Share requires using the scan response in BLE advertising due to
the size of the data required. Previously using the scan response was
not possible in ChromeOS. These changes added some limited and
temporary support for a new d-bus property to specify the scan response
data: https://crrev.com/c/2458306 https://crrev.com/c/2459250.

This CL changes the adapter mojom interface to allow specifying that the
service data should be added the scan response and not the original
advertisement data when registering an advertisement. Due to the limited
and temporary Platform support (AD type 0x16 only), we kept the api
change as simple as possible. This change will likely be reverted or
modified depending on the shape of the final scan response API in
upstream bluez. Tracking that here: https://crbug.com/1136920


Bug: 1135699
Change-Id: I0513197efb1ab62cb75a2151fc738b89b5e9ec67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465132Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: James Vecore <vecore@google.com>
Cr-Commit-Position: refs/heads/master@{#816726}