IdeaWell

Project ideas from Hacker News discussions.

Will Linux phones become a viable alternative to the Android/iOS duopoly?

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Four dominant themes in the discussion

  1. Hardware documentation and vendor lock‑in are the biggest barriers
  2. “Without hardware documentation, you're looking at decades of reverse engineering effort just to get somewhere half as far as an engineer with hardware documentation can get in a weekend.” – apatheticonion
  3. “Look at Asahi. Almost a decade in and we can use the GPU at like 30% of its ability on 6 year old hardware.” – apatheticonion

  4. “The hardware is tightly gatekept so competition cannot exist.” – apatheticonion

  5. The Linux software stack is not optimized for phones (power management, app lifecycle, UI)

  6. “iOS and Android have an incredible amount of engineering to make them RAM and battery efficient that desktop Linux simply doesn't have.” – serbuvlad
  7. “The Linux desktop stack is wholly unoptimized for phones.” – microtonal

  8. “Desktop Linux cannot … open 60-70 … Electron apps simultaneously on 8GB of RAM.” – serbuvlad

  9. Ecosystem immaturity and app compatibility keep Linux phones niche

  10. “Worse compatibility with the millions of Android apps already out there.” – microtonal
  11. “The usability of Android/iOS is far better than non-Android Linux phones.” – microtonal

  12. “Librem 5 … is really just fine. Except the battery life, app compatibility and smoothness of the UI.” – fsflover

  13. LLMs/AI could help overcome reverse‑engineering and optimization hurdles

  14. “The third is that LLMs are kinda good at these optimization loops if you hand them a framework in which they can sample good data.” – hypfer
  15. “Maybe LLMs can help open the 'reverse engineering' Pandora's box.” – apatheticonion
  16. “LLM-driven optimization is a good point. However, Linux desktop communities tend to be quite aggressively anti‑LLM.” – microtonal

🚀 Project Ideas

Generating project ideas…

DocuLens: LLM‑Driven Hardware Documentation Generator

Summary

  • Automatically extracts register maps, timing constraints, and initialization sequences from vendor binary blobs to produce open‑source device trees and driver skeletons.
  • Core value: slashes reverse‑engineering effort from years to weeks, enabling rapid Linux‑phone hardware support.

Details

Key Value
Target Audience Linux‑phone developers, hardware enthusiasts, and device‑tree maintainers
Core Feature LLM‑assisted decompilation + annotation pipeline that outputs DTS files, kernel driver stubs, and hardware‑abstraction headers
Tech Stack Python, LLMs (e.g., Llama 3 via HuggingFace), Binja/Capstone for disassembly, Yocto build system, GitHub Actions for CI
Difficulty High
Monetization Revenue‑ready: SaaS tiered pricing (free tier for hobbyists, $20/mo for professional teams)

Notes

  • HNers lament that “without hardware documentation, you're looking at decades of reverse engineering effort” (apatheticonion) and see LLMs as a potential shortcut (ashirviskas, apatheticonion). DocuLens directly addresses that pain.
  • By providing verifiable, updatable specs, it would unlock community‑driven driver work for devices like Fairphone, PinePhone, and future Android‑based handsets, sparking discussion on open‑hardware policies.

OpenPing: Federated Push Notification Service for Linux Phones

Summary

  • A self‑hostable, protocol‑agnostic push gateway that delivers messages to apps via a unified API, independent of Google Play Services or Apple APNs.
  • Core value: restores reliable, background‑capable notifications on Linux‑based phones while preserving user privacy.

Details

Key Value
Target Audience Linux‑phone OS maintainers (e.g., postmarketOS, Plasma Mobile), app developers, privacy‑focused users
Core Feature Lightweight server (REST/WebSocket) + client library that handles registration, token management, and background wake‑ups using kernel alarm interfaces
Tech Stack Rust (Actix‑web), SQLite or PostgreSQL, Protocol Buffers, systemd‑user services, optional TURN/STUN for NAT traversal
Difficulty Medium
Monetization Hobby (open‑source) – optional paid hosting plans for enterprises ($10/mo per instance)

Notes

  • Commenters note that “notification are a bit of a lottery” on Linux phones (ptidhomme, microtonal) and praise UnifiedPush as an existing open‑source solution (Zak). OpenPing would improve upon it with easier deployment and richer diagnostics.
  • A reliable push layer would enable banking apps, messengers, and other critical services to work without Google services, directly addressing the “missing notifications” frustration.

Mobipower: Intelligent Battery‑Optimization Framework for Linux on Mobile

Summary

  • Daemon that monitors app behavior, enforces aggressive idle states, and dynamically tunes CPU frequency, GPU power, and peripheral clocks based on usage patterns.
  • Core value: brings Android‑level standby efficiency to Linux phones, extending battery life by 30‑50 % on typical hardware.

Details

Key Value
Target Audience Linux‑phone distro maintainers, power‑users, OEMs experimenting with Linux handsets
Core Feature Policy engine (eBPF + systemd) that suspends background apps, manages wake‑locks, and adjusts governor profiles in real time
Tech Stack C/Rust daemon, eBPF, DBus for UI configuration, GNOME/KDE settings plugins, Linux kernel 6.6+ with tickless idle
Difficulty Medium
Monetization Hobby (open‑source) – optional support contracts for device vendors

Notes

  • Many participants point out that “Linux laptops… battery life is still much worse than Windows” (microtonal) and that “Android has an incredible amount of engineering to make them RAM and battery efficient” (serbuvlad). Mobipower would bring that expertise to the Linux stack.
  • By providing a configurable, UI‑driven power profile, it would let users trade performance for endurance—a feature frequently requested in HN threads about Linux phones.

PhoshLauncher: Secure, Android‑App‑Compatible Launcher for Linux Phones

Summary

  • A polished home‑screen and app‑launcher that runs Android apps inside a hardened Waydroid container while exposing native Linux apps side‑by‑side, with per‑app sandboxing and granular permission controls.
  • Core value: gives Linux‑phone users access to the massive Android app ecosystem without sacrificing the security and openness of a pure Linux environment.

Details

Key Value
Target Audience Daily Linux‑phone users who need Android apps (banking, maps, messaging) but want a Linux‑centric UI
Core Feature Unified launcher UI (built with Phosh/GTK) that integrates Waydroid instances, manages container lifecycles, and provides a permission‑dialog system modeled on Android’s runtime permissions
Tech Stack GTK 4, libhandy, Waydroid (LXC + binder), Flatpak for app sandboxing, Polkit for privilege escalation, Rust for backend services
Difficulty Medium
Monetization Hobby (open‑source) – possible donations or premium theme packs

Notes

  • Users express that “the only thing lacking is the launcher” when imagining Linux phones running Android apps via Waydroid (apatheticonion). PhoshLauncher would fill that gap.
  • By offering a familiar, polished launcher with strong sandboxing, it would appeal to both Linux enthusiasts and mainstream users hesitant to give up Android apps, directly addressing the “app compatibility” concern raised by multiple commenters.

Read Later