You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering if there is somewhere a document where the settings are described and maybe some suggestions about best practice.
I guess all users share the same challenge: do not drain the battery to much but try to capture enough details.
The results I am getting are not bad at all so far at the same time the google location history provides more useful data out of the box. For example i automatically shows how long i spend a place A.
I guess in theory the interval (how often owntracks client checks the location) and the minimal location change are defining how accurately i can see that via owntracks. But in reality it did not work that well for me. I am not sure if maybe some location updates the client got did not meet the accuracy setting (500m) and I am also not sure if the frequency which is set in moving mode is about the app detecting that i am moving or is this when i change from significant changes to move (probably it is that ....but might be nice if the app also detects if the device is not moved at all or if it is moved (there are sensors which detects motion i am not mistaken).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am wondering if there is somewhere a document where the settings are described and maybe some suggestions about best practice.
I guess all users share the same challenge: do not drain the battery to much but try to capture enough details.
The results I am getting are not bad at all so far at the same time the google location history provides more useful data out of the box. For example i automatically shows how long i spend a place A.
I guess in theory the interval (how often owntracks client checks the location) and the minimal location change are defining how accurately i can see that via owntracks. But in reality it did not work that well for me. I am not sure if maybe some location updates the client got did not meet the accuracy setting (500m) and I am also not sure if the frequency which is set in moving mode is about the app detecting that i am moving or is this when i change from significant changes to move (probably it is that ....but might be nice if the app also detects if the device is not moved at all or if it is moved (there are sensors which detects motion i am not mistaken).
Beta Was this translation helpful? Give feedback.
All reactions