Main Goal Widget does not work correctly when set to distance.

[12HourWalker]

When i try to use the phone widget for main goal it will work perfectly on any setting EXCEPT distance. When I set it to display distance it always shows a value that is 1.6 times my actual distance travel with or without GPS enabled. I have already adjusted my step length and I get a pretty accurate distance in the app, but the widget is always off by 1.6X my measured distance. I think something is wrong with the distance algorithm for the widget. Can somebody please verify this? I am using The Blaze on my brand new Motorola Droid turbo 2. Thanks in advance for any replies.

[AlejandraFitbit]

It's great to see you around @12HourWalker. Could you please provide me with a screenshot of what you are seeing? Since so far I know, you can only have widgets for steps. In the meantime, you can check if your app is updated by following the instructions provided in the How do I update my Android Fitbit app? post.

Hope to hear from you soon. 

[12HourWalker]

I updated my Fitbit App just 2 days before posting because they released a fix for the Blaze (Classic) Bluetooth which previously could not connect to the new Motorola Droid Turbo 2 for music control. It was well documented in a support thread which I posted in. This update fixed that problem. 🙂 This Widget is for "Main Goals" which works properly for "steps" "and all the other main goals. When my main goal is set to distance though it give erroneous values. I have done the math and it is consistently off by a factor of 1.6 times my actual distance reported by the dashboard, the tracker, and the website dashboard. It should be noted that 1.609 is the conversion factor between miles and kilometers and this appears to be approximately the same factor I am experiencing. It could be possible that someone acccidently left a metric conversion factor in the code for the widget.

[Rich_Laue]

@12HourWalker it sounds as if you know what is going on. I just tried it myself and find the widget off by the same 1.59.

So let's call @AlejandraFitbit back and have her open a case on this. 

[12HourWalker]

I'm still waiting for @AlejandraFitbit to respond with an actual "we will look into fixing this" rather than suggesting that I do something to rectify the situation. Please give me a reason to believe a fix is in the works.

[12HourWalker]

Ok it's been 3 weeks and no replies. Does anybody know where to go from here? @AlejandraFitbit ???

[12HourWalker · Accepted solution]

Ok so it's finally been fixed. I'm not sure which update did it, but my widget now reports the correct distance. Thank you to whoever it was that read this and found the fix. 🙂