Related
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

Repeated bluetooth pairing requests when already paired to Garmin Connect (Android)

englishbob
over 3 years ago

Hello,

For about two weeks now my 245 seems to want to repair with my phone. I'm not doing anything to initiate it, it just starts on its own. If I do get it to pair it syncs and then after a while decides it needs to repair and I have to delete the device from my Android Garmin Connect app and add it again. I've tried turning the watch off and back on but it issue comes back. I can't work out if it is the app rejecting the watch or the watch rejected the existing pairing.

Regards,

Rob

  • 0 over 3 years ago

    Same for me with the current (v8.02 beta) and previous (v7.80) firmware. However, mine only attempts to "re-pair" during a Running or Treadmill activity. I get a six-digit code appear and then a Failed to Pair message if I don't cancel it. This all the while paired with my Android phone, chest HRM and Garmin Pod.

  • 0 over 3 years ago

    I am having this exact issue with the fenix 6 sapphire.  It will stay paired with my Google Pixel 6 Pro for a few minutes, and then all of a sudden it will seek to pair again and a 6 digit code appears on the watch.  Did you ever resolve your issue?

  • 0 over 3 years ago in reply to 1003348

    I'm afraid not. It has become less frequent but it has not gone away. The Pixel 6 Pro has just come out I believe. Did this happen with your previous phone? I don't have any other Bluetooth devices that exhibit this behaviour with my phone.

  • 0 over 3 years ago in reply to JPB123

    Mine never seems to want to repair during an activity. It is always when the watch is 'resting' between activities. I've come back from 5 hour long activities and had no problem syncing. It happens at other time.

  • 0 over 3 years ago in reply to englishbob

    Yes my phone is new and this did not happen with my previous phone (Samsung Galaxy S21).

  • 0 over 3 years ago in reply to englishbob

    Thanks for your response!!  Oddly enough the problem seems to have resolved itself within the last couple of days... though I don't know how.  It may have been a phone reboot or a watch reboot. I wish I knew as I am afraid it might come back and when it was happening, it was fairly regular... every several minutes.