GrapheneOS will remain usable by anyone around the world without requiring personal information, identification or an account. GrapheneOS and our services will remain available internationally. If GrapheneOS devices can't be sold in a region due to their regulations, so be it.
@GrapheneOS thank you team 🙏
@GrapheneOS good on you. Don't give in to the fascists and fearmongers.
@GrapheneOS thanks for fighting the good fight
@GrapheneOS This might screw up my plan to get a new Motorola with GrapheneOS preinstalled, but guarantees that I'll put it on as an aftermarket install.
@GrapheneOS can't you be forced by the government? or can't google restrict you an access one day?

@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.

@Xtreix @esp32 @GrapheneOS bans can always be made, what may happen and likely will is that some people will find ways around it. However bans are frequently effective in preventing most people to access what is being banned, specially in dictatorships.
@jonathan859 @GrapheneOS I wish there was a way I could install that on samsung devices.
@flyingpenguinMwauthzyx @GrapheneOS Well, even if Samsung was supported by GrapheneOS, Samsung just started locking the boot loader, so good luck getting it on there, lol. It would be cool for sure though, yeah.
@flyingpenguinMwauthzyx @jonathan859 @GrapheneOS Unfortunately, Samsung does not support the installation of an alternative operating system. If you do so, an electric fuse (e-fuse) will blow, which will disable all security features, rendering the device unusable, and reverting to the original OS will do nothing.
@Xtreix @jonathan859 @GrapheneOS so samsung has finally made rooting impossible?

@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.

@GrapheneOS

yeah ! Your right fuck their law!

@GrapheneOS do you have a list of non-Google devices where I can install this OS?

@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.

@GrapheneOS @michael So I'm guessing it will be optional on Motorola devices, not the default choice?
@GrapheneOS @[email protected] And this is why I've chosen GrapheneOS. It's the standards you set for yourself and your partners. Kudos to Motorola for stepping up! I look forward to this partnership.
@GrapheneOS will the new gtapheneos phones support att?
@GrapheneOS and now GrapheneOS and Fairphone could be the game-changer annoucement many are waiting for ☺️

@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.

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
@GrapheneOS important clarification, thanks for sharing.
@GrapheneOS What cannot be sold in a store can be smuggled.
@GrapheneOS eh, don't forget the asterisk of "only on supported devices." 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, but it still sticks in my craw a little that my pixel 6a is unsupported, even though the hardware continues to be needs-suiting and i don't want to contribute to the growing e-waste problems not than I need to.

I don't want to have to buy another new (or new-to-me) device just so i can get the kind of privacy and security that
ought to be part of modern Android to begin with (though that part's surveillance capitalism's fault, not yours)

@digitalCalibrator

> 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:

https://grapheneos.org/faq#supported-devices

GrapheneOS Frequently Asked Questions

Answers to frequently asked questions about GrapheneOS.

GrapheneOS
@GrapheneOS huh, i could have sworn i saw something that said it wasn't supported, but i guess I'm wrong! Thanks, now i just need to get the willpower and time to dump all my memes and photos and such so i can switch over...
@digitalCalibrator It's not one of the recommended devices for new purchases because it lacks ARMv9 security features and more important because it doesn't have enough support time remaining. 6th gen Pixels had 5 years of support from launch compared to 7 years for the Pixel 8 and later. Pixel 6a will be end-of-life after July 2027, possibly as soon as August 2027, and then it won't be getting important driver/firmware security updates or official support for new major releases.

@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.

@GrapheneOS so, I was about to give GrapheneOS a try on my Pixel6a. As it stands now, would that still work? And when would the potential changes in regulations start?

@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.

@GrapheneOS ok, thanks for this! Looking forward to try it out!
@Johan_E_M @GrapheneOS same support as Google provides (because GOS is depending on Google support for "proprietary blobs" and "drivers" specific to the hardware)
So just look at here https://endoflife.date/pixel
Google Pixel

Check end-of-life, release policy and support schedule for Google Pixel.

endoflife.date
@GrapheneOS
"So be it."
Yes, that's the spirit.

@GrapheneOS

Ageless Linux

Software for humans of indeterminate age. We don't know how old you are. We don't want to know. We are legally required to ask. We won't.

The fastest path to [age verification] noncompliance. Run this on any Debian-based system to convert it to Ageless Linux:

Installs Ageless Linux identity and a stub age verification API that returns no data. Preserves a thin "good faith effort" argument.

https://agelesslinux.org/download.html

Ageless Linux — Download

@GrapheneOS I hope for an affordable device (means for really really a lot of people) to support GrapheneOS. This could be a game changer.
@morph @GrapheneOS Just look for deals. Last November I bought the 9a, trading in an old Oneplus 7, for 180€. I would consider that affordable.
@Roxxor Wow ... that's indeed a nice price.
@GrapheneOS
Ah, when my Pixel 4a finally kicks the bucket, GrapheneOS will be the first place I look to find out what new phone I need to get.
@GrapheneOS will GrapheneOS come preinstalled on these devices, or will reinstalling be the only option?

@GrapheneOS looking forward to the partnership with Motorola but are you going to keep supporting current pixels (8, 9, 10)?

Asking this because I'm using a pixel 6 that will go EOL in October. As such, I might have to buy a new pixel soon, as I don't expect Motorola to ship new devices compatible with GrapheneOS by October.

Thanks!

@plf Yes, Pixels are going to remain supported and it will be a while before the Motorola devices launch. We launched experimental support for the recently launched Pixel 10a yesterday.

The initial devices with GrapheneOS support from Motorola will be 2027 flagships. We'll add support for new devices each year along with expanding to cheaper devices once those meet the requirements.

@GrapheneOS thank you very much for clarifying 🙂
And thank you very much for all the hard work!
@GrapheneOS
So muss das! Dickes Danke!
That's the way it should be! Big thanks!
@GrapheneOS Word!
Let's see how reliable Motorola really is if the sales figures don't satisfy the shareholders.
@GrapheneOS what this post is reacting against, precisely? any news about security?
@uriel it is in response to mandatory OS-level digital ID verification requirements imposed by several US states, in addition to digital ID implemented in the UK, and proposals currently floating in the EU spearheaded by Ireland in its Presidency, as well as a rash of digital ID-related commits in major FL/OSS projects such as systemd this week

@theodric

ok, so barking at the moon. Bye.

@GrapheneOS Does any law require that this info be sent to the OS developer / that the OS developers need to verify? I thought the Californian law doesn't stop the user from lying?
@GrapheneOS i love you grapheneos
@GrapheneOS will it be possible to have a device with a sd card ?