Edge 840 freezes during 7hr ride - after reboot Training Effect not saved

Jasperth
2 months ago

Just did a big training ride, using navigation with a course.
In the last 10 minutes I noticed the screen of my Garmin Edge 840 is stuck/frozen.
Buttons and touch screen do not respond.
After holding power button for about 10s it does a reboot and opens the current activity. No problem.

Then after I saved and synced, i noticed on my Garmin watch my training status is "Recovery".
Went in Garmin connect, sync/reload everything again. Still the same.
Just had a look on the web and turn out none of the data under 'Training Effect' is there. (Wtf?!)

Anything you can have a look at 
I can upload the files i you tell me what to upload.

Would be great to know:
1) why does the device freeze
2) why all data is there, except for the my Training Effect data
3) any way to recover the data

  • 0 2 months ago

    Exactly same happens from time to time on my Edge 1030+, and there were suggestions this is somehow connected with LiveTrack function which causes Edge to crash and restart. I don't even have to press power button, it restarts automativcally after short time. After restart the Edge is running the same activity, but paused, and I just resume with start nutton. All stats are there intact, except for Training Effect - it's lost and starts from zero.

    Suggestion - try disabling LiveTrack.

  • 0 2 months ago

    Awaiting your input 

    Also      what are your thoughts on this issue? Do you need me to send you any files? 

  • 0 2 months ago in reply to DennisF

    Thanks for the tip Dennis. I do not use LiveTrack however, all switched off already.

  • 0 2 months ago

    Unfortunately, I have noticed this phenomenon with Garmin products since the days of Fenix ​​5 and Edge 1030. If the device is restarted, the calculated score for Training Effect is close to 0.
    I haven't found any solution for this.
    The calculation seems to be somehow in a variable only in the volatile memory of the device and nothing stored, so that on restart it can return to where it was.

  • 0 1 month ago in reply to DennisF

    I had exactly the same but on an indoor ride where the E1030+ only had to detect/measure the speed, cadence and heart rate sensor, that was all. 

    The indoor trainer is a very old machine without any interfaces whatsoever with cycling devices/computers.

  • 0 1 month ago

    Training load, hydration/sweating, calories and probably some other minor stats are not stored during navigation into the fit file. 
    These stats are saved only when you save the activity after ending it. That's the cause of training load being 0 after restart. I had this issue with 820, 830 and 840.
    You can't recover the data, it's lost.

    About the freeze. Contact garmin support. They could look into your device logs. It could be Edge's bug, or some CIQ app, or smth else

  • 0 1 month ago

    I just did an 8 hour MTB race today and had the same issue. I'm really not looking for a solution to the freezing but just a solution to get my training effect! How can Garmin not provide a way to fix this?!?!? Zero training effect is really frustrating. 

  • 0 1 month ago in reply to bryantlikes

    it's a legacy code. I don't think it will get fixed anytime

  • 0 1 month ago in reply to Artem

    I agree. The SW and FW version management of Garmin is absolutely dreadful and way under any acceptable quality level in all their devices and apps.

    Even P1/Major* bugs remain in versions/branches they use time after time to do further development instead of simply discarding versions which have these P1/Major bugs in there.

    Garmin support also has never shown to take any useful action towards the SW/FW developers. The local Garmin support in the country where I live has no clue whatsoever so it is useless to contact them about these major SW issues.

    All in all very very frustrating indeed. 

    The only 'fix' I did was take a paid subscription on Training Peaks. They have their act together.

    *Official definition of a Major or P1 bug is that functionality is heavily damaged and cannot be fixed (by the user) via a work around