VivoActive 3.30 update causing device crash when running ActiveMeter for 42 minutes

Former Member
Former Member
Hi there,

I have a very consistent issue regarding an app I wrote called ActiveMeter running on my Garmin VivoActive ever since 3.30 update. I haven't done any work on the app since the last release (Oct 26). I have been testing the app a lot, the weekend before 3.30 update (ie. 1-Nov) I ran the app over a 4.5 hour ride without any issues for example. But ever since the update was released the watch will crash after 42 minutes, reset, and then the running app will appear to try and resume the activity.

I have been running the app compiled in CIQ 1.1.4, 1.2.0 and 1.2.1 with the same issue. I have factory reset the watch and cleared off all other applications (though it seems like the running app hangs around like a bad smell). Since this behaviour only occurred after the recent 3.30 update I can assume the issue is related to the update. My app uses the activity recording, GPS, and sensor profiles.

I would really like my app to run in 3.30. Where to start in getting help regarding the issue? It does not seem like there is an issue tracker or anything with Garmin.

Hope someone can help

Thanks
Joel
  • Thanks for the report. We'll see what's happening and get the issue fixed.

    I would really like my app to run in 3.30. Where to start in getting help regarding the issue? It does not seem like there is an issue tracker or anything with Garmin.


    The best way to report issues is to post to the forums like you did. We take reports like this and put them in our internal issue tracker. Unfortunately our issue tracker is for internal use only, but we'll report back to this thread once we have it fixed. If you don't get a response from us in a few days, feel free to bump the thread or send an email to [email][email protected][/email].
  • Hi Joel,

    Sorry for the delay on this. I'm attempting to reproduce this, but haven't been able to so far. Do you have any crash logs from your device that you can provide? For example, you may find an ERR_LOG.txt in /Garmin or a CIQ_LOG.txt in /Garmin/APPS/LOGS.

    Thanks!
  • Former Member
    Former Member over 9 years ago
    Found the issue... II think

    Hi there,

    Thanks for your offer to look into the logs, sorry I didn't reply but I figured if the issue was not reproducible then maybe it was my device. At any rate I have found out what was doing it.

    Say you have the code:

    [FONT=Courier New]var _timer_interval = 1 * 1000;
    var _timer = new Timer.Timer();

    _timer.start(method(: onTimer), _timer_interval, true);

    function onTimer (info) {
    ...
    }[/FONT]

    After a while it seems that the timers will run out and the app will crash. Lowering the interval for example made the time before the app crashed lower.

    Changing the code to as follows seemed to make the app run much longer (the longest I have tested in real life conditions so far is 2.5 hours)

    [FONT=Courier New]var _timer_interval = 1 * 1000;
    var _timer = new Timer.Timer();

    _timer.start(method(: onTimer), _timer_interval, false);

    function onTimer (info) {
    ...
    _timer.start(method(: onTimer), _timer_interval, false);
    }
    [/FONT]

    This is probably a better way to go in general because at least if a routine is taking a long time to perform, the delay is added at the end so that at least there is a proper break before the routine is done again. The app is pretty heavy - it draws with math instead of symbols, uses all the sensors and includes the custom power library for the vivoactive as well, so I guess it was pushing the system a bit hard.

    Anyway, thought I'd get back to you, thanks
    Joel