Since updating my Pixel to the Android O beta, my Blaze will not stay connected to the phone when I track a run with it. It will start out with a weak bluetooth signal but will completely drop once I'm about 1 to 2 min into the run and it will not reconnect. This issue has been consistent now. Prior to the Android O update, there was no issue but now there is.
Some things to note:
- The Pixel is very close by
- Pixel is running the latest Android O beta
- Blaze and Fitbit App are running their latest versions respectively
- This issue still persists despite
-- "always connected" is on or off
-- "bluetooth classic" is on or off on
I've also tried re-pairing the Blaze with my phone as well as with my Fitbit account. Lastly, apart from dropping the connection during the run, my Blaze will sync with my phone fine.
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
A warm welcome to the Community @timchoi89 and thanks for troubleshooting this by yourself.
First of all, I recommend checking our list of compatible mobile devices, if your phone is not listed, keep in mind that in order to connect your phone with your tracker it needs to be compatible. In the meantime, you can follow the instructions provided in the My Blaze GPS is not working post.
Let me know the outcome. ![]()
I have the same issues since upgrading to Android O. When is this going to be fixed? Makes the Blaze about useless.