Version 2.89 doesn't stay connected to Versa

[vanderve]

Since my phone updated to V2.89 Bluetooth will not stay connected.

I've tried all the suggestion, eg reinstall, turn on 'stay connected', all the phone battery management stuff off, etc.

It is consistent in that, force close of app, unpair Versa, turn off Bluetooth, turn on Bluetooth, re-pair Versa, start app. Now runs for 15 to 75 minutes then will not connect again; go through this process again, same result.

It worked perfectly with version 2.88.

Moderator edit: Clarified subject

[LanuzaFitbit]

Hello @vanderve.

Thanks for bringing this up and sharing all of the steps that you have tried to get it to work.

In this case I'd like to ask some questions to better understand:

• What phone are you using?
• Is this only happening during the activities? Or is it connection in general?

Look forward to your reply.

[vanderve]

The Phone is an OPPO A57, model CHP1701 running android 6.0.1.
The problem is connection generally.
Also, this morning it continued to run for two hours (ride to work), the
only thing different is that I had not run any other application; then just
to see I run a game for a short time, then it stopped working. Not sure if
that is just coincidence or not.

[LanuzaFitbit]

Hello @vanderve.

Thanks for reaching back with those details.

It is possible that it is happening because the Oppo A57 is not part of the supported devices list. This means that the app has not been fully optimized to work with that phone.

As long as it fulfills the minimum requirements, Android 4.4 and Bluetooth 4.0, there is a possibility that it can work but we cannot guarantee it. Some users of unsupported devices have mentioned that following these steps helps with the syncing.

Let me know if you have any further questions.

[vanderve]

Yes one of the things I hate about Android, no two phones are the same.
I've tried all the suggestions in that link, they have no effect.

After some more testing; the Bluetooth connection fails when ANY other
application runs in the foreground (even the arrival of an SMS, I get the
notification then it stops communicating), so I am reasonably convinced it
is when Fitbit looses foreground processing. It is interesting that it
worked on the previous version(2.88) of Fitbit.

Thanks for your time, Steve

[vanderve]

Email from FitBit;

"Did one of these responses provide the answer you needed?"

Answer:

No solution has been provided

Moderator edit: Format