Jellyfin: The Free Software Media System

There's a couple things that stick out to me in these logs:

1. the androidtv client logs show the crash was due to a time-out while waiting for the server to respond to a request for over 3 seconds.

2. you included a DirectStream log, that's usually not too hard for even a Raspberry Pi to handle reasonably well

3. the first log I looked at showed libx264 was using 36 threads

So my guess is that, due to video encoding not scaling all that well across larger numbers of threads, your server is being bogged down with this transcoding and isn't providing http responses fast enough to your client device(s).

A simple way to troubleshoot this would be to explicitly set the transcoding thread count to something a bit lower than what your server has, say 16 or 20, and see if that does any better.

An obvious potential fix would be to use hardware acceleration if it's available to you. I run my Jellyfin server off of a little N100 mini PC and it can transcode 4K HDR 70 Mbps video (tonemapping included) at about 45 fps due to the hw acceleration. That said, I know it can be tricky to set up in a VM and you may not have the HW accel capability in your server CPU anyhow.