That’s the thing… the Teracube 2e with the Google’d OS installed has a battery charge limiter built-in, the Murena Teracube 2e with /e/OS doesn’t.
As to the Battery Charge Limit app, I have an idea, but I’m not sure if it’d work.
Battery Charge Limit checks for supersu at the very first of its startup. That’s why it needs a rooted phone.
If we had a supersu ‘spoofer’ (something which tells apps checking for supersu that it’s available), that’d keep the app running past that cursory check for a rooted phone.
Then, we’d have to convince the /e/OS developers to bring back Root ADB (which was in an earlier version, but it’s not an option in Developer Options now).
We’d use Root ADB to grant Battery Charge Limit the permissions it needs to run.
So Battery Charge Limit would start up, check for supersu, the ‘root spoofer’ would get it past that cursory check, and the app would have all the permissions it needs to run granted to it manually via Root ADB.
Thus it should run, even if the phone’s not rooted.
We could do the same for all the apps which need root… all we need is that stub of an app which falsely reports that supersu is available, and we need Root ADB back, and we need to figure out what permissions an app needs and grant those permissions via Root ADB.
I’m thinking specifically about AFWall+ here, which I’d love to get installed on this phone.