I'm having issues right now with this.It worked flawlessly for months until a few days ago. If I "forget" the device from the bluetooth settings and add it back, it works until I get out of range,…
I have the same problem as Former Member. I've had the watch for over a year and initially Bluetooth connection with my Huawei P20 Pro was rock solid. You have to turn off the Android power management…
I've had a 645M connected to my Galaxy Note 8 (running Android 9) for 6 months with no issues.
Two days ago the 645M did an automatic software update to v6.50, now it looses connection and does not reconnect to the phone.
The only workaround is to remove it from the Garmin phone app and delete it from the phone's Bluetooth device list. Even then this only works once, and the process has to be repeated. I've tried all the same things listed on this post (and others) without success. Really frustrating as I use the smart notifications a lot.
Interested if others have the same problem with software update 6.50???
I'm having issues right now with this.It worked flawlessly for months until a few days ago. If I "forget" the device from the bluetooth settings and add it back, it works until I get out of range, then nothing again. No need to remove it from the GC app. Very frustrating.
I have the same problem as Former Member. I've had the watch for over a year and initially Bluetooth connection with my Huawei P20 Pro was rock solid. You have to turn off the Android power management etc but thereafter it worked really well. I would leave my phone at home for a run and a few minutes after returning the activity would sync.
A couple of months ago, however, it started losing the connection if the phone went out of range: it would rarely reconnect automatically.
The workaround I have found is to open the Connect app, turn off Bluetooth, wait a second or so for the red warning to come up in the app that Bluetooth is off and then turn Bluetooth back on again. A few seconds later, the app will find the watch again, reconnect and sync. It's a real pain though and sometimes I miss calls because I forget to check that the watch is repaired if I have gone out of range of the phone.
If I had to guess, I suspect this is a problem with Android or the Connect app, rather than the watch. If anybody has any suggestions for fixing this, please do post them here.
I have a similar problem but it started before v6.50. I suspect it is to do with either a sensor hub update (which happened at a similar time but Garmin never give a change log) or the Connect app or an update to Android.