Android app incorrectly recording walks as runs

[Fitzgabbro]

Whenever I try to record a walk in the android app, it will instead start to record a run. How do I fix this?

[Rich_Laue]

Yes this is currently a known problem, the accepted solution is to wait for the developers to fix the issue.

A possible work around would be to side load an older version of the Fitbit app, maybe try version 2.82

[LanuzaFitbit]

Hello @Rich_Laue, @MontenegroMick and @BobbyDinSC.

Thanks for sharing your experience on the matter.

At this moment we do not have any details on the matter but we will be sure to let everyone know as soon as we have any news on the matter.

Feel free to reach out with any other questions.

[Hakkio]

Recognize the same. When using gps tje distance logged in not correct. Zoom on the actual walking path i see it does make z movements on several spots on the track. Why this happens i dont know,lookes like new behaviour.

[neilltupman]

I've had the same issue for weeks also, the walks I've been doing for 6 months are now being logged as runs when I track as a walk from the app. Posting to follow the thread in the hope that Fitbit get this resolved soon.

[neilltupman]

Have gone through my exercise records and have narrowed it down to when the app started recording runs instead of walks -  January 17th. If only we could roll back the app to an earlier version.

[Rich_Laue]

With Android, it is fairly easy to roll back an app a the hardest part is to find an older release from one of the app archive sites.

[the3amigos]

Hakkio, I don't think the incorrect tracking is new. Mine has been doing that since this past August, if not earlier. I'm seriously considering looking for another app for tracking but don't like the idea of installeing *another* app on my phone. PLUS, I think it's wrong to have to "work around" something that's supposed to be an integral part of the Fitbit app.

[orlaxmurray]

Thank you for putting that so clearly  I am having the exact same issue  Fitbit don't seem to have offered any solutions unfortunately  

[orlaxmurray]

The problem isn't with the autorecognise, it's with the manually selected walk on phone. My autorecognise on Charge 2 is switched off for run and on for a walk and it still logs a manually selected walk as a run  

[orlaxmurray]

It appears the problem didn't start occurring until after the update. Also the solution you've suggested has been suggested several times already with no success. 

[Rich_Laue]

@orlaxmurray there is only one solution to fixing this issue, we have to wait for Fitbit to fix the app, this is not something a user can do.

Yes by manually starting an exercise, through the app or the tracker the auto detect function gets disabled.

By starting the walk from the Charge 2 your walk will be labeled as walk, and if you have the phone with you, the Charge 2 will use the phones GPS to restore your route.

There really is only one workaround for now and that is to use the multisport function mode on the Tracker itself. See question to on adding walk to the tracker

How do I track my workouts with my Fitbit device?

Track your workouts in real time with the Exercise app to capture in-depth activity stats.

[mitaerik]

Thank you for your answer, just have to wait and hope it Will work soon then. I am from Sweden and the problem is wideword.

[Rich_Laue]

Please remember that with the Charge 2, Ionic, Surge, Blaze,, and Charge 3 the walks can be correctly recorded as walks by using the tracker and not the app

[dasboot]

I own the Blaze.

Recording 'walks' on the watch itself is not an option.

[Rich_Laue]

Yes @dasboot you do have, as mentioned in my last post, the option to record a walk is available for the Blaze. If you want to add Walk, which is not installed by default, please follow the link to the FAQ I provided in the post above. See question two.

[MattFitbit]

Hi all. Thanks for taking the time to provide descriptions of what you are experiencing around this issue. 

Our team is still working to identify a root cause on this and I appreciate your continued patience as we work towards a resolution. I don't have any additional information to share out at this time but I will be sure to keep you posted as updates become available. 

@LanuzaFitbit @Rich_Laue Thanks for the assistance! 

[Maeday85]

Mine has done that the last couple walks as well 

[Hfunk23]

Just did a chat with Fitbit support and they told me that my Google Pixel 3 is not considered compatible so that issues are bound to happen. I have a Charge 3 and didn't start having an issue with it incorrectly logging runs until after January 17th so it's possible an update for Fitbit made it incompatible with newer Android phones. The chat person also told me to post in the community because the moderators will see it here but no acutal fix unfortunately. 

[Rich_Laue]

Not really @SunsetRunner  the problem with Android phones off that there is no standard hardware, and no consistent Android version, that is why many companies including Garmin release a list of what phones have been tested and found to now work.

Fortunately many phones share the same hardware and thus even without testing do work 

[SunsetRunner]

I stand by a flawed product implementation/design. If GPS should have been included in a device to avoid the Android inconsistencies, then so be it.