Abnormal behavior in Bluetooth-dense environments

[JosephHewitt]

"Side B" will stop sending the "BLE," (Bluetooth device count) messages to "side A" in Bluetooth dense areas. I observed this happening when the device count was in the region of 145 - 165 or higher. Other data (GSM) was still sent normally from side B.

I haven't yet checked the logs or collected data to determine if this issue causes data loss.

This issue manifests as a stuck BLE counter on the LCD. Rebooting the wardriver will cause the "ESP-B NO DATA" warning as this warning is triggered by a lack of "BLE," messages on boot. Moving away from the Bluetooth-dense area fixes this issue.

[pejacoby]

I saw this issue today while walking through a very BlueTooth heavy environment. The wardriver was in my bag so I didn't observe the display, but after the run I can see a large gap in BT data in the heavily congested area. My drive to the location shows plenty of BT, but as some point and during the walk in the high-density area there is no BT from the wardriver. I picked up lots of BT on my other three phones running WigleWiFi. Once I left the high-density area, the data shows BlueTooth recording resumed.

Sorry I don't have much more than that to offer, though I can provide the data file it it's of any use.

[JosephHewitt]

Thanks for the information. It seems like the wardriver is simply being overwhelmed with the amount of Bluetooth data and then stops reporting information temporarily.

I still need to find a way to reliably reproduce this since going to crowded locations to debug isn't very viable. I don't think the data file will offer any insights but thank you for the offer.