07-19-2017 13:06 - edited 09-26-2017 15:58
07-19-2017 13:06 - edited 09-26-2017 15:58
Fitbit Update: 9/26/17
Hello, everyone! I wanted to make it known that I haven't forgotten about this issue with MobileRun. Our team is aware of this ongoing problem, however, I don't have a timeline for when there will be a fix available. I understand many of you are frustrated with this feature, and I hope to give you all more information soon. Thanks for your continued patience!
Just to be clear, this thread is for the MobileRun issue for when you initiate a Run/Walk, if you 'Pause' your activity and then 'Resume' after you finish, you will not see your map or some of your exercise data. Alternatively, this does not happen if you 'Pause' and 'Finish' your Run/Walk right away.
Fitbit Update: 7/20/17
Thanks everyone for providing the information requested about this MobileRun issue. It appears since the Android app version 2.43, users who initiate a MobileRun on their devices and later pause it at some point will not have all the data saved when syncing afterward. This data can include the map and distance data.
I really appreciate your cooperation and patience while our team works towards a resolution. I know many of you have been active on this thread and I want to make sure you know all your input has been very helpful in determining the factors. I will continue to update this thread when there is more information available. Thanks again for your help!
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
07-15-2017 01:00
07-15-2017 01:00
@Elliekennard wrote:Deleted. Although the title doesn't say this is uniquely related to the app use only (for those with no tracker), that is the case. I wish the title would be edited.
Well: "Missing MobileRun map/pace data, Android 2.44"
clearly states Android 2.44.
I contacted the support via mail and they again told me: "we are working on a fix, please be patient"...
For all the new people taking a look at the thread: the Android App does not record map, pace or other data, if you pause a run and continue it as of version 2.44+. If you just press pause and finish at the end of your run the data is fine.
It is android OS version independent. The bug is there since app version 2.44 and Fitbit does not care.
07-15-2017 01:16 - edited 07-15-2017 01:19
07-15-2017 01:16 - edited 07-15-2017 01:19
Correct. Fitbit don't care.
Rubbish after sales customer care.
But we all know we won't buy another.
And won't be recommending to our friends.
07-15-2017 04:29
07-15-2017 04:29
The title should be amended as versions 2.43 and above are affected. 2.42 is the last working version.
As I wrote previously, I don't mind if there's a bug or two from time to time - they're basically unavoidable. Taking over 4 months and 10 minor releases (and counting) to fix an issue breaking core functionality, however, is pushing it.
07-15-2017 08:40 - edited 07-15-2017 08:42
07-15-2017 08:40 - edited 07-15-2017 08:42
Did not pause app. Bike. Android 5.1.1. ZTE Prestige - N9132. Brand new Charge2. Fitbit App version 2.52.
07-15-2017 10:15
07-15-2017 10:15
07-15-2017 11:00
07-15-2017 11:00
Okay, so I tried it, but it worked fine.
In the app, when you are ready to finish the walk, the only choice I had was Pause. There was no Finish until I had pressed pause when there was both Resume and Finish. So I pressed Finish.
But the map is there just fine along with all data. Before I left on the 'walk' I reset my GPS using GPS Status app. I did not have cellular data turned on.
This seems to work better (okay, only tested once) than by pressing the option in the Charge 2 and selecting Walk.
Unfortunately there is no option to track bike rides using the app, so I am stuck with using the broken functionality of selecting it on the Charge 2 and hoping it saves some kind of map.
07-15-2017 11:49
07-15-2017 11:49
07-15-2017 11:58
07-15-2017 11:58
I'm not pausing, and I assure you, the bug is still there. Doesn't matter to me anymore, as I've decided I'm going to return it. What a P.O.S.!
07-15-2017 12:12
07-15-2017 12:12
07-15-2017 12:33
07-15-2017 12:33
Yup! Start, pause, resume, finish, map looks fine. Go to main screen, everything has disappeared from that walk. Map and all. As though it had never happened.
07-15-2017 13:39
07-15-2017 13:39
07-16-2017 01:46
07-16-2017 01:46
07-16-2017 03:00
07-16-2017 03:00
07-19-2017 10:27
07-19-2017 10:27
I'm having the same problem. Have you found a solution? Isnt it so frustrating. Gill
07-19-2017 10:29
07-19-2017 10:29
07-19-2017 10:35
07-19-2017 10:35
07-19-2017 10:38
07-19-2017 10:38
07-19-2017 12:18 - edited 07-19-2017 12:19
07-19-2017 12:18 - edited 07-19-2017 12:19
@don1000 wrote:
it will do it sometimes without pausing
Have not experienced this ...
What works right now for most people are these two fixes:
1. PiLesley Fix: Revert Fitbit App version via APK Mirror to pre 2.42.
2. My Fix: Do not pause runs.
Shame on fitbit for their support.
07-19-2017 12:21
07-19-2017 12:21
Thanks so much. Really appreciate your help
07-19-2017 12:28
07-19-2017 12:28