You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TV: LG OLED55CX6LA, firmware 04.50.90, webOS 5.5.0 (rooted, Homebrew Channel)
PlxNative: 0.9.0 and 0.10.0-nightly-20261030, same result
Playing an episode from the start works.
Resuming an episode, seeking manually or pressing Skip Intro leaves the
player on "Buffering…" forever.
Log attached (0.9.0, resume at 12:17, Direct Play): the TV accepts the first
frames, Play is called, then the position stays at 737s for over a minute
with no retry or reload.
The log shows the TV accepting Play and then going silent, with no error from either side, so I need a bit more to see why.
Could you try these on 0.10.0-nightly-20261030?
While it's stuck on Buffering, press …, turn on Stats for nerds, close the menu and take a photo of the screen. The Feed and Frames rows are the ones I need.
While it's stuck, is the picture black, or is there a frozen frame behind the spinner?
Does a resume hang on a plain 1080p H.264 file with no Dolby Vision or Atmos?
Please attach two separate logs, one from a hung resume and one from a hung Skip Intro. They take different paths in the player.
Is the sound going through the TV speakers or to a soundbar/receiver (ARC/eARC)?
Hi! I do not have a webOS 5 set to reproduce this, so I only read the attached log as data. In case it saves you some digging, here is what it shows (nothing here is a diagnosis):
TV: webOS 5.5 (o20). Direct play of an H.265 file with Dolby Vision P8 and E-AC3 Atmos, resume at 737 s.
The Load succeeds (275 ms). The demuxer seeks to 737 s, rebases the first keyframe to PTS 0 (pts_shift=-736945000000) and feeds 4 video and 4 audio packets, all reply=O. Then: primed: v=833ms a=1007ms runway=0ms -> Play.
feed v# is only logged for the first 4 packets and then every 100th; there is no feed v#100, so fewer than 100 video packets were accepted.
So the TV takes the Play and then never presents a frame. What this does not tell is why. The comparison that would narrow it is the one you already asked for: the same file from the start (reportedly fine) against the resume, and a resume of a file without Dolby Vision/Atmos. In those logs the three things to compare are sink: displayed, pos= in the loop lines, and whether feed v#100 shows up.
Thanks again. Two more things that would narrow this down a lot, on top of the questions above (the Stats for nerds photo and the plain 1080p H.264 resume are still the most useful):
Only if you're happy to update: the nightly dated 20261101 or later has a new Dolby Vision switch (Settings > Video & playback > Dolby Vision, the last row). Set it to Off and resume the same episode. Does it still hang on Buffering? It isn't in 0.9.0 or older nightlies, so skip this one if you'd rather not update.
Did resuming this episode, or any other, ever work on this TV? If you still have the 0.8.0 package, one resume of the same episode on it would tell us whether this is a regression.
@aunterei Thanks for the detailed tests. The same episode resuming with Dolby Vision off narrows this down considerably. We’ve also traced the relevant firmware paths, but haven’t established the cause yet.
Could you share a short sample you’re able to share that still reproduces the hang with Dolby Vision enabled, along with the exact resume/seek timestamp within that sample? Please keep the original video and Dolby Vision metadata without re-encoding, and confirm the sample itself still hangs—cutting or remuxing can change the behavior. A sample reproducing either resume or seeking is useful; it doesn’t need to reproduce both.
We’ll prepare a diagnostic build before asking you for another log, so you won’t need to configure firmware tracing manually. For now, Dolby Vision Off remains the confirmed workaround for this file.
@aunterei The next nightly containing PR #1210 will include optional firmware playback logging. Could you try it once that nightly is available? The existing 20261102 build predates this change. Nightly update instructions.
We're still investigating the Dolby Vision hang. The new recording should show what the firmware does after resume or Skip Intro:
Keep Dolby Vision enabled. Just before reproducing the problem, open Settings → Diagnostics → Record playback diagnostics.
Reproduce one hung resume, return to Settings, and select Save diagnostic log.
Copy /tmp/com.beb.plxnative.nightly/plxnative-playback.log from the TV using your usual rooted-TV file access, and attach it here as the resume log.
Repeat with a fresh recording for Skip Intro and copy that log separately. Saving again replaces the previous combined log, so copy the first one before saving the second.
Recording is off by default and stops automatically after 60 seconds or 8 MiB; start it immediately before the test. Detailed logging can slow playback. The files stay local until you copy them; please review media/device details before posting. Dolby Vision Off remains the working workaround in the meantime. Copy the logs before powering the TV off.
Hi! I waited for the 0.10.0-nightly-20261103 build with the new diagnostics, then
ran the tests with Dolby Vision on.
What I did:
Resume of the episode: hangs.
Played the episode from the start, then a manual seek forward: hangs.
(I used a manual seek instead of Skip Intro because the intro starts around
6 minutes in, too late for the 60 s recording.)
"Save diagnostic log" didn't create plxnative-playback.log, so I copied the files
from the app folder instead. Attached zip:
resume-firmware-trace.log: the resume test
seek-firmware-trace.log: the seek test
events.log and stderr.log: the app logs for both tests
I can't send a clip of the episode, it's a commercial series. I tried a few public
Dolby Vision samples, but none of them reproduced the hang.
Reopening: that PR only added diagnostics and closed this by mistake. Your traces show where it stops (the Dolby Vision random-access check after a resume or seek), but there's no fix yet. Dolby Vision Off is still the workaround.
Thanks for the traces, they pinned it down. On your firmware (webOS 5.5.0-19) the Dolby Vision part of the pipeline only starts showing pictures from one kind of keyframe (an IDR). Your film has only one of those, at 0:00. Every resume or seek lands on a different kind (CRA), so it waits forever. That's also why it works with Dolby Vision off.
The fix is in #1263: when a resume or seek lands on such a keyframe, the app reloads once without Dolby Vision and plays the HDR10 version instead. So after a seek that film will play in HDR10 rather than Dolby Vision. A fresh start from the beginning still uses Dolby Vision.
It'll be in the next release. Could you try the same film there (resume, and a seek or two) and tell us if it plays? If it still hangs, a new trace would help.
@aunterei thanks for testing each case. That's exactly what the fix should do: Dolby Vision from the start, HDR10 after a resume or seek on that film, and no more hang.
This is an automated reply: Claude Code, an AI assistant, wrote it on the maintainer's behalf.
Activity
GLinnik21 commentedon Oct 30, 2026
Thanks for logs!
GLinnik21 commentedon Oct 30, 2026
The log shows the TV accepting Play and then going silent, with no error from either side, so I need a bit more to see why.
Could you try these on 0.10.0-nightly-20261030?
…, turn on Stats for nerds, close the menu and take a photo of the screen. The Feed and Frames rows are the ones I need.Bardioc1977 commentedon Oct 31, 2026
Hi! I do not have a webOS 5 set to reproduce this, so I only read the attached log as data. In case it saves you some digging, here is what it shows (nothing here is a diagnosis):
o20). Direct play of an H.265 file with Dolby Vision P8 and E-AC3 Atmos, resume at 737 s.pts_shift=-736945000000) and feeds 4 video and 4 audio packets, allreply=O. Then:primed: v=833ms a=1007ms runway=0ms -> Play.sink: displayed(type 49) and nopos=in any of the 106looplines of the player (a working play, e.g. the 0.8.0 log in [webOS 9.2.2/OLED55B2] regression: direct play of basic H264 no longer functional with 0.9.0, 0.10.0 nightlies #1096, has both). The UI keeps running at 60 fps and the app keeps reportingtimeline playing t=737s.feed v#is only logged for the first 4 packets and then every 100th; there is nofeed v#100, so fewer than 100 video packets were accepted.So the TV takes the Play and then never presents a frame. What this does not tell is why. The comparison that would narrow it is the one you already asked for: the same file from the start (reportedly fine) against the resume, and a resume of a file without Dolby Vision/Atmos. In those logs the three things to compare are
sink: displayed,pos=in thelooplines, and whetherfeed v#100shows up.GLinnik21 commentedon Nov 1, 2026
Thanks again. Two more things that would narrow this down a lot, on top of the questions above (the Stats for nerds photo and the plain 1080p H.264 resume are still the most useful):
aunterei commentedon Nov 2, 2026
First of all thank you guys for all the work, the app is incredible 🙏🏻
I did a couple of test with the latest nightly (0.10.0-nightly-20261102)
black screen, spinner next to the seek bar time.
works, and manual seeks forward/back work too.
When Dolby Vision switch set to Off, resume of the same episode: works.
Same file, still E-AC3 Atmos, so the hang only happens with Dolby Vision on.
Hanging file: 2160p HEVC Main 10, Dolby Vision Profile 8.1 (BL compat ID 1,
level 6, RPU present) + HDR10+, E-AC3 Atmos 5.1, MKV.
Resume has never worked for me, but I only started using PlxNative with 0.9.0,
so I can't tell whether it worked in earlier versions.
Test A - log-resume.txt
Test B - log-skip-intro.txt
GLinnik21 commentedon Nov 2, 2026
@aunterei Thanks for the detailed tests. The same episode resuming with Dolby Vision off narrows this down considerably. We’ve also traced the relevant firmware paths, but haven’t established the cause yet.
Could you share a short sample you’re able to share that still reproduces the hang with Dolby Vision enabled, along with the exact resume/seek timestamp within that sample? Please keep the original video and Dolby Vision metadata without re-encoding, and confirm the sample itself still hangs—cutting or remuxing can change the behavior. A sample reproducing either resume or seeking is useful; it doesn’t need to reproduce both.
We’ll prepare a diagnostic build before asking you for another log, so you won’t need to configure firmware tracing manually. For now, Dolby Vision Off remains the confirmed workaround for this file.
Add opt-in firmware playback diagnostics (#1210)
GLinnik21 commentedon Nov 2, 2026
@aunterei The next nightly containing PR #1210 will include optional firmware playback logging. Could you try it once that nightly is available? The existing 20261102 build predates this change. Nightly update instructions.
We're still investigating the Dolby Vision hang. The new recording should show what the firmware does after resume or Skip Intro:
/tmp/com.beb.plxnative.nightly/plxnative-playback.logfrom the TV using your usual rooted-TV file access, and attach it here as the resume log.Recording is off by default and stops automatically after 60 seconds or 8 MiB; start it immediately before the test. Detailed logging can slow playback. The files stay local until you copy them; please review media/device details before posting. Dolby Vision Off remains the working workaround in the meantime. Copy the logs before powering the TV off.
aunterei commentedon Nov 3, 2026
Hi! I waited for the 0.10.0-nightly-20261103 build with the new diagnostics, then
ran the tests with Dolby Vision on.
What I did:
(I used a manual seek instead of Skip Intro because the intro starts around
6 minutes in, too late for the 60 s recording.)
"Save diagnostic log" didn't create plxnative-playback.log, so I copied the files
from the app folder instead. Attached zip:
I can't send a clip of the episode, it's a commercial series. I tried a few public
Dolby Vision samples, but none of them reproduced the hang.
plxnative-issue-logs.zip
Report diagnostic export failures and add DV CRA/IDR controls (#1223)
GLinnik21 commentedon Nov 6, 2026
Reopening: that PR only added diagnostics and closed this by mistake. Your traces show where it stops (the Dolby Vision random-access check after a resume or seek), but there's no fix yet. Dolby Vision Off is still the workaround.
Playback: the LG C1's webOS 6.5.3 splitter takes only an IDR first too
Playback: the C1 nativeaudiowide test compares the Opus ceiling, not …
GLinnik21 commentedon Nov 6, 2026
Thanks for the traces, they pinned it down. On your firmware (webOS 5.5.0-19) the Dolby Vision part of the pipeline only starts showing pictures from one kind of keyframe (an IDR). Your film has only one of those, at 0:00. Every resume or seek lands on a different kind (CRA), so it waits forever. That's also why it works with Dolby Vision off.
The fix is in #1263: when a resume or seek lands on such a keyframe, the app reloads once without Dolby Vision and plays the HDR10 version instead. So after a seek that film will play in HDR10 rather than Dolby Vision. A fresh start from the beginning still uses Dolby Vision.
It'll be in the next release. Could you try the same film there (resume, and a seek or two) and tell us if it plays? If it still hangs, a new trace would help.
Playback: a Dolby Vision resume or seek that lands on a CRA plays the…
Merge #1263 (Dolby Vision CRA landing, #1166) into lane/merge-1263
aunterei commentedon Nov 8, 2026
Not at my place rn, will test the new nightly when I get home on Thursday.
Thanks for the work and investigation!
aunterei commentedon Nov 12, 2026
Tested on 0.10.0-nightly-20261112 with Dolby Vision on, same episode:
No more hang on Buffering. Thanks a lot for the fix!
GLinnik21 commentedon Nov 14, 2026
@aunterei thanks for testing each case. That's exactly what the fix should do: Dolby Vision from the start, HDR10 after a resume or seek on that film, and no more hang.
This is an automated reply: Claude Code, an AI assistant, wrote it on the maintainer's behalf.