Repeated bluetooth pairing codes after disconnecting watch (bis)

Since Garmin closed the previous forum (https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-mobile-andriod/283174/repeated-bluetooth-pairing-codes-after-disconnecting-watch) saying the problem was fixed, it has gotten worse. The problem persists. My forerunner 745 unpairs every time I move a bit away from the phone and I have to re-pair over and over again. Please Garmin, fix this issue. Forerunner 745 with Samsung Galaxy A32, Android 12. Thanks.

Garmin-Adrian Garmin-B

Top Replies

All Replies

0 seilogramp over 1 year ago

Did you verify that you have this on your phone?

Garmin-Eiliko said:
fixes were released in the July system software updates for Galaxy A-series phones

If so and still having issues, you probably should contact support directly...

Garmin-Eiliko said:
for faster and more detailed assistance, reach out to your local Garmin Product Support team directly

0 Magali 1807794 over 1 year ago in reply to seilogramp

Yes, I've already done that and it still doesn't work. I have communicated repeatedly with Garmin's technical service about this issue (also because the barometer fails) but they do not know how to fix it

0 seilogramp over 1 year ago in reply to Magali 1807794

Magali 1807794 said:
I have communicated repeatedly with Garmin's technical service

To be clear, the fix that Garmin-Eiliko mentions in the other thread is a Samsung update, not a Garmin Connect Mobile update.

0 Magali 1807794 over 1 year ago in reply to seilogramp

YES, I HAVE SEEN THE SAMSUNG VIDEO AND VERIFIED IT AS IS, ON MY PHONE. IT ALREADY HAS THE SOFTWARE UPDATED TO THE MOST CURRENT VERSION POSSIBLE: VERSION ONE UI 4.1 VERSION ANDROID 12

0 Magali 1807794 over 1 year ago in reply to Magali 1807794

TO BE CLEAR, GARMIN IS FAILING AND DOESN'T KNOW HOW TO REPAIR IT

0 Magali 1807794 over 1 year ago in reply to seilogramp

THANK YOU

0 seilogramp over 1 year ago in reply to Magali 1807794

You're welcome.

0 Konrad over 1 year ago

I have exactly same isue with fenix 5+ and galaxy a13.

Tried many tips from this forum and nothing helps.

0 Magali 1807794 over 1 year ago in reply to Konrad

The worst thing is that Garmin transferred the responsibility to Samsung and washed their hands...

The problem continues but close the forums to cover it

0 Konrad over 1 year ago in reply to Magali 1807794

Funny thing is that all my problems begun when I changed my old S6 to new A13. So maybe it is Samsung`s fault, but somehow Garmin could comunicate with them and try to solve the issue.