Repository navigation
Lull 1.9
Share, and an API that can drive the whole app.
Share button
Send the playing track from the Now Playing top bar, or a whole selection from the library's contextual bar — long-press a track, an album, a folder.
The file itself travels, with its metadata alongside. Title, artist, album, genre, duration, size and your own rating go into the share text, because a content:// uri carries none of that and what arrives at the other end is otherwise a filename. Nothing is re-encoded and no tag is rewritten: the file that leaves is byte-for-byte the file on disk.
A local API
Turn it on under Local API in the overflow menu. Lull generates a key; a script or agent holding it can do what you can — browse the library, play, queue, seek, skip, set repeat and shuffle (including Favourites), rate, build and reorder playlists, change settings, arm the sleep timer, set an A–B region, and share.
KEY=<copied from the app> # adb forward tcp:8787 tcp:8787, from a laptop
curl -s -H "X-API-Key: $KEY" 127.0.0.1:8787/api/docs
curl -s -H "X-API-Key: $KEY" -X POST 127.0.0.1:8787/api/player/play -d '{"group":"album:42"}'
curl -s -H "X-API-Key: $KEY" 127.0.0.1:8787/api/tracks/42/file -OJ # the whole track- Off until you switch it on, bound to
127.0.0.1unless you also turn on LAN access. The key is generated, never typed, compared in constant time, and can be reissued at any moment. - Its own foreground service, separate from playback — because "start playing something" is the request an agent most wants to make, and that is exactly when the playback service does not exist. The notification names the address, and carries a Stop.
POST /api/sharepops the real chooser and says whether anyone can see it: Android discards a dialog thrown by an app that is not on screen, so the share text and the file urls come back either way.
The honest note
This version adds INTERNET to the manifest, because a listening socket needs it even to bind loopback. Lull still makes no outbound connection of any kind and has no analytics, ads or telemetry — but the README no longer claims "no network access".
Internals
Routing, auth, request parsing and every error shape are Android-free behind an ApiBackend interface and tested against a fake: 5 tests to 83, including one that walks the route list /api/docs advertises and fails if any of it is unrouted.