My old Fenix 3 HR would stay connected to my phone via bluetooth at least twice as far as my new F5. Did Garmin decide to gimp the bluetooth transceiver on the F5? It literally buzzes all day long... sometimes when I'm walking only 15 feet away from it. Yes, I can turn off the notification but I really liked how my old Fenix 3 HR would buzz and warn me when I left my phone behind. Nice feature to have. Would hate to lose that feature because of a gimped BT transceiver. I'm hoping that my unit is just defective. Any others here that had a Fenix 3 HR and now have a F5 experiencing the same?
I found that the 2.90 firmware on my 5X is substantially less stable than 2.40 (go figure!) on both bluetooth and ANT+ connectivity. I'd love to be able to downgrade to 2.40 but can't find the download link anywhere.
Can you please point me to where you found the 2.40 files?
Thanks!
The 2.40 file was included together with the 2.72 beta - I guess the link got removed already/replaced with current beta (2.95). Also - not sure if you can downgrade from 2.90 to 2.40 by using the file which they included...This is my first Fenix, so - not much experience here :)
Missed a bunch of important calls today.
Phone was less than ten feet away from me.
It is supposed to be a watch that is connected to your phone right?
Turning off notifications because it won't stay connected is not acceptable at all.
The 2.40 file was included together with the 2.72 beta - I guess the link got removed already/replaced with current beta (2.95). Also - not sure if you can downgrade from 2.90 to 2.40 by using the file which they included...This is my first Fenix, so - not much experience here :)
I casually found that deleting all segments from the /Garmin/segments folder on the watch (especially the ones with non-English characters) has restored some stability to my watch on 2.90. It no longer hangs on Bluetooth or Wi-Fi syncs and the BT connection seems as stable as I remember it from 2.40. What is still broken is that I can no longer find and pair my ANT+ footpod which worked perfectly on 2.40. Mystery!
Just turn off the connection alert then and you'll never know you're not connected. When you are in range then you'll get your notifications. Admittedly you'll be a couple of minutes behind on things, but that's not such a bad thing.
How do you turn off the "connection alert" specifically? I can only see a setting to turn off all alerts. Not really the same thing (unless I'm missing something).
How do you turn off the "connection alert" specifically? I can only see a setting to turn off all alerts. Not really the same thing (unless I'm missing something).
Settings / Phone / Alerts = off
This is different than Settings / Phone / Smart Notifications / Status.
The "Alerts" setting controls whether you get notified when the Bluetooth connection drops. The Smart Notification Status controls if you see notifications from the phone or not.
This is different than Settings / Phone / Smart Notifications / Status.
The "Alerts" setting controls whether you get notified when the Bluetooth connection drops. The Smart Notification Status controls if you see notifications from the phone or not.
Thanks.
Is the Bluetooth connect/disconnect alert really the only thing that's controlled by this setting? If so, that's great, but what a poorly named setting!
So, below is the response I got from Garmin so far. I've upgraded now to 2.95 beta. Don't see any difference for now - lost connection after moving few meters away. Let's see if it'll keep disconnecting while on the same desk...
"our senior team has asked that you upgrade to the beta software that was recently released to see if you notice any improvement".
