samba-documents-provider VS bonob

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.

The github page has a short guide and step by steps for Synology. The last couple of posts on this thread may also be of help.

I just setup Navidrome and bonob (https://github.com/simojenki/bonob) on my Synology. Everything is working really well! I can access all the albums from Sonos app on Android. What I can’t figure out is how to “resume” different albums. Is bonob missing audiobook and bookmark integration?

I have not tried it as I do no have a Sonos speaker (yet), but it is on my list of things to try in the future. I have seen several posts about https://github.com/simojenki/bonob and integrating it with Gonic or Navidrome to stream music to Sonos speakers. Seems like ppl have had good success with it and like it.

Any Subsonic music server works well with this: https://github.com/simojenki/bonob

Dsub and substreamer can stream to Google cast devices. For Sonos, you might need a bridge like https://github.com/simojenki/bonob

Ya'll thanks everyone who commented. I finally found a setup that works very well for me. Navidrome + Bonob. Not too heavy, just works, blazing fast playback

Developer simojenki (https://github.com/simojenki/bonob) has developed something great. We can now finally link Navidrome with Sonos. This is something I, and probably many users, have wanted for a long time.