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

[SOLVED] Android and Garmin Connect Mobile failing to synch F3 after V 4.3 FW update

Former Member
Former Member
I've spent the whole morning, no kidding at least 4 hours, trying to understand why, after the hard reset following 4.3 FW upgrade of my F3, my phone was unable to register my F3 on Garmin Connect Mobile.

With the Hard Reset (due to the restarting loop) all data was lost so I first had to go through the main settings and the NAV points. Luckily all data depending on Garmin Connect are stored online and retransferred to the F3 via Garmin Express.
However, since the Wi-Fi and Bluetooth settings were also lost, I basically had to start ALL the configuration from scratch and I got jammed, literally, at trying to understand WHY the F3 was no longer visible on the GCM phone app (Samsung S3 Neo).

My ordeal is here.

There is definitely a bug in GCM right now and your phone might very often lose the WI-FI connection as you try to fix the issue. Without connection to GC, GCM can't operate so keep that in mind. It's not a problem of routers, wireless or internet connection (youtube all the way in the background here). So GCM messes up both the BT and WiFi.

If you find the authentication FAILS on GC it's because of this connection problem caused by either GCM or 4.3 or both (but I think it's just GCM that needs an update).

Unpair F3 with phone.
Clear data (all data) on GCM... you might as well uninstall and reinstall it but clear the data first.
Turn off and on both the cell phone and the F3 (keep BT off for the moment).
Check your Garmin Connect Dashboard. In my case, the watch was not being loaded in the widget and this rang the bell.
Unregister your F3 from your Garmin Account.
Turn on the F3 and connect it to Garmin Express. Follow the procedure to re-register the watch to your account. Garmin will mail you congratulating for your new Fenix 3 (worst purchase of the year needs an extra congratulation)
Turn on BT on phone and F3.
Pair F3 with phone.
Go to GCM on your phone and you should see the F3 in the devices list, not connected (yet), this comes from Garmin COnnect itself. Check GC dashboard and you'll see the brand new F3 on your devices widget.
Sync the F3 on the phone, this means set the F3 to PAIR again.
At this point GCM will crash and they will ask you if you want to send a report. Do it. Tell them how much you love them.

You will not believe it but when you open GCM again you'll see the F3 is now paired.
Head for the settings.
Turn off and on both the phone and the F3.

And it's done... at least here and in my case.

Summary:
If you see in the GCM synch details Requesting device identification file failed it's because GCM has messed its state on GC (proceed to remove F3 from your devices and reinstate it via Garmin Express).
If you see instead OTHER_FATAL it's because your CONNECTED F3 also needs to be in PAIRING mode (it's the same you do when you pair it with the phone, set it in pairing mode when the GCM is synching).
  • Former Member
    0 Former Member over 9 years ago
    After 4.3 update and with 4.4 update now i always get "Requesting device identification file failed" error message when trying to pair Fenix 3 to garmin connect mobile application.
    If i ignore that message, device will though be connected to the garmin connect mobile,
    but it will never auto sync when connecting to garmin connect mobile again and it won't send me notifications until i call manual bluetooth sync (it also displays 0 subscribers in garmin connect mobile notification settings, after manual sync it will change to 1 subscriber)
    Unregistering device from garmin account does not help, reinstalling garmin connect mobile does not help too.

    Does anyone have the same issue? Maybe there is a way to mitigate that issue?



    Same problem here. V frustrating. .
  • Former Member
    0 Former Member over 9 years ago
    James please refer to formatting f3 thread in the main F3 forums. Post 1.
    Perhaps pix and videos will make it easier... do remember that the situation with gcm is volatile at the moment and changes day by day. If you can see your f3 connected on gcm don't touch anything and forget bluetooth for the moment otherwise follow the guidelines in that threafthread
  • Here's how I solved the issue. I did all this, so I'm not sure if all the steps are needed or not.

    - Erased everything from the Android phone about GCM.
    - Hard reset of the watch (I needed it anyway)
    - Registered the watch on Garmin Express
    - Turned on my iPhone and I paired it with the Fenix 3.
    - Back to GCM on Android phone. The Fenix 3 was there, but with no connection.
    - I WENT TO THE ANDROID BLUETOOTH OPTIONS (this is important, as you never had to do this before), AND PAIRED THE WATCH FROM THERE
    - Back to GCM, I could connect with the watch, install apps, reorder them and so on.

    If the watch gets disconnected, you need to do a manual sync in order to show the notifications again.

    Right now it's working, at least for now, until Garmin solves this mess.
  • Former Member
    0 Former Member over 9 years ago
    So far all notifications are working with this approach

    I have an HTC One M8. I just did the following:

    * Download and run Garmin Express on computer
    * Register the F3 in Garmin Express
    * Turn on bluetooth on both F3 and phone
    * Pair the F3 using the phones Bluetooth settings
    * Download and run Garmin Connect Mobile on phone
    * Select the F3 in GCM
    * Click pair in GCM and immediately click details
    * On the F3 go to Bluetooth settings and immediately if the phone says cannot get the device file then click Synchronize on the F3
    * Now the phone should immediately say paired
  • Former Member
    0 Former Member over 9 years ago
    To reconnect Fenix 3 with phone automatically after watch out-of-range or bluetooth off/on, you can use my free app for Android:

    https://play.google.com/store/apps/details?id=mabi.android.gcmrunner