After the newest WebOS update the app freezes and gets stuck.

[Mertcenk95]

YTAF Version

0.4.1

webOS Version

WebOS25 / 10.2.0 - 42

Firmware Version

33.21.85

OTAID

No response

SoC

No response

Model

LG OLED G4

Description

After the newest WebOS update the app freezes and gets stuck until closed manually.

Priority

Barely noticeable, but still not nice.

[cr1cr1]

related to closed (why?) #342

[cocorenting]

Hello, the issue seems a bit deeper than an orange line state where the screen is frozen, because the video player also have a weird behaviour.

In fact when quickly playing a video before the orange line appear on the menu and freezes the screen, I see that there is another player on top of the YouTube player. This player is very basic and seems similar to the player that appears when I cast music without the Spotify app.

I think the orange line corresponds to some webos “cast” mode. I also see that the "Watch on TV" feature of my youtube mobile app does also not work anymore.

[cr1cr1]

Hmm I have also noticed, that when killing the app (long press Back button), a notification message "Google Cast has been disconnected", after this the app responds for a few seconds. Not sure if related, but would make sense to appear non responsive (though pressing the green button for options works) because it simply has something else layered on top of it.

[gladiac]

Same here on an LG OLED G4 with the latest 33.21.85 release.

[Tom-hwi]

Same thing for me. Will there be an update soon?

[symmetry3000-sys]

Same exact thing for me, tried unistall, reinstall. Same issue. Normal YT works though.

[softestbuns]

As cocorenting said, this is a problem with both the "orange line" leading to the whole app freezing, plus the extra media player on top of the YouTube player.
Tested with both v0.3.8 and 0.4.1 - same issue on both versions.

[sbalogh]

I'm experiencing the same problem with the latest 33.21.85 release on an LG OLED C4.

[Tiki313]

Hi, I have the same issue. Normal YT works. G4 with the latest 33.21.85.

[reisxd]

Just to say, writing "Same here" does not help the maintainers and is spammy. Adding an emoji to the issue does the same.

[RodolfoBoccia]

Same issue for me.
The other player on top of the YouTube one looks like Google Cast.

I checked the active processes from the webOS Dev Manager terminal and found this:

5261 4806 2011 0 10:37 ? 00:00:06 /media/system/apps/usr/palm/services/com.webos.chromecast.cell/com.webos.chromecast.cell
5261 5012 2011 0 10:37 ? 00:00:00 /media/system/apps/usr/palm/services/com.webos.chromecast.log/com.webos.chromecast.log
5261 6210 4806 11 11:06 ? 00:00:01 /media/system/apps/usr/palm/services/com.webos.chromecast.core/com.webos.chromecast.core --oem_cast_config=/media/system/apps/usr/palm/services/com.webos.chromecast.core/conf/chromecast_core.conf --https-listen-fd=28 --http-listen-fd=29 --cast-control-unix-socket-path=/tmp/cast-core-cast-control --castv2-unix-socket-path=/tmp/cast-core-castv2 --enable-multizone=false --disable-mdns

On another LG TV I own (different webOS release), these processes are completely absent, and the app works fine.

Also, I noticed that chromecast.core starts exactly when I open the app, which makes me think the system might be trying to handle the video playback through this new “cast player” instead of the app’s player.

Of course, these are just speculations, but it seems likely that this change in the video pipeline could be related to the freeze issue.

[Mertcenk95]

Same issue for me. The other player on top of the YouTube one looks like Google Cast.

I checked the active processes from the webOS Dev Manager terminal and found this:

5261 4806 2011 0 10:37 ? 00:00:06 /media/system/apps/usr/palm/services/com.webos.chromecast.cell/com.webos.chromecast.cell 5261 5012 2011 0 10:37 ? 00:00:00 /media/system/apps/usr/palm/services/com.webos.chromecast.log/com.webos.chromecast.log 5261 6210 4806 11 11:06 ? 00:00:01 /media/system/apps/usr/palm/services/com.webos.chromecast.core/com.webos.chromecast.core --oem_cast_config=/media/system/apps/usr/palm/services/com.webos.chromecast.core/conf/chromecast_core.conf --https-listen-fd=28 --http-listen-fd=29 --cast-control-unix-socket-path=/tmp/cast-core-cast-control --castv2-unix-socket-path=/tmp/cast-core-castv2 --enable-multizone=false --disable-mdns

On another LG TV I own (different webOS release), these processes are completely absent, and the app works fine.

Also, I noticed that chromecast.core starts exactly when I open the app, which makes me think the system might be trying to handle the video playback through this new “cast player” instead of the app’s player.

Of course, these are just speculations, but it seems likely that this change in the video pipeline could be related to the freeze issue.

interestingly when I manually disconnected the WiFi from the TV, I got the notification that the Chromecast cast ended, even though I wasn't using it. There is something broken with the new Chromecast app / process, and I think as well that the issue of our problems lies exactly here.

You may be right that the app is exactly freezing because it thinks it's a Chromecast and this would explain the picture above with the two media players.