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!
08-24-2017 07:51
08-24-2017 07:51
I wasnt connected to classic for at least 1 week n seems to have started getting notification once connected to blaze classic. Try it. What have u gotyoloose. Connect to classic n wait
08-24-2017 07:54
08-24-2017 07:54
You got it...what do I have to lose? Nothing! Thanks!! 🙂
08-24-2017 12:26
08-24-2017 12:26
10-02-2017 10:09 - edited 10-02-2017 10:10
10-02-2017 10:09 - edited 10-02-2017 10:10
I just bought the Galaxy S8+ yesterday, just for the fun to try something new. I gave my "old" iPhone to my wife.
While with the iPhone I never had any problem with the Blaze neither with my car (a Volvo V60) sound system as soon I paired the S8+ my problems started. Audio dropouts in my car, bad connectivity during calls, no notifications in the Blaze, long (looooooong) syncing times. Nothing seems to be working as usual. So I don't think this is a Fitbit problem, it's Samsung's.
In other forums on the internet there are literally hundreds of people having issues with the bluetooth implementation of the S8.
So right now I'm returning it to the store (hopefully with a refund) and going back to the ugly, old, but reliable iPhone.
¡Never ever Android again!
10-02-2017 10:16
10-02-2017 10:16
@SunsetRunner before the phone was goven to the wife, did you remove the tracker from the phones bluetooth settings?
10-02-2017 10:20
10-02-2017 10:20
¡Yes of course!
She has a Blaze too, so we removed everything from the phone before a hard reset operation. She has no problems at all with her Blaze and the iPhone neither with her car sound system. Bluetooth works just fine.
So I maintain my hypotesis it's the S8's Bluetooth implementation.
10-02-2017 10:25
10-02-2017 10:25
I don't have an issue with anything Bluetooth related except for the Blaze. My car (2015 Toyota Rav4), my old Gear S2, my Bluetooth speaker and my Bluetooth headphones - no issues.
10-08-2017 22:53
10-08-2017 22:53
I'm going nuts here too... It was working fine for a few weeks, then the dreaded battery drain issues resumed and notifications died and bluetooth audio has been stuttering on some devices again - such as my car...
Any luck in any discernible pattern on how to resolve this, at least temporarily? Fitbit have just washed their hands of it by Samsung need to release an update - but who knows how long that will take...
10-17-2017 07:47
10-17-2017 07:47
Did you manage to solbe this somehow? I have the same Issue and it seems that Bloutooth 5 in S8 is not properly managing more BT connections. I guess this should be fixed in S8...
On the other hand since using S8 the battery lasts 2 days less than before...
10-17-2017 08:30 - edited 10-17-2017 08:31
10-17-2017 08:30 - edited 10-17-2017 08:31
I replace my Blaze with the new Ionic tracker, and guess what? No issues with sync, notifications, neither car's bluetooth at all!
Originally, my first thought was it's a Samsung's problem, but I did connect my old Surge tracker during the weekend and surprise: it has no problems either!
So I tend to think it is a Blaze problem more than Samsung's.
So, no more Blaze for me until I get a new iPhone...
10-17-2017 23:58
10-17-2017 23:58
10-18-2017 00:07
10-18-2017 00:07
Here is the thread where Fitbit states it's a Samsung Issue:
10-24-2017 15:25
10-24-2017 15:25
it isnt the android... i had an S7 edge that fully connected both to blaze and blaze classic. the blaze will not fully connect to the S8+
you may as well just dump the fitbit instead of blaming a device that hasn't been fully integrated into the firmware on a 3 year old tracker... Fitbit just does not care to update their stuff fast enough to include the stuff it needs. why will the S8+ not fully sync with the blaze (not just classic, but both blaze and blaze classic)? who knows. it isnt like android 7 is much different between the S8 and S7...
i have no issues with my S8+ and blaze other than it wont fully connect on bluetooth (only the classic). so dont blame the phone for something that isnt the phone's fault.
10-25-2017 14:09
10-25-2017 14:09
11-13-2017 07:38
11-13-2017 07:38
Still no notifications working for me with the S8 after the update. Any ideas when this will be resolved. Each time I call Fitbit I get a different response. One went as far as to tell me that my device is defective, keep in mind it works perfect except for receiving notifications. Of course my warrenty us up so I would have to purchase a new device. Help please !!
11-13-2017 08:34
11-13-2017 08:34
Same issues for me. Have the Galaxy S8. Syncs fine with the phone, but no notifications and most importantly won't connect to my phone to track GPS during my runs.
Exhausted all the fixes I could find (hard-stopping app, restarting both devices, updating everything, making sure all notifications and location services are allowed) and still no luck.
I just keep getting the "Check Fitbit App" when I try to connect for my runs.
I'm wondering if any Galaxy S8's can connect and are working fine or if this is 100% of all Galaxy S8's.
Ed
11-13-2017 09:09
11-13-2017 09:09
11-13-2017 11:27 - edited 11-13-2017 11:27
11-13-2017 11:27 - edited 11-13-2017 11:27
See my post here.
11-13-2017 12:59
11-13-2017 12:59
I just got my Blaze today and I've been trying to get notifications pushed from my Galaxy s8+. No luck. Customer support basically said that there are some issues with Galaxy users and that they are working on it. from what I can see on this and other forums, this has been going on for a while and I doubt they will find a solution. Should I just return my unit?
11-13-2017 13:01 - edited 11-13-2017 13:02
11-13-2017 13:01 - edited 11-13-2017 13:02
If you really want the notifications, yes. It's been going nowhere fast.
It's an inconsistent issue. Some people got it working. Others, like myself, nothing.