Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Fitbit Update: 1/15/2020
Hello, Android users!
We've been seeing a lot of you that recently have upgraded to Android OS 10 report that you're now having difficulty receiving notifications to your Fitbit watches.
I've merged many posts together and we've escalated the issue to our developers to investigate.
Thanks for stopping by the Community to post and let us know about this issue. Subscribe to the thread so you can see any updates after we receive more information. We appreciate your patience!
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
Answered! Go to the Best Answer.
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
@FitE Welcome to the Fitbit Community! It's great to have you here! Sorry for the delay in my reply.
Let me help you with your Inspire not syncing with your Android phone and thank you for troubleshooting this issue with Support. Have you tried clearing the link between your phone and your tracker? Please do the following:
Regarding the reminders to move, try removing them, save and sync then readd them, save and sync again.
Let me know how it goes.
If a post helped you try voting and selecting it as a solution so other members benefit from it. Select it as Best Solution!
Best Answer
01-04-2020
10:47
- last edited on
01-06-2020
15:22
by
RicardoFitbit
01-04-2020
10:47
- last edited on
01-06-2020
15:22
by
RicardoFitbit
I have a Galaxy s10 and have always gotten my text notifications and in the last two days receive all notifications except for texts. I have done all the trouble shooting and can't get it to work! I have the Versa.
Moderator edit: Subject for clarity
Running Versa 2 with a samsung 10e with android 10 UI 2.0. Since the UI2.0 update only call notifications are work. Confirmed all notifications settings in the app and phone and still nothing. I went as far is performing a factory restore on both my phone and the Versa 2. Its sad to see that nobody over at fitbit tests the beta versions of these release prior to launch. I called support also no solution rather was advised its been escalated as a high priority issue. I work for a communications company and we are getting a large amount of customers furious both with IOS13/ Android 10 US2.0. Lets hope this gets resolved soon otherwise I will just recommend our customers purchase an Apple watch or Samsung Active over the Fitbit Versa line.
Having the same issue! Super annoying...
I' m having the same issue with my Versa and my Samgung Galaxy Note 10. I updated the software on my Versa this morning and now I don't get text notifications but I still get phone notifications. I started with a Fitbit chat support and they told me was that my phone was no 100% compatible and they couldn't help me any further.
This is the second time I've had this happen and it took a new watch the first time around so there is something they can do
I have a Samsung Galaxy Note 10 with Android 10 and my notifications were working on it until I updated the software on my fitbit today.
Welcome to the club 😕
I isolated the issue to a compatibility issues with samsung messages app. Installed Google messages for now until they resolve this conflict. ... update looks like notifications stopped again with this method
Best AnswerDoes the new watch work now? Mine literally worked days ago. I have some EVERYTHING! I did everything on the website for resetting it, resetting my phone, etc.
Galaxy s10 plus
Like I said the new watch worked up until yesterday and nothing's changed
I have the same issue with my ionic and my galaxy s10. I think its only been a problem since my phone's newest software update so hoping Fitbit just need to catch up with that update or give us a work around.