Eddystone bug inside beacon firmware?

[heypiotr]

I’m shedding some more light on the timing behavior you’ve been observing in this post:

Motion Only Broadcasting

The 10-second burst after bootup (note that bootup is almost immediate, it’s just the behavior shortly following the boot is slightly different) is a by-product of our QA process, and given that you don’t really reboot beacons often in production, it doesn’t affect things much. The 2000 ms adv interval is result of our Smart Power Mode. If there are no devices around doing Bluetooth scanning (and sending SCAN_REQ packets as a result), the beacon goes to low-power mode where it reduces the adver…