Hello everyone, hope you all had a nice weekend!
Thank you very much for the very valuable tests. I’ll cater to the individual issues below one by one.
App crashing on the watch after ~40 minutes
I’m now trying to pinpoint the issue, which I hope to be something on my part. I don’t think that’s something in the Fitbit OS itself is killing the app as there is supposed to be no battery management/optimalization AFAIK on the watch that would be capable of killing the app apart from when it runs out of memory dedicated to its container. So actually running out of memory is the most likely culprit.
Server running throughout the day
The server on the phone does not need to run all day, it only needs to be running prior to starting sleep tracking and can be turned off after sleep tracking ends.
However, when sleep tracking is not currently running, the server does not do any processing, and thus does not drain any battery. It doesn’t keep your phone CPU alive (ie. does not keep a wakelock) and consumes absolutely no resources apart from statically occupying a few kilobytes of memory.
Starting sleep tracking from the phone
It is only possible to start sleep tracking from the watch. Due to constraints of the Fitbit SDK, it is not possible to start a watch app from the phone.
I have noticed a flaw in the flow if you try to do it the other way - if you start sleep tracking from the phone, we still start it and signify that Fitbit is connected, so that needs to be fixed.
This also most probably has something to do with the #sonar tags appearing along the #watch tag on the graph for @djjstew as you’ve correctly observed.
Heart rates not working
That’s a bug somewhere on my part, they should be working, I’m looking into it.
@treyhendon yep I assume you got them through FitToFit…