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

Strava Live Segments not synchronizing reliably or predictably on 830 (same as 1030)

Strava live segments (ie Training -> Strava Live Segments) are not syncing on the 830 in any predictable or reliable way when when starring/unstarring them on Strava website (not phone app). Using 3.57 firmware. Same behavior as 1030 always had. I missed a segment riding yesterday because it didn't synchronize to the 830. I've now spent hours plugging and unplugging 830 into PC a hundred times to try understanding.

1. Used PC Garmin Express as I can get more details and logs from it than GCM on phone. Latest GE 6.16.1.0

2. Starred four Strava segments, and immediately see them all visible in Segments widget in GC website

3. Of 4, maybe two actually load into 830 when syncing with GE.

4. When 830 connected to PC syncing puts a file in "NewFiles" folder named like "5bdf3f2a-157e-4576-80f0-2f1887d736b9.FIT" No way to tell from whether this will delete a segment or add. Unplugging 830 from PC to take effect.

5. When deleting segments, there is a message that appears on the Garmin briefly indicating "Deleting Segments". There is no message for adding segments. Please Garmin add message saying "Adding Segments". It will help us know what is going on.

6. If segment will be added/removed, it happens on the first synchronization from GE. After 1st time, synchronizing again does not bring it up.

7. Logs for GE are located on PC. Two styles of pertinent messages. Log file named "Express.log". Relevant log file lines indicate something about "segment_list.fit" which is sometimes uploaded to Garmin and sometimes not. Not sure why this file would be uploaded to Garmin

Majority of the time synchronization occurs this is the result:

    Line 8937: 2019-08-01 11:42:54.1691 |  20 | I | File to transfer segment_list.fit -> segment_list.fit (type FIT_TYPE_35)
    Line 8937: 2019-08-01 11:42:54.1691 |  20 | I | File to transfer segment_list.fit -> segment_list.fit (type FIT_TYPE_35)
    Line 9066: 2019-08-01 11:42:54.5163 |  20 | D | Not uploading file Garmin\Segment_List\segment_list.fit because it has not changed.

Sometimes however, it will display this result:

    Line 9417: 2019-08-01 11:44:11.0273 |  59 | I | File to transfer segment_list.fit -> segment_list.fit (type FIT_TYPE_35)
    Line 9417: 2019-08-01 11:44:11.0273 |  59 | I | File to transfer segment_list.fit -> segment_list.fit (type FIT_TYPE_35)
    Line 9557: 2019-08-01 11:44:11.3885 |  55 | I | Uploading C:\ProgramData\Garmin\CoreService\Devices\[#### a number maybe for my device]\Sync\FIT_TYPE_35\segment_list.fit to connectapi.garmin.com/.../upload
    Line 9572: 2019-08-01 11:44:11.4978 |  59 | I | The file[segment_list.fit] was processed successfully with code: 201.

8. Why uploaded to Garmin? What purpose?

9. Tried multiple permutations of starring and unstarring segments. Star a segment, wait a few minutes, sync, maybe or maybe not will get added to 830. Star 4 brand new segments never starred before, maybe 2 will get added to 830. Unstar an existing segment and star a new one, maybe unstarred one will get deleted from 830 but new one not added. No repeatable pattern I can discern on when it will work.

10. All is same behavior I experienced with 1030.

11. Could someone from Garmin could write an explanation of how this is all supposed to work, both with GE and with GCM? Supposed to wait 5 minutes? 30 minutes? after starring a segment in Strava before synchronizing? How does Garmin actually compare what is really on the device versus what is really on Strava? When syncing from GCM is it necessary to turn off Garmin and back on so it activate the files from NewFiles?

If this is fixed, the 830, for me, would be best Garmin I've had. Earlier Garmins were more reliable in syncing segments.


BTW, there is a BUG with synchronizing certain Strava segments (with Android GCM latest version) like this one: https://www.strava.com/segments/2874801  "Topanga/Mulholland to Nike Tower". If this is synced into "NewFiles" folder it created a subfolder "Topanga" and then stick FIT file inside at least for me. FIT file will not be processed since does not know about subfolders. Seems something is interpreting the slash in the segment name as a directory divider.