• Replies 14 replies
  • Subscribers 20 subscribers
  • Views 834 views
  • Users 0 members are here
Options
Related

Can a not loaded IQ datafield crash a device?

mcinner1
2 months ago

I have a question for the developer community:
Is it conceivable that an Edge device crashes and the reason for this is an IQ data field that is not loaded at all?

A user of my data field MapFields claims:
His Edge 1040 crashed after several deviations from the route and the associated route recalculations. This is despite the fact that my data field is only installed in a different activity profile and has not been loaded in the profile currently in use. If he uninstalls my data field, the route recalculation works without any problems.
The Garmin support he contacted does not rule out his theory.

The data field does not provide any ERAs and I do not receive any complaints from other users.

I would really like to know if any of you have already encountered such a problem: an installed but not loaded IQ data field crashes a device?

  • 2 months ago in reply to flocsy🤠

    Ok, then I guess the general problem that was mentioned (data field foreground process runs when it shouldn't) isn't due to some weird bug with a background process.

  • 2 months ago

    I am the "affected person" that   mentioned. As has already been mentioned here, there was no crash (neither data field A or B, nor the device was affected). Both data fields are defined in an activity profile, which was not actively used during the test.
    The following error occurred during route navigation:
    Turn-on instructions were displayed for too long, so the following turn-on instructions were not displayed. If the route deviated, the recalculation process took a very long time and in most cases gave nonsensical results.
    On the recommendation of Garmin support, I deleted both CIQ data fields and carried out a new test, during which this error no longer occurred.


    Yesterday I reinstalled and set up the CIQ data fields in an activity profile. I will carry out another test with this profile today. I will publish the results here.

  • 2 months ago

    "@all"

    I carried out the announced test today.
    1. Started a route navigation with the activity profile in which the data fields A and B are defined = no problems
    2. Halfway through the trip, switched to an activity profile in which these data fields are not included = no problems
    Although the German Garmin support is of the opposite opinion, I now assume that the described problem was fixed by firmware 26.18, which was rolled out under the announcement "Connect IQ bug fixes and improvements" on March 4, 2025.


    Btw: The previous tests in which the problem occurred ran for three days with firmware 26.17 on February 24, 25 and 26, 2025

  • 2 months ago in reply to peggatsch

    Good to hear!
    Hopefully it stays that way.