As for colors, I'm planning to change it to gray for stationary state to not confuse people with red.
I'm used to manually turn on Traccar's continuously tracking at the start of the tour, then turning it off at the end of the tour.
That means:
When I'm responsible to turn off tracking manually at the end because stop detection is off, can't I expect Traccar to turn the app into moving state straight after activating continuously tracking?
If I use traccar in this manner and the mechanism takes 5 minutes (?) for detecting movement, the first 30 data points of the tour are missed.
I think Traccar should wire together auto stop detection and auto moving detection for (de)activating both. Or at least giving it an input field in the user interface.
I tried the auto movement/stop mechanism at some point in the past, it worked well for a while but it suddenly left me with low battery in the morning because the stop detection didn't trigger and continued tracking with interval=10 all the night. And I always missed the first data points so I switched back to manual operation.
@Anton Tananaev It seems you were able to reproduce the issue, but by close the app I mean swipe up and quit or clear the app from multitasking. If I "switch" apps, (swipe up and go to my home screen) it stays in the foreground and the continuous tracking toggle stays on and green. If I close the app (swipe up, and swipe it away to clear my phone of all open apps) it stops sending tracking updates. When I immediately reopen the app, continuous tracking has been disabled.
Here's the logs when continuous tracking is enabled. https://pastebin.com/6eqmHPVA
And here they are after re-opening the app immediately. https://pastebin.com/G3vWg5iv
Looks like there's an issue with iOS app where it doesn't keep the state as enabled after app restarts. Submitted a ticket for it here:
https://github.com/transistorsoft/flutter_background_geolocation/issues/1621