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
first of all many thanks for this app, love it and especially the recent updates of the visit system were improving things a lot for me.
One thing that started for me since a few versions is e.g. on my daily commute (roughly 5km and takes about 10–15 minutes) Currently, the visit detection seems to be triggering incorrectly here:
Instead of creating visits at home and at work:
I see a visit created ~500–1000m after leaving home, and assigns more or less the time it captured points while being at home
Visit is created ~500–1000m before arriving at work, or even in the middle of the track and also aligns with the time I have roughly been at work when the visit is created
Is there a recommended setting to improve this? I want to avoid visits being created in areas where I only passed through and ensure they are only created where I actually stayed. Would it be better to activate or deactivate the "Smart density fill" in this case?
I don´t think its an issue but rather induced by my setup: I'm running Graphene OS and not using Google Location Services. I use GPS Logger, outdoors track a point every 10-15 seconds, indoors I automatically switch to network-based tracking when connected to WIFI with lower frequency which only tracks a point every ~5 mins. This probably means the point density at the moment the visit is detected at the start/end points is too low. Maybe some of my issues would be solved when visits are created later.
On a wishlist of improvements I´d love to see for me would be:
Edit existing visits:
change the Area/Place a visit is assigned to after it’s been detected
manually adjust the start,end orduration of a visit
A workaround would probably be to delete the visit and create it again, but it requires a bit navigating from "timeline" to "create" and back.
Capturing Visits when there are long gaps between points
This happens e.g. when I arrive home, the tracker logs a few points, then it changes to network based tracking with low frequncy but while asleep my phone is in plane mode and no points are tracked, when turning off plane mode the tracking continues the next day.
It would be great if these "gaps" when during a few hours there are no points tracked but the location is still the same (with a certain threshold) could also be tracked as visits.
Possibility to deactivate notifications for new visits
I upload points frequently and therefore constantly visits and notifications are created, in this case I don´t find it value adding and would rather deactivate it.
Prioritize visit suggestions
Whenever a visit is created, prioritzize if it has been used for previous visits often or if an area or place exists the user created
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
first of all many thanks for this app, love it and especially the recent updates of the visit system were improving things a lot for me.
One thing that started for me since a few versions is e.g. on my daily commute (roughly 5km and takes about 10–15 minutes) Currently, the visit detection seems to be triggering incorrectly here:
Instead of creating visits at home and at work:
Is there a recommended setting to improve this? I want to avoid visits being created in areas where I only passed through and ensure they are only created where I actually stayed. Would it be better to activate or deactivate the "Smart density fill" in this case?
I don´t think its an issue but rather induced by my setup: I'm running Graphene OS and not using Google Location Services. I use GPS Logger, outdoors track a point every 10-15 seconds, indoors I automatically switch to network-based tracking when connected to WIFI with lower frequency which only tracks a point every ~5 mins. This probably means the point density at the moment the visit is detected at the start/end points is too low. Maybe some of my issues would be solved when visits are created later.
On a wishlist of improvements I´d love to see for me would be:
A workaround would probably be to delete the visit and create it again, but it requires a bit navigating from "timeline" to "create" and back.
All reactions