@gpatel-fr yeah, I have things to do but in the weekend I'll refine this more the only reason I'm not taking this down is because I'm doing it on mt FP5 and it has not exploded yet... so I may be good until the weekend.

@TheTrench said in Guide to charge limiting your Fairphone 5:

ld work (at least extremely similar if not exactly the same) on most devices, as this is very close to how I manage charge level on Arch on my thinkpad laptop. The exact sysfs path is different, (it's got BAT0 in the

i'd need to do some testing yes, but this could be implemented as a sort of universal way to charge limit UT devices, if its that wide-spread I might just add this feature in lomiri system settings under battery because this has actually come up during a devsync.

@gpatel-fr thanks a lot! after classes I'll make it safe by reading the maximum first from wherever thats stored.

EDIT: at least on FP5 it seems to draw the same amount if I set it to a large value then if I restart (resets it) so FP5 should be safe currently, again will make it safe though I do not like to trust developers edge case fallbacks to not blow up my phone.

@gpatel-fr don't want the bash script in the user directory.
this is because I mess with the user directory a lot, I didn't change it for the guide because this is a proof of concept and if I have a known good I will use it.

I opened an Issue on this for indicator-upower fork, paulcarroty (the developer) is aware.
and I am mostly counting on him to make this into something useful because he already has an app for it.

@MrClayPole no Lomiri does not like more then one monitor.
didn't stop me from trying, it made for a cursed mirror setup where on screen is having a stroke and the other was perfectly fine.

@mikirc it works in Noble, just the overlay for the OSK is broken.

I am doing work on NixManager and cannot two time it with uWolf right now but I will get to it after I finish with that.

I AM NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER TO THE EXTENT LAW PERMITS.

EDIT: there is a edge case that lets the battery continue charging it seems easy to fix so I'll do so tomorrow, for now just use slow chargers. (or make sure to unplug/replug the phone after it stops charging from there it will work fine)

I'll start by saying I have no idea if this works for Focal but I haven't tried so it may work.
also this is a proof of concept you may want to refine this by using a udev rule or whatever else this is just how I got it working the first time so its a known good.

essentially there is something called user_fcc my take is that the fcc part is "full charge capacity" you can essentially tell the device that it actually has a smaller/bigger battery with this, I did tests on this however and either its using different units then charge_full (which is how you get the battery capacity) or its something else entirely, the point is that if set to 0 battery stops charging if set to big number like 10^6 battery charges again.

so... heres my setup I did for the proof of concept.

first start by running:

sudo mount -o remount,rw /

this is to remount read-only root as read/write.

make a file and name it charge-control.sh and put it in the /usr/bin directory ( /usr/bin/charge-control.sh)
change THRESHOLD to whatever percent you want to stop charging at, I put it on 80%

#!/usr/bin/env bash

# Path to capacity file (adjust if needed)
CAP_FILE="/sys/class/power_supply/battery/capacity"
UFCC_FILE="/sys/class/power_supply/battery/user_fcc"
FULL_CAP_FILE="/sys/class/power_supply/battery/charge_full"

# Threshold to compare against (integer 0-100)
THRESHOLD=80

# Commands to run
ON_GE="echo 0 > ${UFCC_FILE}" #echo Battery >= threshold: do X here
ON_LT="echo `cat ${FULL_CAP_FILE}` > ${UFCC_FILE}" #echo Battery < threshold: do Y here

# Trim whitespace and ensure integer
capacity=$(tr -d ' \t\n\r' < "$CAP_FILE")
if ! [[ $capacity =~ ^[0-9]+$ ]]; then
  echo "Error: capacity value is not an integer: '$capacity'" >&2
  exit 3
fi

# Compare as integers
if (( capacity >= THRESHOLD )); then
  eval "$ON_GE" && sleep 10 && "$ON_GE"
else
  eval "$ON_LT"
fi

exit 0

make sure you set executable permissions sudo chmod +x /usr/bin/charge-control.sh

now we make a system service to start this script, make a file called charge-control.service at /etc/systemd/system (/etc/systemd/system/charge-control.service)
and put this into it

[Unit]
Description=Battery charge control script

[Service]
Type=oneshot
ExecStart=/usr/bin/charge_control.sh
User=root

now we create a timer to run this every minute because we want it to enable/disable battery charging without us running the service manually.
so create a file named charge-control.timer in the same directory (/etc/systemd/system/charge-control.timer)
and put this into it

[Unit]
Description=Run charge_control every 1 minute

[Timer]
OnBootSec=1min
OnUnitActiveSec=1min
Persistent=false

[Install]
WantedBy=timers.target

then enable the timer by running these commands:

sudo systemctl daemon-reload
sudo systemctl enable --now charge_control.timer

you may also check that it is working with these commands if you want

sudo systemctl status charge_control.timer
sudo systemctl list-timers --all | grep charge_control
sudo journalctl -u charge_control.service

hope this helps y'all manage you're battery health better.

@haagch on morph it worked for a while on focal, but they seemed to make an update that just breaks it rn.

on uWolf its a question of how to get location working.

@domubpkm ofc the setting is there you can either enter you're own use the local network dns or choose from the presets provided by Librewolf.

@haagch i'm going on vacation today so development is going to be slower then usual combine that with the NixManager plugin for Noble which im also working on, and the fact i just moved all my devices to Noble in preparation for moving uWolf to Noble proper and i can't really do much about it.

but uWolf is janky like that because of Xwayland if the OSK gives you problems enter the wayland windows (the one with the icon and loading gif) it will redirect you back to the browser but in most cases will also unstick the OSK and make it work again, because somehow Xwayland "unselects" the window that is the browser.

@Vlad-Nirky Librewolf not uWolf, Librewolf itself uses it yes, i don't know if its over https for sure but it seems so yes.

@domubpkm by default Librewolf is going to use its own DNS, its usually Quad9 with no filtering.

@rdfrs thats because apparmor rules (waiting for fix to trickle down to stable releases ask @Fuseteam he knows about this better then me)
confinment is mostly done, not a priority though because it will not raise security as much as you think only make it clearer to you the user what i am doing on you're phone, which granted is a very good reason and is why im working on it. (there is a branch with confinement implemented im just waiting until it won't break the app to use)

@arubislander i would say option 5 is what you mean.

Hi someone by the name of AdamSchrey (on Github) created a bunch of nice Icons for uWolf and I would like to hold a vote on which one to choose from the icons he created the icons can be found here

EDIT: this will be the new logo, hope everyone is happy with the decision

@Simmonz this is the fix @TotalSonic is referring to (kind of) https://gitlab.com/ubports/development/core/qtmir/-/merge_requests/92
once this is upstreamed firefox and by extension LibreWolf will be able to use wayland directly.

once its upstreamed I'm also planning on releasing my freetube port.

@RJDan there is the same option but for cookies

Hi @theprivacydad Developer of uWolf here.
LibreWolf is focused on privacy and security, By default LibreWolf will delete cookies when closed you can change that in about:settings

copy/paste as mentioned already is one of many symptoms of being forced to use XWayland there is a fix on the way but until it is merged no dice unless you want to install it through the qa tool and remove the XWayland flags from the launch script in uWolf but I would not recommend that.

@RJDan the copy/paste thing is going to be solved when this fix roles out, as it is a symptom of using XWayland.

As for erasing all tabs LibreWolf is privacy/security focused so this is default behavior, you can turn it off in about:settings

@RJDan hmm, i may be able to do something about syncing passwords, but it would require cooperation from the UT development team.
no promises though I already have my plate full with the upcoming rewrite of uWolf for Noble and NixManager plugin for lss (which i'm waiting on a test device so i can start working on the UI)