10-25-2017 18:14
10-25-2017 18:14
Every time the Fitbit android updates, I have to restart my phone. This is an annoyance, but not a big deal. BUT--it seems I have to restart the phone multiple times, and then the Fitbit Blaze multiple times, before the Fitbit can find the phone in Walk mode; and often notifications don't resume for hours after the update and restart. (1) Why does this always require a restart to begin with, and (2) why do I have to do multiple restarts?
10-30-2017 05:38
10-30-2017 05:38
Hello @KurtH, good to see you around in the Fitbit Community! Sometimes after an update, it is require a restart to reboot the new features or the enhancements has been applied to the update. In several devices and in Fitbit is normal and even required.
Now about the multiple restarts and the issues you mentioned with Walk mode and notifications, this is certainly not an expected behavior. Although I'm wondering if with Walk mode you are referring to the Connected GPS feature?
Usually when this feature is not working, Bluetooth is turned off (preventing your Blaze from connecting to your phone) or your phone can't find a GPS signal. A weak GPS signal on your mobile device is often caused by environmental factors such as tall buildings, dense forest, steep hills, or even thick cloud cover. All of these can interrupt the connection between your tracker and GPS satellites.
So the best to try here is a restart as you have done to reestablish the GPS connectivity.
Hope this information helps. See you around and let me know if you have more questions.
"Great things are done by a series of small things brought together.” What's Cooking?