HybridStatAnim8

The pixel tablet is still supported and will be until after June 2028.

The need for proprietary code for firmware and hardware is the same on desktop. Mobile is not unique in this regard. GrapheneOS is 100% open source.

Not passing attestation for certain services has no bearing on software being open source or supporting reproducible builds.

That is how most software works. If you do not wish for GrapheneOS to hold the signing keys to your OS, you may build the OS yourself.

GrapheneOS is 100% open source and supports reproducible builds. It is in no way a black box.

If you do not want anyone to hold your signing keys, you will need to stop using nearly all modern hardware and software.

That is not the case. It is significantly easier to the point it is entirely optional. GrapheneOSs privacy and security features do not make avoiding google more difficult.

On stock OSs, google signs major portions of the OS and is highly privileged, which is impossible to sidestep.

Optional is obviously easier than impossible.

Nearly everything works on GrapheneOS.

Sandboxed google play can only send the location to google if google services or playstore were granted the location permission. Accessing location for apps, including google, cannot be sidestepped as MicroG once allowed.

GrapheneOS lets you change aspects of location, including PSDS, SUPL, and network location. GrapheneOS also reroutes googlefusedlocation requests to the OS. If you would rather be able to turn it off entirely, GrapheneOS is is capable of this, not MicroG.

Because it is not ironic? You dont see how expanding trust and leaking location data are privacy issues?

No, it would not. That would require expanding trust to a 3rd party, and granting privileged access to software that downloads and runs google code. That software has also had issues such as leaking location to apps that dont have location access.

That would be an extreme reduction in privacy, not an improvement.

That is the meaning. The point of sandboxed google play is to reduce google services to the same unprivileged access all other apps get on android. Normally, google play is incredibly privileged.

Signature spoofing violates the android security model. It means giving privileged access to microG, which means giving privileged access to google. For a privacy project, granting 3rd parties privileged access is unacceptable.

GrapheneOS has 500000+ users, and that is with only pixels. Maby more are waiting for the compatible Motorola hardware.

GrapheneOS is not going to compromise on privacy or security, and so far, pixel devices are the only devices meeting the hardware security requirements. People have not had an issue taking that seriously.

GrapheneOS is and always has been a privacy first project.

MicroG is a sloppy and ineffective reimplementation of google services that does not meet GrapheneOSs privacy, security, and usability requirements. MicroG does not make you degoogled and is not a compromise between being degoogled and making apps work. GrapheneOS, with or without google services, has far better app compatibility.

If you need a functional smartphone that runs the apps you need while reducing exposure to google, GrapheneOS is the best option for that by far.

Running google code sandboxed is far more secure than running google code with privileged access. MicroG downloads and runs google code in a privileged context and has had many privacy and security issues like leaking location to apps that dont have the location permission.