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.


  • Auto LiveTrack did work for me, but I concur with the map crashing reports, using Garmin's OSM cycling map (US). Ironically, I was one who had not experienced Garmin's notorious BT/phone connection problems (as far back as the 510) until the 3.40 update. Now, my phone (Android) will only connect after at least 5-6 minutes of the device being powered on. Gradient remains erratic and inaccurate. Incident detection alerts go off when stopping at lights. Sensor connections seem stable (knock wood).
  • When creating a course from a previous activity on the edge, the course will have 2x duration time and half the average speed. This makes to course unusable for training against it (Virtual Partner).


    I was not able to reproduce this. Could post the activity file you used?
  • the problem with maps zoom out or similar crashing.

    as far as I notice is not happen with USA maps that came with unit, but In my case I do not live in USA, I try OSM for Colombia an Mexico an crash it.
    buy Garmin maps for Colombia (those are horrible for cycling) and also crash it.

    at my local store they think was my unit so the change it. the new came with v2.3 so I live it there, I DO NEED MAPS, I?m traveling to a new country for me so do not know any routs there.

    Hope Garmin fix it ASAP, having a GPS that crashes when using maps are.... well... just that....
  • Now, my phone (Android) will only connect after at least 5-6 minutes of the device being powered on

    What I noticed with my Android (Samsung S8) was that the GC app itself said it was connected (green dot on device, could sync and it said "connected") on the phone, but the BT on the 1030 itself was flashing (not connected) and sensors showed "searching....". Then after riding for 2-3 mins, I got a "Phone Connected" message and the 1030 icon was lit. Odd that the 1030 itself thought it was connected. Through the ride, I had one "Phone disconnected" and 60 secs later "Phone connected" message. Don't think I saw that happen in 3.2

    It actually took 2-3 mins to find my (Garmin) cadence/speed sensor too...but then it just connected.

    End of my ride though....summary screen was displayed (and yes, saw recovery time now !), then the unit just simply powered off on its own :( Thankfully everything was saved
  • Former Member
    0 Former Member over 7 years ago
    Yes I encountered the same problem, Crashes when panning the map. However during a ride navigation was OK no problem with the Map.
    I have to get rid of the big red banner warning when I was requested to make sharp turn....
    I do also have unreliable "Remote command" sensor, start normally then I have yo press the button twice to get a reply, then I see the Red led flashing... then back to normal.. fail again....I endup using my gloved finger....no big deal but irritating.
    Climb grade even "improved on 3.40" remain unusable...
    If the server would stop reseting the unit in English it would be nice... I said "server" because I experienced the same problem with the Edge 820 and the French Garmin support gets 10 call a day since the beginning of october.
  • For changing Frech to english:
    got to setting 1030 on garmin conect mobile. Change to franche.

    then do the same in your computer: go to garmin express and change to franch.

    it's funny that you have 3 places to chang your lenguaje. But it is.
  • What maps do you have? I can zoom out to 500 miles, which is the max zoom level without issue.


    OSM. Crashes if I zoom 5 times. Tested with Garmin Cycle map, does not crash.
  • Former Member
    0 Former Member over 7 years ago
    @md11pat: I was referring to an audible alert "Chainring Shift Next" - that still does not work


    Did you turn it on in the Di2 settings? Mine wasn?t working in 3.2, but works with 3.4.
  • Garmin cycle map continues to crash when zooming out from 5mi to 8mi. Tested with OSM disabled.
  • Did you turn it on in the Di2 settings? Mine wasn?t working in 3.2, but works with 3.4.


    Yes, I did, but I might try cycling it on/off again and perhaps a restart. Thank you.

    I'm assuming you are referring to enabling/disabling Di2 sensor, or something else?