yeah, really no problem with being dependent on google decision and the fact that a change in codebase can end grapheneos at all in one day?... Linux desktop is a gran-bazaar of projects that protect the users from this dangers, a better IMO example of good FOSS projects
Discussion
Not likely to be so fast as GrapheneOS also contributes to Android Security.
The bigger issue is the Pixel hardware, but we have a path out there if we can get scale.
So if Google does something breaking, and then breaking in hardware, could fork the software and then have hardware with control.
if google want to do something really breaking with android (like simply abandon the opensorce codebase and work on new android release like apple work on ios) it will need another google to fork this giant pile of code.
A small-scale team will need to rebuild on linux-dektoputils based phone like postmarketos or will start to pay with security technical dept.