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

Pairing fail Edge 1030

Hello all,

i got from Garmin service a new Edge 1030 (replaced the old one, because of the blue halo). But now I am not able to connect it via BT to phone. I am having still the same one as with the first Edge where the connection works fine. BT connection is working fine for my old Fenix3 and new FR945 (added month ago).

I tried the factory reset, uninstal the GCM from phone, unpairing the Edge from BT menu, restart the phone and Edge multiple times, Wifi is OFF on phone and I still receiving the "Pairing failed" error. Is there anything else what I can try to set up the BT connectipon with phone?

Thanks in advance for another tips/hints

Phone:

Honor 8, Android 7.0

Edge:

software version 9.1

TCS 85.11.00, GPS 4.40!

  • Hello, 

    I had the same problem. It seems to be an error in the Garmin Connect APP. I can recommend you to download the Apk that is availeble here: 

    https://www.apkmirror.com/apk/garmin/garmin-connect-mobile/garmin-connect-mobile-4-22-1-release/

    Install this one on your phone, disable automatic updates and you should be able to pair again. 

    Also, in this version, my segments work, my livetrack works, and notifications work. 

  • Hei gABBY025, thanks a lot for your help. It really looks like that problem was in GCM version 4.27. With version 4.22.1 I was able to pair edge and synchronize as well.

    Thanks a lot once again

    Tom

  • I've was having the same pairing issue with a replacement 1030 on a Samsung S6 running GCM 4.27. I'm on the Edge 9.28 Beta. A previous beta 9.24 did change the way the two BT connections are displayed on the phone to distinguish between the BT & BLE connections when pairing. I didn't know if that was causing a problem. Though as you're on 9.10 that doesn't seem to be the case as that production release doesn't have the change

    I found that pairing would fail just after acknowledging the pairing passkey in GCM. I have since had a successful pairing though. I had WiFi enabled & connected to my home LAN & found disabling WiFi on the Edge while pairing would allow it to pair. It still took a couple of attempts but eventually paired.

    What I did was......

    1. Disable WiFi on the Edge & reboot it

    2. Ensure that there are no bluetooth pairings for the Edge in the phone bluetooth settings (If so delete them)

    3. Force Stop GCM & clear the data cache

    4. Open GCM 

    5. Initiate the BT pairing process on the Edge

    6. GCM might automatically detect that there is a device to connect, but if not go to Devices, select Add Device & follow the instructions

    7. When the pairing passkey is displayed acknowledge it on the phone not the edge & hopefully the Edge will eventually pair. If it doesn't try repeating the process.

    8. Finally once paired Enable WiFi again ..... Happy Days.

    Failing that If you're feeling brave you could install the 9.28 Beta & see if that helps.

    I don't know if all these steps are absolutely necessary but it paired & connects so I'm happy

    As a side note I see you're replacement Edge has TCS 85.11.00. Chances are that will get the blue halo too. I'm on my 3rd replacement for the same issue fortunately? this one has TCS 86.04.00, which I understand sorts the problem...Here's hoping. Good Luck

  • Thanks for the tip, it really looks that version 4.27 is a bit buggy. I was playing with the wifi on/off as well but without success. So far I am happy that all is running with version 4.22.1.

    Regarding the TCS I saw that comment before here on forum, but unfortunatelly I got the new unit again with the same version. Now i can hope that the blue halo will not  come again and if so then before the warranty ends. Let's see...

  • Anyone tried the new GCM 4.27.1 for Android and has better Sync or Pairing Achieved?

  • I tried it today. 4.27.1 instaled and both FR945 and Edge 1030 connected immadiattely. So I would say this version solved the pairing issue.