Acknowledged

22.22 FR165 DrawRadialText symbol not found

Since the last update, 22.22, method Dc.drawRadialText stopped working on the FR165 and FR165m.
It works fine in the sim, but crashes on a real device with error "Symbol not found".

I reported this last month when it was still in Beta as well: 

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

Now the software is rolling out, apps that use this will method will crash (including two of my watchfaces) with no easy way to work around this.

  • On a somewhat related note, it's interesting to me that fr165/compiler.json has "enhancedGraphicSupport": false. In the past it's been stated (or assumed) that a true value for enhancedGraphicSupport means that the device has a GPU, whereas a false value (or the absence of the key) means the device does not have a GPU.

    I always assumed that a function like drawRadialText would require an actual GPU on the device. (Yes, I am aware that the supported device list for drawRadialText includes fr165).

    It was also previously assumed that CIQ 4 (and beyond) devices would all have GPUs.

    This apparent inconsistency has come up before (specifically in relation to new devices like fr165 and vivoactive5 which have enhancedGraphicSupport == false, but nonetheless support certain "advanced" CIQ 4 graphics functions), and I wish Garmin would clarify a few things.

    1) Is enhancedGraphicSupport == true if and only if a device has a GPU? Or does enhancedGraphicSupport == true actually imply something else?

    2) Concerning the "new" CIQ 4 graphics features - e.g. vector fonts, affine transformations, draw radial text - which of them actually need a GPU? Are some of these functions actually implemented in software, for CIQ 4+ devices that don't have a GPU (if any such devices actually exist)?

    > It works fine in the sim, but crashes on a real device with error "Symbol not found".

    Yeah, fr165/fr165.api.debug.xml still contains drawRadialText.

    > Now the software is rolling out, apps that use this will method will crash (including two of my watchfaces) with no easy way to work around this.

    I guess you could use a has check for symbols like drawRadialText and set the --disable-api-has-check-removal compiler flag.

     

  • Too bad the beta forum is a "write only" forum Disappointed