Caller ID showing previous caller's name

[Melriddo]

When I receive a phone call it used to display who was calling, now it displays the same contact all the time. So if My husband is calling me it says my mum's calling me on the fitbit. It's happened 3 times now. And not just with my husband calling. But always says mum's calling. 

Moderator edit: subject updated for clarity

[Francl27]

It started happening to me as soon as the text message issue was solved.

It never ends.

For what it's worth, it shows the last caller I ACTUALLY ANSWERED TO. Not the calls I let go to voicemail or ignored.

[TheWooks]

To be honest I am not that worried. The Fitbit is there do what teh Fitbit does  keep me moving, the add on of using it to see phone calls and messages is a nice to have add on. I have simply switched this off and will switch back on when its fixed. Not getting heated up about it.

Am dropping out of the forum on this topic now

[BarneyBee]

Where did you find the older version?

Google play has the newer version.

[laserbeam1]

Google fitbit android app 2.90.

[AndreaCD]

Me too. Not good. I looked at my fit bit and it showed a random wrong number from earlier in the day...the call was actually coming from my son who had been in a car accident. I looked at my phone in time to realize it was him and I answered. But this could be VERY problematic. Obviously it's best to check your phone, but when you start to rely on the notifications to make a decision as to whether or not to answer, this is not good and needs to be fixed.

[BarneyBee]

It almost seems that Fitbit want's us to buy a newer model. It's all about
the money. I doubt this issue will ever be resolved. I'm switching to a
Samsung watch.

[Vickky]

Yes you cannot rely on Fitbit now because of its false caller notification. Hope your son is fine now.

[Grantis]

Same here. Verizon S9 and charge 2

[Le75]

Seems to be every time they suggest you do app upgrade something goes
wrong, last year I lost all info for about 4 weeks,

[LostEchoes]

I know Fitbit might not recommend this but I will mention it, as I have in other topics (with issues regarding notifications, pairing, syncing, etc), because I'd like to see people getting help and solving their issues. No one can guarantee that this will work for each and every case, though:

- Try the latest Fitbit (android) version 3.7. It came out yesterday on Play Store, but you might have to wait a few hours or days to get it as an update. If you install 3.7 and you see no resolution to your issues try the official troubleshooting steps that have been suggested to you. If that still doesn't work, then follow the next steps:
- Try to sync one more time (if that works) so that you will have all your data synced to your account @ the Fitbit servers.
- Uninstall the current version of the Fitbit app. Reboot your phone.
- From you phone's browser, google "Fitbit 2.90 mirror", find the file, download it and install it. Make sure you do not let the app be updated again to the latest google play version.
- There are reports from people saying that older versions 2.90, 2.95. 2.96 and even 3.3.1 have solved their issues. You might have to try them one-by-one to see which one might work. Uninstall each "previous" version before trying the next one and reboot your phone. 
- Mind you, 2.x versions probably don't support Fitbit premium and Versa 2. I haven't tested these versions because for me everything seems to work fine (Inspire HR with Fitbit 3.7 on a Samsung Galaxy S7 Phone).

Good luck.
Feel free to ask me any questions you might have.
I hope I don't get slammed by Fitbit for proposing this solution, but at least their customers will not end up throwing their trackers to the bin, right ?

[fc29]

Thanks for the advice

[laserbeam1]

I guess I will take the conservative route and leave version 2.90 installed until version 3.7 is rolled out and the community is in agreement that the notification and caller id issues are indeed fixed! Using a Charge 2 with Samsung galaxy s7 edge and android 8.0

[Ildi.P]

Same here, 2.90 works, so I'm sticking to it, until this caller ID issue is solved. Hopefully Fitbit admins will notify us about it, as I am not taking any chances to install a new version that doesn't work. They said to me in mail, that they are working on this problem... but it's been almost two months now 😞

[Btngfn]

I'm having the same problem on my Charge 2. How do I resolve?

[Charis6]

This is exactly where I am at. 

[Charis6]

This worked!  Thank you so much! This has been driving me crazy for so long now.

[Melriddo]

Sorry I must have missed something. What did you have to do to make or work. Sent from my Samsung Mobile on the Telstra Mobile Network

[Charis6]

What lost echos said above about finding the previous version 2.9.0 back from March 2019 did the trick

[Ildi.P]

This is what I received from support:

"We want to be transparent with you, actually we’re aware of the problem that you have right now, but may not be able to provide a fix in the immediate future. We'll continue to monitor the situation, and keep our team informed of the impact to you and other customers. We understand that this isn't the resolution you're hoping for, but rest assured we're always working to improve our products.

Be sure to keep your Fitbit device and app up-to-date to ensure you receive the quickest resolution. We're sorry for any trouble. We appreciate your patience and look forward to getting you back on track."

I've written a few times that I keep the old, 2.90 version til they solve this problem, and I really "love" how they don't want to accept that I am NOT willing to update my app to the newest versions, because it doesn't work.

[AMF81781]

I too am having this issue and it is very annoying! I bought the Charge 2 in part because it had the ability to tell me who was calling so I would have to have my phone on my person at all times.  If there isn't a fix soon, I will need to find a new fitness watch that will be able to do everything I need it to. I (and many other customers) have spent quite a bit of money on these devices and to have an issue like this that has been continuing for months is disheartening! I sure hope it is resolved soon!