05-15-2018
08:16
- last edited on
05-24-2018
06:08
by
AlejandraFitbit
05-15-2018
08:16
- last edited on
05-24-2018
06:08
by
AlejandraFitbit
Had the 32.32.10.20 update for a few days now and have noticed that whilst notifications in general are working, including replies, call notifications had stopped working. All I was getting was a missed call notification after the ringing ended. The test call notification worked fine. Been playing around with settings and one that I changed was transliteration. Call notifications started working again. Odd.
UPDATE: Spoke too soon ... broken again 🤔
Oh and for the support team, I have already done the following:
Moderator edit: subject and format
05-15-2018 16:12
05-15-2018 16:12
I'm having this exact same issue. Anyone have any advice?
05-15-2018 17:32
05-15-2018 17:32
That happened to me earlier today. Try restarting your phone and re-syncing your Versa. This worked for me.
05-16-2018 02:49
05-16-2018 02:49
Only thing so far that works is to turn Bluetooth off and on again. And this is only temporary as at some point it eventually goes funny again 🤔
I've even gone as far as doing a factory reset on both my phone and Versa 😬 It works at first but then, without changing any settings or installing any apps, it went back to not working within an hour. Did you not alpha or beta test this! It is such an obvious fault with the update. By the way before factory resetting my Versa it was on 32.32.10.20, it is now on 32.32.10.15. What is going on Fitbit? There are no more ways to troubleshoot this issue and it needs to be addressed! I'm missing calls because of it, if I'm in an area I can't hear my phone ringing I will not notice it ringing. There's no point in enabling vibrate whilst it's in my pocket as I have nerve damage in my legs and couldn't feel it if I wanted to 🤨
05-16-2018 17:30
05-16-2018 17:30
Same issue here. Interestingly, works while phone is unlocked, but not while phone is locked. Fitbit CS told me my phone is "not compatible" with Versa. But it was working fine before the recent software "upgrade." Looks like this Versa will be going back, since call notifications is one of the primary notifications i need on a "smartwatch."
05-20-2018 11:25
05-20-2018 11:25
Still no response from fitbit about this. It is so temperamental it's annoying me now. As I've said I have even gone so far as to factory reset my phone. Please don't go on about how not all phones are compatible as you barely add any new phones to your list. If people actually went by your list you probably wouldn't sell another device ever again as your list of "compatible" phones is so woefully outdated. If anything it seems to be your "get out" should anyone have an issue that you can't be bothered to deal with.
05-22-2018 11:05
05-22-2018 11:05
Same thing here. I have a pixel2XL, one of the 'unsupported' devices ( really Fitbit, the best Android Smartphone is 'unsupported' ). All notifications EXCEPT call alerts are working fine. I only get call alerts when the fitbit app is open and the phone is unlocked, which quite frankly sucks.
I also have a pebble time 2 ( LOVE MA PEBBLE!!) and it works flawlessly. You guys bought pebble and didnt learn a thing from them. Sad.
Eldukae
05-23-2018 09:41
05-23-2018 09:41
Still waiting for a response Fitbit 🧐
05-23-2018 10:25
05-23-2018 10:25
Try setting the option 'Always Vibrate' in the notifications section of the Fitbit app. It finally solved the issue of call notifications for me.
Eldukae
05-23-2018 11:21
05-23-2018 11:21
@eldukae wrote:Try setting the option 'Always Vibrate' in the notifications section of the Fitbit app. It finally solved the issue of call notifications for me.
Eldukae
Not an acceptable answer for me, when I have that setting enabled I get woken up by notifications during the night. Fitbit shouldn't expect us to compromise with half-fixes or claims that our handsets aren't compatible.
05-23-2018 12:02
05-23-2018 12:02
I have a Pixel XL....through testing this feature, I found that my watch will not notify me of the call to answer or reject until roughly the 3rd or 4th ring. Try letting the phone ring a few times before answering.
05-23-2018 12:11
05-23-2018 12:11
I have a Pixel 2 and I don't get call notifications even with the "always vibrate" option selected. I do get a notification when I have a missed call but by then it's useless!
It also keeps not syncing correctly. About once a day it will stop syncing, and won't work when I manually tell it to sync. The only thing that seems to fix that is rebooting my phone and my watch at the same time.
05-24-2018 06:12
05-24-2018 06:12
Hello all, I hope you are doing fine.
Thanks for troubleshooting this issue by yourselves. If you keep having issues with your notifications, I recommend taking a look at the help article My Fitbit device isn't receiving notifications from my phone and follow the instructions provided there. Also, please check that your phones are compatible mobile devices.
Let me know the outcome.
05-24-2018 06:28
05-24-2018 06:28
Sorry but here we go again, hiding behind the compatibility list that is updated less often than Donald Trump's tax returns....
This is ridiculous, we pay out a considerable amount of money to use your devices and the least you could do is actually do more to ensure that your software/devices work properly. By hiding behind your "list" is pretty much admitting that your software Devs cannot ensure base compatibility with Android as a whole really. I'm sorry but the fault lies with the way you handle things like this, I can't exactly return my versa to the shop I bought it from saying that Fitbit says my phone isn't on the compatible list. They will look at the list and laugh when they see how few handsets are "compatible"!
Tell me, what is the most recent phone to be placed on your list? Most likely something that came out at least 6 months to a year before the Versa was released... You can't release a new device and say you can't guarantee compatibility with something only just released recently...
05-25-2018 22:16
05-25-2018 22:16
I can not receive incoming call notifications on my Samsung S7 Edge. I called Fitbit and was given excellent customer service and advice on what to do to correct the problem and was assisted in the process all the way through to a factory reset. I still do not receive notification for my incoming calls. I have a case number, which I can provide through a secure message. Although I appreciate your advice to correct the problem, I respectfully request that Fitbit accept responsibility as this appears to be a problem they must correct. I receive notification for missed calls and texts so I feel confident that my phone and Versa settings are correct. I also received incoming call notifications when I first set up my Versa and then magically without making any changes to any settings on my phone or my Versa the incoming call notification stopped working. I have mobile service through Verizon. The update to Android 8.0 Oreo is coming in the near future. However, it appears the incoming call notification may also not work on some phones with Oreo as mentioned in a message from a Versa owner. By the way, the "Send a Test Call Notification" would be a good place to direct someone to contact customer service or settings if you do not receive a call notification rather than........nothing. Yes, I am as frustrated as everyone else who is experiencing this problem. I am further frustrated that there is a lack of two way communication from Fitbit. Problems without solutions oddly remain problems. It's an inconvenience for the customer/consumer, but it can have long lasting affects for the brand. Fitbit, please address this problem and find a solution.
05-26-2018 05:29 - edited 05-26-2018 05:30
05-26-2018 05:29 - edited 05-26-2018 05:30
BEarnhardt - Thank you for saying this in a respectful and well-thought out way. I was very frustrated with Fitbit's response, as I'm sure we all were, and wouldn't have been quite so nice!
05-26-2018 09:26
05-26-2018 09:26
05-26-2018 09:41
05-26-2018 09:41
Well said GraV. My 2017 phone isn't on the list either. So half the reason I forked out the money for this watch isn't working. I did work for a bit intermittently. But not the return window at best buy is closed.
06-07-2018 18:43
06-07-2018 18:43
Still not working. Can Fitbit verify this with Verizon? A large carrier in the US and a tech-savvy company like Fitbit should be able to find a way to get things back to how they were working briefly before the update.
Any new information?
06-07-2018 19:39
06-07-2018 19:39
I am having same issues & have done all the things you have done & talked with customer service & still same thing- frustrating........