10-28-2017 21:42
10-28-2017 21:42
There are many many threads about how the blaze does not work correctly with the Samsung galaxy s8 and +. No notifications or connected GPS, and horrid battery life. How do things start working once added to the compatible phone list? Is it an app update, a firmware update to the blaze, or a server side switch that fixes it? Also how does Fitbit decide that a phone is now compatible? The s8 and + are now listed even though the blaze is a glorified step counter with zero "smart" feature that we paid for. Please remove the s8 and s8+ From the compatible phone list until you have solved the problem before you dupe others into buying tech that does not work as advertised.
10-31-2017 04:54
10-31-2017 04:54
Hello @goneeuro, good to see you one more time in the Fitbit Community! When a device is listed as compatible is when all tests of compatibility has been completed and we can guarantee the Fitbit app and features of the tracker will run with your phone as is expected.
Now you have brought to the topic some issues that has been reported regarding the functionality of the app and tracker in relation to the new Galaxy S8/S8+. I'm wondering if you read one of our latest updates about this matter? If you haven't please go ahead and take a look to this post: Battery drain/Notifications - Samsung Galaxy S8/S8+ for more updates.
Hope this helps and let me know if you have other questions.
"Great things are done by a series of small things brought together.” What's Cooking?
10-31-2017 05:32
10-31-2017 05:32
Yes. I have read every thread out there. Done every troubleshooting step. And still have issues. I was just trying to say that the S8 and S8+ should not be listed as compatible as there are still issues that prevent it from working with your devices. And the fact that fitbit is passing the buck to Samsung to fix this is just bad business. I have spent to much money with fitbit now that I feel trapped in your ecosystem. I have purchased the special edition gunmetal blaze, the special edition pink and gold blaze, the Charge2 and the Aria. Fitbit blames Samsung now, which makes zero sense to me. The blaze has the same issues across multiple platforms. Windows phone, Android, and iOS. How can fitbit say it's the phone when the phone works with all the other fitbit devices?