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

Update Bluetooth Connection in Connect Mobile for Android

Starting with the 3.11 release of Garmin Connect Mobile for Android, we have introduced an option to update the Bluetooth connection from within the Connect Mobile application to use the native Android Bluetooth system pairing. For instructions on updating please see the link listed here.

Please feel free to leave feedback in this thread.
  • Yep my FR235 seemed to have lost it's bluetooth connection with the app. The bluetooth settings on the phone (S7) shows the forerunner 235 is an available device but I can't seem to pair it with the app when I try adding the device, something has changed with GCM v4.
  • Update: Yesterday I rolled back to 3.20.3 and got things paired up. Today I see I have had an automatic update to 4.0.5 (was 4.0 prior to yesterday). I have not tried to re-pair under 4.0.5 but at least the BT connection is working, I can sync and I'm getting alerts. It still appears to have the issue of not reconnecting after going out of range but synced up again when I tapped the sync icon in the app.
  • I've got GCM 4.0.5 installed and still can not re-pair my watch with my phone. The Garmin QA team must of been on holiday when they decided to release this v4 update :confused:
  • Finally, I was able to re-pair my FR235 to my phone after I did a network reset on the phone. :D
  • Former Member
    0 Former Member over 7 years ago
    I updated my Fenix 3 HR to version 4.50 and I have some issues with updating by Garmin Connect on Android. I get the answer "There was a problem communicating to your Garmin device". I can't change watch faces...so on. Anybody else met the same issues?
  • The last update (4.0.5) was issued after some interaction with support. Perhaps it's coincidence. But the main part - the problems still growing! Along with the GCM update, the update for FR935 (6.10) was issued. And that is the disaster! Apart it doesn't reconnect the lost connection otherwise than remove and pair back the device, it is no longer possible to correctly reconnect with the stable 3.20.3! And that is the main problem.

    With update FR935 to 6.10 version along with old GCM 3.20.3 the connection restore itself, but it does not communicate: no sync, no installed Connect IQ apps visible, etc.

    It's really frustrating. I don't know if the other platforms (iOS, Win) have such issues, but garmin developers really continue cripple the working software. We all bought one of the most expensive devices on the market and can't properly use it. Seems like developer team use us as beta-testers while roll out the not stable and not fully working releases. Also the is no way to quick communicate with support in order to address the grow in number problems. The response from support - usually standard canned - coming in about 3 days, not to mention delay with another more crippled release. And in that time we should live with cripple product. I start think that I made a serious mistake buying the garmin product. Such problem could be excusable for the pebble team (but they had no such! I used the pebble for years before), but not for garmin.
  • Pairing issue Android 7


    I've had the same problem since updating the same phone to Android 7. My phone, however, will not pair to my 520 at all.


    I have the same problem....the solutions suggested by Garmin do not work either
  • Former Member
    0 Former Member over 7 years ago
    So for my problem - I've wiped cache partition on my mobile and I was able to pair and sync. Jumping up and down did not last too long, after a few minutes all was back to normal - disconnected state. I will try it again tomorrow, with different versions of GCM and Fenix 3 FW. Maybe I will find the working combination.
    EDIT: Regional Garmin support is keep telling me that the problem was with Android 7 since beginning. and the issue is very unlikely to be solved from Garmin side. Which is actually driving me nuts. This is one the issues that really makes me rethink to buy any garmin device in the future.
  • Today I received the reply from Garmin support (after about a week). They said, that my phone is not in the list of compatible phones for Garmin. At first I didn't believed that I read this laughable reply. So, basically they told me, that after they upgraded the software, my phone is no more use for the brilliant software development.

    I have no words to express my feelings over this "dream team".
  • My phones have never been on the compatible list and they've been rock solid. What's your phone anyway?