Just Player: A Lightweight Video App With Few Frills
Just Player (also referred to as Just (Video) Player) on Android: Just Player DTS/TrueHD Passthrough: Why 'No Sound' Is a Device, Receiver, and Connection Problem
App summary
- App
- Just Player (also referred to as Just (Video) Player)
- Developer
- Marcel Dopita (GitHub user 'moneytoo')
- License
- Apache-2.0
- Version
- unknown
- Size
- unknown
- Price
- Free (no ads, no in-app purchases)
Just Player on Android: a minimal ExoPlayer build, not a full media suite
Just Player — also written as Just (Video) Player — is an Android video playback app from developer Marcel Dopita, who publishes on GitHub as “moneytoo.” It ships under the Apache-2.0 license and costs nothing. No ads, no in-app purchases, no premium tier waiting behind a nag screen. That combination is the entire commercial story, and it is worth stating plainly because it shapes what the app is built to do. There is no upsell path, so there is no reason for the app to steer you toward one.
The listed function set is short. The app plays video. It presents a minimal interface built around gestures. It runs on the Media3/ExoPlayer playback stack. It handles audio passthrough, HDR, and subtitles as listed capabilities. It supports Android TV, picture-in-picture, and handoffs from other apps. Installation is the sixth item. That is the published scope, and it is a playback utility’s scope — not a platform’s.
What Just Player is not matters just as much as what it is. Nothing in the listed feature set describes a media library with metadata scraping, an SMB or NFS browser, a subtitle search-and-download service, or a Chromecast or DLNA sender. Those belong to other kinds of software. Reading this listing as a promise of them will produce disappointment that has nothing to do with whether the app plays video well.
The useful way to hold the app in your head is as a handoff target and a file player: something that opens a video, plays it on Android’s modern media stack, and then gets out of the way. Judged on that description, the feature list is coherent. Judged as a media center, it is not, and it was never meant to be.
The Playback Engine: Media3 and ExoPlayer
The listing names Media3/ExoPlayer as the playback engine, and that single line explains most of the app’s behavior as well as most of its limits. Just Player is a player interface sitting on top of that stack. It is not a from-scratch decoder written by the developer, and the listing does not claim otherwise.
The practical consequence is that format support is a function of the playback stack plus the device it runs on, not a bundled universal decoder that travels with the app. When a file plays, it plays because the whole chain supported it. When a file does not play, or plays silently, the useful question is where in the chain the support ran out — and that question is answered by hardware and connection details, not by tapping around inside the app.
This is where expectations from other players leak in. Plenty of people arrive from apps that advertise “plays everything” and assume every video app carries its own codec library. The listing here makes no such claim, and the Media3/ExoPlayer line is the honest signal about how playback actually happens.
None of this makes the engine a weakness. A modern Android media stack is a reasonable foundation for a player that wants to stay small and stay current with the platform. It just means the app inherits the platform’s constraints instead of papering over them, which is a different design decision than the one made by players that ship large codec bundles.
A Minimal Interface Built Around Gestures
The interface is described as minimal and gesture-driven. In practice that means the app is designed to spend its screen on video rather than on chrome. There is no browsing grid to decorate, because the listing does not describe a library. There is no metadata pane, because the listing does not describe scraping.
Gestures as the primary control scheme is a deliberate trade. It keeps the on-screen furniture sparse, which is what most people want from a player they open to watch one file. It also means the controls are learned rather than read. If you prefer visible buttons and labeled menus, this is a design you will have to adapt to rather than one that adapts to you.
Android TV support is listed separately from the gesture interface, and the listing does not spell out how a gesture-first design maps onto a remote control. That is a detail worth verifying against the developer’s own documentation before you commit a living-room setup to it. The two facts — gestures, and Android TV — are both in the listing; the bridge between them is not.
Android TV, Picture-in-Picture, and Handoffs From Other Apps
Three listed capabilities sit close together and are easy to conflate. The first is Android TV support, which puts the app in the living-room category rather than the phone-only category. The second is picture-in-picture, the Android feature that lets a video keep playing in a small floating window while you use something else.
The third is handoffs from other apps, and it is the most interesting of the three. A handoff means another app passes a video to Just Player for playback. That is the scenario the app is structurally suited to: it receives a stream or file, plays it with the Media3 stack, and does not need to know where the content came from.
What the listing does not describe is native integration with any particular media server. If you use Jellyfin or Plex, the honest framing is that Just Player might serve as an external player those apps hand off to, and the specifics of that arrangement are not established by the published feature set. Anyone promising deeper integration is going beyond what is documented.
Just Player DTS/TrueHD Passthrough: Why ‘No Sound’ Is a Device, Receiver, and Connection Problem
Silent playback on AC3, DTS, or TrueHD files is the complaint that sends most people looking for answers, and it is usually misdiagnosed as an app bug. The listed playback stack is Media3/ExoPlayer, and passthrough on that stack is not the same thing as universal software decoding. The app can hand an encoded audio stream onward; it does not follow that every device will accept the handoff.
Passthrough is a chain, and every link has to agree. The Android device has to be willing to output the format. The connection between the device and whatever decodes the audio has to carry it. The receiver at the end has to recognize it. If any link refuses, the result is silence, a stereo downmix, or a fallback to a format the chain does accept. The exact supported codec list is not published in the fact data, so no honest article can hand you a table of guaranteed formats.
That is why “enable DTS passthrough in Just Player” is the wrong shape of question. The right shape is a set of compatibility checks: does this specific device output this specific format over this specific connection, and does the receiver on the other end accept it? Those are hardware and setup questions. Framing them as an app-side fix invites people to hunt for a toggle that will not rescue an unsupported chain.
The same discipline applies to the other listed capabilities. HDR and subtitles are named in the function set as “Audio Passthrough, HDR, and Subtitles.” That is a scope statement, not a guarantee that every HDR variant and every subtitle format will render correctly on every Android device. Keep the claims at the level the listing makes them.
If you are shopping for a player specifically because your device lacks DTS or TrueHD passthrough, understand that no app can add that capability back. The limitation lives below the app layer.
Just Player Has No Listed SMB/NFS, Subtitle Download, or Chromecast Features: What the Minimal Player Leaves Out
This is the section where expectations need the most pruning. The listed feature set includes a minimal gesture-based interface and handoffs from other apps. It does not include a media library, an SMB or NFS browser, a subtitle search-and-download service, or a casting stack. Those absences are not oversights to be worked around; they are the shape of the product.
So: does Just Player support SMB or NFS network shares? Not according to anything in the listed function set. If you need to browse a NAS from inside the player, this app is not that tool, and no amount of exploring its menus will make it one. Does it download subtitles automatically? Again, nothing in the listing describes subtitle retrieval. Subtitles are listed as a playback capability, which is a different thing from a subtitle acquisition service.
Can it cast to a Chromecast or DLNA device? The listing does not describe a casting stack, so it should not be presented as a Chromecast or DLNA sender. Handoffs from other apps run in the other direction: content arrives at Just Player rather than being pushed out of it.
For Jellyfin and Plex users, the only scenario the fact data supports is the handoff. Treat Just Player as a possible external playback target when another app sends it a video. Native integration details are unknown, and the listing gives you no reason to expect them. Marking these features as “not established” is more useful than hunting for hidden settings that the published scope says are not there.
Who Should Skip Just Player: Kodi, Plex, and Jellyfin Media-Center Expectations vs a Media3 Handoff Player
If you want metadata scraping, library management, or built-in network-share browsing, you are outside the listed scope of this app. Those are media-center features, and Just Player is not described as a media center. Choosing it and then judging it against Kodi or a full Plex setup is a category error, not a fair comparison.
The fact data does support Android TV, picture-in-picture, and handoffs from other apps. That is a real set of living-room-relevant capabilities. It is not a full media-center replacement, and the gap between those two things is large: no library, no scraping, no share browsing, no casting.
Jellyfin and Plex users have a narrower reason to care. Just Player can plausibly serve as an external playback handoff target, with integration specifics unknown. If your server app can hand a stream to an external player, this is a candidate. If you want the server’s library to live inside the player, it will not.
Set expectations around the license and the price, too. Apache-2.0, free, no ads, no in-app purchases describes a focused playback utility maintained as open source. It does not describe an all-in-one media hub, and the absence of ads and purchases means there is no product roadmap being funded by upsells toward one.
Just Player Dolby Vision Green/Purple Screens and ISO/BDMV Limits: HDR and Container Realities on Android
HDR support is listed. Correct rendering of every HDR variant on every Android device is not, and that distinction explains the purple-and-green Dolby Vision screens people report. HDR and Dolby Vision behavior is device- and display-dependent. The app can pass along what it is given; whether the panel and the system compositor interpret it correctly is a separate matter.
Purple or green tinting should be treated as compatibility and troubleshooting territory rather than a settled app defect. The exact device support matrix is unknown from the fact data, and so is the set of Dolby Vision profiles the app handles. Anyone who tells you a specific profile is or is not supported is going beyond what is documented here.
Containers are the other hard boundary. ISO and BDMV folder playback are not in the listed function set. Do not read disc-image support or folder-structure navigation into the app; nothing in the published scope implies it. If your library is built from full disc rips in those structures, this is not the player for that job.
HDR10+ support is likewise unknown from the fact data and should be labeled as such rather than assumed. The safe summary is the one the listing supports: HDR is a listed capability, rendering depends on your hardware, and the fine print on formats and profiles is not published.
How to Install
Install from the official source: the developer’s own project page, published under the GitHub handle “moneytoo.” That is the distribution channel the fact data points to, and it is the one to trust. Third-party APK mirrors are not the official source, and treating them as equivalent is how people end up with builds the developer never shipped.
The app is free with no ads and no in-app purchases, so there is no paid unlock to chase and no reason to accept a modified build from an unofficial site. Under Apache-2.0 the source is available as well, which means the project can be inspected and built by anyone who wants to — a meaningful property for a utility that handles your media files.
On Android TV, installation follows whatever the developer’s distribution supports for that platform. The listing confirms Android TV as a supported platform; it does not spell out a separate TV-specific install path. Check the project page for current instructions rather than relying on a general guide written for a different app.
Verdict
Just Player is a focused, free, Apache-2.0 Media3/ExoPlayer playback and handoff utility for Android and Android TV. That sentence is the whole review, and everything else in this article is a consequence of it. The app does a narrow job and does not pretend to a wider one.
It is for you if you want a small, ad-free player that opens a video, uses the platform’s modern media stack, supports picture-in-picture, and can receive handoffs from other apps — including as a possible external player when a server app passes content along. It is also for you if you value an open license and a developer who publishes under his own name.
It is not for you if you want a media library with metadata and scraping, built-in SMB or NFS browsing, Chromecast or DLNA casting, automatic subtitle downloads, ISO or BDMV playback, video editing or downloading tools, or a dedicated music player. It is not for you if your device lacks DTS or TrueHD passthrough and you are hoping software will substitute for hardware. And it is not for you if you expect a Kodi or Plex replacement, because the listed feature set describes no such thing.
The most common disappointments around this app come from asking it to be something the listing never claimed. Read the scope, match it to your setup, and the app behaves exactly as advertised.
Pros
- Open source (Apache-2.0) with publicly readable code and issue tracker on GitHub
- No ads or in-app purchases; the app is a single-purpose player rather than an ad-supported media suite
- Modern Media3/ExoPlayer pipeline gives solid HDR, audio-passthrough and subtitle handling, and it works well on Android TV boxes
- Small, focused feature set that makes it a good 'open with' handler for files and streams from other apps
Cons
- No media library or catalog management: it is a 'just play' player, so browsing a large local collection is limited compared with library-based players
- Codec and HDR support depends on the device's hardware and platform decoders; there is no guarantee for exotic formats on every device
- Fewer extras than full-featured players (no built-in subtitle download service, no casting features of its own, limited streaming-service integration)
- Maintained by a small independent developer, so release cadence and long-term support depend on one person
The link goes straight to Marcel Dopita (GitHub user 'moneytoo'). We do not host app files.
Frequently asked questions
Is Just Player (also referred to as Just (Video) Player) free?
The recorded pricing model is Free (no ads, no in-app purchases).
What license does it use?
It is listed under Apache-2.0.
Where can I download the official version?
The official link points to https://github.com/moneytoo/Player.