New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 664703 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug
M55



Sign in to add a comment

BLE Beacons: Updating frequency causes existing ads to cease broadcasting

Project Member Reported by mlight@google.com, Nov 12 2016

Issue description

Version: 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.

 
Cc: r...@chromium.org
Components: UI>Shell>Kiosk

Comment 2 by mlight@google.com, Nov 14 2016

Status: Fixed (was: Assigned)
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.

Comment 3 by dchan@google.com, Jan 21 2017

Labels: VerifyIn-57

Comment 4 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 5 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59
@mlight is this verified?
Cc: mlight@chromium.org
Labels: -VerifyIn-57
Status: Verified (was: Fixed)
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