Under Review
over 1 year ago

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

ConnectIQ apps, watchfaces, widgets with custom fonts are failing and showing the IQ! symbol. See these topics for more information:

https://forums.garmin.com/developer/connect-iq/f/discussion/324531/major-issues-with-custom-fonts-after-latest-device-fw-updates

https://forums.garmin.com/developer/connect-iq/f/discussion/324099/forerunner-645-firmware-7-20-errors

https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-645-645-m/324599/iq-watch-face-broke-after-7-20-update/1574757#1574757

I'm seeing many reports of unhappy users with failing watchfaces. Please fix this as soon as possible Garmin. 

VAW.BE
  • over 1 year ago

    I just started getting reports of this with one of my DF's on both the 645 and E130+, which matches the description here.  These are fonts created with BMFont and no hand editing.  ERA show the first crash from this mid April.

    Is there any resolution in sight for this?

  • over 1 year ago in reply to Travis.ConnectIQ

    Yes, there will be implications. It will break code that relies on correct reporting of the font ascent and descent, using Toybox.Graphics getFontAscent() and getFontDescent(). Back to my earlier example, the font height == 17, ascent == 13, descent == 4. After setting the base to 17, ascent == 17, descent == 0.

  • over 1 year ago in reply to myneur

    I've been told the difference between the base height and the character height is supposed to be the area for accents to be drawn. Based on what I'm seeing with some generated fonts, I'm not sure that is actually correct.

    If you're using a custom font just for an easy way to do bitmap coloring for status icons, there should be no issue making base equal to the height of 0. If you are actually drawing text with it, there may be implications.

    That said, I have reproduced the issue using a font that is not hand edited using DejaVuSansCondenced.ttf as suggested above. 

  • over 1 year ago

    What is the implication of rising the base value? 

    E. g. I think it will clear everything below up to the base level even for characters that are smaller, right? 

    Any other implications of changing the base to contain the height of the 0 as a hotfix for this bug? 

    Thanks

  • over 1 year ago in reply to 2769103

      wrote:
    Also GPS is worse with 7.20 update. Still think they do all this on purpose to buy a new watch.

    You can think that, but if you do, can you please do it in a thread outside of this one? I'm trying to work on this issue and the unnecessary interruptions are not appreciated.

    If you have issues with GPS please post your comments in a thread dedicated to that topic.