
Ever thought about contributing to Finamp or Open Source in general? Now is the time! It's Hacktober afterall!
There are a lot of things you can help with with regard to Finamp:
If you like Finamp but don't want to contribute for any reason, you can also contribute to Jellyfin directly or to upstream libraries which Finamp uses (just_audio, background_downloader, etc.).
That way you can help Finamp indirectly and Open Source as a whole!
Finamp can't exists without maintained and stable libraries :)
There's still a lot left over from our latest "Finamplify" Hackathon!
Take a look at the Finamplify Project Board or even the full Redesign Project Board (the latter is slightly outdated).
You can find an overview of (hopefully) easy to tackle issues here on GitHub. For some of those prior programming experience is definitely helpful.
Specifically, here a short list of long awaited features:
[!Important] Make sure to check out the
redesignbranch (git checkout redesign)! This is where all development happens at the moment!
Start by reading the "Setting up a Development Environment" section in our contribution guidelines.
Then, once flutter is working, you can simply do flutter run!
Any changes you do to the code can be applied via hot-reload by pressing r in the terminal. There are also first-party Flute integrations for many editors and IDEs.
If you have any questions, just reach out to us on GitHub or Discord!
We're currently in the process of redesigning Finamp to transform it into a modern, beautiful, and feature-rich music player made specifically for Jellyfin.
You can join the beta on Google Play and Apple TestFlight, or download the latest beta APK from the releases page.
Please note that the beta is still work-in-progress, so the UI and functionality might be inconsistent or incomplete, and is not final. However, the beta is fully functional and should be stable enough for daily use.
Finamp is a Jellyfin music player for Android and iOS. It's meant to give you a similar listening experience as traditional streaming services such as Spotify and Apple Music, but for the music that you already own. It's free, open-source software, just like Jellyfin itself.
Some of its features include:
You need your own Jellyfin server to use Finamp. If you don't have one yet, take a look at Jellyfin's website to learn more about it and how to set it up.
Note: The F-Droid release may take a day or two to get updates because F-Droid only builds once a day.
The app is also available as an APK from the releases page.
The SHA-256 fingerprint of Finamp's signing certificate is 20:61:C5:C9:28:9C:00:02:08:81:B7:E5:33:4D:93:A0:2D:FA:4B:E9:80:AF:20:C0:5D:B4:E5:29:C8:DA:5B:54. Google Play releases and provided APKs will be signed with this certificate. F-Droid releases will be signed with F-Droid's own signing certificates.
Absolutely! It costs nothing to use. We do appreciate voluntary contributions of any kind though, be that bug reports, code, designs, or ideas for new features. You can also donate to some of the developers to show your appreciation <3
On Android, Finamp can be installed from the Google Play Store, F-Droid store, or directly by installing the APK file from GitHub.
On iOS, you can install Finamp through Apple's App Store. Just click on the buttons above.
Finamp should support all formats supported by Jellyfin. Some more advanced formats could cause issues for regular playback, but transcoding should fix these issues.
Theoretically, but not yet. There is an issue for this that contains a proof of concept for Android Auto in there, but it hasn't been tested yet. Maybe you could help out!
Yes. Finamp is a tool that lets you interface with a Jellyfin server. Finamp does not come with any music, and will not connect to streaming services other than Jellyfin. You will need to bring your own media and add it to Jellyfin, for example by purchasing music online. This often also directly supports your favorite artists!
If you're experiencing software bugs or other issues with Finamp, be sure to take a look at Finamp's issue tracker, especially the pinned issues at the top of the page. If you can't find anything related to your specific problem, please create a new issue (you will need a GitHub account).
Finamp is a community-driven project and relies on people like you and their contributions. To learn how you could help out with making Finamp even better, take a look at our Contribution Guidelines
You can also contribute by helping to translate Finamp! This is done through our Weblate instance here: https://hosted.weblate.org/engage/finamp/. The current translation status is this:
This app is still a work in progress, and has some bugs/issues that haven't been fixed yet. Here is a list of currently known issues:
just_audio), and is being tracked here

Name source: https://www.reddit.com/r/jellyfin/comments/hjxshn/jellyamp_crossplatform_desktop_music_player/fwqs5i0/
1 activity
Also affected, and I can confirm the rebuilt 0.9.25 assets from flathub/com.unicornsonlsd.finamp#67 do not resolve it. A few data points that may help narrow it down.
Environment (differs from the reports above)
d7ea639 — i.e. the merge of flathub#67 (07a44ed) — Version 0.9.25-beta, build 126b8478e3), which ran for 15h uninterrupted immediately before the updateBoth existing reports are Ubuntu 24.04, so this isn't distro-specific.
Why flathub#67 was unlikely to fix this
That PR changes exactly two lines — the sha256 of the x64 and arm64 tarballs for the same 0.9.25-beta tag. The manifest, the runtime (org.freedesktop.Platform//25.08) and the module list are all untouched; it just re-points at re-uploaded release assets. So unless the re-upload was genuinely rebuilt with a different toolchain/plugin set, the same binary defect ships again — which is consistent with what @felix920506 observed on 07a44ed and what I see here.
For contrast, the equivalent June regression (#1655) was fixed by flathub#64, which was the same "re-roll the artifacts" move — that one worked because the artifacts actually changed. It may be worth verifying that the 0.9.25 re-upload produced a materially different binary rather than a repackage.
The abort point varies between runs
This is the part I haven't seen mentioned. It's SIGABRT (confirmed via coredumpctl), but finamp-logs.txt stops at a different place on each launch.
Run 1 reached:
[MusicPlayerBackgroundTask/INFO] Starting audio service
[MusicPlayerBackgroundTask/INFO] Initializing media-kit for Windows/Linux
[VolumeNormalization/INFO] non-Android base volume gain factor: 1.9952623149688795
[QueueService/FINE] Loop mode set to FinampLoopMode.none
[QueueService/INFO] Restored loop mode to FinampLoopMode.none from settings
Run 2, ~15s later, stopped earlier:
[PlayOnService/INFO] Attempting to start PlayOn listener
[Main()/INFO] Setup PlayOnService
Run 1 also emitted an unhandled SocketException on /var/run/dbus/system_bus_socket (battery_plus → UPowerClient → KeepScreenOnHelper, main.dart:167); run 2 aborted before reaching it. That D-Bus exception is a red herring — the sandbox has no --socket=system-bus, and it appears on working 0.9.24 too. But the process dying at a different point on each launch suggests the abort is triggered asynchronously during plugin initialisation rather than at one deterministic call site.
The assertion itself is the engine's bundled libc++ detecting that something in the process replaced operator new(size_t) without also providing operator new(size_t, nothrow_t). Since it consistently appears immediately after package:media_kit_libs_linux registered., the newly bundled media_kit/libmpv shared objects look like the first place to check.
Workaround for anyone landing here — pin to 0.9.24:
sudo flatpak update -y --commit=b8478e3beef29febc13f34f03139b55230ad50ec6f7d91f2984ba829c32b6a3d com.unicornsonlsd.finamp
flatpak mask --system com.unicornsonlsd.finamp
Remember to flatpak mask --system --remove com.unicornsonlsd.finamp once a fix lands.