Skip to content

Fermata Auto Brings Open-Source Media Playback to Android Auto

Fermata Auto Brings Open-Source Media Playback to Android Auto

Fermata Auto review: verified local video and subtitle support, plus untested wireless hotspot and audio-focus gaps during calls and navigation.

App summary

App
Fermata Auto
Developer
Andrey Pavlenko
License
GPL-3.0-only
Version
unknown
Size
unknown
Price
Free (open source)

The GPL-3.0 License Is the Most Concrete Thing Fermata Auto Offers

Fermata Auto is published under GPL-3.0-only, and the project lives at github.com/AndreyPavlenko/Fermata. That combination is the most verifiable claim in the entire fact set. The license is not a marketing detail; it means the source code is publicly available and can be read, audited, forked, and rebuilt by anyone willing to put in the work. Developer Andrey Pavlenko ships it free.

What the license does not give you is a support contract. There is no verified privacy policy, no published release cadence in the supplied facts, and no confirmed latest version number. You get code and a repository. If something breaks on your specific phone or head unit, the remedy is reading issues, reading source, or waiting — not opening a ticket with a company that owes you a response.

That distinction matters more than usual here, because Fermata Auto is not an official Google or Android Auto app. It is a third-party project that plugs into Android Auto’s media surface. The openness is a genuine advantage — you can check what it does with a stream URL before you hand one over — but it shifts the burden of verification onto you. Treat the repository as the documentation of record, and treat everything else, including this article, as a starting point.

Local Files and Network Streams Are Two Different Promises

The fact data lists two playback paths: local audio and video files, and network streams or online media sources. Those are not the same feature wearing different hats. Local playback depends on your phone’s storage, the file itself, and whatever the app can decode. Network playback depends on a URL, a connection, and whatever sits on the other end of it.

The second path is where expectations tend to inflate. “Online media sources” is a broad phrase, and it does not mean Fermata Auto ships with a catalog, a browser-grade streaming front end, or built-in service integrations. The supplied facts describe support for network streams — the practical reading is that you supply the address and the app attempts to play it. Nothing in the fact data promises more than that.

Two related questions stay open. Whether playback continues with the phone screen locked is not specified in the supplied facts. Neither is whether the app buffers, caches, or reconnects in any particular way. If your use case depends on either behavior, plan to check it yourself rather than assume it. This is a media player with a network input, not a streaming platform.

Fermata Auto Local Video Formats and Subtitles: Verified Support vs. What You Must Test

Here is what the fact data actually confirms: Fermata Auto supports local audio and video files. That is the entire verified statement about local playback. There is no codec list, no container list, no bitrate guidance, and no statement about subtitle tracks — embedded, sidecar, or otherwise. Anyone who tells you the app “supports MKV with external SRT” is going beyond what the project’s supplied facts establish.

The gap is compounded by the missing release metadata. The exact latest version number and release date are unknown, APK size is unknown, and the minimum Android version is unknown. That matters because format behavior is exactly the kind of thing that changes between builds. A codec that works in one release can regress in the next, and without a version number you cannot anchor a compatibility claim to anything stable. Any format list you find online is, at best, a snapshot of someone else’s build.

The open-source license offers a real path around this, but it is a slow one. Because the code is publicly available, someone with the inclination can read the media pipeline and determine what it actually handles. What the supplied facts do not include is an official compatibility matrix — a document the project publishes saying “these containers, these codecs, these subtitle formats.” Without that, code inspection is a research project, not a spec sheet.

So the practical advice is unglamorous: test on your own hardware. Take the specific files you care about — the container, the codec, the audio track, the subtitle file — and try them on your own head unit before you build a routine around them. Subtitle rendering in particular is worth testing early, since a video that plays fine but drops its subtitles is a different experience from one that does not. Assume nothing about broad format support, and you will not be disappointed by a file that turns out to be outside whatever the app quietly handles.

Fermata Auto on Wireless Android Auto and Phone Hotspots: What the Project Does and Does Not Confirm

The fact data lists Android Auto integration and playback of local and network media. It does not list wireless Android Auto. That absence is worth stating plainly, because wireless is the setup detail people ask about first and the one most likely to be answered with confident guesses elsewhere. Nothing in the supplied facts confirms that Fermata Auto behaves any particular way over a wireless connection.

Network stream support does imply a data path — the app has to reach a URL somehow, and in a car that usually means the phone’s cellular connection or a hotspot. But “implies a data path” is not the same as “verified to work over your phone’s hotspot while Android Auto runs wirelessly.” The interaction between a hotspot, a wireless head-unit link, and a media stream is exactly the kind of setup where individual devices diverge. The fact data does not describe it, so this article will not pretend to.

There is also the distribution problem sitting underneath all of this. Fermata Auto is not official Google or Android Auto software, and the fact data notes it may require Android Auto developer-mode or unknown-sources settings. Current Google Play availability is unknown. That combination means wireless setup should never be presented as official or guaranteed — not by the project, and not by a review. If a guide promises wireless playback in three steps, it is describing one person’s configuration, not a supported path.

If wireless matters to your setup, treat it as an experiment with a fallback. Have a wired connection available. Expect that the first attempt may not behave the way a forum post described. And keep in mind that any friction you hit is not necessarily a bug in the app — it may simply be the cost of running an unofficial tool against a platform that was not designed to accommodate it.

Fermata Auto During Navigation Prompts, Phone Calls, and Steering-Wheel Input: The Unverified Audio-Focus Gap

Fermata Auto is designed to play media through a car head unit. That is the stated purpose, and it is all the fact data says about how the app interacts with the rest of the car. Audio focus — the mechanism that decides whether a navigation prompt ducks the music, pauses it, or gets buried under it — is not specified. Neither is behavior during an incoming phone call. These are the details that separate a media player that feels integrated from one that feels bolted on, and the supplied facts are silent on all of them.

The same silence applies to controls. Whether steering-wheel buttons, head-unit knobs, or on-screen transport controls behave sensibly during video playback is unverified in the fact data. It is reasonable to expect basic play and pause to route through Android Auto’s media interface, since that is the surface the app is built against. It is not reasonable to assume anything beyond that, particularly for video, where the platform’s assumptions about what a driver should be doing are already strained.

Because Fermata Auto is not an official Google or Android Auto app, there is an extra layer of uncertainty. The fact data notes that it may require developer-mode or unknown-sources settings, and settings friction of that kind can affect how interruptions and controls are handled. An unofficial app can work perfectly and still sit slightly outside the platform’s normal behavior. When something odd happens during a call or a turn instruction, the cause may be the app, the head unit, or the seam between them.

All of this has to be framed around use. Video playback in a car can be unsafe or illegal depending on local rules, and that constraint shapes which control behaviors even matter. If you are parked or riding as a passenger, a slightly awkward pause behavior is an annoyance. If you are driving, it is irrelevant, because the video should not be running. Test interruption behavior in a parked car, and treat anything you learn as applying to that context only.

Fermata Auto Is Not a Netflix/Disney+ Workaround: DRM Streaming as an Unverified Use Case

This is the misconception that sends the most people to the wrong app. The fact data lists local media plus network streams and online media sources. It does not confirm Netflix, Disney+, or any DRM-protected playback. Those are different technical problems: a stream URL is one thing, and a service that authenticates a session, negotiates a license, and enforces output protection is another. Nothing in the supplied facts says Fermata Auto does the second.

There is a structural reason to be skeptical beyond the missing facts. Fermata Auto is not an official Google or Android Auto app, so DRM service integration is not a promised capability — not by the project, not by the platform, and not by anyone reviewing it honestly. Streaming services generally do not extend playback to unofficial clients, and an app that is not on the platform’s official footing has no standing to expect it. If a video plays through Fermata Auto, it is far more likely to be a plain network stream than a licensed, protected title.

So the guidance is direct: if your goal is Netflix, Disney+, or any other DRM streaming service in the car, Fermata Auto is the wrong tool and you should look elsewhere. The same applies to anyone who wants a subscription service’s catalog on the head unit. This app is aimed at people with their own files and their own stream addresses, and the fact data supports nothing broader.

One privacy note belongs here rather than in a separate section. No official privacy policy was verified for Fermata Auto. The app is open source, so its code can be inspected, which is a meaningful check. But network playback features may contact user-provided stream URLs — meaning the addresses you enter are part of the app’s behavior, and where they point is your responsibility, not something the project has documented in the supplied facts.

Fermata Auto’s Distribution Reality: GitHub Is the Official Source

The official site listed for Fermata Auto is its GitHub repository, github.com/AndreyPavlenko/Fermata. That is the source this article points to, and it is the only one the fact data supports. Current Google Play availability is unknown — not confirmed present, not confirmed absent. Anyone stating flatly that the app is or is not on the Play Store is going beyond the verified record, and anyone treating a Play Store listing as the canonical version has the distribution model backwards.

This is also where the root question gets settled, at least partially. The fact data lists no root requirement and no unlocked-bootloader requirement. What it does list is that the app may require Android Auto developer-mode or unknown-sources settings. Those are two very different levels of intervention. Enabling developer mode is a toggle; rooting is a rebuild of your phone’s security model. Correcting the misconception matters, because people who assume root is mandatory never try the app at all.

Third-party mirrors and aggregator sites are a separate question, and the honest answer is that the official project page is the only source with any accountability behind it. Sideloaded APKs redistributed by unknown parties carry whatever the redistributor put in them. If Fermata Auto does not appear in Android Auto after installation, that is a known consequence of running an unofficial app against a platform that does not officially recognize it — not evidence that you need a different mirror or a deeper modification.

The practical upshot: get the app from the project’s own repository, expect to change a setting or two, and do not expect the update cadence of a Play Store app. Version tracking is genuinely unknown here, so “am I on the latest build” is a question you will have to answer by checking the repository rather than by waiting for an update prompt.

One Head Unit Is Not Every Head Unit

Android Auto is not a single uniform runtime. It runs across a wide range of head units from different manufacturers, with different firmware, different screen sizes, and different levels of cooperation with apps the platform does not officially bless. The fact data does not claim Fermata Auto works identically everywhere, and no honest review should. A setup that behaves well in one car can behave differently in another, and the difference may have nothing to do with the app.

Some of that variability is baked in. Owners of cars with locked Android Auto head units that block custom apps are a group the app simply cannot serve, regardless of how well it is built. That is a hardware and firmware constraint, not a software bug, and no amount of configuration will route around it. If your head unit refuses to surface unofficial media apps, Fermata Auto is not going to change that.

Two specific questions land here because they are head-unit questions rather than app questions. Whether Fermata Auto works with Android Auto’s Coolwalk split-screen interface is not addressed in the supplied facts. Neither is how the app presents itself in a multi-window layout, or whether video renders correctly at whatever aspect ratio your display uses. These are exactly the details that vary by unit, and they are exactly the details the fact data does not cover.

The useful posture is to treat any report — including a positive one — as specific to the hardware it came from. Read other owners’ experiences as a map of possibilities, not a guarantee. Then verify on your own display, in your own car, with your own files.

Verdict

Fermata Auto is worth covering because it does something the platform does not: it brings open-source media playback, including local video and user-provided network streams, to Android Auto. It is free, its GPL-3.0-only license means the source can be inspected, and it adds playback options that Android Auto does not normally offer. Those are real advantages, and they are the reason the project has an audience.

It is also an unofficial tool with a thin verified record. The latest version, APK size, minimum Android version, and current Google Play availability are all unknown. There is no official compatibility matrix for codecs, containers, or subtitles. Audio-focus behavior during navigation prompts and calls is unspecified. Wireless Android Auto behavior is unspecified. None of that makes the app bad; it makes it a test-first proposition, and the testing happens on your hardware with your files.

Who it is for: Android users who are comfortable sideloading an APK from the project’s GitHub repository, who accept enabling Android Auto developer mode or unknown-sources settings, and who want to play their own local media or their own stream URLs through a head unit. It also suits people who value being able to read the source code of a car app before trusting it with a network address.

Who it is not for: iPhone users expecting CarPlay support, which this app does not provide. Anyone hoping to watch Netflix, Disney+, or other DRM-protected services — the fact data confirms no such capability, and the structural case against it is strong. Drivers who want legal, distraction-free video while the car is moving, which is a category that should not exist. People who want a simple phone-screen mirroring tool, since Fermata Auto is a media player, not a mirror. Users who expect official Google Play updates and support. And owners of cars with locked head units that block custom apps, for whom no configuration will help.

If you fit the first group, the app is a reasonable thing to try, sourced from the official repository, with your expectations set to “verify, don’t assume.” If you fit the second, save yourself the afternoon.

Pros

  • Open-source software with publicly available source code
  • Adds media playback options that are not normally available in Android Auto
  • Free to use

Cons

  • Not an official Google or Android Auto app
  • May require Android Auto developer-mode or unknown-sources settings
  • Video playback in a car can be unsafe or illegal depending on local rules
Download from the official source

The link goes straight to Andrey Pavlenko. We do not host app files.

Open official page →

Frequently asked questions

Is Fermata Auto free?

The recorded pricing model is Free (open source).

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/AndreyPavlenko/Fermata.

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.