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! 

[Quppa]

Version 2.51 is available now; it does not fix this bug.

[PiLesley]

Thanks, I'll stick with my trusty 2.42 then.
Appreciate you commenting so I don't waste my time trying 🙂

Sent by LeSLeY

[Colinm39]

@QuppaJust released here in Australia... Thanks for testing.... I was about to test again, so I will test Connected GPS because in Australia  that has the East/West issue where we gain 12"/second or 30cm/second and about 2 mins/KM on Pace..  OK in the North/South.. Correlated with MobileRun and Surge..

I don't expect miracles.

---

@Quppa wrote:

Version 2.51 is available now; it does not fix this bug.

---

[anyutikins]

Just to say mine is now updated to latest version (Moto G4 Plus with Fitbit Charge HR 2), just did a run with location on but Bluetooth not turned on until after and it synced fine this time and remembers the map 🙂 looks like it's fixed for me.

[Quppa]

@anyutikins Are you sure you paused and resumed at least once while tracking the exercise? I just tested it again and the bug definitely still exists.

[Colinm39]

I still tested and no change here... V2.51....

Pause, Resume and Finish doesn't save maps or log activity.

Pause, Finish saves maps and logs activity.

But, you have always been able to do a screenshot of both situations and like all of the maps 0'00" pace shown until you get a successful map saved.

[PiLesley]

Not working for me either.
Back to jolly old 2.42 for me, lol

Sent by LeSLeY

[anyutikins]

Ah apologies, I didn't realise the bug was only if you had paused during
work out then paused again. I didn't pause in the middle at all, just at
the end.

[PiLesley]

Bug is: pause, continue, pause, finish.
Map doesn't save.
And with latest update still doesn't 😞

Sent by LeSLeY

[SunsetRunner]

Yes the bug does definitely exist. It has been a problem since March 9th. That is too long for this severe of a problem to exist. I have taken off both my Fitbit. I have uninstalled the software. I'm doing all of my exercises with MapMyFitness, and carrying my phone. It has been a load off my mind. I no longer lose my maps and workouts. Fitbit has had 4 months to address this issue now. They are obviously uninterested in fixing this issue.

[siris10]

My Samsung gear fit 2 arrived today so I uninstalled the fitbit app and the tracker is now in the bottom of my bag where it shall stay. I went for a run tonight without my phone, Bluetooth headphone synched to my new tracker and guess what?????? The map is saved and all has transferred over to Strava, makes running fun again knowing I can take a breather and not lose my maps


Sent from my Samsung Galaxy smartphone.

[PiLesley]

You make me jealous.
Tech that actually does what it says on the box!
Amazing, novel, I've forgotten what that feels like.

Sent by LeSLeY

[siris10]

I'm a bit sad as I loved the simplicity of the Fitbit, I rolled back the software but simply decided that a company who couldn't sort it's software out wasn't a company I wanted to use anymore.
My fitbit was also falling apart and was made mire of superglue than anything else and it was time to buy a new tracker but wasn't happy to buy a new fitbit on the back of all these problems


Sent from my Samsung Galaxy smartphone.

[BamIAm]

I tried 2.51, but in addition to the disappearing exercises, the dashboard
tiles are doing strange things, moving around, turning on/off on their own.


2.42 is stable, and I like the ability to toggle back to the older view
instead of the dashboard tiles.

[PiLesley]

Good job we're into self help as fitbit not supporting.

3.5 months and nothing to show for it.

Three cheers for apkmirror and 2.42.

[SunsetRunner]

I am having the same issue and came to this thread, filled with frustration. Is it safe to download the old version of this apk from that site and install? Do you uninstall and then install new? How would we know if the bug is fixed (though it seems unlikely to happen after this time)? The map appears just fine on the Google fit app, so the Charge 2 should be able to get it from the same GPS.

Thanks to the community for the help.

So annoying that Fitbit never responds.

Cheers

Ellie

[PiLesley]

Yes uninstall fitbit app.
Then go to apkmirror.
Apkmirror is pretty reliable.
As a site it's been around for ages.
Loads of us have taken 2.42 from there and we're OK, so I guess we've tested that route for you.
There's always a risk downloading from such places, it's your decision.
Works great for me.

Going forward you can try updates.
If they don't work.... go through this process again........
OR just wait to see the woops appear on here before you try updates.
So set your Google Play to NOT auto update apps.

We've been waiting since 9th March.
2.42 offers stability for the time being...

Sent by LeSLeY

[SunsetRunner]

Thanks! 

Do you know if we lose sleep stages with that version? Hope not...

Cheers!

I have it downloaded​.

[Colinm39]

@SunsetRunnerSadly that is the case.  Sleep stages were released in version 2.46.  I'm now using V2.51 because I want to keep seeing the sleep stages and correlate with RHR.

I can put up with NOT using Pause, Resume. In saying that, some Fitbitters are reporting issues using both methods, Pause, Resume and Finish.... and... just Pause and Finish.

---

@SunsetRunner wrote:

Thanks! 

Do you know if we lose sleep stages with that version? Hope not...

---

[SunsetRunner]

Yup, you lose the sleep stages. Sigh. 

At least Google fit keeps my map data. And it doesn't only happen when you pause, restart and then stop the exercise, but mostly, so I'll just not do that.