retry_time ignored if previous point was discarded
Opened this issue · 0 comments
This is a bit of a weird issues that I've run into for a while. It's not 100% and when it happens it's usually after I didn't move enough during the logging interval.
I'm using Tasker to switch between profiles and did switch just before the first point was logged successfully. Not sure if that's relevant though.
This is the timeline of what happens in the attached log.
08:05:33
A point is logged. An alarm is set to log the next point in 60 seconds (time_before_logging).
08:06:35
The first attempt to log the next point fails due to the accuracy not being good enough.
08:06:42
The accuracy is good enough, though no point is logged as the distance to the previous point wasn't big enough. An alarm is set to log the next point in 60 seconds.
08:07:42
Again, the first attempt to log a point fails due to the accuracy not being good enough. Instead of trying again for 30 seconds (retry_time), the app sets an alarm for 60 seconds and goes to sleep.
08:08:42
No point is logged as there is no GPS fix (which is fair, I was underground at this point). Based on the log the app continues to try to get a fix though so everything is back to normal.