Edge 130 Plus restart during course activity with custom course points

rus89
7 months ago

Hello,

as the title says, I have an issue with the Edge 130 Plus restarting during course activity on which I added custom course points (i.e Energy Gel).
This is very annoying since I'm using custom course points as a big helpers during my XCM races, and it's very important to me to work as expected.
It takes about 10-20s to restart, to connect all sensors again and waiting for me to press play again to continue where it stops.
This is very easy to reproduce.
Just make a custom course (or edit existing one) in Garmin Connect and add at least 1 custom course point.
Regarding notification settings, everything is set correctly as it is described here for the iOS, since this is my 3rd Garmin device for the last 10 years.
Regarding sensors that are attached to Edge are Garmin Rally XC100 powermeter pedals, speed sensor, and Garmin HR strap.

Has anyone else experienced this, or does anyone have any suggestions on how to resolve this issue?

Thanks in advance.

EDIT: Workaround is to use General Point type of custom points!!!
EDIT 2: I reached out to them over support, and they confirmed that the Edge 130 has been discontinued and won’t receive any further software updates. Unfortunately, this means the issue won’t be officially fixed.
  • 0 3 days ago

    I hav same problem on course points marked as a distance marker, so what's the solution?

  • 0 3 days ago in reply to 8981084

    I do not know I tried to delete the following ,enter the device folder and deleted ,activities,courses,new files,and the remote sw,then empty the trash on the computer ,eject the garmin from the computer and then disconnect,I allow the edge to boot back up ,but it still didn’t work ,so what are the garmin people doing when this function is the main gold of having a gps device ,cause the rest a can make it with my phone app Strava ,garmin people give us a solution please 

  • 0 2 days ago in reply to 4291694

    I don't think returning it for a replacement will make any difference. It seems to be a software issue. If you get another one it's likely to have the same problem until they release a software update with the fix.

    I reported the issue via the Garmin Support Centre and got a reply asking for more info to help diagnose/fix the problem. I was a bit slow responding but I have sent them some info. I recommend other people who have the same problem also report it via this route so that they are aware of how widespread the issue is and so you can provide extra info.

    Go here (https://support.garmin.com/en-US/?productID=698436&searchQuery=restart&tab=topics) and then click on "Contact Us for More Help". You can then send them a message.

  • 0 2 days ago in reply to DanDyer

    Thanks for sharing this info. It’s interesting to hear that they might not be fully aware of this issue, especially since there are so many complaints about it on this forum.

  • 0 14 hours ago in reply to DanDyer

    I reached out to them as suggested, and they confirmed that the Edge 130 has been discontinued and won’t receive any further software updates.
    Unfortunately, this means the issue won’t be officially fixed.
    For now, it looks like we’ll need to rely on workarounds to address the problem.
    It’s disappointing, but hopefully, the workarounds can help make things more manageable.

  • 0 13 hours ago in reply to rus89

    Espero que no sea verdad, porque si no Garmin se ha reído de todos nosotros y es para no volver a comprar nunca más un GPS Garmin. 

    El seguimiento de rutas siempre ha funcionado correctamente. 

    ¿el plan es “romper” los GPS con actualizaciones para que nos compremos unos nuevos?

  • 0 38 minutes ago in reply to rus89

    The Edge 130 has been discontinued a while ago, but they are still selling the Edge 130 Plus, which has different software. Did they suggest that the 130 Plus is discontinued? They haven't mentioned that in the couple of replies I got. They want me to confirm that the issue with roundabouts also happens on routes created with Garmin Connect and not just Komoot (I've already sent them a Komoot GPX and the report logs from my device). I probably won't be riding for a couple of weeks due to injury so won't get around to that for a while. If anyone else has the issue with non-Komoot routes it might be worth contacting them and mentioning it.