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

"move" mode updates are too slow #778

Closed
gardiol opened this issue Feb 3, 2020 · 5 comments
Closed

"move" mode updates are too slow #778

gardiol opened this issue Feb 3, 2020 · 5 comments
Assignees

Comments

@gardiol
Copy link

gardiol commented Feb 3, 2020

  • App build number: 2.1.3 (21302)
  • Android version: Android 5.0.2
  • Device: Samsung Core Prime LTE

I use owntracks as a "pet GPS" tracker. I hooked up an old phone on my dog collar in a waterproof pouch and i am using OnwTracks to know where she is.

Unfortunately "move" mode let GPS switch off for too long and the next point takes a long long time to get a fix. This is always in the open (meadows or at most light woods), and the phone with another tracking software (Alpine Quest) has flawless GPS reception. When using OwnTracks, the resulting track is jumpy and fragmented.

My guess is that one point every 30 seconds is way too far apart... Constant GPS on or at least configurable intervals would be much more useful.

Also, a dog moves way faster than an human and on much more irregular directions (where the rabbits go... :) )

Is there anything i can try?

@gardiol gardiol changed the title "move" mode updates are too slow / too far awa "move" mode updates are too slow Feb 3, 2020
@growse
Copy link
Collaborator

growse commented Feb 3, 2020

I'm generally against providing more configuration options to end users, but I think there may be a case to make for allowing users to customize the intervals specified to the runtime in each mode. The challenge here will be exposing this to the user in a non-confusing way. Experience shows that the way the location fixes work right now is already too confusing.

An initial option might be to bury everything under "Advanced Options" and see if that at least helps to solve the problem, then work on making the config UI more intuitive.

@gardiol
Copy link
Author

gardiol commented Feb 3, 2020 via email

@growse
Copy link
Collaborator

growse commented Feb 3, 2020

I should have some time today to work on some of the open issues, let me see if I can get a PR together that lets the interval be more configurable.

@growse growse self-assigned this Feb 3, 2020
@gardiol
Copy link
Author

gardiol commented Feb 3, 2020 via email

growse added a commit that referenced this issue Feb 3, 2020
For issue #778, allow the user to configure the locator interval for
Move mode, keeping the default at the old hard-coded value of 10.

Also surface both locator interval configuration options in the Advanced
config UI.
growse added a commit that referenced this issue Feb 3, 2020
For issue #778, allow the user to configure the locator interval for
Move mode, keeping the default at the old hard-coded value of 10.

Also surface both locator interval configuration options in the Advanced
config UI.
@growse
Copy link
Collaborator

growse commented Feb 3, 2020

Added this now, so closing. You can either generate an APK yourself or wait for the next beta release to test.

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

No branches or pull requests

2 participants