@archigato GrapheneOS has an official long term partnership with Motorola and will support many of their future devices, not one. It will support multiple new Motorola devices every year. We aren't lowering our security requirements but rather their devices are being improved to meet our requirements. The reason GrapheneOS won't support their currently available devices is because those don't meet our security requirements. Currently, only Pixels meet our requirements.
@archigato looks like you better get on it!
"It is better to keep your mouth closed and let people think you are a fool than to open it and remove all doubt." --Mark Twain
@Flittermouse @archigato GrapheneOS is privacy project and privacy depends on security. We have very reasonable hardware security requirements which are listed at https://grapheneos.org/faq#future-devices. We only expect industry standard updates and security features. The only non-Pixel Android devices meeting these requirements don't allow using another OS. We're officially partnered with Motorola and they're making devices meeting these requirements with official GrapheneOS support.
@esp32 @GrapheneOS Supporting Pixel devices has become more difficult, which is why the partnership with Motorola is so valuable.
But AOSP is not Google and can be used without Google services, even though AOSP is, in a sense, tied to Google, mainly because Google is the largest contributor, you can create a mobile OS based on AOSP without depending on Google services.
You cannot ban FOSS, just as you cannot ban encryption and the mathematics used for it; you can discredit it, try to generate negative publicity, attempt to impose backdoors, etc, which is exactly what authoritarian and fascist regimes are desperately trying to do.
@flyingpenguinMwauthzyx @jonathan859 @GrapheneOS This has nothing to do with rooting; you cannot install another OS on Samsung devices.
Using root breaks Android's security model, and it is strongly discouraged on production devices. GrapheneOS does not support root and does not provide support for users who root their devices.
You can build GrapheneOS yourself with root support using your own signing keys, but you will not receive official support, and the device will need to be updated using your own signing keys.
@flyingpenguinMwauthzyx @jonathan859
Flashing custom ROMs on Samsung devices was never particular joyful given Samsung's Odin. And Samsung is shutting the door of bootloader locking. ๐ However, and depending on your use case (Say for example only saving notes offline and making photos, and not using LTE or WiFi) Replicant project may be useful for you for really old and cheap refurbished Samsung phones. YMMV. https://replicant.us/supported-devices.php #samsung
yeah ! Your right fuck their law!
@michael Pixels are the only currently available devices meeting the security requirements for GrapheneOS.
GrapheneOS has an official long term partnership with Motorola and will support many of their future devices:
https://grapheneos.social/@GrapheneOS/116159602850585685
We aren't lowering our standards but rather their devices are being improved to meet our requirements. Existing devices from every non-Pixel Android OEM lack important security features and don't provide the level of driver/firmware updates we need.
@gcheseaux Fairphone has made it very clear they don't care about providing serious privacy or security. We aren't going to be supporting their devices or working with them. They already chose a different path incompatible with working with us.
> I understand that manually backporting major security and system updates to "EOL" devices is too effort for what you probably see as a small number of potential users
End-of-life devices no longer receive driver and firmware updates. Porting major OS updates to them won't resolve the insecurity. GrapheneOS is for secure devices.
> my pixel 6a is unsupported
Pixel 6a is supported by GrapheneOS and will continue to be until it's end-of-life:
@digitalCalibrator You won't get decent security on a device not receiving driver/firmware updates. Pixel 6a is not end-of-life yet and is still fully supported by GrapheneOS. It's not one of the recommended devices for new purchases due to lack of recent security features and remaining support time.
The whole point of GrapheneOS is substantially improving privacy and security from the baseline. If Android included our current privacy and security features, we'd have a large set of new ones.
@Johan_E_M Pixel 6a is fully supported and works well. It's part of the oldest generation of supported devices and has an update guarantee from the OEM until at least July 2027.
Some of the laws we're referencing were already passed. It isn't going to result in any changes to GrapheneOS and it will remain available everywhere. Many other projects are making changes due to it or blocking downloads in regions passing these laws but we've determined there's no need for us to do anything.