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

Firmware 3.00 Update Problems

Tried to update through GCM on Samsung Galaxy S8, after tapping the available firmware update button, the running man appears but freezes instantly, and GCM crashes. Then I tried on a iPad Air 2, but there it says 2.30 is the latest. No update available.

GCM updated to the latest version on both devices.
  • Former Member
    0 Former Member over 7 years ago
    Right Power Phase is still screwed. See image attached , I managed to capture is since it happens pretty frequently.
    Hope Garmin provides a hot fix for this!
  • Same problem for me.
    The Garmin Mobile App crashes as sson as the little running man appears in the UPGRADE WINDOW.
    I tried on 3 different devices (2 Samsung Mobile Phones and a Samsung Galaxy Tab S).
  • Same problem with latest GCM on HTC U11 running Android 8.0
  • I just got my vector 3's yesterday. They have 2.30 on them. When I first tried to pair them on GCM, it showed that there was a firmware update available to 3.00 for about 5 seconds. Then it changed to your firmware is up-to-date with a reported v2.30. I have tried unpairing, repairing, hard reset of my phone, bluetooth on/off, Forerunner 935 on/off, FR935 unpair/pair and I cannot get it to push the 3.00 update or even show anything besides "your firmware is up to date" and v2.30.

    I'm not too concerned because of the reported issues with cycling dynamics and that I have no need of the power over bluetooth function. It is working fine for me with the v2.30 software but I figured if i'm having a problem, so is someone else.
  • Former Member
    0 Former Member over 7 years ago
    I just got my vector 3's yesterday. They have 2.30 on them. When I first tried to pair them on GCM, it showed that there was a firmware update available to 3.00 for about 5 seconds. Then it changed to your firmware is up-to-date with a reported v2.30. I have tried unpairing, repairing, hard reset of my phone, bluetooth on/off, Forerunner 935 on/off, FR935 unpair/pair and I cannot get it to push the 3.00 update or even show anything besides "your firmware is up to date" and v2.30.

    I'm not too concerned because of the reported issues with cycling dynamics and that I have no need of the power over bluetooth function. It is working fine for me with the v2.30 software but I figured if i'm having a problem, so is someone else.


    Update through your Edge if you have one or a Garmin Device. Garmin has not refined the phone apps hence the problems.
  • Update through your Edge if you have one or a Garmin Device. Garmin has not refined the phone apps hence the problems.


    Or just stick with 2.3 if you don't need BT. Wait until there are some bug fixes in a future update.
  • I don't have an Edge. I have a Forerunner 935 I use as a display head. It is not updating through the FR935 either.
  • I seem to be having the same problem as Kelmadics Rh Pedal keeps blanking out. Its also saying that the the L/H pedal phase is coming on 20 degrees earlier than before.

    I've previously had SRM's before this starting to be concerned about my purchase already.
  • Former Member
    0 Former Member over 7 years ago
    I've previously had SRM's before this starting to be concerned about my purchase already.


    Same here but I am crossing my fingers. It seems firmware release for this product takes months at a time.

  • Former Member
    0 Former Member over 7 years ago
    I finally updated the firmware today to 3.0, but I had to use my daughters Iphone 6 to do it, since it crashed GMC on my Samsung 8. TERRIBLE FIRMWARE UPDATE. The cadence on my pedals is now very erratic. I was doing steady state intervals at roughly 92 rpm and then suddenly my cadence would spike up to 127, then 80 then correct itself. It did this at least 20 times over an hour ride. Sometimes it would just spike 10 rpm, once it went to 167, then 70 then started to normalize. With a smart trainer in ERG mode, this is a real pain as it is trying to adjust because force (which was steady) x Cadence (which was not) = power. It takes it a bit to settle back down. Is there a way to go back to 2.3 firmware, because this is not acceptable.