10-20-2025 08:17 AM - edited 10-24-2025 10:21 AM
For some reason, the Google TV Streamer doesn't fallback to HDR10 when playing bluray remuxes with the Dolby Vision profile 7 FEL and profile 7 MEL and it happens with any app for local media playback.
Some apps such as Plex, have an option to disable Dolby Vision profile 7 passthrough so videos fallback to HDR10 correctly but not all apps have an option to do the same so playback is not possible.
This is not a problem specific to an app but rather an absence in the code that should allow any local media playback app to fallback videos to HDR10 when they contain Dolby Vision profile 7 FEL and profile 7 MEL without the need to have an option to disable it.
If you need a log or anything please let me know.
10-23-2025 05:43 PM
Hi branches78,
Thank you for reaching out to our community.
I understand you are experiencing a limitation where your Google TV Streamer cannot play certain high-quality media files (Blu-ray remuxes using Dolby Vision Profile 7, specifically FEL and MEL). I am sorry that this technical incompatibility is preventing you from playing local media and forcing you to rely only on apps that have a workaround option.I'm glad to assist you with this concern.
To help me figure this out, please answer the following questions:
Additionally, please send your feedback through the Google Home app and using your Google TV screen. Check the instructions in these Google Nest Help Center articles: Submit feedback about your Chromecast, Chromecast with Google TV or Google TV Streamer device and Share feedback about Google Nest.
Best regards,
Virna
10-24-2025 10:29 AM - edited 10-24-2025 10:59 AM
Hello @virnab,
Please review the information you requested:
"What is the Google TV Streamer's firmware version?"
Current build is UTTK.250729.004 with security patch august 1st 2025, it's the latest firmware version that arrived a few days days ago.
"What is the make and model of your TV?"
LG 55QNED85A.
"Do you have another TV in your home? If so, is this also happening on the other TV?"
Yes, I have a 50 inches Hisense TV with Dolby Vision support where I also observe the same situation.
"Are you connecting the Google TV Streamer directly to the TV"
Yes, it is connected directly to the TV.
"When you mention playback is "not possible," what exactly happens? (e.g., Black screen, freezes immediately, displays wrong colors, or an error message)?"
Depending on the app, there are error messages or a black screen or a green screen or playback is slow because the video is being decoded by software and the Streamer doesn't keep up with the process.
a month ago - last edited a month ago
Hi branches78,
Thank you for your timely response and the comprehensive information you've provided.
Please share your feedback directly with our development team through the Google Home app and using your Google TV screen. Check the instructions in these Google Nest Help Center articles: Submit feedback about your Chromecast, Chromecast with Google TV or Google TV Streamer device and Share feedback about Google Nest. Your input will help us prioritize features and ensure that we're meeting the needs of our diverse user base.
Feel free to keep us posted if you have more questions.
Best regards,
Virna
a month ago
Hello @virnab
Are you going to forward the information I provided to Google?, otherwise I don't see the point of providing it if you're suggesting to send feedback by other means.
4 weeks ago
Hi branches78,
I appreciate you following up on this thread. Your input here is absolutely essential and not wasted.
The reason we also suggest sending feedback through the product's official process is that this method is the dedicated pipeline for Google's engineering and product teams to track, prioritize, and implement future fixes or changes. Both steps are important: your information helps us now, and the official feedback helps Google's broader product development.
We genuinely appreciate you taking the time to do both.
Best regards,
Virna
4 weeks ago
Ok, I will send feedback through the device.
Thank you @virnab.