Here is the log file
Plexclient.log (688.0 KB)
It failed on all my UHD rips with Dolby Vision mkv files.
Since the problem only occurs on my Android 11 and 12 devices, I can’t even load downloaded APKs from previous versions.
Here is the log file
Plexclient.log (688.0 KB)
It failed on all my UHD rips with Dolby Vision mkv files.
Since the problem only occurs on my Android 11 and 12 devices, I can’t even load downloaded APKs from previous versions.
You can still side load APKs via adb, if you wish. Can I get a sample file too, please? Some strange stuff in your logs there
Will this feature come to other platforms, eg LG TV app ?
What feature? This is about fixing a regression that was introduced in 9.13 ![]()
Allow DoVi when direct streaming
It’s dependent on the device. Not all devices can play DoVi when direct streaming
Ah ok, anyway of finding out which ones support what? A support article?
I ran another test. It seems Chromecast With Google TV is working as long as I re-start the movie. So, it is just my RT-G2 Android TV 11 device that was broken. I will try adb method.
As for samples, all I have are full movie mkv files ripped from my UHD discs using MakeMKV. Nothing special. Some sample test files I downloaded from internet work fine though
Update: rolled back to earlier version 9.13.0 and everything works fine now.
Still waiting and hoping the update will be available soon in my Google Play store.
It’s weird, the release date of the current available version of Plex on Google Play has changed (from December 14 and now it is showing December 20), but the current version of the app never changed and remains the same: 9.13.0.37280
Still waiting for the 9.13.1.37459 to be available in my Google Play store.
I’ll patiently wait and hope it’ll be soon!
On version 9.13.1.37459 (39e89c99)
I’m having the same issue with Plex on the Shield Pro - [This may not be super helpful, but here I go] … Using an (enormous) file ripped from the Dolby Atmos 2014 demonstration Blu-ray, the track called “Horizon” (length 1:52), with the ripped name of “00002.m2ts” (I know) described by Plex in the attached image

…has the following results depending on which audio track (in the image) is selected:
Audio1-TrueHD7.1 - Sound plays correctly, but screen is blank, shows no image at all, just black screen.
Audio2-AC3 5.1, plays audio that says [essentially] “You’re using the wrong track, select Audio1 or Audio3”
Audio3 - plays correctly. But only using 5.1
Prior to installing the Shield, I was able to play Audio 1 perfectly and in 7.1 on my Roku Ultra-based Plex system. I believe it also played correctly in 7.1 on the Shield when I first installed it on an older version of Plex months ago.
Any feedback to this? Do I have to open a separate thread?
The update is finally here on my side.
Rushed to update my Plex and tested it out.
Dolby Vision is back.
I do NOT have “green and purple thumbnails” like ktm_91 reported.
It also fixed a video file (DV HDR) I had that would display hues of green and purple.
I haven’t tested for long, but at least Dolby Vision engages on my TV when the video files are DoVi.
Thanks!
Thanks for the update!
Question: Is your Plex version (shown on settings page) 9.13.1.37459?
Or something else?
Yes it is now showing 9.13.1.37459 in the settings page of the Plex App on Android TV.
Before the update, it was 9.13.0.37280.
Thanks - I’m seeing it working well for 5.1 audio but am still getting a blank screen for 7.1 DoAt/DoVi content. I’m hoping the Plex team will be able to fix that too, if possible…
Anyone tried skipping forward in DV content direct play on shield?
It starts to play after a while but with stuttering and broken audio makes it unwatchable this is still happening as i write this and after this update so im not sure if this was caused by this fix or a seperate issue at this point?
I dont have much DV content and most of the time watch a movie from the start but I happened to not finish one the other day and now I cant finish it without leaving it to play all the way through to where I was.
Pausing seems ok its just on skipp forward or resuming after its closed this occurs.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.