Acknowledged
5 months ago

CRASH ANY DATA FIELD!

This baffled me. This crash does not produce a LOG file. I instrumented my code to write to the console and the app-specific log. Didn't make sense. So I tried a couple more DFs like this beer counter. CRASH. Every time. I expect this happens with every data field.

Here is how to reproduce this.

  • Device: Forerunner 955 (but likely happens with (many) other watches)
  • Firmware: 12.23
  • Activity: Pool Swim (but likely any activity)
  • Crash Trigger: SAVE operations (note: Discard does NOT cause a crash, only following a SAVE)

Most people, after a SAVE, will back out to the watch face, never seeing the crash. The activity is successfully saved and uploaded to Garmin Connect. But if, instead of backing out to the watch face, you page down to get back to viewing the activity screens, you'll see the data field has in fact, crashed.

My instrumented code shows this is actually what happens: After you hit SAVE, the code runs the onTimerReset() function, then runs the compute() function exactly twice, and then stops on an IQ crash. Every time.  It does not crash IN the compute() logic. It exits compute() but crashes before it enters it the 3rd time. Affects every DF I've tried.

I'll reply with an image since I can't include it here in the OP

DaveBrillhart
Parents
  • over 2 years ago

    But after that first BACK push to "Select Activity", then I can page down to get back to the activity screens. And can see the DF crashed. Can you try that on the 945 just for fun?

    Yes, on the post-activity summary pages (not the menu), if I press Back instead of Start (*), I'll be returned to the data pages for the same activity type. But all the fields are reset (for some reason I thought you were implying they wouldn't be) and no CIQ data field has crashed. So I guess the only difference here is the crashing.

    (*) If I instead press Start then select Done, I'm returned directly to the watchface.

Comment
  • over 2 years ago

    But after that first BACK push to "Select Activity", then I can page down to get back to the activity screens. And can see the DF crashed. Can you try that on the 945 just for fun?

    Yes, on the post-activity summary pages (not the menu), if I press Back instead of Start (*), I'll be returned to the data pages for the same activity type. But all the fields are reset (for some reason I thought you were implying they wouldn't be) and no CIQ data field has crashed. So I guess the only difference here is the crashing.

    (*) If I instead press Start then select Done, I'm returned directly to the watchface.

Children
  • over 2 years ago in reply to FlowState

    Yes, they all reset as they should. Except on the Forerunner 955 (at least), all Custom Data Fields crash. This isn't really a big deal. I can hit BACK one more time to get to the Watch Face before going back into an Activity, and then the CIQ DFs are fine. If that works ok on your 945, then maybe this is only a 955 firmware issue. Thanks for looking into this on another device!