Auxio: Open-Source Local Music Player On
Auxio review: fix missing SD-card songs on Android 8+, test M3U playlist import/export, and see why this local player isn’t Android Auto-ready.
App summary
- App
- Auxio
- Developer
- OxygenCobalt
- License
- GPL-3.0-only
- Version
- unknown
- Size
- unknown
- Price
- Free
Auxio Not Showing Songs on an SD Card: Android 8.0+ Storage Reality and What to Check
Auxio’s core job, as the available material describes it, is to scan and browse a local music library stored on the device. That one sentence explains most SD-card complaints before any troubleshooting begins. The app is not a streaming client and not a cloud front end, so when a track is missing, the question is why the library scanner did not pick it up — not why a server failed to return it. If hi-res output and USB DAC behaviour matter to you, the Poweramp review covers the local-library and bit-perfect caveats that a simpler player like Auxio does not. For a play-anything approach that trades library organisation for format coverage, the VLC for Android review shows how its media-first design differs from Auxio’s music-focused library. If you want another open-source media app with config-file control, the mpv-android review explains where mpv.conf and input.conf fit and why desktop scripts do not carry over.
The stated minimum requirement is Android 8.0 (API 26) or higher. That is a floor, not a promise. The same fact sheet adds that exact device compatibility should be checked for each release, which is an unusually honest caveat and one worth taking literally. A phone running Android 8.0 satisfies the stated requirement; whether a particular build behaves correctly on a particular manufacturer’s skin is a separate question that the documentation does not settle.
Here is the part that has to be said plainly. The facts provided do not document Storage Access Framework steps, and they do not describe how Auxio handles removable storage on Android 11 and later, where scoped storage changed the way apps reach SD cards. Anything more specific than that would be invention, so treat the exact permission flow as unknown and verify it on your own hardware. The same applies to whether the app requests folder-level access, all-files access, or something else entirely.
What you can do is narrow the problem down rather than guess at it. Confirm the card is mounted and that another app can see the same files. Check whether Auxio finds music in internal storage but not on the card — that split points at a storage-scope issue rather than a broken file. Then confirm whether the folder holding your music is actually inside the library the app scans, since a scanner can only report what it was pointed at.
If a rescan changes nothing and internal storage works fine, you have isolated the problem to removable media handling on your specific device and Android version. At that point the honest answer is that the facts here cannot tell you whether this is a known limitation, a permission state, or a device quirk. Check the project’s issue tracker at the official repository before assuming the app is broken, and check compatibility for the exact release you installed.
Auxio M3U Playlist Import and Export: What “Playlist Support” Does and Does Not Confirm
The fact data confirms playlist support. That is the whole of it. It does not confirm M3U import, it does not confirm M3U export, and it says nothing about editing playlists in an external editor and having Auxio pick up the changes. Those are three different capabilities, and conflating them is how people end up disappointed.
Auxio is a local playback app with local music library scanning and playback controls. Playlist expectations should be framed around on-device library use: building lists from tracks the scanner has already found, then playing them back. That is the context in which the confirmed feature sits, and it is the context in which the word “playlist” is least likely to mislead you.
Any M3U workflow has to be labeled unverified until you check it in the installed release. The facts simply do not specify playlist file compatibility, so a claim that Auxio reads .m3u files would be fabricated, and a claim that it cannot would be equally fabricated. If playlist portability matters to you — because you maintain lists in a desktop player and want them on your phone — test that specific path before you commit to the app.
There is a practical way to think about the risk. Playlists that live inside the app are usually tied to how the app identifies tracks; playlists stored as files are tied to file paths. Those two models diverge the moment you move files or change an SD card. Since the facts do not tell us which model Auxio uses, the safest assumption is that you should not migrate a large curated playlist library on faith.
Auxio and Android Auto: Why a Local Music Player Is Not Automatically a Car-Ready App
The fact data lists playback controls and local playback. It does not list Android Auto, it does not list widgets, and it does not list lock-screen control support. Those absences are not proof that the features are missing — a fact sheet is not a feature audit — but they are a clear signal that you should not assume them.
Auxio is a local-first Android player that requires no account for local playback, and it is explicitly not designed as a streaming or cloud music client. That description tells you what the app is optimized for: files on your phone. Android Auto is a separate integration surface with its own requirements, its own testing burden, and its own review process. Being a music player does not get you there automatically.
Drivers who need Android Auto should treat support as unknown and check the current release and their specific device rather than inferring it from the app’s category label. This is the single most common misconception about local players, and it cuts both ways: people buy a phone mount expecting a car interface, and people dismiss a good player because it lacks one.
If in-car listening is a hard requirement, the practical move is to verify before you rely on it. Install the app, connect to your head unit, and see what appears. Do not plan a road trip around an assumption that a local player will surface in your dashboard.
Auxio F-Droid vs GitHub vs Play Store: Which Build Exists, and Which Is Unknown
The facts confirm distribution via F-Droid. They confirm a source repository on GitHub at github.com/OxygenCobalt/Auxio. They confirm the Android package name org.oxycblt.auxio. Those three details are enough to identify the project and to check that an installed app is the one you think it is.
Current Google Play listing status is explicitly unknown. So are the latest stable version number and the APK download size. That means any article, forum post, or comment telling you which channel updates fastest, which build is signed by whom, or whether the Play Store version has extra features is working from information that is not in the record here.
Differences between F-Droid, GitHub, and any Play Store build are not documented in the facts, so this article will not claim feature parity, update cadence, or signing details. Those are exactly the claims that age badly and mislead people. If you need to know, compare the channels yourself at the official source rather than trusting a summary.
The package name is worth remembering for a mundane reason. Android lets you install builds from multiple sources, and it is easy to end up with two copies of the same app under different signatures, which usually fails to install or behaves oddly. Knowing that the identifier is org.oxycblt.auxio lets you confirm what is actually on the phone.
Scanning, Browsing, and Playback Controls: The Three Things the Fact Sheet Actually Confirms
Strip away the assumptions and the confirmed feature set is short: local music library scanning, playback controls, and playlist support, wrapped around the two stated functions of playing local audio files and browsing and organizing a local library. That is a coherent, deliberately narrow product.
“Browsing and organizing” here should be read as organizing your view of a library you already have, not as repairing that library. The facts do not describe tag editing, artwork fetching, or metadata cleanup, and the app is not positioned as a library maintenance tool. If your collection is a folder of files with inconsistent tags, Auxio will scan it; it will not fix it.
Playback controls are listed without elaboration, which means the specifics — shuffle behavior, repeat modes, queue management, notification controls — are not documented in the material available. That is not a criticism, just a boundary. The fact sheet tells you the category of feature, not its depth.
This narrowness is the point, and it also defines who should look elsewhere. Listeners who mainly use Spotify or YouTube Music, users who want cloud sync across phones and computers, Poweramp-style tinkerers needing an equalizer and DSP, people who need built-in tag editing, drivers who require Android Auto, and anyone who wants video playback or podcast management are all outside the intended audience. None of those are flaws in Auxio; they are different products.
Reading Auxio’s Provenance: Developer, GPL-3.0 License, and Package Name
Auxio is developed by OxygenCobalt, and the source is hosted on GitHub. The license is GPL-3.0-only. That combination is the strongest concrete claim you can make about the app: the codebase can be independently reviewed, and the license terms are explicit rather than implied.
GPL-3.0-only means the source is available and that redistributed modified versions must stay under the same license. For a user, the practical benefit is reviewability — someone with the skills can read what the app does rather than trusting a description. It is not a guarantee of quality, and it is not a security audit. It is a precondition for both.
The package name, org.oxycblt.auxio, plus the repository URL, gives you a way to verify provenance without relying on an app store listing. That matters more than usual here, because the current Google Play listing status is unknown and the latest stable version number is not documented. When version metadata is missing, identity metadata becomes the thing you check.
Distribution via F-Droid is confirmed. Beyond that, the facts are silent on channel differences, so treat any claim about how the F-Droid build compares to a GitHub build as unverified.
Gapless Playback, Crossfade, ReplayGain, and the Equalizer Question
These are the questions that decide whether a player is “good enough” for a serious listener, and the fact sheet does not answer any of them. Gapless playback, crossfade, and ReplayGain are not listed. Neither is an equalizer, DSP, or a sleep timer. Their absence from the list is not proof they do not exist, but it is the only evidence available, and it points toward a player built around straightforward local playback.
The misconception worth correcting directly is that Auxio is a full-featured Poweramp-style player with equalizer and DSP. Nothing in the facts supports that framing. If you want tone controls, visualizers, and per-track gain adjustment, you are shopping in a different category, and the alternatives named in the material — VLC for Android for broad format support, Musicolet for ad-free offline playback — are more plausible starting points for that kind of feature hunting.
Scrobbling deserves its own line because it is asked about constantly. Last.fm integration and other scrobbling services are not mentioned anywhere in the facts. Treat scrobbling as unknown and verify in the installed release if it matters to you, rather than assuming that any local player must support it.
The honest summary is that these features are unconfirmed, and unconfirmed is different from absent. If gapless playback is a dealbreaker for live albums and DJ mixes, test it on your own files before you rebuild your listening setup around the app.
Tag Editing, Album Art, Lyrics, and Scrobbling: Maintenance Tools the Facts Do Not List
Auxio does not fetch album art and artist photos from the internet, and it does not edit tags or fix messy music libraries. That statement is safe to make not because the facts explicitly deny it, but because the facts describe a local-first app with no account requirement and no cloud component. Online artwork and metadata retrieval would require a network service the documentation never mentions.
The same reasoning covers lyrics. Automatic lyrics are not listed, and there is no indication of an online lookup. If your library depends on embedded lyrics, that is a different scenario from expecting the app to find them for you.
This is where a lot of people misjudge the app before installing it. They come from streaming services where the catalog is curated, artwork is automatic, and metadata is somebody else’s job. Auxio assumes the opposite: you own the files, you organized them, and the app’s role is to scan and play them.
The correct expectation is that library quality is your responsibility. If that sounds like a burden, it is — and it is the burden that every local-first player shares. Users who want built-in tag editing and library cleanup tools should look at software built for that purpose rather than hoping a playback app grows the feature.
Album Artist, Multi-Disc Sets, and How Deep the Library Model Goes
How Auxio handles album artist versus track artist, and how it groups multi-disc compilations, is not documented in the facts. The app browses and organizes a local library, which means it must read tags in some fashion, but which fields it groups by and how it resolves conflicts between them is unknown.
This matters more than it sounds. A two-disc album with consistent tags can still show up as two separate albums if the grouping logic keys on disc number, and a compilation can fragment into one album per track artist if album artist is ignored. Whether Auxio does either of those things is not something the available material can tell you.
The practical advice is to check with a small test case rather than a full library. Rip one multi-disc album and one compilation, scan them, and look at how they appear. That takes minutes and tells you more than any description can, including this one.
Until then, the fair characterization is that the library model’s depth is unverified. The confirmed capabilities are scanning, browsing, organizing, and playback — everything past that is a question for the installed release.
Verdict
Auxio is a credible open-source local-only Android player for people who already own and organize their music files. The confirmed facts support that much without stretching: scanning, browsing, playback controls, playlist support, GPL-3.0-only licensing, no account required for local playback, and F-Droid distribution. If you have a folder of audio files and you want an app that plays them without asking you to sign in, this is a reasonable thing to install from the official source.
It should be chosen for playback and library browsing, not for anything adjacent. It is not a streaming client, so listeners who mainly use Spotify or YouTube Music are in the wrong place. It is not a cloud sync tool, so users wanting their library mirrored across phones and computers should look elsewhere. It is not a Poweramp-style tinkerer’s playground, and the equalizer, DSP, and visualizer crowd will find it thin. It is not a tag editor, so people who need library cleanup should not expect the app to fix a messy collection. It is not a video player or a podcast manager.
Android Auto support is unknown and should be verified before anyone builds a commute around it. M3U import and export are unknown and should be tested before migrating playlists. SD-card behavior on Android 11 and later is undocumented in the material available, and storage problems should be diagnosed on-device rather than assumed to be bugs or assumed to be fixed. The latest version number, APK size, and current Play Store status are all unknown, which makes the official repository and F-Droid the channels to check.
One more group should be named explicitly: people who assume a music player is only for rooted or tech-savvy users. Nothing in the facts supports that. The app requires Android 8.0 or higher and no account; the technical bar is installing an app. The real filter is not skill, it is whether you keep local files at all.
Pros
- Open-source codebase that can be independently reviewed
- Local-first playback without requiring an account
- Distributed via F-Droid
Cons
- Not designed as a streaming or cloud music client
- Focused on local playback rather than all-in-one media features
- Exact device compatibility should be checked for each release
The link goes straight to OxygenCobalt. We do not host app files.
Frequently asked questions
Is Auxio free?
The recorded pricing model is Free.
What license does it use?
It is listed under GPL-3.0-only.
Where can I download the official version?
The official link points to https://github.com/OxygenCobalt/Auxio.