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: 

No device found- versa 2 on samsung galaxy s10

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

‎01-11-2020 10:32

‎01-11-2020 10:32

I have been having syncing issues with my Versa 2 ever since the recent update. First it just took a very long time to sync, now every time I go to sync in the app, it tells me 'device not found'. I have tried turning my blue tooth on and off, restarting my phone, deleting the Fitbit app and un-pairing and re-pairing my Versa 2. I have done all of these multiple times. The ONLY thing that works is restarting my Versa 2. So now I am forced to restart the device multiple times a day, and sometimes even 5 minutes after i get 'no device found' again. This is along with getting no text message notifications on my Versa 2. Both my fitbit app and my phone are and have been up to date. How else can I troubleshoot this? I am forced to restart my fitbit 5-10 times a day. 

Best Answer
Labels:
1 REPLY 1

‎01-11-2020 15:25

‎01-11-2020 15:25

Hi @raiiny00 , besides iPhone users who have this problem after the update of Apple to iOS 13, I noticed that some Android users, mainly Samsung users (Tizen layer), also suffer from the same problem. But, the reason is different: it's caused by the recent update to Fitbit's newest Firmware Version 70.7.14. Fitbit is aware of this problem and is working on a fix. regards kuzibri

Best Answer
0 Votes