Related

FR165 music goes into standbye during run

8822947
1 month ago

I did a run with navigation and music (Spotify) and every 5 minutes,  the watch tries to go to standbye (it warns 30 seconds before). I didn't get to wake it up during these 30s and all data was lost which is unacceptable.

I know I can adjust the standbye time from 5 to 25 minutes but the question is why does the watch even try to go into standbye?

The manual says "after X minutes of inactivity" but clearly there is no inactivity as I'm navigating, tracking my run and listening to music.

(During the run there is no connection to Garmin Connect and the battery was full.)

  • 0 30 days ago

    Sorry if this is a dumb question, but did you start the activity timer by pressing the START button (the top right button)? If so, did you stop the activity (using the START button) and not restart it (again using START)?

    If you leave the activity "not started" or stopped for a period of time, that's what the manual refers to as "inactivity", for the purpose of the power save timeout (which is either 5 minutes or 25 minutes).

    e.g. assuming the power save timeout is set to the default of 5 minutes

    - If I open the run activity, but don't start it, after 5 minutes the watch will automatically discard the activity (because it was never started, and nothing was recorded in the first place)

    - If I open the run activity, start it, stop it, and leave it stopped for 5 minutes, the watch will automatically save the activity. (You can tell that the activity is in the stopped state by the red ring that appears around edge of the screen.)

    In any case, I can tell that activity is stopped (or never started) by checking the Timer data field to see if it's changing: if it's constantly updating then the activity is not stopped; if it's frozen at 0:00, then the activity never started; if it's frozen at something other than 0:00, then the activity is stopped.

    If the watch is actually detecting "inactivity" while the activity timer is running, then that would be a bug that should probably be reported to Garmin,

  • 0 25 days ago in reply to FlowState

    Hey, thanks for the reply,
    it seems to me that it really was a bug because I was during a normal run and occasionally checking the pace and time, which was displayed. I get that it could have detected inactivity in the stopped menu but then I would have returned to the "save, continue, etc." page when I first dismissed the 30s inactivity timer (I was able to stop it the first time it tried to go to sleep, only the second time I didnt realise and lost the data) but I got to the normal running/navigation screen.

    I have since done a software update and maybe should try it out again, as I only did runs without navigation.