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 have 2.40 with 5 sapphire iPhone 7.
I saw that one betatester on 2.72 claimed the bluetooth has improved under 2.72, but Ive only read this claim once.
Looks like all the people say the BT is good is on 5x (same size as fenix3), and everybody complain have the normal fenix5.
I moved to 2.72 on my Fenix 5 - still a lot of re-connects, not even related to distance.
Not everyone with the 'normal' Fenix 5 is complaining either. I'm on 2.72 beta and the BLE connection is entirely stable with my iPhone SE. I also have my Fenix 3 connected and as I slowly walk away from the phone with both watches the Fenix 5 looses BLE connection ever so slightly ahead of the Fenix 3, but by that point I'm already at the far end of a separate room to the phone, so the Fenix 5 maintaining that far is more than acceptable. I remember in the early days of the Fenix 3, there was big variability of BLE connection depending on what make/model of phone was used (not just iOS vs Android). If you are on 2.72 beta, record your findings (including exact make/model of phone and version of OS and GCM) and fire it over to the [email][email protected][/email] email, as detailed in the first post in the beta thread.
I also have F3 - my F5 stays connected while I am close to the iphone, just that compared to F3, the F5 range is 3 or more times shorter!
I also have F3 - my F5 stays connected while I am close to the iphone, just that compared to F3, the F5 range is 3 or more times shorter!
Maybe the F5 reports the disconnect earlier than the F3. Maybe the F3 is already out of range and does not know about it, so notifications wouldn't reach the F3.
Maybe the F5 reports the disconnect earlier than the F3. Maybe the F3 is already out of range and does not know about it, so notifications wouldn't reach the F3.
It is not that, F3 gets notifications when F5 reported out of range many metres before...
IMO, metal case = reduced GPS, WiFi, and Bluetooth signal integrity. Goodbye F5...hello 935!
I'm probably in the same boat but 935 is not around to buy yet. Not to mention this watch is a bit too heavy for running. I've only had this watch a day and been getting disconnect alerts from the start with my Galaxy S6. I suspect it has something to do with the android app and the bluetooth on the phone. Where is the setting to disable disconnect alerts? I can't find it in the menus.
I do not see any BT setting options in the 5X. I watched DC Rainmaker's video and it shows a BT setting option just above the WiFi setting option. Am I alone in this or does the 5s/x not have an option to change BT settings?
I do not see any BT setting options in the 5X. I watched DC Rainmaker's video and it shows a BT setting option just above the WiFi setting option. Am I alone in this or does the 5s/x not have an option to change BT settings?
On my watch it's called "Phone," and it's just above WIFI.
I have 2.40 with 5 sapphire iPhone 7.
I saw that one betatester on 2.72 claimed the bluetooth has improved under 2.72, but Ive only read this claim once.
Looks like all the people say the BT is good is on 5x (same size as fenix3), and everybody complain have the normal fenix5.
I'm on the original 2.40 that came with the watch. I actually find the BT range improved slightly vs. my F3.
