04-05-2018 13:57
04-05-2018 13:57
Today my Fitbit recorded 15,000 steps and zero-km, it has been like this for a few weeks. In my Activity History it seems it has been recording my distance as N/A almost every day for months. I have checked my stride length, it is set to 700mm. My phone is a Sony Android, Fitbit is a Charge 2, Bluetooth is on, GPS is on. I am really fed up with Fitbit working for a while and then stopping working, it is really tedious to have to keep an eye on it to check it is working, restart everything when it isn't, and to to keep having to log in here and troubleshoot it every couple of months. Anyone got any suggestions as to what is up this time?
04-06-2018 09:50
04-06-2018 09:50
I went on a 15,000-step walk today and over about 2 hours, apperently I traveled 0.02km. It looks like my old problem (link below) has come back, but it my be a new problem. The solution last time was to wait for an update that covered my phone, that happened about 1 year ago, now I am back to where I was before. I am using the same phone and same Fitbit. I restarted both my phone and my Fitbit before I started my walk, I made sure I had wireless coverage, that the GPS was on, that Bluetooth was on, that the Fitbit and the phone were talking to each other... I'd be really grateful for some input here.
https://community.fitbit.com/t5/Charge-2/Charge-2-is-not-longer-working-with-phone-s-GPS/m-p/2126962
04-07-2018 21:15 - edited 04-07-2018 21:17
04-07-2018 21:15 - edited 04-07-2018 21:17
I'm not sure if this explains your case, but:
For an auto-detected walk, the distance in the Activity Log is not calculated. However I think the distance is included in daily total. I don't know why it is this way, but if you start and stop the walk with the side button, you should get a distance in Activity Log.
04-07-2018 23:31
04-07-2018 23:31
Hi, Thank you for your reply. This is not auto-detected activity, these are logged activities. I am going on a hike (for work) today and will log that as an activity, as I always do, and then show you the result.
04-08-2018 06:44 - edited 04-08-2018 06:49
04-08-2018 06:44 - edited 04-08-2018 06:49
So here is the result of today's walk... it tracked location accurately but only for about 1/3 of the walk. It got the time right, 57 minutes. As you can see, it measured the distance as zero-km. I very deliberately did not touch the phone or the Fitbit at any point on the walk, just at the beginning and end. The location data appears to have kicked in after I had been going for about 20 minutes. Heart rate and everything else sees to be fine. The phone has no access to Internet of any sort at any point on the walk, it's a very rural location, but this was not a problem in the past.
04-09-2018 01:03
04-09-2018 01:03
Anyone... ?
04-09-2018 10:48
04-09-2018 10:48
Here is today's walk / run. What I actually did is in yellow, start and finish at the same location. Everything seems to have been recorded correctly except location / route / elevation. Internet is available to the phone for the entire route, so it is not that. I don't know what I did to break it about 3 weeks ago, and I don't know why it is now recording some of the location data when it was recording none.
Please help!