Librephone battles the proprietary binary blob
(2025/10/16)
- Reference: 1760572572
- News link: https://www.theregister.co.uk/2025/10/15/fsf_librphone_vs_proprietary_binary_blog/
- Source link:
To bridge the gap between Android distributions and true mobile phone freedom, the Free Software Foundation (FSF) has launched an initiative called Librephone.
It's not an attempt to build yet another mobile operating system. Rather, the goal is to develop replacements for proprietary blobs – binaries without associated source code – in Android device firmware that limit software freedom technically or legally.
Google's Android operating system and Apple's iOS both limit that freedom through contractual rules and intellectual property rights. While alternative mobile operating systems exist, often distributions based on the Android Open Source Project (e.g., LineageOS), they may contain [1]proprietary blobs related to specific vendors (e.g., Qualcomm). Such blobs, which often handle functions related to networking and wireless communication, are governed by software licenses that limit the sharing or modification of code.
[2]
The FSF says it wants people to have the freedom to inspect, alter, and share the source code for mobile phone firmware and applications.
[3]
[4]
"A lot of work has been done in mobile phone freedom over the years that we'll be building on," said Zoë Kooyman, executive director of the FSF, in [5]a statement . "The FSF is now ready to do what is necessary to bring freedom to cell phone users. Given the complexity of the devices, this work will take time, but we're used to playing the long game."
The aim of the Librephone initiative is to reverse-engineer various proprietary blobs so FOSS versions of the code can be created and used in place of freedom-limiting bits.
[6]
Not everyone wants the FSF seal of approval. The makers of AOSP-based GrapheneOS – which the FSF has [7]declined to endorse – have argued that GNU/FSF approval is not a goal because the FSF's stance on firmware updates is fundamentally insecure.
"We don't want their endorsement since it simply means an OS is insecure," a GrapheneOS administrative account said in [8]a forum post last year. "They even require removing security warnings about insecure out-of-date firmware/microcode because they consider it promoting non-free software. That's scammer behavior. We want nothing to do with it."
[9]Framework flame war erupts over support of politically polarizing Linux projects
[10]Raspberry Pi OS, LMDE, Peppermint OS join the Debian 13 club
[11]Meta will move React to Linux Foundation to address vendor dominance fears
[12]Qualcomm solders Arduino to its edge AI ambitions, debuts Raspberry Pi rival
The Librephone project is backed by FSF board member John Gilmore, who explained in a statement, "I have enjoyed using a mobile phone running LineageOS with MicroG and F-Droid for years, which eliminates the spyware and control that Google embeds in standard Android phones. I later discovered that the LineageOS distribution links in significant proprietary binary modules copied from the firmware of particular phones. Rather than accept this sad situation, I looked for collaborators to reverse-engineer and replace those proprietary modules with fully free software, for at least one modern phone."
With Gilmore's funding, the FSF has hired developer Rob Savoye, who has contributed to various GNU/Linux projects such as GCC, GDB, DejaGNU, Gnash, and Autotools.
Savoye told The Register in an email that initially he intends to focus on binary blobs associated with radio functions, cellular connectivity, Wi-Fi, and Bluetooth. After that, he expects to be looking at GPU functions, and blobs associated with touch screen interaction and media playback.
[13]
He's not sure how long the project will take. "This will be a multi-year effort," Savoye said. "It's impossible to propose a timeline as that's dependent on resources like funding and developers. To really get this done in a reasonable amount of time is going to require developers working in parallel."
Asked whether Google's recently announced plans [14]to limit Android app distribution played a role in the launch of the Librephone project, Savoye said it hadn't.
"My initial discussions with the FSF pre-date that announcement," he said. "John Gilmore and I have talked about this for ages, but it had to wait till I had the time freed up from other work. I'm not trying to build a free mobile OS, just freeing up the low-level layer that controls the hardware. Any of the mobile operating systems would be able to use any replacements for the binary blobs."
Savoye said he expects the most significant technical challenge to be the obstacles smartphone makers have put in place to make reverse engineering difficult.
"For example, I can't even get datasheets on the chipsets," he said. "Then throw in things like Secure Boot, Trusted Computing, and layers of firmware signing. In addition there are also legal issues to be conscious of here in the US, namely the DMCA and FCC regulations. The real challenge is to work around all these issues in a legally conforming way."
For those disinclined to wait, there's the [15]FSF-blessed [16]Purism Librem 5 . ®
Get our [17]Tech Resources
[1] https://wiki.lineageos.org/proprietary_blobs
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://www.fsf.org/news/librephone-project
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[7] https://www.gnu.org/distros/common-distros.html
[8] https://discuss.grapheneos.org/d/14034-gnu-claiming-that-grapheneos-is-partially-non-free/14
[9] https://www.theregister.com/2025/10/14/framework_linux_controversy/
[10] https://www.theregister.com/2025/10/15/raspberry_pi_os_lmde_debian_13/
[11] https://www.theregister.com/2025/10/09/meta_react_foundation/
[12] https://www.theregister.com/2025/10/07/qualcomm_arduino_acquisition/
[13] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[14] https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/
[15] https://www.fsf.org/givingguide/v10/
[16] https://puri.sm/products/librem-5/
[17] https://whitepapers.theregister.com/
It's not an attempt to build yet another mobile operating system. Rather, the goal is to develop replacements for proprietary blobs – binaries without associated source code – in Android device firmware that limit software freedom technically or legally.
Google's Android operating system and Apple's iOS both limit that freedom through contractual rules and intellectual property rights. While alternative mobile operating systems exist, often distributions based on the Android Open Source Project (e.g., LineageOS), they may contain [1]proprietary blobs related to specific vendors (e.g., Qualcomm). Such blobs, which often handle functions related to networking and wireless communication, are governed by software licenses that limit the sharing or modification of code.
[2]
The FSF says it wants people to have the freedom to inspect, alter, and share the source code for mobile phone firmware and applications.
[3]
[4]
"A lot of work has been done in mobile phone freedom over the years that we'll be building on," said Zoë Kooyman, executive director of the FSF, in [5]a statement . "The FSF is now ready to do what is necessary to bring freedom to cell phone users. Given the complexity of the devices, this work will take time, but we're used to playing the long game."
The aim of the Librephone initiative is to reverse-engineer various proprietary blobs so FOSS versions of the code can be created and used in place of freedom-limiting bits.
[6]
Not everyone wants the FSF seal of approval. The makers of AOSP-based GrapheneOS – which the FSF has [7]declined to endorse – have argued that GNU/FSF approval is not a goal because the FSF's stance on firmware updates is fundamentally insecure.
"We don't want their endorsement since it simply means an OS is insecure," a GrapheneOS administrative account said in [8]a forum post last year. "They even require removing security warnings about insecure out-of-date firmware/microcode because they consider it promoting non-free software. That's scammer behavior. We want nothing to do with it."
[9]Framework flame war erupts over support of politically polarizing Linux projects
[10]Raspberry Pi OS, LMDE, Peppermint OS join the Debian 13 club
[11]Meta will move React to Linux Foundation to address vendor dominance fears
[12]Qualcomm solders Arduino to its edge AI ambitions, debuts Raspberry Pi rival
The Librephone project is backed by FSF board member John Gilmore, who explained in a statement, "I have enjoyed using a mobile phone running LineageOS with MicroG and F-Droid for years, which eliminates the spyware and control that Google embeds in standard Android phones. I later discovered that the LineageOS distribution links in significant proprietary binary modules copied from the firmware of particular phones. Rather than accept this sad situation, I looked for collaborators to reverse-engineer and replace those proprietary modules with fully free software, for at least one modern phone."
With Gilmore's funding, the FSF has hired developer Rob Savoye, who has contributed to various GNU/Linux projects such as GCC, GDB, DejaGNU, Gnash, and Autotools.
Savoye told The Register in an email that initially he intends to focus on binary blobs associated with radio functions, cellular connectivity, Wi-Fi, and Bluetooth. After that, he expects to be looking at GPU functions, and blobs associated with touch screen interaction and media playback.
[13]
He's not sure how long the project will take. "This will be a multi-year effort," Savoye said. "It's impossible to propose a timeline as that's dependent on resources like funding and developers. To really get this done in a reasonable amount of time is going to require developers working in parallel."
Asked whether Google's recently announced plans [14]to limit Android app distribution played a role in the launch of the Librephone project, Savoye said it hadn't.
"My initial discussions with the FSF pre-date that announcement," he said. "John Gilmore and I have talked about this for ages, but it had to wait till I had the time freed up from other work. I'm not trying to build a free mobile OS, just freeing up the low-level layer that controls the hardware. Any of the mobile operating systems would be able to use any replacements for the binary blobs."
Savoye said he expects the most significant technical challenge to be the obstacles smartphone makers have put in place to make reverse engineering difficult.
"For example, I can't even get datasheets on the chipsets," he said. "Then throw in things like Secure Boot, Trusted Computing, and layers of firmware signing. In addition there are also legal issues to be conscious of here in the US, namely the DMCA and FCC regulations. The real challenge is to work around all these issues in a legally conforming way."
For those disinclined to wait, there's the [15]FSF-blessed [16]Purism Librem 5 . ®
Get our [17]Tech Resources
[1] https://wiki.lineageos.org/proprietary_blobs
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://www.fsf.org/news/librephone-project
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[7] https://www.gnu.org/distros/common-distros.html
[8] https://discuss.grapheneos.org/d/14034-gnu-claiming-that-grapheneos-is-partially-non-free/14
[9] https://www.theregister.com/2025/10/14/framework_linux_controversy/
[10] https://www.theregister.com/2025/10/15/raspberry_pi_os_lmde_debian_13/
[11] https://www.theregister.com/2025/10/09/meta_react_foundation/
[12] https://www.theregister.com/2025/10/07/qualcomm_arduino_acquisition/
[13] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aPBt1-7OinyyAXz0KuYBIQAAAJA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[14] https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/
[15] https://www.fsf.org/givingguide/v10/
[16] https://puri.sm/products/librem-5/
[17] https://whitepapers.theregister.com/
This will be a multi-year effort
that one in the corner
Whilst the idea is intriguing, can't help feeling that it is going to be limited by the rate of churn in the mobile hardware market: by the time they have support for one device it'll have been declared "obsolete" by the manufacturer.
Whilst this may mean that someone who is really interested in running a Librephone system may be happy with the older model (possibly very happy, if they got a good second-hand deal) it will struggle to appear viable to the many people who insist on riding (close to) the leading edge of phone bling.
Ain't it easier to persuade a SoC manufacturer to make FOSS blobs
williamyf
A small SoC manufacturer could release a mobile SoC sans propiertary BLOBs. Then. all these "free as in freedom" phone projects could rally arround said Small SoC maker, making it strong...
Or perhaps, the market is so limited, that is of no interest even for the smaller of SoC makers...
¿Which is it?
Re: Ain't it easier to persuade a SoC manufacturer to make FOSS blobs
chuckufarley
It's Option C. The IP that distinguishes SOC vendors (and actually most hardware manufactures and designers) is often not that hard for a competitor to reverse engineer and incorporate into their own products provided that the software that drives it is completely open and honest about what it is doing.
God bless them...
...but how many phone models need work?