Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Daylight saving time breaks detection of new activities? #165

Open
msitms opened this issue Apr 16, 2017 · 2 comments
Open

Daylight saving time breaks detection of new activities? #165

msitms opened this issue Apr 16, 2017 · 2 comments

Comments

@msitms
Copy link

msitms commented Apr 16, 2017

I'm using antfs-cli with my Forerunner 310XT. From time to time, it tries to download not only the new files, but all activities on the device. This is particularly painful when you're affected by the problems described in #132 and #145 -- in this case such a download might run for the whole night. (There is also no convenient way to delete all activities on the device except for the last few that have not yet been transmitted...)

Now it occurred to me that the last time this happend was after the daylight saving spring change. Both devices (my computer and my Forerunner) use the same local time zone and automatically adjust to daylight savings time, but depending on how activity time stamps are stored in Forerunner internally, and how the antfs-cli sync operation compares these time stamps to local file system time stamps, this might cause all activities to be recognized as new.

Maybe it helps to convert all time stamps to UTC before comparing?

@henningspruth
Copy link

I'm observing the same issue (downloading all "old" activities), and this only starts to happen after the DST changeover.

@jklaise
Copy link

jklaise commented Apr 8, 2018

@henningspruth same here, would not have realized it is DST related! It seems that all my old activities have somehow got new timestamps on the watch (as in all on the day first day of attempted upload after DST), hence the re-download, so it is possible that it's fundamentally a firmware issue (I'm assuming here antfs-cli cannot alter the activity timestamps on the watch itself).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants