GrapheneOSWe'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.
https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/
🌸 Ⓐnarkitty lumi-nhac 
@GrapheneOS does this mean i will be able to get a degoogled motorola device in the future?
Alexia 
@alexia @GrapheneOS yeah, ofc the end goal is using a proper linux phone, to get maximal freedom and security
but having a degoogled android device is a step along the way. though i have been stuck at that step since around 2014
but having a degoogled android device is a step along the way. though i have been stuck at that step since around 2014
@lumi @alexia GrapheneOS and the Android Open Source Project are Linux distributions. We strongly disagree with the premise that glibc, systemd and GNOME are preferable to the much more private and secure AOSP software stack. Moving to the desktop software stack would be a huge regression for nearly everything we care about and focus on improving. It's already possible to run desktop Linux apps in GrapheneOS including GUI apps via the hardware virtualization support and there's a desktop mode.
witch_t *navi@GrapheneOS @lumi
me with a musl, openrc, and sway system looking over -- i think you're starting with the wrong premise here
me with a musl, openrc, and sway system looking over -- i think you're starting with the wrong premise here
@navi @lumi Where's the application sandboxing, memory safe languages, modern exploit protections, deep integration of powerful hardware-based security features and everything else we focus on in GrapheneOS?
Aside from any of that, the concept that the Android Open Source Project isn't a Linux distribution is wrong. Linux isn't the userspace software that's largely portable to other operating systems. There was a Debian variant using the FreeBSD kernel which is clearly not Linux.
@GrapheneOS @lumi
where's your vetted package repository and actually end-user verifiable system booting and bootstrapping (aosp taking 3 days to build on a fairly high end personal hardware makes it fail at that, hard, not to mention the cursed build system), and open community based development model (which google is dead set on removing from aosp)
where's your vetted package repository and actually end-user verifiable system booting and bootstrapping (aosp taking 3 days to build on a fairly high end personal hardware makes it fail at that, hard, not to mention the cursed build system), and open community based development model (which google is dead set on removing from aosp)
LisPi@navi @GrapheneOS @lumi > (aosp taking 3 days to build on a fairly high end personal hardware makes it fail at that
How was that ever considered reasonable? Astonishing and appalling.
How was that ever considered reasonable? Astonishing and appalling.