My server logs show that "no movement" alert messages are actually sent quite often. They are sent after 15 to 20 minutes of absence of movement (or absence of data reception), only if the user is at more than 500 m of the start of the track (and of the end of the planned route, if one has been uploaded).
Ideally, Locus would send an "end tracking" message when you stop tracking without going back to the start location, but this is out of my scope. Should I adjust these constants, or should I let the user customize them in the tracking parameters? I would like to receive user feedback. Thanks!
Ideally, Locus would send an "end tracking" message when you stop tracking without going back to the start location, but this is out of my scope. Should I adjust these constants, or should I let the user customize them in the tracking parameters? I would like to receive user feedback. Thanks!
