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

Bluetooth connectivity issues

My phone is the Pixel 6 Pro. I've had my Fenix 7X solar sapphire for 3 days now and the last two mornings, after sleep the watch has refused to sync. It will say it's connected but when I go to the Garmin Connect app and push the sync button (two arrows in a circle) the watch will begin syncing then disconnect from bluetooth. This causes the sync to fail. After which the watch will start connecting and disconnecting before finally settling down in a connected state. If I try syncing again it fails with the same behavior.

I've tried forgetting the watch under bluetooth settings and pairing the watch again. It doesn't work. Neither does rebooting both the watch and the phone.

The only way I've been able to reconnect the watch is forgetting the watch under bluetooth settings, removing the watch from the Garmin Connect app, and then adding the watch through Garmin Connect app again.

So far this hasn't happened during the day and it's only occurred after waking from sleep.

Has anyone else had similar issues? 

  • Maybe F7 would like to save too much battery

  • I have Fenix 7x sapphire version connected to a pixel3xl and i can say that i have  a similar issue : the watch it keep connecting and disconnecting and I don't know what to do .

  • Hi have the Fenix 7X Sapphire and connect to my Samsung 8 with no issues.  Hasn't disconnected once.  The only BT connection issue I have, which was the same on the 6X, is connecting to my Jabra Elite BT ear buds. I have to first disconnect them from my phone and then connect to my Fenix 7X and then connect to my phone.  This is the only way I can get both the 7X and my phone connected to the Jabra Elite ear buds at the same time.

  • Hi - do you still have this issue? It happens randomly to me. I had this problem with my Oppo Reno 6 Pro and now the same happens with the galaxy S22 Ultra. Interestingly enough - it doesn't happen all the time. For like 2-3 days or even more it works just fine, then it starts to disconnect / connect randomly. 

  • If this question was for me, no I do not have drops.  I just have to turn off bluetooth on my phone first, then connect to my headphones and then connect to my phone.  Works every time and never disconnects.

  • This is a pixel issue.  I have the same phone and issue with my new Epix.  Google "fixed" BT in the Feb update, but it created this issue for me. I have also removed/re-added the watch with  no change in the issue.

    For now, i turned off the notice of BT disconnect and just live with it. it only seems to happen when I am on calls with another BT headset and then - its CONSTANT. 

    Practically, I have seen no "impact" of this as my Sync's and notifications are working fine since the drops are very short and only when on calls.

  • For me it's not a phone issues, instead the service app (Garmin). For some reason it crashes and then it keeps disconnecting. A phone reboot fixes the issue until the next time...

  • I have the same issue with my Fenix 7 x and Apple phone. Connects and disconnects constantly. Drains battery. This is my 4th Fenix and I have not had these issue before.

  • Today something interesting happened:

    The watch had no disconnecting issues for 2 days (last phone reboot). I started youtube music on my phone (no external / bluetooth speakers, just using the phone speakers) and the watch started the connect/disconnect loop. I then started the garmin app (while playing music) and the watch kept the connection. I started my strenght training and after about 4 minutes I decided to change song from the watch. After changing 2 songs in a row, the watch disconnects and starts its loop again. This time I did nothing and after about 30 secs it fixed by itself.

    I literally don't get it.

  • I got exact same issue, I use Fenix 7x Solar Saphire + Pixel 6 Pro... 

    Garmin really need to to something, I got this issue as well as crashing issue all the time