11-02-2017 08:40
11-02-2017 08:40
Has anyone else had problems with their Blaze staying connected to their Android device during workouts (for GPS data) after updating to the latest firmware and/or Android app version?
The gory details:
I recently updated my Blaze to firmware 17.8.402.1. I am having issues getting it to connect (and stay connected) to my Andriod phone (LG V20) for GPS data during runs. I've had the Blaze for almost a year now, and I haven't had this issue until this past week.
I can eventually get it to sync for data transfer purposes, but that often requires either rebooting the phone (rebooting the Blaze itself doesn't help) or doing a force stop on the Fitbit app on the Android device. The force stop seems to take a couple of attempts before actually stopping the process. After that, I can connect to my phone for running (GPS). However, it seems to loose that connection. I am using a Bluetooth headset (2 different ones, both known to work previously).
The Android Fitbit app is at v. 2.60.1 and my phone is running Android version 7.0 (kernel 3.18.31). Basically, I think everything is updated to the most recent version available to me.
Answered! Go to the Best Answer.
11-07-2017 09:30
11-07-2017 09:30
I appreciate your reply. I am frustrated with the situation. This leaves me the choice of changing phones or changing trackers. I am not up for changing phones right now. I guess I will be checking out my options for other trackers.
11-05-2017 10:00
11-05-2017 10:00
A very warm welcome to the Community @pendrgn! Great to see new members.
That sounds quite frustrating. After checking, I could see that the LG V20 is not currently a supported device and thus this type of behavior is to be expected. While the phone might have all of the needed hardware to work properly, like it did, it is possible that any update to the tracker or the app might cause some optimization issues and thus the app is not working properly and that causes the syncing issues. .
Please feel free to let me know if you have any further questions.
11-07-2017 09:30
11-07-2017 09:30
I appreciate your reply. I am frustrated with the situation. This leaves me the choice of changing phones or changing trackers. I am not up for changing phones right now. I guess I will be checking out my options for other trackers.
11-09-2017 05:46
11-09-2017 05:46
Hey @pendrgn.
I understand how this must be frustrating! If you have a computer or a tablet perhaps you could use them to sync your Fitbit to your account. That way you can use the tracker for all of your performance.
Please let me know if you do have another device and I could guide you on how to get it to sync.
11-09-2017 09:26
11-09-2017 09:26
I can get the fitbit to sync to a computer. I can also get it to sync with the phone (when I first start the app). However, the app has trouble <staying> connected.
If the app doesn't connect, I can force stop it (or reboot the phone), and it will connect and sync up. It will then also connect (sometimes) when I start a run, but loses the connection almost immmediately. This means no GPS anymore.
It has worked well for almost a year, but I'm now growing tired of messing with it. The app seems to be using more battery on the phone since the last update. Given those two factors, I'm not running the android app right now. The convenience of the android app is one of the main draws of the fitbit products. I realize that you can't support all possible models. However, if cheap bluetooth headphones can pull off a consistent connection, I'd hope the Fitbit could manage the same.
I may check back and see if future updates work. In the mean time, I'm looking at other alternatives. I spend most of my day supporting computers, my morning workouts are supposed to get me out of that mode! 🙂
11-14-2017 06:52
11-14-2017 06:52
Hey @pendrgn!
Thanks for sharing all of your feedback and for sharing your insight on the whole situation Please do know that we take comments like this seriously and we're always looking for ways to improve.
If you have any further questions, please let me know.