Lost cycled miles

[Nix219]

When using the blaze and logging cycling miles, it doesn't start the miles unless I've synced the blaze to my phone before I press start? Why is this and how can I stop this from happening. It's annoying because it wouldn't track when I was cycling in Spain? Any advice????

[AlejandraFitbit]

It's great to see you here @Nix219. Have you tried using the SmartTrack feature? If you haven't, I recommend trying it. You don't need to do anything, just wear your tracker, do your exercise and it will automatically log the exercise you were doing and your information won't be missed. 

Let me know the outcome. 

[Nix219]

Hi yes I do use it but it doesn't count miles just duration!

Sent from my iPhone

[Rich_Laue]

Yes smart track without GPS has no reference points to measure distance.
I don't know much about iOS but do know that if notifacations are not working, neither will the connected GPS, which connects to the phone through the notification services.

[bbarrera]

---

@Rich_Laue wrote:
I don't know much about iOS but do know that if notifacations are not working, neither will the connected GPS, which connects to the phone through the notification services.

---

@Rich_Laue No, not exactly. Connected GPS, a Fitbit app feature, is not fundamentally related to Apple Notification Center Service (ANCS). Therefore the Blaze can use Connected GPS even if notifications "aren't working."  If Fitbit was using Notification Center for Connected GPS, then your iPhone lock screen would be full of gps coordinates!

Think I know where your confusion is coming from... Fitbit Blaze's feature set for Windows 10 Mobile phones.

Some background:

1. Bluetooth Low Energy 4.0 (BLE) introduced GATT as the protocol for sharing data between two BLE devices. 

2. A Fitbit device needs to "sync" or share step count (and HR) with the Fitbit phone app. In this basic scenario the tracker is the (gatt) Server and the phone app is the (gatt) Client.

3. Now consider Notifications and Connected GPS. Roles are reversed now, the phone must share data with the tracker (Blaze). In this scenario the tracker is the (gatt) Client and the phone is the (gatt) Server. More specifically, with Connected GPS the Fitbit app is the Server of gps data to the Blaze. And the Apple Notification Center Service (ANCS) is the Server of Notifications to the Blaze - in fact ANCS is completely independent from the Fitbit app and the Blaze could receive notifications without any involvement of the Fitbit app (however Fitbit decided to use the app, and not Blaze, for configuring which notifications appear on the Blaze). 

Notifications and Connected GPS only work with iOS and Android, because Windows 10 mobile does not support GATT Server (however it is possible for a vendor like Fitbit to hack their own solution).

Hope that background explanation helps.

[Rich_Laue]

Sorry I was going by Fitbit saying at notifacation needs to be enabled, checking manual again I see that thy. Statement has been changed to read Android as to be enabled. As for Win10 Fitbit is waiting on Microsoft, for the last 9 months Microsoft says they are working on this, to implement the GAAT Service on BTLE. Until this gets fixed Connected GPS will not work with a windows phone. 

On android the fitbit app does not need to be running, Fitbit notifacations does.