• Replies 2 replies
  • Subscribers 20 subscribers
  • Views 521 views
  • Users 0 members are here
Options
Related

CGM & Garmin IQ Crashes with some devices (e.g. F45, 735XT)

km19

I am developing Clear & Powerful watchface (apps.garmin.com/.../35a64cd7-7cff-4903-b138-48633373384b)  and some users are reporting to me that CGM or GIQ crashes while changing settings. 

Watchface doesn't crash - it's CGM does. It's very difficult to investigate while I can't reproduce this behavior.

I search the forum and double check the code - with appropriate checks against nulls, type of values (float, numbers, boolean), with default values in code etc.

Have no idea where to search now. Some additional info:

- watchface has a separate code & configuration for watches with 48kb (F45 & Swim2)

- watchface has separate resources (but common code) for different size of watch

- CGM crashes were reported for now by F45 (separate code with oldest version of watchface and old version of settings), but also 735XT users (with common code & settings)

- crashes of CGM and not specific parameters changing depended

- settings are quite big (45 KB for now) - maybe there are some limitation for that file ?

- maybe there are other limitations ?  number of drop down options in list ?  length of id ?

- in newest version I added support for Garmin weather info from Toolbox.Weather - I am checking in code if Weather is available in 

Have no clue where to investigate - maybe you can point some ideas or check ?

  • A lot of memory contraints on these 2 watches. When you make un update settings the size of the new variables adds to the actual variables and the file settings is detroyed. The maximum memory use is less than 43K pour F45 and less of 55K pour 735. 

    Use exclude code in code and in manifest file, reduce size of settings files for these two watches

  • in reply to riedid74

    I understand. So you have to have more memory margin while having bigger settings.
    I started to refactor code to have separate settings & source (using jungle) for all legacy watches (sdk < 3.0), which have other limitations as well (no. of colors, memory, sdk).
    Thank you for your help.