[Issue]: Cant use native resolution or 90hz

[Steso871]

Describe the bug

When i choose my phones native resolution (1920x1200) moonlight gives me error 5 video decoder failed to initialize and says that my device cant use that resolution and same with 90 hz. If i choose 1080 and 60hz everything works. My sunshine server works perfectly with other devices and a big range of resolutions.

Steps to reproduce

changing to native 1920x1200 and choosing 90hz

Affected games

All

Other Moonlight clients

PC

Moonlight adjusted settings

No

Moonlight adjusted settings (please complete the following information)

none

Moonlight default settings

Yes

Gamepad-related connection issue

Yes

Gamepad-related input issue

Yes

Gamepad-related streaming issue

Yes

Android version

Android 14

Device model

Samsung tab a9+

Server PC OS version

Windows 11

Server PC GeForce Experience version

32.0.15.6590

Server PC Nvidia GPU driver version

566.03

Server PC antivirus and firewall software

Windows defender

Screenshots

No response

Relevant log output

No response

Additional context

I tried a custom rom lineage 21 and i got same error

[pfroo40]

I have this same issue on my Galaxy Tab A9+. I found an unofficial version of Moonlight which allows custom resolution and found that 1440x900 works fine, but not 1680x1050 or native 1920x1200.

[timharry]

I have this issue, though I don't get the same exact error.

On my Pixel 9 Pro, if I connect to my host PC (windows running Sunshine) using the 4K setting or the Native resolution settings, moonlight immediately disconnects from the session saying: "Host returned error: client stream limit has been reached". If i use 1440p, 1080p, 720p etc, the pixel 9 pro connects just fine. Its only when I use 4K or native that is fails to connect.

There is no way I have another client connected at the time though, because this occurs even when I try to connect using those resolution settings immediately after rebooting sunshine, so it is guaranteed to have no sessions connected. Furthermore, there is no issue when connecting with another android client (oneplus 6) using the 4K setting and native resolution settings.

Furthermore, I have tried adding the native resolutions used to the sunshine settings for advertised resolutions, and that didn't appear to help.

On the pixel 9 pro, the native resolutions that have issues are:

1. 4K
2. 2025x960
3. 2856x1280
4. 2142x960

All of these provide the same error, no matter what I try. All the other resolutions connect just fine to my host PC.

Furthermore, I had only been trying 60Hz connection. The lower resolutions don't work at 90Hz or 120Hz connection, just like the OP reported as well.

The oneplus 6 connected just fine at 4K, and its native resolutions. I didn't try anything other than 60Hz on the Oneplus client.

The sunshine log for connection doesn't show any issues, it just shows that as soon as the client connects it disconnects. Sunshine does not appear to be reporting any errors. Here is the sunshine log: sunshine log

I would try to capture moonlight logs to see whats going on, but it doesnt look like there are any ways to generate debug logs on moonlight android.

[timharry]

I noticed the comment on this pull request saying that their client's decoder didn't support the native resolution. Maybe the issue is that the decoders don't support these resolutions? Feels a bit strange for the new pixel 9 pro, but i guess i wouldn't be all that surprised.

[Steso871]

I noticed the comment on this pull request saying that their client's decoder didn't support the native resolution. Maybe the issue is that the decoders don't support these resolutions? Feels a bit strange for the new pixel 9 pro, but i guess i wouldn't be all that surprised.

In their conversation they mention a test version with that code, do you know where to find it?

Every other device I have supports their native resolution and Hz so it's really frustrating

[timharry]

I have no idea, though I did try to find it. Probably would have to find someone to compile a build with the pull request changes to give it a go.

Yeah it's pretty frustrating for sure. Seems like a really odd issue