Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Fitbit Blaze First Long Run Was a Failure

Replies are disabled for this topic. Start a new one or visit our Help Center.

I had a training 8.3 mile run today in preparation for my first half marathon in April. I was excited to use my Fitbit Blaze for this long trek (long for me). How disappointing when I got back to find out for no reason at all the Blaze simply shut off half way up a hill after 6.39 miles. It's winter, it was 30 degrees out this morning and I had a long sleeve Under Armour running sweater on and "Quick View" turned on, which means when I turn my wrist it wakes when I raise my wrist. I am wondering if that's what happened, that it turned on and somehow a button was pressed somehow that thought the run was finished.

 

Thankfully my daughter was also tracking the journey, sans mapping, but we knew at least the mileage was 8.3 and just under 14 minute mile pace. I know I'll never win any medals with my pace and just started running at age 55. I'm really disappointed right now with the Blaze.

 

 

undefined

Best Answer
0 Votes
1 REPLY 1

This is an issue with the Blaze and it happens to me almost every time I run. I also have a Surge and have never had this behavior. The touch screen on the Blaze is so sensitive, that any thing touching the face will hit the Pause button and will pause the workout. There is no haptic feedback when this happens. It's also not possible to manually turn the face off, or to change to a screen that does not have the pause button displayed, or to require the hard button to be pressed to pause the workout.  I have to roll up my long sleeves and keep them away from the watch face. and I have to make sure that I don't accidentally brush my shirt.

 

It's disheartening to run 8 miles and find out that the fitbit decided to pause itself 2 miles into the run.

 

This should definitely be fixed, or I can't use the Blaze for running.

Best Answer