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

Forerunner 920XT issues - GCM hanging and Re-pairing required with pin

Hi guys

Hopefully support read this forum so it is a useful post and also to hear from others with similar problems

My setup
GCM 2.5.2
FR920XT (firmware 2.5)
Android 4.4.4
Sony Xperia Z1 Compact

Issue #1 sync hang

Had a lot of hanging when the forerunner is syncing.. in the image you see that the sync is hanging half way through. Once it hangs nothing to do but try and crash it (usually by turning off bluetooth on phone)
I think I have found a work around (think).. which is to leave GCM using the back buttons (repeated until it takes me back to the home screen) rather than use the home screen button.

Issue #2 re-pairing with pin
This is the real biggy
Several times a day I go out of range of the phone. When I do the connection is lost and the only way I can get it to re-establish the connection is through re-pairing using the pin.
If it was a 'click here to reconnect' button it would be fine.. but the whole thing means I need to ..
a. pull down the notifications bar from the top and click on the Yes to connect request (when the phone spots a request)
b. pull down the notification bar from the top again and this time go through the re-pairing process by entering the pin showing on the watch.

It is seriously taking away from my 920XT experience

Things to note
1. I am a long term Garmin user and have used GCM/bluetooth with my Edge 810, Vivofit and FR620 (the 620 could be fussy and not always connect, but usually worked)
2. I have tried the usual..

Turn on turn off Bluetooth
Turn on turn off phone
Remove device and re-pair
Uninstall and reinstall GCM

Would love to hear if this is a known issue that others are experiencing and if Garmin are working on some fix

To garmin.. really don't mind being a tester.. been with you guys since the FR301 :-)

0 Former Member over 10 years ago

I have to say that my experiences after a week or ownership is exactly the same as most here (Nexus 5 with Lolipop).

Various things will *fix* it temporarily:
1) Turn Bluetooth off and on again (on the phone) - I always get an immediate "re-pair" message.
2) Switch "Airplane mode" on-off (on the the phone) - Same effect as above.
3) Reboot the watch - This often just fixes the issue without a "re-pair" prompt on the phone.

Interesting: I don't even get prompted for a pairing code, it always just connects and sync (when it works). I am prompted for the security code, but this is just to configure the Bluetooth security override function in Android, you don't *need* to do it.

This Bluetooth pain (which was reported many, many months ago by DCRainmaker interestingly), renders the "smart watch" features of the watch virtually useless. It also means more effort to get "live tracking" working before setting off. Plus it heavily impacts on how often your data gets sync'd (steps and calories), so also impacts on those features and functions.

I see reports of this across all makes of devices and OS's (Android and iOS), so it seems like it must be related to the watch firmware (although it's never that simple!).

0 mathblais over 10 years ago

So did anyone get the re-pairing fixed by any means?
I replaced my s4 mini (that worked) for a newer Xperia Z3

I don't use watch for notifications that much, but just hate the fact I got to re-pair it constantly

0 rastikw over 10 years ago

I did, using latest GCM. I'm using Xperia Z1c.

0 Former Member over 10 years ago

I'm getting these problems with a 920xt and a Xperia Z3 Compact.

I get a pairing request when I come back into range of the phone. This pairs okay with Bluetooth on the phone as the 920 shows up in the Bluetooth list of devices. GCM sometimes picks this up and starts to use it. Other times it refuses point blank to recognise the device is connected. I've almost got used to the constant pairing requests but the fact that GCM won't work when the pairing is sorted is a real pain.

I've had the 920xt since Christmas and I really like it as a device but I have to say the Bluetooth connectivity issues really take the smart out of smart watch. It's not a show stopper for me but does limit the usefulness of some of the great features.

0 Garmin-Patrick over 10 years ago

Hi Everyone - We have an update coming in February that should improve Bluetooth compatibility/stability for the 920XT. Sorry for the trouble!

0 milkywaye over 10 years ago

Hi Everyone - We have an update coming in February that should improve Bluetooth compatibility/stability for the 920XT. Sorry for the trouble!

That is great news!
It is really starting to drive me nuts

0 figgeo over 10 years ago

Hi Everyone - We have an update coming in February that should improve Bluetooth compatibility/stability for the 920XT. Sorry for the trouble!

Is that update based on the 2.64 beta? If so the problem still remains.

0 Dr Phil over 10 years ago

I see reports of this across all makes of devices and OS's (Android and iOS), so it seems like it must be related to the watch firmware (although it's never that simple!).

it is mostly related to Android and Android devices. There are few complaints from users with iOS devices and then they appear to be usually due to user error. Granted there are some faulty devices out there, but the problem for Garmin with Android are the many versions and adaptations of Android and types of Bluetooth hardware in the Android based phones.

Still, the impending release of an update may go someway to alleviate some of those issues for some.

0 Former Member over 10 years ago

Good news that an update is on its way.

I ususally get a repairing request when I come back in range of my phone. This connects the Bluetooth okay, but GCM usually refuses to play. I'm fairly new to the Android ecosystem and have now discovered that if I close the app by swiping it away didn't work. However once closed in this way if I find the app in the Settings -> Apps and force it to stop and then restart the app, GCM ususally connects.

0 Garmin-Patrick over 10 years ago

Is that update based on the 2.64 beta? If so the problem still remains.

No, it is not.