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 mmmotors over 2 years ago

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:

support.google.com/.../google-pixel-update-september-2022

0 6987991 over 2 years ago in reply to mmmotors

Thank you very much, going to try on my Pixel 4a straight away if already available

0 6987991 over 2 years ago in reply to 6987991

Unfortunately, that didn't fix it for me either

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

This patch installed on my Pixel 5 last night.. So far, it does appear to be better. Will report back later in the week if this has fixed my particular scenario.

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

Nope, I'm already seeing similar failures. Will try to collect ADB logs and report to the Android development forums.

0 bhwilkins over 2 years ago

I finally bit the bullet and erased my network info. It fixed it for me. (As stated in another comment, I had already installed the September "5th" update and that alo e didn't work.)

Clear your network settings

Open your phone's Settings app.

Tap System, then Reset options.

Select Reset Wi-Fi, mobile & Bluetooth.

After the reset is complete, try and repair your watch and phone.

0 floppyrom over 2 years ago in reply to bhwilkins

This won't fix it as we're talking about a core Android 13 bug. So far the issue seems to be fixed using the Android 13 update from a few days ago.

0 bhwilkins over 2 years ago in reply to floppyrom

The "Sept 5th" update didn't fix my phone. I had to erase all of the radio info too. Read above to find several others who also didn't experience your claim.

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

That seems a little heavy handed.. Was this discussed in one of the google developer threads? Do you have a reference as to why resetting all WiFi/Mobile/Bluetooth information would help?

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

I was extremely hesitant to try it too. I hate that you lose all of your info that is supposed to be backed up, but a guy at my carrier told me I should do it, and it immediately did it. That text was copied directly from a Google chat gone dead reply email telling me the same generic thing.

It's surprising and disappointing how often this has been required to fix issues with my Android/Google devices.