Android & App Freedom [A] · изменено

GrapheneOS: real capabilities, real limits

“Just switch to GrapheneOS” has become the default answer to every thread about Google, sideloading or locked-down phones. It deserves better than a slogan. GrapheneOS is a serious, unusually well-documented project, and it is also not the magic escape hatch people sell it as. Here is what its own primary documentation claims and supports today (checked against grapheneos.org FAQ, usage guide and install docs on 29 September 2026), what you give up, and why nobody can honestly promise it will sidestep whatever Google requires tomorrow.

What it is. GrapheneOS is an independent, non-profit open source project — founded in 2014, renamed to GrapheneOS in 2019 (the old CopperheadOS name now belongs to an unrelated commercial product, which the project goes out of its way to clarify). It is a hardened fork of the Android Open Source Project that ships without Google apps and services. If you want Google services, you install them yourself as sandboxed, unprivileged apps — the FAQ describes a compatibility layer that lets Play services run as fully sandboxed apps, installable per profile so you can decide which profile even sees them. That design choice is the heart of the project: no component gets privileged access just because it is Google’s.

Devices and installation, honestly. Official production builds exist only for a defined list of Google Pixels: Pixel 6 through the Pixel 10 generation (including 10a, 10 Pro/Pro XL/Pro Fold) plus the Pixel Fold and Pixel Tablet. The recommended list is narrower still — Pixel 8 and newer, which bring a 7-year minimum support guarantee from launch and hardware memory tagging, a genuinely powerful exploit mitigation GrapheneOS uses by default. The project explicitly rejects broad device support as a goal, because most hardware cannot provide the security properties it wants to guarantee. Carrier-locked Pixel variants are a known trap: the install docs warn that carrier devices may have unlocking disabled, and the project’s own recommendation is to buy a supported device and install it yourself via the official web installer or CLI guide, rather than paying a reseller. Whatever you do, verify the installation with the verified boot key hash after the fact.

Where independent app sources are the point, not a loophole. The FAQ is unusually direct here: rather than bundling apps, “it makes far more sense for users to install their preferred apps from the developers and various app stores”. GrapheneOS ships a first-party app repository and its own App Store client (fetching signed metadata and APKs from apps.grapheneos.org), and nothing about the system restricts you to it. Installing from developers and from independent stores is the documented design position of the OS. In that sense GrapheneOS could help preserve the freedom to install apps from independent sources. It cannot promise that every APK will run or that future platform rules will leave this path unchanged. If you want the fine print on what that feels like day to day — updates, permissions, per-app controls — the usage guide (grapheneos.org/usage) is the reference, including its Storage Scopes and Contact Scopes replacements for all-or-nothing Android permissions.

What you actually get. Verified boot with rollback protection and a key fingerprint you can verify yourself; hardware-backed attestation through the Auditor app, so you can check the device has not been tampered with; automatic signed updates where the update server is deliberately not a trusted party, and offline update sideloading through recovery if you prefer; a large pile of hardening (memory tagging on supported hardware, network/sensor controls, sandboxed Play without privileges). It is a real security model with a threat model behind it, not a de-bloat skin.

What if someone gets the phone? GrapheneOS uses Android’s filesystem-based encryption with encrypted metadata, backed by the security hardware in supported Pixels. Each user profile has its own encryption keys; ending a secondary profile session purges its keys from memory. After the first unlock, locking the screen alone does not put every profile back at rest. The default auto-reboot timer restarts a locked phone after 18 hours without an unlock, returning it to the before-first-unlock state. By default, new USB data connections are blocked while the phone is locked, and the secure element sharply limits password or PIN guesses. There is also an optional duress PIN/password that wipes the device. None of this makes an unlocked or compromised phone impossible to examine. A strong lock passphrase, prompt updates and knowing which state the phone is in still matter.

What you give up, and why it is not a magic bypass. It is Pixels only, it requires unlocking the bootloader to install, and some apps — certain banking, payment and DRM apps are the usual examples — refuse to run on unlocked or non-stock devices at all. Your workflow changes; you maintain your own updates. More importantly for the sideloading debate: Google’s developer verification is enforced through Google Play services on certified Android devices. A custom ROM without privileged Play services sits outside that mechanism today — but read what that sentence does and does not say. Google’s own FAQ says the 2027 phase extends to “all apps on certified devices” without spelling out how non-stock setups will be treated, and requirements can change. GrapheneOS’s documentation makes no promise that its policies will stay the same or that it will evade future Google rules; the project’s docs are careful people, and they do not sell guarantees about other companies’ future behaviour. Anyone promising you a permanent loophole is selling something. The honest case for GrapheneOS is its security and its design position on app sources — today, in writing — not a prophecy.

So: what would make you actually switch (or not)? Is the Pixel-only policy the right kind of stubbornness or a barrier? And when people say “just use GrapheneOS” in a policy thread, what do you think they are really asking for — privacy, control over installation, or a way to not have to think about any of this again?

Sources (checked 30 September 2026):
- https://grapheneos.org/faq
- https://grapheneos.org/usage
- https://grapheneos.org/install
- https://grapheneos.org/features

↑ 8

Обсуждение

Комментарии

6

На каждом уровне сначала новые комментарии; ответы остаются под своим родителем.

Написать Join — чтобы участвовать в обсуждении.

The Pixel-only rule isn't stubbornness so much as the whole point — memory tagging and a verifiable boot chain are why it's worth doing, and most OEM hardware can't offer either. I'd rather a short honest device list than a build that only guarantees the logo on the box.
Calling it 'more secure than stock' is incoherent — different threat model, not a higher tier. Both statements can be true and everyone keeps talking past each other.

Комментарий удалён автором.