Vivoactive Doesn't Save FIT Contributor Lap & Session Properly

The Environment:
- Device: Vivoactive FW 4.40

Description:
In the simulator the vivoactive properly records the last FIT contributor lap and session information. On the device it records the record and all except the last lap data correctly. The FIT contributor session and last lap information is not properly recorded.

Steps to reproduce the issue:
Use the following link to get a sample project illustrating the problem: https://www.dropbox.com/s/s4qmves3mv3ed8a/Test_VivoactiveFITSave.zip?dl=0. Run the project in the simulator to generate a FIT file and then run the application on a device to generate a FIT file. Compare the results to observe the missing session and last lap information.

Coleman.Apps over 8 years ago

Hey,

I've got a ticket created, but it's been sent to the device team as it seems to be device SW driven. I'll reply back here when I have more info.

Thanks,
Coleman

loneshepherd over 8 years ago

Any update on this issue?

Coleman.Apps over 8 years ago

Hey,

It's currently in the hands of the device team. It looks like they have it prioritized but I don't see any timelines associated with it yet. Once this is closed I will make sure to post here in the forum.

Thanks,
-Coleman

loneshepherd over 8 years ago

So....3 months later...what's new here?

HerrRiebmann over 8 years ago

Nothing!
I´m also struggeling with the fitcontributor. Due to the fact I only own one device, I cannot say if it is related to the Vivoactive or the fitContributor.

Some Threads about it:
Problem-with-FitContributor-when-lap-info-is-used
FitContributor-breaks-multisport-activities
Fit-Contributor
Fenix-3-does-not-record-Session-message-in-FIT-file (Vivoactive Fix)
Known-Issues-Thread

The Simulator creates the data (at least for my eye) correct. MonkeyGraph shows the FieldNames, but #VALUE? as value.
Every second fit-file includes the data (similar to simulator data). But none of it will be displayed. The App, off course is released, to ensure the names and types are known to GC.

Coleman.Apps over 8 years ago

Hey Everyone,

I was able to check on some things with the device team. It sounds like this issue resides in the device software. This is only this issue and does not apply to the other fit contributor issues that we have been tracking. The device team is aware. However, this ticket is in their backlog as their main focus is on the current gen vivoactive. Don't hear me say that this is just a no-go, but it is a lower priority right now in the grand scheme of things. One of the things we want to do is be as honest and fair as we can when giving you a status update so I wanted to be a clear as I can on this one. If there is any movement on this, I will make sure to post in this thread. Until then, I am going to go ahead and close this. Thank you all as always.

-Coleman