Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Blaze notifications stop every time I charge it

Replies are disabled for this topic. Start a new one or visit our Help Center.

Every single time I charge my Blaze, the text and call notifications somehow get disabled even though it's paired with my phone and notifications are turned on. It's maddening. Can you please fix this issue? Tired of having to jump through the troubleshooting hoops every time I charge this thing.

 

Moderator edit: Caps

Best Answer
0 Votes
4 REPLIES 4

It's great to see new faces @sdpitk, welcome! And thanks for troubleshooting this by yourself.

 

Are you charging your Blaze when the battery completely drains or when it stills have some charge? If you are letting the battery drain completely, I recommend charging it with some charge. Also, you can follow the instructions provided in the My Tracker isn't receiving notifications (iOS Fitbit app) post.

 

Let me know the outcome. Woman Happy

Alejandra | Community Moderator, Fitbit

If you like something I recommended, I encourage you to mark that reply as "Best Answer". 🙂

Best Answer
0 Votes

I'm usually charging it with some charge left. Unfortunately I go through the hoops listed in your troubleshooting post every time and only find success every once in a while.

Best Answer
0 Votes

Are notifications being disabled in the app or on the Blaze itself @sdpitk?

 

Tey swiping down on the Blaze screen, or hold in the top right button to get to the notifacation sertings on the Blaze.

 

Best Answer
0 Votes

Since last fall, I have had the same problems. Notifications are not working after I charge my Fitbit.  I always have some charge left, I pair it with my Galaxy 6.  Please fix this annoying problem.  I go through all the steps that are recommended and sometimes it works right away and other times it takes me up to an hour to get the notifications to come through.   I am so glad to see that I am not the only one with this problem.  Maybe Fitbit techs will update and fix this bug.

Best Answer
0 Votes