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…
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…
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…
[delayed]
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…
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…
GrapheneOS is significantly more private, secure, and usable than LineageOS.
It doesnt change ever, regardless of who likes what, and this does not match the definition of brigading. Brigading is an offensive action that involves rallying people to abuse services and/or people. Mass reporting…
No, it isnt. It would be highly immoral and unethical to call a project private and secure when using hardware that fails to provide either of those things. Google pixels are the only devices that support the hardware…
No, it isnt. Brigading is leveraging community support to harm others. Asking people to help resolve wrongful reports is not brigading, nor harmful. The vouch button exists for a reason.
The security features are not niche, you are claiming that arbitrarily. The needed hardware security features are generic and industry standard, OEMs are just lazy and choose to ignore such improvements.
GrapheneOS is not obsessed with google. Other OEMs have simply failed to reach the needed hardware securuty requirements, which will soon change. GrapheneOS also is not interested with maximizing adoption above all…
None of this is true, you seem to be making it up for the sake of attacking them. Google is often criticized and has been for years. That was never a bannable offense from the community chats. Nobody from GrapheneOS has…
Motorola devices are the priority but they will support devices meeting the requirements. If pixels fall to do this, no support, but if they succeed, no reason to stop using them. Only time will tell.
They are not interested in shoveling corporate slop. They dont know why, and so, that is what they said. That is a commendable trait and google has many things to answer for. Being silent only serves to benefit google…
They had to, as many users were purchasing pixel 11 devices before support was announced. Announcing an unclear future is fine and transparency is appreciated. Simply ignoring the problem is not a solution.
Because google may have disabled it due to issues/errata. Google willing to enable it is a good sign it is fine, and at worst, affects stock OS as well. Google isnt answering GrapheneOS when they ask why it was…
Yes. That would remove the need to flash, which is a roadblock for many. Greenboot support and Auditor would ensure your install of GrapheneOS is genuine.
GrapheneOS is not interested in silencing themselves for the sake of greed and optics. Their image is built on explicitly not doing that. You are making a false dichotomy, and suggesting they give into sanitized,…
GrapheneOS has no relationship with Google.
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…
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…
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…
[delayed]
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…
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…
GrapheneOS is significantly more private, secure, and usable than LineageOS.
It doesnt change ever, regardless of who likes what, and this does not match the definition of brigading. Brigading is an offensive action that involves rallying people to abuse services and/or people. Mass reporting…
No, it isnt. It would be highly immoral and unethical to call a project private and secure when using hardware that fails to provide either of those things. Google pixels are the only devices that support the hardware…
No, it isnt. Brigading is leveraging community support to harm others. Asking people to help resolve wrongful reports is not brigading, nor harmful. The vouch button exists for a reason.
The security features are not niche, you are claiming that arbitrarily. The needed hardware security features are generic and industry standard, OEMs are just lazy and choose to ignore such improvements.
GrapheneOS is not obsessed with google. Other OEMs have simply failed to reach the needed hardware securuty requirements, which will soon change. GrapheneOS also is not interested with maximizing adoption above all…
None of this is true, you seem to be making it up for the sake of attacking them. Google is often criticized and has been for years. That was never a bannable offense from the community chats. Nobody from GrapheneOS has…
Motorola devices are the priority but they will support devices meeting the requirements. If pixels fall to do this, no support, but if they succeed, no reason to stop using them. Only time will tell.
They are not interested in shoveling corporate slop. They dont know why, and so, that is what they said. That is a commendable trait and google has many things to answer for. Being silent only serves to benefit google…
They had to, as many users were purchasing pixel 11 devices before support was announced. Announcing an unclear future is fine and transparency is appreciated. Simply ignoring the problem is not a solution.
Because google may have disabled it due to issues/errata. Google willing to enable it is a good sign it is fine, and at worst, affects stock OS as well. Google isnt answering GrapheneOS when they ask why it was…
Yes. That would remove the need to flash, which is a roadblock for many. Greenboot support and Auditor would ensure your install of GrapheneOS is genuine.
[delayed]
GrapheneOS is not interested in silencing themselves for the sake of greed and optics. Their image is built on explicitly not doing that. You are making a false dichotomy, and suggesting they give into sanitized,…
GrapheneOS has no relationship with Google.