Simó Albert i Beltran
Simó Albert i Beltran
This time I was lucky... The code does not change but now it passed tests. Please see #517.
A WiFi report cannot be created every 50m (the default value) when the device moves at more than 60Km/h if the location interval is hardcoded to 3s.
I do not know how it works but when I reduce the location interval I am getting more reports with more accurate location.
I created this pull request because, if the problem is DB performance, UI and battery life, leave to the user the decision to modify it. I extended to 10 seconds...
The solution you proposed about making internal location dynamic is a good alternative to me if interval location is adjusted to the minimum of wifi and cell scan distance divided...