Syncing with Samsung A50

[dpatten]

I recently got a Samsung A50 phone. I have tried to connect my fitbit alta to the phone but it isn't working. Does Fitbit support the use of a Samsung A50 and if not when will it be supported?

Moderator edit: subject for clarity

[Hewitt4boys]

I was very happy with the way charge 3 worked with my last phone, but it will not sync messages to my a50.  I see thru this thread that most everyone is having the same issue.  How did you get yours to work??

[pennyfds]

My kid set it up for me.  Will check and get back to you.

[pennyfds]

I get Fitbit notifications and reminders but not phone call notifications.  You can swipe sideways and check to see if Notifications is set to On.

[pennyfds]

Going back to our troubleshooting, here are the things you need to do if your Fitbit Charge 3 can no longer receive notifications from your phone…

1. Make sure your tracker is within 20 feet of your phone.
2. Restart both your phone and your Charge 3.
3. Troubleshoot problem with only the tracker connected to your phone.
4. Ensure that Do Not Disturb (DND) feature is disabled.
5. Restart Fitbit app.
6. Uninstall and reinstall Fitbit app.
7. Reset Network Settings in your phone.
8. Factory Reset your Fitbit Charge 3.

[pennyfds]

1) Go to the App

2) Account

3) Set up device

4) Choose... Charge3 (or your device name)

4) Notifications

5) Set Calls to ... On; set Text messages to On; Calendar Events to On

hope this helps

[Sha26]

It is very unfair. It is not informed in the box or by the seller that it  is not compatible to all android. I have a samsung now and thought have upgrade it with fitbit but looks like it is worse.  Non of the review spoke about compatibilty

[Neilray67]

They don't seem bothered by the many comments on this thread. Perhaps they are hoping we will buy Samsung trackers?We certainly won't, having had our Fitbits for quite some time and linked to both earlier Samsung phones and other makes of phone!
Oh well such is the way of corporate organisations - sadly

[pennyfds]

I have now fully synced my Samsung A50 to my Fitbit.  It works fine.  I get a notifications when a text message is received and I can actually read the message on my fitbit once.  Just follow the steps I posted.  It should work.  It works with Carge2 and Charge3.

[pennyfds]

And that's because it IS compatible.

[pennyfds]

Oh I see now what is happening 😞  Thanks for alerting me NeilRay!

[CZK12]

The first message on this thread was May of 2019, now almost a year later they are still handing out the same non-answer as to either what is a reasonable work around or when are they going to find a way to work with this phone. If its unfixable then post that somewhere prominent so that we don't have to waste our time.

[Marya83]

I found this thread when chat support told me that my A50 is not compatible with my Versa 2. Like, what? The list of compatible Samsung devices is incredibly short, I was actually shocked.

Now, I actually do get my notifications come through after going through various notification settings. Checking the WhatsApp app on the list of notifications on the Fitbit app did not work, so tried unchecking it, then syncing, then checking the app, and syncing. And boom, notifications come through.

However, what doesn't' work is GPS tracking. It's 25% off in measuring the distance, although the map shows the correct route. This has a knock on effect on cardio fitness score etc, running distance comparison etc. Chat told me it's because the A50 is not compatible, so the GPS signal drops every now and then, leading to the map showing a consistent route, but the measurement of the length of that route is off. Seems like an easy fix would be to get the distance measured based on the mapped route, and not consistency of GPS signal. But then again, I'm not a software engineer, maybe this is impossible to do 🙄😂

This issue came up in the autumn 2019, about 5 months after I bought my A50, and has been consistent ever since. I thought maybe it was the old Fitbit Blaze causing the issue, but now my brand new Versa 2 has the same problem.

Very frustrated, and totally regret I didn't go for the Samsung watch like those above in this thread. Get your act together Fitbit or you'll lose your customers!

[Duhyathink15]

When will the galaxy A50 be supported? I see you were working on it in July.. yet I still have issues today, late april..

[Usernameplswork]

I have an a50 and I just got a new fitbit as a gift, it's been a year since this post and it still isnt compatible 

[Marie3101]

Actually, Fitbit DOES NOT not work on that phone AT ALL. 
It’s a Samsung Android.. higher than version 7 .. what makes it incompatible?

[Marie3101]

Why would you have to test all the phones that come out??  
Samsung A50..  an Android OS version 9... Garmin works on it, why not Fitbit? 

[SunsetRunner]

I updated mine, but it still isn't working. It is ridiculous that it's taking so long when so many people have had this issue.

[SunsetRunner]

It is not compatible as the FitBit respondent has stated. That doesn't mean it will NEVER work, but there could be issues. You are just lucky that it worked for you. It doesn't work for everyone because it is NOT a supported device.

[SunsetRunner]

OVER. Year later and it still isn't fixed.  This is ridiculous. I guess when this Fitbit goes out, because at this point, I'll just go with a Samsung watch that will actually work. It's ridiculous that I spent so much money on a watch that doesn't function with a phone even though all the other Samsung Galaxys I've had in the past that works fine.

[SunsetRunner]

I finally got my FitBit to connect, after trying everything else,  by doing a factory reset if the FitBit. (I have the Versa.)