We have a partial port of GrapheneOS to the Pixel 11 series after a week of work on it. We're unable to complete the port due to lack of support for ARM hardware memory tagging in software, firmware and near certainly hardware. It appears Google cut an important security feature to save money.
The hardware requirements are public. Those manufacturers have chosen not to implement supported hardware, which is step 0.
There is also a maintenance burden for the GrapheneOS team. The ROM requires kernel patches and driver work that makes supporting additional phones intensive work.
Why would manufacturers choose to meet GOS’s extra requirements?
There needs to be a give and take. It seems like GOS’s mantra is their way or the high way, which isn’t collaborative in the slightest.
Can there not be discussions held between Linux and sustainable/repairable OEMs and GOS to start integrating each other’s requirements? Diplomacy/negotiations/working groups are just completely neglected?
Those also don’t meet the hardware requirements
But why can’t GrapheneOS work with those companies to ACQUIRE the right hardware requirements, rather than leaning on a corporation?
The hardware requirements are public. Those manufacturers have chosen not to implement supported hardware, which is step 0.
There is also a maintenance burden for the GrapheneOS team. The ROM requires kernel patches and driver work that makes supporting additional phones intensive work.
Why would manufacturers choose to meet GOS’s extra requirements?
There needs to be a give and take. It seems like GOS’s mantra is their way or the high way, which isn’t collaborative in the slightest.
Can there not be discussions held between Linux and sustainable/repairable OEMs and GOS to start integrating each other’s requirements? Diplomacy/negotiations/working groups are just completely neglected?