In this ver. The back buttons don't work and the black colors are highlighted

Upgraded and runs well on ChromeOS via the Linux container.

After the update, i have the exact same issues i had back in June related to color and contrast accuracy, but now, is the Steam Link app the one with issues, and Steam Remote Play the one running fine:
https://steamcommunity.com/app/1675200/discussions/1/4340987530083793527/

Hope it gets fixed soon... again.
Thanks for the update, though.

Originally posted by Lord Bidón:

After the update, i have the exact same issues i had back in June related to color and contrast accuracy, but now, is the Steam Link app the one with issues, and Steam Remote Play the one running fine:
https://steamcommunity.com/app/1675200/discussions/1/4340987530083793527/

Can you provide Steam logs\streaming_log.txt from the remote computer after streaming to the Steam Link app?

Originally posted by slouken:

Can you provide Steam logs\streaming_log.txt from the remote computer after streaming to the Steam Link app?

https://drive.google.com/file/d/19WDPFVsGFYGswGEtEO01cTcXsW1tCbYk/view?usp=sharing

There it is. Sorry for the late response. Wasn't subscribed to the discussion lol.
I... also was a bit curious of what was in the log, and after noticing that it gives time and dates for... erm... things, i decided to run two tests in case it helps:

• The first one, with Hardware Decoding and HEVC enabled (and with contrast issues) at 31/10/2024 08:55 and left the streaming on for about 5 minutes.
  
• The second one with Hardware Decoding disabled (and no contrast issues) at 31/10/2024 09:05 and again, left it on for about 7 minutes.

Also, i have tried Hardware Decoding enabled and HEVC disabled, but there are no changes in the constrast issue.
Hope it helps.

Originally posted by Lord Bidón:

Originally posted by slouken:

Can you provide Steam logs\streaming_log.txt from the remote computer after streaming to the Steam Link app?

https://drive.google.com/file/d/19WDPFVsGFYGswGEtEO01cTcXsW1tCbYk/view?usp=sharing

There it is. Sorry for the late response. Wasn't subscribed to the discussion lol.
I... also was a bit curious of what was in the log, and after noticing that it gives time and dates for... erm... things, i decided to run two tests in case it helps:

• The first one, with Hardware Decoding and HEVC enabled (and with contrast issues) at 31/10/2024 08:55 and left the streaming on for about 5 minutes.
  
• The second one with Hardware Decoding disabled (and no contrast issues) at 31/10/2024 09:05 and again, left it on for about 7 minutes.

Also, i have tried Hardware Decoding enabled and HEVC disabled, but there are no changes in the constrast issue.
Hope it helps.

Interesting, it looks like you're running this on a Steam Deck. I'm guessing the default colorspace for hardware accelerated frames changed in a recent SteamOS update? I'm putting together a build that explicitly requests the colorspace we're streaming with, and I'll post info for you to test it.

Originally posted by Lord Bidón:

Also, i have tried Hardware Decoding enabled and HEVC disabled, but there are no changes in the constrast issue.
Hope it helps.

Can you try this one?

flatpak install --user https://dl.flathub.org/build-repo/142203/com.valvesoftware.SteamLink.flatpakref

Originally posted by slouken:

Can you try this one?

flatpak install --user https://dl.flathub.org/build-repo/142203/com.valvesoftware.SteamLink.flatpakref

I pasted that command into the terminal, and I assume it installed a new version, replacing the old one, instead of adding a second Steam Link app. So, this new test is with the only Steam Link app I found on the Steam Deck.

Unfortunately, I ran it again, and I'm sorry to say that using hardware decoding (both with HEVC enabled and disabled) still has contrast/brightness issues. With hardware decoding disabled, it works without any problems.
So, yeah, no changes at all on my end.

However, when I first noticed this issue, I used a random black image from Google as a background and asked some coworkers to check if there were indeed contrast/brightness issues between hardware decoding enabled and disabled (and to also confirm that I wasn't losing my sanity), and they confirmed that there were definitely differences in contrast between the decoding methods.

This time, though, using that same image, they said the issue is still present but is less noticeable than before. It might not be an empirical test, as I don't see any difference compared to before, but that's their feedback.

Also, in case it helps, here is a new log:
https://drive.google.com/file/d/1F8M1SaB0IDIMi6PHsxbPd9cPIJIz48vF/view?usp=sharing

I made some... "controlled" tests again using Hardware + HEVC, Hardware Enabled, and Hardware Disabled. In that order.
But... erm... i forgot to take note of the timestamps... so erm...

Hope this was helpful, somehow.

EDIT: I'm an idiot, and it seems that I also forgot to change from Hardware Enabled to disabled in the last test. Don't know if this tests are useful, but if you want, i can repeat them.