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

Some new bugs

Today I was riding and encountered a couple of new bugs.

1) Device decided I was on a segment that I wasn't on, and then would not stop alerting me that I was off-segment. To be clear, I was never on the segment so I definitely dont care that I'm off of it. The alerts are so annoying. Two issues here: 1) why did it behave this way. 2) We really need a discrete toggle to disable off segment alerts. I see them often. I dont care if I am off-segment.

2) I was experiencing significant issues with the device responding to touch. Being unresponsive to touch, scrolling erratically, and sometimes registering a touch/click that didnt happen because my hand wasnt even near the screen. I saw this on my last ride too, but it wasnt as significant as what I saw today.

3) My "smart" light (a bontrager Ion rt200) started showing a low battery alert. It was impossible to dismiss this notification that covered half the screen for the remainder of my ride. I tried everything short of stopping my activity and power cycling. I could still use the Di2 buttons to change the screen in the background (behind the alert in the foreground) but it was impossible to dismiss the alert. Neither the onscreen button or the physical button on the side of the 840 did anything.

4) Today I set the Varia radar alert to show only on the right side. It still shows on both sides.

5) Following my ride it took repeated attempts to power off the device. The on-screen button just wouldnt respond initially. After a number of attempts it worked.

6) This probably isnt a bug per se, but it would be nice to be able to set priority for climbpro and live segments. With both enabled, when climbpro kicks in it supersedes the live segment screen. I would prefer the opposite. Show me climbpro unless I'm on a segment in which case I only want to see the segment screen. Again, this probably isn't a bug, but changing the prioritization would be a nice-to-have. For now I've disabled climbpro to get it out of the way.

0 Dew4rd over 2 years ago

I had #2 happen on my previous ride too. I had 4 data screens + navigation + a strava segment. It was behaving like a 10 year old device where it couldn't seem to handle everything and became very unresponsive.

0 Wongataa over 2 years ago

Make sure you report any bugs you find the correct way by contacting Garmin support. Hopefully then they will look at fixing them.

0 thetomfox over 2 years ago in reply to Wongataa

Garmin don't even seem to respond to bug reports. I experienced a couple more new and serious errors today. If these arent resolved fast this thing will have to be returned. Unfortunately, it seems pretty unreliable.

0 WStuder over 1 year ago

#1 happened today. Wasn't even on the segment as I turned onto a different road. It made my Edge 840 mad and I could not dismiss the "Stop current segment" notification, even though I could still toggle through my screens. I finally just saved the ride to hope to get rid of the annoying notification, but even as I stop and saves ride, that damn notification would not go away until I restarted the device. I never had this problem with my edge 1030. I debated upgrading to the 840, but likes the longer battery life. Wishing I wouldn't have changed.

0 5735449 over 1 year ago

What did you end up doing? Did things get better, or did you return? I've had #1 *many* times now, along with some other fun ones, like nonstop "Radar disconnected" tones/popups starting partway through a mountain bike ride and never going away (popping back up as soon as dismissed), when my radar was specifically disabled in sensor settings and was never connected that day. Also why wouldn't it start right away?

Also getting really wacky climb notifications - I can't tell if they're from ClimbPro or Segments, though - it's a two-field pop up on the bottom with "Segment 0mi" and "Climb 26688mi" - Yes, 26 **thousand** miles. My longest starred segment is 4 miles. The rest are under 1.3 or so.

And once I go anywhere near a segment it really seems to latch on to it - I ride a lot in some trail systems here that have trails that go kind of parallel to each other, so of course every once in a while I might get within 500ft or whatever triggers the initial alert for the upcoming Segment (even if it's a mile or 2 of riding before you'd actually get to that point, unless you cut through the woods randomly) - but no buttons and no amount of dismissing it makes it chill out - I just have to keep riding with it constantly alerting me that I'm riding away from the segment. I KNOW! Ugh. I like Segments when I'm actually riding one and it's working properly so I don't want to turn it off. And I don't want to disable tones because I never want them off for the radar (again, when working) for my road rides, and also want them on for turn prompts.

0 aweatherall over 1 year ago in reply to 5735449

This is addressed in the public beta 18.15 build

0 5735449 over 1 year ago in reply to aweatherall

Which part? All I saw in the beta release notes that might be applicable is "Improved climb and segment interaction." But that's pretty scarce on details and may or may not apply to what I'm seeing.

0 aweatherall over 1 year ago in reply to 5735449

The wacky climb notification

0 5735449 over 1 year ago in reply to aweatherall

Ah, great, thanks Any idea if the over-eager segment popups are part of that, too? I have a race tomorrow so I don't want to mess with anything now, but maybe I'll give the beta a shot on Monday to see if it fixes what I'm seeing - would like to get this ironed out (or at least acknowledgment or a "we're working on it") before the return period's up.