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

Android pairing problem

Former Member over 7 years ago

Hi, so since a few days, my Forerunner 235 wouldn't sync anymore with my phone. This has happened before so I deleted the device from my devices on Garmin Connect and tried to pair it back as that usually works. Now it won't pair anymore. It gets so far as to give me the passkey, but before I can type in the passkey in my phone, the watch goes back to "Ready to Pair" and gives me a new passkey, and so forth. On my phone it says "Timed out while connecting to device" over and over in red and "couldn't connect to Forerunner 235" in grey every time the passkey disappears again.

New passkeys keep showing and disappearing and sometimes I'm fast enough to type it, but it just does the same thing.

I've restarted both Forerunner and phone countless times, turned Bluetooth on and off, all in every order I can think of. It just won't pair back up. I have no idea what to do and I can't find this particular problem anywhere on the internet... help would be appreciated. Thanks!

0 ASmugDill over 7 years ago

It does not seem to be a watch or mobile problem, but a Connect Mobile problem.
A bit disappointed.
My phone is a Huawei P8 Lite, android 6 EMUI 4.0.3

I got the impression that, by and large, it's only affecting Huawei-branded Android devices and not ones produced by Samsung, etc. so I wouldn't (i) say it's just a Connect Mobile problem and (ii) discount the part played by how Huawei may have implemented some critical component in providing connectivity.

0 Former Member over 7 years ago

Hi ASmugDill,

I also note that most of the other apps have been working correctly with the BT on my phone, and apparently it is the same with other people owning a Huawei. The issue also concurs with an update on GC.
These 2 elements are why we are questioning Garmin's responsibility (during non-regression tests for example).
But yes, indeed, there must be also a matter of compatibility with Huawei's equipment, and it might not be to Garmin's to know what is particular with the architecture of H's phones (or whatever it is called), but to H to specify it.

I'd say it's a 75-25 resp. on Garmin.

What is absolutely astonishing is the time it takes to solve it.

0 Former Member over 7 years ago

I got the impression that, by and large, it's only affecting Huawei-branded Android devices and not ones produced by Samsung, etc. so I wouldn't (ii) say it's just a Connect Mobile problem and (ii) discount the part played by how Huawei may have implemented some critical component in providing connectivity.

Yes, looks like different brands send different connection signals and Garmin devices receive and use all of them so they are trying to fix the problem handling each specific case , but it's not an easy job and probably they don't feel they should do it.
The approach to deactivate spare connections (data and position) on my P9lite worked for me, I have 4 days of stable connection but i still waiting to try a live track session because I'm afraid the connection is still weak.

0 fabrice9164 over 7 years ago

Yes, looks like different brands send different connection signals

I thought that Bluetooth was a standard !!! Imagine if other protocols have same issues !!! WiFi, TCP/IP...

0 ASmugDill over 7 years ago

I thought that Bluetooth was a standard !!!

See this post by Joshky: https://forums.garmin.com/forum/into...59#post1284759

I'd be absolutely delighted if it turns out not to be a problem with either Android or the Garmin Connect Mobile app per se, but because some other app (perhaps installed by Huawei at the factory) is interfering with the procedure. Of course, my expectation would then be for all the disappointment and anger to be directed at Huawei and/or developer of whichever app is interfering, instead of Garmin users reframing the problem as something that Garmin ought to accommodate anyway because somehow it's the smaller player in the ecosystem and therefore everyone's bitch, so to speak.

(Yes, I'm well aware how many people like to whinge about the bloatware Samsung installs on its Galaxy range of Android devices, and to which lengths users are prepared to go in order to defy Samsung and/or have their own way on their devices.)

0 fabrice9164 over 7 years ago

See this post by Joshky: https://forums.garmin.com/forum/into...59#post1284759

I don't understand your answer with this link...

0 Former Member over 7 years ago

I'd be absolutely delighted if it turns out not to be a problem with either Android or the Garmin Connect Mobile app per se, but because some other app (perhaps installed by Huawei at the factory) is interfering with the procedure. Of course, my expectation would then be for all the disappointment and anger to be directed at Huawei and/or developer of whichever app is interfering, instead of Garmin users reframing the problem as something that Garmin ought to accommodate anyway because somehow it's the smaller player in the ecosystem and therefore everyone's bitch, so to speak.

Hi there,

Do I feel sarcasm here ? People are getting pissed with this issue not being solved while it is 6 weeks old, and it is completely normal, and it is also annoying to be kept in the dark about the progress of the issue. But nobody claimed for a fact that it is a GC problem only, just that the problem was concomitant with a GC update, so there might be something with the non-regression tests to be investigated.
Between Garmin-basher and Garmin-fanboy, there is a lot of room !

Once again, most of the latest issues with BT occur with Huawei phones, but for what I've seen here, nobody refers to any other app having similar connectivity problem as with GC and the G-watches (maybe someone with his car... Huawei chipset maybe ?).

0 ASmugDill over 7 years ago

People are getting pissed with this issue not being solved while it is 6 weeks old,

So, first of all, I'd be interested to know whether it is Garmin's problem to solve, arising from a code defect or failure to comply with technical standards. If Garmin is not at fault for causing the problem, then it is not Garmin's responsibility to solve, no matter how annoyed Huawei device users are or how old the issue is. At this point I don't know whether it is one way or the other, but I'd be delighted to get some clarity.

But nobody claimed for a fact that it is a GC problem only,

It does not seem to be a watch or mobile problem, but a Connect Mobile problem.

What does that say to you?

Once again, most of the latest issues with BT occur with Huawei phones, but for what I've seen here, nobody refers to any other app having similar connectivity problem as with GC and the G-watches (maybe someone with his car... Huawei chipset maybe ?).

It doesn't matter whether any other app or Bluetooth devices are exhibiting the same issue, as far as attributing fault and/or responsibility goes. Knowing where else or to what else the issue is happening could assist with a systematic problem-solving approach, that's all. If it indeed turns out to be something installed by Huawei by default somehow intercepting the procedure of entering the confirmation code, then it's not up to Garmin to program defensively with a view to working around it.

0 valentinrf over 7 years ago

So, first of all, I'd be interested to know whether it is Garmin's problem to solve, arising from a code defect or failure to comply with technical standards. If Garmin is not at fault for causing the problem, then it is not Garmin's responsibility to solve, no matter how annoyed Huawei device users are or how old the issue is. At this point I don't know whether it is one way or the other, but I'd be delighted to get some clarity.

What does that say to you?

It doesn't matter whether any other app or Bluetooth devices are exhibiting the same issue, as far as attributing fault and/or responsibility goes. Knowing where else or to what else the issue is happening could assist with a systematic problem-solving approach, that's all. If it indeed turns out to be something installed by Huawei by default somehow intercepting the procedure of entering the confirmation code, then it's not up to Garmin to program defensively with a view to working around it.

I have a Motorola Moto G2, and also have the same problem. It's not only on Huawei, despite what they're saying.

It was working good before the latest updates. They don't even want to know why it worked before and now is no more working.... Incredible.

0 Former Member over 7 years ago

What does that say to you?

If it was a Huawei problem, the devices never pair.
My mobile phone bluetooth system detects the watch and the watch is in the list of paired devices, but the GCM app does not detect the mobile phone.
While the devices are connected everything works fine, smart notifications, SMS, music controls etc. no issue.
When the bluetooth connection is lost the GCM app never connects again with the mobile phone, I need to remove the GCM watch and pair again.
99% of users report that everything worked fine until 2; 3 months ago.
My 2016 Huawei P8 lite is an Android 6.0 with bluetooth 4.0, so meets the requirements indicated by Garmin, and pair with any new or old device even with Bluetooth devices below 4.0.
So, it's definitely a Garmin Connect issue, not a phone problem.