Hi. After the upgrade of my Asus Zenofone 3 ZE520KL to Nougat, Garmin connect has issues in reconnecting my device when I go far from the phone and I go back. Until I'm near the phone all is ok and notifications are perfect. When i go out for a while and then come back near the phone I must open the app and wait 30 seconds until the app reconnect my Garmin or restart my phone. With Android 6 I had no problems so I think the issue is with Nougat. If my garmin is non connected and I switch on my Bluetooth headphones they work perfectly. I don't think is my bluetooth stack issue but something in the software. Thanks
Have you tried updating your Bluetooth connection, as described in the sticky thread in this forum? This may have fixed the issue for me.
I was also having problems with Bluetooth not automatically reconnecting when taking my watch out of range of my smartphone and back into range again.
To reconnect, I have had to open Garmin Devices in Connect Mobile and wait.
Garmin device: Forerunner 630, Software Version 7.10, Bluetooth/ANT 2.40.
Android device: LG Google Nexus 5x, Android 7.1.2 Beta (build NPG47I).
Connect Mobile: version 3.16
The fact that I am running a beta version of Nougat means I'm wasn't totally surprised that there were issues.
Hello,
I have a Fenix 3 HR (firmware 4.20) and an Asus ZE520KL with Android 7.0.
Until last week my phone was an Android 6. I update it to Nougat and since my Fenix 3 HR can't reconnect automaticaly when I loose connection and return close to my phone.
As last week I upgrade my Phone and my Garmin connect throught Goolge Play, I suspect the new version of GCM 3.16.
I uninstall it and revert to GCM 3.15. But thee issue still persist.
So I upgrade to GCM 3.16.
I force in GCM > Settings >Help connection > Device Connection aid = enable
But it doesn't resolve this issue.
I check GCM is granted to "automatic start management"
But it doesn't resolve this issue.
I read the sticky post about connection issue, but it doesn't help.
The only thing I can do when it is not reconnecting automatically (every time I loose conenction!), is to stop Bluetooth and restart Bluetooth, the Fenis 3 HR will reconnect in the minute after ...
Hello,
I have a Fenix 3 HR and a Asus ZE520KL phone. Until last week I was with Android 6 and GCM 3.15 and everything works fine for the notifications :
Even if my watch and my phone were disconnected, they reconnected in Bluetooth Automatically.
I upgrade my Asus ZE5230KL to Andoid 7 Nougat, and GCM 3.16, and since, my Fenix 3 HR and my phone can’t reconnect automatically when they loose connection one time.
It’s impossible to reconnect without stopping the Bluetooth on phone and restarting it. It’s a now a nightmare to have notification.
I uninstall GCM 3.16 and reinstall GCM 3.15 with old apk but it doesn’t resolve the issue.
I update to GCM 3.16 repairring my watch and force in Setting>Connction Helper>Device connection Aid to enable, but it doesn”t resolve the issue.
I check GCM is granted to start automatically in the “Automatic starter manager”, it doesn’t resolve the issue.
I read the sticky post about BT connection issue, but it doesn’t help.
The only way is to stop and restart the bluetooh on my phone…
I posted an email to the dev team no reply. I'm having issues with my VivoActive HR+ The issue started with Nougat and I suspect it's something to do with power savings. I have in fact tried the repairing and it works until you get out of range again. I usually have to try several times to get it to pair - almost like Bluetooth is being sluggish.
Have you tried updating your Bluetooth connection, as described in the sticky thread in this forum? This may have fixed the issue for me.
I was also having problems with Bluetooth not automatically reconnecting when taking my watch out of range of my smartphone and back into range again.
To reconnect, I have had to open Garmin Devices in Connect Mobile and wait.
Garmin device: Forerunner 630, Software Version 7.10, Bluetooth/ANT 2.40.
Android device: LG Google Nexus 5x, Android 7.1.2 Beta (build NPG47I).
Connect Mobile: version 3.16
The fact that I am running a beta version of Nougat means I'm wasn't totally surprised that there were issues.
Yes...but it asks for a PIN CODE that I don't know
Yes...but it asks for a PIN CODE that I don't know
Are you following directions?
First add the device and when it says to pair the device you need to put the watch into pairing mode.
When the phone finds the watch the watch will post a pin code that you need to enter to proceed.
Not sure why they require the pincode - most BT devices use a default like 0000 or nothing at all.
Garmin seems to be a little overboard with "security" - like having to enter a captcha every single time you post. Not enough that you're logged on or have the watch and phone in your possession - they gotta have some input.
When the phone finds the watch the watch will post a pin code that you need to enter to proceed.
To be able to read the PIN number on the band's screen I had to take off my band and prop it up next to my android. The screen on the band is minuscule for purposes like this.
