Google is preparing to let you run Linux apps on Android, just like Chrome OS

Original Article ↗ Hacker News Discussion ↗

Google is working on a way to run traditional Linux applications inside virtual machines on Android, bringing it closer to the Linux support already found on ChromeOS. Commenters see potential for real development workflows, desktop-style “convergence” (phone as primary computer with monitor/keyboard), and running tools like Docker, but note that performance, permissions, and tight sandboxing may limit access to device data compared to existing tools like Termux. Many welcome the feature for power users and developers, while others worry it will further entrench Google’s control over devices and marginalize more open, root-friendly approaches.

Overall Reaction

  • Many are excited: Android already feels close to a general-purpose OS; first‑class Linux app support could make phones/tablets viable as primary computers and even replace laptops for some.
  • Others are skeptical or indifferent, preferring to run Android apps on desktop/Linux instead of Linux apps on Android.

Existing Solutions (Termux, VMs, DeX, etc.)

  • Termux + X11/VNC already allow many CLI and some GUI Linux tools on Android; people run servers, dev tools, even long‑running processes successfully.
  • This new feature appears VM‑based (AVF/pKVM), more like ChromeOS’s Crostini than native syscalls, so Termux may remain faster and better integrated with Android APIs.
  • Some fear Google may use this to justify restricting or deprecating tools like Termux, qpython, or rooted/Docker hacks; others argue these are niche and not really a target.

Architecture, Permissions, and Capabilities

  • Expected model: a fully isolated Linux VM/container, with its own storage and optional shared folders, including sudo inside the VM but no privileged access to Android itself.
  • Users doubt Google will grant broad access to SMS, cameras, or app data; likely limited for security and policy reasons.
  • Questions about running Docker/podman and using the phone as a small server; ChromeOS’s Debian VM can do this, so people hope Android will as well.

ChromeOS, Fuchsia, and Platform Strategy

  • Many see this as Android catching up to ChromeOS’s Linux support and/or part of a slow unification: ChromeOS taking Android’s stack, Android getting Linux VMs, Fuchsia gaining Linux compatibility.
  • Others argue there may be no grand strategy, just overlapping projects and internal fiefdoms; ChromeOS deprecation is viewed as possible but not certain.

Convergence and Desktop Use Cases

  • Strong interest in “phone as desktop”: plug into monitor/keyboard (similar to Samsung DeX) and get a full Linux dev or productivity environment.
  • Comparisons made to GNU/Linux phones (Librem 5, etc.), which already run Linux apps natively and Android apps via compatibility layers, but with weaker hardware and higher prices.

Trust, Control, and Antitrust Concerns

  • Several commenters object to Google’s control over what runs on user devices, tying it to broader worries about monopolies, privacy, and locked bootloaders.
  • Others note similar concerns exist with Apple and Microsoft; antitrust and regulatory angles are discussed but outcomes are viewed as uncertain.