Print this page with your browser's Print command, or copy the labels into your own local notes. The blank record is static: there are no fields to fill in online or results to submit. No Moonfade account is required.
Run a short, awake check
- Keep the test controlled. Stay awake. Use replayable media that you can pause safely, at a comfortable volume, with the device within reach. Use the same player, media and speaker or headphone route for both runs. Do not use a live call, an alarm or a safety-critical session.
- Record the setup below. Note versions and the player's own sleep-timer or autoplay settings. Turn the player's own sleep timer off for this check; note other automatic stopping behavior. Check Android's screen timeout so natural timeout does not masquerade as Moonfade lock. Do not record private titles, account details or listening history.
- Choose one configuration. For the lock-only run, set Stop audio & video off and Turn off the screen on. For the combined run, enable both. Choose a 1-minute countdown and note Fade out from 0 to 60 seconds; a positive value makes gradual volume change easier to observe in the combined run.
- Start playback, then the timer. Note the playback position. Tap Start in Moonfade and complete any required Device Admin activation before the countdown begins. Activation enables Turn off the screen. Confirm and record the actual settings after activation; do not assume an earlier switch state survived. Keep the timer notification available and avoid changing settings during the run.
- Watch the ending. With Stop audio & video on, countdown completion precedes the configured fade, then the audio-focus pause request. A 0-second fade has no gradual interval. With it off, both fade and audio-focus request are skipped, even if a fade duration is stored. Display lock is requested separately when enabled, after any enabled playback ending. Record what you hear and see around expiry and through the fade interval.
- Check the player afterward. Wake/unlock the device if needed and inspect its paused/playing indicator and playback position without pressing Play first. Silence or a dark screen alone does not prove pause. Note anything unclear, restore your preferred settings and volume, then repeat using the other configuration. If the setup changes or the run is interrupted, keep it inconclusive and repeat a short run.
Why no playback-only run? In the released app, switching off Turn off the screen removes Device Admin access. Starting another timer requires activation again and enables that setting. This method therefore uses lock-only and combined configurations; it does not prescribe a lock-free playback-only start or changing permission during a countdown.
Record the exact setup
Leave every observation blank until you run the check. Keep this record on paper or in local notes.
- Date and timezone
- Device make / model
- Android version / build
- Moonfade version / build
- Media player name / version
- Output route and headset model, if relevant
- Countdown / Fade out / fade curve
- Player sleep timer / autoplay / Android screen timeout
- Starting media volume / notification availability
- Setup changes between runs
Record two separate runs
Each blank record starts not run. Fill in observed behavior, not assumed internal request status.
Lock-only configuration — not run
Stop audio & video: off. Turn off the screen: on. Fade and audio-focus request are skipped; any playback response must still be observed, because a player may react to display state.
- Run date/time and attempt number
- Actual settings after activation
- Playback position before / after
- Volume before / during / after
- Player response: paused / continued / unclear
- Display: stayed on / went off / unclear
- When changes happened relative to expiry
- Unexpected interruptions or inconclusive observations
Combined configuration — not run
Stop audio & video: on. Turn off the screen: on. Record volume change, player pause/continuation and display state separately; none proves the other.
- Run date/time and attempt number
- Actual settings after activation
- Playback position before / after
- Volume before / during / after
- Player response: paused / continued / unclear
- Display: stayed on / went off / unclear
- When changes happened relative to expiry
- Unexpected interruptions or inconclusive observations
Read a result within its limits
The app's audio-focus and display-lock requests are implementation steps, not directly observable from this worksheet. Record the player's visible response and display state; do not infer that Android accepted a request, diagnose a mechanism from silence, or treat an app counter as proof of physical pause or lock.
A successful run applies only to the versions, settings and output route you recorded. It does not establish universal compatibility. Repeat after a relevant player, Android, device or output-route change. Keep differences and inconclusive runs rather than turning one result into a supported-app claim.
Privacy choice: this method does not require enabling Share anonymous usage results. That optional native setting is off by default and separate from advertising choices and website measurement. Worksheet notes are not collected by this page; the website's existing aggregate measurement remains described in the Privacy Policy.
Use the guide for the next question
- Player-response test guide for checking what the player actually did.
- Headphone check guide for recording your output route.
- Countdown and fade order for the configured ending sequence.
- Media keeps playing for recovery, or Moonfade support for help.
Original Moonfade method and blank recording labels, written for this resource. No third-party media or test findings are reproduced.