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. 

[danshawna]

Everytime I get a call my Blaze says it's an unknown caller .This started after Android Pie update. The latest Fitbit update has not helped and all appropriate permissions are checked. Fitbit please help with this. Thanks. 

[Bkropcptn]

I have Pixel 2 XL and my wife has pixel 2. We both have latest Fitbit update and sync and restarted Fitbit and phones. Caller ID always shows unknown yet text message shows the person name.

[danshawna]

I have reported this also with my Blaze but Fitbit hasn't addressed the issue that the newest update hasn't helped the problem.

[jst1986]

Same with my Surge in my Pixel 2XL.

[LanuzaFitbit]

Hello @danshawna.

Thanks for trying all of those steps and letting us know that it didn't work. 

In this case I'd recommend that you try to go through all of the steps in this article. Basically, let's setup notifications again from scratch making sure that all of the permissions are there.

Let me know if you have any further questions.

[danshawna]

  Hello, I have gone through this steps more than once. All notifications come through fine, the issue is that all calls come through as "Unknown" .This a very frustrating issue because everything else is working fine .there obviously seems to be a software issue.

Thanks for your reply

[LanuzaFitbit]

Hello @danshawna.

Thanks for giving those steps another chance. 

Maybe we could try to remove the permissions and then add them once again. That should help. 

I'd also like to ask what phone is it that you are using at the moment. Maybe that could give us an idea of what is happening.

Let me know if you have any further questions.

[danshawna]

Hello, I have turned permissions on and off several time with no change. I have a Google Pixel with Android Pie .

[LanuzaFitbit]

Hello @danshawna.

Thanks for letting me know that you have already tried that. 

I will be passing this information on to the rest of the team. The moment we have any news or updates on the matter I'll be sure to let everyone know about it.

Let me know if there are any further questions.

[Innob]

I'm having the same issue!  Google pixel 2, Android 9 pie, and Fitbit version 2.78.

[lpendy]

Same issue here. Charge 2, app v2.78. All permissions enabled. Reinstalled three times. No go. SMS coming through fine.

[LanuzaFitbit]

Welcome to the Forums @Innob.

Our team is aware of the situation with the call notifications showing as unknown on Android Pie. As soon as we have any news on the matter we'll be sure to let everyone know.

Be sure to visit one of our Discussion boards. Lots of different topics to talk about with other users.

Let me know if you have any further questions.

[ferrocene]

When receiving calls, my Fitbit used to show either the caller (if they were in my contacts) or the number of the caller. Now, no matter what, it shows the caller as unknown. Text messages show up correctly.

Things I have tried to fix this:

- Made sure everything is up to date and synched.

- Restart app

- Restart BluTooth

- Uninstall/reinstall Fitbit App

- Make sure Notifications are fully enabled

I've read a bunch of articles on this and have tried all the suggestions I can find. Nothing has worked. What else can I try?

[LanuzaFitbit]

Welcome to the Forums @ferrocene.

Thanks for trying all of those steps prior to posting and sharing them with us.

In this case I'd like to ask some questions to better understand what is going on:

• What Android version are you running?
• What phone do you have?
• When did this start happening?

Look forward to your reply.

[ferrocene]

I am running Android version 9 (Pie) and I have a Pixel 2. I'm not completely sure when it started happening. I think maybe about six weeks ago. There was a Fitbit app update that started a bunch of weird things happening (my step count would always reset to zero any time I opened the app, stuff like that) and I was waiting for another update to fix the issues. There has since been another app update that fixed the weird step issues, but this has not gone away, so I started actively trying to figure out what was up.

Thanks for getting back to me so quickly!

[wardenllama]

I am also seeing this issue with a pixel 2 on android pie. Mine started when the phone was updated. It seems pixel 2s did not get fixed with the most recent fitbit app update (Version 2.78). I am hoping something is being done about this. I too have tried all the fixes you mentioned above and then some like re-adding contacts from a back up CSV file, and soft resetting the charge 2.  

[analshah89]

I have just bought a Fitbit Versa and I have paired it with my Google Pixel 2 Xl which is running on Android Pie. whenever I get a incoming call, Watch shows "unknown caller" even if the caller's number is stored in my contact list. I have tried modifying the option of permission on my android device but it does not solve the issue. Application update is also not available. Please advise if some is facing the same issue and able to get rid of it

[SunsetRunner]

Hi @analshah89. Your Google Pixel 2 XI is not on the list of Fitbit supported devices. Now this simply means that Fitbit has not tested this particular model for compatibility. In many cases I’ve seen, unsupported devices may still work, but you may not be able to take advantage of all the capabilities. In your case, since you seem to have done a good job of trouble shooting, I would guess that caller ID is one of those capabilities. Sorry. I wish I could help more. Perhaps someone else with this phone will respond. Have you tried searching the Community Forums? 

[LanuzaFitbit]

Hello @wardenllama and @ferrocene.

Thanks for bringing this up. Please know that our team is aware of this situation with Android Pie. At this moment we do not have any updates on the matter but we'll be sure to let everyone know the moment we do.

Feel free to let us know if you have any further questions.