findroid VS Exoplayer

I am not sure if I might be missing understanding you. If you just want a mobile client you should check out Findriod Will allow you to download episodes for offline viewing in the app itself, and keep track of it to mark it as played when you come online.

mobile apps - I use Findroid on my tablet instead of plex (which is use if I need to download, if transcode is necessary), because it gives me a better experience. Plex still sometimes refuses to autoplay the next episode after years of being reported, no more getting out of the bath to press next.

On your Android phone, you can try installing VLC or MX Player and in your Jellyfin Android settings allow the use of an external player. See if that fixes it. Or try Findroid. I don't have an Android phone so I don't actually know if any of this will work.

Findroid (version 19): client for the Jellyfin media server

Jarne Demeulemeester — developer of findroid (Android Jellyfin client)

Checkout the developer's github link https://github.com/jarnedemeulemeester/findroid

According to some people on the Internet [0][1], it is. Apparently, Java's (Android's?) Locale.getLanguage() is broken for Russian locale and instead of returning "ru" as the docs promise [2], it returns "русский".

[0] https://stackoverflow.com/questions/46916210/cannot-get-writ...

[1] https://github.com/google/ExoPlayer/issues/8251

[2] https://docs.oracle.com/javase/8/docs/api/java/util/Locale.h...

I tried using the Fire TV but it has huge problems with some 4K HDR video formats that goes black screen. It is an issue reported by multiple users for Plex but it's the same for all applications on FireTV. This is the issue on github for Exoplayer: https://github.com/google/ExoPlayer/issues/11096

Media3 is the new home for APIs that enable you to create rich audio and video experiences. If you’ve used libraries like ExoPlayer, MediaCompat, or Media2, you’ll find Media3 to be familiar. However, instead of using these separate libraries, Media3 provides a unified API for playback use-cases and also expands to cover new use-cases like video editing and transcoding. The APIs are simple to use yet powerful, customizable to meet your needs, and reliable and optimized so you can build for the diverse Android device ecosystem. (https://android-developers.googleblog.com/2023/03/media3-is-ready-to-play.html)

Haven't done video work in years, but checkout the DefaultTrackSelector and start following around in the source code. Android Studio should allow you to do this all in the IDE. It's really the only way to learn/understand this stuff.

Also in regards to having to tell PC rtspt:// and Quest rtsp:// and waiting for ExoPlayer to fail over to TCP (8 seconds delay) https://github.com/google/ExoPlayer/issues/11069

I wonder if it's an ExoPlayer bug?

See the full changelog of ExoPlayer 2.18.2. Some notable changes are:

This started happening on Android when they enabled DRM on the streams. Assuming you use a device with Android 12 or later, you can just use Race Control TV to fix the issue. With Android 11 or earlier, Race Control TV also stutters due to this issue, which can be fixed by a custom build of the the app and force-enabling the fix mentioned in the issue.