I've installed now #GrapheneOS.

There were a few reasons I only tried GrapheneOS now. The main issue was purchasing a device - I didn't want to pay much if I didn't like Graphene, but I'm only interested in Pixels for GrapheneOS. I found #BackMarket is the best option for refurbished phones, especially since they deliver to Greece and other small EU countries, and deliver just within 3 days! As for eBay, I have found it is problematic.

#Graphene #mobileos #customrom #android #aosp #degoogle

@m7v Does any other brand works for GrapheneOS? Or still no other yet
@autumnstuff Only Pixels. It is so technically difficult to support every additional mobile device, especially for small-tech organizations, so, I understand it. They will still support only Pixels in the future. BTW, there are #NitroPhones which ship #GrapheneOS.
You may install #eOS or #iodeOS if you want a not-Google device, but it's unclear how it is secure, maybe it's just like iOS or stock Android. However, it is #AOSP-based mobile OS (so-called #CustomROM) like #GrapheneOS.

@m7v @autumnstuff No, that's not accurate. The reason we can currently only support Pixels is not about our resources or the difficulty of supporting other devices.

/e/ and iodéOS are extraordinarily insecure and non-private options. Both lag extremely far behind on extremely important privacy and security patches. Both heavily roll back the privacy and security model. Much more information including coverage by third party privacy/security researchers is available at https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private.

Devices lacking standard privacy/security patches and protections aren't private - GrapheneOS Discussion Forum

GrapheneOS discussion forum

GrapheneOS Discussion Forum

@m7v @autumnstuff /e/ and iodéOS are not in the same space as GrapheneOS at all. They're the opposite of privacy and security hardened mobile operating systems.

Neither GrapheneOS or these other projects are custom ROMs but rather they're mobile operating systems based on the Android Open Source Project (AOSP). Custom ROM is incorrect terminology and using it is problematic because it propagates major misconceptions such as the incorrect idea that they're modifications of the OS on the device.

@GrapheneOS Thank you for your clarifications :)

@GrapheneOS Thank you for your clarifications too:)

@autumnstuff I was never exploring security of /e/ (#murena) and #iodéOS, just met few average users of these "mobile operating systems based on the #AOSP" at #FrOSCon (in Bonn) and had very short talks with them about UI, features, etc.

@m7v Hey, yes, don't worry! I appreciate you :) Thanks!