Enrollment of ChromeOS slave device could not be remotely triggered by the bootstrapping process. |
|||
Issue descriptionPeppy/Daisy M ChromeOS Chrome ARC Type Channel 55 8872.27.0 55.0.2883.29 3399754 release dev Steps: 1)Add flag on two devices -one with master flag and other device with slave flag. 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 2)Enable bluetooth of both devices and Enroll the master device. 3)Search slave device id while enrolling master device Expected :Slave id should be displayed in the list of bluetooth devices Actual:No id of slave machine is seen while enrolling the master device
,
Oct 30 2016
Assigning to Daisy based on git blame for kOobeBootstrappingMaster. Trapti, please note that afaics there is no --oobe-bootstrapping-slave command line parameter.
,
Oct 31 2016
Hey trapti@, 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 (bluetooth discoverable); otherwise, press Ctr+Alt+Shift+S to put the device in the bluetooth discoverable mode.
,
Nov 2 2016
It works with the folloing configuration. M ChromeOS Chrome ARC Type Channel 55 8872.35.0 55.0.2883.35 3426244 release beta master: Device: Kip DVT SKU 3 was cnnected with WIFI slave: enguarde MP use Ctr+Alt+Shift+S |
|||
►
Sign in to add a comment |
|||
Comment 1 by trapti@google.com
, Oct 28 2016