Weird Session Recording (discard not being honored and others)

This is on an F3.
I'm seeing sort of a weird(?) behaviour on an app I'm writing.

Weird #1
When I StopSession, i expect it to discard the session. But it seems like sometimes I honors it, most times it does not. I still see the session still being saved (from the watch's history page)

Shouldn't it NOT be in the history page?

Weird #2
sometimes, when i stop the app, and supposedly it will discard the session. When I immediately (or couple secs) go to a native app (RUN App for instance), it will show me a Save/Discard/Trackback etc view. The top will read something like 0:00 / _:__ km

I will go and do the "discard" and the watch will just hang there w/ the circling discard animation. (I have to Hard reboot the watch via the LIGHT/POWER Button)

Is there a native Save / Resume / Discard view that we can leverage whenever we stop a recording session?

BTW - for clarification (not entirely clear to me in the manual/API doc)
session.save == we stop and save the session
session.stop == we stop the session (not saving the fit file? or does it save it?)
session.discard == we stop and discard the session. (we do not need to explicitly do a session.stop(); session.discard();)





function StartSession(dc) {
var SS_Start = Sys.getTimer();
if ( session == null ) {
Sys.print("Session CREATE & START");
session = Record.createSession({:name=>"Running", :sport=>Record.SPORT_RUNNING, :subSport=>Record.SUB_SPORT_STREET});
session.start();
} else if( (session != null) && (session.isRecording() == false) ) {
Sys.print("Session RESTART");
session.start();
} else if( session != null && session.isRecording() ) {
Sys.print("Session STOP (PAUSE)");
session.stop();
}
var SS_End = Sys.getTimer();
var SS_Total = SS_End - SS_Start;
Sys.println(" StartSession Total Time: " + SS_Total);
Ui.requestUpdate();
}


function StopSession(dc) {
if( session != null && session.isRecording() ) {
Sys.println("Session STOP & SAVE");
// session.stop();
//session.save();
session.discard();
session = null;
Ui.requestUpdate();
}
}
  • I'd be happy to compare your code to that of another project that is known to work on the fenix3.

    Travis
  • I'd be happy to compare your code to that of another project that is known to work on the fenix3.

    Travis

    thanks Travis. Have sent the PM.
  • Former Member
    Former Member over 9 years ago
    I am also interested in seeing an app that does not trigger this behavior on the Fenix 3 because based on what I see in the product code, it is not possible to prevent the issue once you have started recording a session with ConnectIQ.

    (Except if you connect the device to USB before entering another activity profile it will reset the state.)
  • I tested the Golfscore app and seems to be fine.
    does it affect specific sport sessions? (like the strength training profile)
  • Former Member
    Former Member over 9 years ago
    I tested the golf score app (planetscooter's I assume) and it does trigger the bug on Fenix 3 if you use the recording feature.
  • I know the MOxyRun and MOxyCycle apps have been tested a bunch on the fenix3. I'm not sure if the problem exists there, but it may be a useful data point.
  • Brian - you are correct. The bug exists in the Golf_SC app (planetscooter's). I was mistaken.
    Travis - The bug also exists in your activity recorder app. (just managed to test it as you've just made it available for the F3)

    So, if I may be so bold to presume that you are going to compare my code against your activity recorder code, then both has the issue and will need Garmin to fix it.
    Unless the users can live w/ this bug and complain the heck out of it .... sob.. sob.. ZERO star reviews
  • Former Member
    Former Member over 9 years ago
    Yes, the issue is a device firmware bug, as best I can tell there is no workaround, so all apps that use Activity Recording on Fenix will experience it.

    Given that this wasn't noticed sooner, I suspect people are usually connecting to the charger between using ConnectIQ recording and native recording, which will reset the state that causes this issue.
  • i can confirm that this bug has been fixed in the 3.6 fw release for the F3.

    However I'm noticing the occasional freezing. (I'll start another thread on this)