05-18-2016 17:26 - edited 05-18-2016 21:57
05-18-2016 17:26 - edited 05-18-2016 21:57
I've taking three bike rides with my new Blaze, on a hilly route that phone apps like Bi.Cycle show as around 400 feet of climb. However, the bLaze has shown zero the first two times for the climb. I thought perhaps it just wasn't implemented but today it showed 20 feet, so it is at least trying to show something, but its completely wrong.
Have others experienced this? I wonder if my Blaze is faulty.
05-26-2016 06:52
05-26-2016 06:52
I'm having the exact same problem. I did a ride yesterday that had 1178 feet of climbing my Blaze only indicated 100 feet! A routine ride I do has about 1800 feet of climbing and my Blaze indicates less that 100 feet. My bike computer is a Sigma that is several years old that that has an altimeter. I would think that the Blaze would be able to handle this without a problem as this is something other devices have been doing for years!
05-26-2016 11:04
05-26-2016 11:04
Its been a problem since Bike Mode was introduced about a year ago. Never fixed.
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze