Fenix 5X - 2.96 Beta Release

HR Rate??

The HR bug is odd. For me, I find sometimes changing the watch-face shows HR 255BPM, however, if I just leave it for 20-25 mins, it automatically updates and shows the correct HR.

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?

No such problems here.

I may have found an issue with 2.96 and Vector 2 power meter pedals.

The zero offset calibration is reading as successful but the calibration is ending almost instantly; in then displays a value of 0 with no fluctuations.

This is different to how the calibration has always gone on my Edge 1000, FR935 and the Fenix 5X prior to installing 2.96.

Then during the activity; every 90 seconds or so it will briefly drop to a spike of no power.

Only done one ride so far but I'm about to do a slow ride on Zwift so I will record it on the F5X and see what happens.

EDIT 3:
Yup; removing and re-adding the sensor sorted it; I think I added the sensor before upgrading the firmware so maybe it sent it a bit wappy and I just never noticed but seems fine now so ignore the below post.

Feel free to poke fun at me ;)

I may have found an issue with 2.96 and Vector 2 power meter pedals.

The zero offset calibration is reading as successful but the calibration is ending almost instantly; in then displays a value of 0 with no fluctuations.

This is different to how the calibration has always gone on my Edge 1000, FR935 and the Fenix 5X prior to installing 2.96.

Then during the activity; every 90 seconds or so it will briefly drop to a spike of no power.

Only done one ride so far but I'm about to do a slow ride on Zwift so I will record it on the F5X and see what happens.

Yeh seems to be an issue.

Garmin Edge:
https://connect.garmin.com/modern/activity/1707190434

Fenix 5X:
https://connect.garmin.com/modern/activity/1707192060

Both were calibrated before the ride and I stopped briefly after a few minutes and did it again.

Fenix 5X is showing power dropouts at very consistent intervals.

EDIT:

Looking back at all my previous activities it seems the 5X has had the dropouts everytime I've used it; even with firmware 2.95.

It is also not recording cycling dynamics at all.

Sadly I upgraded the firmware before I did any rides so I have no data on the stock firmware unless I revert it back and record some.

My FR935 is working fine though, both in terms of no dropouts and recording cycling dynamics:
https://connect.garmin.com/modern/activity/1690352337

EDIT 2:
Possibly scratch all that lol

Removed the sensor and re-added it and now I can at least see the cycling dynamics options within the sensor settings and the calibration was more as expected, so riding now to try it but I suspect it will have solved it :)

Here is a copy of my mail to the beta team (for reference) :

Greeting beta team!
I took the time to install the latest beta just when my Stryd footpod arrived.
Couple of bugs I found (most like Stryd related) :

1.Stryd has been paired as footpod and power meter at the same time.

A. Fenix 5x consumes excessively battery - 20% while on 50min activitiy.
B. 10 min into activity gps looses track and stops recording (I've set pace and distance from footpod). It resumes when I click map screen zoom in and out a couple of times. After that missing track is connected with a straight line from the place where it losts its signal to where I was.
C. Fenix 5x continues to drain battery even after activity has been finished - it dropped from 31% do 26% in 30min after finishing the activitiy, and then misteriusly regained 4% during a couple of hours into the evening (when I was watching tv).

2. I've deleted Stryd as power meter and left footpod only and set distance to gps and pace to footpod (did this, before my 10k race this morning).
A. Map problem and GPS signal loss didn't occur.
B. LT levels didn't get updated even thou they are currently at 4:46/173 and my 10k race was on avarage at 3:55 pace.

For the sake of keeping things alive ill paste my software suggestions from a previous mail:

Please allow me to suggest some things that work on older garmin devices and are something that I, as a ultrarunner consider as basic (not to mention, that I updated from F3 hoping they all are there by default):

MISSING FEATURE: Working coursepoints - there is no way to add working coursepoints / waypoints for a route (prepared in basecamp), so that the watch can show distance to next waypoint while navigating.

MISSING FEATURE: auto valleys / summits when navigating: my 10 year old gpsmap62s has this and it's the only reason I still keep the device. When uploading a GPX with route it automatically calculates summits and valleys out of gpv elevation and shows distance / evelation to next.

MISSING FEAUTRE: zoomable elevation plot while navigating a route. While on a 100k (or even 50k) ultra run, elevation plot is not readeable. Please add an option to zoom in / zoom out for a user defined scale (say 5k, 10k, 20k...)

HR bug

Please fix the HR bug. For a device at this price-point, it really isn't acceptable. Most useful watch faces (e.g not the Garmin stock ones) crash, they reset themselves, they crash the device, they don't show information correctly etc etc. AFAIK this is not the fault of the developers. If Garmin tried to use the extra processing power in the 5x in a 'novel' way, could they at least make it work first. I'd rather functionality, than 'novel' ideas.

Please fix the HR bug. For a device at this price-point, it really isn't acceptable. Most useful watch faces (e.g not the Garmin stock ones) crash, they reset themselves, they crash the device, they don't show information correctly etc etc. AFAIK this is not the fault of the developers. If Garmin tried to use the extra processing power in the 5x in a 'novel' way, could they at least make it work first. I'd rather functionality, than 'novel' ideas.

I posted about this a few posts back including a quote from one of the ConnectIQ SDK team stating that they know about the issue, explaining what's causing it and saying they are working on a solution to it.

I posted about this a few posts back including a quote from one of the ConnectIQ SDK team stating that they know about the issue, explaining what's causing it and saying they are working on a solution to it.

Indeed, however ttbomk and afaik this beta was released after the dev conference.
Without reading your post, how could I have known about the 'novel' processor usage?
Anyway, here's hoping the issue is sorted for 2.96 final. :cool::cool::cool: