Crossover Solar Tactical producing broken swim data?

I'm running into an odd issue with the Crossover Solar Tactical when using indoor swim. It looks like some of the metrics are being calculated incorrectly and end up hitting values over 4 million for the last few minutes of a recorded swim - swolf in particular. Times for these graphs also stretch into several days, despite my swims rarely lasting over 45 minutes. This behaviour has persisted through a factory reset of the watch, along with fully clearing Connect's cache and stored data and re-syncing the watch.

I've attached my latest recorded swim as an example of this. It might be a bug specific to the graphs in Connect (including the web version) as the stats show correctly on the watch and the stats screen in Connect- the graphs appear to be the only broken area, as the 4 million plus swolf is evidently not taken into account during averaging.

The watch is on the latest firmware version (16.11). This issue has occurred on Connect releases 5.3 through 5.4.1, though it likely predates 5.3 as my first recorded swim was on that version.

Swim activity in question: https://connect.garmin.com/modern/activity/16880119916?share_unique_id=15

I can share two more pool swims with the same issue if additional data is needed.

Top Replies

All Replies

  • Looks to me as a hardware problem of the accelerometer. Does the watch count steps correctly? How does the Cadence data look at running? I would definitely recommend reaching out to the Product Support through their website at https://support.garmin.com. Use the Phone or Chat options for an instant response. Email exchanges usually take a few days. 

  • I think it's pretty unlikely that the accelerometer hardware is the issue here. It correctly tracks things like steps, running cadence, move IQ events et cetera.

    The absurd values recorded in the activity listed above are suspiciously close to multiples of 2, possibly indicating an overflow of some sort (likely a software bug). An accelerometer fault also wouldn't explain the extended time on the graphs.

    Setting the graphs to display by distance also removes the erroneous time extension - indicating that something else is going on here.

  • In fact, the activity is 1193 hours long (almost 50 days), and all the data is crammed on the very beginning and the very end of the activity. You can zoom on that parts to see it, or you can change the viewing mode to Distance or to Length + Rests.

    And that long duration of the activity skews then in the consequence the other metric too. I do not know how it happened, whether the watch was set to a wrong date and then resynced the time, but more probable is that the FIT file got corrupted somehow (for example due to a crash and reboot during the swim). You can export and post the activity zip file, and ask whether a kind fellow user would have a look at it with some external tools, and attempted to repair. Lately it is almost exclusively  who helps people with broken activity FIT files.

  • The issue here is that every swim activity produced by the watch has the same issue. So I'd have to repair each swim file after swimming.

    That's not an acceptable solution. The watch should produce usable files consistently.

  • That's not an acceptable solution.

    Contact Garmin Support.

  • That's not an acceptable solution

    What do you imagine under acceptable solution on the user forum? You can try resetting the watch to factory defaults. If not helping, indeed reach out to the Product Support, the outcome you get is not normal, and we can only offer helping you with fixing the existing data, but if the device needs to be exchanged, you have to speak to Garmin.

  • The purpose of posting on the forum was to check if this was an isolated issue, or if it's a known problem with a simple fix. That way I avoid wasting support's time if possible.

    I appreciate that you're trying to help here; it appears you're quite active on the forums and that's a good thing. But so far:

    • You've blamed an accelerometer that is working, and more importantly couldn't be the full cause of the issue to begin with due to skewed time values.
    • You've failed to even read the post, which clearly states that this occurs with every swim file and instead suggested that I manually repair (or have someone do this for me) every swim the watch creates.
    • Now you suggest resetting the watch to factory defaults. Not trying to be rude here, but this is getting annoying. Read the post before replying to it. I have already factory reset the watch along with re-syncing it to Garmin Connect, as stated previously.

    Please. If you can't put in the effort to understand the issue, don't bother replying. It doesn't help anyone.

    As this appears to be an isolated issue, I will be contacting support for troubleshooting and advice.

  • This is my next course of action. I'm going to leave this marked as un-solved for now; once I get this resolved with Support, I'll come back here and add the solution in case this comes up for others in the future.