Low Accuracy Threshold has no effect

[glocalglocal]

Describe the bug A clear description of what the bug is.

I have set the Accuracy Threshold to 40m but lower accuracy readings are not actually rejected. They are recorded under Data and the points are added to the trip map. The result is scenarios like this: I walk on a straight line, suddenly the trip path jumps 300m off course and back. This zigzagging happens repeatedly adding several kms to my short trip. The app also interprets this as me walking at 30km/h. When this happens Data shows readings with accuracy of, say, 100m+ which should have been rejected.

Expected behavior What you expected to happen.

I would expect the app to reject these reading. Alternatively, it could record them but not use them to plot the trip unless we change the accuracy threshold later.

Device info
Moto g73
Android 15
1.5.1 F-droid

[dietrichmax]

Thanks for the report. To be honest I have no idea so far what could cause the issue. The code looks correct to me and I see that locations are correctly filtered on both my test devices (gms and foss).

When the locations are filtered out they are also not saved on the device and not shown for trips.

Just to be sure. To you have by incident toggled Filter Inaccurate Locations to off? When it's active it should be shown like this:

[glocalglocal]

Yes, my Filter Inaccurate Locations is on. My debug log doesn't show anything 'filtered' but I think the log captures data for the last x hours and I haven't left home today.

For illustration, before the geofence by wifi feature was introduced, I could be at home all day and the app would show me walking all over the neighbourhood. The result was a very busy hub and spoke graph. Not a problem now thanks to wifi pausing, but still an issue when I am stationary, say, at the cinema.

Off-topic but an idea might be optionally pausing when the same SSID can be seen for a long time (ie you are probably stationary in an enclosed space like cinema, restaurant etc).