Most recent activity
-
-
Sleep Log seems to be quite unreliable...
Just downloaded the current file and only got two entries, starting at 2pm today.The previous file in the app ends 2 weeks ago.
I never press delete (yet), I only ever download file.
I have downloaded files before between these (now nonexistent) times and data was present, or in binary, or not present for times... no pattern really :/ -
To do that we probably would need to match their acceleration data against acceleration data from the JS2 since thats probably the only common denominator. Then we could map the current values to their values/sleep levels.
Not done in 5 minutes;)I do like that they go top down ( 0 = unknown, 1-3 = sleep stages 3-1, 5 = REM, 6 = awake, 7 = movement), it looks weird to be awake at 0 and sleep at 4 in the current log data;)
-
Well I am all for more data (while its not a huge drain on the battery or user configurable).
In this case were the data is captured anyway (i think if it sums up all intermittent values?) it probably increases accuracy significantly.I mean sleep tracking was one of the main reasons I got a smartwatch for in the first place:)
Now what can be done about identifying sleep or not probably depends on how common a tight boundary really is. If most people have a clearer cut off between the two states then I am an outlier and could be treated as such. If its common then at least the initial values should be adjusted and the potential range tightened (or better documented)
We need more data;)
-
The lit up display sure helps with reading the fineprint.
Still think name would be better placed as main item due to more space -> larger font.
Also would consider cutting the chatter short - Don't need the polite "Incoming Call:" if I'm short on space in the first place, "Caller:" would totally suffice (imho). -
-
Yes, looked at older data and its always the same.
O/c I do have movement values of up to 100 too during the day so that's not the entire range, but the only range that applies to me sleeping.Sleep value was 19, the small peak at 01:10 was 23 and the big peak at 3 was 56. Dont ask me why I was up in the middle of the night :/
Bottom Graphs are from recorder, upper one is Health app. Thought it interesting how the same data looks different giving the different aggregation levels (60s vs 10m)
Sorry for the delayed answer...
I basically stopped getting data off the js2
Between unreliable apps and imprecise values I lost interest at some point