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

Garmin watch is loosing Bluetooth connection on Android 13

Yesyerday my Pixel phone updated to Android 13 and I noticed the 2-nd time that it lost connection with the watch. Is this a google bug or a garmin bug?

Top Replies

Garmin-Kevin over 2 years ago in reply to floppyrom +1 verified

Please use caution when clicking any links, as this does violate our terms of use. We understand that some links may be helpful to the community, so we hesitate to delete all links that are posted. We…
Garmin-Kevin over 2 years ago +1 verified
All-

Thank you for your participation in this forum thread. So that I may assist you further, if you are having Bluetooth trouble with your Forerunner 245/245 Music, please reply with the following:
…
floppyrom over 2 years ago +5

Issue is tracked here: https://issuetracker.google.com/issues/242755161?pli=1
mmmotors over 2 years ago +5

An Android patch is out - claims to help resolve Bluetooth issues - hopefully this helps. It hasn't been pushed to my P5 at this exact moment, but if this helps anyone, sound off and let us know:

…
floppyrom over 2 years ago +4

It's all probably related to the new Bluetooth stack from Android 13 https://www.reddit.com/r/Android/comments/wwo4ld/android_is_using_a_new_bluetooth_stack_for/

All Replies

0 3031720 over 2 years ago

Same issue here with forerunner 955 and Pixel 6 on Android 12. Connection loop after the Smartphone switches from 5ghz wifi to 2.4ghz.

0 bhwilkins over 2 years ago in reply to CanoeBeyond

Google owns Fitbit.

0 Jason S. over 2 years ago

I just updated my Pixel 5 to Android 13, and started having issues with my Epix 2 getting disconnected and refusing to reconnect. In my case, not using the phone as a key (PAAK) features for my car seem to stop this from happening.

0 Mindas, O Bardina over 2 years ago in reply to Jason S.

Same here.

0 ipowyourface over 2 years ago

This happens when you upgrade Android OS. For some reason, the OS doesn't remember your Garmin device correctly.

To fix this, just open up Garmin Connect, go into the menu then go to Garmin Devices. Click on your watch, then at the top right press the three dots, then press on "Remove Device". After this just pair up your watch to your phone like you did when you first paired it, and you won't have anymore issues.

0 GrenWW over 2 years ago in reply to ipowyourface

Doesn't work. That was the first thing I tried.

0 ipowyourface over 2 years ago in reply to GrenWW

Strange, that's what fixed it for me when I updated to 13.

0 Jason S. over 2 years ago in reply to ipowyourface

Same, I also removed and re-paired my device, but it still gets dropped/blocked after using my PAAK. I've noticed a few of these threads around, and it seems like a Android 13 must have some sort of Bluetooth bugs (not just with Garmin). It is good to capture information here though, as I'm sure more and more people are starting to encounter these issues.

0 floppyrom over 2 years ago

It's all probably related to the new Bluetooth stack from Android 13 https://www.reddit.com/r/Android/comments/wwo4ld/android_is_using_a_new_bluetooth_stack_for/

0 floppyrom over 2 years ago

Issue is tracked here: https://issuetracker.google.com/issues/242755161?pli=1