An unattended display has a constraint that no ordinary browsing session has: if anything goes wrong, nobody is going to fix it. A screen that dims after ten minutes, a lock screen that wants a passcode, an update that reboots at 3 am — each of these turns a working display into a dead one for the next twenty-five hours. This guide covers every setting worth changing before candle lighting, device by device.
The general rule is worth stating up front: configure for the failure you cannot repair. Prefer the boring, over-cautious option every time.
The four things that actually kill a Shabbat display
In rough order of how often they cause trouble:
- Screen sleep and auto-lock. Every device ships with a timeout of a few minutes, and most cap the adjustable range well below twenty-five hours.
- Automatic updates and restarts. A device that reboots overnight comes back to a lock screen, not to your dashboard. This is the failure that people forget entirely.
- Power. No tablet in existence runs a lit screen for twenty-five hours on battery.
- Notifications and popups. A single full-screen alert, cookie banner or “rate this app” prompt can obscure the whole display.
Everything below is aimed at one of those four.
iPad and iPhone
- Settings → Display & Brightness → Auto-Lock → Never. This is the essential one. Note that iOS hides the Never option when Low Power Mode is on, so turn Low Power Mode off first.
- Settings → Focus → Do Not Disturb, scheduled to cover Shabbat, so notifications do not cover the screen.
- Settings → General → Software Update → Automatic Updates → off for the automatic install, at least over Shabbat.
- Add the site to the Home Screen from the Safari share menu. Opening it from the resulting icon runs it without browser chrome, which both looks better across a room and removes the address bar as something to tap by accident.
- Guided Access (Settings → Accessibility → Guided Access) locks the device to the single running app, so a curious child cannot navigate away. Set a passcode you will remember — and be aware that ending Guided Access requires interacting with the device, so decide in advance whether that suits you.
Menu wording shifts slightly between iOS versions, but the paths have been stable for years.
Android tablets
Android's ordinary screen timeout usually maxes out at thirty minutes, which is not enough. The setting you actually want is in Developer options.
- Enable Developer options: Settings → About tablet → tap Build number seven times.
- Settings → System → Developer options → Stay awake (sometimes “Stay awake while charging”). With the device plugged in, the screen stays on indefinitely. This is the single most useful Android setting for a wall display.
- Settings → Display → Screen timeout → longest available, as a belt-and-braces measure.
- Turn off adaptive battery and any battery saver, which can throttle background activity and interfere with a page that refreshes on a timer.
- Disable automatic system updates in Settings → System → System update, and pause automatic app updates in the Play Store settings.
- Do Not Disturb on, scheduled across Shabbat.
Amazon Fire tablets
Fire tablets make excellent cheap wall displays and have two quirks of their own.
- Settings → Display → Display Sleep → longest available, and turn off Show Screen Saver, which otherwise replaces your dashboard with a photo slideshow.
- Ad-supported models show ads on the lock screen. If the device ever locks, you get an advert instead of a forecast. Amazon will usually remove lockscreen ads for a one-off fee, or you can simply make sure the device never locks.
- Fire's Silk browser works, but installing Chrome or Firefox generally gives a better result.
Windows
- Settings → System → Power & battery → Screen and sleep. Set both screen off and sleep to Never, for both battery and plugged-in profiles.
- Settings → Personalisation → Lock screen → Screen saver settings. Set to None and clear “On resume, display logon screen.”
- Settings → Accounts → Sign-in options. Set “If you've been away, when should Windows require you to sign in again?” to Never.
- Windows Update → Advanced options. Set active hours to cover Shabbat, and pause updates for the week. Windows restarting itself overnight is the most common way a Windows display dies.
- Kiosk mode. Launching the browser with the
--kiosk flag gives a genuinely full-screen page with no tabs, no address bar and no way to navigate away:
chrome.exe --kiosk https://shabbatscreen.com
Create a shortcut with that target and you have a one-click Shabbat display. Edge takes the same flag. Failing that, plain F11 gives full screen.
macOS
- System Settings → Lock Screen. Set “Turn display off when inactive” to Never, and “Require password after screen saver begins” to Never. Set “Start Screen Saver when inactive” to Never as well.
- System Settings → General → Software Update → Automatic Updates: turn off automatic installation.
- Do Not Disturb from Control Centre, scheduled across Shabbat.
- If you would rather not change system settings permanently, a single Terminal command holds the display awake until you close the window:
caffeinate -d
Then put Safari or Chrome into full screen with Ctrl + Cmd + F. On a laptop, remember that closing the lid sleeps the machine regardless — if you are driving an external monitor, keep it open or use clamshell mode with external power and peripherals attached.
Raspberry Pi and Linux kiosks
A Pi behind a monitor is the most reliable permanent installation, because you control everything. Disable the screen blanker and power management, then launch Chromium in kiosk mode:
xset s off -dpms
chromium-browser --kiosk --noerrdialogs --disable-infobars https://shabbatscreen.com
Put both lines in an autostart file so the display comes back by itself after a power cut — the one failure mode a Pi handles better than any tablet.
Screen burn-in
A dashboard is a static image for hours at a time, which is precisely the condition that causes burn-in on OLED panels: uneven ageing of the subpixels, leaving a faint permanent ghost of whatever sat there.
- LCD and IPS panels are effectively immune. They can show temporary image retention that fades within minutes to hours, but not permanent damage. For a screen you intend to leave running every week, an ordinary LCD tablet is the safer choice, and usually the cheaper one.
- On OLED, use the dark theme and lower the brightness. OLED pixels are individually lit, so dark pixels are genuinely off. A dark dashboard at moderate brightness ages the panel dramatically more slowly than a white one at full brightness.
- Do not leave an OLED phone running a bright dashboard every week for years. An old LCD tablet from a drawer is the better tool for the job.
The content on this screen helps a little on its own — a clock that changes every minute and a news panel that rotates through headlines means large parts of the display are not truly static.
Battery and heat
Any device driving a lit screen for twenty-five hours must stay plugged in. That raises two secondary issues.
Lithium batteries age faster when held at 100% charge, particularly when warm. Modern iPads and many Android tablets mitigate this automatically with optimised charging that holds at around 80%, and for a device that lives on a charger, that feature is worth leaving on. A dedicated wall tablet used this way every week will lose battery capacity faster than a normal one — a reasonable trade, and another argument for using an older spare device rather than your current one.
Heat is the second issue. A tablet in a thick case, running a bright screen continuously, gets warm, and heat is what actually degrades a battery. Take heavy cases off, leave the back unobstructed, and do not mount the device in a sealed enclosure or in direct sunlight.
Network
The display needs a working connection for the whole period, since every panel refreshes over the network.
- Turn off any Wi-Fi power saving or “sleep Wi-Fi when screen is off” option on the device.
- Check the router for a scheduled reboot or a nightly parental-controls window. Routers with a 4 am maintenance restart will take the display offline until you notice.
- If the tablet sits at the edge of your Wi-Fi range, move it or move the router. Marginal signal produces exactly the sort of intermittent failure that looks fine on Friday afternoon and is dead by Saturday morning.
- A guest network with a captive portal that expires after some hours is a poor choice; use the main network.
Do a dry run
Configure everything on a weeknight, start the display, and walk away for twelve hours. Whatever is going to fail will have failed by the morning, and you will still have days to fix it. Checking the countdown timer on the screen tells you immediately whether refreshes are still happening or whether the page died at some point in the night.
Then on Friday, run through a short checklist before candle lighting: device plugged in, screen timeout off, correct location loaded, panels showing what you want, refresh interval set, full screen on, and the countdown visibly ticking. Five minutes of checking beats twenty-five hours of a blank screen.
A note on refresh intervals
For an unattended screen, five or fifteen minutes is the right choice. One-minute refreshes cost bandwidth and heat without telling you anything new — forecast data does not update anything like that fast, and neither does a news feed. Fifteen minutes is the setting to pick if the device is older, warm, or on a weak connection.
Once the hardware side is sorted, the setup walkthrough covers the display's own options: choosing panels, picking news sources, units, theme and language.