[BUG REPORT] S22 super lag. detect 10k devices

[NumbarZero]

using the latest version of the RF-CHAOS (1.0) it worked alright for 10mins while i was trying to understand how things worked and what buttons did what. when i was finally settling down and using it to scan a particular WiFi device to locate it inside my house the app was frozen and unresponsive. like 30sec lag delay. it would go up and down. killing it and restarting seemed to fix the problem, but it got worst and worst.

seems to be triggered by the scanner detecting a constant flow of different BLE devices? my list goes into the thousands and it just keep on pilling up.

what i tried:
-setting the refresh delay to 5sec.
-cleaning up the database
-turning the BLE scanning OFF
-turning BLE OFF in the cellphone (only thing that fix the problem)

i think i tried to kill the app and restart it after i changed each setting, but i cannot be sure. i know that dissabling the BLE on the phone fixed the problem.

Samsung Galaxy S22

edit:
i wish i could provide a video, but you'll understand that it would DOX me. because of the WiFi and BLE names of things in my house and the easiness of corelating them with a WarDriving database.

[scramblr]

Thank you - Looking in to this. If you could create a video and make it "Private" on youtube, that would be awesome but I get it if you don't want to do that. Only I would see the video, as long as it's Private with me added (please add youtube.com/notdan to the people who can look at it)

[scramblr]

Oh and after reading your Issue more closely this is something that I've seen as well, and it's going to be addressed in the next major release, pending review of feasibility - let me explain: The reason you keep seeing traffic even when you're not scanning is because something else on your phone is still scanning WiFi/BLE/etc. Think of RF-CHAOS as having an "App Wireshark/Tcpdump" capability - it watches the phone for any signs of beacons and doesn't care if another app is the reason there's beacons in the pipeline.

EDIT: At least, I think thats what you're saying. Honestly your issue is very hard to understand so I'm not sure what you're getting at my dude. Try to get that screencapture to me somehow privately if you can.