05-01-2020 16:51 - edited 05-01-2020 16:53
05-01-2020 16:51 - edited 05-01-2020 16:53
Yesterday it started mapping my route but then stopped after 0.4 miles. It still knew I went 7000 steps or whatever and I had walked for 30 minutes, but the map had just stopped. Today it thinks we did just over a mile, but we did almost 4. When we got to the top of the hill, I checked it, and it seemed to be catching up our distance, we were stopped but the distance numbers climbed from 0.8 to 1.6 just while I was holding my phone. This issue started just after the app crashing issue was fixed. Also, we have it set to do voice cues every 15 minutes and that hasn't happened either, despite the stopwatch working.
05-04-2020 15:56
05-04-2020 15:56
Hi @Berkana, it's nice to see you again participating here in the Community Forums! Sorry for the delay in responding your post.
Thanks for bringing this to our attention and for the details that were shared. 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 issue and how many times since then? Are you tracking the exercise with a Fitbit device or with MobileTrack? In the meantime I receive your answers, please try the following steps and let me know if the issue persists:
Keep me posted and let me know if you have any additional questions.