A week ago I took my 1040 Solar (FW 17.29) on a 600km ride. I had a single GPX track that I imported and uploaded through connect (mobile). Selecting and loading the track worked good and quick enough. Overall navigation experience was good, battery performance was also okay'ish, but I expected more (I had to recharge to be able to reach the destination after 36h) There were a few things that went not so well.
rendering performance:
- sometimes the map view did not draw new content until only the lower quarter of the view showed something
- rotation of the map after a turn was very slow and delayed (seconds)
- switching to the list of upcoming climbs took 10 seconds and more. The previous screen was visible for that time until suddenly the list appeared. swipe gestures and Di2 commands were queued, so in the beginning i often pressed multiple times, just to "overshoot" after the list of climbs was finally calculated.
navigation and climb pro:
- after deviating from the route/course, it took minutes after returning to it, that the current position was matched to the route and navigation continued
- climb pro was often lagging, sometimes it showed that the climb was done when there was clearly still some 10s of (steep) meters left to the peak
- when approaching a climb and switching away from the climb pro page that "announces" the climb, I do not expect that it will switch back the climb pro page when the climb starts. This was very annoying combined with the long time to render the list of upcoming climbs.
- is there a rule to wich page to switch when a climb is done? it seems random, sometimes it is page 1, sometimes the page that was left when the climb started, sometimes just any page.
after the ride:
This was actually the biggest bummer. After stopping and saving the ride, the device started to sync and sync and sync and would never stop. I restarted device and phone - the usual drill. Nothing was synced or uploaded. I tried Garmin express on the Mac, which was at least showing an error message that the activity was corrupted and could not be synced.
I used mass-storage to get the fit file and upload it to Strava, which did not complain and just accepted the file, everything was there, all sensor data, etc
I was not able to sync new activities, until I deleted the long, "corrupted" one.
I had a lot of trust in all Garmin devices I ever used, also on the long Brevets. I never felt the urge to "double record" - I guess at least for the next one I will.
If this is useful for Garmin QA or engineering, I can provide the fit file, logs if the exist, etc. I can also send this to an support email address if needed.
Thanks,
Roland
