One UI Watch devices
Sleep tracking with Galaxy Watch 4 and Galaxy Watch 5 (running the ONE UI Watch OS) requires a companion app installed from the Play Store on the watch.
|
Unfortunately due to limit put for non-Samsung apps, we cannot read SpO2 or HRV from those watches at the moment. |
1. How to set up
-
Make sure the watch is connected to the phone.
-
Go to app list on your watch, select Play Store.
-
Find Sleep as Android and select Install.
-
After the companion app is installed, you can enable the connection in Settings → Wearables → Use wearable → Galaxy Watch 4+.
-
Test the connection in Settings → Wearables → Test sensor - you should see a graph reacting to your movement (a short delay is normal, data are sent in batches).
-
For HR data, enable Heart rate monitoring in Settings → Wearables.
|
Make sure the sleep tracking activity is allowed in the background within Wear app in Galaxy Wear > Watch settings > Apps > Sleep tracking > Allow background activity. |
FAQ
-
Make sure no system restrictions are applied to Sleep as Android: Check our guide here.
-
If the guide won’t help, send us your log using Left ☰ menu →
Support →
Report a bug.
Sleep tracking with Wear OS device requires a companion app installed from the Play Store on the watch.
How to get there:
-
Make sure the watch is connected to the phone.
-
Go to app list on your watch, select Play Store.
-
Find Sleep as Android and select Install.
-
After the companion app is installed, you can enable the connection in Settings → Wearables → Use wearable → Wear OS.
-
Test the connection in Settings → Wearables → Test sensor - you should see a graph reacting to your movement (a short delay is normal, data are sent in batches).
|
Sleep tracking collects data the night and they are analyzed in real-time. This means the watch must stay connected with BT during sleep tracking. |
For all currently supported devices, check out list of compatible devices.
If you’d like us to integrate another device, please add it as a suggestion to our suggestion forum. Also please check whether the device has an API so we can integrate it.
Google made it impossible to start screens from the background on newer Android versions. This is why we can no longer show the alarm screen with the big buttons under usual settings. The app can just show notifications from the background if the screen is on when the alarm starts. If the screen is locked we usually are able to show the full-screen alarm.
-
Go to Settings → Alarms → Always fullscreen alarm (might be hidden under Advanced in Snooze/Dismiss section), and enable this option.
-
It will take you to the system settings, where you need to grant the Draw over other apps permission.
On Xiaomi/MIUI, you need to grant special permission to Sleep as Android so that it may unlock your screen during alarm.
-
Go to System Settings → Permissions → Advanced Permissions → select Sleep app and give it permission to access Lockscreen.
|
If you are using a Captcha task from the Captcha add-on, please, make sure the permission is granted to the add-on as well. |
When alarm goes off, it does not disable the lockscreen and you have to manually unlock the device to tap snooze or dismiss.
You may have Sleep as Android enabled under Border lights (Edge Lightning on some versions). This causes the alarm popup to not display over the lockscreen, as the notification is being shown as a light around the edge of the screen.
-
Disable Border lights for Sleep as Android in your device’s settings.
On Wear OS platform and ONE UI Watch (Galaxy Watch 4 + 5), we use gentle vibrations for even more natural wake up.
It starts with a single vibe, another in 30s, than again in 20s and so on. After few minutes the vibrations will be continuous.
If you are worried this won’t be enough, you can set a delayed start of alarm sound on the phone. And there is always the backup alarm.
This can be a result of multiple things, so please make sure to do the following troubleshooting:
-
Make sure you have Sleep as Android Gear Addon installed on your phone
-
It can happen that the addon cannot be started by us if it was force stopped previously. In that case please go to Play Store app on your phone, open addon page tap on “OPEN”.
-
Opt out of any battery savers that you might have on your phone, for all involved apps (Sleep as Android, Sleep as Android Gear Addon, Samsung Accessory Services) – to find out how to do that, please consult dontkillmyapp.com
-
Samsung Accessory services sometimes misbehaves and prevents connection to the watch for 3rd party apps. Please uninstall and reinstall it.
If the tracking stops completely after few minutes, the background processes are restricted by your system.
-
Make sure no system restrictions are applied to Sleep as Android, or any companion app for a tracking with wearable: Check our guide here.
-
If the guide won’t help, send us your log using Left ☰ menu →
Support →
Report a bug.
-
Please make sure that you are not accidentally starting the Sleep as Android app from your watch. This would start sleep tracking immediately.
-
Make sure you are not using automatic start of sleep tracking in Settings → Sleep tracking → Start sleep tracking.
You can find more information about automatic sleep tracking start here.
The red block indicates that something went wrong with tracking at that time and the device stopped providing sensor data for some reason. Usually those are some non-standard battery optimizations or battery savers, the battery gets too low so we preserve it for the alarm or connectivity issue if you use a wearable.
1. Battery restrictions
Make sure no system restrictions are applied to Sleep, or any involved apps like wearable companion app).
See our guide here, and follow the instructions.
2. Too low battery
When the battery is too low (usually below 10%), data collecting is terminated to preserve enough battery for alarm.
When the battery was too low, there is a battery icon is displayed on the graph:

3. Connectivity issues with a wearable
When the connection with the wearable is lost, you can see red sections on the graph. The app always tries to reach the wearable again.
The graph can look like this:

-
Opt-out from any battery restrictions is applied by your system (https://dontkillmyapp.com/)
-
Pair the wearable with your phone in System settings.
-
Make sure the BT is not lost, and try lowering the distance between the phone and the wearable.
-
Try settings the device as Trusted device.