Troubleshooting

My access code won't work

Codes look like LUDIN-XXXX-XXXX. Check yours character by character against the email — it's typed by hand, so a transposed character is the usual culprit, and it's worth copying it straight from the email rather than retyping. If it still fails, email ludindreaming@gmail.com with the code and we'll look it up.

I never got a code

Check your spam folder first — the early access and waitlist emails land there more often than anywhere else. If it isn't there, email ludindreaming@gmail.com from the address you signed up with and we'll resend it.

I got a new phone and my code won't activate

Expected. Each code activates on one device only, so it can't simply be re-entered on a second phone. Email ludindreaming@gmail.com and we'll move it across for you.

The screen went black and I can't get back to the app

Tap anywhere on the black screen. Every armed sequence blacks the display out on purpose, so a lit phone doesn't keep you awake or contaminate the light cue. It isn't frozen — it's waiting.

Nothing fired overnight

Work through these in order:

• Was the sequence still armed? Tapping the black screen returns you to the app. If you tapped it in the night, check whether the sequence was still running.
• Did the phone have battery? A sequence armed for six hours needs the phone to still be alive at hour six. Charge it, or leave it plugged in.
• Was the delay longer than you meant? Delays count from the moment you press Start, not from when you fall asleep. A 90-minute delay armed at 11pm fires at 12:30am regardless of when you actually dropped off. If you armed it going back to bed after WBTB or for a nap, the delay should be short — a bedtime-length delay will overshoot the whole session.
• Sensor-Based only: the model may not have reached its confidence threshold. A night with no cue is a real outcome, not necessarily a fault — see Sensor-Based flashing.

The cue woke me up completely

The cue is too strong for you. Turn it down in this order:

• Flashing: shorten the flash duration first, then reduce flashes per burst. Leave the repeat count alone — it's the individual flash that jolts you awake, not the number of attempts.
• Audio: lower your phone's volume, and lengthen the gap between repeats so a missed cue isn't immediately followed by another.

I slept straight through it

Go the other way, but add attempts rather than intensity: raise the repeat count so more bursts fire across a longer window. A brighter, longer single flash is more likely to wake you than to reach you. If you're on Time-Based, the delay is more likely to be the problem than the burst — you may simply have been cued outside REM.

I've used it for a week and had no lucid dreams

This is the normal experience, and it's worth saying plainly: lucid dreaming is hard. The best evidence-based techniques produce lucidity on a minority of nights even for trained practitioners, and a cue only helps if you're primed to notice it.

The things that move the needle fastest, in order:

• Check you're not arming cues at bedtime. This is the most common mistake and the biggest one. The flashing and audio tools are built to be armed after a WBTB wake or at the start of a midday nap. Armed at the start of a normal night, they mostly fire into non-REM sleep and there's nothing there to become lucid inside.
• Try the nap route. If WBTB is too costly, a midday nap reaches REM fast and doesn't damage your night. It's the easiest place to get a first result.
• Journal every morning. Recall is the foundation — see Sleep Journal. If you don't remember dreams, you won't remember lucid ones either.
• Change one thing at a time. Changing four settings a night means never learning which one mattered.

Sensor-Based never fires

Check View last session first, so you're working from what actually happened rather than a guess. Then, in this order:

• Placement. Phone on the mattress, screen up. Not a nightstand, not under a pillow. This fixes it more often than any setting.
• Something else on the bed. A partner or a pet adds movement that isn't yours. Raise max movements allowed in window to make Ludin more forgiving.
• Raise the movement threshold a step, so less counts as movement.
• Shorten the quiet window a step, so Ludin needs less time before it will cue.

Change one at a time and give each several sessions before judging it.

Sensor-Based fires at obviously wrong moments

Make it more selective, in this order: lengthen the quiet window, then lower the movement threshold, then reduce max movements allowed in window. Again, one at a time.

Check View last session before changing anything — guessing at what happened overnight is how people end up tuning the wrong setting.