help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unknown Caller ID

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎10-06-2019 13:51 - last edited on ‎10-07-2019 13:28 by Fitbit Moderator

‎10-06-2019 13:51 - last edited on ‎10-07-2019 13:28 by Fitbit Moderator

I still get Unknown Caller when phone calls come in. It worked on Android 8. Currently, after missing a call, the fitbit tells me, correctly, who the call was from, but during the actual incoming call it shows Unknown Caller.

 

You guys keep marking this as fixed, but it's not. Updating the app, uninstalling and reinstalling, disconnecting Bluetooth... Nothing works. You have previously confirmed it's a bug and it's been a year. Are you ever going to fix this? Stop marking it resolved, it's not.

 

When will you actually fix this? 

 

Galaxy Note 8, Android 9, latest fitbit as of today. 

 

Moderator edit: Subject for clarity 

Moderator edit: Format 

Best Answer
3 REPLIES 3

‎10-07-2019 13:27

‎10-07-2019 13:27

Hello @Gomcse, it's nice to see you again participating here in the Community Forums, welcome back.

 

Thanks for bringing this to my attention and for all the details that were shared in your post, totally understand how frustrating this matter can be for you. Just as per previously mentioned, we are aware of this situation and working towards a resolution as soon as possible, therefore, your understanding and patience while we work to resolve this is appreciated.

 

Keep in mind that the mobile device that you're currently using, which in this case is a Samsung Galaxy Note 8 is not listed as a compatible device with our products and services, therefore, the notifications feature can be affected.

 

Let me know if you have any additional questions.

Best Answer
0 Votes

‎10-07-2019 15:07

In response to RicardoFitbit

‎10-07-2019 15:07

Really? It worked before the Android 9 updates. The #1 Android phones on the market are not compatible with fitbit? Do you see a problem with that statement? My issue with the regular answer we see from fitbit, "we're aware of it and working on it," go for literally years without resolution. That's a serious marketing and customer service problem. 

Best Answer
0 Votes

‎10-07-2019 15:18

In response to Gomcse

‎10-07-2019 15:18

Your reply is appreciated @Gomcse.

 

I'm aware that some users are and were able to use non-compatible mobile device with our products and services, however, due to Android, Fitbit app and device updates we cannot ensure that the notifications feature will work as intended, this is the reason why we always recommend our users to use compatible devices to avoid any connection difficulties. 

 

Thanks for the input that was shared in your post, if I receive an update regarding this I'll post it over here to keep you updated. 

 

Don't hesitate to contact me back if you need anything else. 

Best Answer
0 Votes