Someone is bringing Fedora Linux to phones, and it is not Red Hat

A group of Fedora community contributors has been quietly working on a project to put Fedora Linux on smartphones, and the most interesting part of the story is who is not driving it. The project is not a Red Hat initiative. It is not a corporate moonshot. It is a small group of volunteers who looked at the Linux phone ecosystem and decided that the missing piece was a clean, well-supported mobile distribution, not a new app store or a new UI shell.

The result is a project that has been generating interest on the Fedora discussion lists and on the Linux-on-phones forums for the last few months. I have been following it loosely since the first public build was announced, and the approach is more disciplined than most of the previous attempts at this space.

Why phones, and why now

Linux on phones is not a new idea. Ubuntu Touch (the mobile continuation of Canonical’s phone OS), postmarketOS (a community project that extends Alpine Linux to older smartphones), Plasma Mobile (a touch-friendly interface built on KDE software), and Mobian (Debian for mobile devices) have all tried to do this in the last ten years. Each has a small, committed user base. None has reached a place where a non-technical user could pick up a phone and use it as a daily driver.

The reason is the gap between “runs Linux” and “works as a phone.” A modern smartphone is not just a CPU and a screen. It is a tightly integrated stack of modem firmware, GPU drivers, camera pipelines, audio routing, and power management. Most of that stack has to be reversed and rebuilt for a new operating system, and most volunteer projects run out of engineering hours before they finish the lower layers.

What the Fedora-on-phones project is doing differently is starting from a distribution that already has the upper layers in good shape (Fedora’s package management, security model, and contributor base) and tackling the hardware enablement as a separate, scoped problem. The team is not trying to make every phone work. They are picking a small set of devices, getting them to a stable state, and expanding from there.

What is actually shipping

The current focus is a small list of devices where mainline Linux support (the upstream kernel that all distributions share, as opposed to vendor-modified forks) is already in reasonable shape. The Pine64 Pro, the OnePlus 6, and a few of the older Pixels are on the supported list. The team is not promising that any flagship phone will work, and the marketing is honest about it.

The user experience is a GNOME-based shell (the default Fedora desktop adapted for touch and a phone-sized screen) with the Fedora package repository as the software source. There is no separate app store. Apps are installed the same way you install them on Fedora desktop, with dnf (Dandified Yum, Fedora’s package manager) or a graphical package manager on top of it.

That choice has trade-offs. It means the catalog of mobile-first apps is small, because most of what people want on a phone is a web app or a desktop app. It also means the user gets the same software, the same security updates, and the same packaging model as Fedora desktop. For a Linux user, that is a feature. For a non-technical user, it is a hurdle.

Why Red Hat is not driving it

Red Hat’s official position on phones has been hands-off for years. The company funds Fedora as a community project, but mobile is not a strategic priority. The Fedora-on-phones effort is happening because the Fedora community has the contributors and the infrastructure, not because anyone in the corporate sponsor chain decided that phones were the next big bet.

That distinction matters. The project can move at the speed of a community, ship experimental builds, break things, and recover. It does not have to defend a product roadmap or a quarterly revenue target. It also does not have the resources of a corporate mobile effort, which is why the supported device list is short.

I find this reassuring. The Linux desktop survived and grew because the people who cared about it built it on their own time and on their own terms. The mobile effort is following the same pattern, and that is the pattern that has worked before.

Trade-offs

The project is not for everyone. The supported device list is small, and the user experience is closer to “Linux desktop that happens to run on a phone” than to “phone that happens to run Linux.” If you are coming from iOS or Android, the gap is real. App notifications, push delivery, and the camera experience are not at parity with the mainstream platforms, and the project is honest about it.

The other trade-off is volunteer risk. The team is small, the project is young, and a community effort of this scope depends on a handful of people staying engaged. If the lead maintainer moves on, the project could stall. That is the same risk that every small open-source project carries, and it is the reason I always test a new project on a spare device before recommending it to anyone who depends on their phone for work.

There is also a real risk that the project hits a hardware wall. Mainline Linux support for the modem chipsets in modern phones is uneven, and the parts of the system that depend on proprietary firmware (modem, GPU, camera) will need vendor cooperation that may or may not come. The community has done impressive work on the open side of that equation, but the closed side is a moving target.

What I would tell past me

If I could send a message back to the version of me who was excited about Ubuntu Touch in 2013, I would say four things.

• The phone is not the hard part. The hard part is the modem, the camera, and the long tail of small hardware quirks that do not show up until you actually use the device as a phone.
• A small, well-supported device list beats a long, broken one. A phone that mostly works on three devices is more useful than a phone that boots on thirty and crashes on the apps you actually use.
• A community-driven mobile Linux needs you to be the maintainer of your own experience. You will install nightly builds, file bug reports, and sometimes patch the kernel. If that does not sound like fun, this is not your project.
• Watch the people, not the press releases. The Fedora phone effort has momentum because a handful of specific people are doing specific work. Look at the commit history, not the headlines, before you bet on the project.

Bottom line

Fedora on phones is the most disciplined community mobile Linux effort I have seen in years. The team is not promising more than it can deliver, the supported device list is short on purpose, and the dependency on Fedora’s existing packaging and security model removes a class of problems that killed the earlier attempts. It is not ready to be anyone’s daily driver, but it is the project I would point a tinkerer at if they asked me “which Linux phone should I try in 2026?” The answer is this one, with the caveat that you should expect to debug.