The phone does not always mirror its screen. It discovers a Chromecast receiver, sends a playback request, then the receiver normally accesses the media itself. An address only reachable by the phone, an unsupported codec or Wi-Fi isolation can therefore break casting while local playback still works.
Key points
- Phone and Chromecast normally need the same local network.
- The receiver must be able to access the media address itself.
- Successful local playback does not guarantee Chromecast compatibility.
- VPNs, guest networks and client isolation often block discovery.
The path of a cast session
The sender app discovers Chromecast over the local network. Once selected, it sends the receiver the playback information and becomes a remote control. Chromecast usually downloads the media directly.
That is why locking the phone does not necessarily stop playback, and why an address only visible from the phone may fail on the receiver.
Troubleshoot by symptom
| Symptom | Likely cause | Test |
|---|---|---|
| No device found | Different Wi-Fi, guest network, isolation or local permission | Same SSID, local-network permission and restart |
| Connects then returns | Cast session or receiver app state | Close other senders and restart Chromecast |
| Black screen, local playback works | Codec, container, headers or receiver cannot reach URL | Test a simple authorised media profile |
| Regular buffering | Unstable Wi-Fi or insufficient throughput | Move closer or use 5 GHz/Ethernet |
| Playback expires | Temporary link not renewed | Restart from the app and report the exact duration |
Checks in the right order
- Update the phone, receiver and DringTV.
- Use the same non-guest network.
- Temporarily disable VPN and filtering to isolate discovery.
- Grant the operating system’s local-network permission.
- Start with an authorised media item using a common resolution and codec.
- Compare a second item from the same source to separate global and item-specific failures.
Compatibility and transcoding
Chromecast supports a defined set of containers, codecs and profiles. A media item may play through a decoder on the phone but not on the receiver. Conversion would then be required; DringTV does not create a transcoding server between both devices.
A useful report includes the exact Chromecast model, resolution, displayed codec and failure point — never the private URL.
Privacy
- Never paste a private media URL into a public test tool.
- Avoid casting to an unknown or shared receiver.
- End the session from DringTV when finished.
- Check the room name before sending playback.
Common questions
Why does it play on my phone but not Chromecast?
Chromecast normally retrieves and decodes the media itself. It may not reach the address or support the same codec as the phone.
Does a VPN always block Chromecast?
No, but some VPNs isolate local traffic. Temporarily disabling it is a useful diagnostic.
Technical references
DringTV is a media player only. It does not provide, sell or recommend any channel, playlist, portal or content. Only use sources you are authorised to access, and follow your source owner’s rules and the law in your country.