News: 0179795022

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

FSF Announces the LibrePhone Project (phoronix.com)

(Wednesday October 15, 2025 @11:20AM (BeauHD) from the f-is-for-freedom dept.)


The Free Software Foundation (FSF) has [1]launched the LibrePhone Project , an initiative to create a fully free and open-source mobile operating system that eliminates proprietary firmware and binary blobs. From the [2]FSF :

> "Librephone is a new initiative by the FSF with the goal of bringing full freedom to the mobile computing environment. The vast majority of software users around the world use a mobile phone as their primary computing device. After forty years of advocacy for computing freedom, the FSF will now work to bring the right to study, change, share, and modify the programs users depend on in their daily lives to mobile phones.

> ...

> Practically, Librephone aims to close the last gaps between existing distributions of the Android operating system and software freedom. The FSF has hired experienced developer Rob Savoye (DejaGNU, Gnash, OpenStreetMap, and more) to lead the technical project. He is currently investigating the state of device firmware and binary blobs in other mobile phone freedom projects, prioritizing the free software work done by the not entirely free software mobile phone operating system LineageOS."

The project site can be found [3]here .



[1] https://www.phoronix.com/news/FSF-LibrePhone-Project

[2] https://www.fsf.org/news/librephone-project

[3] https://librephone.fsf.org/



Interesting Idea (Score:5, Insightful)

by Registered Coward v2 ( 447531 )

A very interesting technological challenge. I suspect phone manufacturers will attempt to find ways to block installing it on their devices, given the phone itself is not the only revenue stream but also user data. A cat and mouse game will ensue, much like Apple with jailbreaks. Good luck to them, it would be a great plus for users.

Re:Interesting Idea (Score:5, Interesting)

by AleRunner ( 4556245 )

This is 100% going to require dedicated / custom hardware no matter what. Most phones have multiple important devices that need binary blobs. Most often that includes the cellular radio, so a normal phone with this system is going to be a brick with this.

There have, through history, been a bunch of projects for better / more free / more user owned phones. Fairphone, Purism / Librem / PinePhone and several of them delivered hardware. So far that's always been noticeably more expensive for worse hardware, but it shows it can and will be done. Now that Google looks like they will close off the hardware support for Pixel phones in AOSP, the GrapheneOS project are talking about doing a phone with an OEM so maybe we will end up with something much more competitive soon.

This kind of project can give a focus for getting one of those phones you more or less own actually over the line to the state where you really own it and have all the drivers.

Re:Interesting Idea (Score:5, Informative)

by AmiMoJo ( 196126 )

The issue is the modems. If the firmware can be modified, it can be made to exceed legal transmission power limits, or behave badly on the network in a way that affects other users.

The same is true of WiFi, but the damage tends to be more limited. Screwing up a cell tower can affect thousands of people.

Re: (Score:3)

by Mononymous ( 6156676 )

So it's illegal to run such a modified firmware. That shouldn't stop the FSF from releasing free firmware.

Re: (Score:3)

by AmiMoJo ( 196126 )

True, but it will stop the hardware vendors helping them. They typically have a binary blob, and maybe it has to be validated with a signature before loading. Blob itself is probably encrypted to make reverse engineering difficult.

Cellular and WiFi modems are complex DSPs. Figuring out how they work and re-writing the stack from scratch is a huge undertaking. I'm just not sure it's a realistic goal for the FSF. Their other attempts to open up less complex systems haven't exactly had stellar results.

Re: (Score:2)

by serafean ( 4896143 )

It is kind of accepted in Libre software circles that connecting the modem through USB is "good enough" to keep the rest of the device Libre.

Re: (Score:2)

by TheCRAIGGERS ( 909877 )

Software defined radios already exist in various form factors and powers. I saw one in a walkie-talkie form factor a year or so ago with a range listed in miles and it could operate in cell bands. Point is, such things already exist in the mass market, and they're pretty dang cheap.

Re: (Score:2)

by AmiMoJo ( 196126 )

Yes, and it's a developing issue. But also we aren't quite at the stage where people can download an app to their phone and screw up the local cell tower. If we were, you can be sure something would be done about it.

In fact when someone found you could screw with Bluetooth quick pairing using a Flipper Zero, it was patched pretty quickly.

Re: (Score:2)

by TheCRAIGGERS ( 909877 )

You're making a rather large assumption there. I, for one, highly doubt that you could just "download an app to their phone and screw up the local cell tower". In fact, as an end user, I wouldn't even want this.

What the FSF is proposing (and hopefully eventually succeeding) is making some open firmware. Just because the firmware code is open doesn't mean every app (even if granted root access) in userspace will have unfettered access to everything the hardware radio could potentially do. There should be saf

Re: (Score:2)

by thegarbz ( 1787294 )

> I suspect phone manufacturers

What phone manufacturers? Locking down bootloaders is a thing some do and some don't. Non-manufacturer controlled Operating Systems do exist and are in use on many devices. Additionally some manufacturers exist to provide open options to customers such as FairPhone.

Nothing in the mobile world changes with this announcement. If there's a cat and mouse game to be had then it is already ongoing. An example of everything you list as a problem is right there in TFS, LineageOS which itself has roots that date bac

Re: (Score:2)

by DesScorp ( 410532 )

> I suspect phone manufacturers will attempt to find ways to block installing it on their devices

I suspect they'll just ignore it because no one will want to actually use it.

The problem with these ideology-based projects is that they have no mass appeal. No one out there in userland gives a flying fuck about free software. They want the latest apps. They want a seamless experience. Especially Gen Z who were raised on mobile devices. Tell them that they should give up iPhones and Android phones because "Free as in Freedom is the right way", and they're going to look at you like you're a tentacled thing

get over yourself its called android no google (Score:2)

by johnjones ( 14274 )

so how about funding

[1]https://grapheneos.org/ [grapheneos.org]

[1] https://grapheneos.org/

Re: (Score:2)

by quenda ( 644621 )

GrapheneOS is not GPL, sadly.

Re: (Score:2)

by AleRunner ( 4556245 )

The main body of the OS inherits from AOSP so you are right, but the kernel is still Linux so GPLv2. That's where the main body of work for LibrePhone would be.

Re: (Score:2)

by AleRunner ( 4556245 )

> so how about funding

GrapheneOS doesnt' have the same aim. They happily run on Pixel hardware with binary blobs. In principle this project could be good for though because if the binary blobs can be eliminated then it would be possible to provide hardware support after Google has given up, so GrapheneOS could extend the lifetime of devices considerably.

Re: (Score:2)

by bill_mcgonigle ( 4333 ) *

They're talking about LineageOS. Think Graphene but it doesn't just run on Google hardware. Over a hundred devices and they just added mainline kernel and qemu support so it potentially runs on thousands of devices.

Sadly with less hardening. I wish Lineage would take some Graphene patches. The crazy thing is Lineage descended from Cyanogenmod which had many of these patches!

Re: (Score:2)

by ChunderDownunder ( 709234 )

This just sounds like rebranding the Replicant project?

Unless FSF are planning on partnering with hardware projects such Purism, Pinephone or Fairphone, I can't see them making any headway over what postmarketOS has achieved.

Re: (Score:2)

by AleRunner ( 4556245 )

Those projects almost all only physical address hardware. This project is about replacing some binary blobs with free software and seems more interested in Androide based systems like LineageOS and similar systems than Linux base systems like postmarketOS. LineageOS already works, so just getting it working on any modern hardware without any binary blobs would be a great achievement. PostmarketOS could then copy that setup and and run on the same hardware, which would also be great.

Best of luck to them (Score:2)

by Cley Faye ( 1123605 )

It's really hard these day to be positive about things. I wish them the best of luck. Having a working, usable, open-source based phone sounds great. However, I can't shake off the few limitations that are likely to make this not viable for most people, beyond a general lack of interest in openness:

- support for banking/govt. apps that may or may not become mandatory in the near future. Not having my bank app on Android makes doing anything hard already

- support for the aforementioned apps that are likely

Re: (Score:3)

by Viol8 ( 599362 )

"Not having my bank app on Android makes doing anything hard already"

You do realise you can access almost all banks via the web too? And IME the web page is often more functional than the app which is why I don't bother with the banking app. Sure , using a browser is a bit more faff but I don't have to worry about possible theft of my money if my phone is unlocked when lost/stolen as I clear down all cookies on the browser.

Re: (Score:2)

by greytree ( 7124971 )

My banking app doesn't work on my phone any more because they choose not to support the old version of Android it runs ( and I don't want to get a new phone because I hate phablets because I am not a sheep ).

So I have to use the bank's web app.

Which only works with a hardware authentication device, which I have to have with me to use it.

Which is very annoying.

Re: (Score:2)

by FudRucker ( 866063 )

Yup, I can access my bank through almost any browser on Apple, Linux or Windows

Re: (Score:3)

by itsme1234 ( 199680 )

The number of things nowadays for which you need a phone app is staggering, from banking to credit card or even brokerage apps where the web interface is gimped or it just doesn't exist to all shop coupon apps, DHL locker apps, even health insurance and oh, this is a nasty one, the apps for charging your e-vehicle.

What's more, in the EU (and possibly some associated states from around too) you need to 2FA authorize the transactions in a way where you can see the amount and where it's going. That means none

Re: (Score:2)

by Viol8 ( 599362 )

"this is a nasty one, the apps for charging your e-vehicle"

If ICE vehicles had just been invented in the last few years I can guarantee that there'd be a different app not only for each oil/filling station company, but probably different sub apps for whether you need to fill up with petrol or diesel.

Re: (Score:3)

by John Allsup ( 987 )

Logging in on the web to my bank requires generating a security code using the app.

Re: (Score:1)

by mechanyx ( 960689 )

"almost" is doing a lot of work there. My bank info and their payments systems can only be accessed via their phone app.

My reaction to reading this news was that this isn't really viable if anyone using this has to have a second "normal" phone to function in society.

Re: (Score:2)

by AleRunner ( 4556245 )

All of my banking apps (and I have a bunch) accept working on GrapheneOS. Even if Librephone doesn't themselves attempt to pass verification then a GrapheneOS build for whatever hardware they support would be able to work with their kernel drivers.

Re: (Score:2)

by coofercat ( 719737 )

I have no idea how this pans out, but I'd imagine their first phone won't be a smart phone. They've got far too many 'low level' issues to work out first, and even getting hardware which doesn't need a manufacturer's binary blob to make it work is already a significant challenge. The subject of apps, app stores and operating systems will likely come later.

As others have said, the low level radios and modems have the capacity to be a real problem for networks. Most networks are held together with sticky tape

Re: (Score:2)

by Tokolosh ( 1256448 )

Correct, this is the acid test. Can I do everything on a LibrePhone that I could before? NFC credit card tap-to-pay, banking, transit apps, government ID/drivers license, TFA?

All power to FSF and good luck opposing the Leviathan.

Relationship to Replicant and other projects ? (Score:1)

by rzr ( 898397 )

[1]https://en.wikipedia.org/wiki/... [wikipedia.org] Replicant is sponsored and supported by the Free Software Foundation,[7] which also hosts Replicant's source code.[28][29]

[1] https://en.wikipedia.org/wiki/Replicant_(operating_system)

Re:Relationship to Replicant and other projects ? (Score:4, Informative)

by AleRunner ( 4556245 )

The announcement on the FSF web site explicitly mentions Replicant and on the Replicant web site they still seem to be alive, but they are targeting different / older hardware. The announcement also mentions that the project sponsor wants to get rid of binary blobs in his LineageOS install.

My understanding: Replicant is a full AOSP distribution with the binary blobs removed. Librephone is a project trying to eliminate binary blobs in the underlying Linux kernel. When Librephone succeeds it will be easier to move Replicant to more devices.

Google is going to lock down Android (Score:3)

by FudRucker ( 866063 )

So no more side loading third party apps, I am now on the hunt for an android phone that isn't under Google's thumb

Re: (Score:2)

by itsme1234 ( 199680 )

> android phone that isn't under Google's thumb

Ironically the main choices I can think of are:

- if DIY a Pixel - they most reliably come with unlockable bootloader, no shenanigans at all to unlock it (and lock it back with your system), have most/all hardware well supported and so on

- if you want something off the shelf from any somehow known entity it can't be something with Google Play (as it comes with all Google's restrictions) so you're mostly down to ... drumroll ... Huawei !!!!!

It is mind boggling that

Re: (Score:3)

by drinkypoo ( 153816 )

> Ironically the main choices I can think of are:

> - if DIY a Pixel - they most reliably come with unlockable bootloader,

No. Google just took the Pixel device trees out of AOSP and is not publishing them elsewhere. Alternate OSes for Pixel devices just died.

Re: (Score:2)

by itsme1234 ( 199680 )

Any more suited alternative? At least you have all the existing code, and access to the device (which is absolutely NOT granted with most manufacturers). I guess you could do Fairphone, but still probably any Pixel from 6 and above (let's say you use one of the previous ones so it's better supported with existing code) would be better than any Fairphone for the foreseeable future.

What hardware are they targeting? (Score:2)

by jonwil ( 467024 )

If they want to create a free-as-in-freedom mobile phone OS of some sort that is actually useful, they will need hardware that the OS can run on (and hardware that you can actually connect to modern mobile networks and use to make calls, send messages, access the internet etc). What hardware are they trying to target?

Will this be like coreboot/libreboot/etc where it only works on old obsolete hardware that you can't easily just go and buy anymore or will it actually be usable on hardware I as a FOSS-loving

Re: (Score:1)

by Narcocide ( 102829 )

The Purism Librem 5 and the Pine64 Pinephone, as well as anything listed as supported currently by Ubuntu Touch and PostmarketOS are probably good candidates for this. You can already use many of these right now with several different Linux distros as the reverse-engineering work has already largely been done, and the phones are already in the wild, people are using them, and some of them are indeed still available for sale new. By and large, they suck compared to the latest iPhone but you can't have everyt

Re: (Score:2)

by DrXym ( 126579 )

This isn't the first time somebody has tried to make a not-android open source phone OS. Firefox OS for example got some initial traction and even sold in some markets. But it died on its ass because the reality is that phone buyers want a phone that runs apps and runs the apps they want - games, banking, streaming etc.

It doesn't matter if some other phone OS is built on open source principles or not, or even if it functionally usable in a limited way. If it doesn't have the apps it sucks.

Here is appropriate phone... (Score:4, Funny)

by zawarski ( 1381571 )

[1]https://skysedge.com/telecom/R... [skysedge.com]

[1] https://skysedge.com/telecom/RUSP/index.html

Sorry... (Score:2)

by Junta ( 36770 )

It's GNU/Hurd or nothing

I look forward to seeing it in 2045 (Score:2)

by DrXym ( 126579 )

Because FSF seems to have a knack for sucking all momentum out of projects and miring them in politics. No doubt the first release will be powered by Hurd and take 5 minutes to boot to a bash prompt.

Tried before, went no where ... (Score:2)

by kbahey ( 102895 )

This has been tired before, and ended no where ...

Anyone remember [1]Openmoko [wikipedia.org] and the hype around it in the Open Source community?

There were also [2]Nokia's Maemo [wikipedia.org] (before Nokia abandoned it and the underlying hand sets after that CEO took over) then the Linux Foundation's [3]MeeGo [wikipedia.org].

I hope this effort succeeds though despite the odds.

[1] https://en.m.wikipedia.org/wiki/Openmoko

[2] https://en.m.wikipedia.org/wiki/Maemo

[3] https://en.m.wikipedia.org/wiki/MeeGo

Wrong Starting Point (Score:2)

by Voyager529 ( 1363959 )

I swear, the FSF has no concept of onramps, incremental victories, or provisional compromises.

Graphene, iode, and /e/OS exist, in addition to LineageOS. Are they "free enough" for the FSF? No, but to argue that the reason these things don't have mass acceptance is because users can't modify their modem firmware is patently absurd. I can appreciate the desire for purity, and a truly Free/Libre software stack from the low-level firmware to the apps, but this is absolutely the wrong starting point.

For starters

Is your job running? You'd better go catch it!