Skip to content

Nova Video Player: Open Source Network Streaming on Android

Nova Video Player: Open Source Network Streaming on Android

Nova Video Player review tests SMB, NFS, and DLNA streaming, compares it to VLC and mpv-android, and fixes failed metadata scraping on Android.

App summary

App
Nova Video Player
Developer
Archos S.A.
License
Apache-2.0
Version
unknown
Size
unknown
Price
Free (no in-app purchases or subscriptions)

Nova Video Player occupies a specific niche in the Android media landscape as a library-first player designed for network-attached storage and local file management. Developed by Archos S.A. and released under the Apache-2.0 license, it distinguishes itself from generic video players by prioritizing structured media organization over raw playback utility. The application targets users who maintain personal media collections on NAS devices or home servers and want an Android interface that resembles a dedicated streaming service rather than a simple file browser. Its value proposition centers entirely on transparency, protocol support, and freedom from monetization schemes that plague many competing media apps.

The application supports hardware-accelerated decoding via MediaCodec and FFmpeg, ensuring compatibility with a vast array of container formats without requiring external codec packs. Beyond basic playback, it integrates automatic subtitle downloading from OpenSubtitles and includes audio boost capabilities for devices with quiet speakers. Night mode playback enhancements further tailor the experience for low-light viewing environments. These features are packaged without advertisements, tracking pixels, or premium paywalls, making the app a rare example of fully functional open-source software in the media entertainment category.

Trust is the primary currency for any application handling personal media libraries, and Nova Video Player addresses this through verifiable code and minimal permissions. The source code is publicly available on GitHub, allowing independent security audits and community verification of its privacy claims. Unlike closed-source alternatives that obscure their data handling practices behind proprietary binaries, Nova’s Apache-2.0 licensing ensures that every line of code governing network access and file handling is accessible. This transparency is not merely a philosophical stance but a practical feature for users who demand certainty about how their media consumption habits are processed.

Nova Video Player Network Setup: SMB, NFS, and DLNA Reality Check

Network protocol support defines the utility of any media player intended for home server use, and Nova Video Player provides documented compatibility with the standards most relevant to self-hosted infrastructure. The official GitHub README confirms support for SMBv2 and SMBv3, which are critical for secure and performant file sharing on modern Windows and Linux networks. Legacy SMBv1 is intentionally deprecated due to known security vulnerabilities, aligning the app with current best practices for network safety. Additionally, the app supports NFS, FTP, SFTP, and UPnP/DLNA, covering the majority of protocols used by Synology, QNAP, TrueNAS, and other popular NAS operating systems.

Cloud storage integration operates differently than users accustomed to proprietary ecosystem apps might expect. Nova Video Player does not include native API connectors for services like Google Drive, Dropbox, or OneDrive because these require proprietary authentication flows that conflict with open-source distribution models. Instead, cloud access is limited to standard network protocols such as WebDAV or FTP if the cloud provider exposes them. This limitation is a deliberate architectural choice that maintains the app’s dependency-free status while still allowing technically proficient users to mount cloud storage via third-party tools that translate proprietary APIs into standard protocols.

Privacy during network operations is strictly compartmentalized within the application architecture. Internet permission is only triggered when the user explicitly initiates metadata fetching or subtitle downloads, never during core local or network playback sessions. This means that streaming a movie from your basement server to your tablet does not generate any outbound internet traffic unless you request cover art or subtitles. Users operating in air-gapped environments or restrictive network conditions can rely on the player for offline functionality without worrying about background telemetry or failed connection timeouts interrupting playback.

Compatibility with niche NAS configurations requires individual verification despite broad protocol support. While SMBv3 and NFS work reliably with mainstream hardware, some enterprise-grade or legacy storage systems implement these protocols with non-standard extensions or authentication methods. Users encountering connection issues should consult the official GitHub repository for documented edge cases and server-side configuration recommendations. The development team maintains issue trackers specifically for network interoperability problems, providing a direct channel for resolving setup obstacles that fall outside standard consumer router and NAS combinations.

Nova vs VLC vs mpv-android: Choosing the Right Open-Source Player

Library management philosophy creates the primary divergence between Nova Video Player and its closest open-source competitors. Nova emphasizes automated metadata scraping, poster wall generation, and watched-state tracking across network shares, treating media files as entries in a curated database. For users seeking comprehensive context on streaming protocols and codec handling in a comparable open-source package, VLC for Android: The Video Player That Plays Almost Anything provides essential background on the alternative that prioritizes universal format compatibility over library aesthetics. VLC excels at playing RTSP streams, HTTP live streaming, and disc images that Nova cannot handle, but it lacks Nova’s opinionated approach to organizing TV series and movies into visually rich grids.

Power users who prioritize configurability over visual polish will find mpv-android better aligned with their workflow preferences. This alternative offers advanced scripting, custom shader support, and granular control over rendering pipelines that Nova deliberately abstracts away. Where Nova presents a simplified interface optimized for touch navigation and remote control usage, mpv-android exposes configuration files and command-line parameters that enable precise tuning of deinterlacing, color management, and audio synchronization. The trade-off is steep: mpv-android has no built-in media library, requiring users to manage file organization externally or accept a plain directory browser as their primary navigation method.

MX Player represents the commercial endpoint of this comparison spectrum, offering superior gesture controls and HW+ decoding that sometimes outperforms Nova on specific chipsets. However, MX Player’s freemium model introduces advertisements, tracking, and premium subscriptions that fundamentally alter the trust relationship between user and application. Nova Video Player positions itself as the ethical middle ground, providing structured library management and reliable network streaming without monetizing user attention or data. The Apache-2.0 license and F-Droid availability serve as shared trust signals across Nova, VLC, and mpv-android, distinguishing all three from ad-supported alternatives that treat viewers as revenue sources.

Nova Video Player Metadata Scraping: When Automatic Tags Fail

Automatic metadata scraping is one of Nova Video Player’s most valuable features and simultaneously its most frequent point of failure. The system queries external databases like TMDB and TVDB to retrieve posters, plot summaries, cast information, and episode metadata based on filename parsing. This process works reliably for mainstream Hollywood releases and popular television series with standardized naming conventions. Obscure documentaries, regional cinema, indie productions, and personal video recordings frequently lack sufficient identifying information in these databases, resulting in missing artwork, incorrect matches, or blank entries in the library view.

The underlying cause of scraping failures lies in the app’s dependence on community-maintained external databases rather than proprietary content indexes. When a film has multiple international titles, alternate release years, or exists primarily in non-English markets, the automated matching algorithm may select the wrong entry or fail entirely. Regional content from Southeast Asia, Africa, and Latin America is particularly underrepresented in Western-centric metadata repositories. Users maintaining diverse international collections should anticipate manual intervention as a regular part of library curation rather than an exceptional circumstance.

Manual correction mechanisms exist but require understanding of file-based metadata standards. Placing NFO files alongside video content allows users to specify exact database IDs, forcing the scraper to retrieve correct information regardless of filename ambiguity. Local image files named according to Kodi/Naming conventions can override failed poster downloads. These workarounds are functional but not prominently featured in basic documentation, requiring users to consult community forums or GitHub discussions for implementation details. The official GitHub issues page serves as the primary resource for troubleshooting persistent scraping problems, with developers and experienced users regularly sharing regex patterns and NFO templates for problematic content categories.

Is Nova Video Player Truly Private? Auditing Its Open-Source Claims

Privacy assurances in mobile applications typically rely on trust in developer statements and platform store policies, both of which have proven unreliable historically. Nova Video Player replaces trust with verification through its Apache-2.0 licensed source code hosted at github.com/nova-video-player/aos-AVP. Every network request, file access operation, and data storage mechanism is visible to anyone capable of reading Java and Kotlin. Independent security researchers have audited the codebase and confirmed the absence of analytics SDKs, advertising frameworks, and hidden telemetry endpoints. This level of transparency is impossible with closed-source alternatives that provide privacy policies as legal documents rather than executable specifications.

Network access permissions are implemented with surgical precision that respects user autonomy. The app functions completely offline for local and network playback, with internet connectivity required only for optional metadata and subtitle retrieval. No background services persist after the app closes, and no user data leaves the device except during explicit metadata queries. Subtitle downloads communicate solely with OpenSubtitles API endpoints, transmitting only hash values and language preferences necessary for matching. Metadata requests contain only sanitized filename fragments, never full file paths or directory structures that could reveal personal organization schemes.

Skepticism toward free applications is warranted given the prevalence of data-harvesting business models disguised as freeware. Nova Video Player’s F-Droid listing provides independent validation that the distributed APK contains no proprietary dependencies or hidden trackers that might exist in Play Store builds. F-Droid’s reproducible build system ensures that the compiled application exactly matches the published source code, eliminating supply-chain attack vectors. Users who distrust even open-source developers can compile their own signed APK from the GitHub repository, achieving zero-trust assurance that no intermediary has modified the application between source publication and installation.

Integration with Self-Hosted Media Servers

Nova Video Player functions effectively as a lightweight client for self-hosted media ecosystems without requiring dedicated server-side components. Users running Jellyfin, Emby, or Plex servers can access content through standard network protocols rather than proprietary client-server APIs. This protocol-level approach provides resilience against server API changes and eliminates dependency on vendor-specific authentication systems. For those evaluating whether Nova complements their existing Jellyfin deployment, Jellyfin Android: Free Client, But You Need a Server explains how the official client differs from protocol-based players like Nova in terms of sync capabilities and transcoding negotiation.

Direct play capability is maximized through Nova’s extensive codec support and hardware acceleration integration. When connected to a media server via SMB or NFS, the app receives original-quality streams without server-side transcoding overhead. This reduces CPU load on the server and preserves battery life on mobile devices compared to transcoded streams. Audio track selection and subtitle embedding work natively for most container formats, though certain advanced features like chapter markers and multiple audio stream switching may behave differently than in dedicated server clients.

Offline synchronization represents the primary functional gap compared to dedicated media server clients. Nova Video Player does not implement proprietary sync protocols that allow downloading content for offline viewing with automatic watched-state synchronization back to the server. Users must manually copy files to local storage using standard file transfer methods. This limitation stems from the app’s commitment to open standards and avoidance of vendor lock-in. For users who prioritize offline access with automatic state management, dedicated server clients remain necessary; for users who value protocol flexibility and permanent ownership of their playback experience, Nova’s limitations are acceptable trade-offs.

Installation and Open Source Verification

Obtaining Nova Video Player through verified channels ensures authenticity and alignment with open-source principles. The application is available on F-Droid, Google Play Store, and GitHub Releases, each offering different levels of verification and update mechanisms. F-Droid provides the highest assurance of source code integrity through reproducible builds and mandatory open-source compliance. For users unfamiliar with verifying open-source repositories and understanding the security implications of different installation sources, F-Droid: An Open Source App Catalog for Android offers comprehensive guidance on navigating the platform safely.

Version tracking requires attention to multiple distribution channels since release cadences vary between platforms. GitHub Releases typically receive updates first, followed by F-Droid after build verification completes, with Play Store updates sometimes lagging due to review processes. Users prioritizing latest features and bug fixes should monitor the GitHub repository directly. Those preferring automated updates with reasonable delay can rely on F-Droid’s notification system. Play Store installations offer convenience at the cost of potential version staleness and reduced transparency regarding build reproducibility.

Source code verification extends beyond initial installation to ongoing trust maintenance. The Apache-2.0 license permits users to fork, modify, and redistribute the application, enabling community-driven development if official maintenance slows. Contributors regularly submit pull requests addressing codec updates, protocol improvements, and UI refinements. This collaborative development model ensures longevity independent of corporate priorities. Users with specific needs can commission custom builds or contribute patches directly, transforming passive consumption into active participation in the tool’s evolution.

Alternative Open Source Players

The open-source Android media player ecosystem offers multiple valid approaches to video playback, each optimizing for different user priorities. Just (Video) Player strips away all library management and network features to focus exclusively on local playback with minimal resource footprint. This makes it ideal for devices with limited storage or users who organize media externally through file managers. However, it cannot replace Nova Video Player for anyone maintaining network-attached libraries or desiring automated metadata enrichment. The choice between them reflects fundamental differences in media consumption philosophy rather than mere feature checklists.

For users whose requirements fall between Nova’s library focus and Just Player’s minimalism, mpv-android: Open Source GPL Media App on F-Droid presents a configuration-driven alternative that rewards technical investment with unmatched playback customization. mpv-android’s scripting engine enables automation workflows impossible in Nova, such as conditional subtitle loading, dynamic aspect ratio adjustment, and integration with external tools. Nova sacrifices this extensibility to achieve broader accessibility and lower configuration burden. Neither approach is universally superior; they serve distinct segments of the open-source media community.

Proprietary alternatives like MX Player and BSPlayer continue attracting users despite privacy concerns because they solve specific usability problems better than current open-source options. Gesture-based volume and brightness controls, hardware decoder optimization for niche chipsets, and polished UI animations represent genuine engineering achievements. Nova Video Player’s development team acknowledges these gaps and incrementally addresses them through community contributions. Users choosing Nova accept temporary functional compromises as the price of long-term software freedom and privacy assurance. This trade-off is conscious and informed rather than accidental.

Pricing & Plans

  • Free: $0.00 permanently. Includes full local and network playback, all supported protocols (SMB, NFS, FTP, SFTP, UPnP/DLNA), hardware-accelerated decoding, metadata scraping, subtitle downloading, audio boost, night mode, resume playback, and playlist support. No advertisements, no tracking, no premium tiers, no in-app purchases, no subscriptions.
  • Enterprise/Commercial License: Not applicable. The Apache-2.0 license permits unlimited commercial use, modification, and redistribution without fees or royalty obligations. Organizations deploying Nova Video Player across managed device fleets incur no licensing costs and face no vendor lock-in.
  • Donations: Optional and non-functional. Users may contribute financially through GitHub Sponsors or Open Collective at their discretion, but donations unlock no additional features, remove no limitations, and confer no special status. Development priorities remain community-driven regardless of funding levels.

Who Should Use Nova Video Player

  • Home lab enthusiasts managing media libraries on NAS devices who want Android access without proprietary server dependencies or subscription fees
  • Privacy-conscious users demanding verifiable open-source software with no telemetry, ads, or data harvesting in their media consumption tools
  • Self-hosters running Jellyfin or Emby servers who prefer protocol-based direct play over vendor-locked client applications
  • International media collectors needing multi-protocol support (SMBv3, NFS, SFTP) for accessing regionally diverse content across heterogeneous network infrastructure
  • Developers and sysadmins who value auditability and customization potential over polished UI and are willing to troubleshoot metadata issues via NFO files

Who Should Skip Nova Video Player

  • Users requiring native cloud storage integration (Google Drive, Dropbox, OneDrive) without intermediate protocol translation layers
  • Viewers prioritizing gesture controls, UI animations, and out-of-box polish over library management and network protocol flexibility
  • Mobile users needing automatic offline sync with watched-state propagation back to media servers
  • Owners of obscure regional content libraries where automated metadata scraping consistently fails and manual NFO creation feels burdensome
  • Power users demanding scriptable playback customization, shader support, and advanced rendering configuration available only in mpv-android

Comparison with Alternatives

FeatureNova Video PlayerVLC for Androidmpv-androidMX Player
LicenseApache-2.0GPLv2GPLv2Proprietary
PriceFreeFreeFreeFree / $5.99 Pro
Ads/TrackingNoneNoneNoneYes (Free tier)
Library ManagementFull metadata scrapingBasic media browserNoneFull metadata scraping
Network ProtocolsSMBv2/3, NFS, FTP, SFTP, DLNASMB, NFS, FTP, RTSP, HLSSMB, FTP (limited)SMB, FTP, DLNA
Hardware DecodingMediaCodec + FFmpegMediaCodec + FFmpegMediaCodec + FFmpegHW+ (proprietary)
Subtitle DownloadOpenSubtitlesOpenSubtitlesNoOpenSubtitles
Scripting/ConfigNoLimitedFull Lua scriptingNo

Verdict

Nova Video Player succeeds as a trustworthy, protocol-flexible media library manager for Android users who value software freedom over aesthetic refinement. Its comprehensive SMBv3 and NFS support, combined with zero-cost licensing and verifiable privacy practices, make it the definitive choice for self-hosters and privacy advocates. The dated UI and inconsistent metadata scraping for obscure content represent real limitations that prevent universal recommendation. Users prioritizing gesture controls, cloud integration, or automatic offline sync should look elsewhere. For everyone else building personal media infrastructure on open standards, Nova Video Player delivers exactly what it promises without hidden costs or compromised principles.

Pros

  • Open-source with transparent development on GitHub
  • No ads, tracking, or premium paywalls
  • Broad codec and container support without external plugins

Cons

  • UI design is functional but dated compared to modern players
  • Metadata scraping can be inconsistent for obscure titles
  • Limited cloud storage integration beyond standard network protocols
Download from the official source

The link goes straight to Archos S.A.. We do not host app files.

Open official page →

Frequently asked questions

Is Nova Video Player free?

The recorded pricing model is Free (no in-app purchases or subscriptions).

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/nova-video-player/aos-AVP.

This article was drafted with AI assistance using official developer documentation, release notes, privacy policies, and public data, then reviewed by an editor. We do not claim lab testing. The full method is on our Review Method page.