RESOLVED: Unknown Caller ID w/Android Pie (9.0)

[AlessFitbit]

Fitbit Update: 10/3/18

Hi, Android Pie users!

I'm aware that many of you are still receiving your call notifications as "Unknown Caller."

I'm sorry for any trouble this issue may be causing. I've gone ahead and escalated that the problem persists. When I hear of any updates from our team, I will provide them here.

Thanks for your troubleshooting efforts and for reporting. 

[nmnkohli]

Hello I have recently bought fitbit versa and I am surprised to see the compatibility issue with the google flagship phone (Pixel 2 XL). 

During the conversation in the thread, fitbit has claimed many a times to have rectified the issue but I am still seeing "Unknown Caller".

I would like to know if the current version 2.81 has resolved the issue or not. If yes by when the latest version will be available in India.

Kindly resolve the issue as this seems to be very frustrating.

Thanks

[Dolphinsausage]

My fitbFihas not automatically synced to my phone since it was updated to the Pie OS two months ago. I have to reset it manually each time in order for it to work. Is there a fix for this? If not, I will be getting a new tracker and probably not a Fitbit. I'm really tired of this not working.

[Icecream2010]

Is there a timeline to when this will be fixed? I have tried all that has been mentioned in the thread and continue to have "unknown caller". Thank you for your response

[scubadiveri]

original pixel, Android 9, charge 2, Fitbit ver. 2.80.1.  after Android 9 update calls show as unknown.  They used to display contact name or number.  Text and calendar notifications work.  Tried all fixes in this thread.  It's unacceptable that Fitbit sells an expensive device and can never support it. WHEN WILL WE SEE A FIX?

Moderator edit: Format

[LanuzaFitbit]

Hey everyone.

Unfortunately there aren't updates to share at the time. Whenever we have anything to share we'll be sure to let everyone know. 

We appreciate your patience and understanding. 

Feel free to reach out with any other questions.

[TheWraith119]

Before the last 2 updates, I only had issues with the Unknown caller problem.  As of Sunday, the app has now stopped communicating with my Charge 2 altogether.  I uninstalled and reinstalled the app on Wednesday when I noticed it hadn't synced and I hadn't received any notifications for calls or text messages.  That seemed to fix the problem.  Now I just noticed that I had a missed call from 40 minutes ago and I took a look at the app again.  It stopped syncing again as of 4:02 PM yesterday.  I also installed a new update yesterday, not that it resolved the Unknown caller issue either.  When the primary function of the tracker still works, I can deal with it telling me "Unknown" caller, but when it can't even sync to the app, now we have a problem!!!

[TheWraith119]

---

@TheWraith119 wrote:

Before the last 2 updates, I only had issues with the Unknown caller problem.  As of Sunday, the app has now stopped communicating with my Charge 2 altogether.  I uninstalled and reinstalled the app on Wednesday when I noticed it hadn't synced and I hadn't received any notifications for calls or text messages.  That seemed to fix the problem.  Now I just noticed that I had a missed call from 40 minutes ago and I took a look at the app again.  It stopped syncing again as of 4:02 PM yesterday.  I also installed a new update yesterday, not that it resolved the Unknown caller issue either.  When the primary function of the tracker still works, I can deal with it telling me "Unknown" caller, but when it can't even sync to the app, now we have a problem!!!

---

I forgot to include: Charge 2 SE, Fitbit App ver. 2.80.1, Google Pixel 2 XL, Android ver. 9

[SunsetRunner]

I'm tagging in on this topic as well. Pixel XL, Android Pie, Charge 2, Fitbit version 2.81. Call notifications all show 'Unknown Caller', and often continues (or only starts) vibrating after the call has been answered or missed.

[DBRII]

Alta (Firmware version: 21.21.40.2), Pixel, Android Pie "Unknown Caller" complaint. Started a few weeks ago. Text message details come through as they always have but every call is unknown caller, and often very delayed at that.

Have uninstalled/reinstalled the app, reset the Alta, powered down the phone and toggled the various options within the app that ostensibly are there to provide better connectivity. 

Super *issed off about this as I often rely (or used to rely) on the caller ID notification to screen calls. 

[RageKage]

Also having this problem. Pixel 3 with Android Pie and a Blaze .

[Innob]

My "patience and understanding" is wearing thin.  Fitbit has known about this issue for months and all you keep saying is that you don't have any new information.  Take a look at the recent ratings of the app.  Everyone is having this problem and from our point of view, it doesn't look like you are doing anything about it! When is Fitbit going to formally acknowledge and fix this issue?

[Mathewk69]

Why doesn't the fitbit charge2 work with the Samsung a5??

[LanuzaFitbit]

Hello everyone.

We understand how frustrating this must be. Unfortunately we have yet to receive any updates on the matter. I'll continue to have my eyes open and let everyone know the moment we receive any news.

Please feel free to let me know if there are any further questions.

[scubadiveri]

Do you work for Fitbit? Are these concerns being relayed to their
Developers? Or are you just a moderator doing this in your spare time? This
needs to be raised up to Fitbit customer support

[lamptey1]

Do you still have this problem ?

[scubadiveri]

Yes, there has been no change everything works except the call notifications. But I can see calendar event and I can see text messages and who they're from.

[jst1986]

I've upgraded from the Surge to the Ionic and still getting it! 

[Bkropcptn]

Yes my Pixel2 XL still has unknown caller ID. My wife Pixel2 has unknown
caller ID and the watch notifies you twice every time someone calls.--

Regards,

Brian Rozas

[lamptey1]

They need to sort it out as its annoying

[Slavs06]

yes i still have the problem

Shawn Laverty

Moderator edit: Personal info removed