I just noticed a feature on lineage that I think would be really nice to have on graphene. It's an option in the battery section of settings called "Charging Control", and it provides an option to limit your charge session to a specific percentage peak to limit wear on the battery. This doesn't seem like a feature that would add any security vulnerabilities, but would provide an increased QOL for people like me who care about longevity of device lifetime. I try to manually limit my charge sessions to 80%, but sometimes I just get too distracted and don't catch it in time. I would love this feature. Is it feasible?
Battery Charge Control
[deleted]
cloud1494 if you use a search function, you will discover that this has been discussed here a number of times and apart from smart plugs and a lot of misinformation it hasn't brought any meaningful resolutions. If you can't catch your phone before it gets to 80℅, remove it from the charger early. You can always top up at some point later.
He has a point that it would be a nice to have feature, but it's also understandable that it's not high on the priority list for GOS when they focus so much on security and privacy which is more important.
[deleted] I understand what you're saying. But since the feature already exists in lineage, wouldn't the code for it be easily ported to graphene? I don't really see any downsides to this equation... I understand it's been discussed before. I just don't understand why it can't be implemented. Care to shed some light?
[deleted]
cloud1494 from what I have read to limit battery charge on LOS root access is needed and that on GOS will unlikely be supported.
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.
@cloud1494 You really don't have to manually limit my charge.
You can use accubattery. It will notify you when your phone charged to a set limit. Just change the notification sound for accubattery in notification setting to listen the alarm. I use police siren sound.
I know that lineage OS actually has this feature, And obviously on some rooted phones, you can download apps that can also do it. So it would be nice if GrapheneOS had one built into it. I would love that to where you can control it, to whatever percentage you want for charging and discharging
It's in the issue tracker here: https://github.com/GrapheneOS/os-issue-tracker/issues/3213. Based on the priority label, it's not a high priority feature.
It may be added some day by GrapheneOS developers, but if this is a feature that the community wants, then it will be done faster if someone steps up and comes up with a good implementation that meets the project's standards.