Airpods connect/disconnect to iPhone

I recently got a Fenix 8 47 mm AMOLED and really love it HOWEVER, for some reason my Airpods have stopped working with my iphone. I do not want to connect the airpods to the watch and haven'r done so eather, but not when I want to use the airpods with my phone, they keep connecting and disconnecting instantly. I know its the garmin watch / app spooking because they work perfect when the watch is disconnected. 

I have also tried resetting the airpod connection with my iphone but with the same results.

Anyone else experienced this and know how to solve it? 

  • Absolutely this. If Garmin were to share what they'd found so far and ask for help in the open forum then they'd most likely have had a root cause in a couple of weeks. Many of us have setups that would be ideal for A/B testing - I have 1 watch, 2 identical iphones, and 2 sets of airpods. On one phone the issue happens consistently, on the other it never happens at all. If we processed all this and other feedback we should be able to find out what's wrong very quickly.

    My feeling is that despite the noise on here, this is a relatively rare problem amongst the tens of thousands of devices they sell - so it's low on their priority list. 

  • 6092549, which automatic updates have you disabled?  Garmin Connect, your Garmin device or your iOS?  I'm running an EOL Garmin device (an edge 1030 plus that Garmin hasn't issued an update for in a few years).  Would love to find a way to resume using Garmin Connect on my iPhone (as disabling Garmin connect is the only way I've found to keep my AirPod pro 3s from disconnecting)

  • 3938100 have you tried quitting Garmin connect on your phone and then changing your watch's bluetooth settings on your phone so that the phone doesn't launch connect when it automatically connects to the watch via bluetooth?  This solved my issue with my AirPod pro 3s randomly disconnecting from my phone, but I miss my Garmin connect functionality

  • !!!  FIXED  !!!!

    Hey everyone. While Garmin doesn't fix it (not fixed, in 23.15, 23.18 nor 23.19), just roll back to the latest stable version (22.37) and you're good to go. I did that and my Fenix 8 47mm AMOLED is back to work like a charm. No airpods disconnected, no bluetooth unstability, no sluggish menus, no supressed lap alerts, nothing of that mess they did later on beta program.

  • Many on here have done something that "fixed" the problem - but often only for them. I've tried older versions of Connect and it still happens for me. 

  • Sure you didn't. That has nothing to do with Garmin Connect but with the firmware you have installed on your device.

  • You do know that this doesn't just affect Fenix? I had a Vivoactive that follows a completely different firmware schedule. Others on here have other products and experience the same problem. The only thing consistent is the Connect app.

  • That's why it's written "my Fenix 8 47mm AMOLED".

  • Not consistent for me cause it didn't work. So, NOT consistent for me at all.

  • Maciel C. Glad to hear that reverting to an older firmware version works for you (and enables you to use your airpods with garmin connect running on your phone). You seem to indicate that, prior to reverting to an older firmware, closing Garmin Connect on your Iphone did not work for you(?) Did you both close the connect app on your Iphone AND go into your iphone’s bluetooth settings and, for your Fenix’ bluetooth connection disable connect from starting up when your phone connected to your Fenix via bluetooth?  I’ve recently (a few months ago?) had this problem crop up on another device (an Edge 1030 plus cycling computer, which Garmin hasn’t updated since May 2023) and the only way I’ve been able to use my airpod pro 3s while riding without disconnects was to make sure Garmin Connect is closed on my phone while using my edge/airpods and changing my phone’s bluetooth setings to prevent Garmin Connect from launching in the background when my phone and Edge connect via bluetooth.  Can’t believe that switching to a pre-may, 2023 firmware is going to solve this for me and want to be sure that Garmin support has a full picture of the scope (# of different devices affected by this ongoing issue) and nature (what remedial steps work and don’t work) of this issue.  Thx!