Methodology

How we test Zee Cast

Every guide on this site carries a "Tested on" block. This page is the detail behind it: what we run the server on, what we play it back on, how the network is set up, and how often we re-check.

The short version

Zee Cast Settings screen showing Display Name, Display Icon, Auto Start, Port 8080 and Require Device Approval under Advanced Settings
Advanced settings — Display Name, Port, Auto Start and Device Approval — are the surfaces we change when testing network and discovery scenarios.
  1. 1Port 8080 is the HTTP server port we verify the TV connects to.
  2. 2Device Approval is switched on to test the allow/deny gate during a browse request.

Phones we run the server on

DevicePlatformWhy it is in the matrix
iPhone 16 ProiOS 26Current iOS reference; HEIC→JPEG, Dolby Vision Profile 8.4 capture, hotspot mode
Samsung Galaxy S24Android 15Current Android reference; HEVC/HDR10+ capture, foreground-service backgrounding
iPhone SE (2nd gen)iOS 18Older-device regression check for the background runtime
Pixel 6aAndroid 14Non-Samsung Android discovery and codec check

Renderers we play back on

Device familyTested versionPlayer used
Samsung Smart TVTizen (2018–2025 models)Native Smart Hub media player
LG Smart TVwebOS 4.0–24Native Photo & Video / SmartShare
RokuRoku OS 11+Roku Media Player channel
Amazon Fire TVFire OS 7+VLC for Fire TV / Nova Video Player
Android TV / Google TVAndroid 9+VLC, Kodi, native Files
Apple TVtvOS 16+Infuse
PlayStation 5 / PS4System software 22+Media Player
Xbox Series X|S / OneSystem software 22+Media Player
DesktopWindows / macOS / LinuxVLC, Kodi

Networks we test on

SetupWhat it is for
Home Wi-Fi — 5 GHz bandPrimary reference: one router, phone and renderer on the same SSID
Home Wi-Fi — 2.4 GHz bandRegression check for 4K stutter and discovery
Wi-Fi 6 / 6E routerThroughput headroom tests for high-bitrate 4K 60fps
iPhone Personal HotspotNo-router and travel scenarios — TV joins the phone's hotspot
Wired Ethernet TVBaseline where the renderer supports it

How a guide gets verified

  1. 1

    Reproduce on real hardware

    We follow the guide's own steps on the devices above — no emulator-only claims.

  2. 2

    Confirm the original bitstream

    We check that playback is Direct Play — the TV reports the original resolution, frame rate and HDR metadata — not a re-encode.

  3. 3

    Check background behaviour

    We lock the phone, switch apps and take a call mid-playback to confirm the stream is unaffected.

  4. 4

    Cite primary sources

    Protocol, codec and OS claims link to the primary spec (IETF, OCF, vendor developer docs), not to another blog.

What we cannot test — and say so

Honest limits

  • SSDP multicast does not work in the iOS Simulator or most Android emulators. Discovery claims are verified on physical hardware only.
  • No HEVC → H.264 transcoding. iOS converts HEIC photos to JPEG; Android serves originals. We do not claim otherwise.
  • No UPnP event subscriptions (SUBSCRIBE/NOTIFY) and no CDS Search.
  • The HTTP port must be free at startup. There is no automatic fallback port.

Update cadence

Guides are re-verified when a TV platform ships a behaviour change, when Zee Cast ships a feature that a guide references, or when a reader reports a factual error. Each article shows aLast reviewed date in its byline and author box; material corrections are listed in that article's changelog.

Tell us we are wrong

If a step does not work on your TV, tell us the model, firmware, and what you saw. Emailsupport@eslamx.com and we will try to reproduce it and update the guide.