cloud1494 Since the feature already exists in lineage, wouldn't the code for it be easily ported to graphene?
Maybe yes, maybe no. A possible first step might be locating the code they use to do that (that alone might be some work).
I don't really see any downsides to this equation...
One downside which has been mentioned is the ongoing cost of maintaining each and every change as the upstream AOSP changes. For any given change it may be small, but likely not zero.
I understand it's been discussed before. I just don't understand why it can't be implemented. Care to shed some light?
Did somebody say it can't be implemented?
I think people have suggested that the (non-zero!!!!!) estimated cost is not justified by the estimated benefit, in the eyes of the people who have done the estimating and would be doing the work.
One option would be to find the code some other OS has deployed, port it to GrapheneOS, and then quantify how much work it takes to re-apply the change for a couple of upstream releases, including testing on 5 or so devices. Maybe that will turn out to be really cheap, in which case a pull request might work. Or maybe it would turn out to be hard.