Edge 1050 randomly reboots on firmware 32.20

Yesterday I was riding without navigation turned on, just a regular activity recording.

Maps are the standard ones, nothing third-party loaded.

The ride was long — moving time was 8:17:31, total time 15 hours 30 minutes — which is why the radar battery started running down.

Connected sensors were: cadence, HRM, and a Varia RTL515 (battery was low, then critical low). I had turned off the Varia's tail light to save battery, leaving only the radar function active.

The device rebooted twice, about 20-30 minutes apart, with no error messages at all — it just restarted. After the reboot, the tail light turned back on, and my activity was in a state as if I had pressed Finish but hadn't confirmed it yet — the screen had a red outline and a checkered flag icon.

This issue never happened on previous firmware versions.

If there's anything I can do to help investigate this, I'd be happy to.

  • Thanks for the post  . I'm not seeing any reported concerns quite like this, but we'd love to investigate.

    • Was a course being followed?
    • When the Edge powered off and then back on, did it go through the standard booting screen and then back to your activity? Or, did it just blank out then go right to the activity recap screen?
    • Have you experienced this when the Varia and other sensors are not connected?
  • hello

    1. No, without any course.

    2. Yes, standard booting — with the copyright screen, loading courses, etc., just like normal booting.

    3. No, this was my second ride after the update. The first one was just a couple of hours, the day before, and I didn’t notice any issues. Both rides had the same number of sensors, but the day before, the Varia was fully charged because I only rode for a couple of hours.

    Also, I wanted to mention that the reboot issue appeared during the last hour of my ride. I rode for 13–14 hours (±140 km) without any issues, and in the last hour the unit rebooted twice.

    BTW: I agree if you want to contact me via email 

  • I have exactly the same issue. Riding a planned route. The device restarted after about 160 km.
  • Same here, updated firmware just before starting my ride (rookie mistake!), and it started crashing very quickly (my rides were showing as going reverse, so tried to reverse them, but it would crash). Eventually, I took off and it crashed 2-3x after that, early in the ride, and got an "out of memory exception" at some point. The biggest issue is that, at some point, as it restarted, it ended up in a paused state so stopped recording, and I didn't realize, so I lost a couple of km of my ride before I pressed "record" again. Komoot tool was in there but not used at that point. Others non-garmin apps were Heart Rate Zone Chart, Power Zones Indicator. I have a zip with 3 RamDumps available if interested (about 60Mb), feel free to send me an email if interested.

  • Anche a me stesso problema ,stavo seguendo un corso , come faccio sempre,e il 1050 di e spento e riacceso fortunatamente senza perdere i dati , però io ho la versione 29.22 ho il Garmin da 6 mesi ,non ho mai aggiornato perché non ho mai avuto problemi, e invece ieri e successo

  • I have exactly the same problem. Bad it 3 times by now. Today was the 3rd one at about 220km if I remember correctly.

    It sent a dump report or something like this. So maybe you can check this if I give you the serial of my device or check it via my profile?

  • I’m afraid I have the same issue both yesterday and today 

  • Thanks for the reports and info, all. We may be reaching out over email to gather additional files/info if needed.

    In the meantime, we recommend following and bookmarking this thread, as we will post meaningful updates here as they become available. **

  • Maybe my story is of use. I never experienced crashes on my 1050, until yesterday. Last sunday I did a ride, with navigation, of a course I created a long time ago, about 50KM, no issues. Yesterday and today I did a little two day tour. I made two new routes, with Basecamp on MacOS as I always do. Uploaded both to Garmin Connect and sent them to the Edge. Yesterday I started the first leg, about 80Km so not that much. Within 10 minutes after starting I noticed that datafields that should be updating because I was moving, did not update. Before I could act, Edge crashed. I noticed a message in small white font on a black screen, saying something like 'uploading diagnostics'. Edge rebooted and nothing was lost, the ride continued as well as the navigation. Today I did the second leg which was about 70Km. Halfway I left the course to have lunch. Paused navigation & put the device stand by. After lunch pushed the power button to wake the device. Everything looked fine until I rsumed navigation - immediate crash, same uploading diagnostics notice, and after reboot completed I could proceed. The good news - I lost nothing. I could check if there are the 'diagnostics' files on the device, if only I knew where to look. But maybe, since the device said it uploaded, they are already with Garmin?