One UI Watch devices - Sleep as Android

Sleep tracking with Galaxy Watch model 4 and newer models (running the ONE UI Watch OS) requires a companion app installed from the Play Store on the watch.


This is a companion discussion topic for the original entry at https://sleep.urbandroid.org/docs/devices/one_ui.html

Has something changed with the settings? I can’t find any option to allow background sleep tracking. The most there is, is the sleep app, which has no additional options.

Hello. I recently started to use SleepAsAndroid on my phone along with Samsung Galaxy Watch 6 Classic. What bothers me from beginning is that the alarm overlay does not show up instantly on the watch so I have to wake the screen manually, then tap on the icon on the bottom of the screen and only then I can dismiss the alarm.

Doing some research, I found this thread and explanation that the full screen alarm is not possible because the permission needed has not being implemented. Is it still true? As far as my Android/WearOS knowledge goes, “Draw over other apps” permission is needed. True, Samsung OneUI watches does not provide a way to grant this permission but it can still be done with ADB. I’ve done that for some other apps like AutoWear and Shake Launcher.

If I’m right, can I expect this feature in a forseeable future?

1 Like

On my Galaxy Watch 6 Classic, I am noticing stark differences between the tracking of sleep cycles by Sleep as Android versus default Samsung Health app. Is there any way to tell which one is more accurate?

Bump. Is this thread monitored?

Hi, big sorry I missed your post.
The mapping of N1, N2, and N3 phases (the standard actigraphy) into deep sleep and light sleep does not have any standards or rules, so each app can use a different approach.
We map a small part of N2 without significant movement as deep sleep. It made more sense and produced slightly better results when compared with Sleep lab data (if you are interested, this is explained here or here).
Other apps may map only N3 and a smaller fraction of N2 as the deep sleep phase (we don’t know exactly how their algorithms work; this is just the feedback we see). The most prominent difference is probably with S Health, which reports little deep sleep in comparison to our findings. So they probably map only the N3 as deep. This does not mean one approach is better than the other; it is just a different method.
We recommend using all approaches even when the results don’t match - the more data you have, the better.
But do not compare one night between the apps. It is much better to evaluate your long-term progress in each app individually.

Thank you. That makes sense, and highlights the danger of presuming too much when you interface the two apps together. For example, based on what I’m understanding you to say it would seem that their diagonal gray bands which indicate “typical” results for each phase would then be skewed.

Is there an analogous place within Sleep as Android which shows the typical ranges, possibly based on age group? I am assuming the AI assistant uses such ranges in its algorithms when it’s giving paragraphical feedback, but I was wondering if you could see those ranges just simply in the graph itself.

Hi, we do not have typical ranges of sleep phases in the app to be honest. Sleep is highly individualistic, and showing averages (even based on the age group) comes with a risk of biases and incorrect conclusions. Some users might feel anxious if they don’t fit the “expected” range. And making users worry about their sleep may have a negative impact on their sleep. What do you think about this?
The advice section works with your averages, and the charts show you the long-term progress. Evaluating your progress within your results feels better.
But this is just the current state, if we have more requests on this topic, we will for sure reconsider.