10-14-2019
17:13
- last edited on
12-10-2019
17:35
by
LizzyFitbit
10-14-2019
17:13
- last edited on
12-10-2019
17:35
by
LizzyFitbit
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
01-03-2020 13:56
01-03-2020 13:56
I have been really frustrated by this issue as well. I rated the app stating these issues and they reached out with the following:
"Hi there, We're sorry to hear that you're no longer receiving notifications after the iOS 13 update. To help you with this, please make sure your notifications are correctly set as instructed here: https://help.fitbit.com/articles/en_US/Help_article/1979. We also suggest following our troubleshooting tips there. Let us know at contact.fitbit.com if you need more help. We'll be glad to further assist. Sincerely, Fitbit Support "
...and...I am happy to report...IT WORKED!! I just received a text notification!! I am so happy!!!
01-03-2020 14:01
01-03-2020 14:01
This is fantastic news @MissKelly24 I’m super happy for you!! 😃 Happy Dance Indeed!
01-04-2020 05:15
01-04-2020 05:15
Well... Happy for you if you now get your notifications.... However, I think you wrote your comment in the wrong post....
The issue reported in this header is that the device receives the call notifications and does not stop to vibration after answering the call.
My two cents...
01-04-2020 09:20
01-04-2020 09:20
@MissKelly24 does your Blaze still vibrate? in your earlier post you said it wouldn't stop vibrating... did it stop vibrating? You didn't provide an update on that issue,
01-04-2020 14:53
01-04-2020 14:53
I have been following the same instructions since October, and the problem still remains. Which is more worrying, as it means that the issues are not generic but hardware specific. @Fitbi, how are you going to address this? It is enough to make me consider moving from the Fitbit environment, as much for the lack of attention to the problem as the issue itself.
05-19-2020 08:11
05-19-2020 08:11
100% agree