REPOST: Re-start activity after crashing

Bump.

Hi wes-m apologies for the delay.

The blue arrow you are describing is the "prompted" Timer Start Mode setting. The Edge is receiving speed data and knows that you are moving, but the timer has not been started/re-started and the arrow is the start button symbol. You can adjust this setting following the steps here: Starting the Timer Automatically

If the device is powered off or reboots during an activity, you will need to press the start button to resume activity recording.

Hi Clayton,

Thanks for the response. I've owned 5 generations of Edges, so I know what the beep is for and how to change it... But it used to ONLY beep if you were on the "activity" screens. If you went back to the home screen, no beeps. Now it beeps all the time no matter what. Want to turn on your device in a moving vehicle? beep beep... beep beep... beep beep... beep beep... *friend yells TURN THAT THING OFF*. I just turned off the start prompt, it was too annoying.

Regarding restarting the ride. This is a simple quality-of-life improvement you guys could make. Previous units had a boot-up chime, so if the unit crashed and rebooted, you would usually hear it. Now that you have a real "speaker", I'm guessing that the bootloader isn't capable of beeping. Think about this from a user experience POV. When an activity is in progress, the user intent is to record the activity. When the device crashes, it should remember that the intent is still to record the activity, not wait for the user to confirm it again. And the "beep beep" start your ride reminder doesn't work if an activity is in progress but stopped

In industrial control systems, if the HMI restarts, it generally doesn't reset the process - it reattaches and continues where you left off. Imagine if that happened with a nuclear reactor. The edge obviously isn't a nuclear reactor, but it doesn't hurt to learn the lessons. Maybe the design team should get a copy of The High Performance HMI Handbook.

It's a shame you guys don't appear to have a real "user feedback team" that interfaces directly with the product design team. There are many loyal Garmin users who would gladly volunteer to participate. They just want to make their Garmin better. I could put together dozens of slides of UI regressions -- not just "changes", regressions -- since the 830, but it would be as productive as kicking rocks. Some examples.

1. On my beloved 810 (the 830 is on loan), pressing STOP immediately brings up the save/discard screen, so you can do exactly what you requested -- save or discard. On the 1050, there is an inexplicable ~5 second delay, where the activity is stopped but you can't save or discard it. Wth? You can tap the little red flag and go directly to it, but why? A tap tax.

2. The segment screen. This thing is an absolute mess. Below the map are two icon things, with tiny numbers and arrows -- arrows that do nothing but sure look like they are the old "choose goal" arrows. Below that is another box of equally small and difficult to read numbers that can't be changed or removed, and probably duplicate other numbers in the data fields. Gone is the "x" that can be used to cancel the segment in two quick taps --- "x" + confirm. Now you have to pay the Tap Tax - tap, choose cancel, confirm, and now tap AGAIN to get off the overlay screen. Twice as many taps, twice as long fiddling with the unit and your eyes not on the road.

3. Segment and Climbpro popups. These will pop up no matter what. If you're six screens deep into the setup, prepare to be kicked out to a segment or climb. I've even had Climbpro pop up on top of a segment. Wth?

4. Navigation arrows. Most of them are at the top of the screen. These seems pretty natural when you're holding the unit in your hand, right? But what's wrong is that 99% of the time the unit is on the bike, not in your hand. Tapping at the top of the screen with your index finger makes your hand cover the screen. I've even had the backlight cycle bright/low when my finger briefly covered the light sensor.

5. Bezels and buttons. My beloved 810 (I love it so much, it was peak Garmin) has buttons on the top, and they are always very accessible. The 1050 buttons are down out of sight, for aesthetics I guess. But with the mount point shifted up, the buttons are super close to the handlebars on many bikes with out-front flush style mounts. One of mine doesn't fully clear the bars as it turns if it has a protective case. This makes it very difficult to press them. The unit has big bezels, which I don't personally care about, so why not make good use of them and put buttons (perhaps capacitative) there?

6. Backlight weirdness. Sometimes the backlight is weird, and the unit will be almost unreadable in direct sunlight. Not sure if rebooting helps, but putting the backlight at maximum in manual helps a little. I'm a little worried it's because the unit has almost 1000 hours on it and the light source is dimming.

7. Lots of little things. CIQ widgets are neutered. On the 830, if you went to the segment list and found the one you just completed, it would tell you your time and speed. Gone on the 1050. That made me sad. When you long press a screen, the icons at the bottom make it a pain to change those fields, especially with gloves on.

Not every thing is bad, though. Some great improvements:

1. Garmin Pay. If you don't care about all the little things I do, this alone is enough reason to upgrade, if you're on an old unit.

2. Last course added on the home screen. Top idea. Give that person a donut.

3. Battery Saver -- I've personally ridden for almost 3 hours after being notified the battery was at 4%. I probably could have gone longer. Never tried it on other units, but it does live up to its name.

4. Navigation on your phone. It doesn't always work, but it's very nice when it does.

Another silent reboot yesterday, after updating to 3.14

Three silent reboots on 3.13 in the prior two weeks.

I personally never found my previous devices to be what I would call "unstable", but the 1050 crashes far more often than my 830, and we're over a year since release.

Fixing bugs is hard. Auto-resuming the activity is easy (easier).