talk
talk copied to clipboard
Position confused by Cell Towers
App build number: 2.4.9 (20409000) Android version: 10 Device: Samsung Galaxy S9
I use Owntracks for tracking my route in a sailboat, and upload the track to Wordpress. It function very well expect one issue.
It looks like Owntrack send wrong positions when I am near a Cell Tower. I have tried to find answers in the documentation but without luck. I use Owntrack on Android but guess the problem is the same with IOS.
Please see the attached GPX file for understanding the issue.
Note: I have edited your comment to remove the configuration which included your passwords.
If you want to send us private data (your GPX file and/or your configuration) do so to [email protected] please.
@jpmens: Thanks. I send the files to Support:-)
Re-opening as not yet completed.
Is this an example of what you mean by "wrong position", or did you actually land here?
This is exactly what I mean. I am by boat and not on shore:-)
Bonus info - If I use similar apps fx. TrackMe, with the same phone. I do not see this problem.
Note that the credentials are still visible through the edit history, so at the very least it's time for a new password. :)
Thanks for reminding us, @linusg
Password is changed! Again - thanks for helping me when I am so stupid with my bad copy/paste operation:-)
Bonus info - If I use similar apps fx. TrackMe, with the same phone. I do not see this problem.
Are you using owntracks in "move mode"?
Can you check what value you have for "Ignore inaccurate locations" (in the advanced settings, or under ignoreInaccurateLocations
in the config editor). I wonder if setting that to a lower value will filter out the non-GPS locations.
Yes - I use Owntracks in "Move mode".
ignoreInaccurateLocations = 0
Yes - I use Owntracks in "Move mode".
ignoreInaccurateLocations = 0
Car you try setting this to a higher value? If you have this as 0, OT treats every location received from the device as 'publishable', regardless of how accurate it is.
That point on land that you saw probably has an accuracy radius that includes your actual location, but is much larger (less accurate) than previous points.
I have now tried to set ignoreInaccurateLocations = 100
The result is the same.
important observation - the problem is only related to Android!
I have now tested OwnTracks on iPhone, Samsung phone and Lenovo tablet. The problem is only seen on Android - OwnTracks works perfectly on iPhone.
We're tracking this with detecting inaccurate locations in Android; the feature should be in the next release which will be released as soon as it's ready.