Sleep latency change and deep sleep measures

[userU46noblzs2]

Hi there!

This past week Samsung replaced the sleep cycles in the health app with sleep latency. I wish they would have kept it the old way, and added sleep latency as a feature. However, since the change my deep sleep also changed, well, at least that's what the app is telling me. I suddenly only get exactly 20 minutes, for four nights in a row now. That can't be right. 

Any suggestions / insights on that? It almost appears it doesn't measure properly. 

Thanks!

[mar_mel]

Dude, it's health - I'm always trying to better myself. You do you.

If you're not affected by an issue, there's zero reason to chime in aside from trolling and distracting from the reported issue(s).

Retired software engineer engineer here, but thanks for your feedback on how I should proceed.

[realaud · Accepted solution]

You are reporting in the wrong place, this is a peer-to-peer user forum.  The only official way to garner a fix for your perceived issue is to put in an error report.

https://us.community.samsung.com/t5/Tips-Tricks/How-to-Send-Feedback/ba-p/3001692

[userU46noblzs2]

Agreed. This app is out of whack right now. Mine doesn't really sync anymore, unless I do it manually, the stress recording is off, and it also seems changes were made by Samsung in that app area, and deep sleep is still not working.
This is very disappointing. I will be reaching out to customer support today again and no reply from Samsung has made it to me or us.

[dazone75]

The sleep latency numbers are totally inaccurate. I've lost almost all my deep sleep after the last update on my Galaxy watch 7.

[rcm62]

Samsung Watch 6 is terrible at detecting when I get to sleep. As a result, since they introduced Sleep Latency in the score, the result is completely unusable. I may have to switch to an Apple watch is this doesn't get fixed. It seems like the reasonable step to take would be to revert back to the previous score computation using the number of cycle and removing the sleep latency as a factor since it is completely unreliable. 

[userU46noblzs2]

Well, a new software update just came out. That was related to the watch and the app. Hopefully this solves some of the issues we all experienced. I keep my fingers crossed!

[Samuraieclipse]

Terrible update. I hope they listen to users and fix it 

[MW341red]

Sleep latency jumps from 1 minute to 1 hour and 40 minutes the next night. I have had multiple sleep latency scores over 2 hours and also 1 minute.

[userU46noblzs2]

Same. Even with the watch and ring on it's off every now and then, but by hours.
If I fall asleep fast, the score goes down, which I don't get at all.

[Members_4cRCihK]

Still an issue and still Sleep latency:  According to sleep latency it took me 7hours and 20 minutes to fall asleep, 7 hours 53 minutes of total sleep, 7:13 actual sleep time. Just wildly inaccurate sleep latency.