2023-10-07, 01:53 AM
(This post was last modified: 2023-10-07, 01:53 AM by TheDreadPirate. Edited 1 time in total.)
This is a client side problem and we have little or no information to work with. Even if we have more information, it could very well be that its a bug that requires a code change.
We could install the debug version of the Jellyfin Android TV app and that would produce a stack trace that a developer could work with. But, because of the nature of open source, who knows when it would actually get worked on.
IMO, and in a lot of other people's opinion, smart TVs are not ideal because of how rapidly Android changes vs how rarely TV makers updates their TVs vs how rarely most of us buy new TVs. Then you have the issue of codec support being static and new codecs coming around, etc.
Hence my suggestion to get a cheap dongle. You get the equivalent experience as the built in smart TV capabilities and can update it cheaply when needed.
We could install the debug version of the Jellyfin Android TV app and that would produce a stack trace that a developer could work with. But, because of the nature of open source, who knows when it would actually get worked on.
IMO, and in a lot of other people's opinion, smart TVs are not ideal because of how rapidly Android changes vs how rarely TV makers updates their TVs vs how rarely most of us buy new TVs. Then you have the issue of codec support being static and new codecs coming around, etc.
Hence my suggestion to get a cheap dongle. You get the equivalent experience as the built in smart TV capabilities and can update it cheaply when needed.