Fēnix 5S/5 – 3.42 Beta Release

Has anyone faced any of these "issues" that have been fixed? I've not heard anyone have these issues. One would think the priority would be to fix things like ant and bt connection issues, livetrack not ending etc. You know, the problems that people are actually facing! Also improve gps to at least the level of the Fenix 3

Has anyone faced any of these "issues" that have been fixed? I've not heard anyone have these issues. One would think the priority would be to fix things like ant and bt connection issues, livetrack not ending etc. You know, the problems that people are actually facing! Also improve gps to at least the level of the Fenix 3

Er yeah. Have you not seen all the posts in these issues? Obviously not ...

Has anyone faced any of these "issues" that have been fixed? I've not heard anyone have these issues. One would think the priority would be to fix things like ant and bt connection issues, livetrack not ending etc. You know, the problems that people are actually facing! Also improve gps to at least the level of the Fenix 3

That's funny you should mention that because that is exactly what I was thinking while reading this. Non of the issues stated by other is even been considered here?? I would expect that before fixing simple issues , that they would deal with the real problems ....

Where's the new sensor hub update

The beta program should be updating the sensor hub as first priority until the Ant+ connection is stable across all devices. It sad when my Fenix 5 sapphire 900 dollar watch won't connect to my bike speed/cadence sensor which connects to my edge 500 fine. It's basically useless for anything but running. I didn't pay that money for it not to connect to ant + sensors. Fix it as first priority Garmin.

Hello Fenix 5S/5 users,

We have new beta software ready for your upcoming adventures! Please read the 'notes' and 'installation instructions' in the 'Updates and Downloads' page found in the links below for your specific device. We look forward to your feedback.

Fenix 5S:http://www8.garmin.com/support/download_details.jsp?id=11661
Fenix 5:http://www8.garmin.com/support/download_details.jsp?id=11663

Please send all bug reports to [email][email protected][/email], and indicate which model of the fēnix 5 series you have in the subject line.

Note: Please allow for the updates to propagate across all servers. There is no need to post that the link does not work. It will after a bit of patience. :)

3.42 Change Log Notes:

• Fixed an issue where ConnectIQ data fields were not able to record information to FIT files.
  
• Fixed an issue where the device screen seems to pulsate when using a white background, in low power mode.
  
• Fixed an issue where the ‘Lap Ascent’ field was not displaying valid data on the lap alert page.
  
• Fixed an issue where the Indoor Row summary information was displaying distance metrics, instead of stroke data.
  

Send all bug reports to [email][email protected][/email]

Any chance of fixing the inaccurate floor count/inaccurate altimeter readings please?

Well, I get the pulsing display but hadn't posted about it because I assumed it was just a hardware thing. You only notice it at certain angles and in a certain light. That's not with a white background though, it's black background and the white text pulses.

The beta program should be updating the sensor hub as first priority until the Ant+ connection is stable across all devices. It sad when my Fenix 5 sapphire 900 dollar watch won't connect to my bike speed/cadence sensor which connects to my edge 500 fine. It's basically useless for anything but running. I didn't pay that money for it not to connect to ant + sensors. Fix it as first priority Garmin.

It's silly to assume this isn't a top priority for Garmin but clearly it's not an easy fix either.
Also based on what we know it would appear to be a sensor hub issue, which is a different section of code to the "main" watch OS so it will be a different set of developers with a different set of expertise.
Asking the rest of the developers to drop everything else to focus on the sensor hub issues would likely be of little benefit to the Ant+ problem and slow down sorting out fixing bugs/adding features to the main code.

It would also be foolish to hold off the rest of the beta programme will they've found a fix for the sensor problems - there's plenty of "quick wins" they can sort out in the meantime and it doesn't make sense to break their weekly beta cadence just to show that the sensor problem has been their main priority. Imagine the uproar here if they didn't release a beta for a month.

That's funny you should mention that because that is exactly what I was thinking while reading this. Non of the issues stated by other is even been considered here?? I would expect that before fixing simple issues , that they would deal with the real problems ....

Though it might seem like this forum is the only source of bug issues with the watch the fact is that isn't true at all - there will be people who chose to log issues through the other support channels that Garmin have, or otherwise they may have encountered the bugs via the previous beta releases and emailed the beta team directly which is what they ask you to do (and which I have done rather than posting bugs while running beta firmwares).

Also don't forget the main watch firmware is shared across Chronos, the F5 series and the Forerunner 935 so there's more than just this forum to trawl for bugs/issues.

With regards to fixing the "real" problems first. As I just mentioned in my response to ShannonA the Garmin team are clearly operating a weekly beta cadence and if a developer has a chance to quickly fix a problem then why wouldn't they?

I look at the list of fixes in this release and the first thing that strikes me is how small the list is - which to me suggests they have devoted a decent chunk of the past week to tackling some of the "real" problems but they haven't got to a stage where they can release any fixes. But the beta users still have an expectation of a weekly release so here we are. It will be very interesting to see what we get in next week's beta release.

Thanks for the update... the guys with flickering screens will be happy :)

I'll test the IQ datafield fix tonight.

I disagree

We have had numerous sensor hub updates in the beta program. It's the number one issue of the sport watch. The watch is meant to connect and stay connected to Ant and Bluetooth sensors just like every other Garmin watch or edge bike computer. It just isn't and for such an expensive piece of equipment it should work with out any issues.

It's silly to assume this isn't a top priority for Garmin but clearly it's not an easy fix either.
Also based on what we know it would appear to be a sensor hub issue, which is a different section of code to the "main" watch OS so it will be a different set of developers with a different set of expertise.
Asking the rest of the developers to drop everything else to focus on the sensor hub issues would likely be of little benefit to the Ant+ problem and slow down sorting out fixing bugs/adding features to the main code.

It would also be foolish to hold off the rest of the beta programme will they've found a fix for the sensor problems - there's plenty of "quick wins" they can sort out in the meantime and it doesn't make sense to break their weekly beta cadence just to show that the sensor problem has been their main priority. Imagine the uproar here if they didn't release a beta for a month.