01-26-2018
06:30
- last edited on
01-27-2018
05:30
by
RobertoME
01-26-2018
06:30
- last edited on
01-27-2018
05:30
by
RobertoME
I had the Surge which worked great with no issues but the band finally broke, "upgraded" to the Blaze a few weeks ago. Tracking for running is a joke. I know there is no built in GPS, but it connects to my android. TOTALLY INACCURATE. Shows me running places I wasn't even close to. Also, syncing is a joke. Set on all day sync, skips days, constant "syncing now" message then syncing error message...... I know what I'm doing, wifi is set correct, etc..... HUGE NON FAN and totally disappointed in this device!
Moderator Edit: Updated Subject For Clarity.
01-27-2018 05:29
01-27-2018 05:29
Hi there @JohnnyMacIII, welcome aboard to the Fitbit Community! Thank you for your feedback about the feature of the Fitbit Blaze.
Regarding the inaccurate GPS, it will depend also on external factors. Usually when the mapping is showing locations that you are near, is because the GPS signal was lost for a period of time.
So make sure your phone can identify your location and can track your location when you're not using Wi-Fi. Also keep the Fitbit app open on your phone or running in the background. Do not force quit the Fitbit app. A weak GPS signal can be caused by environmental factors such as tall buildings, dense forest, steep hills, or even thick cloud cover.
If you're still having difficulty, try these troubleshooting steps:
Now regarding the syncing issue I'm wondering if you have tried any troubleshooting step so far. Perhaps the following post might give you some help: Having trouble syncing? (here's how to fix this).
See you later. Keep me posted how it goes.
"Great things are done by a series of small things brought together.” What's Cooking?