Open source privacy and security focused mobile OS with Android app compatibility. Official chat channel is #grapheneos:grapheneos.org via Matrix.

Toronto, Ontario, Canada
Joined March 2019
Pinned Tweet
Our far better new Camera app has a new alpha build with improvements to video recording and support for scanning inverted QR codes: github.com/GrapheneOS/platfo… Most of our developers are working on Android 12 migration but we have an app developer still working on the Camera app.
2
6
0
69
Join #testing:grapheneos.org on Matrix (grapheneos.org/contact#commu…) if you want to help with testing the Camera app and more importantly the upcoming experimental releases for Android 12. Best to raise issues with alpha/beta releases in testing room before filing issues.
1
4
0
29
Android 12 port milestone has been created on our issue tracker for the remaining work to launch Android 12 GrapheneOS: github.com/GrapheneOS/os-iss… Finishing device support depends on official release of Android 12 for Pixels around October 18th but shouldn't require many changes.
0
2
0
1
Issue tracker for our new camera app is at github.com/GrapheneOS/Camera…. You can see the planned features and their priorities there. It'll be integrated into GrapheneOS shortly after we launch the port of the OS to Android 12 alongside AOSP Camera. AOSP Camera will then be removed.
1
3
0
19
Show this thread
GrapheneOS retweeted
Are you an Android developer? Here's your chance to get involved with one the most important FOSS projects in the world:
GrapheneOS is well into the migration to Android 12. Many unexpected issues have cropped up and progress is going much slower than anticipated. It's a better time than ever to start working on the project since so much work needs to be done over the next few weeks in many areas.
Show this thread
36
415
14
1,589
GrapheneOS retweeted
Network incident, October 13th, 2021
17
54
24
117
birdsite.xanny.family/ovh_status/statu… GrapheneOS servers will be disrupted temporarily due to something that went wrong with this. We're going to continue working on the Android 12 migration rather than stopping work on that in order to rush to work around this. Don't have resources for it.
Network and racks:: VIN/DC: We will do a maintenance on our routers on VIN DC to improve our routing. Maintenance is planned for 13/Oct/21 9:00 AM to 10:30 AM ( UTC+2). No impact expected, device will be isolated before the change. travaux.ovh.net/?do=details&… #ovh
2
2
0
46
This was an IPv4 routing issue for 90% of OVH and is resolved now. IPv6 continued working fine so people with working IPv6 largely wouldn't have noticed for the GrapheneOS sites/services. Should all be fine now which is good since we need to focus on Android 12 porting work.
0
2
0
22
GrapheneOS is well into the migration to Android 12. Many unexpected issues have cropped up and progress is going much slower than anticipated. It's a better time than ever to start working on the project since so much work needs to be done over the next few weeks in many areas.
9
75
8
383
Starting with making a development build of Android 12 GrapheneOS for the emulator via grapheneos.org/build is the best way to start. Most of the work can be done in the emulator. Since there aren't official releases of Android 12 yet, building for devices has extra steps.
2
2
0
69
Temporary instructions on using android-prepare-vendor with the Android 12 Beta 5 releases has been added to grapheneos.org/build#extract…. Our recommendation is to start with the emulator target. We also haven't yet finished initial device support for all of the supported devices yet.
1
0
0
49
Device support still needs to be completed and many of the significant features still need to be ported to Android 12. Certain features such as using full ahead-of-time compilation to fully replace the Android Runtime JIT and exec-based spawning have proven difficult to port.
4
0
0
50
Vanadium browser and Vanadium are already working properly on the early Android 12 branch of GrapheneOS. Chromium's Android developers did a great job with support for the new OS version this year. It launched in Chromium 94 before Android 12 was released so the WebView works.
2
5
0
82
In the past, they've only landed proper support for the new OS version in the public (upstream) Chromium after the new OS version launches. It then had to go through the entire 18 week release cycle to reach Stable. It's far smoother and friendlier to GrapheneOS this time around.
1
1
0
34
We're grateful to the people who made this happen and hope that it's the new norm. We'll poke upstream about it a few times every year as we did this time around to try to make sure it happens. It's usually very painful and we waste a lot of time getting working WebView builds.
0
2
0
41
birdsite.xanny.family/GrapheneOS/statu… GrapheneOS kernels are now based on Android 12 with our changes ported over to it. It's a small portion of the overall port. We're working on finishing up device support for Android 12 and migrating all of our userspace changes across all the projects.
GrapheneOS 2021100606 release: grapheneos.org/releases#2021…. See the linked release notes for an overview of the changes since the previous release.
3
10
0
61
Android 12 will likely be officially launching for Pixels on October 19th. We'll need to wait for the non-Beta firmware, device support code, etc. to finish porting to it. It's likely we can get nearly everything done before then so we'll likely be able to release shortly after.
1
6
0
68
GrapheneOS 2021100606 release: grapheneos.org/releases#2021…. See the linked release notes for an overview of the changes since the previous release.
1
7
1
40
We're increasingly going to be needing to deal with setting up in-tree kernel builds and configuration for modules and fixing their code to work properly when it's part of the kernel from boot instead of loaded by userspace in late boot. It's already a major hassle without GKIs.
0
1
0
23
Show this thread