08-22-2018 12:47 - edited 09-06-2018 16:53
08-22-2018 12:47 - edited 09-06-2018 16:53
Fitbit Update: 9/6
Everyone, please make sure you are enabling the Fitbit app permissions under Settings of your Android device. You can go to Settings > Apps> Fitbit app > Permissions and make sure you have it toggled on.
Since I've received confirmation that this has been resolved with the latest update to the Fitbit app, version 2.78, I will be closing this thread. If you come across this issue in a future instance, please create a new topic on the forum and reference this one as the issue. Thanks for all your patience as we worked to get this resolved.
Fitbit Update: 9/5
Hi, everyone - Yesterday on 9/4, we started the release of the Fitbit for Android app version - 2.78. As with all our Android app releases, it is a slow and gradual release until it is completely out to everyone. You should all see it available sometime this week. Once its available to you, you'll be able to download it from the Google Play store.
This app version contains fixes and improvements for calls being received as "Unknown Caller." So please download it once you see it available and let me know here in this thread how it goes. I really appreciate everyone's patience! I'll stick around to hear some confirmations that the fix worked.
Fitbit Update 08/22/2018: Hi, everyone!
I wanted to let you know our team is aware that some of you are seeing "Unknown caller" on your Versa/Ionic watches since updating to Android Pie (9.0).
They are already investigating the issue and I will let you know when a fix is available. Thanks for reporting this here on the Community.
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
Answered! Go to the Best Answer.
09-05-2018 12:16 - edited 09-05-2018 12:17
09-05-2018 12:16 - edited 09-05-2018 12:17
Fitbit Update: 9/5
Hi, everyone!
Yesterday on 9/4, we started the release of the Fitbit for Android app version - 2.78. As with all our Android app releases, it is a slow and gradual release until it is completely out to everyone. You should all see it available sometime this week. Once its available to you, you'll be able to download it from the Google Play store.
This app version contains fixes and improvements for calls being received as "Unknown Caller." So please download it once you see it available and let me know here in this thread how it goes.
I really appreciate everyone's patience! I'll stick around to hear some confirmations that the fix worked.
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
06-16-2018 19:21
06-16-2018 19:21
I have the Versa peered with my Pixel 2 XL. When I get an incoming call, it always shows up as Unknown caller on the Versa. If I miss the call, it will eventually show the name of the person who I missed the call from in the notifications. But when I am actively receiving a call, every caller is an Unknown caller on the Versa. It is nice knowing who is exactly calling you. Suggestions please?!
06-16-2018 19:29
06-16-2018 19:29
Unfortunately I cant see your phone on the Supported devices list so that is probably why it is not working correctly. In any case have a look at THIS Help Article on troubleshooting notifications. There may be something there that helps you. Let us know how you go
Helen | Western Australia
Want to discuss ways to increase your activity? Visit Get Moving in the Lifestyle Discussion Forum.
06-16-2018 20:07
06-16-2018 20:07
I tried all the steps in the Help article you mentioned, but no luck...
06-22-2018 07:17
06-22-2018 07:17
It's unfortunate that Google's flagship device of 8 months still isn't on the supported list. There have been far too many bugs with this watch since release.......
07-05-2018 09:06
07-05-2018 09:06
Hi all,
I am using Pixel 1 currently running Android P DP4, and my incoming calls always show as "unknown caller" even though it displays the name correctly on my phone. Is there any way to resolve this? Having a call notification is useless if it always says Unknown Caller.
Thanks!
07-05-2018 18:04
07-05-2018 18:04
I am having the same issue with the same phone running the same beta version.
07-10-2018 11:44 - edited 07-10-2018 11:45
07-10-2018 11:44 - edited 07-10-2018 11:45
I have this same issue...
Any resolve?
Using Versa, Pixel 2 XL on Android P
07-10-2018 11:47
07-10-2018 11:47
07-10-2018 12:29
07-10-2018 12:29
@Sawdizzle wrote:I have this same issue...
Any resolve?
Using Versa, Pixel 2 XL on Android P
@Djslimz no resolve on my end either 😞
07-11-2018 11:53
07-11-2018 11:53
same here .. when it turns to miss call İt can show the name What the hack ??
07-11-2018 15:03
07-11-2018 15:03
@BeyBaba wrote:same here .. when it turns to miss call İt can show the name What the hack ??
Yep. Really negates this feature if all calls show up as "Unknown caller".
07-12-2018 15:16
07-12-2018 15:16
Do we know if this x the same way in oreo?
07-20-2018 05:34
07-20-2018 05:34
@Rdwng1975 sorry, I do not know as I am running Developer Preview for Android P.
Does anyone else encounter this? This is really annoying!
07-30-2018 00:33
07-30-2018 00:33
Same here.
Pixel 1
Android P Beta
08-01-2018 20:43
08-01-2018 20:43
Same here .Android P beta on OG pixel .
Tested the watch on my wife's iPhone .Calls work fine. It's and adroid P issue I think .reinstalling the app and checking permissions and even repairing the watch many times is of no help
08-01-2018 20:59
08-01-2018 20:59
I see! Well Android P is set to be finalized next month so let's see if it gets resolved by then.
08-02-2018 03:00 - edited 08-04-2018 11:30
08-02-2018 03:00 - edited 08-04-2018 11:30
I've downgraded my Android to Oreo (On my Pixel) and now it works.
I'm in ongoing thread with customer support so I'll let them know it's an Android P issue.
Please all update them as well so they can work on a fix.
Thanks.
08-02-2018 05:31 - edited 08-02-2018 05:32
08-02-2018 05:31 - edited 08-02-2018 05:32
İ guess fitbit app is not ready for android P So not an android issue Fitbit Software development team needs to work harder
08-06-2018 18:07
08-06-2018 18:07
Has anyone tried to see if it is still broken on today's Android Pie release? I went back to Oreo and it works .