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]

---

@rencarr wrote:

I have this exact same problem. It's been ongoing for months and is very frustrating. My most recent occurrence was on Saturday 8 July 2017. I ran a 4km fun run. Stopped and finished that run. Waited about 5 minutes before closing the screen and it saved. Random success!
Then I started a new run about 10 minutes later - this time covering 7kms over 53 minutes. Exactly the same process. I waited 5 minutes before changed the screen on my phone (took a screen shot which shows pace as 0:00) and then when I went back to the main fitbit screen, it was lost.

There is no warning either. It's gone and thats that.

---

It's not quite random - your data will be saved as long as you don't pause and resume tracking your exercise.

The pace showing as 0:00 may or may not be a related issue, but it seems to affect a lot of us in this thread.

We're past the 4 month mark for this bug now. I wonder if we can get to half a year.

[rencarr]

I didn't pause my tracking. I completed one run, then restarted a brand new run completely separate to the first. 
I never used pause.

[Quppa]

---

@rencarr wrote:

I didn't pause my tracking. I completed one run, then restarted a brand new run completely separate to the first. 
I never used pause.

---

Yours may be a distinct issue, then. My data is reliably saved as long as I never pause the tracking (other than to then click 'finish'), and I believe this is the case for most of the other people posting in this thread.

[rencarr]

I have experienced this issue several times and don't use the pause feature. I just run and go. 
If I am able to access a PC immediately after my run, I usually come to the computer to check the Fitbit website first and once I know it's there, then I am happy it's been saved. I don't believe it's a pause problem for me when I'm not using pause during my runs. 

[AKezer]

The pause button isn't a factor with my lost of the GPS map either.  I click "pause" and immediately press "Finish"...it's hit or miss with me...some days it's saved...some days it disappears.

[rencarr]

Yeah that's exactly the issue! It's random. There's no reason why it happens. It just does sometimes. 

[grjam28]

Hi HayleyCh                     ,

I thank you for that tip. It works as long as you do not click Pause. That seems to not record the walk.

Kind Regards,

Geoff James

[PiLesley]

Pause is the issue for us all on here.
You are first to say it isn't Pause.
That's what we've all boiled it down to.
Don't use Pause until you're going to press Finish.

If that's not your problem then you got a new issue which probably needs a new thread.

Although I keep repeating myself...
For that I'm sorry to regulars here...
I suggest you uninstall app.
Go to apkmirror and get good old reliable 2.42.

But you have different issue to us on this thread so maybe start a new one.
Pause is our downfall.

Sent by LeSLeY

[don1000]

i find pause makes it certain not to work but it also sometimes doesn't work without pause

[HLJackson]

I think that might be the issue...  Both times I started exercising, forgetting to track, using the MobileRun Tracker from the get go. It seems that if the Auto Recognizing Feature is already in play & you start the MobileRun Track after that has started, therein lies the issue of losing the data, such as the Distance & Map. I think I am going to put this theory to the test. Thank you so much for your insight!!! I'm also going to see if the Pause button is the issue as well...  

[Colinm39]

@HLJackson Welcome, you only need a minimum of 1 minute to test all of the MobileRun options. For me multiple pauses cause the problem but a single pause and finish is always successful.

V2.53 has just updated. I will try that soon.

[Quppa]

2.53 does not solve the pause/resume data loss issue or the 0:00 pace display issue.

[Colinm39]

@Quppa Thanks for the quick response.

---

@Quppa wrote:

2.53 does not solve the pause/resume data loss issue or the 0:00 pace display issue.

---

[HLJackson]

To Colinm39... 

The post that I was referring to... 

- Kelgan 

Brycebeaumont, it sounds like you're starting the exercise tracking from your Charge 2 rather than your phone, and that the connection between the two is failing.  Until they can get that sorted, I might suggest starting the exercise through the app instead of through your Charge 2 - just don't press pause until you're ready to finish the exercise - and let Fitbit insert the data from the tracker into the phone-based recording. 

-end post-

-----------------------

So it was then I realized that it was either the pause button or that I had already started my exercise w/out tracking it w/the MobileRun Tracker 1st... So I did a test run, I did not pause & I started the MobileRun Tracker at the very beginning of my walk. My data has NOT been lost, thus far. Tomorrow, I will start my exercise & let the Auto Recognize Feature start 1st, then I will apply the MobileRun Tracker after, to see if that could be one of my app's issue. Since the Pause button seems to be most people's issue, I want to see if this might be another cause for the data loss. If that doesn't seem to be my case, then I will test the Pause theory out as well... After second thought, I should probably test the Pause issue out anyway. Either way, I'm happy that I've been able to narrow down what the glitch is & the possible causes.  

Thank you for your imput. - warm regards, HLJackson   

[PiLesley]

Thanks for testing.
I'll continue to stick with 2.42.

How much longer do we have to wait for a fix?
Moderator can we get an update please?

It's been over FOUR months now!
Do you actually have any plans to address this?



Sent by LeSLeY

[Colinm39]

@PiLesleyI agree with you.. Android is going to be with us so the App must be corrected.. The pending release of a Blaze 2 will take the pressure off the connected GPS issues.. BUT... we have many users who rely on the MobileRun. 

Question:.... Is this problem with iOS ?

Ironically the logic works in V2.42 and it dismayed me that this logic can't be ported to the V2.53..

---

@PiLesley wrote:
Thanks for testing.
I'll continue to stick with 2.42.

How much longer do we have to wait for a fix?
Moderator can we get an update please?

It's been over FOUR months now!
Do you actually have any plans to address this?

Sent by LeSLeY

---

[Quppa]

---

@PiLesley wrote:
How much longer do we have to wait for a fix?
Moderator can we get an update please?

It's been over FOUR months now!
Do you actually have any plans to address this?

---

Indeed - unless the cause of this bug is something really arcane, how hard can it be to open up whatever source control Fitbit uses and check the diff between the 2.42 and 2.43 code? The bug is dead simple to reproduce, as noted by the many people who have posted in this thread.

[PiLesley]

I know someone using iOS, no problems.

Agree. If the Pause/Continue code works in 2.42 (which it does) why can't that be reinstated in some form into latest updates.... To get us up and running (!) again?

Silence from Fitbit moderators?
Very poor customer service.
Just ignored.



Sent by LeSLeY

[SunsetRunner]

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.

[PiLesley]

But this thread has nothing to do with tracker.
It's about Android app.

Sent by LeSLeY