Damus
GrapheneOS · 62w
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 upcomin...
GrapheneOS profile picture
Unfortunately, Android has made changes which will make it much harder for us to port to Android 16 and future releases. It will also make adding support for new Pixels much more difficult. We're likely going to need to focus on making GrapheneOS devices sooner than we expected.
128โค๏ธ17๐Ÿ‘€2๐Ÿ–ค2๐Ÿค™2๐Ÿซ‚2:flex:1
GrapheneOS · 62w
We don't understand why these changes were made and it's a major turn in the wrong direction. Google is in the process of losing multiple antitrust cases in the US. Android and Chrome being split into separate companies has been requested by the DOJ. They may be preparing for it.
beejay · 61w
LFG https://media.tenor.com/u124hDgyWY4AAAAM/dinhdaica132-high-five.gif
Ancap Revolt · 61w
Who could have seen this coming? Google does not like FOSS
High Heel King · 61w
Fuck
Wasted Potential · 61w
Please support #oneplus phones.
The Photonsphere · 61w
They're also implementing restrictions to #sideloading on #Android, which is a disaster (I run as much of my software as possible from F-Droid as possible)
MrWonderland · 61w
Please talk to Framework and maybe Fairphone about that. I think that could make a great combo!
steven8rown ๐Ÿ‘Š · 61w
This is unfortunate although taking the positives out, we may get a GrapheneOS device sooner than previously thought. ๐Ÿ‘Š
Klaus Vink Slott · 61w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqtva8g98fx0fks0pt38vr75tv02t30qd5ev7n5v7fcpl6t44hf7kq5fm8mr Would it be possible to port Graphene to another more open source friendly device instead? Something like #Fairphone or maybe other.
hrast · 61w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqtva8g98fx0fks0pt38vr75tv02t30qd5ev7n5v7fcpl6t44hf7kq5fm8mr switch efforts to Plasma Mobile?