The server/app requests all data since the last chunk it got. This will ensure we don't loose data
Server/app requests the badge to start recording, with a timeout. Is the badge hasn't been contacted by a server for that timeout, it will stop recording (saving battery). There is another command that can be used to ask the badge to stop recording
Server/app sends the current time every time it communicates with the badge (or at least, it can do that)
implications
Average volumes are higher we speaking. That's probably because there are less 0's pulling down the average
"Lag" for getting new data is much small. Both because the chunks represent a shorter period of time, and because we send incomplete chunks
Gaps and overlaps between chunks. Because we send out the time very frequently, the time on the badge is less consistent.
changes:
implications