MetropleX | GrapheneOS | metroplex.bot

There's a major state sponsored misinformation and smear campaign towards GrapheneOS in the Netherlands and Germany. The misinformation campaign includes unsubstantiated security claims not holding up to scrutiny to scare people away from it. They're also heavily misrepresenting who uses it overall. These smear campaigns conflate GrapheneOS with forks and modifications of it sold by shady companies. Those usually include a device management app to remotely manage the devices of their customers as if they're employees. These are largely not GrapheneOS devices or have preinstalled malware apps. A common tactic being used in these smear campaigns is to make unsubstantiated and outright false claims about the capabilities of forensic data extraction tools. They misrepresent how they get into devices. They want to scare people into using far less secure devices which are easier to exploit. France, Germany, Spain and the Netherlands are becoming increasingly authoritarian surveillance states with an ongoing crackdown against privacy. It's happening throughout the whole EU and it's likely both secure devices and end-to-end encryption without backdoors are going to end up outlawed. There are a bunch of companies based in the EU selling phones with drastically worse privacy and security than an iPhone including Jolla, Volla, Murena and iodé. These products are effectively backdoored by not providing standard privacy and security patches/protections while misleading users. France and other EU countries are actively cracking down on legitimate privacy and security projects while supporting unsafe products within their control. These products make it far easier to remotely exploit devices and also to bypass encryption to extract data. They're phony privacy products. Each of the companies we've listed have participated in the misinformation and smear campaigns against GrapheneOS. Jolla spent years working closely with Putin's regime. Volla, Murena and iodé are building an EU Play Integrity API. None provides the crucial standard privacy patches/protections. Murena is directly assisting with state anti-privacy campaigns smearing highly private and secure devices as mainly benefiting criminals. They've repeatedly falsely claimed GrapheneOS is mainly used by criminals. Here are 2 of many examples: teapawt.net/GrapheneOS/status/2040… clubic.com/actualite-604786-… GrapheneOS, end-to-end encrypted messaging apps, Monero and other projects are being targeted with state and corporate propaganda and anti-privacy laws. Meanwhile, the same governments heavily fund and support phony privacy projects clearly downgrading privacy and security compared to an iPhone. GrapheneOS is only an initial target for these state actors and their sycophants in corporate news organizations. Apple heavily works on protecting users against exploits too. It would be much harder to convince the public that an iPhone is for criminals so they're starting with open source.

There's a malicious website copying the content from our website which is trying to trick people into installing malware. It's registered via Namecheap and is using Cloudflare in front of their server. This should be taken down. installgarphenos [dot] ink /GrapheneOS [dot] zip

Our plan is to port 6th through 10th generation Pixels to Linux 6.18 to entirely phase out requiring the older kernel branches. Having a single kernel branch across all of the supported devices will greatly simplify shipping upstream LTS revisions and hardening the kernel.

Our port of the 10th generation Pixels to the Linux 6.18 GKI LTS branch has been through a day of public testing by a couple dozen users. There are no known issues remaining anymore. We're going to continue heavily reviewing the commits and looking for more unhandled API changes.

Experimental releases of GrapheneOS with our initial port to the Linux 6.18 branch are now available for testing on the Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL and Pixel 10 Pro Fold. We've done initial testing but there will likely be at least a dozen more crashes and other issues to find and fix. People should only help with testing this if they're able to tolerate regular kernel panics and various hardware functionality not working. We've done basic testing of Wi-Fi, Bluetooth, cellular, GNSS, Vulkan and virtual machines via the Terminal app and microdroid API but there's far more to test. If you're interested in helping with testing, please join either our #testing:grapheneos.org channel on Matrix or #testing on our Discord server. We've posted links to over-the-air updates for each of the 4 releases in both channels. These are production builds signed with the official signing keys. Users can update to these from our current releases and update from those to future experimental and regular releases. Hardware functionality should be the focus. Bluetooth / BLE, NFC, assorted Wi-Fi APs / standards, DisplayPort alt mode, USB peripherals, USB host modes, GNSS and NFC are examples. These experimental releases have all of the changes from our current development branch and are security preview releases with the security preview patches from our previous release. We have 4 official build machines so we can build for all 4 devices in parallel and make new releases as people test. Do not install the experimental releases unless you can tolerate regular freezes, kernel panics and broken hardware functionality. These are highly experimental and you should not expect the device to be very usable during the early testing. We'll make new releases with fixes for discovered issues.

Yahoo resolved this at some point on October 23rd after we posted this thread. Emails from our discussion forum and attestation service have been getting accepted every day since then. Thank you to whoever got this fixed. It was the last known email issue with our new IP space.

Google made a change to their RCS service breaking using it for a small number of users. It's likely in the process of being rolled out and is gradually causing issues for more users. We're already working on resolving it. It isn't caused by the OS update about to move to Stable.

Our discussion forum is updated to PHP 8.5.12 and has been available again for over an hour: discuss.grapheneos.org/

Our discussion forum is the only software we have using PHP. We've taken it down temporarily while waiting for the patches for php.net/archive/2026.php#202… due to vulnerability details already being available and proof of concept exploits being developed. Don't want to take the risk.