03-13-2016 20:02
03-13-2016 20:02
Answered! Go to the Best Answer.
03-14-2016 08:31
03-14-2016 08:31
@hawkyou Voice cues function through the application when using MobileRun, so if you're looking to use voic cues, you'll have to initiate an activity through the app as opposed to the Blaze.
Learn more about MobileRun here. The formula for voice cues is doing your preferred activity with the device, and using Track Exercise > Stopwatch Icon > Start on your app (this is the workflow for iOS, and is similar to Android as well).
03-13-2016 22:21
03-13-2016 22:21
03-14-2016 07:26
03-14-2016 07:26
@hawkyou A warm welcome to the Community! Please make sure that you're doing this procedure to set the run cues that you will get in your Blaze.
Hope this helps. Keep me posted.
Want to get more active? Visit Get Moving in the Lifestyle Discussion Forum.
03-14-2016 07:30
03-14-2016 07:30
@hawkyou In addition to @SilviaFitbit's point, it's also important to note that voice cues will be heard on your phone when using MobileRun, as opposed to on-device exercise modes (Blaze does not have a built-in speaker, so you won't be hearing much of anything on the device, really).
Hope this helps!
03-14-2016 08:26
03-14-2016 08:26
03-14-2016 08:27
03-14-2016 08:27
03-14-2016 08:31
03-14-2016 08:31
@hawkyou Voice cues function through the application when using MobileRun, so if you're looking to use voic cues, you'll have to initiate an activity through the app as opposed to the Blaze.
Learn more about MobileRun here. The formula for voice cues is doing your preferred activity with the device, and using Track Exercise > Stopwatch Icon > Start on your app (this is the workflow for iOS, and is similar to Android as well).
03-14-2016 09:15
03-14-2016 09:15
Got it! And it's pretty crazy that you can't use your $200 Blaze to activate this when selecting Walk, Run or Bike.
03-18-2016 01:48
03-18-2016 01:48
@EmersonFitbit And how do you get the watch to display all the stats in real time when doing a mobile run? Beacause I need both audio cues and stats on my wrist.
03-18-2016 12:40 - edited 03-18-2016 12:47
03-18-2016 12:40 - edited 03-18-2016 12:47
I believe the link @emersonFitbit posted will explain this. But before you hit go, turn voice cues on, then adjust the settings.
03-22-2016 08:42
03-22-2016 08:42
It doesn't need a speaker. If it can control music, presumably it can add voice cues to to the music that is being played, like other devices do. It might need Fitbit to rethink their architecture a bit.
03-22-2016 11:30 - edited 03-22-2016 11:35
03-22-2016 11:30 - edited 03-22-2016 11:35
If you look at how the Blaze controls music, it is acting as a remote keyboard, ie just a switch. Stop, go, forward, back, vol up, vol down.
The other devices dont add voice cues to the music, they speakup over the music, and a lot of music players will pause when another app wants the speaker.
As some have suggested that it might be possible for the Blaze to tell the Fitbit app to do the voice cue. This would require new firmware in the Blaze, and an updated Fitbit App.
03-22-2016 12:14
03-22-2016 12:14
03-22-2016 12:28
03-22-2016 12:28
That's what I was thinking. The ideal would seem to be getting the voice cues no matter whether you're using the Fitbit app or the Blaze. Perhaps the Blaze could have a more communicative relationship with the Fitbit app: it could be the 'controller' for it, stopping and starting the run, and the app could then carry on giving cues as normal.
On an Apple Watch, you have (for example) the Runtastic app on the watch, and the app on the phone runs on the background. The watch isn't connected to the headphones, the phone is. But yet, the voice cues come through. I'm thinking the watch app tells the phone app to do it.
Get your thinking caps on, Fitbit 🙂