Support

Reporting a bug

Alarm bugs are hard to reproduce, because they usually depend on the exact phone and the exact Android build. Include as much of this as you can and the odds of a fix go up sharply:

• Phone make and model, for example Pixel 7a or Samsung Galaxy A54.
• Android version, and the manufacturer skin if there is one, such as One UI or MIUI.
• The Awake version, which is 1.0.0 for the first release.
• Which challenge was selected on the alarm that misbehaved.
• What you expected, what actually happened, and the time it happened.
• Whether the phone was locked, charging, or in a battery saver mode.
• Whether it is reproducible, and the steps if it is.

Send it to ywalum@gmail.com. If it is a security issue, please say so in the subject line and do not post the details publicly first.

Troubleshooting

• The alarm did not ring at all

  This is almost always battery optimization. Android, and in particular Samsung, Xiaomi, Oppo, Vivo, OnePlus and Huawei builds, will suspend an app it thinks is idle, and a suspended app cannot wake you.

  1. Open Android Settings, then Apps, then Awake.
  2. Open Battery and choose Unrestricted. Do not leave it on Optimized or Restricted.
  3. On Samsung, also open Settings, Battery, Background usage limits, and make sure Awake is not in Sleeping apps or Deep sleeping apps.
  4. On Xiaomi, Oppo, Vivo and OnePlus, find the Autostart or Auto launch setting for Awake and switch it on.
  5. Accept the battery exemption prompt if Awake offers it. That prompt exists for exactly this reason.

  Then set a test alarm for two minutes ahead, lock the phone, and put it down. Do not keep the app open: that hides the problem.

• The alarm rang late, or at the wrong time

  Awake needs permission to schedule exact alarms. Android 12 and later can revoke it, and some Android 14 and later builds ask for it separately. Without it the system is free to fire the alarm whenever it next feels like it.

  1. Open Android Settings, then Apps, then Awake.
  2. Open Alarms & reminders, sometimes listed under Special app access, and switch it on.
  3. Re-open Awake so it can reschedule with the permission restored.

  If the alarm fired at the right time but on the wrong day, check the repeat days on the alarm, and check that your phone's time zone and automatic time settings are correct.

• No ringing screen appeared, or nothing showed on the lock screen

  The full-screen ringing UI is delivered through a notification, so a denied notification permission takes it away.

  1. Open Android Settings, then Apps, then Awake, then Notifications, and allow them.
  2. Check that the alarm notification channel is not muted and is set to a high importance.
  3. Check Do Not Disturb. If it is on, allow alarms through it, or add Awake as an exception.
  4. Check that your alarm volume, not the media or ring volume, is turned up.

• The push-up or jump challenge will not start

  Those two challenges need the camera. If the permission was denied, and especially if it was denied twice, Android stops asking and the challenge cannot open the preview.

  1. Open Android Settings, then Apps, then Awake, then Permissions, then Camera, and choose Allow only while using the app.
  2. Make sure nothing is covering the front camera and that no other app is holding it open.
  3. Reps are counted from your whole body, so prop the phone where it can see you, in a reasonably lit room.

  If reps still do not count reliably on your device, please email the phone model. The counter is tuned per movement and that feedback is genuinely useful.

  The walk challenge is separate: it needs Physical activity permission rather than the camera, and Awake asks for it when you set the challenge up.

Still stuck, right now, with an alarm ringing

Press and hold the dismiss control for five seconds. The alarm stops immediately without any challenge. It gives no streak credit, which is deliberate, but it always works.

Other questions

The FAQ on the home page covers snooze, uninstalling, cost, and whether the camera challenges send anything anywhere. The short answer to the last one is no, and the privacy policy explains exactly why.