Can someone tell me exactly how Avare gets the time stamps that it puts into the KML files it creates?
I have some strange effects showing up in my KML tracks. I suspect part of the problem is in my Stratux, and it might be that there are other wifi networks involved in some way, but I'm also pretty sure that Avare's behavior is significant in trying to get my configuration correct. Hopefully this forum can tell me what to look for.
I have always found that the timestamps in my KML files are wrong in the sense that they appear to UTC (from the numbers) but they're marked as MDT/local. My tablet (Galaxy Tab, Android 11) shows the right (local) time, and I believe it has picked this up from my home network. That time does not, so far as I have noticed, change when I connect to my Stratux, nor to the glider-club's "shack" network. I'm pretty sure the tablet knows that it's Mountain time too.
That part would be "nice to correct" but doesn't bother me a great deal, frankly.
But yesterday, after some longer runs, I noticed that there are two different times showing up. So, for example and from memory, I have times IRO 17:00 at one of the recorded points, and subsequent points are in the 22:00 range. Later points might go back the "earlier" time. Since the bird I fly has only a tach, and no hobbs, I have previously used the times on the first and last points on a KML track to determine flight time, but minus five hours isn't really going to work ;)
I have the Avare GPS source configured to "Avare apps only".
How might this happen, and what should I try toward the goal of stable (and, if possible, correctly annotated) timestamps?