hi, I’ve noticed that sometimes the NFC function of the alarms just doesn’t seem to activate. The alarm with the NFC CAPTCHA is my last alarm of the morning - I have the NFC tag in my kitchen and it gets me out of bed. Most of the time it works just fine but sometimes it will randomly just not turn on … as in I wake up confused realizing I’ve overslept and am now late to work and its because the NFC CAPTCHA alarm either just didn’t turn on or it turned on without the NFC function (I don’t know which one it is as I’m barely awake when I reflexively snooze/dismiss my alarms in the morning) and I would remember if I had gotten out of bed and dismissed the NFC and then went back to sleep after. I rely on this feature to get me up in the morning since I am a chronic oversleeper and I am not sure what causes it to sometimes not work (besides the occasional phone software update in the middle of the night which I know messes it up, but this happens sometimes even when my phone hasn’t updated).
Steps to reproduce: n/a - see above
Version of Sleep as Android: Samsung Galaxy S25 Ultra
That’s really frustrating especially if you rely on NFC to get out of bed. A few quick things to check: make sure battery optimization is disabled for Sleep as Android and NFC services, confirm NFC stays enabled overnight and try re adding or re resting the NFC tag in the app. Also check whether Bedtime mode, DND or overnight system updates could be interfering. If it keeps happening, enabling debug logs and sharing them here would help the devs see whether the alarm or the NFC step is being skipped.
Hi @Mira_Falicki, may I ask for more details about your alarm configuration?
Are you using chained alarms, close to each other?!!
We do not support and actively discourage chained alarms. Sleep as Android approaches this from a different angle.
If you want to make sure you wake up but want some flexibility in the exact time you wake up, set up a captcha for your morning alarm. This will allow you to snooze (which you can limit, so you can’t snooze indefinitely), but won’t allow you to dismiss the alarm until you prove you’ve woken up.
So instead of creating a chain of alarms, where the first alarm starts the snoozing, and the last alarm should have ended it, you can have one alarm and limit snoozing (Settings → Alarms → Snooze), and once the snooze limit is reached, you will only be allowed to dismiss the alarm and solve the CAPTCHA.
You can halve snooze intervals each time you snooze, limit the maximum snooze time, or set a fixed snooze time…
Creating a set of alarms nurtures a bad habit of relying on “future alarm” in a row, which will be really hard to break later. It can also lead to overlapping alarms.