4,000 beacons vs. one phone link
In crowded BLE areas, trackers lost their phone link, and some got stuck in a reset loop. I measured everything in a flood of about 4,000 beacons before touching any code. Stuck cycles went from 17 of 62 to 0 of 350.
Trackers had two problems in places crowded with BLE devices. After a phone session ended, the tracker stayed invisible to the phone. And in very dense areas, it reset every 33 seconds.
Neither shows up at a desk. So I brought the crowd to the bench.
Measuring before changing
I set up a flood of about 4,000 beacons. Before changing any code, I measured stuck cycles, resets and how many phone sessions passed.
Getting the phone link back
For the invisible tracker, I added three layers that kick in one after another. A probe checks that the phone link is really alive. With no phone connected, an advertising watchdog restarts advertising if it gets stuck. And if the Bluetooth stack doesn’t confirm that advertising started, the radio restarts.
Stopping the reset loop
For the reset loop, scanning now runs in slices, so the scanner can’t hog the system. The records that beacons generate are also paced.
Conclusion
Stuck cycles went from 17 of 62 to 0 of 350, over 10 hours. The reset loop went from one reset every 33 s to none in 80 minutes. Phone sessions passing went from 51% to 80%.
80% still means one session in five failed, and my data doesn’t say why. For the vendor’s part of the problem, I sent them an air log of 1,009 sniffed connection events.
The baseline is what let me say “better” with numbers.