| ▲ | rustcleaner 4 hours ago | |||||||
While yes I am on GrapheneOS' side on these issues, I'm surprised nobody clones the GrapheneOS repo and simply disables the minimal handful of features which block it from working on devices. Maybe calling the clone CarbonOS? If MTE is required to boot GrapheneOS and Fairphones don't have MTE, then Fairphone clones GrapheneOS and disables MTE for its images. Graphene has so many features beyond just hardware security that other Androids lack, that it would be worthwhile to do this and it would still be higher security than the others (even if it's below GrapheneOS' own full security). Sensor & network permissions, storage & contact scopes, autoreboot, scrambled pin, radio auto-off, MAC address randomization, and more, I'm sure don't require MTE or Titan etc. Just follow GrapheneOS as upstream, making sure that the minimal set of changes needed to get it working on other/older devices transfers with the new updates. | ||||||||
| ▲ | pferde 4 hours ago | parent | next [-] | |||||||
Lack of MTE is not the only huge reason why the GrapheneOS team refuses most devices. Most vendors' lack of timely bugfixes for device-specific drivers and firmware, and no commitment to keep providing bugfixes for a number of years is another major factor. | ||||||||
| ||||||||
| ▲ | gib444 an hour ago | parent | prev [-] | |||||||
> I'm surprised nobody clones the G®apheneOS repo and simply disables the minimal handful of features which block it from working on devices. I wouldn't recommend that. They would be denounced by GOS (which is just idealism and purism and definitely not bullying – not at all.) Anything which isn't G®apheneOS is by definition technically inferior, wicked, insecure, privacy-invading and should erased from your device immediately. | ||||||||