Forerunner 165 CIQ Apps crash since Firmware update 22.22

jim_m_58 said:

It's kind of interesting this didn't come up with the public beta FW as it could have been stopped or fixed before it was released.  Are people not using public betas?

Are you using public betas? Lots of bugs make it into production that were reported on betas.

And actually, this bug was also reported on beta firmware, 3 weeks ago.

https://forums.garmin.com/beta-program/forerunner-165-series/forerunner-165-series---bug-reports/i/public-beta-version-22-xx/drawradialtext-symbol-not-found-in-dc

Is that enough time for Garmin to fix the bug in time for the production release? And are you suggesting that Garmin would’ve stopped the production release because of a CIQ bug? Clearly they haven’t done so, with several weeks notice (the current 22.22 production firmware for devices like 955, 965 and 165 was released 3 days ago). I just don’t think Garmin cares about CIQ that much.

I assume Garmin also has the ability to test beta software internally, as well.

CIQ has never been high on the list for groups like the platform groups.  Part of that could be they have their own stuff to worry about, and part could be they don't really understand CIQ

If a CIQ problem is reported for a platform beta, that would be a case where you probably also want to reports it as a CIQ bug report so someone in CIQ sees it right away

jim_m_58 said:

Maybe they could release a renamed earlier version

As per the beta bug report, this bug has probably existed since 22.14, so that’s very unlikely.

I think it would be unlikely in any case (e.g. even if they could just go back to the previous beta version), as releasing an earlier version means you lose all the improvements and fixes of the latest version, unless they’re “lucky” enough that the only meaningful change in the latest firmware release is this CIQ bug.

For context, there have been 2 additional betas between 22.14 beta and the current 22.22 production release: 22.18 and 22.21. For Garmin to roll back to a firmware version that doesn’t have the bug means they’d have to go back to at least one version before 22.14, meaning they’d be losing up to 3 beta versions worth of changes.

Also note that the version before 22.14 is 22.12, which is the first beta version on the 22.xx track. I think this means that it’s the first beta version since the previous 21.xx production release. So to roll back to 22.12 means you’re only 1 beta version ahead of the previous production release. Not only do you lose 3 betas worth of changes, you’re left with a beta that’s probably more unstable then the current production release.

At this point, why not just roll back to the previous production release? Maybe that’s what you meant? I still doubt they’d do this, unless there was a huge problem that affects normal usage (not CIQ apps). Btw, users of one the current devices that supports beta (Fenix 8 iirc) did notice that there was an emergency minor release on the production branch at one point, to fix a major issue that was affecting lots of ppl (the device shutting down in cold water due to software fault).

So I think if Garmin really wanted to make a quick fix for non-beta users, they would probably release an emergency fix (which would be identical to the fix that would appear in the beta), as opposed to rolling back production firmware. Ofc that assumes that a bug like this has high priority for Garmin (seems like it doesn’t)

I also have the same problem. After updating the firmware to 22.22 getVectorFont not working. Please fix it.

Please also fix the device in the CIQ simulator. With the last update the rounded text has been removed here as well

An update to the fr165 and fr165 music should be starting to roll out next week with the fix. Once that starts to roll out we'll get the device configs updated as well.

Device Configs for the FR165 series have been updated within the last 48 hours. Still, in the simulator, drawAngledText() and drawRadialText() are not available (symbol not found error). As 22.24 started rolling out some days ago, I expected this issue resolved?

SAME!!! Symbol Not Found crashes!! Using the latest SDK. Ugh. Two different places in a stable data field, occurs somewhat randomly maybe 5 mins into an activity.

DaveBrillhart said:

SAME!!!

Are you sure that’s the same problem?

This thread is specifically about FR165 crashes due to drawAngledText() and drawRadialText() not being found.

In your case, it’s Edge 1050 that’s crashing. Those functions are not even available in Edge 1050 in the first place.

DaveBrillhart said:

occurs somewhat randomly maybe 5 mins into an activity.

If you read the thread (or even just the last comment before yours) you would realize this isn’t about random crashes at all. (See above)