--- title: Will Linux phones become a viable alternative to the... description: A deep, data-heavy analysis argues that mobile Linux may finally become a viable niche alternative to Android/iOS, unlike its stagnation since the 2020 Librem... canonical: https://daily.dev/posts/will-linux-phones-become-a-viable-alternative-to-the-android-ios-duopoly--kkjcvwnhm twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Will Linux phones become a viable alternative to the Android/iOS duopoly? | daily.dev og:description: A deep, data-heavy analysis argues that mobile Linux may finally become a viable niche alternative to Android/iOS, unlike its stagnation since the 2020 Librem... og:url: https://daily.dev/posts/will-linux-phones-become-a-viable-alternative-to-the-android-ios-duopoly--kkjcvwnhm og:image: https://api.daily.dev/og/posts/KKjcVwNhM.png og:image:alt: Will Linux phones become a viable alternative to the Android/iOS duopoly? og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Will Linux phones become a viable alternative to the Android/iOS duopoly? **[Hacker News](https://daily.dev/sources/hn)** · 95 min read · 1 upvotes · 0 comments ## Summary A deep, data-heavy analysis argues that mobile Linux may finally become a viable niche alternative to Android/iOS, unlike its stagnation since the 2020 Librem 5/PinePhone era. The piece traces why early Linux SoCs (Allwinner A64, i.MX 8M Quad) were too weak and power-hungry, then explains how Rockchip's RK3588S (used in the Liberux NEXX, Dawndrums Divine D., and likely Purism's next phone) finally offers enough CPU/GPU power with growing mainline Linux driver support. It also covers Qualcomm's Dragonwing IoT chips (QCM6490, QCM4490, QCM8850) as an alternative path with long-term support programs, and examines the security risks of libhybris-based phones (FuriLabs FLX1, Jolla C2) running outdated, unpatched Android kernels that can't receive kernel-version upgrades from MediaTek or UNISOC. The piece closes by detailing how competitive pressure between Google, Samsung, and Qualcomm is pushing Android OS/security support out to 7-8 years, which could eventually make Android-kernel-based Linux phones more sustainable too. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why is the Rockchip RK3588S considered a turning point for Linux phone hardware? The RK3588S, released in 2022, is the first Linux-compatible SoC with enough CPU and GPU power for an acceptable smartphone experience, featuring four 2.4GHz Cortex-A76 cores, four 1.8GHz Cortex-A55 cores, and a Mali-G610 MP4 GPU. It scores 730/2250 on Geekbench 6, and mainline Linux now supports its GPU, NPU, and boot chain with largely free drivers, powering phones like the Liberux NEXX and Dawndrums Divine D. _Anyone evaluating open hardware for a Linux phone project can track SoC and driver updates like this on daily.dev._ ### Why are Linux phones like the FuriLabs FLX1 and Jolla C2 running unsupported Android kernels a security risk? Both phones use an Android 11-era 5.4 kernel that Google stopped patching on January 1, 2026, and that mainline Linux stopped maintaining on December 3, 2025, because their MediaTek Dimensity 900 and UNISOC Tiger T606 chips never received a major kernel upgrade. Running Android apps via Waydroid or AlienDalvik on this unpatched kernel exposes these phones to the 37.62 million known pieces of Android malware without ongoing security fixes. _Developers choosing a mobile Linux distro for longevity watch kernel support timelines like these via daily.dev._ ### How does Qualcomm's QCM6490 Dragonwing chip help Linux phones compared to the RK3588S? The QCM6490, used in the Fairphone 5 and SHIFTphone 8, offers better CPU and GPU performance and energy efficiency than the RK3588S and is supported under Qualcomm's Product Longevity Program until July 2036, far outlasting typical 2-3 year smartphone SoC support. This long support window matches the lengthy development and sales cycles Linux phones need, though it depends on proprietary blobs for WiFi, Bluetooth, modem, and other functions. _Teams weighing long-support IoT chips against open hardware for embedded or phone projects follow comparisons like this on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 3 discussions and 185 comments across hackernews, lobsters (as of 2026-10-12). **TL;DR:** Discussion is dominated by skepticism: most argue that forking/supporting AOSP (GrapheneOS, LineageOS, /e/OS) is far more practical than building mobile Linux from scratch, citing weak hardware documentation, poor battery/power management, and immature app compatibility as persistent blockers. **Sentiment:** 10% positive · 25% mixed · 65% skeptical **The case for** - A few see potential once hardware is properly documented, pointing to Waydroid and FEX as proof that full Android app compatibility and even PC gaming could eventually run well on Linux phones. - Some argue that avoiding dependence on Google's unilateral control over AOSP is worth the long-term investment in independent Linux stacks. - HarmonyOS's growth in China is cited as evidence that a true third mobile ecosystem can take hold given enough institutional backing. **The pushback** - Many argue closed/undocumented hardware (SoCs, cameras, radios) makes genuinely competitive open-source drivers nearly impossible without reverse engineering over many years. - Desktop Linux's historically poor battery life and lack of an app-suspend/resume model comparable to Android/iOS is seen as a deep architectural gap, not just a polish issue. - Security is repeatedly flagged as weak, since Android-compatibility layers like Waydroid and libhybris undermine Android's sandboxing model. - Several say forking AOSP (as GrapheneOS/LineageOS/e/OS already do) is strictly less work and more practical than maintaining a from-scratch Linux mobile stack, given AOSP's existing driver and app ecosystem. - Tiny market reach for Linux-friendly hardware like the Fairphone means little incentive for developers to invest in polish. **By community** - hackernews (skeptical): Extended, technical debate mostly concludes that forking AOSP is more realistic than building a mobile Linux stack, with hardware documentation and battery/power management cited as the core blockers. **Hottest debate:** Whether the pragmatic path forward is forking/hardening AOSP (GrapheneOS-style) versus investing in ground-up mobile Linux distributions. **Open questions** - Would regulators ever force hardware vendors to release documentation needed for competitive open-source drivers? - Can mobile Linux ever replicate Android/iOS's deep app-suspension and power-management model without a similar vertically integrated stack? - How would banking and other Play-Integrity-gated apps function on a non-Android Linux phone at scale? **Highlights** > No, they won't become a viable alternative: - Worse compatibility with the millions of Android apps already out there. - Hardware vendors (outside Apple) all target Android. - The usability of Android/iOS is far better than non-Android Linux phones. - The security of non-Android Linux phones is in a bad state (e.g. lacking proper app sandboxing). Heck, even the Android emulation layers that some of these phones have, throw the strong Android sandbox model out of the window. The answer is very obvious and it is AOSP. Even though Google is trying to close AOSP more (e.g. by not pushing source continuously to the AOSP Git repos and keeping QPR1/3 for themselves), it is still an open source system. Play Services can either be run sandboxed or emulated with microG. AOSP allows alternative systems to hit the ground running, you get great app compatibility, a tested security model, great usability, and support from hardware vendors, including vendors that are alternative friendly (used to be Pixel, now Motorola, Fairphone, etc.). If ever needed, AOSP could be forked and it would still be leagues ahead of non-Android Linux phones. All the downsides that apply to AOSP-based systems (like things getting blocked by Play Integrity, unlockable bootloaders) also apply to non-Android Linux systems. > — [microtonal on hackernews · 8 comments](https://news.ycombinator.com/item?id=50052002) > The lack of polish is a function of the inability to use the hardware. The hardware is tightly gatekept so competition _cannot_ exist. Regulators are the only ones who can force vendors to distribute documentation for and unlock their hardware. Once we can actually target the hardware, open source alternatives will be much better than first party options. You can already see the potential in the open source world. Linux has Waydroid so Android apps can be run on Linux at full speed without emulation. That means, if you had a Linux phone, you have the entire Android library - the only thing lacking is the launcher. How hard is a launcher to program? It's just Steam's big picture mode. Other examples of the nice things we can't have; FEX lets you run Steam games on phone hardware. Open source drivers can unlock displayport over USBC. Instantly your phone becomes a thin client / laptop replacement that can play PC games (poorly, but 1080p games are possible). We are _not allowed_ to do these things. I love OS development and, if I was allowed, I'd make iOS look like janky trash. > — [apatheticonion on hackernews · 5 comments](https://news.ycombinator.com/item?id=50052076) > > This comes up every time, I just don't understand the argument. You can fork AOSP when that happens Hacking on the Linux stack is several orders of magnitude more practical than AOSP though. AOSP's build system is massively unwieldy for individual contributors to work on. You can't easily work on any of the system components without dedicating >100 GiB of storage for a build, for example. Everything is scattered across hundreds of repositories tied together with a bespoke repository management tool. This all works for a company equipped with entire build infrastructure teams, not for a grassroots project trying to keep up maintenance with (at best) limited funding. It's why Nura (fka postmarketOS) is a thing whereas the various AOSP forks barely ever modify the core experience. > — [neobrain on hackernews](https://news.ycombinator.com/item?id=50053685) > About 5 years, Mandrake and SuSE with KDE around 1996 were already quite good. Since then the problem has always been the same, rebooting the DE experience for the sake of it, desktop environment wars, rebooting the development stack from GNOME and KDE, and the problem that despite all OEMs have Linux running on their data centers, the community has to reverse engineer the hardware from the same OEMs. > — [pjmlp on hackernews · 1 comments](https://news.ycombinator.com/item?id=50052525) > iOS and Android have an incredible amount of engineering to make them RAM and battery efficient that desktop Linux simply doesn't have. And its not a case of simply implementing some feature, since all apps have to written with this stuff in mind: apps can be suspended/killed at any time and should be able to restart gracefully, notifications go through a side channel, etc etc Do these phones have any of this? > — [serbuvlad on hackernews · 6 comments](https://news.ycombinator.com/item?id=50051948) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=50051530) · 159 points · 183 comments - [hackernews](https://news.ycombinator.com/item?id=50008334) · 2 points · 2 comments - [lobsters](https://lobste.rs/s/slsj46/will_linux_phones_become_viable) · 8 points · 0 comments ## Similar posts on daily.dev - [Nura \(postmarketOS\): The road to daily-drivable mainline phones](https://daily.dev/posts/nura-postmarketos-the-road-to-daily-drivable-mainline-phones-36drcjxt0) · Lobsters · 1 upvotes · 0 comments - [A Linux-Powered Smartphone That Has Features You Won't Find on Most Phones](https://daily.dev/posts/a-linux-powered-smartphone-that-has-features-you-won-t-find-on-most-phones-tmvknkrwm) · It's Foss · 0 upvotes · 0 comments - [Ubuntu Phone failed, but running full Linux on your phone is actually possible now](https://daily.dev/posts/ubuntu-phone-failed-but-running-full-linux-on-your-phone-is-actually-possible-now-5ylqvolj9) · XDA Developers · 1 upvotes · 0 comments - [I'm switching my phone from Android to Linux.](https://daily.dev/posts/i-m-switching-my-phone-from-android-to-linux--7sjxcrb4s) · Hacker News · 0 upvotes · 0 comments --- Tags: [#android](https://daily.dev/tags/android) [View this post on daily.dev](https://daily.dev/posts/will-linux-phones-become-a-viable-alternative-to-the-android-ios-duopoly--kkjcvwnhm) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Will Linux phones become a viable alternative to the Android/iOS duopoly?","url":"https://daily.dev/posts/will-linux-phones-become-a-viable-alternative-to-the-android-ios-duopoly--kkjcvwnhm","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/will-linux-phones-become-a-viable-alternative-to-the-android-ios-duopoly--kkjcvwnhm"},"datePublished":"2026-10-12T07:00:36.356Z","dateModified":"2026-10-12T11:17:38.782Z","description":"A deep, data-heavy analysis argues that mobile Linux may finally become a viable niche alternative to Android/iOS, unlike its stagnation since the 2020 Librem...","image":"https://i0.wp.com/amosbbatto.wordpress.com/wp-content/uploads/2026/10/pinephoneandlibrem5-1.jpg?fit=1196%2C1200&ssl=1","thumbnailUrl":"https://i0.wp.com/amosbbatto.wordpress.com/wp-content/uploads/2026/10/pinephoneandlibrem5-1.jpg?fit=1196%2C1200&ssl=1","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/will-linux-phones-become-a-viable-alternative-to-the-android-ios-duopoly--kkjcvwnhm","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"android","timeRequired":"PT95M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Will Linux phones become a viable alternative to the Android/iOS duopoly?"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/will-linux-phones-become-a-viable-alternative-to-the-android-ios-duopoly--kkjcvwnhm#faq","mainEntity":[{"@type":"Question","name":"Why is the Rockchip RK3588S considered a turning point for Linux phone hardware?","acceptedAnswer":{"@type":"Answer","text":"The RK3588S, released in 2022, is the first Linux-compatible SoC with enough CPU and GPU power for an acceptable smartphone experience, featuring four 2.4GHz Cortex-A76 cores, four 1.8GHz Cortex-A55 cores, and a Mali-G610 MP4 GPU. It scores 730/2250 on Geekbench 6, and mainline Linux now supports its GPU, NPU, and boot chain with largely free drivers, powering phones like the Liberux NEXX and Dawndrums Divine D. Anyone evaluating open hardware for a Linux phone project can track SoC and driver updates like this on daily.dev."}},{"@type":"Question","name":"Why are Linux phones like the FuriLabs FLX1 and Jolla C2 running unsupported Android kernels a security risk?","acceptedAnswer":{"@type":"Answer","text":"Both phones use an Android 11-era 5.4 kernel that Google stopped patching on January 1, 2026, and that mainline Linux stopped maintaining on December 3, 2025, because their MediaTek Dimensity 900 and UNISOC Tiger T606 chips never received a major kernel upgrade. Running Android apps via Waydroid or AlienDalvik on this unpatched kernel exposes these phones to the 37.62 million known pieces of Android malware without ongoing security fixes. Developers choosing a mobile Linux distro for longevity watch kernel support timelines like these via daily.dev."}},{"@type":"Question","name":"How does Qualcomm's QCM6490 Dragonwing chip help Linux phones compared to the RK3588S?","acceptedAnswer":{"@type":"Answer","text":"The QCM6490, used in the Fairphone 5 and SHIFTphone 8, offers better CPU and GPU performance and energy efficiency than the RK3588S and is supported under Qualcomm's Product Longevity Program until July 2036, far outlasting typical 2-3 year smartphone SoC support. This long support window matches the lengthy development and sales cycles Linux phones need, though it depends on proprietary blobs for WiFi, Bluetooth, modem, and other functions. Teams weighing long-support IoT chips against open hardware for embedded or phone projects follow comparisons like this on daily.dev."}}]} ```