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.

Parents
  • So the issue isn't solved after 2 months. With SDK 8.x, support of drawRadialText() and drawAngledText() was dropped on the FR165. Therefore we have currently two choices: Discontinue support of FR165 on existing apps when compiling with SDK 8.x. Or stay with SDK 7.x for existing apps to further support customers who paid in the past for the app - but then the app won't be available to new devices like the Vivoactive 6, which isn't available under SDK 7.x. That's a BAD situation and totally avoidable by Garmin.

Comment
  • So the issue isn't solved after 2 months. With SDK 8.x, support of drawRadialText() and drawAngledText() was dropped on the FR165. Therefore we have currently two choices: Discontinue support of FR165 on existing apps when compiling with SDK 8.x. Or stay with SDK 7.x for existing apps to further support customers who paid in the past for the app - but then the app won't be available to new devices like the Vivoactive 6, which isn't available under SDK 7.x. That's a BAD situation and totally avoidable by Garmin.

Children
  • I'm unsure what happened so I will look into this and make some inquiries to the FR 165 product team and the CIQ Tools team as to why the device configurations aren't supporting it.

    The device has the true type fonts available and it shouldn't require a GPU to render angled and radial text.