Acknowledged

FR645 and others since fw 7.20: major issues with custom fonts

  • Looks like I fixed it years ago my using a fnt file from bmfont instead of one I'd hand modified (see below).  For the first time in years, I charged the 645m. and let the CIQ mobile app update my watchfaces to current ones built with the latest SDK.

    Everything is running fine.

  • There's nothing the user can do to fix this. Just stop using watch faces that constantly throw errors. If you're lucky enough to contact the developer, and they're merciful and still involved with the Connect IQ platform, and they recompile the app in Visual Studio Code (instead of the old SDK and Eclipse), then yes... you can go buy a lottery ticket.

    Clearly, Garmin believes the Connect IQ app developers, not Garmin, are responsible for this issue.

  • Hot fix? How many years ago was the last firmware version of fr645 released?

  • This is a pretty serious regression, a firmware update breaking custom fonts across all ConnectIQ apps and watchfaces simultaneously suggests Garmin changed something fundamental in how the font rendering engine handles third-party font resources in fw 7.20!

  • This is a pretty serious regression, a firmware update breaking custom fonts across all ConnectIQ apps and watchfaces simultaneously suggests Garmin changed something fundamental in how the font rendering engine handles third-party font resources in fw 7.20! Triumph Garmin really needs to push a hotfix ASAP since this isn't just affecting developers but end users who paid for watchfaces and are now just seeing that dreaded IQ! symbol instead! Dart