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

New Edge 530 Public Beta 3.57 Now Available

A new Beta software for the Edge 530 has been released. Full change log, instructions, and software for installing the beta can be found here.

  • If you experience problems with this build, our engineering team would like to hear about your experience so they can work toward resolving any remaining issues. Please visit the Garmin forum for the Edge 530. Please note that you may not get a response to the forum post unless we need more information on the issue you report.
  • Although this software is believed to be reliable, it has not yet been released for production and should be used at your own risk.

Changes made from version 3.55 to 3.57:

  • Improved LiveTrack reliability.
  • Improved overall device stability.

Installation Instructions

  1. Connect your Edge 530 device to your computer using the micro-USB cable.
  2. Download and unzip Edge530_357Beta.zip and place the GUPDATE.gcd file in the \Garmin folder of your device's internal storage drive.
  3. Disconnect your device from the computer, approve the update on the Edge, and wait for the update to finish.
  4. If you would like to revert to the last public release software, follow the above steps but place the GUPDATE-350.GCD file in the \Garmin folder. Rename the file to GUPDATE.GCD before disconnecting your device.
    NOTE: If you revert to an older version of software, all of your settings will be reset to defaults.
  • First issue with 3.57. After saving my activity, I put the device to sleep. It took a while before I heard the usual beep. When I tried to power on the 530, nothing happened. It froze. I had to press and hold the button to unfreeze it, follow by pressing the power button to turn it on. I hadn’t experienced this in 3.55. 

  • Improved overall device stability

    What does this mean?

    I find it disappointing that software developers often default to generic terms like this rather than actually listing the bugs that are being addressed. When I see terms like that I read it as " Hopefully fixed some bugs that we don't want to publicly admit to having existed and don't want to list in case the fix doesn't work"

  • Yeah to all the returns - Strava live segments is not working at all so I say 530 is not fit for purpose. I'm going on holidays tomorrow and if the firmware is not perfect in 3 weeks I'm returning mine. This is rubbish Garmin...again :( 
    As soon as Wahoo get a radar you will not sell ANY Garmins. 

  • Are Strava segments really that important? I've never understood wanting to pay $ to chase a virtual PR. Just upload to Strava after the fact and go from there. That said, I seriously doubt Wahoo is going to overtake Garmin, ever. The Roam is too large and very overpriced, and the Bolt is 2 years old and pales in comparison to the 530 that's only $50 more. 

    I went Edge 510 > Bolt > 530, and the only two things I miss about the Bolt are the sharpness of the screen (black and white) and being able to use my phone to change settings. Otherwise the 530 is vastly superior in features and in the few weeks I've had mine, it's been pretty flawless with the 3.55 firmware, only a few minor quirks on the navigation re-routing, which even with the quirks is still way better than the maps on the Bolt. 

  • Yes live segments are a great training motivation tool when they are working properly and help me push myself to gain new goals. Some of the people I race against pay considerable $$$ for personal trainers I only pay $60 per year to Strava for live segments. 
    Seeing as you have bought three GPS' in the last couple of years you have spent HEAPS more money than I have.

  • Has there been any progress on Strava Live Segments? This can't be a difficult fix, my FR935 doesn't have the same problem (but it is difficult to look at while racing a segment).

  • I really hope they fix the 530 Strava live segments soon before I return mine, it seems much worse than my 520 at live segments and that wasn't good either. But reading this thread from a year ago I don't hold much hope that they will fix it sadly.
    https://forums.garmin.com/sports-fitness/cycling/f/edge-1030/143209/strava-live-segments-issues-comparative-times-are-not-accurate

  • Haven't spent much at all. Had the 510 for a number of years and discovered the Wahoo was missing a number of features that Garmin has built in. Sold the Bolt for not much less than I paid for it. 

    If segments is such a big deal for you, why not just temporarily create them with the Garmin segments until they get the kinks worked out? Seemed to work fine on my initial test. 

  • This update is just bad. 3.55 was working halfway ok with the phone occasionally disconnecting. First ride on 3.57 the device freezes after couple minutes, hard restart needed. At least it was able to resume the ride afterwards. Phone disconnects just as much as before. Mid-ride I get a message that it found the speed sensor?!?

  • Thanks for the idea, but it's easier for me to continue to use my 520, the main reason I bought a 530 is my battery life isn't good in the old 520 but I can use an external battery for long rides anyway.
    The more people that return their 530's for a refund the more likely Garmin are to fix their products.
    This thread shows the Edge 1030 has had the same issue unresolved for over a year so I'm not holding my breath on it ever being fixed for the 530 https://forums.garmin.com/sports-fitness/cycling/f/edge-1030/143209/strava-live-segments-issues-comparative-times-are-not-accurate