07-14-2017 08:06
07-14-2017 08:06
I recently purchased a Blaze, after downgrading from the Surge.
I can not for the life of me get my Samsung Galaxy S8 plus to connect with the Blaze to
be able to get notifications. After spending almost 45 mins between the chat feature on Fitbits website and on the phone with a tech. They determined that the Blaze's notifications do NOT work with the Galaxy S8. Seems like a cop out, why didn't they tell me that in the first 3 mins of talking with them?
Any solution to this? Anyone else have this issue, and resolved it?
thanks!
11-28-2017 11:27
11-28-2017 11:27
What I don't understand is that the Samsung s8+ is on the list of compatible smart phones and even shows notifications as an available feature. It would appear that FitBit did not actually do any testing of compatibility or we wouldn't all be screwed like we are. This amounts to false advertising regardless of whose side the problem exists on. We were all lead to believe we would have fully functional FitBits. Planning to return mine and get a Gear or 360. This is pathetic in this day in age.
11-28-2017 11:30
11-28-2017 11:30
So does this mean that with the Charge1 the issue between the Blaze and S8 didn't exist and this problem is unique to the Charge2? That's what it sounds like that you are saying.
11-28-2017 13:33
11-28-2017 13:33
I have a S8+ and I have gone through all of there troubleshooting including making sure that everything is enabled and always connected and it still will not work. Apparently this is a problem that FitBit knows about and is on Samsung's end not theirs. While I still love the device I wish I had known that before purchasing.
11-28-2017 13:35
11-28-2017 13:35
I got mine on Friday and it has never sent me a notification, not once. It is very frustrating! I had a FitBit Charge 2 before and it worked just fine with my phone. I'm not understanding what could be so different about this one now.
11-28-2017 13:37
11-28-2017 13:37
I checked that list myself and agree totally. I've had a Samsung Gear before and ended up giving it to my daughter. I use the FitBit app a lot and it was more user friendly than the Samsung app. I really don't want to return the Blaze but the fact that I could also get notifications on it was one of the reasons I purchased it.
11-28-2017 13:38
11-28-2017 13:38
I had a Charge 2 and it worked fine with my S8+ phone. There was never an issue getting notifications.
11-28-2017 15:21
11-28-2017 15:21
I give up have 8+ nothing but Bluetooth rejected by blaze have tried all the suggestions
11-29-2017 05:47
11-29-2017 05:47
@Steffa21 You are the only one that I have seen posting to these boards and on the internet in general that has had success. What did you do to make it work? This is a known issue in Samsung engineering. How old is your charge 2 and what version of firmware is running on it?
You may have the one and only holy grail.
11-29-2017 06:09
11-29-2017 06:09
@bskon I've had my Charge 2 since about the beginning of March and never had any issues with it connecting with my phone and giving me notifications. As far as the version of firmware that I have I'm really not sure. I just let it update when it needed too. Sorry, I can't be of more help!! That is why I am so stumped with the connection issue between the Blaze and my phone. I've never encountered a problem before and this is the third FitBit I've owned.
11-29-2017 06:28
11-29-2017 06:28
I had EXACTLY the same issue. Old blaze wasn't holding its charge but my S8 received notifications. New blaze holds charge but no notifications. Very frustrated.
11-29-2017 06:36
11-29-2017 06:36
I had a Surge I purchased in the spring. Worked great with my old Note 5. Then I got the S8+, had all the syncing issues and no notifications. I thought it was the Surge, so I bought a Blaze in September, same problems. Then it just magically started working in mid-October. But over the last week, it went back downhill, issues syncing and no notifications again.
So frustrating.
11-29-2017 07:17
11-29-2017 07:17
I got my blaze Sunday. I did every trouble shooting thing I could find on these boards to get it to work with the galaxy 8+. Nothing worked. Then Tuesday it started receiving notification in the middle of the night. It worked until about 2pm Wednesday. It's back to no notifations again. Also the blaze only holds a charge for a day. Such a waste of time and money.
11-29-2017 11:46
11-29-2017 11:46
11-29-2017 12:02
11-29-2017 12:02
Which phone do you have Rich?
11-29-2017 15:09 - edited 11-29-2017 15:11
11-29-2017 15:09 - edited 11-29-2017 15:11
You all should have read the other threads on this before buying your Blaze. Contrary to what Fitbit says and advertises, the Blaze is not fully compatible with the S8. It will not receive any notifications from your S8. I gave up long ago once Fitbit started pushing the blame game to Samsung. I mean, seriously? Why would Samsung really care if a Fitbit worked with their phone. What's in it for them? I'll also bet Samsung is working hard and spending money and time addressing Fitbit's problem? NOT!
What I think is terribly bad is that Fitbit still isn't warning customers and is still listing the S8 as a compatible. It appears that sales are more important than customer service.
My Blaze, which I got pretty cheap on eBay, will soon be going back on eBay. I will, however, in contrast to Fitbit, warn any potential buyer that the watch doesn't function with an S8.
At least my Surge is still working and fully compatible with my S8. A second new $20 band and it's just like new.
11-30-2017 04:54
11-30-2017 04:54
11-30-2017 11:48
11-30-2017 11:48
12-12-2017 20:01
12-12-2017 20:01
So I'm aware of the problems involving the battery drain of the Blaze and the S8/S8+, and notifications don't come through.
Do these same problems also include why I can't get the Blaze to connect to my phone's GPS for runs? It's very frustrating...and I'm starting to really regret the switch from the Charge 2. Everything I wanted to do with the Blaze, I can't, with a host of other problems.
12-13-2017 07:18
12-13-2017 07:18
Hey there @Main1988. Great to see you in the Community Forums! 🙂
I'm sorry you're having problems to get your GPS connected to your tracker 😕 I'd say this has to do with the known issues with the Samsung Galaxy S8 and S8+ as GPS connects through Bluetooth and this is the issue that has been detected. It seems like we'll need to wait for Samsung to release an update to get this fixed. You can find more information on this on this thread.
Thanks for your comprehension and anything else I can help you with, let me know!
Help others by giving votes and marking helpful solutions as Accepted
12-13-2017 21:41 - edited 12-13-2017 22:25
12-13-2017 21:41 - edited 12-13-2017 22:25
S8, India - I can confirm that the latest update to the S8 has fixed the bluetooth issue. I updated my phone 3 days back and have it hooked up to my Blaze from the last 2 days.
The issues seem to have resolved now -
- Notifications have started appearing on the Blaze
- Normal battery drain from the Blaze
- Can start a GPS based activity directly from the Blaze - Earlier it threw the "Phone not found"/"Check Fitbit App" error
The build number for the update I have is: G950FXXU1AQK7
Note: Forgot to capture a screenshot from my phone. Found a screenshot of the S8+ online.