04-01-2016 14:50 - edited 06-29-2016 13:57
04-01-2016 14:50 - edited 06-29-2016 13:57
Update 4/12/16:
Hey all,
As of yesterday, the firmware update for Blaze should be available to everyone. As is common with initial updates, this version focuses on stability improvements and bug fixes. We're looking forward to delivering feature improvements with future updates so stay tuned!
Update 4/5/16:
I've addressed some things I've seen come up in this thread in a post I made here. Check it out!
Hey! While it is April 1st, the Blaze firmware update to version 17.8.104.1 is no joke. As usual, we're rolling out the update in waves, and we hope to have everyone updated soon.
This release includes the following:
Any questions, just let us know.
04-14-2016 19:28
04-14-2016 19:28
Has anyone noticed a change in the accuracy of the HR feature since the firmware update? Mine seems to be off my 10%-12% since the update...
04-14-2016 23:07
04-14-2016 23:07
Music control doesn't work 😞
Bought the Blaze instead of the Surge becasue of the music control functions. Tried restarting the device and the app and bluetooth on both side but still not able to connect with my music player. Please help?
04-14-2016 23:18
04-14-2016 23:18
04-15-2016 01:58
04-15-2016 01:58
04-15-2016 02:15
04-15-2016 02:15
04-15-2016 02:24
04-15-2016 02:24
04-15-2016 02:38
04-15-2016 02:38
I have tried to update my tracker, but it is taking ages to do so, I have twice left it doing it for over an hour but it just sits there saying " Updating tracker.." how long should it take ?
04-15-2016 02:56
04-15-2016 02:56
Fitbit says 10 minutes, I think they are being cautious, for me it was 8. It depends on the network connection.
If after a couple minutes of the progress bar not moving, I kill the app.
Ice also noticed that with the app up front on android, when the Phone goes into sleep the update fails, this is tyre same for most Windows and mac computers.
04-15-2016 04:15
04-15-2016 04:15
04-15-2016 10:40
04-15-2016 10:40
I have a Sole E35 and it does not recoognize it, but my Basis Peak did'nt either.
04-15-2016 15:35
04-15-2016 15:35
04-15-2016 15:53
04-15-2016 15:53
@mhgerhold the Sole is an elliptical machine, what is the 'it' that's not being recognized.
@Tkcmom when you say your Blaze is inaccurate, are you testing it during your free walk/run while outside? This is really the only time your garnered that the steps will be counted correctly.
04-15-2016 16:10
04-15-2016 16:10
04-15-2016 17:42
04-15-2016 17:42
04-15-2016 19:12
04-15-2016 19:12
04-15-2016 20:26
04-15-2016 20:26
04-15-2016 21:29
04-15-2016 21:29
@mandyjorn1978 there is a lot of discussion on your unsupported phone, do a search people have gotten it to sync.
@Tkcmom While I agree that anytime your walking, I went through your history to see what you ment by inaccurate. The only reference I see is "That's when I have the most errors. I have the freestrider fs9 and the blaze calculations are no where near the freestrider". Searching tells me it is an elliptical, this tells me that the miles will not agree with the Blaze, does tyre elliptical count your imaginary steps, as it counts your imaginated distance?
This is the reason I asked about free walking, since there is no stepping done on this machine.
04-15-2016 22:35
04-15-2016 22:35
04-16-2016 06:52
04-16-2016 06:52
04-16-2016 19:58 - edited 04-16-2016 20:00
04-16-2016 19:58 - edited 04-16-2016 20:00
Returned my Blaze today. After a VERY helpful exchange with Mario via e-mail support. I tried three 100 step tests where the Blaze recorded 67, 61, and 74; clearly failing to accurately count steps. Best Buy was good about returning the Blaze.
I saw the Alta when I was in Sam's Club tonight, and I decided to give it a try. Same problem as the Blaze. I'm a big guy (6'4") with a healthy stride (the Fitbit app estimates 31.5", but not sure about that estimate). I'm not going to wait. This one goes back tomorrow.
As a footnote, my Blaze was working well prior to a recent "upgrade" patch. When I checked it originally by manual count and against my Samsung phones tracker, it was close. I'm thinking the problem started with a patch. FWIW, my new Alta ran a patch first too.
I wish I knew why things went south with my Blaze. I may go back and try another new Blaze.
One final note: I could not possible have received more helpful and timely responses from Mario M. Regardless of what others may say, I give them A++++ for their online support!