09-19-2019
12:54
- last edited on
09-20-2019
11:49
by
RicardoFitbit
09-19-2019
12:54
- last edited on
09-20-2019
11:49
by
RicardoFitbit
I have a Blaze version 17.8 and up until this week have had no issues with it syncing automatically. This week I've had to manually sync and as of today its telling me device not found. It also is running about 5 minutes behind the actual time.
I have Galaxy Note 8 running Android Version 9.
I have tried all of the help fixes and nothing works. While doing so I tried to type my phone into the compatibility checker and the Galaxy Note 8 isn't there? I'm concerned about this because 1) all the other notable versions are there and 2) I've been using them together for months.
Moderator edit: Subject for clarity
09-20-2019 11:48
09-20-2019 11:48
Hello @mamab.losing.it, welcome to the Community Forums!
I appreciate the information and details that were shared in your post, your effort and patience troubleshooting this situation prior to posting are appreciated too. Let me share with you that the Samsung Galaxy Note 8 is not currently listed as a compatible device with our products and services, therefore, you may experience certain connection difficulties with it. I'm aware that some users are able to use non-compatible devices with our Fitbit products, however, we cannot ensure a proper function of all its features due to this compatibility concern, Fitbit app and Android updates.
Even though your mobile device is not compatible, I recommend you to check how the syncing procedure works here and see if there's a missing requirement on your Samsung mobile device that's preventing the syncing procedure to be completed. Also, you can move forward to the troubleshooting steps that are specified on: Why won't my Fitbit device sync? and let me know how it goes.
If by any chance you're still unable to use your Fitbit with your mobile device, I suggest you to try with a compatible device or a computer instead.
Keep me posted and let me know if you have any additional questions.
05-18-2020 00:49 - edited 05-18-2020 00:51
05-18-2020 00:49 - edited 05-18-2020 00:51
Hi @mamab.losing.it, I'm having the exact same issues with the same Phone and Fitbit that have been working fine from day dot until recently, I've tried just about every known fix there is but haven't been able to solve the problem. Also I have 2 Blaze's and they are doing the same thing on the Note 8 so I'm thinking that it must have been a phone update that caused the issue. If I do find a solution I'll post it for you. Cheers