While I’m a fan of GrapheneOS, I think it could still be considered “tied to Google” both due to it being based on Android, and also because it only runs on Google Pixel phones. Graphene focuses more on security, then on privacy, but not so much on reducing our dependency on Google’s software and/or hardware.
My understanding is that AOSP is still and will continue to be a thing. That’s Android. What Google has done though is put more and more new capabilities into Play Services, which are not open, rather than AOSP.
I hope someone will correct me or add better nuance though.
No. The latest changes by Google means all incremental work is now no longer visible to the public until a release is done. For most people and developers this shouldn’t make a difference.
As an example lets say I implemented features A, B and C and then did a release to v2. Before the changes you would see A get added, then B then C and then the release. With Google’s changes you will see nothing for a while and then all of a sudden see A, B, C and the v2 release all at once.
ilmagico@lemmy.world 4 weeks ago
While I’m a fan of GrapheneOS, I think it could still be considered “tied to Google” both due to it being based on Android, and also because it only runs on Google Pixel phones. Graphene focuses more on security, then on privacy, but not so much on reducing our dependency on Google’s software and/or hardware.
A_Union_of_Kobolds@lemmy.world 4 weeks ago
Yeah those are things on my mind too, especially since Google moved Android behind closed doors.
Deconceptualist@lemm.ee 4 weeks ago
My understanding is that AOSP is still and will continue to be a thing. That’s Android. What Google has done though is put more and more new capabilities into Play Services, which are not open, rather than AOSP.
I hope someone will correct me or add better nuance though.
idunnololz@lemmy.world 4 weeks ago
No. The latest changes by Google means all incremental work is now no longer visible to the public until a release is done. For most people and developers this shouldn’t make a difference.
As an example lets say I implemented features A, B and C and then did a release to v2. Before the changes you would see A get added, then B then C and then the release. With Google’s changes you will see nothing for a while and then all of a sudden see A, B, C and the v2 release all at once.