GrapheneOS

Google's plan requires every Android developer to register centrally, hand over government ID and prove they hold the signing key, even for apps shared outside the Play Store. Power users keep a 9-step escape hatch with a mandatory 24-hour wait.

Commenters split on whether that wait is a fair compromise or the first turn of the screw. One of them brought up tech-support scams.

The project says Motorola is porting GrapheneOS and names a 2027 Signature plus Razr fold and flip devices as prospective targets, while lower-end models may take longer.

That qualifier was the story for HN: an alternative OS still depends on vendors shipping long update windows and the security features it requires.

The author’s Android-to-Linux switch is a case for a phone that can be inspected and changed like a general-purpose computer. HN readers pointed to alternatives such as postmarketOS and Purism hardware, but also named what does not travel cleanly: services built around Google Play Services and Wallet.

The discussion’s disagreement was not whether Android contains open-source code. It was whether the experience can remain meaningfully open as important APIs and everyday features live in Google-controlled services.

The project points to secure-element rate limiting, hardened exploit defenses, blocked USB data while locked, and an 18-hour locked-device reboot that returns the phone to its pre-unlock state.

HN readers focused on the everyday trade-off: strong protection depends on how the phone was last used. A device left running after first unlock presents a different problem from one powered down before a border crossing.

Version 3.0 is a real step: non-destructive crop/rotate/adjust on mobile, a Workflows automation engine, HLS on-the-fly transcoding, and integrity checks that catch missing or mismatched files. Breaking changes hit third-party integrations.

Encryption was the fault line. Several users said the lack of E2EE is why they picked Ente instead. A contrarian pushed back hard: for a home photo library, end-to-end encryption is arguably pointless — lose your keys and you lose the only copy of grandma. The sharpest bug report was an operator finding 20% of his disk eaten by duplicated per-user thumbnails.

The EU's digital identity wallet uses Google Play Integrity to vouch for a phone, which rejects de-Googled Android as untrusted. Switzerland uses Android's plain Hardware Attestation API instead; Italy and the Netherlands wired in Play Integrity unconditionally.

A Waag researcher argues that route breaches the Digital Markets Act. In the thread, the developer of the Fenrir protocol predicts nothing changes until an antitrust lawsuit lands.

Reuters rounds up a wave of near-simultaneous laws restricting minors' access to social platforms. A reader back in the UK described the lived version: he can't read half of X without handing over a government ID to prove he's an adult.

The argument wasn't whether kids should be protected, it was the mechanism. Engineers sketched cryptographic age-proofs that reveal one bit and nothing else, then asked why the actual laws reach for face scans and license uploads instead.

VW didn't just drop GrapheneOS support — it shut its API to anything not certified by Google Play, killing the community integrations people used to schedule charging and preheating.

The detail that stung most in the thread came from a reader pointing out that none of this needs to touch a server: your own charging data should be readable locally from the car. Several would-be buyers said they cancelled orders over it — one mid-purchase.

Tested so far on the Pixel 6a, 7, 7a, 8, 10a, 10 and 10 Pro Fold, with official releases coming soon and longer security-patch support than Android 16 gets.

Notably absent from the list: the Pixel 9 and 9a, which several owners in the thread are still waiting on.

The bigger flip: a privacy OS that only installs on phones from the company you're trying to leave, and Pixels aren't even sold worldwide.