Blaze vibrates for incoming calls and drains

[Mcossie]

Since update to iOS 13 & Fitbit update (all on same day), having the following issues.

1. Blaze still buzzes after I answer incoming calls.

2. Battery drains very fast. Have to recharge 3 times a day as get only 6-7 hours max on a full charge.

Have followed the instructions on iOS13 Fitbit notification but made no difference.

Have switched off all day sync, made some difference to battery usage but still cannot get more than 7 hours of usage out of a full charged Blaze.

Moderator edit: updated subject for clarity

[kygirl73]

I’m having similar issues.  The Blaze continues to buzz even when I’ve answered a call.  Whenever I answer or initiate a call, I get an “active call” notification that I never got before iOS 13.  Sometimes when I get a call, my “answer” or “decline” icons don’t appear. 

[joaniedun]

I’m having the same issues with the calls. I get email, and snap chat notifications- but no text messages. Everything is on. Anyone have any suggestions? 

[Lisaj82]

I am having the same issues with my blaze since last updates. Blaze doesn’t last a full day after charging, phone calls continue to buzz even after answered, no text messages anymore. I’ve tried every suggestion and nothing works. I suppose it’s time for an Apple Watch after so many years with different fitbits 😕

[MissKelly24]

Has anyone solved this issue? I have tried EVERYTHING in terms of troubleshooting. My blaze buzzes when I call someone as well. Since the original iOS 13 update, I have not received any text messages on my Blaze. 

[rob_db]

I'm having the same issue, and see nothing from Fitbit Staff on the subject.  Could someone from the team please confirm this is being worked on? 

[Rosser_d]

Has a fix for this been found? It’s starting to really iritate me!

[dnssmrd]

I opened a service request on Nov 17th and no real development since...

I requested an update + ETA on fix and here is the answer I received on Dec 17th (One month later)

Thank you for contacting us again. 

We are sorry to confirm you that the issue have been studied but we have not find a solution so far. 

We must to request you to wait a little bit more until ours engineers find a solution. 

Please let us know if there's anything we can do to assist you in the meantime.

Sincerely,

[thenameless1]

I don't work for fitbit, just a fellow blaze owner. I offered to step in and try and fix the issues because i get the impression fitbit isn't going to address. I hope im wrong and they do fix it

I think they are just trying to phase out the blaze owners with the hopes that we will buy one of the newer versa trackers.

I like my blaze and i'm going to use it until it dies! When it finally bites the bullet  i won't be giving fitbit any more of my money though. I'll be switching to the apple watch when that day comes.

[dnssmrd]

Same here... If they think that I’ll spend more money on Fitbit product.... 

They have to deserve it... They’re not on the right track so far.

[Goooooch]

This affects me as well. Both the continuing to buzz even after taking the call, but the buzz to notify me that I am on an active call. It seems highly unnecessary when we all know if we have dialed a number. 

One simple solution to stop the buzzing is hitting the single button on the left side of the Blaze as soon as it starts buzzing. That will stop the watch from buzzing and hopefully preserve some of your battery life. 

Ultimately though, I am hoping Fitbit will remedy the situation or there will be a bunch of us moving to Apple watches. 

[Lisaj82]

Just so y’all are aware... it’s not just my blaze with these issues. My husband has a versa and it’s doing the same exact things as my blaze. Constant buzzing, no texts (although he is receiving messages from WhatsApp) I ve owned just about every fitbit which has been years and years of product buying. Unfortunately, with my blaze not working the way it was designed to, I have resorted into buying an Apple Watch instead. You’ve taken too long fitbit... sorry. 

[Odyssey13]

@thenameless1    "these guys" have been here a long time and posting so often that the forum rank of "Community Legend" was given. Anyone who posts gets a rank, even you have one. People often laugh when they are given "jogger" as a rank, when they don't jog.  As Community Council members, we try to help people,but we are not Fitbit employees. 

While the Blaze is no longer being produced, the support is still there. It's true that independent developers will make clock faces for the newer devices. I have an older Samsung Galaxy S4 and a S8, but with the newer ones out there, mine aren't remembered as much. Same for any device where the new models are released and developers want to be the first to make the extras for it. Developers often work on their own, as do app makers who create for a product they didn't create. It's no different than a company making their own bands for the various fitness trackers or charging units for them.

I am sorry you're unhappy. You keep mentioning the Apple watch. From looking at their forums and Garmin's, they also have unhappy people and many complaints on the same issues people post on these Fitbit forums. Whatever you do, I wish you well. 

[Lisaj82]

Keep mentioning??? I’ve mentioned twice. First when I was thinking about switching over and just, as I’ve decided to switch because fitbit can’t seem to fix its multiple problems.... it’s been months since blaze stopped working. 

[Odyssey13]

@Lisaj82  my post was directed at @thenameless1  and not to you. When posting on the forums, it's most helpful to tag the person by using their name. The way the forums work, if you post in a thread and there is a response, you get notice of it by email. You can remove this by unchecking it.

[thenameless1]

@Odyssey13 i didn't mean anything bad when i referenced you and @WendyB as Community Legends! i know exactly how you guys got the rank and that i have one too. If you look at your stats (the number of posts and accepted solutions) I'm more inclined to believe information provided by you guys as opposed to some of the fitbit moderators and that's my personal preference.I'm saying that because i think I'm more likely to get a straight answer from you guys.

It's kind of like those farmers commercials where the guy says "we know a thing or two because we've seen a thing or two."  I'm not really a Patriots fan, but  another reference is everyone referring to Tom Brady as the "goat" (greatest of all time). You can't deny that Tom Brady is good at what he does. Community legend wasn't meant in a bad way!

Now the blaze isn't like the versa or the Ionic it doesn't run fitbit OS so it never had the option for 3rd party developers  to step in and make improvements or new clock faces. Everything with the blaze was controlled by fitbit. If i'm wrong and this existed at some level or if it's going to then i would like to be part of it. I would love to step up and help others in the community with their blaze issues.

I'm not looking to go out there and create a new app/ecosystem like these guys did when Fitbit bought pebble. https://rebble.io/howto/

All i want to do is maintain the trackers functionality. Just because it's outdated doesn't mean its a bad tracker and some people don't need the latest and greatest features of a new one.

[Mcossie]

Found a solution, I got a Fitbit Ionic. Far from ideal and not the solution everyone is looking for, it has been months since this issue was raised with Fitbit, do not believe anyone is really working on Blaze issue. Can confirm Ionic works fine and does not have the issue a Blaze does.

[SunsetRunner]

I’m happy to see your Fitbit Ionic is working great for you. Happy Holidays and Happy Stepping! 😃

[WendyB]

I didn't even post in this thread so I dont see why you are calling me out @thenameless1 

[thenameless1]

@WendyB I wasn't calling you out.  I thought of it as a compliment. I'm sorry it was taken the wrong way!

Merry Christmas WendyB!