Are the activity data provided with a time delay?

I find that when I just display data from ActivityInfo (not even recording it to FIT), there's a delay of roughly 1 second, so I don't think there's much you can do about it.

7016150 said:

Is it somehow possible to write the data to the current time step or in my case the time step before?

If you wanted to be in sync with native data, wouldn't you have to display/write data from 1 second in the *future*?

e.g. If I get the data for 1:20 at 1:21, then it's already too late for me to write 1:20's data.

Unless you mean that you want to delay writing of native data by one second, which isn't possible.

7016150 said:

That would mean that it is a default behavior having a delay.

Yes, that's what I was alluding to. You can test this easily by reading ActivityInfo.timerTime, formatting it as [hh]:mm:ss, displaying it in your data field, and testing your data field alongside the native Timer field. When I've done this (as part of a more complex app), I've seen a delay of approximately 1 second. (Sometimes the delay can be longer or shorter)

7016150 said:

I want to write my data in line with the native data.

Yes I understand that but it's not possible for you to write your own delayed data "in the past" so to speak.

I think the only way to theoretically accomplish what you want would be to delay the writing of all other (native) data, which also isn't possible.

When you do a setData, that doesn't write to the fit.  Fit files are written at most every second, so your setData may be written a second later.

That's just the way it works.

That's pity but thank you for confirming my impression and checking my code indirectly.