Fēnix 5S/5 – 3.44 Beta Release

Hello Fenix 5S/5 users,

We have new beta software ready for your upcoming adventures! This is a public release candidate. Please let us know of any major issues ASAP!

Please read the 'notes' and 'installation instructions' in the 'Updates and Downloads' page found in the link below. 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.44 Change Log Notes:

Misc. bug fixes and improvements.
Fixed an issue where certain types of navigation would not work as expected on device.

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

0 espenringom over 8 years ago

Bluetooth connection is still abysmal. Im worried this will never be fixed. That it is a hardware problem. If it is, this watch is useless for me. I find my old fenix3 superior for anything except the size.

0 rickj2903 over 8 years ago

Road silva

Bluetooth connection is still abysmal. Im worried this will never be fixed. That it is a hardware problem. If it is, this watch is useless for me. I find my old fenix3 superior for anything except the size.

If it's a hardware issue I will be expecting Garmin to issue a recall and issue refunds. This is getting beyond a joke now.

0 rickj2903 over 8 years ago

I have already written many times: Why Americans with citizenship will not be sued by Garmin.
For the sale of goods not corresponding to their descriptions.
For the use of customers as beta testers of their products. This happens with all Garmin products. (sport)
They throw unfinished goods on the market.

In the UK an item has to be fit for the purpose for which it was sold, well I'm beginning to think the F5 may not be fit for purpose. Other than telling the time it doesn't do anything else reliably

0 calu_46 over 8 years ago

I am surprised at the bluetooth connection problems that many people encounter, the problem is present with your smartphones? The connection between my fenix 5 and my S7 is stable even if one floor and about 15 meters separates the two devices

Fenix 5 with 3.30 firmware

0 peteholloway over 8 years ago

I am surprised at the bluetooth connection problems that many people encounter, the problem is present with your smartphones? The connection between my fenix 5 and my S7 is stable even if one floor and about 15 meters separates the two devices

Fenix 5 with 3.30 firmware

I agree... think the phone is the culprit. I use an iPhone 6 with no issues. Normal range is around 20m, consistent with my fenix 3 and fenix 3 HR.

0 Former Member over 8 years ago

It's not the phone, although it may have a small impact. I have tried an iPhone 7, Samsung s7 edge, oneplus 3t and Samsung s8 and the range is poor on all. My old garmin vivoactive has no issues.

Clearly fault is with fenix 5s.

0 peteholloway over 8 years ago

It's not the phone, although it may have a small impact. I have tried an iPhone 7, Samsung s7 edge, oneplus 3t and Samsung s8 and the range is poor on all. My old garmin vivoactive has no issues.

Clearly fault is with fenix 5s.

Might be a hardware issue then, as not all fenix 5 watches are affected.

0 calu_46 over 8 years ago

Ok so it seems to be a hardware problem on some devices, but it's not a common problem with all the fenix 5

edit : too late

0 rickj2903 over 8 years ago

There is a theory that it was the early units that are having the issues. I was one of the first adopters but have had a second unit since then which is just the same.

0 peteholloway over 8 years ago

I had a weird issue yesterday trying to navigate straight back to the start using the SUP App (using 3.42), a corrupted screen with 4 time indicators with lines through them appeared. I tried again using trackback, which worked as expected. I will test if this bug is fixed with 3.44 tomorrow.

This issue appears to be resolved, straight line trackback using the SUP App appears to work as expected now. The only minor issue is the text displayed when arriving back at the start, it says: "Arriving at straight line" and should probably rather say: "Arriving at Start"