Pinned Tweet
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.

motorolanews.com/motorola-three…
645
1,760
12,656
1,134,777
GrapheneOS Messaging version 17 released:

github.com/GrapheneOS/Mes…

See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.

Forum discussion thread:

discuss.grapheneos.org/d/43079-graphe…

#GrapheneOS #privacy #security #android
0
0
5
587
Google made a change to their RCS service breaking using it for a small number of users. It's likely in the process of being rolled out and is gradually causing issues for more users. We're already working on resolving it. It isn't caused by the OS update about to move to Stable.
18
64
1,046
68,776
Replying to @GrapheneOS
Resolving this before it impacts a much larger number of users is one of our highest priorities. It's likely only going to be possible to resolve it with an OS update rather than a GmsCompatConfig release. We've only just started working on it so we don't know the cause yet.
2
6
194
7,543
Replying to @GrapheneOS
Most of the people reporting RCS no longer working were able to resolve it by enabling the ICC authentication toggle. It's likely the requirement to have it enabled was rolled out to more carriers. The remaining reports may all be non-GrapheneOS-related.

grapheneos.org/usage#rcs
1
0
31
1,331
GrapheneOS retweeted
Replying to @tqbf
@tqbf @jonoberheide Both the TLD operator and registrar can take over DNS for any domain and obtain valid certificates from a CA. That's not CA misissuance. It will be logged in the transparency logs for all the good it will do. WebPKI is based on validation of control over DNS at one point in time.
3
3
79
3,918
Yahoo is still blocking emails from our newly assigned IP space. We've continued using it and aren't going to stop because Yahoo won't accept mails from it. It already has a great reputation elsewhere and there are 0 issues with anything else blocking it.

x.com/GrapheneOS/sta…
Yahoo is still blocking emails from our newly assigned IPv4 space (206.220.120.0/22). It's likely they're behind on updating their database of allocated IP space. It was already published via arin.net/resources/guid… and other providers have been accepting it for 2 weeks already.
21
37
1,063
25,473
GrapheneOS retweeted
Replying to @GrapheneOS
We'd appreciate if someone working at Yahoo could get it resolved. We're going to continue using our new IPv4 space for email since it works with Google, Microsoft, Proton and hundreds of other mail providers. We'll just block yahoo.com registrations on our forum.
4
8
266
13,347
GrapheneOS retweeted
Yahoo is still blocking emails from our newly assigned IPv4 space (206.220.120.0/22). It's likely they're behind on updating their database of allocated IP space. It was already published via arin.net/resources/guid… and other providers have been accepting it for 2 weeks already.
15
38
703
52,318
GmsCompatConfig version 178 released:

github.com/GrapheneOS/pla…

See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.

Forum discussion thread:

discuss.grapheneos.org/d/43045-gmscom…

#GrapheneOS #privacy #security #gmscompat
3
5
123
5,704
GrapheneOS retweeted
Replying to @pgattic1
@pgattic1 GrapheneOS is Linux. Linux is already enough of a problem without adding the mess of systemd, GNU, GNOME and similar software. We don't want any of that and it should be replaced on the desktop too. Linux should be replaced with a microkernel. It's all increasingly doable now.
34
55
1,116
35,067
Our latest OS release moved to using the Linux 6.18 LTS branch for both arm64 and x86_64 for the emulator, Cuttlefish and microdroid targets. We've made a highly experimental port of the Pixel kernel drivers to 6.18 and are planning on moving to it across all supported devices.
11
28
683
20,873
Replying to @GrapheneOS
We've successfully made an initial port to using the upstream LTS branch for Pixels. We need to do a huge amount of code review and fixing regressions. Once we have it shipped, it will become trivial to ship each upstream revision, although those do often introduce regressions.
1
1
44
2,151
Replying to @GrapheneOS
Shipping this requires a long term commitment to porting all the relevant Pixel and Motorola/Snapdragon kernel drivers to the latest upstream LTS code. We've determined that's much easier than expected. The hard part is making the device independent LTS with all the backports.
4
1
54
2,163
Replying to @GrapheneOS
In the past several months, Android's official Generic Kernel Image (GKI) branches have fallen behind the upstream LTS revisions. We're resolving this by moving all of the devices we support to the latest LTS branch and making a GKI replacement for the latest upstream release.
1
1
188
7,862
Replying to @GrapheneOS
We have a Pixel 7 working with the upstream Linux 6.18.58 release. We'll be getting all supported devices fully working with all hardware functionality. The upcoming Motorola flagship uses a fork of the 6.18 GKI LTS branch and we'll need to port it to the upstream kernel too.
4
0
164
6,369