Post Atp4FyYRbznUkshHtY by GrapheneOS@grapheneos.social
(DIR) More posts by GrapheneOS@grapheneos.social
(DIR) Post #Atp4FyYRbznUkshHtY by GrapheneOS@grapheneos.social
2025-05-06T16:23:42Z
0 likes, 2 repeats
We need an Android OEM or someone working at one to provide us with early access to the Android 16 sources in order to have a smooth port this year. We need this before June. We requested it to help with this very difficult situation (see the linked thread) and still need it.https://grapheneos.social/@GrapheneOS/114359660453627718
(DIR) Post #AtqPM8lgqKUAMhdL60 by noodle@aus.social
2025-05-07T06:04:48Z
0 likes, 0 repeats
@GrapheneOS Is this something that gets easier with donations?
(DIR) Post #AtqPMA6druq6VyRaOO by GrapheneOS@grapheneos.social
2025-05-07T07:34:46Z
1 likes, 0 repeats
@noodle Not directly, but we do need donations for hiring people including more than developers so we can build out the GrapheneOS Foundation. That will help us get stuff like this going forward. We currently almost entirely spend money on paying developers but we should be hiring people to deal with more than development. It'd help us with getting valuable contacts and partnerships to get stuff like this instead of depending on someone seeing a public request and figuring out how to get us it.
(DIR) Post #AtvCSfbtK5RGLXdJnU by GrapheneOS@grapheneos.social
2025-05-06T20:43:38Z
0 likes, 0 repeats
GrapheneOS Foundation can sign an NDA for this. We can act as a contractor for an Android OEM or one of their contractors. We need this early access so that we can start early due to the developer who usually does most of it being unavailable. If you can get us this, please help.
(DIR) Post #AtvCSgTm5kXZ2eqLmi by GrapheneOS@grapheneos.social
2025-05-09T15:04:43Z
0 likes, 0 repeats
Since we still haven't received early access to Android 16 sources, we'll need to begin deciding which subset of the GrapheneOS features must be ported and which ones could be initially dropped and added back in the following weeks in order to keep doing full security patches.
(DIR) Post #AtvCSgzKCRmGcVbXxg by GrapheneOS@grapheneos.social
2025-05-09T15:06:18Z
0 likes, 0 repeats
For example, our 2-factor fingerprint unlock feature is going to be particularly hard to port due to massive changes to the lockscreen code in Android 16. We can drop it for the initial release and add it back later with user configuration being preserved so it works as before.
(DIR) Post #AtvCShS2TgkK3Z2Tia by GrapheneOS@grapheneos.social
2025-05-09T15:08:18Z
0 likes, 0 repeats
Without early access, our porting process is likely going to involve making an initial release with dozens of GrapheneOS features missing to get initial Alpha testing going, then adding back features alongside fixing many upstream regressions and a small number of porting issues.
(DIR) Post #AtvCShvSiIHXWonya0 by GrapheneOS@grapheneos.social
2025-05-09T15:11:13Z
0 likes, 0 repeats
In the past few years, we've typically been able to make an experimental release with all of our features ported within a day or two of the new yearly release being pushed to the Android Open Source Project. It tends to take a week to reach Stable, which was already too long.
(DIR) Post #AtvCSiKzBOhMnykMMa by GrapheneOS@grapheneos.social
2025-05-09T15:14:04Z
0 likes, 0 repeats
Over time, we've added many more features including ones which are harder to port including sandboxed Google Play compatibility layer, Storage Scopes, Contact Scopes, 2-factor unlock and much more. Some MUST be ported for an initial release, others could be temporarily omitted.
(DIR) Post #AtvCSj1WdEj4vueKfY by GrapheneOS@grapheneos.social
2025-05-09T15:23:46Z
1 likes, 0 repeats
We hired an extremely talented developer in 2021 who later became our lead developer. He was doing the majority of this porting work from 2022 on. He's currently stuck in a military training camp due to being forcibly conscripted so we need standard early OEM access this year.