• State Verified Answer
  • Replies 13 replies
  • Subscribers 19 subscribers
  • Views 919 views
  • Users 0 members are here
Options
Related

How restart datafield after crash?

bunny.hu
6 months ago

Maybe a simple qustion, but how can I restart a Connect IQ datafield after crashed?

My only solution is restart the device, but maybe there is some better way.

  • +1 6 months ago

    Change the field to Timer (or any non-CIQ data field), then change it back to your CIQ data field.

    Notes:

    - the max allowed number of CIQ data fields in a single activity for most watches is 2 (for Fenix 8 series, the max is 4). This is relevant for the next 2 points

    - if a CIQ data field crashes at startup, the watch may automatically change it to Timer to prevent crashes every time you start an activity. In this case, due to a long-standing bug, the watch may lose track of how many CIQ data fields are actually added to the activity - e.g. if you have 2 CIQ fields in the activity, and 1 crashes, the watch may change the crashed field to Timer, but it may still think you have 2 CIQ fields and prevent you from selecting a 2nd one. The solution in this case is usually to change the remaining field to a non-CIQ field, at which the point the watch will realize you have 0 CIQ fields.

    - another related bug/quirk: if the watch thinks you have the max number of CIQ fields in an activity, when you try to change any of the existing CIQ fields to a different CIQ field, it will only allow you to select 1 of the 2 CIQ fields that are already in the activity, instead of showing all available CIQ fields as it should. The workaround here is again to change one of the CIQ fields to Timer - at this point, you will be able to change the field to any available CIQ field.

  • 0 6 months ago in reply to flowstate

    Thanks! So, in nutshell there is no good way only hacking :/ It is not clear, if the device can show the field crashed, why not provide a button to restart it.

  • 0 6 months ago in reply to bunny.hu

    What do you see in ERA or just in the ciq_log files?  The best thing is to fix the reason it crashed.

  • 0 6 months ago in reply to bunny.hu
    bunny.hu said:
    It is not clear, if the device can show the field crashed, why not provide a button to restart it.

    That's not a bad idea. A couple of educated guesses as to why not:

    - the UI on a watch is much simpler that that of a phone or computer, so it may not be so easy to implement what you want

    - Garmin would need to provide a way to restart a crashed field with the physical buttons, not just with touch (this would be pretty unintuitive)

    - Garmin may not wish to provide this functionality - they may wish to make it clear to the user that the app has crashed. (But then again, they also automatically change a data field that crashes on startup to the Timer field, which is the opposite kind of idea.)

    You could always make a feature request in the CIQ Bug Reports forum. Even if they don't implement it, they might explain the rationale for not doing so. And it might spark some discussion on their end.

  • 0 6 months ago in reply to bunny.hu

    + some if not all data fields would have hard time to collect, aggregate,  display, let alone record the correct data if they weren't started at the beginning of the activity. Even some data fields that had 100k+ downloads had a bug when the user saved it for "resume later" and then resumed.

  • 0 6 months ago in reply to flowstate

    That's an interesting theory. But I don't think it's true, because I've had the same 2 CIQ data fields for ages in my activity, when one disappeared and I was able to put them back (after all the hacks you mentioned). If the reason was the max number of fit fields / data and especially if it's a deliberate action from Garmin's part, then this should behave more consistently IMHO.

  • 0 6 months ago in reply to jim_m_58

    I found the bug with log files, that's clear, I just realized the problem that I cannot restart my app. My app using weather information and some real rare constellation make it crash, but 99 other do the job well. I found luckily the probleatic setting but what if I do not found all and the user found "oh crap the field crash, what can I do"?

  • 0 6 months ago in reply to flowstate

    Anyway I am using Edge computer and 3 CIQ field without problem. Where is this limit in the documentation?

  • 0 6 months ago in reply to bunny.hu
    bunny.hu said:
    My app using weather information and some real rare constellation make it crash

    Does it crash on line „Weather.getCurrentConditions“?

  • 0 6 months ago in reply to mcinner1

    No, that's working well, it is a bit more complicated. I cached the weather data for offline mode with different mode and one of Math got null sometimes that I belived not possible. Why you ask, there is your experience when that crashing?