Acknowledged
CIQQA-4750

Venu 4 (18.30) resets while a watch app saves an ActivityRecording session

Device: Venu 4, system software 18.30
App type: device app (watch-app) using Toybox.ActivityRecording
SDK: 9.1.0 (app version 1.05 or 1.06 at the time; both built with 9.1.0)

What happens

A user ended a run and the whole watch reset. It went through a full restart, not the Connect IQ "IQ!" crash screen. This happened while our app was saving the session. After the restart the activity was not on the watch and never reached Garmin Connect.

What the app was doing

The run was ended from the paired phone. The phone sends a stop message, and the app then runs:

session.stop();
session.save();

Heart-rate data was flowing normally up to the stop. The watch dropped its connection to the phone about 4 seconds after the stop, and reconnected about 55 seconds later after the restart.

Frequency

Across the 30 runs recorded with our app on a Garmin since September 16, this is the only time the watch dropped off right after the end of a run. The same watch saved three earlier runs (5, 24 and 62 minutes), ended the same way, without a problem. It has happened once on this Venu 4. We have no reliable repro yet.

What we're adding

Our latest build (1.07, live now) records a breadcrumb just before save() and reports it on the next launch, along with the firmware version. We'll update this thread if more resets show up on Venu 4 or other devices.

Questions

1. Is there a known reset on Venu 4 18.x during Session.save(), or after stop() when a phone message triggered it?
2. Is there a device error log the user can send that would help you here?

Eric Chan

  • Same watch and software here, reported as CIQQA-4757. If you pull /Garmin/Debug/err_log from your Venu 4 after a reset, you could compare it with ours: RTL Trap 0x028, programCounter 0x60f9c547, stackPointer 0x20064be0. In my tests the restart happens mid-session and follows reading heart rate through the Connect IQ Sensor API, with no stop or save involved. You mention heart-rate data was flowing up to the stop, so it may be worth checking. A 40 line app that only reads heart rate restarted my watch twice; the source is in my reply on CIQQA-4757.

  • First off, answers to your questions:

    1. No.
    2. Yes, the /Garmin/Debug folder contains device error logs, which our product teams may be able to use to determine the root cause of the crash.

    Since this was a one-time thing and is really more of an exploratory question, this kind of thing would be better posted on the developer discussion forums to find out whether anyone else has experienced a similar issue. For us to investigate this, we would at least need the product error logs and the app used when this problem was seen.