Android API BluetoothAdapter#getBondedDevices provides all devices in range (not just paired devices) |
|||||
Issue descriptionOS: Chrome OS (I think it was M60) What steps will reproduce the problem? (1) Call BluetoothAdapter#getBondedDevices() in an Android app (2) Query the set of BluetoothDevices What is the expected result? #getBondedDevices provides a list of devices that are paired to the Chrome OS device What happens instead? #getBondedDevices provides a list of all BT devices that are available and in range
,
Apr 19 2018
,
Apr 19 2018
,
Apr 25 2018
,
Apr 25 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d04eb6ad2b30f2414c0c3bac35b8c152f224b380 commit d04eb6ad2b30f2414c0c3bac35b8c152f224b380 Author: Qiyu Hu <qiyuh@google.com> Date: Wed Apr 25 20:43:25 2018 arc: bluetooth: Fix incorrect bonded devices reported to android This was introduced in the following patch as a typo: https://codereview.chromium.org/1927803002/diff/320001/components/arc/bluetooth/arc_bluetooth_bridge.cc BUG= 727843 TEST=Run CtsVerifier and confirm that non-bonded devices don't show up as paired Change-Id: Id50a5564257a270b62bc78c63835e194af772cce Reviewed-on: https://chromium-review.googlesource.com/1028574 Reviewed-by: Rahul Chaturvedi <rkc@chromium.org> Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org> Commit-Queue: Qiyu Hu <qiyuh@google.com> Cr-Commit-Position: refs/heads/master@{#553728} [modify] https://crrev.com/d04eb6ad2b30f2414c0c3bac35b8c152f224b380/chrome/browser/chromeos/arc/bluetooth/arc_bluetooth_bridge.cc
,
Apr 25 2018
The patch in #5 fixes this one. Mark closed.
,
Apr 25 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rjahagir@chromium.org
, Sep 20 2017