08-13-2017 19:03
08-13-2017 19:03
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.
08-14-2017 07:24
08-14-2017 07:24
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.
08-21-2017 17:54
08-21-2017 17:54
Hello,
I've read the post and I've already tried all those solutions with no change to my issue.
Thanks,
Tim
08-30-2017 03:35 - edited 08-30-2017 17:57
08-30-2017 03:35 - edited 08-30-2017 17:57
I have the same problem as Tim. Any progress on a fix?
Thanks,
Brian
09-02-2017 15:30
09-02-2017 15:30
and I have the same issue now too. Seems like the problem started when I upgraded to Android O. Not getting any notifications.
09-21-2017 22:42
09-21-2017 22:42
I have the same issues since upgrading to Android O. When is this going to be fixed? Makes the Blaze about useless.
09-22-2017 19:24
09-22-2017 19:24
I'm having the exact same issue. Started right after I updated to the latest Android version.
10-01-2018 19:29
10-01-2018 19:29
Did anyone made it work? I am also facing the same issue between Blaze and Samsung Android phone