samba-documents-provider VS jellyfin-android

This all feels like it should be 800x less of an issue because phones & tablets should just be able to connect over SMB & you should use whatever media player you want on your device.

Telling your home router to forward 445 is not that hard. Usinf minupnpc or just building in auto-port forwarding would be better. Alas I've seen some isp's block users from connecting to 445, which seems insane (my ispets me host there, but my parents isp blocks me from dialing home?!). So I often forward on another port (ex: 4445) and then everything works fine.

The main problem why the obvious "just use computers" problems doesnt work is... Android. Phones. These incressingly user-hostile anti-general-purpose-computing systems. Some of my media players still work with the 2017 code drom of the Android Samba Provider, but it uses old Android APIs so many media players wont work with it. I have no idea if Android still makes filesystem providers possible at all, but we havent seen any, and this one old one-time-drop artifact remains the only example I know of it ever having beem done ever on Android. But then again I really have had no interest in Box/Azure Drives/whatever... it'd be interesting/great to know if anyone does remote drives on android today. It feels wild that we have so much bespoke special software for remote media serving... when we have seemingly so little that does the general job.

https://github.com/google/samba-documents-provider

Ideally upnp/dlna should also somehow be an option too, but it assumes secure private networks I think? I'd love if it could be exposed publicly but locked down but it does all use mdns. And Tailscale's the only company on the planet who seemingly has the sense to extend our homenet's reach quickly/easily.

Since Android 13 the Google Samba client https://github.com/google/samba-documents-provider won't load. It's by far the simplest and best client I've seen (free, ad-free, works with the OOB file explorer). But it's knackered, and you know, Google and their abandonware makes me think it'll never be fixed.

I'm not sure if we're talking about the same thing though, because as far as I recall, many client apps currently do not support the usual authentication protocols. Which authentication are you referring to? If you only use the WebUI client maybe this works.

Jellyfin - your media in your hands! (version 2.5.2): Mobile client for Jellyfin, the free software media system

Someone else mentioned this about 2.5.0.. they said it seemed fixed in 2.5.1, but you can go back to 2.4.x https://github.com/jellyfin/jellyfin-android.... Jellyfin Media Player is a windows/Linux client https://github.com/jellyfin/jellyfin-media-player

https://github.com/jellyfin/jellyfin-android/releases for people want the apk early

It's a bug in the web player on Android: https://github.com/jellyfin/jellyfin-android/issues/853