device/bluetooth/bluez: track service and advertised uuid separately
BlueZ's device UUIDs property could return either the service UUIDs or the advertised UUIDs (not both), depends on whether the service UUIDs are resolved. Unfortunately there is no simple way to detect which of the two sets of UUIDs are returned. This CL separates the UUIDs tracking. The advertised UUIDs can be retrieved by reading the EIR data, therefore we can treat the UUIDs property as the service UUIDs. In the end, both are merged so a call to GetUUIDs() would get both the service and advertised UUIDs. Bug: b:172359553 Change-Id: I7de6f0c47f3799265b833c4b3be3da84bdf0e458 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560347 Commit-Queue: Archie Pusaka <apusaka@chromium.org> Reviewed-by:Reilly Grant <reillyg@chromium.org> Reviewed-by:
Sonny Sasaka <sonnysasaka@chromium.org> Cr-Commit-Position: refs/heads/master@{#834606}
Showing
Please register or sign in to comment