01-30-2019
22:00
- last edited on
01-31-2019
05:05
by
LanuzaFitbit
01-30-2019
22:00
- last edited on
01-31-2019
05:05
by
LanuzaFitbit
I am on Samsung Note 9 which just moved to Pie. I have a charge 2
App version 2.86. Charge 2 Firmware 22.55.2. OneUI version 1.0. ANDROID 9
Unlike other people, I have no issues synching.
However, the app shows weird behavior : When I start an excercise from the pebble, it randomly stops on its Own. For example, I start a new walk on the pebble, check that it is connected to the phone and is tracking. After 5km,I find that the charge2 has stopped tracking sometime in between for no reason. This has happened multiple times.
Any fix for this?
Moderator edit: Clarified subject
01-31-2019 05:10
01-31-2019 05:10
Welcome to the Forums @sridhu.
Thanks for bringing this up!
It is possible that the connection between the two was stopped or interrupted in some way. When you go on walks, where do you keep your phone? Is it on your arm or in a pocket? Do you keep them on the same side of your body?
Look forward to your reply.
01-31-2019
05:40
- last edited on
02-01-2019
10:17
by
LanuzaFitbit
01-31-2019
05:40
- last edited on
02-01-2019
10:17
by
LanuzaFitbit
It is typically in my pocket; on the same side as the pebble.
This has not been an issue until now; only after the Pie update, as far as
I can see. However, I only had the Note 9 for about a week; ten days before
it updated to Pie.
Thanks
--
Regards,
Moderator edit: Removed personal info
02-01-2019 10:21
02-01-2019 10:21
Hello @sridhu.
Thanks for bringing this up.
It is definitely possible that it is related to the new Android version caused the connection to be not as stable.
My recommendation would be to try to uninstall the app and then reinstall it to verify if that improves the connection.
Let me know if there are any further questions.
02-07-2019 02:57
02-07-2019 02:57
I have reinstalled the fitbit app & for good measure, I have reset all radio connections.
Did not drop connection today; hopefully it is a fix that will hold. WIll update you either way after using for 10 days.
02-08-2019 09:56
02-08-2019 09:56
Hello @sridhu.
Thanks for sharing those details on the matter! Glad to read that everything is working correctly.
If you have the time, be sure to visit one of our Discussion boards. Lots of different topics to talk about with other users so one might pique your interest.
Let me know if you have any further questions.
02-17-2019 21:42 - edited 02-17-2019 21:45
02-17-2019 21:42 - edited 02-17-2019 21:45
The problem came back.
The problem seemed to have resolved itself after the reset but unfortunately, it is back again today. In my 6.5 km walk, the tracker stopped tracking the walk after around 5.26 km
See: https://www.fitbit.com/activities/exercise/19953142477
Obviously, I have not returned to where I had started.
Bluetooth seems to work fine with my headphones, also used during the same walk.
02-18-2019 09:36
02-18-2019 09:36
Hello @sridhu.
Thanks for letting us know that it is happening again.
It definitely seems like it is related to the connection not being stable, be it between the Fitbit and the app or the GPS connection. My suggestion would be to try keep an eye on the connection during the run and making sure that it is connected from time to time.
My other questions would be if the activity was paused at some point.
Let me know if you have any further questions.
02-19-2019 19:12
02-19-2019 19:12
Actually, I may have figured this out ( you folks should give me a bug bounty!)
As you suspected, it has to do with pausing and I suspect , a timeout.
But not the Fitbit activity
Allow me to elaborate:
I think the connection is lost when a parallel audio app (Pocket cast & Listen, in my case) is paused for 3 minutes. As in, I was listening to a podcast and paused the audio to cross the road. Took me a while and while I could restart my podcast, the Fitbit tracking disconnected .
I confirmed it by pausing audio a couple of times. Seems to take 3 minutes to induce the behavior. Also seems to be a condition that the pebble itself not be 'on' (as in the display being visible) at the time the timeout happens
This insight & recreation happened during my morning walk about 90 minutes before now, in case you want to check server logs.
Thank you
02-21-2019 09:46
02-21-2019 09:46
Hello @sridhu.
Thanks for taking the time to test that and even sharing your findings on the matter.
We will be sure to bring this up from our team. Having said that, let's hope that knowing this helps us prevent it from happening in the future.
If you have the time, be sure to visit one of our Discussion boards. Lots of different topics to talk about with other users.
Let me know if you have any further questions.
12-19-2019 00:27
12-19-2019 00:27
The connection problem seems not to be linked to a specific phone. I have the same issue. the fitbit app never tracks my activity correctly. It is always interrupted several times. My phone is a Xiaomi Redmi Note 7. Would be great for Fitbit to gather some insight on what is causing these problems.