Blaze GPS tracking fails

[john99]

I'm using a Blaze with a Google Pixel, have been using it for about a year now with few issues. I upgraded to Android 9 last week. 

Now I start a ride from the Blaze, confirm the "Let's go!" prompt with phone connectivity, and within 10-15 minutes it will be disconnected and no longer tracking distance. 6 out of 7 recorded bike rides in the last week have failed this way. I've tried restarting the app, rebooting the phone, rebooting the Blaze multiple times and in different order. Nothing seems to help.

Any known issues with Blaze and Android 9 Pie?

Moderator edit: subject for clarity

[AlejandraFitbit]

A warm welcome to the Community @john99.

Thanks for troubleshooting this by yourself. Keep in mind that in order to have a successful connection between your tracker and phone, it needs to be a compatible mobile device.

When a phone isn't compatible, it doesn't mean that it won't work with your Fitbit but you might experience some connectivity issues. You can always try the instructions provide in the help article Why isn't GPS working on my Fitbit device? but I don't guarantee it will work 100%.

Let me know how it goes. 

[john99]

Thanks for the reply.

As stated in OP, I have a Pixel, which is a supported phone.

I tested this over about a dozen more bike rides and walks and found a pattern.  After starting the activity from the Blaze, I will get the "Let's go!" message on the watch.  There is also a phone "connectivity" icon on this screen that shows 1-3 bars.  If the message shows less than 3 bars, the tracking will fail at some point after starting the activity.  I can cancel and restart the activity from the Blaze until the connectivity to phone shows 3 bars, and then it will successfully track the activity without dropping.   Note that I make NO other changes other than cancelling and restarting from the watch (I don't restart the devices, the apps, or make changes to how I'm using them).  Seems like a software issue to me.