FR220 Nexus 5 Android 6 GCM no longer Bluetooth pair/syncs

Fr 225

My Nexus 5 upgraded to Android M 6.0 two days ago, after the upgrade my FR225 will not sync with GCM. Tried removing device from GCM and re-pair, GCM cannot search and pair with watch, even phone itself's Bluetooth show it's paired with FR225. I have checked several threads in forum with similar issues, don't think the issue is isolated with specific watch.

Galaxy S4 issues...

I've had issues connecting my 220 to my Galaxy S4 for the last week. I've tried rebooting the phone and watch... still nothing. I removed the device from Garmin mobile and now I can't add it back via bluetooth. When I show details, it gives me a bunch of Connecting to device failed. messages.:confused:

I'm having similar issues with a new ForeRunner 25 on my Nexus 5.

I updated to Android before I got the watch. I can not get the watch to pair in the GCM app, however it will pair correctly through the bluetooth menu.

Luckily I have a Nexus 7 still running Android 5. GCM correctly paired in Android 5 and the watch can sync in GCM, etc. If you are on Android 6, better wait till an update is issued to fix this.

Workaround: After a lot of time I was able to get my FR25 working in Android 6. The only way this is possible was:
1) Connect and setup watch on Android 5 device (or PC but I didn't test this).
2) Open GCM on Android 6. The new device shows up, but says its not paired. Again, pairing in GCM always fails.
3) Using the Android bluetooth menu pair the FR25 to the phone.
4) Go into bluetooth "More Settings", click the gear icon next the the FR25 and say "Forget Device"
5) Go back to GCM -> Devices and try and refresh. After a while (1 to 2 min) GCM will automatically connect to the device.
6) If it still doesn't work, close GCM, start/stop the bluetooth receiver on the Nexus 5. Go back to set 5, repeat.
7) If still having trouble try and restart both the watch and phone, Go back to step 5, repeat.

So eventually I am able to get the FR25 to pair with my Nexus in the GCM app. The other option is just to use Garmin Express USB until there is a new GCM update with the fix.

Issue stays, with the latest GCM update 3.0, still cannot pair with watch on Android M.

Anyone still having issues pairing or staying connected with Android 6.0 should go into their Settings - Apps - Garmin Connect Mobile - Permissions and make sure that GPS is turned on. If you have been unable to pair, try pairing after this. Feel free to report any findings on this thread!

This will not work, I have all permissions turned on, including location.

Funny thing is, even with the recent GCM 3.0, and Forerunner 225 V2.5 update, the issue hasn't been resolved.

My Nexus 4 which runs on Android L. 5.1.1 just paired with my watch in less than 2 seconds.

Garmin support keeps telling me that I don't know how to pair the watch instead of looking into the issue further, in total denial.

Just to prove that I'm not hallucinating:
Nexus 4 L. 5.1.1 pairs in less than 2 secs, and yes I know how to pair it. Sorry for the Chinese, but you get the idea


Nexus 5 with Android M 6.0, nop, counts down to 0, search again, goes to 0 again, even watch gives up

Seems you folks should be complaining to your cell providers for breaking your phone.

THEY broke something that was built to their specs with the android update... Looks like they broke BLE. It is NOT a Garmin issue, as it works on Android 4 and 5...

If you go into Settings - About are you running build version MRA58K? If not, can you list the build you have?

MRA58K is the build.

Seems you folks should be complaining to your cell providers for breaking your phone.

THEY broke something that was built to their specs with the android update... Looks like they broke BLE. It is NOT a Garmin issue, as it works on Android 4 and 5...

If you go into Settings - About are you running build version MRA58K? If not, can you list the build you have?

You are right!

The issue has been resolved. After reading some articles online about Android M's BLE set up:

"Android M Issues
Every major OS release introduces new challenges with implementing BLE but M is particularly problematic...
Low-Energy scanning only returns results if (A) Location permissions are in your manifest, (B) new so-called "runtime permissions" are enabled (https://developer.android.com/training/permissions/index.html), and (C)Location services are on. (B) is a new requirement in Android M that forces a user to confirm "dangerous" permissions granted by (A). If (A) and (B) are fulfilled but (C) is not, SweetBlue falls back to classic discovery mode, which only returns device name and mac address as opposed to full advertising packets, but is better than nothing. If either (A) or (B) are not enabled no scanning will work at all. As for why location is needed, technically your location could be ascertained by receiving advertising packets from bluetooth devices with known geographic locations."


So, it's not the GCM's app GPS location permission, but instead the phone's system location service. You have to turn it on in order to use BLE to pair.

Thanks for posting this update! I'll report back if it works later. I also found this related FitBit link: http://www.androidcentral.com/psa-you-may-have-issues-using-fitbit-marshmallow-phone-0

Yes. This was it. Thank you!!!!