# Fossify Phone Review: A Private Open-Source Android Dialer

> Fossify Phone is an Android call manager written in Kotlin, with a phonebook, number blocking, and multi-SIM support. It suits users seeking an ad-free dialer distributed under GPL-3.0, but its documentation does not explain permissions, device compatibility, or build procedures in enough detail for a technical evaluation.

**FossifyOrg/Phone** — A handy phone call manager with phonebook, number blocking and multi-SIM support

- Repository: https://github.com/FossifyOrg/Phone
- Website: https://www.fossify.org
- Stars: 1,404 · Forks: 226
- Language: Kotlin
- License: GPL-3.0
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/fossifyorg-phone

## Why Fossify Phone Replaces a Basic Android Dialer

Fossify Phone targets Android users who need more call control than a bare keypad and recent-calls screen. The repository description identifies concrete responsibilities: managing calls, maintaining a phonebook, and blocking numbers. It also says the application supports multi-SIM devices, making it relevant to people who carry more than one mobile line or want to keep work and personal numbers within one call manager.

The application is presented as a FOSS dialer, with source code published under the GPL-3.0 license. The README links to Google Play, F-Droid, and IzzyOnDroid, so the documented acquisition paths are app distributions rather than a proprietary customization program. It also states that the app is free of ads and intrusive permissions, but it does not enumerate the Android permissions requested by the app. That omission matters because access to contacts, call logs, or phone state is central to a dialer's operation, even when the application is open source.

Fossify Phone is therefore aimed at users who accept an Android-native telephone interface but place source availability and control over ads at the center of their selection. It does not present itself as a cross-platform softphone or a desktop calling client. The visible scope remains conventional Android call management, with the stated additions of blocking and multi-SIM handling.

## Kotlin Android Structure and Build Surface

The repository identifies Kotlin as its primary language. Its top-level layout follows a conventional Android application structure: `app/` contains the application module, while `build.gradle.kts`, `settings.gradle.kts`, and `gradle.properties` define the Gradle build. The repository also includes `gradlew` and `gradlew.bat`, which provide wrapper launchers for Unix-like and Windows environments respectively. Configuration for static analysis appears in `detekt.yml`, while `lint.xml`, `.editorconfig`, and `.gitignore` cover linting and repository hygiene.

That layout gives a prospective contributor several concrete places to inspect. Android-specific resources, manifests, Kotlin code, and packaging configuration should be found beneath `app/`, although the README does not walk through their internal organization. Release metadata and screenshots are stored under `fastlane/metadata/android/en-US/`, which indicates that store-facing copy and images are part of the repository rather than generated entirely outside version control.

Open-source distribution can make code review and reuse possible, but this repository listing alone does not establish which Android versions it supports, whether it uses AndroidX, or what dependency versions are pinned. Those points would need confirmation in `app/` and the Gradle files. The available documentation establishes that Android code and build metadata are public. It does not provide a technical architecture diagram or explain whether call handling, storage, and filtering run through separate components.

## Obtaining Fossify Phone Without Undocumented Build Flags

The README does not provide installation commands or document how to build an APK. It directs readers to Google Play, F-Droid, and IzzyOnDroid through named download links. A new user can therefore obtain the published application from one of those channels, but the README does not say which Android versions are supported, whether device installation is required, or whether release signatures are the same across stores.

The presence of `gradlew` and `gradlew.bat` confirms that Gradle wrappers exist in the repository. It does not confirm a supported local build command, required Java version, Android SDK level, or release configuration. Inventing a command at this point would be misleading. Contributors should first read `CONTRIBUTING.md` and `keystore.properties_sample`, then inspect `settings.gradle.kts` and `build.gradle.kts` for the actual toolchain and signing expectations.

For a first real use, install the published app from one of the documented stores and open it as the phone-management application on an Android device. The repository description indicates that the relevant first workflows are entering or accessing contacts, placing calls, configuring blocked numbers, and working with multiple SIMs. The README supplies screenshots but does not describe each menu or confirm whether the app can become Android's default phone application. Users who require exact setup instructions will find the public distribution links useful but the operational documentation thin.

## Multi-SIM and Call Filtering Trade-offs

Multi-SIM support is the most distinctive feature named in the repository description. A dialer that understands multiple SIMs can reduce the friction of choosing a line for each call, especially on phones that maintain separate carrier profiles. However, the README does not document whether users can assign contacts and blocked numbers per SIM, whether calls can be placed from secondary lines, or whether every feature works on every supported handset. Carrier and device implementations of Android telephony can vary, so multi-SIM is also an area where a broad feature label needs device-level verification.

Number blocking provides a more direct form of call management, but the documentation does not specify whether blocking covers incoming calls only, whether the block list can contain spaces or international formats, or whether blocked calls can be reviewed later. No claims about spam detection or automatic call classification should be inferred from the word "blocking."

These constraints make Fossify Phone a reasonable candidate for users who want manual filtering and explicit SIM selection. It is less suitable for administrators who need documented policy sync, carrier-specific provisioning, or a published matrix of supported devices. The feature names establish intent, not the full behavior of each Android telephony backend.

## Privacy Claims, GPL-3.0, and Review Boundaries

The strongest documented benefit is source availability. The README invites users to review the code on GitHub, and the repository publishes its application under GPL-3.0. That license grants broad rights to use, copy, modify, and redistribute the covered software, subject to its terms. The repository also includes a `LICENSE` file. This is relevant to organizations that need to inspect source rather than accept only a compiled store package.

Source visibility does not by itself answer every privacy question. The README uses broad claims about privacy and data protection, yet it does not list requested permissions, explain whether call or contact data leaves the device, describe analytics, or identify network endpoints. The repository topics contain no analytics claim either. A technical buyer should inspect the Android manifest under `app/`, dependency declarations in the Gradle files, and any networking code before treating the marketing wording as a complete data-flow account.

The README also states that the interface is customizable, including themes and functional preferences. It does not document individual settings, so customization should be understood as a stated product area rather than a catalog of verified options. Similarly, claims about efficient resource use are not backed here by battery measurements or implementation notes. Open source permits independent inspection, but the documentation does not supply measurements from which to validate those claims.

## Release History and the Cost of Following Changes

The repository is not archived, and the last push was on 2026-10-13. Recent releases include 1.10.0 on 2025-12-16, 1.11.0 on 2026-01-31, and 1.11.1 on 2026-02-03. This history shows several releases over a short period, including a patch-level update after version 1.11.0. It does not, however, document migration notes, Android compatibility changes, database upgrades, or behavioral differences for those versions.

For users, adopting the application through an app store reduces the need to manage its Gradle build directly, although the README does not state which store carries the newest version or how update prompts are handled. For contributors or organizations that build Fossify Phone themselves, the `app/`, `fastlane/`, and Gradle files are the relevant areas to inspect when a release changes. The source license allows modification and redistribution under GPL-3.0 obligations, but downstream packaging and distribution should be reviewed against the actual license and included source requirements.

The upgrade cost cannot be reduced to a claim that the app is "lightweight." The repository supports ongoing code inspection, but it does not document release procedures, migration compatibility, signing requirements, or a formal support policy for Android versions. Those omissions are especially relevant to a telephone application that may interact with system contacts, SIM state, and call permissions.

## Conclusion

Fossify Phone is a reasonable adoption candidate for an Android user who wants a free dialer with call management, blocking, and multi-SIM features and who accepts reviewing an app whose README does not document detailed permissions or compatibility. It is a poor fit for someone who needs documented migration procedures, a reproducible build guide, or clear assurances about device and carrier behavior. Review `app/`, the manifest configuration, and the `CONTRIBUTING.md` build guidance first, then verify the current APK through one of the distribution channels named in the README.

## FAQ

### Does Fossify Phone support blocking phone numbers?

Yes. The repository description explicitly lists number blocking as a phone-call management feature. It does not document which call types can be blocked or provide instructions for configuring the block list.

### Does Fossify Phone work with multiple SIM cards?

The repository description states that Fossify Phone supports multi-SIM operation. The README does not list supported devices or explain SIM-specific behavior in detail.

### Where can I download Fossify Phone?

The README links to Google Play, F-Droid, and IzzyOnDroid. It does not provide an APK command or document a local build procedure.

## Sources

- [FossifyOrg/Phone on GitHub](https://github.com/FossifyOrg/Phone)
- [License: GPL-3.0](https://github.com/FossifyOrg/Phone/blob/main/LICENSE)
- [Project website](https://www.fossify.org)
- [README](https://github.com/FossifyOrg/Phone/blob/main/README.md)
- [Releases](https://github.com/FossifyOrg/Phone/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/fossifyorg-phone