You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 2, 2021. It is now read-only.
After Wifi ScanResults are received (& handled), there is a 2 second delay (see constant and code), then a new scan is triggered.
It is unclear how long the scan takes. This is presumably device-dependent. A quick glance at the logs shows intervals from 3 to 6 seconds.
However, we want to make sure that this interval is consistent, i.e., that there are no interruptions. Thus the time between scans (while logging is activated) should be tracked, and the user should be warned, if a certain threshold (e.g., 15 seconds) is exceeded.
The text was updated successfully, but these errors were encountered:
After Wifi
ScanResult
s are received (& handled), there is a 2 second delay (see constant and code), then a new scan is triggered.It is unclear how long the scan takes. This is presumably device-dependent. A quick glance at the logs shows intervals from 3 to 6 seconds.
However, we want to make sure that this interval is consistent, i.e., that there are no interruptions. Thus the time between scans (while logging is activated) should be tracked, and the user should be warned, if a certain threshold (e.g., 15 seconds) is exceeded.
The text was updated successfully, but these errors were encountered: