Fitbit has issues to resolve

[SunsetRunner]

I specifically purchased Fitbit Blaze because of the additional functions, which regretably have issues. I have lost count of the many times I have unpaired repaired rebooted etc etc and looked at every possible setting on all my other devices along with the Blaze's

My blaze is mainly used with a windows 950 phone, but also I have a Samsung galaxy and apple Ipad. On ALL  3 devices I see a comment that GPS will not be used, even though any of the above mentioned devices have a good GPS signal verified by using various other apps such as inbuilt satnav.

On the Blaze I have "use phone gps" set to ON, notifications set to On, and bluetooth classic set to On.

The Blaze will not track a route that I ride, I just get the basic stats with Zero mileage recorded.

Having thrown the towel in with the Blaze, I tried using the app itself, to record a ride.

Hey presto, I see all kind of stats, even a map, wowee ..... err just a minute,

why does the map show a route similar to a letter Y on its side, when the route was a perfectly straight cycle path that I rode in both directions.  Oh, its probably because the GPS signal was lost somewhere.  Unfortunately not, I am an engineer, and know the importance of having other sources of information available, so I was running another app at the same time on the same phone, this app showed an almost perfectly straight line on the map it created with near perfect distance recorded.

So, in conclusion, The Blaze that I purchased partly because of its ability to track routes via GPS does not actually provide this function,  and the Fitbit app is not reliable to record routes either.

Very sorry to say Fitbit, But when my Blaze eventually dies, I will be looking elsewhere for a smartwatch, Reading through these forums tells a story that we dont see on other hardware forums.

P.S.  The other app I use is Sportstracker, Never failed me once in six years across multiple platforms and devices.

[SunsetRunner]

Can only agree ! My Blaze worked quit well until May/June (bought it last October).
All activities starts with either "Phone not found" or disconnects after a couple of minutes..
brg/steff

[Rich_Laue]

@SunsetRunner lets start with the Windows phone, it is not compatible with the connected GPS, yet, fitbit and microft are together working on this. Once fixed im sure notifications will also work.

Whic device did you set the Blaze up with Wndows phone, that could be the problem with the other devices.

My suggestion would be to set it up, do a replace current tracker, with the phone or ipad, whichever you carry the most. All 3 devices will configure the Blaze differently.

Now when you want to sync through a device, make sure the other two have at least their BT off or are at least 30 feet away.

Usually when i see tye message GPS will not be used I find there is some permission the app needs but doesnt have.

@SunsetRunner, your problem most likely is unrelated to the above problem. Your app d8d not warn you of anything. 

You want to make sure the Fitbit app is in memory, Fitbit notifacation iservices are running. Once i confirmed these havent changed, then i restart tye phone. The tracker always gets GPS at this time. Clicking always connected could help also.