Galaxy S8 having Bluetooth problems, Lost Blaze Features

[ChiefNoJustice]

Moved from Galaxy S5 to Galaxy S8.  All features were working with S5.  On S8, I loaded the Fitbit App, and my Blaze is able to Sync.  However, now when I try to start a run exercise and connect to GPS, I get "Phone not found".  Through all the troubleshooting I have gotten it to the point of saying "Check Fitbit App".  Feels like I've tried everything I can find on the forums.

I am becoming convinced this is a problem with the Galaxy S8's Bluetooth functionality.  I have had problems with this phone on a couple other BT devices (car BT and stereo, and headset).  There is a thread on the Samsung support page that they admit this is a problem.  Hopefully Samsung fixes this problem with a SW update soon, so we can use the features we are expecting!

Just wanted to share my experience with Samsung S8 so others don't waste too much trying to troubleshoot Fitbit app or devices.

[AlejandraFitbit]

It's great to welcome you @ChiefNoJustice. Keep in mind that your phone needs to be compatible in order to communicate properly with your tracker. Samsung Galaxy S8 is not compatible yet. You can try to follow the instructions provide in the Having trouble syncing? post but I don't guarantee it will work properly, you can also keep an eye on our list of compatible mobile devices for any update.

See you around. 

[ChiefNoJustice]

After removing the Fitbit App from my phone, all the other Bluetooth problems went away.  This now definitely feels like an issue Fitbit can fix in their app.

Being that the Galaxy S8, is probably the biggest phone introduction this year, I would expect it is in Fitbit's plans to get it supported.  It should not be a trade secret to let us know when to expect our Fitbits to become compatible with our new GS8.  Can we get on a mailing list to know when Fitbit solves their end of the problem?

[jeffbe]

Our problem is with Samsung. The S8 has Bluetooth 5 technology, which is supposed to increase range and data transfer rates, but sadly it was not ready for prime time.  It was supposed to be backwards compatible with Bluetooth 4 devices, but is not.  There is an update in the works that is supposed to fix the issue.  

[ChiefNoJustice]

There is both a Samsung and a Fitbit element to this problem.  Sure, the Fitbit works on my old BT4 phone without any issues.  Sure, BT5 should be backwards compatible and be plug-in ready with all my old BT4 devices.  Garmin users are having the same problems as Fitbit users on GS8/8+.  Follow that logic and it seems like a Samsung problem.  

 . . . However, now that I have removed the Fitbit app from my phone, all my other BT4 devices are now working without issue.  I paired up a Samsung Gear Fit 2 (also BT4) with my phone and all devices are working as expected for 1 day so far.  On Friday, I had the Samsung rep at Best Buy load the latest GS8 OS build on my phone and it still did not resolve the Fitbit problems.  If Fitbit's only strategy is to wait around for Samsung to fix the problem, there's going to be a lot of disappointed customers for a long time.

Still feels like Fitbit owes it to their customers to state whether or not they are going to attempt fixing the problem, and when they intend to have the work complete.  

[FerdinandFitbit]

Hey guys @ChiefNoJustice @jeffbe! Great to see you in the Forums! As my friend @AlejandraFitbit mentioned before, it appears that the S8 is still not in the list of compatible devices, however, as you mention, the S8 is a very popular phone and I wouldn't say that it's not Fitbit's plans to make it compatible but just that this process could take a little while so it would be matter of giving it some time and I'm pretty sure it will work with all the other features in the near future.

Thanks for understanding and anything else, we're here to help!

[pwdiver]

I have the S7 Edge and my Blaze will not stay connected I did as you did at Bestbuy the fellow there downloaded the latest OS but my phone and Blaze dont like staying connected. My Samsung Gear S3 frontier has no problem it connect's as soon as Im near it.

[FerdinandFitbit]

Hi @pwdiver. Good to see you around!

I'm sorry you were having problems with your Blaze and your S7 not staying connected. In this situation, I would say this has to do more with the bluetooth connection itself between each device rather than the compatibility as most users are able to use their trackers without a problem.

Have you tried by any chance to set up your tracker as a new device? Before doing that, you could try to restart your tracker. You can easily do this by pressing the left and lower right buttons for 10-12 seconds. This will make your tracker to reboot. After that, restart your phone as well and then you can proceed to set up your tracker as a new device.

For this, go to the Account section at the top right corner on the Fitbit app and select the option that says "Set up a new device". Follow the on-screen instructions and once you're done, your tracker should be syncing without a problem.

Hope this helps and if you need anything else, let me know. I'm here to help!

[WesA]

I did not realize that the Galaxy s8 was not supported. This explains my issues I've been battling for the last few weeks. Connectivity is very hit an miss, very difficult to get it to sync. Notifications rarely work. I hate having to re-login to my app ALL THE TIME!

Hope Fitbit gets with the game here for sure. I love my Blaze, I don't want to have to buy a different watch, but that a lot cheaper than buying an older phone so i can use my tracker...

[FerdinandFitbit]

Hi there @WesA. Good to see you around! I'd say that is the reason why it has not been working properly. I'd expect our team to be already working on making this phone compatible as it's a very popular phone, however, I don't have a timeframe on when this will happen. Please keep an eye on the forums for more updates!

[JudeKnight]

I just feel that fitbit doesn't care about their customers at all. It's just like Microsoft I've been bullied by them. Paid out of my own pocket for a Samsung galaxy s8 and my blaze to get messed around by fitbit! Don't know what more I can do! 

[WesA]

I disagree! I think Samsung should have waited to release Bluetooth 5, or made sure it was completely backward compatible. There are no Bluetooth 5 devices and won't be for another 6 months maybe (if we are lucky). I think this is the price we pay for getting the jump on technology. I just wish my Blaze battery would last longer. I've managed to most other functions to work most of the time. 

I don't see how you can blame Fitbit. The phone is the new part of the equation. Clearly not Fitbits fault.

[JudeKnight]

So fitbit managed to miss the launch of the Samsung galaxy s8, the most hyped and eagerly anticipated phones in recent months and not get a spec to check compatibility to make sure their loyal customers were catered for? Just poor practice! Can't believe you feel like people should have to put up with the problems even though it has been known for some time. 

[WesA]

Can anyone name just one Bluetooth 5 accessory on the market? If you think Fitbit got it wrong, them so did every other company.

[ChiefNoJustice]

Unless you need a specification from BT5, why would anybody sell a BT5 device right now?  No way to sell a BT5 device if there is no phone on which it will work.  Right now you would only be able to sell your device to GS8/8+ owners, but any major phone release from here on out will include BT5, so the potential compatibility list will be increasing.  GS8 just happens to be the first major phone release since BT5 was ratified.

BTW, had lunch with a friend today that also recently upgraded to GS8.  Their Fitbit Alta also had connection problems, so I believe the problem is across all Fitbit products (mostly likely due to the SW and the App).  We have both moved to alternate Fitness devices that use BT4 and they work without issue.  

[JudeKnight]

It's not a point scoring exercise! I'm just saying that fitbit should have got this sorted sooner. Even if it might be the first product of the like.  There are likely to be more, I can see fitbit being left out in the cold and missing out on future purchases and loyalty. 

[Immer75]

have the same problem. had a old Pebble and that work`t just fine no problem at all, then i bought a Fitbit Blaze and no notifications works at all, bt goes in and out all the time. so there should be no problem for Fitbit to solve the problem becuse they bought Pebble and have the Pebble platform to work from !

[TWGator]

So, if I'm hearing all this right - I'm out of luck. My Blaze, that I have depended on as my only activity tracker and running partner, for close to a year, is worthless right now, because I decided to purchase a new phone?

Listen, I can appreciate that maybe there are problems on both sides of the Fitbit and Samsung fences. But having someone from Fitbit tell me to just sit tight and get to me when they can seems like a slap in the face. Right now, I have to figure out how to track my runs using something else. I can use another app, but the whole reason for purchasing the Blaze in the first place was that I could control my running apps from my wrist while my phone was safely tucked away. I don't have that capability right now, and it's a major distraction. 

I guess I have no choice but to wait. But anymore than a couple of weeks and that Gear 3 will start looking awfully tempting....