WS

WakeSage

Alarm-first for Android

Home Guides Privacy Support GitHub

Support

WakeSage Help Center

Reliable wake-ups with clear troubleshooting steps.

If you want direct help, email support@wakesage.com.

For faster response, include phone model, Android version, and what is happening when the alarm should ring.

Frequently asked

My alarm did not ring on time

Check exact-alarm permission, notification permission, and battery optimization settings. Rebooted devices can reset scheduling state, so a full app sync after reboot helps. The app is local-first by design and does not keep remote fallback services.

The ring screen is missing in the first wake attempt

Confirm full-screen alarm visibility is enabled for WakeSage and system Do Not Disturb does not block wake audio. WakeSage needs device-level alarm permissions for the strongest wake behavior.

Camera proof is not available

Optional camera proof may require camera permission. If camera is denied, WakeSage will still ring and can continue with standard wake flow.

How does accountability/contact flow work?

Accountability contact usage is optional and uses selected local contact data to send accountability context. WakeSage does not require account sign-in for this flow.

What to try first

  1. Verify alarm time and repeat state are active.
  2. Run a quick permissions sweep in the app for alarm, notification, and battery settings.
  3. Test once with Demo wake flow if available in the app.
  4. Send one support message with device details and a 5-step timeline.

Reliability guides

How Android exact alarms work Battery optimization and alarm reliability WakeSage privacy and local-first design

Still need help?

Email support with issue details and your WakeSage build ID from Settings:

Email support

WakeSage

Alarm-first for Android. Designed for clear mornings.

Guides Privacy Support support@wakesage.com