[Help Wanted] Disable stationary state

[tananaev]

Is there a way to disable stationary state completely? I tried setting disableStopDetection, but it seems like in that case the moving state doesn't persist across app restarts. What is the correct way of doing it? I want to basically force always "moving" state when the plugin is enabled.

[christocracy]

You can set a very high stopTimeout and pausesLocationUpdatesAutomatically: false

[tananaev]

I thought about it, but the documentation says:

WARNING: Setting a value > 15 min is not recommended, particularly for Android

Is it just because it will drain battery? Or is there any other side effect of setting a really high value?

[christocracy]

I only wrote that to warn people away from having the plug-in keep location-services pinned ON.

If that’s what you actually want to do, you’re free to do so

Use .changePace(false) to force the plug-in back into the stationary state.

[tananaev]

Thanks. And one last clarification about pausesLocationUpdatesAutomatically: false. It says this will also force disableStopDetection. Doesn't that mean on restarts plugin won't enter moving state?

[christocracy]

No. disableStopDetection doesn’t mean what you think it does. Long ago, I had the plug-in tune down location-accuracy to save power for short intervals while briefly stationary as reported by the motion api, eg stopped at traffic light.

[tananaev]

OK, I tried setting pausesLocationUpdatesAutomatically: false and stopTimeout to a high value. The problem is that if I kill the app and re-open it again, bg.BackgroundGeolocation.state.isMoving is false. That doesn't seem like what I want. I want isMoving to be basically ON all the time. Or am I misunderstanding something?

[christocracy]

You can provide isMoving: true to Config provided to .ready(config).

You’re also free to call .changePace(true), after .ready resolves, to manually toggle the plug-in into any state you desire.

[christocracy]

But State.isMoving is persisted through app restarts and will only be forced to false if stopOnTerminate: false.

[tananaev]

I have it as stopOnTerminate: false. Why would that force it to false? Shouldn't it be the opposite?

[christocracy]

Sorry, I meant stopOnTerminate: true.

[tananaev]

Could it be resetting because I do this on app launch?

await bg.BackgroundGeolocation.ready(myConfig);

Note that myConfig doesn't have any value for isMoving. If yes, how to preserve the state?

[christocracy]

You must call .ready(config) on app launch. You can always provide isMoving: true to you .ready(config)