We're happy to announce a long-term partnership with Motorola. We're collaborating on future devices meeting our privacy and security standards with official GrapheneOS support. motorolanews.com/motorola-th…

Vanadium version 149.0.7827.114.0 released: github.com/GrapheneOS/Vanadi… See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread: discuss.grapheneos.org/d/363… #GrapheneOS #privacy #security #browser

GmsCompatConfig version 170 released: github.com/GrapheneOS/platfo… See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread: discuss.grapheneos.org/d/362… #GrapheneOS #privacy #security #gmscompat

Purism's devices have Intel ME and don't attempt to break it anymore. Purism spent years portraying it as a backdoor and claiming they were stopping it. Purism switched to leaving ME fully intact a while ago and their past content claiming to be neutralizing it isn't applicable. Purism misrepresents their products with closed source hardware and firmware as being open hardware. They mislead people and benefit from uninformed tech media sites spreading it. Their products also have atrocious security far worse than the norm but are marketed as secure. Purism's approach is avoiding bundling closed source firmware in the OS by having an extra CPU core to load and run it, using much less secure components with firmware stored on a flash chip and using a separate partition for the OS to load it from. They claim this makes it open. Their devices leave remotely exploitable radio vulnerabilities unpatched and don't address severe CPU vulnerabilities. They choose components lacking proper security updates and protections. They also can't use important standard security protections due to the semantic games. Your reply history is filled with you using the auto-generated text from a search engine as your main source of information. It's a bottom of the barrel LLM model run with minimal resources. If you're going to place so much trust in LLM output, then at least start paying for access to a decent model instead of using a search engine for it. You shouldn't trust the output regardless but it wouldn't be nearly as ridiculous.

Motorola Mobility was fully split from Motorola Solutions in 2011. Motorola Mobility was subsequently acquired by Google in 2012 and sold to Lenovo in 2014. The companies are entirely separate and aren't sister divisions. You should pay for a better LLM because this is garbage.

Your account is openly acting in bad faith and posting content you know is untrue. These posts trying to trick people into believing our non-exclusive partnership with Lenovo is with a different company is a great example: x.com/kekzploit/status/20605… It's also clearly AI slop.

Second available post continuing to discourage using privacy technologies including private cryptocurrencies and E2EE messaging: x.com/kekzploit/status/20335… Your posts aim to stop people protecting their privacy with illogical claims about backdoors contradicted by actual evidence.

That's a strange claim coming from an account which was cleared out and repurposed for AI slop propaganda against privacy and security technologies in March 2026. Here's the first available post discouraging using disk encryption and encrypted messaging: x.com/kekzploit/status/20333…

There isn't another publicly available privacy and security hardened fork of AOSP. GrapheneOS isn't in the same space as LineageOS and other alternative mobile operating systems. A current gen iPhone is quite privacy/security hardened but isn't open source or an open platform.

The account makes a mix of false and unsubstantiated claims to convince people not to improve their privacy and security. Claiming there are backdoors in everything without evidence and in conflict with a lot of actual evidence about exploit capabilities is bad faith tactic.

RISC-V is an open instruction set. Most RISC-V hardware is closed source and there isn't an open source RISC-V SoC to use for a smartphone. Pixels have a RISC-V secure element based on OpenTitan. The SE being RISC-V instead of a fully custom ARM chip doesn't make it more secure.

There's a massive amount of evidence against your unsubstantiated claims and none to support it. You're trying to convince people not to protect with their privacy and security with a bunch of different unsubstantiated claims and outright fabrications. x.com/kekzploit/status/20605…

Google Mobile Services licensing has been found to be illegal in multiple countries including South Korea. The terms are outrageously coercive and monopolistic. Play Integrity API exists to enforce an illegal licensing model to crush competition. It's not a security feature.

Android was successful due to being open source and an open platform. Google has spent years scaling up illegal coercion of OEMs forcing them to deeply integrate Google apps/services and comply with outrageously illegal anti-competitive requirements in order to have a viable OS.

This is nothing but lies and misinformation. We haven't said anything of the kind. GrapheneOS fully supports hardware attestation. Play Integrity API banning using GrapheneOS despite it being far more secure and fully supporting hardware-based verification is blatantly illegal.