FadCam: an ad-free Android recorder for background video, screen capture and remote control

What FadCam is for, and who it is not for

FadCam is an Android multimedia recorder built around a single constraint: recording should keep running when the app is not on screen. The README describes it as a "privacy-focused Android multimedia suite" covering background video recording, dashcam use, screen recording with annotations, live streaming over a local network, and remote camera control. The repository is Java, licensed GPL-3.0, and sits inside the FadSec Lab suite, which the README describes as a group of ad-free, privacy-first applications.

The intended users are people who want a camera or screen recorder they can leave running without an account, an ad layer, or a cloud upload. The README lists personal security (dashcam, home monitoring), content creation (annotated screen recording), remote monitoring, and documentation as the ethical cases. That list is doing real work, because the same features support covert recording. The README answers with a caution block: the developers "do not condone or support any unethical or illegal use of this software" and name unauthorized surveillance as misuse.

It is the wrong tool if you need an audited, tamper-evident chain of custody. Nothing in the README or the repository listing describes hashing, signed exports, or an evidence workflow. A PRIVACY.md exists at the top level, which tells you the project has thought about data handling, but that is a policy document, not a forensic one.

How the recording pipeline is put together

The topics list on the repository is the clearest statement of the mechanism: camera2-api, camerax, ffmpeg-android, material-design, screenrecorder. That mix says FadCam is not a thin wrapper over Android's stock capture intent. It uses the modern camera stack (CameraX on top of Camera2) for capture, and it carries FFmpeg for Android, which is what you would reach for if you need muxing, codec choice, or stream output rather than a plain MP4 dump from the system recorder.

The feature list implies three output paths sharing that capture layer. Background video recording writes camera frames to a file while the app is off screen. Screen recording captures the display and adds annotations, which the README calls "professional annotation tools." Live streaming pushes over the local network, and remote camera control accepts commands from another device on that network. Those last two are the parts that make FadCam more than a recorder: the phone becomes a node you can drive, not just a device you press record on.

One structural detail is visible in the repository root and worth reading as a signal. There is a MEDIA3_MIGRATION.md file alongside the README. Android's Media3 stack is the successor to the older ExoPlayer and media session APIs, and a migration note at the top level suggests playback or media session handling is being moved onto it. For anyone evaluating stability, that is a live refactor, not a finished one.

Installing FadCam and making a first background recording

The README does not give a build-from-source walkthrough, so the practical install path is the published distribution. The badges point to F-Droid, the IzzyOnDroid repository, the App Store, and SourceForge, and the package identifier used by those channels is com.fadcam. If you are on Android and want the ad-free build, F-Droid is the channel the project advertises first.

There is a Gradle wrapper in the repository root (gradlew, gradlew.bat, settings.gradle.kts, build.gradle.kts), so a source build is possible, but the README does not document the steps or the required SDK. Treat the source build as an undocumented path.

For a first real use, the sequence the feature list implies is: grant camera and microphone permission, grant storage or media permission so the output file can be written, start a background recording, then turn the screen off and leave the phone alone for a minute. When you come back, the recording should still be running and the file should be present. If it stopped, the cause is almost always an Android background execution limit or a battery optimization setting rather than the app itself, and that is the first thing to check.

The beta channel is the honest limitation

The most concrete limitation is not in the feature list, it is in the version numbers. The three most recent releases are v4.0.0-beta10.6 (2026-08-17), v4.0.0-beta10.5 (2026-08-14) and v4.0.0-beta10.4 (2026-08-11). Those are beta builds of a major version, published days apart. A cadence that tight usually means fixes are landing faster than they can be validated, and it means the 4.0 line is not the stable line.

The repository itself is not archived, and the last push was on 2026-09-20, so development is current. That cuts both ways for an adopter: you get fixes, and you also get churn. If you install from F-Droid and the client tracks the beta channel, an update can change recording behaviour under you.

The second limitation is platform. The README states that FadCam for Desktop is planned, and the App Store badge points at an iOS app, but the repository is the Android project. Anyone reading the feature list and assuming a single cross-platform recorder is reading it wrong. The third is documentation depth: the README is a feature and download page, and it does not document rollback, storage layout, or what happens to an in-progress recording when the process is killed. Those are the questions you will actually have after a failed recording, and the README is silent on them.

FadCam against Android's built-in screen recorder

The obvious alternative is the screen recorder already on the device, or a general-purpose open source recorder distributed through the same F-Droid channel. The difference in approach is architectural rather than cosmetic.

A stock Android screen recorder captures the display and stops there. FadCam's topics list shows CameraX and camera2-api alongside screenrecorder, meaning the same app also owns the camera pipeline, and ffmpeg-android, meaning it owns the encoding and muxing step. The consequences are concrete. Because it controls encoding, it can offer codec and container choices the system recorder does not expose. Because it owns the camera session, it can record the camera while the screen is off, which the system recorder cannot do by design. And because it adds local streaming and remote control, the phone can be operated from another device on the network instead of by hand.

The trade is scope. A system screen recorder has no background camera session to keep alive, so it does not fight Android's background execution limits and does not need battery optimization exemptions. FadCam does, and that is the price of the feature set. If all you need is an occasional screen capture, the built-in tool is less likely to be killed mid-recording.

Licence, upgrades and what a fork inherits

FadCam is GPL-3.0. For most users that changes nothing: you can install and run it freely. For anyone modifying and redistributing it, the copyleft terms apply to the distributed work, and the source must be made available under the same licence. This is not legal advice; read LICENSE in the repository root and, if you are shipping a product, get proper counsel.

The licence does not cover the project's funding model. The README links a Patreon shop offering what it calls "Unlock FadCam Pro with lifetime access." That is a separate commercial arrangement layered on top of a GPL-3.0 codebase, and it is worth understanding which Pro features live in this repository and which do not before you plan around them. The README does not spell that split out.

Upgrade cost is the beta cadence. Three releases inside a week means you should expect to update often and to re-verify recording behaviour after each update, particularly background recording, which depends on permissions and battery settings that a new build can reset. Budget for that rather than assuming an install-and-forget tool.

Editorial conclusion

Adopt FadCam if you want an ad-free, GPL-3.0 Android recorder that keeps recording with the screen off and can be driven from another device on the same network, and if you accept that the newest published builds are beta releases. Do not adopt it as a compliance or evidence system: the README carries a misuse disclaimer, the repository holds a PRIVACY.md but no documented chain of custody, and the Android app is the only target, with the desktop build described as planned. Before relying on it, install the F-Droid build, record once with the screen off, once with the screen on, and once through the remote control, then confirm the exported file plays and that storage permissions and Android background limits are not cutting the recording short.

Frequently asked questions

Official sources

1. anonfaded/FadCam on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases