IQ fields keep crashing

cycleanalyze 1 month ago

Hey all,

I'vehad lots of problems with IQ fields crashing. Is there some way to get a crash log?

If I have just windfield, Xert, powerslider, coretemp running all is fine.

If I add HDrop, it crashes. If I add eat my ride carb balancer, it crashes.

Those two working on their own without the others work just fine.

Is there some sort of memory allocation problem?

The developers are of zero use in this "works for us"

0 mcinner1 1 month ago

There is no documentation in the IQ SDK about limitation of FIT file contributions, but developers are reporting: there is a limitation!
FIT file contribution means, if IQ datafields (or apps) write data to the fitfile during a activity recording.

Various experiences about the maximum number are shared among developers. One say: if all IQ apps together exceed 16 fit contributions, the apps will crash. I cannot confirm - my datafields have some contributions but I never got problems reported.

If you have many contributions in your IQ apps, it‘s worth to test it by turning off some of them (if possible).

0 mcinner1 1 month ago

cycleanalyze said:
Is there some way to get a crash log?

Yes! In the directory /Garmin/Apps/LOG there are logfiles (both log and bak), but only the developer can „read“ which line of the program is causing the crash.

And - btw - the developers themself get ERA reports about crashes of their apps with detailed information about the line of causing a crash.

0 cycleanalyze 1 month ago in reply to mcinner1

I bet you nailed it here. I'm going to monkey around with it. Thanks!

0 cycleanalyze 1 month ago in reply to mcinner1

mcinner1 said:
If you have many contributions in your IQ apps, it‘s worth to test it by turning off some of them (if possible

Sadly none of the data fields have a toggle for turning off write to fit file

0 mcinner1 1 month ago in reply to cycleanalyze

Yeah, that‘s a pitty…

(My datafields offer to disable contributions for that reason.)

0 MGRogue 1 month ago

Have you tried fully resetting the device to factory default settings?

If the device isn’t quite working as intended, that’s usually what I would do in order to get things running correctly, as long as I don’t lose any personal data, although the data is synced to the account anyway so I don’t believe you can lose it

0 cycleanalyze 1 month ago in reply to MGRogue

No haven't gone down that route, it will not help anything. The combo of fields causing the crash is so repeatable and reliable that I don't think it's some squishy problem that an erase/restore combo is good at dealing with.

0 mcinner1 1 month ago in reply to cycleanalyze

I have opened a discussion in the IQ developer forum…
https://forums.garmin.com/developer/connect-iq/f/discussion/390655/iq-datafields-crashing-caused-by-fit-contributions

0 cycleanalyze 1 month ago in reply to mcinner1

hey thanks I'll monitor that thing

0 flocsy🤠 1 month ago in reply to cycleanalyze

I think it's worth to point this out to the developers of all those data fields. Hopefully at least some of them will be kinds enough to add such setting.