MobileRun missing data after pausing - Android 2.43+

[AlessFitbit]

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! 

[anyutikins]

Well I suppose I'm glad it's not just me...

Set a personal best today and was hoping to sync to Strava the lovely map, distance and time displayed to me by the FitBit app. Pressed pause, then stop and finish. Went back to check it and *poof*, the map was gone. Shame as it was a random route just following my feet and I was curious where I'd been. Might as well have just used Strava directly.

Hope this gets fixed 🙂

[siris10]

That's what I've started to do as got fed up with losing my runs - I feel your pain especially if you had PBs


Sent from my Samsung Galaxy smartphone.

[PiLesley]

We've only been waiting for a fix since 9th March.
I recommend rolling back to 2.42 back to the day when everything worked.
Use apkmirror

Sent by LeSLeY

[Slowrunner30]

The solution offered related to avoid pausing is not suitable for me as I am doing interval training. Does anyone here use strava?

Do you know if a possible workaround would be to track your run with strava (rather than fitbit) and then sync both of apps?

Thanks!!!

[PiLesley]

Uninstall.
Install 2.42 from apkmirror.
Takes you back to pre 9th march when this all began.
2.42 works fine

Sent by LeSLeY

[Quppa]

Version 2.50 is available now. It doesn't fix the problem.

[senas]

this is ridiculous 😞

[PiLesley]

If it doesn't fix the problem I'll stick with the fully working 2.42 😞
This fix been required since 9th March.

Sent by LeSLeY

[PiLesley]

Indeed it is.
Since 9th March....
Poor communication and poor customer service.
Roll back to 2.42, that works

Sent by LeSLeY

[Slowrunner30]

I think I need some instructions on how to use apkmirror. It's not really clear for me (I can't even find an app with that name in play store)

[PiLesley]

Uninstall fitbit app.
Google apkmirror and go to the apkmirror website from search results.
Search for fitbit in apkmirror website, download and install 2.42

Sent by LeSLeY

[Slowrunner30]

So simple!!! Thank you 😊😊😊

[PiLesley]

Report back if all works so that others may share

Sent by LeSLeY

[Slowrunner30]

Lesley... thank you so much for this!!! 

Just finished a couple of tests from my end:

- paused my run for 9 times as I was doing interval training

- used my Bluetooth headphones whilst syncing

Run synced successfully.

The only thing is that 2.42 has the old dashboard and for a reason I can't understand I don't find the setting under advanced configuration. But tbh, I prefer the run syncing properly so I am happy to sacrifice the dashboard.

I have also disabled the auto-update feature for fitbit on google play until a definitive fix is released.

[PiLesley]

I agree.
Old dashboard may well be your sacrifice.
Add yes. Don't update app until you see lots of cheering on these forums!

Sent by LeSLeY

[don1000]

how do i stop fitbit from updating i can not find a setting to do it thank you

[Rich_Laue]

Actually if you look at the requests youll noticed tgatvthe Android users where peetty upset when ios got the new dashboard and we did not get it.

Since your so adamant agaist the new dashboard, why not add your constructive thoughts. Failure to draw a map of your run is not dashboard related.

@don1000 you control the way any app updates rhrough the play store

[PiLesley]

We're stuck with the new dashboard going forward.
But 2.42 uses old dashboard.
The point about 2.42 is that it works!

Google Play, settings, stop auto updates of all apps.
You get a notification of any updates and you choose which ones to update.

Don't update fitbit from 2.42 until you see cheers and woops of delight from others on this forum, would be my suggestion

Sent by LeSLeY

[Rich_Laue]

The dashboard is only the UI, it sounds as if you are mixing the two up.

[PiLesley]

Please.
I know what a UI is.
The old dashboard started to be phased out around 2.42 and just before.
You could try it and revert back.
At 2.42 that still stands.
If you want the old dashboard you can.
I've been posting on this forum since the GPS pause/continue map loss appeared after 9th march.
After update to 2.42.

It is an Android issue and not related to tracker.

IF you want pause/continue to work you'll have to roll back to 2.42.
Easy enough if you know how.

Coincidentally, and completely unrelated to GPS map issues, 2.42 uses the old dash - IF that happens to be your preference.



Sent by LeSLeY