Fenix 5X - 2.96 Beta Release

RecHR is calculated when you STOP the log and before you save it.
What you see is NOT the rest data page but the timing of the log and the option to save-discard.

What I'm saying happens with ALL activity types but it never happened with Pool Swimming. Now... I have logs with and logs without the recHR and I don't understand why because that vibration and popup never shows up (in pool swimming).

I'm gonna hook the HRM Swim now and do a mock log and see if I can get it displayed. I think this has to do with the software.

Same thing here, no recovery time for pool swimming with HRM-Swim paired...

Round trip for walking activity

Why it isn't possible to have round trip for walking activity?

What the program does is to take the HR drop from the moment you press stop and record it into the log the moment you press SAVE.
I think this means we've got to get the chest and watch out of the water THEN press stop and wait. This is not something that can be done with a delayed transfer because, apparently, Garmin hasn't implemented it yet in the delayed mode. That would explain why some of my logs have the recovery hr and why others haven't.

Gonna try on monday... please do the same. Stop -> get chest and watch out of the water, wait 2 minutes and see what happens. My guess is you won't get the notification on the watch but the parameter will be on the log.

Till now i always save HR data before saving swim workout, i have never used "download later" hr data neither on my previous fenix 3...

Bugs with Strava Live Segments

Hey all!

I'm experiencing several bugs with Strava Live Segments and the 2.96 beta and would like to know if others are having them too. Here's a description of the bugs from a mail I just sent to the beta team:

Unfortunately there are still several bugs that make the Strava Segments more or less unusable for me on the Fenix 5X:

1) The “Distance Remaining” data field doesn’t change when you are behind your PR (see attached) picture. It stays on the same value while “Time Behind” and “Segment Pace” at least show changes.
When I switch to another screen, pause or press the lap button (Autolap does the same) the “Distance Remaining” jumps to what seems to be the correct value but immediately gets stuck on that new value again not changing no matter how far I run along the Segment until I do one of the things mentioned before.

I had “Distance Remaining” work on some segments when I was ahead of my PR, but it was never consistently counting down the distance: it was always very “laggy” and sometimes randomly jumped back to an older (higher) value.

2) When running a segment the watch sometimes switches to the map screen and gives me completely senseless turn directions. In the attached “Thru tha Gibb” Segment it always tells me to turn left on one of the junctions before the end of the Segment though the Segment clearly continues straight.

3) Sometimes canceling a Segment when approaching it works as expected, but sometimes after pressing cancel the watch starts beeping as if it was giving turn directions after a while. There are neither directions popping up on the screen nor is a course shown on the map screen, just the beeping. If I press the up button to get to Settings I get the option to “Stop Navigation” which is the only way to turn the beeping off.

I think those issues are only found on the 5x (like the special characters freeze) and am guessing that it has something to do with its different routing capabilities.

1) The “Distance Remaining” data field doesn’t change when you are behind your PR (see attached) picture. It stays on the same value while “Time Behind” and “Segment Pace” at least show changes.
When I switch to another screen, pause or press the lap button (Autolap does the same) the “Distance Remaining” jumps to what seems to be the correct value but immediately gets stuck on that new value again not changing no matter how far I run along the Segment until I do one of the things mentioned before.

I had “Distance Remaining” work on some segments when I was ahead of my PR, but it was never consistently counting down the distance: it was always very “laggy” and sometimes randomly jumped back to an older (higher) value.

The lagginess issue is something I've had and noticed in 2.95. Haven't tried it yet in 2.96.

I'm getting incorrect altitude. It's almost twice the correct altitude. The ambient pressure seems correct but the barometric pressure is too high. The altitude and barometric was correct before the beta 2.96.

Till now i always save HR data before saving swim workout, i have never used "download later" hr data neither on my previous fenix 3...

I'm not talking about the download later but about the instant save of the log.
The way the rechr works is simple... the log is stopped but not yet closed so you wait for your heart to drop and after the rechr is notified, you can save the log and that data is saved into the log alongside everything else.

The problem here is that in order for this to happen, i think you need to stop the log when bothe the watch and the hrm swim are out of the water. This is what I did with the second of the 2 logs. I've waited and waited and waited but didn't get the notification. However, the rechr was there. So there's surely something wrong with the hrm/swim and F5 (and probably F3) in regards with the rechr.

I think the software doesn't understand that the rechr with the hrmswim can't be working the same as with the ohr or hrmrun because it's still a delayed transfer: the hr is not in the log until the download is done while it already is in the log with the ohr and hrm run.
So you see... your heart starts dropping when your hit stop but the watch doesn't know that since the hrm is still underwater and can't compute your recorded hrmax against your Z1 because there's no live connection (it's a delayed download).

I notified the beta devs about this.

I can confirm #1 and #3 on 2.90. #1 is really anoying and ruins the experience

Hey all!

I'm experiencing several bugs with Strava Live Segments and the 2.96 beta and would like to know if others are having them too. Here's a description of the bugs from a mail I just sent to the beta team:

Unfortunately there are still several bugs that make the Strava Segments more or less unusable for me on the Fenix 5X:

1) The “Distance Remaining” data field doesn’t change when you are behind your PR (see attached) picture. It stays on the same value while “Time Behind” and “Segment Pace” at least show changes.
When I switch to another screen, pause or press the lap button (Autolap does the same) the “Distance Remaining” jumps to what seems to be the correct value but immediately gets stuck on that new value again not changing no matter how far I run along the Segment until I do one of the things mentioned before.

I had “Distance Remaining” work on some segments when I was ahead of my PR, but it was never consistently counting down the distance: it was always very “laggy” and sometimes randomly jumped back to an older (higher) value.

2) When running a segment the watch sometimes switches to the map screen and gives me completely senseless turn directions. In the attached “Thru tha Gibb” Segment it always tells me to turn left on one of the junctions before the end of the Segment though the Segment clearly continues straight.

3) Sometimes canceling a Segment when approaching it works as expected, but sometimes after pressing cancel the watch starts beeping as if it was giving turn directions after a while. There are neither directions popping up on the screen nor is a course shown on the map screen, just the beeping. If I press the up button to get to Settings I get the option to “Stop Navigation” which is the only way to turn the beeping off.

I think those issues are only found on the 5x (like the special characters freeze) and am guessing that it has something to do with its different routing capabilities.

F5x + stryd

F5x on 2.96 + Stryd 2.0 seems to consume excessive battery.
A 40min activity eats 15% of juice from Fenix5x.

Also noted that when distance and pace are set to ALWAYS in footpod (stryd) F5x looses GPS aprox 5min into activity - there is no track on map. It misteriously resumes after 10-15min with an ugly straight line.

Anyone else noticed similar problems on 2.96 or with stryd?