Sleep as Android > FAQ

FAQ

Alarms

See https://sleep.urbandroid.org/documentation/faq/alarms-sleep-tracking-dont-work/

Permalink

General

See https://sleep.urbandroid.org/documentation/faq/alarms-sleep-tracking-dont-work/

Permalink

Sleep tracking

See https://sleep.urbandroid.org/documentation/faq/alarms-sleep-tracking-dont-work/

Permalink

Usually battery consumption issue or related issues causing phone over-heating during sleep tracking are not caused by the sleep tracking directly.

In most cases sleep tracking itself is not consuming too much battery (usually around 1-2% per hour of tracking). But because we hold a wake lock (keeping the phone awake) any other usually badly written apps may access the CPU extensively during the sleep tracking time. We would suggest checking which services are running before you get to sleep. For us it is hard to debug this. Also battery statistics are not a hint here as all battery consumption is accounted to the app which holds the wake lock even it did not consume the battery (this is by design in Android).
A good test would be to reboot your phone before sleep tracking (or kill any unnecessary services running) and see if sleep tracking will still consume too much battery afterward. Features within Sleep as Android which may cause higher CPU load during tracking include noise recording. You may try tracking without it for a reference. Also I would strongly recommend to track with airplane mode on.
Category: Sleep tracking
Tags: battery, hot
Permalink

Battery saving mode currently resumes full tracking before the smart wake up period in order to find the best moment for your wake up, so the tracking uses up just a fraction of the battery consumption for the whole night. If the battery would drop under your defined stand-by threshold (default: 10%) the battery saving mode will re-occur.

Category: Sleep tracking
Permalink

In most cases sleep tracking itself is not consuming much battery (usually around 1-2% per hour of tracking). But because we hold a wake lock (keeping the phone awake) any other usually badly written apps may access the CPU extensively during the sleep tracking time and the consumption is anyway mistakenly accounted to the app holding the wake lock (Sleep as Android in this case). We would suggest checking which services are running before you get to sleep and try to kill some of them or reboot your phone prior tracking. For more details, please read Troubleshooting.

Category: Sleep tracking
Permalink