IdeaWell

Project ideas from Hacker News discussions.

LineageOS 24.0

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Four prevalent themes in the discussion

  • Extending phone life with custom ROMs – Users appreciate LineageOS/GrapheneOS for keeping older devices usable and reducing e‑waste.

    “big thanks to the Lineage maintainers, keeping so many phones from landfill!” – deng
    “I replaced battery in mine for like 90 EUR … Would still use it instead of 9a, love how light and compact the phone was.” – Klaster_1
    “I recently pulled out my Pixel 3 and forgot how much I liked the form factor.” – mistyvales

  • Banking app restrictions on unofficial Android builds – Some banks block LineageOS/GrapheneOS, prompting workarounds like Magisk Hide or private spaces.

    “I have yet to find a banking app that refuses to work on LineageOS. The only problem is if you root your phone, in which case you'll have to use Magisk to hide root from those apps.” – deng
    “Revolut … explicitly check the build string for LineageOS and block the app if it matches.” – platinum95
    “I create a private space for the apps needing play services … when locked, the apps including play services are completely off.” – pimeys
    “What possesses companies to do things like this? A customer running a current version of LineageOS is going to have better security …” – AnthonyMouse

  • Shift away from NFC payments toward cash or physical cards – Frustration with app‑based NFC leads many to carry cash or cards as a fallback.

    “Go even further and carry cash! No technology dependency and ‘just works’.” – phillc73
    “Not everywhere … only accepting digital payments is the norm and they won’t serve you if you pay in physical cash.” – latexr
    “I just decided to completely stop paying with NFC. I always carry a few cards with me…” – pimeys
    “one generally doesn't want to be 'that guy'.” – Telaneo

  • Trade‑offs between LineageOS and GrapheneOS – LineageOS offers broader device support; GrapheneOS provides faster updates and stronger security at the cost of fewer supported models.

    “GrapheneOS actually feels just like LineageOS, except that it has faster upstream updates, better security, and greater usability.” – imkac
    “GOS => security, usability … LOS => most security, most usability, breadth of support.” – user2722
    “GrapheneOS has paid developers working on it full‑time, while LineageOS is done by people in their spare time … LineageOS supports roughly 10× the number of devices.” – timschumi
    “GrapheneOS doesn't receive early access to security patches via Motorola … We were already doing security preview releases …” – grapheneos

🚀 Project Ideas

BankROM Check

Summary

  • A community-driven web app where users report whether banking/payment apps work on LineageOS, GrapheneOS, or rooted devices, including workarounds like Magisk Hide or custom build props.
  • Core value: Saves users time trial-and-error, reduces risk of being locked out of essential banking apps.

Details

Key Value
Target Audience Users of custom Android ROMs (LineageOS, GrapheneOS) who rely on banking apps
Core Feature Searchable database of app compatibility status with user-submitted notes and workaround instructions
Tech Stack Frontend: React/Vue; Backend: Node.js/Express or Python/FastAPI; Database: PostgreSQL; Hosting: Vercel/Render
Difficulty Medium
Monetization Revenue-ready: Freemium (free basic search, paid API for devs)

Notes

  • HN commenters expressed frustration with Revolut and DKB blocking LineageOS (e.g., "Revolut is notorious... they explicitly check the build string for LineageOS") and reliance on workarounds like Magisk Hide or private spaces (pimeys: "I create a private space for the apps needing play services"). A centralized compatibility list would be loved.
  • Could spark discussion on reducing app attestation overreach and provide practical utility for privacy‑focused Android users.

PartFinder for Phones

Summary

  • Aggregates prices and availability of replacement parts (batteries, screens) for specific phone models from multiple vendors (eBay, AliExpress, iFixit) and links to step‑by‑step repair guides.
  • Core value: Helps users keep older devices alive affordably and avoid surprise costs like broken screens during repair.

Details

Key Value
Target Audience DIY repair enthusiasts and owners of aging smartphones seeking low‑cost parts
Core Feature Real‑time price comparison, vendor ratings, and embedded repair‑guide links (e.g., iFixit)
Tech Stack Python scraper backend, Elasticsearch for search, React frontend, hosted on Docker/Kubernetes
Difficulty Medium
Monetization Revenue-ready: Affiliate fees from parts vendors + optional premium guide bundles

Notes

  • Users mentioned battery replacement costs (~90 EUR) and breaking screens after replacement (Klaster_1: "I replaced battery in mine for like 90 EUR and several months in dropped it and broke the screen"). PartFinder would surface the cheapest reliable parts and highlight guides with warnings.
  • Practical utility: extends device lifespan, reduces e‑waste, aligns with the HN community’s right‑to‑repair ethos.

LineageOS‑Easy‑X86

Summary

  • Provides a one‑click installer and manager for pre‑built LineageOS images on x86 laptops, tablets, and convertibles, with seamless integration into the host Linux desktop (file sharing, clipboard, notifications).
  • Core value: Lets users run Android apps on familiar hardware without juggling a separate phone, addressing the desire for app consistency and security on older devices.

Details

Key Value
Target Audience Linux users who want to run Android‑only apps (banking, messaging, NFC‑free utilities) on x86 hardware
Core Feature Automated download, flashing, and runtime management of LineageOS‑x86 via a GUI frontend (uses Waydock/LXC under the hood)
Tech Stack Rust or Go for daemon, Flutter/Electron for GUI, relies on Waydroid/Anbox containers, distributed as AppImage or Snap
Difficulty High (due to hardware integration and driver handling)
Monetization Hobby (open source; optional donations)

Notes

  • Deng expressed interest: "Would be interesting for x86‑based tablets/convertibles, like for instance an old Lenovo X1." Others discussed running Android on Linux for familiarity, app availability, and security. A streamlined installer would be welcomed.
  • Could generate discussion about the trade‑offs between full Android on x86 vs containerized solutions, and provide a practical path to de‑Google older hardware.

PrivacyGuard‑Lineage

Summary

  • An open‑source Android app (or Magisk module) that gives granular control over sensors, camera, microphone, network, and build‑prop spoofing to thwart unwanted attestation checks while preserving device functionality.
  • Core value: Empowers LineageOS users to protect privacy and avoid app‑based blocks (e.g., banking apps that reject custom ROMs) without sacrificing usability.

Details

Key Value
Target Audience Privacy‑conscious LineageOS/GrapheneOS users who need to hide root or spoof device identifiers
Core Feature Per‑app toggles for camera/mic/sensor access, network VPN‑like routing, and automated build‑prop/fingerprint spoofing based on app profiles
Tech Stack Java/Kotlin Android app, optional Magisk module using Zygisk; uses Android’s AccessibilityService and Storage Access Framework; distributed via F‑Droid
Difficulty Medium
Monetization Hobby (free, open source)

Notes

  • Commenters worried about remote attestation and LiDAR‑based photo verification (AnthonyMouse vs hollerith debate) and desired a way to stop attestation from harming legitimate users. PrivacyGuard‑Lineage would let users spoof the build string that Revolut checks (as platinum95 noted: "build the ROM yourself with a new build name string") and hide root via Magisk‑style mechanisms.
  • Practical utility: reduces need for constant ROM rebuilding, gives users a UI to manage attestation

Read Later