zlacker

>>tripdo+(OP)
GrapheneOS made an unforced error by exaggerating the situation. ("Boy who cried wolf"). When you're generic and obviously false in your criticism, it makes it easy for the company to counter it. "Google is killing AOSP" catches eye, but it is sooo easy for the company to counter.

What is going on is frustration. GrapheneOS has been relying on Google's good faith effort on providing binary blobs to Pixel in addition to AOSP to make their OS. Google was under no obligation to give that, and they stopped doing it for whatever reason.

To make things worse, GrapheneOS mentions legal/anti-trust blah blah blah, which means no engineer will touch / comment / help in the matter, and it gets routed to legal blackhole.

>>bitpus+v4
Now maybe GrapheneOS will expand to support more than just pixel devices, which, IMO, it already should be doing.

The hardware support is nice, but even without it it's still vastly more secure than stock android.

>>JCatth+V8
IIUC, GrapheneOS cares about being forensics-proof very much. And for Android phone forensics without consent, almost 0% of work are done after the boot chain ends. So it's all about firmware.

Non-Pixel devices usually require you to just give up secure boot, in this case a GrapheneOS install could be even worse than stock Android.