The GrapheneOS folks are working with Motorola to have Graphene pre-installed on one of their phones. It would be the first time it is officially usable on anything but a Pixel. It won’t solve the problem described in the OP though. It’s still Android.
Afaik GrapheneOS won’t be affected, neither will e/OS. The real problem with them still being based as AOSP is, that google might stop the AOSP project. That would mean the forks would need to do that continous based development themselves.
The GrapheneOS folks are working with Motorola to have Graphene pre-installed on one of their phones. It would be the first time it is officially usable on anything but a Pixel. It won’t solve the problem described in the OP though. It’s still Android.
Afaik GrapheneOS won’t be affected, neither will e/OS. The real problem with them still being based as AOSP is, that google might stop the AOSP project. That would mean the forks would need to do that continous based development themselves.
It affects Graphene because people using it still get their apps from Google Play, Aurora Store (also the Play Store), and F-Droid, etc.
I searched for statements from GOS and e/OS and what I found tells a different story
https://discuss.grapheneos.org/d/26337-android-developer-verification-are-we-screwed-no-doesnt-apply-to-gos/25 https://xcancel.com/GrapheneOS/search?f=tweets&q=certified&since=&until=&near=
https://community.e.foundation/t/e-os-statement-about-google-developer-verification/79892
Do you have different information?