12-31-2019
08:38
- last edited on
01-03-2020
19:14
by
RicardoFitbit
12-31-2019
08:38
- last edited on
01-03-2020
19:14
by
RicardoFitbit
I have a Samsung GS8 and a new Versa 2. Everything is up-to-date. I have been noticing that notifications will stop coming to my watch. Everything works fine for a while and then stops. This happens almost every day. Notifications come to my phone but not to my watch. The only way I have been able to get the notifications working again is to reboot my phone. After my phone reboots, all the notifications start working again. Is there a way to fix this?
Moderator edit: Subject for clarity
01-03-2020 19:14
01-03-2020 19:14
Hi @MCTronix, welcome to the Community Forums! Sorry for the delayed reply.
I appreciate the details that were shared in your post, your effort and patience troubleshooting your device prior to posting are appreciated. If you haven't already done so, I recommend you to check: How do I get notifications from my phone on my Fitbit device? to see that all the necessary requirements to receive notifications on your Versa 2 are correctly configured. After verifying this, please try the troubleshooting steps that are specified on: My Fitbit device isn't receiving notifications from my phone and let me know how it goes.
Keep me posted.
01-04-2020 07:20
01-04-2020 07:20
Here is an update for anyone else who has to keep rebooting their phone to get notifications to work.
The other day, I backed up my phone and the performed a factory reset. Then I restored it. Had to do setup, restore, log into all the apps again and also redo my customizations, Bluetooth connections ...etc. It took about 3 hours total and I was working fast. It was a real pain in the a$$. But, in the end, notifications have been working great for the last three days. I had exhausted all other options and tried everything that I found while searching the internet. I’m not sure what the problem was but I’m glad it’s working now and I feel the effort was worth it.
01-09-2020 14:40
01-09-2020 14:40
Your update @MCTronix is appreciated, sorry for the delayed reply.
Thanks for taking the time to share your thoughts and personal experience with the notifications issue you were experiencing with your Versa 2 and the Samsung Galaxy S8, I'm really glad to know that your concern was resolved after trying some troubleshooting steps. Please do not hesitate to contact me back if you require further assistance or if you have any additional questions for me to answer, I'll be around.
I want to suggest you to visit our discussion forums and participate. There are several users who are interested in fitness, healthy eating, better sleep, among others. I'm sure that they will be happy to meet you there.
See you around, thanks for being part of the Fitbit family!
01-09-2020 15:01
01-09-2020 15:01
I have the Samsung Galaxy S10 and just spent 40 minutes on chat troubleshooting literally everything I have already done. I can get email notifications and phone calls to my phone but no text messages. After having this watch for one month and $150 I can't get text messages to it...plus the battery is HORRIBLE and only get notifications up to 30 feet? This is really frustrating.
01-09-2020 15:38
01-09-2020 15:38
Update #2. After 2 days, the problem came back. I now have my phone scheduled to reboot once a day so the notifications will come back.
01-09-2020 15:42
01-09-2020 15:42
Turn off all day sync and I believe 30 feet is about right for bluetooth.
This post is for if you text comes back for a while when you reboot your phone. That is why I created this post.
01-09-2020 15:50
01-09-2020 15:50
Hi @MCTronix , all of the above mentioned "solutions" are not working at all. Some Android users, mainly Samsung users, suffer from the notifications issue, which is the result of the update to the newest Firmware update. Fitbit is working on a solution for that, but is not communicating that at all. Regards kuzibri
01-13-2020 07:22
01-13-2020 07:22
Mine is still not working. Over the weekend I tried everything again to get it to fix and still nothing. This is very frustrating.