Related

Bike and run activity mode malfunction

JillStephenson100
5 months ago

I have a new 955 (ver 19.18) that has been working fine for a week. Today I started a bike activity and it continually vibrated and showed a screen with a little clock at the top and a display of 0.00 (like a timer screen, perhaps). All I could do was stop the activity as it was unusable. I could stop the vibration by turning off the system vibrate mode but the display was still the same. The same happened with a run activity though a pool swim open water swim or walk was fine. I've restarted the watch several times and no change. All notifications and alerts that I can find are off and it has worked successfully several days ago. Any help? Thanks.

  • 0 1 month ago in reply to 7540935

    That time (1193 hours, 2 minutes, and 47 seconds) is also what I get. It looks like it's just 2^32 (the maximum integer number) milliseconds. It could also represent -1 under some circumstances.

  • 0 1 month ago in reply to 2688463

    So my watch hit this error today and this comment got me thinking. I just had set up a time alert on my race screen activity the previous night and this was the first activity after. As soon as I finished my planned workout this bug occurred and after I started a fresh run with no workout plan it occurred instantly. Given the timing relative to when I did set up an alert and this comment, I figured there's likely a code bug on how alerts are saved for various activities of the same or similar types. My theory was if I set up an actual alert on the misbehaving activity and then removed it, it would clear however Garmin's code saves the alerts. My theory worked and I was able to fix this without hard resetting my entire watch.

    If Garmin support or devs stumble upon this, I'd double check the code on how alerts are saved across activities and/or pulled. In non-technical terms given I don't know the codebase, it seems as if there's an improper pointer being stored or an activity is trying to reference an alert it doesn't have and when the code tries to pull an non-existing alert's value (in this case the time to alert) it defaults to -1 (or there's code that replaces null values with -1) causing it to constantly alert. The solution works because it properly resets however the vars are stored to be an empty list/hashmap/etc. (This is just the ramblings of a fellow SWE who hopes he can help other Garmin users so obvious disclaimer that I have no clue how the watch's code actually works)

  • 0 1 month ago in reply to 4543104

    Just to further clarify this comment and confirm my theory. I checked my other activity that I wanted to have an alert on and that alert’s status was turned off after doing the above fix. I can fully replicate this and the behavior is the same where I activate the time alert in my other activity and my normal run activity will constantly alert with the bad value when doing a non-structured workout. As soon as I do the above fix, it switches the alert off in my other activity. This seems like a clear bug where different activities should not interact with each other’s settings. 

  • 0 1 month ago in reply to 4543104

    Yep. Can confirm that. FR 955solar

    I have this issue only for my Walk activity only when having active alert for ultrarun. I'm getting 1194:02:47 time alert. It goes away with this ultrarun alert disabled or an actual walk alert set (can also be disabled).

    Agree with initial diagnosis. Seems like some hashmap/hashset issue, as alert from one activity type affects another activity. Missing activity type check when fetching number of alerts?

  • 0 29 days ago in reply to 4543104

    This worked for me. Thank you. Another activity had -1 frequency in an alert. Took it out and solved issue.

  • 0 29 days ago in reply to 4543104

    Great find! I've seen a handful of posts about this problem on various current Forerunners (255, 265, 955, and 965). Someone else also posted a workaround where adding an alert to the broken activity will fix it. (They were also seeing the problem with structured workouts.)

    Hopefully it will be fixed soon.

    I'll also note this isn't the first time Garmin has had a bug where multiple things inappropriately share the same settings/data:

    - in the past, a CIQ data field installed in one activity might be silently/invisibly active in another activity where it was not installed

    - under some circumstances, settings for one CIQ app will be inappropriately displayed for a different CIQ app (if the settings definitions are similar or identical)

    One would hope that once a given error pattern is discovered, steps would be taken to avoid it in the future...

  • 0 1 day ago in reply to 4543104

    THIS SOLVE MY ISSUE !!

    Same problem : Error 969 1193:02:47 every time I start a new run or hike, without any goal. Deleted every activity alarm and now it works ! Thanks !

    GARMIN DO SOMETHING PLS