Edge 25 and Speed Sensor setup issues

I hope it's getting fixed soon! I bought the edge 25 this week, but with more than 5 km/h difference to the real speed, it's not a suitable bike computer for me...

Took them half a year or longer to admit fault and to just starting to fix it. Better return it than hoping it is going to be fixed any time soon.

Hope is a very dangerous commodity.

I don't trust Garmin at all now. Actually I always thought their software is shoddy.

But maybe I was blessed. After this edge 25 fiasco I've been directed to using my phone as GPS. What a great idea. Instead of having all these fancy connection which is unreliable why not use my galaxy s7 edge? way too powerful than any garmin can offer and it is just amazing what it can do as long as you are prepared to put your phone on the mount. Oh and it is like magic that it picks up the garmin sensors!

Garmin please provide an update on this speed sensor issue. This is a basic feature that most all Garmin devices perform and I can't believe its taking this long to correct. Were not asking for the computer to have some kind of crazy feature like live video feeds or google voice. ;)

seems like the 3.13 update wil fix most problems :)

Edge 25 software version 3.13 Beta
as of May 27, 2016

Download (563 KB)

View installation instructions

Notes:

We are looking to get feedback regarding the ability to remove sensors and connectivity to spd/cad. For any issues that you encounter please fill out the form included in the download and attach it to an email to [email][email protected][/email]. Please note that you may not get a response to the email unless we need more information on the issue you report.
In the process of troubleshooting reported issues we may access information in your Garmin Connect account, such as your activity files. More information about Garmin's privacy policies can be found at: http://www.garmin.com/en-US/legal/privacy-statement

Although this software is believed to be reliable, it has not yet been released for production and should be used at your own risk.
Change History
Changes made from version 3.00 to 3.13:

• Fixed an issue where Split/Lap times could post inaccurate data when the Split/Lap was triggered at extremely slow speeds
  
• Fixed a crash that could occur while navigating a course
  
• Fixed an issue with the save/discard page
  
• Fixed an issue where personal records were being set from discarded activities
  
• Will now favor speed from sensor over GPS
  
• Tightened proximity pairing for sensors and added prompt to accept/reject new sensor
  
• Fixed an issue which could the device to get caught in a loop of notifying the user that a speed/cadence sensor was connected
  
• Adds basic support for Bontrager headlight/taillight
  
• Adds tone to a sensor prompt
  
• Adds ability to remove sensor via the UI
  
• Device now tells a paired headlight to stay ON if Edge dies due to low battery
  

seems like the 3.13 update wil fix most problems :)

No kidding...

:D

Where did you see this?

Here http://www8.garmin.com/support/download_details.jsp?id=10471

Found it

http://www8.garmin.com/support/download_details.jsp?id=10471

Going to give this a go.

Just downloaded 3.13 and installed and I still can't get it to pick up the speed sensor. Anyone else have luck with it?

Just updated and got on the trainer and it worked with GPS set on.......I will try it in my next ride.

Fingers Crossed

Lets hope this update finally works. It has only taken 6 months to resolve and issue which all the other Garmins do flawlessly.

Oh an lets hope that they update the firmware with a 1 second sampling rate, I'd love to know why Garmin have chosen to compromise the device in this way.

There is no indication on the product packaging OR the quick start guide OR the product manual about sampling rates. I had to find out the hard way why my brand new edge 25 is showing a lot of discrepancy in the distance covered when compared with Strava on my smart phone. It shows 400 meters less for a 9 KM ride than my Strava app! When you pay 230 dollars for a device that is supposed to provide metrics *solely* based on GPS signals, it better do that job well! If the device did not have enough storage to hold data sampled at 1 or 2 second intervals, then I'm sorry, but the product is engineered wrong. If the target customer is an entry-level/ recreational rider, chances are that he already has an el-cheapo smart phone with Strava installed and competing for segments on rides, but wants something that can last for 6-8 hours without running out of juice. That demographic is going to be hugely disappointed that they spent all this money on a dedicated device which performs badly when compared to a 'generic' smart phone. I would have bought a Bryton rider 310 for half the cost or heck, just a set of power-banks for my smart phone.

Thanks itisravi - hope you don't mind but you have summed it up beautifully!

I still cannot believe it has taken 6 months to fix a problem that was the fundamental workings of the unit.