Open felixk101 opened 7 years ago
I've discovered a cheap but ugly workaround for this issue. If I only have one connection to the Empatica wristband, almost half of my data had timestamps that were out of order, which would be really frustrating to simply discard. But, by opening 4-6 more connections, the "invalidity" drops from 47% to 2%.
Hi, I'm just taking a look at what the console prints out when I subscribe to certain stream, and occasionally some messages appear later than they should be.
Does this have anything to do with the fact that
HandleResponseFromEmpaticaBLEServer(_response);
is being called before "All the data has arrived"?