Bluetooth: CrOS Bootstrapping slave id is not seen while enrolling master device |
|||||
Issue descriptionGlimmer Master Lulu Slave To configure a test device as a master/controller: Edit /etc/chrome_dev.conf, add the following flag and restart ui --oobe-bootstrapping-master To configure a test device as a slave device: Edit /etc/chrome_dev.conf, add the following flag and restart ui --oobe-bootstrapping-slave Steps: Enable bluetooth of both devices Enroll Master Look for the slave bletooth id while enrolling. Expected:Slave id should be available Actual:Slave id could not be seen on the devices list available while enrolling master.
,
Jan 20 2017
Achuith, could you help triage this? Our team is not involved with BT enrollment.
,
Jan 24 2017
Daisy - I think this is yours?
,
Jan 24 2017
There is no --oobe-bootstrapping-slave command line parameter any more. For now, for a Chrome OS device, if it doesn't have any input devices (keyboard/mouse), it's eligible for bootstrapping process by default; otherwise, press Ctr+Alt+Shift+S to put the device in the bluetooth discoverable mode and you should be able to see the Slave id on the Master device.
,
Jan 24 2017
@trapti, could you try this out-https://bugs.chromium.org/p/chromium/issues/detail?id=682502#c4
,
Jan 25 2017
Tried on Peppy-Candy combination.Could detect slave after trying 2-3 times with Ctr+Alt+Shift+S. Peppy as Master.Added no flags on Candy as slave. Columns M ChromeOS Chrome ARC Type Channel 57 9202.1.0 57.0.2987.6 3663478 release dev
,
Jan 25 2017
Looks good after trying with Ctr+Alt+Shift+S.Marking as Verified. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ortuno@chromium.org
, Jan 19 2017Components: -Blink>Bluetooth OS>Systems>Bluetooth