-
-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not detect associated smart phones. #3
Comments
This might depend on the OS and phone but I can see its not true for any of the phones I've tried (Pixel, LG, iPhone). @carstenschwede does it not detect your smartphone when its associated? I've seen that phones affiliated with an access point do send out probe requests to see if there is a stronger wifi connection that they can switch to. The rate that this occurs is slower, but usually within 3 minutes in my tests. When idling it happens less frequently (maybe every 10 minutes). |
Interesting. I remember this being the case for an iPhone 4. Maybe the intervals get longer once the smart phone is connected - I don't think that I waited more than a couple of minutes and I probably wrongly deduced that they won't send out any requests at all. I will check again with my current phone. |
It won't detect my Samsung S6 Edge, only Apple devices. One of them is my Macbook.
|
@diego-vieira Can you try adding the |
@schollz unfortunately no. Don't worry, might be something with the router or the way Samsung deals with packets dunno. Here's the log tho.
|
Thanks for the software, much appreciated!
AFAIK smart phones will only issue probe request when they are not currently connected to an access point. This might lead to a severe underestimation of the number of smart phones in areas where most phones are connected to an AP (e.g. bars with open WiFi, universities, ...). Not sure how this applies to Bluetooth.
Maybe this is worth a note in the README?
The text was updated successfully, but these errors were encountered: