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.
04-01-2017 11:17 - edited 04-02-2017 06:04
04-01-2017 11:17 - edited 04-02-2017 06:04
That is true @PiLesley Fitbit is never been known to give an estimate date.
The easy thing would be to remove the pause, the right thing would be to troubleshoot and find the cause. Then find a solution and test this solution in phones that are known to have the problem. Now test the solution with the other phones to make sure a secondary problem didn't creep in.
There has been at least once in the last 9 months a release date announced only to have a major problem show up within the first hour of release, none of the beta testers saw this problem. So yes Fitbit has been very cautuos
04-01-2017 15:49
04-01-2017 15:49
My reply....."We apologize for the delay, Lesley! Our engineers are aware of the problem and are working to resolve it as quickly as possible. We're sorry for any inconvenience it's caused. We appreciate your patience and look forward to getting you back on track."
04-02-2017 04:08
04-02-2017 04:08
So my latest run (today at 11.21am) recorded and I have my map and pace recorded (I did not use the pause button at all today) however I am now missing my heart rate info and my fat burn/cardio/peak percentage bar? What's going on?! Have attached screenshot below...
04-04-2017 13:51
04-04-2017 13:51
I have had this problem since around 04/03. It was fine up until then.
It's really frustrating as it's useful to see routes/distances that I'd like to repeat.
My phone is a Samsung S5 and I haven't changed any settings and Bluetooth is always activated.
Help!!!!!
04-05-2017 13:30
04-05-2017 13:30
I also have this problem. I tracked a walk today using gps (droid) and saw my results and map when it hit "finished", but when my Blaze synced all the map and gps data vanished 😞
04-05-2017 13:34
04-05-2017 13:34
04-05-2017 23:40
04-05-2017 23:40
I am having the exact same issue for the past 6 weeks on a Samsung Galaxy S5. All workouts record but only some record with a track despite the fact that it appears that the track is recoding during the activity / workout. Attached are two screenshots one from the workout summary page top workout showing no map, and the second screenshot shows the track being recorded during that same workout. This seems to be an intermittent issue with the app on my phone. (both app and phone are fully up to date)
04-06-2017 00:48
04-06-2017 00:48
04-06-2017 01:28
04-06-2017 01:28
Seems my previous post was deleted.
There's a new version of the app available - 2.46. Has anybody checked to see whether this issue has been fixed?
04-06-2017 03:17 - edited 04-06-2017 03:20
04-06-2017 03:17 - edited 04-06-2017 03:20
I don't think it is solved, today I lost my map data again...
The weird thing is that it does not happen all the time.. in the last 6 runs it happened twice.
Fitbit Charge HR with Huawei GX8 Android app.
-edit: sorry I just realized: app is version 2.45 (2183107)
04-06-2017 03:54
04-06-2017 03:54
04-06-2017 05:40
04-06-2017 05:40
I have installed 2.46 and just did 4 tests with MobileRun.. (exercise track). At least the flag points are now in the correct pl;ace for the RHR graphs.
The first two, I paused and resumed, then paused and finished and I was able to capture screenshot but nothing synced.
The final two I paused then held finish and they synced.
All four did not have a pace on the screen shots but the two that were successful showed the pace.
I'm sure Fitbit would have announced in the 2.46 release that they had solved that.
04-06-2017 09:46
04-06-2017 09:46
04-06-2017 09:46
04-06-2017 09:46
04-06-2017 11:56
04-06-2017 11:56
So sorry I've not been able to contribute for a while to any walks for the community testing. I took a rather bad tumble down my basement stairs and have been out of commission (since last Friday)...Thankfully, nothing broken...just banged up a bit and concentrating on one day at a time...Hopefully, I will be back in my walking shoes soon!!
04-06-2017 12:19
04-06-2017 12:19
04-06-2017 12:36 - edited 04-06-2017 12:47
04-06-2017 12:36 - edited 04-06-2017 12:47
I also have this problem on my phone very frustrating. Lg g3
04-06-2017 12:37
04-06-2017 12:37
The plan is to try a short trek on Sunday..I've been checking the forum every day and, while I was excited (at first), it didn't last long. I think, for now, our best bet is to stay away from the pause feature..It has been a long week for me and I can't wait to get some miles in!!
04-06-2017 12:40
04-06-2017 12:40
04-06-2017 23:10
04-06-2017 23:10
I turned off my Bluetooth last night and my map saved!!
May be coincidence but worth a go