10-28-2019
15:00
- last edited on
10-29-2019
15:37
by
RicardoFitbit
10-28-2019
15:00
- last edited on
10-29-2019
15:37
by
RicardoFitbit
I have recently moved over from IOS to Android and now my cues whilst I am out on a run dont report accurate distances on my Fitbit Blaze. Today I ran for 6km in a time of 33mins when I look at the recording on the app it only shows 5.12km. I have to say I think this is correct judging by previous runs, but the split time cues were indicating I was running much faster then that recorded on the splits page, never had a problem with this when I used my iphone on IOS.
Has anyone any idea what is going wrong and what i could try to sort it out.
Moderator edit: Subject for clarity
10-29-2019 15:36
10-29-2019 15:36
Hi @Bankfield88, welcome to the Community Forums, thanks for bringing this to my attention.
I appreciate the information and details that were shared in your post. To better assist you with this, can you please let me know which Android mobile device are you using? When was the first time you experienced this and how many times since then? Does this occur with specific exercises or just with one of them? If you haven't already done so, please restart your Blaze and try the following steps:
Keep me posted and let me know if you require further assistance.
10-30-2019 01:24
10-30-2019 01:24