Favorites and Scheduler
Favorites
Anything playable can be saved as a favorite: a surah by a reciter, a radio station, or a direct file path. Favorites are stored on the device, so they appear identically in every browser.
- Add or remove: the Favorites page has a form to add one by surah and reciter, by stream, or by file path, with a real surah picker; each saved favorite has a delete control on its row.
- Play counts: the Favorites page tracks how often each favorite has been played, which quietly sorts your real habits to the top.
- One-click playback: the Favorites page is the fastest dashboard route to the recitations you return to.
Scheduler
Schedules start playback at a chosen time: a morning surah, evening recitation, or a radio station at a set hour.
Creating a schedule
On the dashboard's Scheduler page, fill in the form and set:
| Field | Meaning |
|---|---|
| Time | 24 hour clock, device local time |
| Repeat | Once, daily, or specific weekdays |
| What to play | A surah and reciter, or a station |
| Volume | Optional volume override for this schedule |
| Enabled | Toggle without deleting |
Schedules live on the device and survive reboots.
The clock requirement
A schedule can only fire when the device knows the actual time. Two ways it can:
- Over the internet (SNTP), shortly after WiFi connects, with periodic re-syncs.
- From the DS3231 clock module, when fitted: the coin cell keeps time through power cuts, so schedules work with no network at all, seconds after boot. SNTP still corrects the module whenever it is available, and Settings offers a manual "use browser time" for fully offline installs.
Two consequences:
- Set your timezone in Settings (pick a zone from the dropdown or enter a custom POSIX rule for daylight saving). Schedules run on local time; the hardware clock stores universal time, so changing timezone never confuses it.
- Without either time source after a power cycle, the clock is unknown and the scheduler deliberately stays idle rather than firing at wrong times. The idle screen showing
--:--means exactly this state.
Behavior details
- If something is already playing when a schedule fires, the schedule wins and playback switches.
- Missed schedules do not fire late: if the device was off at the scheduled minute, that occurrence is skipped.
- "Once" schedules disable themselves after firing.
- A device put to sleep from the dashboard wakes itself for the next enabled schedule, provided the DS3231 module is fitted: its alarm pin wakes the chip, the clock module seeds the time, and the due schedule plays within seconds of waking.