Salt Player: what the SaltPlayerSource repository actually ships

A release repository, not the player's source code

The first thing to get straight is what Moriafly/SaltPlayerSource is. The README states plainly that the repository "is used for releasing new versions, collecting feedback, and posting announcements." The player itself is a closed application; the top-level entries are .github/, LICENSE, README files in four languages, android/, articles/, privacy_policy/, src/ and windows/. There is no application source tree here to clone and build. The src/ directory holds images referenced by the README, such as the header banner and the SPW screenshot.

That matters for anyone arriving from a search for an open-source Android music player. The repository is MIT licensed, but the licence covers the repository contents, not a codebase for the app. If your reason for choosing a player is that you can audit or fork it, this project does not offer that, and the README does not claim otherwise. What it offers is a stable, documented distribution channel and a public issue tracker. Salt UI and Media Kit, listed under Open Source Related, are separate repositories that the project points to for Compose Multiplatform UI components and Android media service handling.

What problem Salt Player solves, and for whom

Salt Player is a local music playback app for Android. It is aimed at people who keep their own audio files rather than streaming, and who want the player to cooperate with the phone's system-level music surfaces: lock screen controls, car projections, status bar lyrics, widgets and cover screens. The README's system adaptation table is the clearest statement of that intent. Xiaomi MIUI/Hyper OS gets Mi Magic Broadcast, CarWith, cover screen display on devices such as Mix Flip, with the MIUI/Hyper OS widget still marked as follow-up. OPPO ColorOS gets Fluid Cloud. Meizu Flyme gets status bar lyrics and Dynamic Ring. vivo OriginOS gets Joviincar Smart Car and a manual Hi-Fi enablement path.

The audience is therefore narrower than "anyone who plays music on a phone." If you never touch an OEM-specific feature, you are paying for a set of integrations you will not use. If you do use a Xiaomi car projection or a vivo Hi-Fi mode, those integrations are the reason to pick this player over a generic one, and the README documents the status of each, including the ones that do not work.

How the Android build is packaged and versioned

The APK filename encodes everything about the build. The README gives the example 10.5.0.2-release-2024091902-moriafly-arm64-v8a and breaks it into five parts. The version name is four numbers: major, minor, patch and emergency fix count, with the emergency count omitted when it is zero, so 10.4.4 appears without a fourth number. The version type is release, beta or alpha, and release is usually omitted from the name. The README's stated stability order is release, then beta, then alpha, and it notes that alpha versions may still be published publicly with lower stability.

The version code is a timestamp, not a counter. In 2024091902, the README explains, the build was made for the second time on September 19, 2024. That is a useful property: you can compare two APKs without trusting a monotonically increasing integer, and you can tell how old a build is from the filename alone. The last two fields are the channel ID and the architecture. The most recent releases listed for this repository are 12.3.2, 12.3.1 and 12.3.0, all published in the first week of September 2026.

Installing Salt Player on Android and checking the build

Salt Player for Android requires Android 6.0 or higher and supports arm64-v8a and armeabi-v7a. There are two distribution channels. The Moriafly channel is the GitHub Releases page plus CoolApk, and it ships the standard package; the README notes that the CoolApk release is arm64-v8a only. The Google Play channel is a separate package signed and released by Google, and the README states it is incompatible with the standard package, meaning you cannot switch between them by installing over the top.

Open the releases page and pick the APK matching your device architecture. The filename tells you both the architecture and the channel, so a download named with moriafly and arm64-v8a is the standard package for 64-bit devices. The README does not give a command-line install procedure; the download itself is a manual step from the release page, and the README's only warning is to download from official channels and avoid installation files with unknown or unverified signatures.

On a vivo device, Hi-Fi output is not enabled by default. The README documents a manual step that adds the package to the system Hi-Fi list over adb:

settings put global game_support_hifi_list com.salt.music

After running it, the README says to add Salt Player in the Hi-Fi list and then go to System Settings > Sound & Vibration > Enable Hi-Fi. Whether the device supports Hi-Fi at all depends on the model, and the README points to vivo's own product pages for that.

Where the project stops: DSD, HarmonyOS and the Windows gap

Three limitations are documented rather than hidden, and each changes who should use the app. DSD audio in .dsf and .dff form is no longer maintained or supported; the deprecation is dated 2024 in the README, which calls DSD an obsolete format and recommends replacing it with FLAC. If your library is DSD, this player is the wrong tool and the project says so directly. There is a linked article, articles/240902_Deprecated_DSD.md, for the reasoning.

HUAWEI HarmonyOS Music Control Center is marked not supported, with the README citing whitelist control, no adaptation documents found, and unsuccessful contact attempts. vivo's Atomic Walkman is in the same state, suspected whitelist with no adaptation document, tracked in issue #749. These are not bugs waiting on a fix; they are integration requests the project could not progress.

On Windows, the README does not describe a player in this repository. It points to a separate project, SPW, and says to see that documentation for details. The windows/ directory exists at the top level, but the README gives no installation steps for it here. If a Windows local player is what you need, this repository is not the place to get it, and the README does not present it as one.

Salt Player against Poweramp and Auxio

Poweramp and Auxio are the two names that come up in searches around this project, and they represent genuinely different bets. Poweramp is a long-standing commercial Android player with its own audio engine and a paid licence; the trade-off is cost and a closed ecosystem, and it does not pursue the OEM integration table that Salt Player maintains. Auxio is an open-source Android player, which means you can read and build its source, the thing you cannot do with Salt Player here. If code auditability is your deciding criterion, Auxio answers a question Salt Player does not.

Salt Player's differentiator is the system adaptation work: Mi Magic Broadcast, CarWith, Fluid Cloud, Flyme status bar lyrics and Dynamic Ring, Joviincar Smart Car. Those are negotiated or reverse-engineered integrations with specific phone vendors, and they are the reason the README reads like a compatibility matrix instead of a feature list. The cost of that approach is visible in the same table: HarmonyOS and Atomic Walkman are dead ends, and the MIUI widget is still pending. You are choosing a player whose value depends on which phone you own.

Maintenance, licensing and what an upgrade costs you

The repository is not archived, and the last push was on 2026-09-06, which is the same day release 12.3.2 was published. The three most recent releases, 12.3.2, 12.3.1 and 12.3.0, all landed within six days of each other in September 2026, so the release cadence around that period was tight. The repository is MIT licensed, which covers the contents you find here: the README, the articles, the policy documents and the release metadata. It does not turn the player into an open-source application, and the README's legal section separately notes that Salt Player and 糖醋音乐 are registered trademarks of Xunxun Technology (Shanghai) Co., Ltd. in the People's Republic of China, and that Android is a trademark of Google LLC. Nothing here is legal advice; if you plan to redistribute or rebrand anything, read the licence and the trademark notice yourself.

The upgrade cost is mostly a channel decision. The Google Play version follows what the README calls a different update strategy from the standard package, selecting special stable releases or custom-built versions, so it will not track GitHub Releases one for one. The two are incompatible, so upgrading across them means uninstalling first. Within the standard channel, the timestamp version code makes it easy to confirm you are moving forward rather than sideways.

Editorial conclusion

Adopt Salt Player if you want a local Android player that integrates with MIUI, ColorOS, OriginOS and Flyme system features and you are willing to install a signed APK from GitHub or CoolApk. Do not adopt it if you need a Windows player today, if you rely on DSD files, or if you wanted to read or build the player's source, because this repository publishes binaries and tracks issues instead. Before installing, check which channel you are on: the Google Play build is signed by Google and is incompatible with the standard package, so pick one and stay on it. Then verify the signature matches an official channel, because the README explicitly warns against installation files with unknown or unverified signatures.

Frequently asked questions

Official sources

1. License: MIT
2. Moriafly/SaltPlayerSource on GitHub
3. Project website
4. README
5. Releases