GrapheneOS on Nostr: We did far more preparation for Android 16 than we've ever done for any previous ...
We did far more preparation for Android 16 than we've ever done for any previous yearly release. Since we weren't able to obtain OEM partner access, we did extensive reverse engineering of the upcoming changes. Developers also practiced by redoing previous quarterly/yearly ports.
Published at
2025-06-11 00:39:04Event JSON
{
"id": "348241cda4018a8dcb7a479158afad96439127f7b30391622315d9d1b0b31c4c",
"pubkey": "5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed",
"created_at": 1749602344,
"kind": 1,
"tags": [
[
"e",
"8f3d3577e1076167c1abaa9126cce90955322e228d75eeef120f0ce50c13c70d",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://grapheneos.social/users/GrapheneOS/statuses/114661939260321933",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.mostr.pub"
]
],
"content": "We did far more preparation for Android 16 than we've ever done for any previous yearly release. Since we weren't able to obtain OEM partner access, we did extensive reverse engineering of the upcoming changes. Developers also practiced by redoing previous quarterly/yearly ports.",
"sig": "377672866cb1d4a6584f0d922f0d41b2dcccfbe88d5aab6e834834fe8b56cfaa8e15bbcc2644c973d3c89b818ccccf3ad61ceb6e45dff15902bca0cf47a98ec2"
}
