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

FR 255 un-pairs from Garmin Connect

5601726
over 2 years ago

I have a nice new ForeRunner 255, that is driving me crazy.  It will not stay pared with Samsung A32 phone.  I've been on chats with Garmin support, and they even sent me a new watch that behaves exactly the same as the previous one.  It disappears from the top of Garmin Connect, and when I go look under "Garmin Devices", the FR255 shows as "Registered to Garmin Connect" but is not paired.  Then I have to go through the whole pairing procedure like it is a new device.  This is a pain, and unacceptable for a brand new $500C device.

I have just discovered that turning on my Garmin Edge 530 so it connects to GC, makes the FR255 un-pair.  The Edge 530 never seems to un-pair.

I had posted this previously in one of the many threads about Forerunners losing pairing with phones, and Garmin e-mailed me to start a new thread, so here it is:

"My 255 keeps disappearing from  Garmin Connect, and I have to go through the whole add new device pairing routine repeatedly.  Garmin support sent me a new watch, but it does the same thing.  I've updated the watch, Garmin Connect,  deleted and re-added all my network connections on my phone, etc, etc. Android 12, Samsung A32.

There are threads about this on other Garmin watches going back years, with huge lists of time consuming things to do, none of which are a definitive solution.  My Garmin Edge 530 bike computer has always stayed connected, and my old Amazfit watch was connected to several phones for years without an issue.  There is something wrong with Garmin's watch firmware.

I like Garmin Connect when it works, and it is very good to have my bike computer and running watch rolled up in the same app, but I am very tired of the disconnects and no solutions from Garmin support.  I'm thinking of sending the 255 back before the 30 day free return period is over, and trying a Coros."

I have tried an awful lot of the suggestions at the top of this thread.  I have also updated the 255 to the Beta software version 12.27.  I thought deleting all the networks from my phone, and then building up the WiFi and Bluetooth pairing all over, worked, but now I've found just starting my Edge 530 (up to date firmware) kicks my Forerunner off Garmin Connect, and I have to again do the whole re-pairing procedure. 

There are dozens of threads in these Garmin Forums about Garmin watchs un-pairing from Garmin Connect, going back years.  There is obviously a fundamental issue that all their time consuming suggested "fixes" do nothing to address.  The support people on their chat don't have a clue.  It's like it's a new problem they've never heard of, and they have no idea of how to fix it.

Some other recent threads describing the same problem:

https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-mobile-andriod/307085/fenix-6-pro-constantly-disappears-from-garmin-connect--/1503100#1503100

https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-mobile-andriod/287205/why-does-my-watch-frequently-unpair?pifragment-1286=2#1387050

forums.garmin.com/.../1387050

  • 0 over 2 years ago

    For the fix, look at the very last post from Garmin-Eiliko in this thread: Repeated bluetooth pairing codes after disconnecting watch - Garmin Connect Mobile Android - Mobile Apps & Web - Garmin Forums

    In brief, you need to update your Samsung phone - Samsung released a patch addressing the issue.

  • 0 over 2 years ago in reply to trux

    Thanks for the input, but my SS A32 is up to date, there are no patches available.  Last software update was Sept. 16, 2022, and when I search for updates it says the phone is up to date.

  • 0 over 2 years ago in reply to 5601726

    Wow, that is a huge thread with hundreds of people with the same problem.  I guess closing the thread fixed the problem... not!

  • 0 over 2 years ago in reply to 5601726
    5601726 said:
    Thanks for the input, but my SS A32 is up to date, there are no patches available.

    In that case, I suggest contacting Samsung, and asking them whether a patch for your model will be available too.

  • 0 over 2 years ago in reply to trux

    They were about as helpful as expected, re-set networks (done before, no effect); re-set entire phone.  Guess I'll try it, serious pain in the ass, and I suspect it won't make any difference either.

  • 0 over 2 years ago in reply to 5601726

    I'm cautiously optimistic it is actually fixed!  Factory re-set of the phone seems to have allowed the patch to function. The FR255 watch has not un-paired for 3 days, even after adding my Edge 530 back on.  I did pair the FR255 first this time, not sure if that makes any difference.

    Backing-up my phone to the SD card before the re-set made it somewhat less painful than the Google back-up I've used before, but there is still a lot of time required to get the phone back to where it was, more or less. 

    It would be nice if the Garmin/Samsung patch was mentioned right at the top in the "Sync / Connection Troubleshooting Guide" in this forum, and if the Garmin support people knew about it.  There are a lot of people with SS phones.  Weeks of chatting to support, searching the forums and web, and trying a hundred ineffective "cures" first tends to wear a person down.

    I really hope the patch and phone re-set has actually fixed the problem, I really like most aspects of the watch and Garmin Connect.

    Thanks for your help trux!

  • 0 over 2 years ago in reply to 5601726

    Of course hours after I type that, the bloody thing un-pairs again.  I used my Edge 530 today, and that seems to do something to the FR255 pairing.  The FR255 is again registered, but not paired, and the entertainment value of Garmin's convoluted pairing routine has lost it's novelty.  As much as I like having my bicycle computer and running watch feeding into  Garmin Connect, the hassle isn't worth it with a $500C device.  I've spent way too many hours trying to fix this problem.  This thing is going back.

  • 0 over 2 years ago in reply to 5601726

    One week into owning a Coros Pace 2.  The Coros pairing routine is very quick and painless:  scan a QR code that comes up on the watch, done. And so far at least, it has never unpaired from my Samsung A32.  Coros has over-the-air firmware updates that don't require having a Windows or Apple computer running yet another app like Garmin does, I only have Linux and my wife's Chromebook.  The Pace 2 is $180C less than the FR255, and a lot less trouble. 

    I do miss the Garmin app with my bike computer tied to it as well, but Garmin really needs to improve the basic functionality of their watches.  Garmin support was useless.  The sticky list in this forum of 50 things to do to solve pairing problems is very time consuming, and doesn't ever fix the problem. 

    A very poor experience all the way around.