BLE Beacons: Updating frequency causes existing ads to cease broadcasting |
|||||||
Issue descriptionVersion: Milestone 55, build 8872.34, chrome 55.0.2883.34 What steps will reproduce the problem? (1) Enterprise-enroll a device into a domain (ex: crosprqa4.com) with an Org. Unit (ex: Debug > BLE-Advertise) which has these Device Settings: Disable Bluetooth on device: set to "Do not disable bluetooth". Kiosk applications contains "Krishna Test BLE freq App" (webstore id: akbaeokbhhplcacgmkkcbjghgbhchkib) Auto-launch kiosk app: "Krishna Test BLE freq App" Note: The device must support bluetooth 4.0, and be running chromeos of M55 or higher. (2) After app auto-launches, create one advertisement by clicking the [Advertise] button. Verify the ad is broadcasting at 20ms (the default) using the nRF Connect app on a phone (available from the Play Store). (3) Enter a different value in the [Update Advertisement Interval] text box, (ex: 30) then click that button. What is the expected result? Registered advertisements should continue broadcasting with the new frequency. What happens instead? The advertisement stops. If you register a second ad, both advertisements are played at the new frequency. Change the frequency again, and both ads stop. Please use labels and text to provide additional information.
,
Nov 14 2016
The problem has already been fixed in Joseph's test build from Nov. 3, 2016. Will verify the fix in the earliest goldeneye build that contains it.
,
Jan 21 2017
,
Mar 4 2017
,
Apr 17 2017
,
May 1 2017
@mlight is this verified?
,
May 1 2017
,
May 1 2017
Yes, this problem is verified fixed on most devices, but Veyron-Tiger and Veryon-Fievel are experiencing new problems on M-58 Stable and M-59 Dev (Issue 713948). |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by harpreet@chromium.org
, Nov 12 2016Components: UI>Shell>Kiosk