This presentation explores the 20-year journey of Linux on smartphones, arguing that while Android-based solutions like GrapheneOS offer privacy, they remain tethered to proprietary components and Google's increasing control via "Play Services." The speaker advocates for truly open-source alternatives, tracing the history from early projects like OpenMoko and Maemo/MeeGo to more recent efforts such as Ubuntu Touch, PinePhone, Librem 5, and PostmarketOS.
Current progress is highlighted, particularly PostmarketOS's success in porting Linux to existing Android hardware without proprietary blobs, though challenges remain with drivers for components like cameras and GPS. The "Frankenstein" approach, where Linux distributions leverage Android kernels and proprietary drivers (standardized by projects like Halium), is presented as a necessary interim step towards fully open systems. The speaker shares personal experience with the FLX1 from Fury Labs, a modern Linux phone that functions as a daily driver, benefiting from software advancements like Purism's "Lip Advaita" (for adaptive GTK apps) and Fury Labs' ported Low Memory Killer Daemon. User interfaces like Fosch, Gnome Mobile, and Plasma Mobile are discussed, showcasing a growing ecosystem of functional open-source applications. The presentation concludes with an optimistic outlook, urging users to adopt modern Linux phone hardware and contribute to building a self-determined, open-source mobile ecosystem.
Linux on Smartphones: A 20-Year Journey to Usability
0:11 A Long-Standing Dream: The idea of Linux on smartphones has persisted for over two decades, with early projects like OpenMoko demonstrating initial attempts despite rudimentary hardware.
1:19 The Problem with Android: Even "open" Android variants like GrapheneOS often rely on proprietary drivers and Google's "Play Services," which Google uses to maintain control over hardware manufacturers and app developers (e.g., for location, push notifications, maps).
3:55 The "Chasing Google" Dilemma: While alternatives like MicroG, UnifiedPush, and F-Droid exist, they are often seen as playing catch-up to Google's proprietary offerings, hindering a truly independent open-source ecosystem.
7:10 A Historical Timeline of Projects: The speaker traces the evolution of Linux phone projects including OpenMoko, Maemo/MeeGo (Nokia N900/N9, leading to Sailfish OS), the failed Ubuntu Edge crowdfunding, PostmarketOS, PinePhone, and Librem 5.
9:11 Recent Breakthroughs (PinePhone & Librem 5): Despite initial hardware limitations, these devices significantly boosted development, fostering a community that adapted apps and built essential phone functionalities, leading to the current state of usability.
10:22 The "Frankenstein" Approach (Halium): Many current projects use a hybrid architecture (dubbed "Frankenstein") combining a Linux kernel with Android-like components and proprietary drivers, standardized by projects like Halium, to leverage existing hardware support. PostmarketOS is noted for its goal of entirely open drivers.
OpenMoko, Maemo/MeeGo (Nokia N900/N9): Early pioneers that generated initial excitement before Nokia's shift to Microsoft.
Sailfish OS (Jolla): Emerged from MeeGo, a commercially available Linux-based OS that still exists.
Ubuntu Edge: A highly ambitious but ultimately failed crowdfunding campaign for an Ubuntu phone.
PinePhone/PinePhone Pro: Designed for open-source development, it propelled progress but is now largely outdated or discontinued.
Librem 5 (Purism): Crowdfunded, its hardware quickly became outdated, but the project invested heavily in crucial software development (like Lip Advaita), benefiting the wider ecosystem.
20:50 The FLX1 (Fury Labs) Experience: The speaker highlights the FLX1 as a modern, high-performance Linux phone that, after initial bugs, became a reliable daily driver thanks to consistent monthly updates. It offers an Android container for compatibility and working hotspot functionality.
22:50 User Interfaces: Prominent mobile UIs include Fosch (developed for Librem 5, GTK-based, similar to Gnome Shell), Gnome Mobile (adapting the existing Gnome Shell), and Plasma Mobile (KDE-based).
24:00 PostmarketOS - The Open Frontrunner: This project aims to install Linux on existing Android phones, reverse-engineering drivers to eliminate proprietary blobs. While making significant progress, challenges remain with camera, GPS, NFC, and mobile data functionality on many devices.
26:12 Adaptive Applications (Lip Advaita): A key development from Purism for the Librem 5, Lip Advaita enables GTK applications to adapt seamlessly between small phone screens and larger desktop environments, making many existing Gnome apps readily available on Linux phones.
27:30 Power and Memory Management (LMKD Port): Fury Labs ported Android's Low Memory Killer Daemon (LMKD) to Linux, significantly improving system stability and preventing freezes in low RAM situations, a common issue for Linux devices.
30:05 Functional Core Apps: Standard phone features like clocks (alarms work in standby), calls (using Modem Manager and Ofono), weather, and PDF viewers are now fully functional.
32:15 Camera Compromise & Development Motivation: The FLX1's good camera performance relies on proprietary Android drivers, highlighting the ongoing "Frankenstein" compromise. This daily usage motivates the speaker to contribute fixes and improvements to the Linux phone ecosystem.
34:02 Growing App Ecosystem: A wide range of open-source applications are available and well-maintained for Linux phones, including Calendar, Email, Matrix, Notes (with Nextcloud sync), Mastodon (Tuba), Podcast apps, MusiC (Shazam alternative), and Maps (G Maps, Comaps for navigation). Firefox is also adapted for mobile use.
36:46 App Acquisition: Users can build apps themselves, find them on F-Droid, or use frontends like Aurora Store for Play Store apps, though the reliance on proprietary apps for certain services (e.g., banking, mobility) remains a challenge.
38:03 Conclusion & Call to Action: Linux on smartphones is now usable and enjoyable. The speaker recommends choosing modern hardware (like the FLX1 or PostmarketOS-supported devices) and embracing the "Frankenstein" approach as a necessary interim step to build a truly open-source ecosystem, rather than merely imitating Android.