01-05-2019
10:54
- last edited on
09-08-2020
18:22
by
MatthewFitbit
01-05-2019
10:54
- last edited on
09-08-2020
18:22
by
MatthewFitbit
Hi
Can we expect someday that my Charge HR 2 bought in 2015, will be able to be synchronized with my new Samsung S9+ bought in 2018 ?
So far, after so many tests with the Fitbit App (such as re-install, re-setup and so on) seems that this issue still remain not fixed at all, unlike what it was said in the following post:
https://community.fitbit.com/t5/Charge-2/Synchronisation-avec-Galaxy-S9/td-p/2923022
Or, some people in the same situation as my case, seem to have gave up since a while:
https://community.fitbit.com/t5/Charge-2/Samsung-S9-compatibility-with-Charge-2/td-p/2611330
I don't want that you provide me the same solutions as suggested into the two previous post, here above, as I've already tried them without any success. I just want to know if I have to throw into the trash my Charge HR, because this compatibility issue which still occures and will never be fixed in the future at all ?
I hope that I'm wrong and I won't get a positive answer to this question (as well as to Earth's protection).
Regards.
01-05-2019 17:45 - edited 01-05-2019 17:45
01-05-2019 17:45 - edited 01-05-2019 17:45
May I ask what the problem you are experiencing may be, you links go where.
Unlike Apple I'm not aware of any planned obsolescence, which for Apple they expect their watch to die within 3 years
Many still have their 5+ year old trackers still going strong.
01-06-2019 04:36
01-06-2019 04:36
With my new smartphone (S9+), whenever the Fitbit app attempts to synchronize data from my Charge HR, there is nothing but just a little logo spinning itself, meaning synchonization is on going. But after a long time, the synchronization stops with an error.
One more thing, I'm not sure that the pairing procedure has been correctly fullfilled. Whenever I try to do the pairing procedure, after enter the four number code into the app provided by the Charge HR, the app stays blocked, with the same behaviour as I've described just above.
This is quite confusing because sometime the app says that the synchronization is over but when I want to relaunch it, the app rebegin to wait during long time. I guess that this unsteady behaviour could coming from a wrong software development or something else in the bluetooth's interfaces used by the Fitbit's api (?).
01-08-2019 17:09
01-08-2019 17:09
Having the same issue. It is so frustrating and I feel like throwing this thing against the wall. Bought it from T mobile and months later the phone was no longer supported. I went to another carrier, got an S9 and was disappointed to see it wasnt compatible. NOW I see that in September it is supported. I have reset, unpaired, logged out/in, everything and no results
01-09-2019 03:46
01-09-2019 03:46
I shared the same feeling. Even though our devices are a few old, I'm pretty sure that every issues like this one aren't from themselves but mainly from software uploaded inside them, instead. As result for me, that can be fixed by the companies.
But now, seems that I've got synchronize successfully data in my smartphone. May be this is due to the last system update of my smartphone, I carried out few days ago.
May be in your case you could solve this by first deleting all your Fitbit App's settings and then by trying again to configure your account and restart the device pairing with your phone. It is what I did few days ago.
Good luck ! 😉
09-02-2019 04:47
09-02-2019 04:47
Same issues here. Our family always had the same devices, and they always seem to get the same problems, at the same time. The problems are always unfixable, and blamed on incompatibility (where it worked fine before) and updates (which 99% of the time never work). Devices are rendered useless.
Very dubious in my opinion, and if that is not the case, Fitbit must consider seeing it from a consumer point of view... it smells bad, and dodgy.
Had two fitbits, but I don't trust you guys anymore, number 3 will be ANY other brand.
09-02-2019 06:04 - edited 09-02-2019 06:15
09-02-2019 06:04 - edited 09-02-2019 06:15
This whole there's seems to be about app updates and the Android ver 9, and not about any single type of tracker. You could read one of the threads on the Android forum.. Do I have an answer.. No, what seemed to work for me in the past was to clear the apps cache.
Unlike most issues there doesn't seem to be a central thread but several threads spreads over multiple hardware and software boards.