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

Edge 1050 mid ride reboot/Reboot needed for buttons to function

Since upgrading to the 1050 a month ago (prior user of 530, upgraded for bigger screen, but so far the bugs are pretty disappointing), I've had a couple of issues.

1. This has happened 3 times so far. I cannot use any of the physical buttons on the device aside from the power button for hard reboot. I start, and I can use the touch screen to navigate to profile and select course, but then I cannot hit the start button. I can use all of the touch screen capabilities as well as the controls I have mapped to my Di2, but the buttons the the device itself just do not respond. I have fixed this by long pressing the power button to force a reboot (which is the only button press it seems to recognize). This is kind of annoying, but since I essentially only use the button to start the ride, it is not a huge issue.

2. Last weekend the device just rebooted mid ride. It lost a bit of distance while it was rebooting (and invalidated the Strava segment I was on), but then after, I hit start and it resumed recording. However, for the rest of the ride, it did not show any radar alerts. I stated the radar was connected. I rebooted the radar (Garmin Varia) and it correctly notified me it disconnected during the reboot and then reconnected  once it powered back up. But it still did not show any radar alerts on the screen. After a few more hours, the Varia battery died, and it gave me first the low radar battery warning and the disconnected message, which indicates it was getting messaged from the radar and the radar was powered, but for some reason was not showing the radar detections on the screen.

The device is up to date and running the latest version of the software.

  • Welcome to the reboot party. Mine rebooted the last 3 rides after a week or two of "stability". The 13.x firmware 1050 is hands down the least stable firmware of the least stable Edge device I've ever owned.

  • Yeah, I am kind of frustrated as I don't use all of the advanced features on the 1050 and in many ways, it seems worse than the 530 I had. I do like the bigger, clearer screen, which is the reason I bought it (I'm getting older and don't want to have to use reading glasses to read the bike computer).
    Hopefully the issues get resolved with some more software updates, but the current version has been out for a couple of months, so it is not like this can be a new, random or unknown problem.
    If this were a $100 device, I wouldn't be as upset, but when a company charges a huge premium over everything else on the market, I think it is reasonable to have a much higher expectation for the quality level.

    As an update, I rebooted it again after the weekend ride to restore the radar functionality. But then I tried it again this morning, and the buttons would not work again. After another hard reboot, it functioned as expected. But at this point it seems 80-90% of the rides I go on, I have to manually reboot the device in order for it to function.

  • Coming from an 830, I was impressed by the screen at first, but the UI experience is much worse. On top of that, it's about a year old now -- and I swear it wasn't like this when new -- but riding in direct sunlight the screen is virtually unreadable. So for about 4-6 hours midday, the screen is terrible. I compared it side by side with my old 830 and the difference is shocking. I ride a lot, so the unit has ~15,000 miles and probably > 900 of screen on time.