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

bluetooth connection (again, and again, and again)

Former Member
Former Member
And again, my watch and phone stopped talking to each other. Nothing changed on either. First step, check if there is an update for the phone app. Yes there is. Update app. Straight after - phone finds watch and watch shows bluetooth connection key. Hooray! But unfortunately, next day - no connection (NOTHING CHANGED ON PHONE OR WATCH). Tried almost everything - uninstalled app from phone, reinstalled - no find. Connect watch to laptop - updated Garmin Express, try to reconnect to phone - no joy.

I really like the watch, but this connection issue is driving me up the wall. I've been looking at all the competition but none of them tick the same boxes as the FR235. APART FROM THIS CONNECTION PROBLEM.

Please please GARMIN sort this out. Garmin must be seeing this forum and know that it is a recurring issue.

Watch: FR 235 version 7.80 (867f440) Bluetooth 2.40 Connect IQ 1.4.5
Phone: Samsung A3 (2017) SM-A320FL Android version 8.0.0
Connect version 4.10 build code 4050
  • Thanks hpaixao. I tried v4.8, and it looks a bit more stable indeed. Unfortunately though I still have to disable/enable BT quite often after my phone has been out of reach. So it didn't fully fix the issue for me. Hopefully Garmin can get this fixed at some point.
  • Thanks hpaixao. I tried v4.8, and it looks a bit more stable indeed. Unfortunately though I still have to disable/enable BT quite often after my phone has been out of reach. So it didn't fully fix the issue for me. Hopefully Garmin can get this fixed at some point.


    Sorry didn't help you... unfortunally like i said, the version 4.8 in my case have justo put my bluetooth connection more stable, but didn't solve me the problem too.
    I have maybe 2 or 3 times per day to kill the System Process "Bluetooth share" and enable again the bluetooth.
    By the way, whats your Android Version?! Android Nougat 7.0?!
  • Yes, I'm using 7.0 on the Moto G5 Plus. They say Oreo 8.0 will have some BT improvements. I'll see if that one improves this (if it will be released at some point for my Moto G).
  • Former Member
    0 Former Member over 6 years ago
    Anyone have figured out any resolution for this!?


    I've had same last 48 hours.
    I think issue is with watch rather than phone. Phone seems connect to my car ok.
    Any suggestions welcome.
  • I've had same last 48 hours.
    I think issue is with watch rather than phone. Phone seems connect to my car ok.
    Any suggestions welcome.


    My phone connect's too very well to my car, without any issue.
    For me it's a mix of issues: Watch and Garmin Connect Mobile. For example, I have problem with my watch and with my Edge 820.

    Yesterday has been released a new Beta Version for 235 with the change log: Minor improvements related to Bluetooth smartphone connections.
    Maybe this could be the fix... hope so!
  • I installed the 7.81 beta, but unfortunately that didn't fix the BT-issue for me. I get to the "enter pincode", and then it keeps trying to establish the connection (same as before)
  • I installed the 7.81 beta, but unfortunately that didn't fix the BT-issue for me. I get to the "enter pincode", and then it keeps trying to establish the connection (same as before)


    What version of Garmin connect Mobile are you using?
  • I have installed the 7.81 beta version and decide to update the GCM to 4.12.3 and the bluetooth connection was horrible.
    after that I decided do go back to GCM 4.8 with the beta version on the watch and the thigth are stable.
    With this, I'm convinced that the problem is with the Garmin Connect Mobile, that for some reason don't work well on the new versions
  • Okay, update from my side. Several days ago I finally got the Oreo 8.1 update for my Moto G5 Plus. And I must say, all works perfectly now! :). Always perfectly reconnecting after the phone has been brought into reach again. Not failed a single time. Seems the Android update really fixed the issue here.
  • What version of Garmin connect Mobile are you using?


    4.12.3