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

My experience with v3.40

After a short 44 mi. ride this morning here are my findings:

Grade % = completely useless. Garmin remedied the limit of 6 or 7% but now it is wildly erratic, inaccurate and never stabilizes. The numbers are all over the place. I made several stops after riding different gradients and took notes:

Flat (0%):

+5, -2, 0, +4, +3, -1, +2, 0, -4, +3, -2, 0, +1

3-4% grade:

-1, -3, +9, 0, -4, +5, -2, +7, -3, +6, +4, 0, -2

On a steeper climb, 10-11%:

After around 6-7% it was less erratic and made smaller fluctuations between 8% and 10% which is normal. I don"t know if it ever displayed 11% as I was dividing my attention. ;-)

It's just as bad on descents.

Incident Detection: Garmin has increased the sensitivity WAY too high! From 21-22mph I made a stop and lifted the bike six inches to maneuver around some road construction. The darned alert sounded! Good thing I was able to cancel it before it shot off messages. I have permanently disabled it.

BT Connection (phone): I'm one of the luckly ones who previously had no problems with my (older) phone, Galaxy S5, until today. It always connected right away but not today until about a half mile into the ride.

Autostart LiveTrack: Unable to test (see above)

Recovery time now displays at the end of a ride.

Recording to micro SD:
I haven't yet connected my 1030 via USB to actually verify this but today's ride listed in History has an asterick associated with it. I am assuming this identifies the file as being located on the SD card. That said, I did not get the usual "Ride uploaded" message at the end of the ride. Worse, I attempted to upload it directly from the device and received an "upload failed" message. Some minutes later, notifications appeared on my phone, both GC and Strava. Problem may be coincidental, or perhaps not.

I forgot to test the 3D mode on the map. Next time.


  • Updated mine this morning then went 40 miles. I have a different result than you did.

    My phone (Android) connected instantly and all sensors and phone stayed connected throughout the ride with no issues. I received 3 sms messages and they all alerted on the 1030.

    I did not test grade % and I dont use live track. I also did not put my SD card in before the ride.

    Did 2 segments and they performed as expected.

    The ride uploaded instantly after I ended it and then it auto sync'd to Strava.

    So far, after one ride, happy with the update. I'll test grade and SD card tomorrow.


    ​​
  • All sensors were connected throughout the ride, as usual, just this one time the phone did not instantaneously connect.

    Received SMS as usual.

    I rarely use LiveTrak but there are many who do and have reported problems with the Auto start function.

    Segments worked but I don 't normally use them.

    Gradient is a very big problem and it needs to be fixed ASAP. It worked fine on the 1000.

    And the ascent total is still reporting higher than actual.
  • Auto LiveTrack functions normally. And I think I know what an asterisk next to a recorded ride signifies: an incident detection alert occurred.
  • I do not know what previously was wrong with incident detection as luckily it never fired until now, 2 times in a single ride on a traffic light stop! this thing is now completely useless! how come there is nothing in the changelog around sensitivity change to incident detection or the new workout alerting??

    at least di2 is working as it should now, I wish there was a chainring change alert though (as was on edge 820).
  • Incident detection is now far too sensitive and useless. I have permanently disabled it.

    "Chainring Shift Next" notification has been working correctly since v3.20.
  • @md11pat: I was referring to an audible alert "Chainring Shift Next" - that still does not work
  • More than that. They removed the flashing bars in the gear graphics as well as the vertical bar underlining the active chainring under the numbers in gear combo..

    I wonder whose brilliant idea it was to foul up a perfectly functioning feature (1000)?! Really getting tiresome.
  • Installed 3.40, then found a strange bug. I go on the map screen, zoom out few times. At the fifth zoom-out the Edge crashes. I repeated the test multiple time, same behavior.
  • Which mode were you using for the map?
  • What maps do you have? I can zoom out to 500 miles, which is the max zoom level without issue.