iliraga

Is `disableStopDetection: true` in combination with `pausesLocationUpdatesAutomatically: false` not going to "ignore" that setting?

Based on our server data the last point before the big stop was recorded at `2022-08-02T13:27:42.040Z` which translates into `3:27 pm` local time. [Screenshot of it](https://files.irte.ch/x6zgrqA). Unfortunately the last logged...

In addition, just to be sure: Based on the documented description of `stopTimeout` a value of `1` means that (even if the system is enabled) would mean that there would...

That's an interesting observation and tbh I don't have an explanation for it. After digging through the logs & the server data there seem to be some mismatches there. Will...

Thanks, we are doing the `changePace` bit already: ``` Future _startReceivingLocations() async { await startPlugin(); await BackgroundGeolocation.changePace(true); stopwatch.start(); final state = await BackgroundGeolocation.state; /// Ensure that positions are fetched no...

Those pieces you refered to above were the initial phase of the test where I just started a `run` and just kept the device stationary for roughly 30minutes. Afterwards I...

Hi Chris, thanks for your help so far, we were able to figure out some other issues on the side. In the meantime I did a re-test again where I...

In addition to the recent comment also my question: If `disableStopDetection` is set to `true` and `pausesLocationUpdatesAutomatically` to `false` all those other properties like `stopTimeout` or `stopDetectionDelay` won't have an...

Thanks a lot, your recent comment put os on the right path I think. > This is not interesting at all. This is merely the result of your call to...

For reference this is the related code which caused it: ``` Future _startReceivingLocations() async { await startPlugin(); await BackgroundGeolocation.changePace(true); stopwatch.start(); final state = await BackgroundGeolocation.state; /// Ensure that positions are...