Version: M-56, Build 8955.0.2016_11_03_1617, (internal build by Joseph Hwang)
OS: chromeOS
Device:  samus chromebook, and rikku chromebox.

What steps will reproduce the problem?
(1) Install on a device a M-55 or higher version of ChromeOS, built after Nov. 16, 2016.  The device must support BlueTooth 4.0 (BLE).

(2) Enterprise-enroll the device to a domain, and use Cpanel to assign the device to an Org. Unit which has these Device Settings:
  Under Kiosk Settings:
    A) The force-installed kiosk apps include an app which can create BLE Advertisements. (example: "Krishna Test BLE freq App", webstore id: akbaeokbhhplcacgmkkcbjghgbhchkib)
    B) Designate the app to be auto-launched.
  Under Other: Bluetooth: 
    C) "Disable bluetooth on device" must be set to "Do not disable bluetooth".
  
(3) Reboot the device and wait for the app to auto-launch.  Register at least two advertisements and verify they are broadcasting.  (The nRF Connect app on an android phone is useful for this, available at the Play Store).

(4) Suspend the device, either by closing the lid on a chromebook, or on a chromebox break to VT2 (ctrl+alt+f2) and executing this command as root:
# sleep 10; powerd_dbus_suspend
Go back to the app screen (ctrl+alt+f1) and wait for the screen to go blank.

(5) Wait about 5 seconds for the suspend state to take full effect.
Use your phone to scan for any advertisements.


What is the expected result?
All advertisements should cease (I assume; but could be mistaken).

What happens instead?
One advertisement stops, but another (the ad registered first) continues broadcasting.