Fair enough. I said “huge” because I guess some people care a lot. I personally don’t and have been on security preview releases since they started releasing them.
- 0 Posts
- 5 Comments
- other8026@lemmy.mltoOpen Source@lemmy.ml•What will you do after Android starts restricting FOSS apps?English1·9 months ago
- other8026@lemmy.mltoOpen Source@lemmy.ml•What will you do after Android starts restricting FOSS apps?English0·9 months ago
Not exactly. GrapheneOS has an OEM partner and has early access to AOSP changes that aren’t public. A huge downside to that is that security preview releases can’t be open source until after Google makes the code public.
- other8026@lemmy.mltoTechnology@lemmy.world•Google Confirms Non-ADB APK Installs Will Require Developer RegistrationEnglish1·9 months ago
GrapheneOS won’t be affected. The developer verification thing will be handled by another app and won’t be part of the OS. That app won’t have permission to block app installs or anything like that.
- other8026@lemmy.mltoTechnology@lemmy.world•Google Confirms Non-ADB APK Installs Will Require Developer RegistrationEnglish1·9 months ago
GrapheneOS will be fine without F-Droid.
I may be misunderstanding, but which push? The open source project was started in 2014 and was named GrapheneOS sometime in 2019. You may be seeing more about GrapheneOS because of the Motorola partnership, CalyxOS dying/being on hiatus (so many of their users switched to GrapheneOS), and recent news pushing people to use more private OSes.