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.
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.
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.
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.
GrapheneOS will be fine without F-Droid.
That’s because they’re the only ones that meet the project’s requirements at the moment, but that may soon change soon. Maybe you’ve seen the news that the project is in talks with an OEM for them to meet the requirements and have official support for GrapheneOS for some of the existing devices.
The way profiles work right now makes a decoy profile not work properly. GrapheneOS developers don’t add features that can be defeated by basic training.
Last I heard, the way the developers want to do it is add an early boot passphrase and then a decoy setup would be possible without leaving a way for attackers to be able to know for sure that a decoy feature was used.