GrapheneOS

Open source privacy and security focused mobile OS with Android app compatibility.

Forum, Discord and Matrix:

[GrapheneOS @GrapheneOS]

We'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://t.co/8flkjD52Eg

[GrapheneOS @GrapheneOS]

@N104AP This is some kind of API change in Android 17 we haven't dealt with for our Log Viewer app yet that's breaking some forms of search. It hasn't been prioritized yet.

[GrapheneOS @GrapheneOS]

@DaryllSwer They'll say anything to attack us. They would happily justify the company they're supporting using GeoIP data which they likely do. They're attacking us for having server sponsors with support chat bots while justifying that company sending user data to OpenAI without consent.

[GrapheneOS @GrapheneOS]

GrapheneOS opposes authoritarianism. It's a core part of why we're building privacy technology as part of a non-profit open source project. We're opposed to it regardless of whether it comes from left, center or right. The flood of people lying about what we believe and have said won't change this.

Our beliefs are not defined by what people who use GrapheneOS or donate to it believe. We decide what's acceptable within our community and we do a lot of moderation. We don't police what's done fully outside it. We clearly won't only have users, donors and supporters with beliefs aligned with ours.

We don't usually allow much political discussion in our community unless it's directly related to GrapheneOS. Today has been a very good demonstration of why that's the case. Many people are unable to tolerate even a minor disagreement on semantics without being absolutely enraged over it.

[GrapheneOS @GrapheneOS]

@_trespaul It's a little part of a large wave of attacks which started several days ago. The attacks largely resemble what you can see throughout the linked thread. It's very focused on claiming we have views we don't by claiming people who use/support GrapheneOS having a view means we do.

[GrapheneOS @GrapheneOS]

@_trespaul Earlier in the thread, you can see typical highly inaccurate personal attacks on our team including promoting harassment content.

It isn't from any particular fediverse instance or group of people, it's across it. There are hundreds of people posting similar attacks on us.

[GrapheneOS @GrapheneOS]

GrapheneOS version 2026062800 released:

https://t.co/ICAN6FPugj

See the linked release notes for a summary of the improvements over the previous release.

Forum discussion thread:

https://t.co/pGknh2vjwi

#GrapheneOS #privacy #security

[GrapheneOS @GrapheneOS]

@commonman078 GrapheneOS has support for 21 devices from 5 generations. The older devices aren't supported anymore because those stopped getting the driver and firmware updates we need. Those also don't have anything close to the current era hardware security features we use to protect users.

[GrapheneOS @GrapheneOS]

@commonman078 We support the oldest Pixels receiving updates. The past 3 generations of devices get 7 years of updates from launch. People don't need the latest flagship device to use GrapheneOS, they can buy a several year old budget 'a' series. Other devices don't have what we need yet.

[GrapheneOS @GrapheneOS]

@ProfChocCaXe There will hopefully be a tablet from Motorola we can support within a couple years. It's unlikely there's going to be another Pixel Tablet we can support any time soon. A budget and premium version of a large tablet would be interested but small ones aren't as useful anymore.

[GrapheneOS @GrapheneOS]

@ProfChocCaXe GrapheneOS supports the Pixel Tablet but it's getting old and we don't recommend buying one anymore. It supports folding devices becoming a small relatively square tablet including 2 recent ones which are part of our recommend device list.

https://t.co/RU2Xpev5Hw

[GrapheneOS @GrapheneOS]

@FourToedJones Those are currently the only devices providing the updates and security features we need. That's why we have a partnership with Motorola Mobility to bring GrapheneOS to their future devices meeting our requirements. Other OEMs are welcome to make better devices supporting it too.

[GrapheneOS @GrapheneOS]

@wathws_ Those don't provide what we need. That's why we have an OEM partnership with Motorola Mobility to bring GrapheneOS to future devices meeting our requirements. We can work with more OEMs in the future but they'll need to be interested in working with us, it's mostly up to them.

[GrapheneOS @GrapheneOS]

@perkelix @lizar72718 Pixels have 7 years of update support from launch which we need for driver/firmware updates even on the budget 'a' series devices.

You have that backwards, Motorola's market share is mainly outside of the US. The non-folding flagship Motorola Signature wasn't launched in the US.

[GrapheneOS @GrapheneOS]

@perkelix Those don't provide support for running GrapheneOS. Samsung doesn't allow an alternate OS on their devices without crippling functionality. LG doesn't make Android devices anymore. There aren't other devices available meeting the security requirements which permit another OS.

[GrapheneOS @GrapheneOS]

@infogulch @nicolas_danelon JobScheduler deliberately doesn't offer much control over when jobs run because it's focused on saving power. There are other ways to run things at an interval but JobScheduler is nice because it supports only running the job when constraints such as an Unmetered network are met.

[GrapheneOS @GrapheneOS]

@infogulch @nicolas_danelon Our System Updater app has a built-in power optimization exception but that doesn't seem to change much about JobScheduler beyond avoiding App Standby buckets throttling it even more. We could reduce how much it happens by lowering the flex time to avoid as much coalescing.