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! 

[PiLesley]

Thanks. Will update now, UK, and test tomorrow

Sent by LeSLeY

[Quppa]

@ErickFitbit As per my above post, unfortunately 2.47 has not solved the issue for me. Pausing and resuming still causes the exercise log to be forgotten, and 'pace' still shows as 0:00 on the summary page.

1. Samsung Galaxy S7 (Android 7.0).

2. MobileRun.

3. Run.

4. 2017-04-20 18:23.

[Colinm39]

@QuppaThanks for the info for the Moderators..  Does a Finish only work ie Pause then Finish with no resume.?

We have two distinct issues spread over different phones..

The one you mentioned but there are also some that the Pause, Finish fails as well.

---

@Quppa wrote:

@ErickFitbit As per my above post, unfortunately 2.47 has not solved the issue for me. Pausing and resuming still causes the exercise log to be forgotten, and 'pace' still shows as 0:00 on the summary page.

1. Samsung Galaxy S7 (Android 7.0).

2. MobileRun.

3. Run.

4. 2017-04-20 18:23.

---

[SunsetRunner]

Thanks @Rich_Laue, I saw other comments / posts after I'd posted (but for some reason not before!). work around works, so happy again now that I can export *.tcx files to my running logbook.

[SunsetRunner]

Hi ErickFitbit,

this appears to be occurring in version 2.47 for me.

• Motorola Moto G4 Play
• Using GPS on the mobile device and a Fitbit Alta.
• I was running
• Last run where everything worked normally was on 18th April 07:11 BST (UTC +1) - I believe (but am not sure) that my app updated to v2.47 after this
• 19th April 07:03 BST (UTC + 1) no GPS info stored.
• 21st April 06:47 BST (UTC + 1) no GPS info stored.
• 24th April 12:30 BST (UTC + 1) tried switching off auto detect, and using the GPS on mobile device, and nothing was stored at all, so I entered this manually in my activities list.
• My usual way of using the device is to start tracking, and then to pause it whilst I strap the phone to my arm, and then resume as I leave my work site to start running. Following other posts r/e work around, I uninstalled and reinstalled the app, and then I did not pause/ resume yesterday, 25th April 12:33 BST (UTC + 1), and all worked normally. I will continue to use this work around until the bug is fixed.

Kind regards

Spidricks

[PiLesley]

Hi, This still fails. No record of activity at all after using Pause, Continue. Nexus 6 Android 7 8am UK time, 26th April Using app to connect for a GPS walk. Charge 2 HR. Thanks

[Quppa]

@Colinm39 Pause then finish with no resume has worked consistently for me, at least.

[Colinm39]

@Quppa Thanks again for letting the Community know.  The more facts we gather the quicker Fitbit Engineers will have our solution.

---

@Quppa wrote:

@Colinm39 Pause then finish with no resume has worked consistently for me, at least.

---

[PiLesley]

Yes. Pause Finish works.

Pause Continue fails every time.

[HayleyCh]

@ericfitbit Failed again this morning. 27 April 2017 at 08:18. Fitbit Charge HR. Samsung J5 (2016). Latest app update. Paused mid walk, resumed and then finished...app crashed!

[ShadowC78]

Also happened to me yesterday. Thankfully I also track on another app at the same time (I need the evidence for a challenge!) I'm curious to see if the same thing happens if I track from the HR2 directly rather than starting the track through the phone. 

Samsung S7, Nougat

[Colinm39]

@HayleyCh  Your post will help Fitbit immensely because I couldn't screenshot that error.

To finish your test could you do a simple test and just Pause, Finish... No resume.  The test only needs to be greater than a minute.

There are two issues, and Fitbit are trying to tabulate the phones and the failure type. ie Resume and Pause and non Resume..

I had your error on walk, run and hike but success on all of those three with no pauses..

---

@HayleyCh wrote:

@ericfitbit Failed again this morning. 27 April 2017 at 08:18. Fitbit Charge HR. Samsung J5 (2016). Latest app update. Paused mid walk, resumed and then finished...app crashed!

---

[HayleyCh]

@Colinm39 thanks. Just went for a stroll down to our office postroom and back. Paused and finished... recorded and saved all stats. Pause and resume has always been the issue for me.

[frerunner]

---

@HayleyCh wrote:

@ericfitbit Failed again this morning. 27 April 2017 at 08:18. Fitbit Charge HR. Samsung J5 (2016). Latest app update. Paused mid walk, resumed and then finished...app crashed!

---

@Colinm39@ and @ErickFitbit this is exactly the same message I got today.

I have a Motorola Moto G, operating Android 6.0. My app has updated to 2.47 and my fitbit is a Flex (though I know this bit is irrelevant). And I live in the UK.

Nowhere on my app does it say MobileRun, but I go to Track my Exercise and use the GPS.

The problem started for me when fitbit upgraded to 2.44. I got on fine with the workaround of not pressing Resume, after having pressed Pause, but instead just pressing Finish. That was irritating, but as we all know, it would save the route map and stats.

Today, I got that same error message (that HayleyCH posted) twice. First on a jog. I did not press Pause and Resume, but Pause and Finish. I was really pleased with my map and distance and delighted it had saved. Then after the congratulatory green screen, it stopped and lost everything.

The second time was on a walk. I did press Pause and Resume just to test if that was fixed yet. Maybe it is, but I don't know as again after the green screen it stopped and showed me the error message again.

Interestingly, prior to all this mess, I used to frequently get an error message saying "Fitbit has stopped working" or something like that. I used to Close it each time and it would start up again with no trouble and nothing missing. 

I am really upset now. I know my fitbit is purely a useful device to help assist, it won't actually get me fit just by being worn on my non-dominant wrist. But I like being able to see where I've run and walked to. I like the GPS feature. I like to compare my stats to help monitor my fitness and motivate me. 

Please fix it!

.

[Jas143]

Same happened to me 
Sent from my LG Mobile

[Jas143]

Same happened to me 
Sent from my LG Mobile

[PiLesley]

So for all we're now on 2.46 and this has been broken since 9th March and it's now near as **ahem** it May...I don't see anyone reporting a fix!

We all continue to report fail.

Is that correct?

[PiLesley]

Sorry. 2.47 even

[siris10]

I have recently changed to a Samsung S7 edge from an IPhone and am having the same issue so I kinda glad it's not just me.... strange thing is that it doesn't happen every time... I went for a run earlier and it mapped it and gave me my stats (took a screen shot as I thought it might go belly up) however it's not showing in my exercise record in the app. Is the issue just with Android as I had a seamless service using IOS, I'm loving the android and just want this to work 

[PiLesley]

Just android.

Likely you selected pause continue during your walk/run.

That's the bug.

Don't select pause continue.

Only pause finish.

The workaround pending a fix sometime never is record your walk/run in chunks with pause finish.

Don't use pause continue