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

735XT Bluetooth sync issues - Huawei p9 Lite

Since last week of October my 735 refuses to connect and sync with my Huawei P9 Lite.

I tried to do almost everything.
On the smartphone, clean data and cache, uninstall and reinstall the app.
On the watch, turn off/on, master reset, format partitior, reinstall files, trying to downgrade firmware...... Nothing !

Actually If I try to pair, often it's not possibile to digit the bluetooth sync numer (windows disappears before I completed , and then reappears, and so on..)
And if you reach this phase, it goes on timeout during pairing process...

This has been working for a year and a half, with minor but acceptable issues .
Actually watch is less useful and, more important, not doing what I paid for.

Garmin smartphone compatility list marks OK this brand/model.

I wrote to Service Support and I received a standard mail with instructions to format and reinstall files. Done with no success.
After that, another mail suggesting to send to service point to fix the problem.
Customer service not useful.

I tried also to connect a Samsung J5 and magically.... it worked
So I assumed that all my time, efforts and personal loss of data have been caused by an improper software release that has caused problems to huawei p8 - p9 model in particular.

I read a lot of complaints on this forum, with same issues on 235 model, but not on 735xt .

Have you faced similar problems?
Have you any suggestion?
thank you
Alex
  • Former Member
    0 Former Member over 7 years ago
    Hi AScalise,
    I'm in the same situation.
    I have a P8 lite 2017 and I have many problems since months, now I have no way to sincing the watch.
    When I need to upload trainings or to simply update the datas I have to use my wife phone.
    It's incredible that there's no way to fix these issues with these phones when they are "fully compatible" with the software..
    Customer service totally unuseful
    I hope for the future upgrades but I don't believe in...

    ciao


  • Hi...
    I've the same problems too, trying with two different devices:
    1. A Huawei tablet that working fine before last update (last week of october). Now the device can't pair the watch and it's totally unuseful...
    2. A Nexus 5 phone that also working before mobile app update and now it's able to pair the watch, but not seeing all the data registered with the 735XT.

    Now I've on the wrist a watch a watch that is worth half of what it cost.
    It's incredible for the Garmin.
    Have you any suggest?
    Thank you.
  • I am having similar issues with my iPhone. The phone's bluetooth settings page shows the watch is connected, but the app doesn't show it connected.
  • I have the same issue here. Fenix 3, iPhone with iOS 11.1. Garmin said it's not there problem... WHAT!!!! So I hold my breath till Apple releases another patch? How does an update break the BT protocol?? As a firmware engineer, this makes no sense to me. I'm not sure I believe Garmin on this one. The worst thing is that they give no updates!!! I had this issue and at least my phone would occasionally connect via bluetooth. Once everything was disconnected and unpaired, I've never been able to connect again! I can use a hardwired with USB and garmin connect and sync my work outs but HOW IN CONVENIENT IS THAT! Time to look at other products I guess. It would be nice if Garmin would publicly announce what is going on and give updates on status. When you call in, they know about it yet everyone knows nothing about it on the forums. No wonder there NPS sucks.
  • Former Member
    0 Former Member over 7 years ago


    Same problem here, and it seems to be a very common problem and app related. In fact, like you did, when I tried to connect a different phone it worked. If you look for comments on the google play store you will find a lot of people has this issue with every device. The issue is probably related to disconnection, because it seems that after a disconnection it is impossible to reconnect again. Now I'm trying to clean data and cache and everything related to garmin connect on my phone and then uninstall and reinstall the app, because this seems, logically, the best way to fix the issue (I wonder if formatting the phone would be the solution, since you had no luck with data clean and un/reinstall). I'll let you know if I'll figure something out.

    ---------
    Update:
    I called customer service and I figured everything out. We need to wait until an update for the app comes out, in the meantime we have to use garmin express on pc. Apparently this problem is related to Huawei devices (I have a Honor 6x) and the only fix is to wait for developers to fix this (LOL). Still I don't like how they are handling this situation, they should, at least, write something in the website (At the beginning i thought the watch was broken...).
  • Yes It's incredible that no one of Garmin's team take care to reply or suggest something to do (also wait for a fix)
    I think that this is a baseline on which build trust and reliability. Actually Garmin doesn't deserve any of this.

    It's unbelievable that this can be happening with a brand like Garmin. It's unbelievable to spend about 500€ and receive such a service level .
    Probably conditions to ask a reimbursement ....

    Dear Garmin, please read all these posts, REPLY and do something to fix it, quickly!
    Thank you
    Alex
  • I find it really funny people always point at Garmin, not at the phone vendor! Why not moan at them and get them to fix their Bluetooth stack. I can’t believe they don’t check their compatibility with Garmin products. If I was you I’d change to another phone vendor. Don’t always assume this is down to Garmin.
  • Agreed. Too often folks blame Garmin when it's nothing to do with them.
  • Former Member
    0 Former Member over 7 years ago
    here there isn't a "blame problem" for Garmin but it's clear that someone who buys the watch checks the compatibility list of the watch not of the phone!
    In other case the phone vendor have to publish an endless list of all the bt devices on the world? the opposite it's easier
  • Former Member
    0 Former Member over 7 years ago
    I find it really funny people always point at Garmin, not at the phone vendor! Why not moan at them and get them to fix their Bluetooth stack. I can’t believe they don’t check their compatibility with Garmin products. If I was you I’d change to another phone vendor. Don’t always assume this is down to Garmin.


    I am not blaming Garmin, I am "blaming" (I am not pissed off nor angry, I'm just realizing there is a problem and trying to resolve it) the developers of the app, the watch itself is alright... I think they should say that there are some issues with some devices declared as compatible and make it clear. When I had the issue I had a hard time trying to understand the root of it. And the customer service is of the same opinion, in fact they told me to wait for an app update. Conclusion: the watch works very well, my phone works very well (with other Bluetooth devices i have no problems at all), so the issue is the app: probably is a very small bug, but I would like if they fix this. Of course the watch can be used anyway, but to fulfill its potential the app needs to work.

    Last thing about compatibility: most Huawei models are listed as compatible, someone is indicated to have issues, but this one is a major issue which prevent the app to be used (again, not the clock:unlike AScalise I have never thought about a reimbursement or that the service level offered by Garmin is not good, in fact customer service, as I said, worked perfectly for me).


    If I was you I’d change to another phone vendor. Don’t always assume this is down to Garmin.

    Like I said this probably is a problem which isn't related to either of the twos, but to the developing team, and from their point of view is also a silly one and easy to fix.

    Don’t always assume this is down to Garmin.

    Of course. We agree. But, please, don't assume this is everytime (maybe often, but not everytime) down to the user or his devices.