BUT BEFORE YOU INSTALL THIS UPGRADE, remove all the *.fit files from your Edge (you can store them on the computer) including the activities folder AND the courses folder (which I forgot about).
Some people upgrading with *.fit files left in the memory are experiencing issues ranging from inability to upload, to completely bricking the unit.
That said, now that mine is back working, it does seem to be faster on the upload. And my strange "have to push the start button several times to get it to work" issue is gone. Which I was thinking was a physical problem with my unit, but apparently not.
There's also apparently a bunch of powermeter enhancements that I'm sure I'd find awesome if I had a powermeter.
I appreciate your words of caution. I followed your advice, and deleted the files before doing the upgrade. Everything went smoothly and I am now running 3.0. Thanks!
Has anyone noticed that now with the unit on it reads a mph all the time even when not moving? Mine will read anywhere from .5mph to 1.5mph. My brother is having the same issue after updating his firmware to the 3.0
I'm getting weird heart rate reading since the new firmware upgrade. A lot of times it's 220 - 230 for the first 15 minutes of riding or so, later on it's about 90 most of the time. In between heart rate seams to be ok as before,145 - 160.
The high reading at the beginning is a known problem with ANT+ HRMs since before the update, might just be showing up for you now.
Make sure that a jersey zipper is not flapping against the transmitter. Failing that, try pre-wetting the fabric that is against the HRM before a ride.
The low reading at the end of the ride has me stumped.
I will assume you were referring to me on this one so I will answer the question. I had not checked but just did and it is on the same setting it was before the firmware update. I have it on "When Stopped".
I had the same issue when standing still with my 800. Garmin wasn't much help, all they said was it was normal and due to their GPS chips being very sensitive. The guy said the one he had sitting on his desk did the same thing. Even after I told him previous firmware versions didn't do it and having the GPS show I traveled 189 feet in the four minutes we were on the phone wasn't right, he was a good corporate drone and said nothing was wrong. Whatever. Sounds like bad software/filtering to me.
Anyway, the solution for me was to downgrade the firmware since I didn't need any of the added features.
Okay, mine was indeed doing this on a stop during a ride yesterday when I had no wheel sensor set up. The GPS chip hasn't changed, so it's just now displaying a non-zero number due to GPS drift (which all units experience) whereas previously it would be displaying a zero for the same amount of drift.
I can't see this resulting in any measurable error over the course of a ride. And I think a wheel sensor will solve the issue if it really bothers anyone.
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Related Threads
?
?
?
?
?
Mountain Bike Reviews Forum
15.4M posts
515.2K members
Since 1990
A forum community dedicated to Mountain Bike owners and enthusiasts. Come join the discussion about bike parts, components, deals, performance, modifications, classifieds, trails, troubleshooting, maintenance, and more!