Your own music server, on your phone

StarSonic plays the music you already host yourself. Point it at your Subsonic, Navidrome or Airsonic server and it copies the catalogue onto the phone, so browsing your library does not wait on the network — and neither does the train tunnel.

No account of ours, no server of ours, nothing in the middle. Every byte comes from a machine you run.

What it does

• Your library, on the deviceArtists, albums, tracks and playlists are copied into a database on the phone and browsed from there. Scrolling your collection is instant, and it works with the server unreachable.
• More than one server at onceTwo servers are not two profiles to switch between: they coexist, every album knowing which one it came from. A NAS at home and a server somewhere else are one library.
• It syncs the way Android wants toServers are added as system accounts, and the library refreshes through Android's own sync mechanism — so it appears under Settings → Accounts, obeys the phone's sync and battery rules, and does not invent a scheduler of its own.
• The player where you expect itLock screen, notification, Bluetooth buttons, headset controls, and anything that browses media on Android — all of it works, because StarSonic is a media session and not a screen with a play button.
• ChromecastSend what you are listening to to a speaker or a TV, including music the phone has cached, which a Chromecast cannot normally reach.

How it works

Your server already speaks the Subsonic API — Navidrome and Airsonic both do — and that is all StarSonic needs. You give it the address, a username and a password; it authenticates the way the protocol prescribes, with a per-request token rather than the password itself, and pulls the catalogue in the background.

Music is streamed and cached as you listen, so what you have played recently stays with you. The player is a normal Android media session, which is why every surface that knows about music on your phone knows about StarSonic without StarSonic having to be open.

Honest about where it is

It works — the library, the sync, the player and the casting are all real — and it is in open testing on Google Play and on the F-Droid beta channel, but it still has gaps:

• It has been used against few servers beyond the author’s. Navidrome, Airsonic, Jellyfin and beets are tested against real servers; servers that only take an API key (LMS, Ampache, Nextcloud Music) are tested against a stand-in, not the real thing yet.
• Android Auto is new. Voice requests and search from the car are tested on a phone, the way the car talks to the app, but not yet in a car.
• The app is in English only. An Italian translation is still to come.
• Small things that say so on screen: the Library’s row menu has an “Info” entry that does nothing yet, and a download’s badge only updates when the list is reloaded.

That list is the roadmap, and it is public on purpose: this page says what the app does today and what it does not.

Privacy in one paragraph

StarSonic has no account, no telemetry and no server belonging to its author. Your credentials stay on the device, in Android’s own account system; your listening goes nowhere except to the server you configured. The full text is on the Privacy Policy page.

Get it

StarSonic is published in the same self-hosted F-Droid repository as the other apps here; use the F-Droid badge at the top of this page to add the repository to your client. It is also in open testing on Google Play.

• Changelog — what changed in each release
• Privacy Policy · Terms of Service