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

Fenix 2; Garmin Connect Mobile Android 3.10; Device registration failed. OTHER_FATAL

Former Member over 8 years ago

Hi All,

I've got a fenix 2 with the latest fw: 4.50, and I want to sync the watch with my OnePlus 3 using the Garmin Connect Mobile Android app (version 3.10).

So everything goes ok, up until step 4 of "Setting up device...". After successfully reading the device identification file, the device registration failed. OTHER_FATAL?

Can somebody explain to me how this works... The watch will actually get registered and sync through Garmin Express on my Mac though.

I can reproduce the situation after:
- using a different Android device (Samsung Galaxy Tab S)
- switching from WiFi to LTE
- rebooting the watch
- rebooting the phone
- factory reset of the watch
- switching the timezone's (now back at auto timezone)
- reinstalling the Garmin Connect app on my phone
- turning off bluetooth, and let the app notify me to switch bluetooth on (although this probably has nothing to do with the registration problem...)

Does somebody know what to do? Running out of options here. Seems to be a Garmin service side issue?

I'm almost giving up, and switching towards a Polar M600 over this problem.

Regards

0 Bit over 8 years ago

I wouldn't quite phrase it the same.. but I feel your pain.
Just opened a case with Garmin Support.

Edit: version 3.4.1.1 works. It doesn't show the "an error occurred" popup as often as 3.3.2 and displays most notifications most of the time, it's a bit flaky though.
I guess that all versions < 3.10 work, the higher versions probably better, but personally I prefer versions < 3.5.
Installing of old versions downloaded somewhere is not without risks of course, you can never be completely sure of what's in them.

0 Former Member over 8 years ago

I also get the Device registration failed, OTHER_FATAL with the Fenix and GCM 3.10. Haven't reported it yet, doing so now.

You'd have to download an old APK somehwere and install that. Version 3.4 works with Fenix 1 and 2 but not Fenix 3. Beware though, changes in the Connect servers can make old app versions dysfunctional, there is no guarantee they will keep working.

Edit: Just checked if version 3.3 still works with a Fenix (not tested Fenix 2 yet). It pairs, it connects, it syncs activities, but notifications do not work (an to make sure, even on Android 4.4.2, location services are on and notification access granted).

Some notifications work, most don't. GCM 3.3 displays "Error" popups very often. It's not worth the effort of installing the old APK.

Thank you for advice. It really working. With new version Garmin connected planty time tried synchronised fenix2 but all them were unsuccessful.
When download old apk file "Garmin connect" -everything is working without any remarks.

0 Former Member over 8 years ago

GCM 3.4 work fine in fenix2
best reggards

0 Former Member over 8 years ago

I was having the same problem with pairing my f2 to a replacement Note 7. The GCM 3.4 at freeapk had some kind of error. I ended up downloading 3.3 from here:

http://www.apkmirror.com/apk/garmin/garmin-connect-mobile/garmin-connect-mobile-3-3-2-release/garmin-connect-mobile-3-3-2-android-apk-download/

It installed and I was able to finally pair my f2 and sync the ride from today. I just checked the Play Store and GCM is linked and the Store indicates that an update is available.

Thank you very much to those of you that posted this solution! I did not want to download over USB.

0 jhs.bdn over 8 years ago

Ok,thanks for the solution,but....

Isn't Garmin going to do anything? Really?,

0 Bit over 8 years ago

They are more likely to solve this if more people raise incidents with Garmin Support. As far as I know Garmin only rarely read/respond on this forum, so please all Fenix / Fenix 2 users, contact Garmin support so that they become aware of the impact of this problem.

0 houstonrj over 8 years ago

Agreed to the need to open more tickets. In addition I also emailed the email address listed on the GCM app page on the play store. No reply, but maybe someone read it.

I also downgraded to v 3.3 and am now able to connect and sync again. Turned off auto-updating for the app since Garmin likes to break things.

0 Former Member over 8 years ago

This was garmins response but i cant seem to get it to work.

Thank you for contacting Garmin International.

The new version of Connect Mobile on Anrdoid will not pair with the fenix 2 in the same way. You will need to pair to the phone and then to Connect.
1. Power the device on
2. Press and Hold the Menu or Action button
3. Select Settings
4. Select Bluetooth
5. Select Pair Mobile Device
6. Open the Settings on the Android device
7. Open the Bluetooth setting
8. Touch the Garmin Device
9. Type in the passkey displayed on the watch and confirm the pairing request
10. Press Done when the pairing complete message appear
11. Open the Garmin Connect Mobile application
12. Open the app menu (3 horizontal lines)
13. Touch Garmin Devices
14. Touch the Garmin Device
15. If requested, type in the passkey displayed on the watch and confirm the pairing request
16. Press Done when the pairing complete message appears

With Best Regards,
Nathan
Customer Care - Outdoor Team
Garmin International
913-397-8200
800-800-1020
913-440-8280 (Fax) Att: Laurie 8996211
www.garmin.com

0 Bit over 8 years ago

Thanks ! I got the Fenix 2 paired with GCM 3.10 on a tablet running Android 5.0 with this procedure.
No success yet with original Fenix and Android 4.4, but will retry later today.

0 Former Member over 8 years ago

Same issues here

I've also been having the exact same issues. I sent in a support ticket last weekend. It of course took them 6 days to respond to my email, then another 2 days to respond again. So far I've just gotten generic copy pasta responses telling me to make sure location services etc are turned on and that everything is updated. I wish they had gotten past all of that in the first email. I'm sending them a new email linking this thread so they can see that it is a common issue.

Downgrading Garmin Connect Mobile to 3.3 worked for me.