Manually enabling Bypass charging...

Gayan

Please add an option to manually enable bypass charging within a certain battery charge percentage(similar to Samsung's implementation) because the current 'dynamic mode'(or whatever its called) is no longer working. Thank you.

DeletedUser495

Gayan this forum is not the right place to ask for feature implementation that is hardly going to affect your battery lifespan which is dependent on the manner you use your device.

de0u

Gayan Please add an option to manually enable bypass charging within a certain battery charge percentage(similar to Samsung's implementation) because the current 'dynamic mode'(or whatever its called) is no longer working.

If the device has "Charging optimization" turned on, there is nothing else to do except wait. There are a couple of devices where "charging optimization" doesn't work right at present, but the developers are aware of the issue and are working on it.

https://discuss.grapheneos.org/d/24672
https://discuss.grapheneos.org/d/24609

Gayan

DeletedUser495

My pixel is four months old, I use it every day and has a 40 cycle count according to 'Battery Status'.

Gayan

de0u

I think giving user the control is the best solution here. Thank you for the updates.

DeletedUser495

Gayan that sounds about right and in two-three years your battery will be knackered regardless how gentle you have been with it.

de0u

Gayan I think giving user the control is the best solution here.

That makes sense in the abstract. But the GrapheneOS project does not operate in the abstract. Replacing the 80% "charging optimization" feature shipped by Google in AOSP would require development time, testing time, and then rebasing time and re-testing time for every release. The GrapheneOS project is focused on security and privacy, so features that are not security features or privacy features tend to be prioritized behind those. I suspect that if Google ships a user-settable threshold into AOSP then that will be shipped by the GrapheneOS team but that otherwise it is unlikely that a user-settable threshold will be developed and maintained by the GrapheneOS team.

Please note that I do not speak for the GrapheneOS project.

Gayan

de0u That makes sense in the abstract. But the GrapheneOS project does not operate in the abstract. Replacing the 80% "charging optimization" feature shipped by Google in AOSP would require development time, testing time, and then rebasing time and re-testing time for every release. The GrapheneOS project is focused on security and privacy, so features that are not security features or privacy features tend to be prioritized behind those. I suspect that if Google ships a user-settable threshold into AOSP then that will be shipped by the GrapheneOS team but that otherwise it is unlikely that a user-settable threshold will be developed and maintained by the GrapheneOS team.

Please note that I do not speak for the GrapheneOS project

de0u

I think you're right, my short experience with GOS has given me the same impression.