Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problem using setConfiguration to change mode from move to significant #1977

Open
JuliusFruitfly opened this issue Feb 12, 2025 · 0 comments

Comments

@JuliusFruitfly
Copy link

I'm using setConfiguration to go from

'monitoring': 2, 'moveModeLocatorInterval': 60

to

'monitoring': 1, 'locatorDisplacement': 100, 'locatorInterval': 240

I would expect to get a location update no faster than every 240 seconds only when distance moved is greater than 100m

In fact, I am getting updates every 60sec (approx). i.e. the moveModeLocatorInterval. The distance moved is minimal, a metre or two.

This sort of update usually works OK.

Am I misunderstanding the doc? The significant mode/android section mentions moveModeLocatorInterval, but only to say its relevant for move mode (?).

Attached log shows config update and three subsequent location updates.

Thanks

locationLog.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant