Force open peer socket and file-transfer

[Scorseze]

Is it possible to force open messaging socket between app and companion? It should reconnect automatically but often doesn't (need to restart watch app).

The same applies to file transfer: sometimes it gets stuck after enqueueing -> pending -> .... [should be transfered]. I can try several times with no go. What can I do about it?

Testing on Versa.

[JonFitbit]

It sounds like the Fitbit mobile app isn't running. Can you check that the Fitbit app isn't being suspended by your mobile phone's battery optimization.

[Scorseze]

Could it be the Fitbit mobile app isn't running as I'm browsing companion logs in it? Maybe some of its process respnsible for watch app <-> companion communication isn't running (hence socket doesn't reconnect).

Battery optimization in my Android 8.0 is off for the Fitbit app.

Wake interval for the companion is set to 5 minutes and I even try file transfer from the watch to wake up the companion (according to docs it should wake it up).

It's also a bit odd that the socket connection sometimes closes when I walk to a different room (I listen for open/close events in my watch app and display socket state. It's open, then I move away, it closes, then move back and after a few minutes it doesn't reconnect. If I restart the watch app, it reconnects).

[HowardMcD]

I was having trouble with this all morning and finally fixed it by re-installing the Fitbit app on my phone.

I have also now excluded it from battery monitoring in case that was the issue.

Howard