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? 

  • I should be able to listen to music without worrying about a watch hijacking the bluetooth connection. What’s the deal here?

  • Hi there, are the Air Pods connected directly to the watch Bluetooth or are they paired with the phone Bluetooth when you are experiencing this issue? 

  • Yes, I've received such email as well, and I was honestly quite surprised by the amount of troubleshooting being requested: granting access to my account, recording videos, testing different configurations, sending app logs, enabling Bluetooth logging on the watch, answering multiple questions, and so on.

    I'm a customer, not an outsourced member of your QA team. And the statement "Please note that we cannot work towards a resolution on this concern if we are not getting replies to the emails we are sending out" comes across as a bit absurd.

    At this point, I'm dropping out of this discussion thread. I hope Garmin is able to reproduce the issue internally and provide a proper fix.

  • I’m having the exactly same issue. It started right after I got my garmin forerunner 570 a week ago. My airpods are directly connected to my iphone.

  • I have exactly the same issue, really find this unacceptable for top of the range watch. 

    As long as the watch is ON, is it not possible to use Airpods. The headphones connect/disconnect non-stop. 

    What is the fix for that as this issue basically makes the watch unusable in day-to-day life if you are using Airpods.  

  • I just reported the same issue, but if this is what I will receive from Garmin I agree it is absurd...       - have you been able to recreate the issue internally? Given how many people are literally reporting the same problem, this should be very easy to recreate on your end. 

  • I isn't, if they don't know exact configuration of your watch (widgets installed and so on), they might not be able to replicate it.
    And to be honest, if you reporting issue and expect it to be solved you need to work with vendor on it, if you think it will be solved just because you expect it it never happen, it is technology, not a magic.

    I was worked on various software issues with various software vendors and it is typical that they ask for logs and other evidences to find issue source and fix it.

  • Ok fair, but it looks like a widespread issue so I doubt it would be super difficult to replicate. In any case whether I find it absurd or not, will certainly try and help as this basically makes the watch unusable for me... 

  • FWIW, I’ve been having the same issue with my Edge 1030+ bicycle computer.  Closing garmin connect (and changing the Edge’s bluetooth setting to prevent connect from launching at bluetooth connection) now allows me to use my airpods without interruption (3 successful rides so far), but I’m no longer able to use incident detection or livetrack.  Frustrating!

  • I understand that logs and additional information can be necessary, and I'm certainly not expecting issues to be fixed by magic.

    But if you follow the full thread, you'll see the complete lack of transparency regarding this issue - whether Garmin has been able to reproduce it internally or whether any progress has been made. Even a simple note saying they can't share that information would have been something, but there has been virtually no communication for weeks. And it's exactly this lack of communication and transparency that makes it feel like the bulk of the troubleshooting effort is being offloaded to us.

    In the meantime, I worked around the issue by disabling automatic updates, as mentioned somewhere in this thread. Given how frustrating this whole experience has been, I simply don't feel like investing a considerable amount of my personal time into troubleshooting it any further.