Skip to content

faq & known issues

answers to common questions and problems. if none of these solve it, capture a debug log (below) and share it with the developer — the app is local-only and reports nothing unless you choose to send it.

capturing logs for a bug report

the app keeps a plain-text log on the device, one file per day, kept for a week. it records what the app did — sessions starting, audio events, sync runs, and crashes — at the level you choose.

  • open settings > troubleshooting.
  • set log level to debug so the log captures fine detail. (the default, info, already records the important events.)
  • reproduce the problem, then open view logs.
  • pick the day it happened (today is marked) and tap the share button to send the day's file, or copy all to paste its contents somewhere.

logs stay on the device unless you share them. they can contain app internals and file paths (for example, the name of an imported sound), so check a day's contents before sending. clear logs in the viewer deletes every stored file.

soundscapes or bells stop playing

  • make sure the session is actually running — the media notification shows a live session. previews stop on their own after about ten seconds by design.
  • a notification, navigation prompt, or spoken prompt can briefly duck the soundscape; it should fade back when the interruption ends. if it stays silent, that is a bug — capture a debug log of the session.
  • if it happens when the screen turns off, try again with the screen kept on (a session option) and note the difference in the log you share.
  • on the watch, see the Wear OS guide — ambient mode can suspend audio on some devices; the keep awake setting is made for exactly that.

the watch session goes silent or desyncs

  • turn on keep awake in settings on the watch — it holds a wake lock for the session.
  • the watch can silence the paired phone instead of itself when it lacks do-not-disturb access; the silence watch settings row explains the one-time adb grant that fixes it.
  • after raising the watch, the session recovers audio, bells, and haptics on its own. if it does not, capture a log on the phone at debug level.

reminders do not fire

  • check the exact-alarm permission and battery-optimization exemption — see Android reliability in the reminders guide.
  • a reminder's snackbar shows the next scheduled time when you save; if none appears, nothing was scheduled.

media controls are missing from notifications

  • the app asks for notification permission when a session starts. if it was denied, sessions still run — only the media card is missing. re-enable notifications for the app in system settings.