07-16-2019 01:32
07-16-2019 01:32
I've been checking every few weeks to see if the Samsung Galaxy S10 is on the list of compatible devices. After 4 months since getting the phone on its launch date, it still isn't.
I recently saw a question on the forum about combatibility and the answer was that FitBit try to stay away from newer phones and can take 3-4 YEARS before becoming compatible.
I'm sure anyone on a contract phone would agree with me that in 3-4 years we'll probably have different phones altogether!
My sister and my mother both have the samsung S9+ which took about 5 months after launch date to become compatible with the app. My sister has the Charge 2 and my mother has the Alta HR so I dont believe the watches are the issue but the app is.
Can we petition for a quicker resolution on getting the app to be compatible with Samsung S10 devices?
07-17-2019 18:01 - edited 07-17-2019 18:02
07-17-2019 18:01 - edited 07-17-2019 18:02
Hello @llebpmacelocin welcome to the Community Forums, your post is appreciated.
Let me share with you that we're always working with new and recently released mobile devices to test them out and verify that are compatible with our products and services to add them to the compatibility list that was previously mentioned in your post. Thank you for sharing your thoughts and suggestions with us, the feedback that is submitted here in the Community Forums is always appreciated because we are always striving to improve the Fitbit experience with our products and the services we offer to our users. I recommend you to keep checking the compatibility list for any updates, also, if I receive any update regarding this specific device I'll be sure to post it here for you.
Let me know if you have any additional questions, see you around.
07-17-2019 18:44
07-17-2019 18:44
I bought my galaxy in April. I also had problems for days synching it to my new phone. It didnt work until I unpaired and deleted it off of the phone I switched from. This could of been a complete coincidence. I haven't had any issue until the new download a couple of days ago. Good luck! I know how frustrating it is.
08-05-2019 06:41
08-05-2019 06:41
How is this "solved?" 'Keep checking' is not solved.
My s10e syncs--well, as best as the Alta HR ever did sync (repeatedly refreshing to get my sleep, rarely, if ever tracking my workouts on its own)--but now I can no longer get alerts from my phone to the HR. I used that on my workouts to easily see what I needed to respond to immediately versus what could wait. Becoming irrelevant...
08-11-2019 06:27 - edited 08-11-2019 06:43
08-11-2019 06:27 - edited 08-11-2019 06:43
Most recent update to my phone resulted in call notifications on my Fitbit again. No identifying info and NO TEXTS received...
08-11-2019 07:53
08-11-2019 07:53
When will the fitbit zip be in sync with the samsung s10 phone.
08-23-2019 15:27
08-23-2019 15:27
Hello again, it's a pleasure to continue providing assistance with this situation, sorry for the delay in replying. It's nice to see both of you participating here in the Community Forums @Kaysha54 @Gamma19.
@Kaysha54 I appreciate the information that was shared in your post. To better assist you with this, can you please let me know when was the first time you experienced this? If you haven't already done so, I recommend you to check: How do I get notifications from my phone on my Fitbit device? to see that all the necessary requirements to receive notifications on your Fitbit are correctly configured.
After verifying this, please try the troubleshooting steps that are specified on: My Fitbit device isn't receiving notifications from my phone and let me know how it goes.
@Gamma19 My best advise for you will be to constantly check our list of compatible devices here. Please refer to the information that was shared on my previous post for more details about this.
See you around.
10-22-2019 12:05
10-22-2019 12:05
sure makes me very very very reluctant to keep upgrading your products. was interested in the versa 2 for myself, husband and daughter...BUT..............FOOL ME ONCE....