moonlight-stream / moonlight-stream/moonlight-android

[Issue]: High latency on Chromecast with Google TV (4K)

Open
#1,352 9 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
7.1k
Forks
1.5k
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

Horrible perceived latency when playing on Chromecast with Google TV (4K) (played at 1080p60).
The issue is not reflected in the performance stats.
Network latency is ~3ms and decoding latency is ~7ms but perceived latency is ~250ms.
No issue on an Android phone.
Decoder used is OMX.amlogic.hevc.decoder.awesome2.

Steps to reproduce

Start streaming the latest version of Moonlight on the latest firmware for Chromecast with Google TV (4K).
(GFE & Sunshine tested)

Affected games

Any

Other Moonlight clients

PC

Moonlight adjusted settings

No

Moonlight adjusted settings (please complete the following information)

Default settings.

Moonlight default settings

Yes

Gamepad-related connection issue

Yes

Gamepad-related input issue

Yes

Gamepad-related streaming issue

Yes

Android version

Android TV 12

Device model

Chromecast with Google TV (4K)

Server PC OS version

Windows 11 23H2

Server PC GeForce Experience version

3.27.0.120

Server PC Nvidia GPU driver version

551.86

Server PC antivirus and firewall software

Windows Defender and Windows Firewall

Screenshots

No response

Relevant log output

No response

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the latency on Chromecast with Google TV (4K) using the latest Moonlight version and firmware, then compare its performance stats and decoder behavior with an Android phone. Done means identifying and addressing the gap between reported and perceived latency, with validation on the affected device and streaming setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile-dev, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.