This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connected... not connected... connected... not connected; weak bluetooth signal

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?
  • Former Member
    0 Former Member over 8 years ago
    The bluetooth connection on this watch is garbage when paired to my Samsung GS6. I have had nothing but problems staying connected to my phone. I have to remove the device from Garmin connect and add it back every few days. I'm ready to take it back to the store.
  • Former Member
    0 Former Member over 8 years ago
    iPhone 7 plus in jacket pocket, watch loses connection, annoying, Garmin, can u fix this?
  • Former Member
    0 Former Member over 8 years ago
    I confirm that the bluetooth signal is awful, especially for a 600$+ watch.
    Owned a Vivoactive HR previously and it was much better.
  • What's the best way to get Garmin's attention/reaction for this issues? Just wondering, if this can/will be fixed in the future.
  • What's the best way to get Garmin's attention/reaction for this issues? Just wondering, if this can/will be fixed in the future.


    The best way is that all with such issues to complain here then call garmin and direct them to read this thread. If there is a hardware thing than at least they should acknowledge as there is nothing to be done.
  • Former Member
    0 Former Member over 8 years ago
    I've learned that rebooting my phone will re-activate the bluetooth connection... the watch will disconnect and be unsearchable to my phone within a day of connecting and their is nothing I can do about it except reboot the phone. And when I walk into another room with my phone left on a table, I get that disconnect alert. I never had this problem with my garmin 235.
  • The best way is that all with such issues to complain here then call garmin and direct them to read this thread. If there is a hardware thing than at least they should acknowledge as there is nothing to be done.


    So, I've e-mailed Garmin, by using the "support/e-mail" feature on their website. Provided the link to this thread as well. Below is what I've written. Let's see if there will be any constructive response :)

    "Hi, I've been struggling with the BT connectivity between my Android Phone and Fenix 5, since I got the watch. Device keeps disconnecting very often, even if the phone is within 30 cm range (on the same desk for example). There is a thread on Garmin Forum as well, where a lot of users are reporting same issue - link below. wondering, if there are any way to fix this? Link: https://forums.garmin.com/showthread.php?373080-Connected-not-connected-connected-not-connected-weak-bluetooth-signal
    Thanks in advance, Alex
    "
  • 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!


    So, I can also now confirm, that similarly to "Dutch30114" experience, the annoying disconnects are now gone after downgrading from 2.72 back to 2.40.
    To clarify - the "disconnected/connected" issue was present for me on 2.40 as well, from day 1. So, what was done chronologically:
    • Got the watch, registered/set up in Garmin connect/Express
    • Paired with the phone (sony Z1 compact, Android) via Garmin connect Android app - worked with the 3rd attempt
    • Updated to 2.40 firmware
    • Happy for the next day :)
    • Realized that watch drops the connection with phone every 20 min or so, even within half meter distance from each other
    • Noticed the 2.72 Beta - so upgraded by following instructions
    • Still same issues on 2.72
    • Downgraded back to 2.40 (WILL WIPE YOUR SETTINGS, VO2Max etc!) - as per "Dutch30114" suggestion
    • Re-paired with the phone again, put all settings back manually (backlight, alerts etc.)
    • No more disconnects every 5 minutes
    • Still weak range - 5-10 meters max
    • Sometimes the watch still needs "help" to connect back (re-enable bluetooth on the phone)


    My theory is that perhaps, for those who also have such disconnect issues, there is no need to upgrade/downgrade, but just reset to default and re-pair.
    *Disclaimer - the above are just my experiences :) - I'm not encouraging you to reset etc., entirely up to you!
  • Former Member
    0 Former Member over 8 years ago
    Answer provides no answer

    I spoke to Garmin support today. I got a Fenix 5s about 2 weeks ago and it also always connects/disconnects from my phone. At first I thought it may be my phone (I have a Pixel). Response is if you turn off the smart notifications it will work but it will also turn off phone and text notifications. It is all or nothing, so you basically have to accept it :mad: wrong answer. This thing was too expensive to not be able to turn off the annoying stuff and leaving the important stuff. Maybe with enough complaints they will realize something needs to be fixed.
  • I spoke to Garmin support today. I got a Fenix 5s about 2 weeks ago and it also always connects/disconnects from my phone. At first I thought it may be my phone (I have a Pixel). Response is if you turn off the smart notifications it will work but it will also turn off phone and text notifications. It is all or nothing, so you basically have to accept it :mad: wrong answer. This thing was too expensive to not be able to turn off the annoying stuff and leaving the important stuff. Maybe with enough complaints they will realize something needs to be fixed.


    Interesting "solution". So, once you disable "Smart Notifications" on the watch, the BT connection remains solely to facilitate the sync of activities data. Wondering now, does this mean that the problem is SW related, rather than HW? Did you notice any "improvement"? :)