• Replies 15 replies
  • Subscribers 19 subscribers
  • Views 560 views
  • Users 0 members are here
Options
Related

Both CIQ datafields in the activity crash suddenly

flocsy🤠

I am in a walking activity with 2 CIQ DFs. All of a sudden both display the IQ icon, without anything in ERA or in the device logs.

fr965 FW 28.08. I don't expect this to be fixed ever, as Garmin seems to have abandoned both fr965 and CIQ lately, but maybe other devs will have something important to add.

  • What data fields?  Do both crash if you only use one at a time? Is there anything about when they crash?  For example. you'll likely lose GPS if you are walking through a tunnel.

  • in reply to jim_m_58

    One does use GPS, but GPS was disabled (Walk Inside), the second doesn't even use GPS.

    One is full screen (this was on my display), the other is a 1 field that is on the second screen inside a 6 field layout.

    I don't know what causes the crash, but I don't think it's caused by something in the datafields. Probably some bug in the firmware 

  • Just happened to me again today, 4 times in a 10 minute walk. Nothing in ERA after syncing via Garmin Connect and Connect IQ apps.

  • in reply to flocsy🤠

    Which CIQ DFs?.  All mine are working fine.  It could be one of them is causing a problem to the CIQ VM and it takes both of them out.  This has happened in the past.

  • in reply to jim_m_58

    First it was two of mine datafields, but then I started to suspect that one of them might cause it. Replaced it with another CIQ DF (not mine) and it still happened (it happened 5 times during a 1 hour walk). Then I changed the other too, and it didn't happen for a while. So I now have the suspect DF (of mine).

    However I have no idea where to start. No crash files on the device. This itself is a FW bug IMHO. Even if let's say the VM intentionally kills it there has to be a crash report! Otherwise how can I

    a) know about it (maybe it happens to hundreds of users every 2nd day?) and

    b) fix it (if it's something I can, which probably is the case, if indeed it happens only because of one DF, and not because of thousands others in the store.

    c) if one DF causes it why the other is also killed?

    Is it possible that the VM kills them because of some watchdog, like we have for the watchfaces? I'll add some code to measure how long the compute and the onUpdate takes and save it to properties so I can see if it's high (though hard to know, when there's nothing to compare to.

  • in reply to flocsy🤠
    flocsy🤠 said:
    b) fix it (if it's something I can, which probably is the case, if indeed it happens only because of one DF, and not because of thousands others in the store.

    If it was happening with a bunch of others, there would be reports of it here or in bug reports.  I suspect it's issolated to your DF

    flocsy🤠 said:
    c) if one DF causes it why the other is also killed?

    As I said, this has happened in the past where one Df takes out any other running.

    If you can narrow it down to one of yours, do a bug report pointing at that specific DF and Garmin has the tools to track it down.

  • in reply to jim_m_58

    How? There's nothing in CIQ_LOG? Even bugs that happen to many people but don't always happen, so it's not easy to reproduce (even though I can reproduce at about 20% success rate) are not fixed for years. Like the bug that CIQ datafields suddenly disappear and become Timer. And even I can't describe it very well, and this can not happen for a few weeks, and then it can happen in 1 activity number of times. The only fact I have is the app id. Also I don't believe they'll put effort in finding a bug in my app, when there are hundreds of firmware bugs related to CIQ that we reported and are not fixed yet :(