• Replies 49 replies
  • Subscribers 21 subscribers
  • Views 4226 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.

  • in reply to flocsy🤠

    Interestingly I somehow managed to get Settings > Activities & Apps > [Activity] Settings > Data Fields into a state where the normal contents of CIQ data fields *are* shown (instead of "IQ..."), both for existing fields and the blinking preview that's shown when you edit an existing field (without actually applying the changes).

    So maybe I will pivot and say I don't care so much anymore....

    flocsy🤠 said:
    No, because it's IQ... which according to Brandon is not published to ERA (or actually there's no error file locally)

    But I've already verified that I see IQ... when I deliberately induce a crash in a data field, and I do see a local crash log. So I wouldn't say that "IQ..." alone proves there was no crash.

  • in reply to flowstate

    What did you do in order to see them? Does it work for all the datafields you have installed? Maybe this is a FW bug then?

  • in reply to flocsy🤠
    flocsy🤠 said:
    What did you do in order to see them?

    Not sure but it might have had something to do with first going to a real activity (like Run), exiting the activity (for which the timer was never started), then going to the activity settings from the global settings menu. I think the real activity "session" might stay alive for some time after exiting the real activity. (Maybe something like how CIQ watch faces can access ActivityInfo in some cases?)

    EDIT: to be clear, at this point, the settings for *all* activities (from the global settings menu) appeared to have active CIQ data fields, not just the settings for the Run activity. Ofc I didn't test all of the activity profiles - just a handful - but the ones that I tried had active CIQ fields.

    Some time later (like 30 min), the activity settings data pages (from global settings) are back to the same "IQ..." state.

    But if I now go to the Run activity, exit the activity, and go to Settings > Activities & Apps > Run > Run Settings > Data Screens, the fields are still in the IQ... state.

    So I'm not sure exactly what's happening, and I don't really care too much to investigate it further.

    It's not like knowing (or guessing) how it works makes a difference. I'm as curious as the next person, but there's limits to that curiosity, especially when the payoff is low or nonexistent.

  • in reply to Brandon.ConnectIQ

    Can it be that it happens when I looke at the darafield? Meaning the screen was black and as I raised my hand the gesture turned the screen on. Of course it's hard to tell because it kind of tricks the brain. You suddenly see the IQ... but it's a bit like Schrodinger's cat: you don't know whether it still works or it already has "crashed" until you raise your hand and look...

  •   this still happens daily (even more than once in the same activity). Opened also this bug report:  firmware bug: CIQ datafields crash with IQ... .  

  • in reply to flocsy🤠

       I still get these crashes almost every day. I noticed one thing: sometimes it happens "as a consequence" of raising mi hand. It seems like the gesture is causing the crash. When this happens then as I raise my arm I can see for a split second that the screen goes from black to the datafield and then to IQ...

    This is interesting, because according to the Walk settings (and my understanding) the only thing that can cause the screen to go black on the fr965 is Power Save Timeout: Normal. Maybe this is causing the crash (or when it's waken up)

  • in reply to flocsy🤠

    The interesting thing here ia no one else is seeing/reporting this, which leads me to believe that something in your apps is involved.  I run multiple CIQ data fields all the time and have never seen this.

  • in reply to jim_m_58

    I'm not saying it didn't cross my mind. I think even in this thread I wrote about it. But I was able to reproduce it with other developer's datafields. However even then this would be clearly a firmware bug! If there's an app crash then give the developer a crash report in ERA! Except of course if "IQ!" means a bug in the app => show it in ERA, and "IQ..." means a bug in the firmware => send it to Garmin, and don't show it to the developer (kind of what maybe System Error should be?) But if that's the case, then this is a very nice feature, why would Garmin be so secretive about it?

    I would be the happiest developer if Garmin would do such differentiation and finally stop spamming us with bugs we can't fix. However I can see why others would want to at least know about the number of these happening to their users. Now we no nothing, as the only thing we know is that "IQ..." is not reported to ERA (we don't even know if Garmin does get a report or cares about it - well this we can maybe guess....)

  • in reply to flocsy🤠

    Do your DFs have a background service, and if so how are you trying to stop temporal events?  omStop isn't called in DFs.

    Are your DFs still on the Garmin when you try other dev's DFs meaning your DFs could still be running a background at that time.