This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

A weird "Transfer Completed" message everytime before start workout

Former Member
Former Member
Do any of you guys saw a weird message "Transfer Completed" right after you click on the run button?

I am sure my watch is not connected to the phone or what so ever.
  • Yes, I am wondering what that is all about too ... transfer to what/where? I see it all the time too and I am definitely not connected to my phone.

    Max
  • Do any of you guys saw a weird message "Transfer Completed" right after you click on the run button?
    Often.
  • I'll also see this toast while recording an activity if I get out of BT range, and then come back in range. It doesn't seem to cause any problem though.
  • Yeah, same here. Been seeing it for a while.
  • Former Member
    0 Former Member over 8 years ago
    My assumption is that the watch is routinely syncing the other watch data--steps, RHR, VOMax, etc. and the toast is confirmation of that. It might be particularly relevant in activity mode, since it might need to make sure to sync prior to any activity in case of a long run that results in potentially overwriting other information.
  • Former Member
    0 Former Member over 8 years ago
    The transfer complete message comes up after your previous activity upload I'm guessing to let you know that it was done successfully. It'll only come up once after an upload.
  • My assumption is that the watch is routinely syncing the other watch data--steps, RHR, VOMax, etc. and the toast is confirmation of that.
    Quite possibly, although just now I manually triggered a sync (with Garmin Connect Mobile running on my iPad), waited for it to complete (with the sync progress panel in the app at the bottom turning green, and then disappearing) and then thirty seconds more, then pressed at the watch face and – Presto! – the Transfer Complete ‘toast’ notification popped up immediately until getting into prepping for a Run. It makes me wonder whether the previous sync set a flag/bit on the watch upon completion, that doesn't get checked or actioned until the next time a screen in which toast notifications can be presented is brought up.
  • Former Member
    0 Former Member over 8 years ago
    it is simplier than you think: it is only one (of the thounsand) littel bug of 235 :mad:
    Thw warning (transfer completed) cames on the next action you take on tha watch and not at the end of the transfer.
    If you try to set up BT as example and make a sync, then set bt off (or not) and after a while start an activity the warning appears...

    poor memory on the watch or bad software engineering :rolleyes:
  • Apparently this is intended behaviour, so I've been told.

    Transfers occur while in Low Power Mode (background syncs to Garmin Connect Mobile) however the TRANSFER COMPLETE banner is suppressed since the watch is in LPM. The banner gets pushed upon exiting LPM informing the user that a transfer was completed during LPM.

    This behaviour is to maximize battery performance.

    HTH

    CW
  • Apparently this is intended behaviour, so I've been told.


    The fact that it only shows the toast when not in the FW's LPM is intended... The fact that it forgets that it displayed it and displays it again when every you leave the FW's LPM (or regain the BT connection) is probably not....

    It already did the toast, and shouldn't continue to do it each time you leave the FW's LPM. :)

    Other watches I use may display the toast regardless of being in the FW's LPM (the va and va-hr for example), but in all cases, only show it once, and not on-going. This is a bug....

    These watches only sync when they need to. With steps, there is a time or number of steps component (it always tries to sync soon after midnight, and IIRC, try to sync every 1000 steps. And this syncing doesn't result in a "Transfer Complete" toast at any time.

    "Transfer Complete" is the result of sending a saved recorded activity, as it wasn't a sync, but transferred one or more .fit files. (that "auto upload" thing in settings :) )

    It's a good thing the toast is annoying but causes no harm... The kid in the back seat that keeps asking "Are we there yet?" :)