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

Garmin connect causing bluetooth issues on samsung phone

RubenAneca
over 1 year ago

Since the latest update on my forerunner 255, garmin connect doesn't synchronise well with my phone. It can be paired, but the last step: synchronisation doesn't work. Most of the times it only synchronises once after starting up my phone, then the connection is lost. Workouts won't upload anymore and I cannot see live data from my forerunner, the synchronisation keeps hanging. Aside from that, other bluetooth devices (for instance in-ears, or laptop, sound device ...) also cannot couple to my phone when garmin connect is installed, even if they are already paired. The devices cannot find my phone's bluetooth. Had contact with garmin but they keep sending me random links to try standard issues, nothing helped. When garmin connect is removed, all bluetooth devices work fine. 

  • 0 over 1 year ago in reply to stevebrophy

    Thanks - I'll give those workarounds a go.

  • 0 over 1 year ago in reply to trux
    trux said:
    What brought you to this conclusion?

    Well if I turn my Garmin 255 off and don't use it, then I have no issues at all with my phone connecting to any of my bluetooth devices, from ear buds to Bluetooth midi devices.  But once I turn on my Garmin and manage to connect to my phone, then it usually disconnects pretty soon on its own, and then I have all sorts of issues connecting to my other devices as well as my garmin, and end up having to turn off the phone or try force closing bluetooth.  So it's definitely the garmin device or garmin connect that is causing the issues.

    I never had any problems with my phone before I purchased and starting using my 255.  Also it's got much worse after the latest Garmin update.

    That's why it's a Garmin issue.  I appreciate that with so many Android devices that it more difficult for developers to get apps to place nicely with each other, as compared to iOS, but it is Garmin's responsibilty to check and sort out any issues that arise.

  • 0 over 1 year ago in reply to therunningdad
    therunningdad said:
    But once I turn on my Garmin and manage to connect to my phone, then it usually disconnects pretty soon on its own, and then I have all sorts of issues connecting to my other devices as well as my garmin, and end up having to turn off the phone or try force closing bluetooth.  So it's definitely the garmin device or garmin connect that is causing the issues.

    It still does not explain why it does not happen to everyone using Garmin Connect, or the same watch. It means, very probably, there is still something wrong on the phone. 

    therunningdad said:
    it is Garmin's responsibilty to check and sort out any issues that arise.

    Well, certainly, but you can tell absolutely the same about Samsung.

    BTW, did you already try disabling Wi-Fi on the phone, and reset the Network, as advised earlier in this thread, and in the Sync / Connection Troubleshooting Guide? It did help some of the concerned Samsung phone users.

  • 0 over 1 year ago in reply to stevebrophy

    This is an interesting thing. Turning phone in airplane mode and off works with me, so i'm already a bit happy with this. Thanks! Definitely some good feedback to give to garmin as well.

  • 0 over 1 year ago in reply to RubenAneca

    I had the same problem with Samsung Galaxy A41 and Fenix 7S. Really annoying. At least, turning airplane mode on and off helped me as well. But I do not think it would be the solution.

    However, I found an interesting thing in the GC app: in Sync History I found lots of sync attempts, and most of them were a failure.

    Overall Sync Status=FAILURE
    Overall Reason=DEVICE_FAILED_TRANSFER: Read failed: Device internal error path 0:/garmin/fbtptdbackup/ptd_bkup.fit, code -5, source 4.

    Etc.

    Maybe, it worths a try to check out if you guys has the same in this sync history.

    What if that is the reason behind the multiple disconnects, because a number of unsuccessful attempts of bluetooth sync of the backup it automatically disconnects?