Bluetooth Connection Issues When Using GPS

[Maganou]

I am having issues with the GPS sync feature (Galaxy S6, Charge 2). The Charge 2 will only intermittently connect to my phone. When I look at it while running, much of the time I can see the icon showing it either as disconnected to trying to connect, while other times it's connected just fine. This is resulting in wildly inaccurate maps (like a line cutting across the lake I'm running around) and distances (a 7 mile workout was recorded as 1.5 miles). This is not a GPS signal issue - it is a Charge 2 to phone connection issue (another device was recording accurately and as I said, I can see the Charge 2 is cutting in and out in connection to the phone). I carry my phone in a hip belt so it's not very far from the tracker. Anyone have any ideas for how to fix this? Looking at the forums it seems like a lot of people are having similar issues regardless of phone model.

[The_Lion]

I have a similar problem with my Blaze. After phone reboot I can connect my Blaze to the phone's GPS. But short time later the phone cannot be found. If the notifications stopped working too, I don't know. Didn't send test mesages to me all the time and I don't need that feature so much. For getting Blaze and phone connected again I have to start the Fitbit app. Then it works again. For the tracking I start after that. A bit later it doesn't work again. I will try if this also happens when I choose always connected in the app.

[GarethDPhillips]

I have the same with my Blaze, and am going to post seperatley about it, as its clearly a very common issue, but Im not sure it is officially acknowledged by Fitbit?

My Fitbit wil sync just fine with the app (although I have to say its sometimes slow to connect and begin). When I start a run, I often find that the Blaze cannot find the phone. I reboot the phone, I reboot the Blaze, and eventially it connects. At least 50% of the time when running, my Blaze will lose its connection with the phone at some time during the run. THis is beyond annoying, as it stops GPS tracking the activity. Also in my case, its is almost never the case that the Blaze will re-connect. It just remains disconected. I actually cant live with this, as it is destroying the main use of this device.  I guess I could start and stop the activity in the app as a workaround, but why should I have to?

I have tried rebooting both devices before a run to try and impprove reliability, and also I have disabled WiFi. I run with the phone on my arm, so this cannot possibly be bluetooth signal strentgh related. I am runnning with Bluetooth headphones, but I never have any issue with Bluetooth devices in general, my hands free car kit never misses a beat. It just seems to be unrelaible with the Blaze, presumaby due to the low power bluetooth used?

My mobile is a Google Nexus 5x runnig Nugaat 7.1.2 

I have "always connected" enabled, but I guess this doesnt behave as I thought it did, as the Blaze doesnt remain connected. Each time I open the app, it takes a while to connect up, and which point I get the green connected icon on the Blaze picture in the top of the app. WHy cant this connection persist when the app is running in the background?  It feels like the connection is being dropped by the phone, but I'm not sure. 

Are any Fitbit developers looking at this issue? is there any official advice do we know?

[The_Lion]

Do you lose the connection if you leave the app in background? That means you open it, then press home button. Don't close the app. If it doesn't help switch off energy saving mode.

[GarethDPhillips]

The app is always in the background, as I dont really want to  leave the Fitbit app running, and the phone awake, during a run. I would assume it is not intended to work this way, and that it should be happy with the phone locked. 

however this is the next thing for me to try. I have an app that will force the Fitibt app to remain open, and will force the device to stay "awake" so I am hopeful this will work.  I will report back here, but I shouldnt have to do this !

[The_Lion]

For me it worked when I open the app, wait to sync, then press menu button. I usually run with another app. So I have to apps running, Fitbit in background.

[GarethDPhillips]

I find that I can start the activity OK, and the Blaze is connected for the beginning part of the run, but it will disconnect some way in, after seeminly random amounts of time, and then wont re-connect. 

As I say, I always have the app in the background, as I have another app I run with which is open in the foreground. 

I wil try forcing the Fitbit app to the foreground in the hope this offers a workaround, but I dont really want to have to do this (as there is then little point in using the tracker to start and stop the exercise at all) 

I dont undetrstand why the app cant continue to track the run if the tracker disconnects. Surely its just badly thought out. 

[The_Lion]

You have it in the same way like me: Fitbit in background, another sports app in foreground. So it's really strange that it works on my phone (S4 mini with Android 4.4.2) but not on your phone. But you start the run on the Blaze or not?

Another possibility: Is Wifi switched on? If so, switch it off. With later Android versions Wifi and Bluetooth (BTLE) don't work well together.

[GarethDPhillips]

I wouldnt say it doesnt work, as it does much of the time. Its intermittant, but a lot of my runs do suffer this problem, which ruins my tracking of the run. 

Yes I start the run on the Blaze. If I were to start it in the app, this would not occur I dont think, as the Blaze would not be connected, and the app would track the GPS regardless?

I have tried WiFi on and off, it does not appear to make a difference. 

[The_Lion]

If you want to see your stats on the Blaze you have to start it there. If it doesn't matter and you just want properly recordings of your activities then start it in the app.

Just another question: Is only the connection lost or is there also a gap in the map?

[GarethDPhillips]

Starting it in the app isnt really an option, I need to start it on the Blaze, otherwise there is no point in having it !

When the connetion drops I get a gap in the map, as it stops tracking the GPS at that moment. 

[The_Lion]

But you don't have any energy saving options or apps running?

[GarethDPhillips]

OK so I ran again tonight. I turned off WiFi, opened the Fitbit app, and the Blaze was connected (green dot). I started the run (from the Blaze), and left the app open, and the screen unlocked. 

3 mins in and it disconnected. I stopped, rebooted the phone and the BLaze, messed about for another few minutes, and it connected again. I then started a fresh run, and off I went.

2/3 into the run and it disconnected, so I have no data for the last 1/3

Im really sick of this, it isnt doing what I bought it to do. Far from it. If even having the app open and phone unlocked doesnt help, I dont know what will.

Tracking the run with the app is not an option, as I dont get heart rate, or any stats on my wrist. 

Starting to wish I got a full GPS watch, but I like the Fitbit "ecosystem: 

Is this common on Android, or is it the Nexus in particular. 

Is there anything else I can try? I cant think what. 

Thanks 

[The_Lion]

But you don't have energy saving options or apps on your phone running?

[GarethDPhillips]

The only energy saving options are the screen lock. I have disabled this, so no. 

No other apps running 

[The_Lion]

I don't have any other idea. 😞

On my S4 mini it helped leaving the app in background. Obviously the Blaze isn't for sports. It's only a fitness tracker. Meanwhile I'm using a Forerunner 35. Fits better on my wrist and oHR works better. I don't have to wave my arms to see the stats or even slap on it. That was really annoying. Screen off during workouts. Turning wrist or slapping on the Blaze during pushups or similar exercises to see the time elapsed, yeah. I'm not an octopus.

[jpat1990]

I have the exact same issues. When I talked to Fitbit they said it's
because I'm using the Google Pixel which doesn't have guaranteed
compatibility but your Nexus does, supposedly, so I'm still stumped for
both of us!

[GarethDPhillips]

It's rubbish. I'm sure it's an android thing, I think the Bluetooth LE is a bit flaky on android. I'm sure if I had an iOS device it would work ok. 

I'm just trying to find some kind of workaround, as this is the main feature I want the phone for. If I can't reliably track my runs, I may as well get another device.

Are you using Bluetooth headphones? There is a known issue with multiple blues devices. I am, as I feel I should be able to, but I will test without.

Also I dont seem to be able to reproduce the issue indoors, odd.

[The_Lion]

I track my runs with another sports app on my S4 mini. The last months with a chest strap connected. And nearly every run with a BT headset for music and audio feedback (distance, time, pace, HR). The first times the signal of the strap got lost after a few minutes. Then the developer changed several things an the BTLE connection stayed. Android and BTLE, there are a lot of problems. After the update of my sports app everything was fine with my chest strap. I could track my runs with full data. Additionally the Fitbit app was running in background, with the Blaze connected, showing HR and pace. And the music player with BT headset connected was running. No problems with the connection of 3 BT devices.