That’s really cool
1 Like
Yes, you are. chg_en is not a LED, it’s just hackily (and temporarily) exposed using the kernel’s LED framework. It does actually stop charging - it’s a GPIO line that is connected to BQ25895’s CHG_EN input. It’s completely unrelated to the actual red LED.
It’s the other way around! The red LED is directly controlled by BQ25895, so it can indicate real status of charging without software involvement. You can disable that and control the LED exclusively from software as well, but we don’t do that right now.
The actual red LED is exposed as part of rgb:status LED device.
A cleaner way to stop charging using kernel interfaces that are actually designed to do that would be to write 0 to /sys/class/power_supply/bq25890-charger-0/constant_charge_current (though this alone won’t stop precharging deeply discharged batteries from happening - you’d need to set precharge_current as well, though I don’t see much point in doing so unless you really need it and know what you’re doing).
4 Likes
This is very interesting. It has happened to me as well but for me it was because I either had put the phone on suspend (the the script didn’t get a chance to run) or it hit 100% before the 10 minute timer which is the service timer. Check the logs next time it happens and send it over. I’d be happy to troubleshoot with you 
1 Like
Hey thanks! Can you tell me which logs you mean? Terminal or any specific logfile?
1 Like
- run journalctl -u manage_librem_battery.service in terminal and grab the logs for the given time period your incident happened. ie it didnt charge
- go to Documents/codes/manage_librem_battery/logs and grab that day’s csv
(i so need to make log save location better)
1 Like
Hi after executing the journalctl -u command, it shows me the logs in the terminal, but my Documents folder ( Data/Documents) is complete empty!
Is there another location that you mean?
1 Like
Not data/Documents but just Documents it should be in your home directory. You can send me a dm with the information aswell if you want.
1 Like
Finally after an hour or so I managed to copy and paste the terminal prompts into a text file! The controls on the mobile screen are just terrible, I really should think about an adapter cable for a bigger screen. Hopefully this helps to find the error, Im so exited to try to use it as standart phone!
– Journal begins at Thu 2022-12-22 11:55:43 UTC, ends at Thu 2025-03-13 13:25:17 UTC. –
Mär 04 11:08:38 librem systemd[1]: Starting Manage Librem5 battery…
Mär 04 11:08:38 librem systemd[1]: Started Manage Librem5 battery.
lines 1-3…skipping…
– Journal begins at Thu 2022-12-22 11:55:43 UTC, ends at Thu 2025-03-13 13:25:17 UTC. –
Mär 04 11:08:38 librem systemd[1]: Starting Manage Librem5 battery…
Mär 04 11:08:38 librem systemd[1]: Started Manage Librem5 battery.
Mär 04 11:08:38 librem python3[5237]: /usr/bin/python3: can’t open file '/usr/bin/manage_libre>
Mär 04 11:08:38 librem systemd[1]: manage_librem_battery.service: Main process exited, code=ex>
Mär 04 11:08:38 librem systemd[1]: manage_librem_battery.service: Failed with result 'exit-cod>
Mär 04 11:08:39 librem systemd[1]: manage_librem_battery.service: Scheduled restart job, resta>
Mär 04 11:08:39 librem systemd[1]: Stopped Manage Librem5 battery.
Mär 04 11:08:39 librem systemd[1]: Starting Manage Librem5 battery…
Mär 04 11:08:39 librem systemd[1]: Started Manage Librem5 battery.
Mär 04 11:08:39 librem python3[5239]: /usr/bin/python3: can’t open file '/usr/bin/manage_libre>
Mär 04 11:08:39 librem systemd[1]: manage_librem_battery.service: Main process exited, code=ex>
Mär 04 11:08:39 librem systemd[1]: manage_librem_battery.service: Failed with result 'exit-cod>
Mär 04 11:08:39 librem systemd[1]: manage_librem_battery.service: Scheduled restart job, resta>
Mär 04 11:08:39 librem systemd[1]: Stopped Manage Librem5 battery.
lines 1-15
P.S. Ah first see now that the ciles are still incomplete. I need to find the journalctl extension which allows me to copy and save specific prompts directly into a file.
1 Like
If you run the command journalctl -u manage_librem_battery.service > log_file it will save everything in the log_file which you can grab and post. Also tell me the date and time it happened
2 Likes
Great we go it, thank you for this easy method, the one I wanted to use would be much more complicated! So now here is the log, it is a lot longer, but it is always only repeating those lines:
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Failed with result ‘exit-code’.
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Scheduled restart job, restart counter is at 3.
Mär 13 12:36:42 librem systemd[1]: Stopped Manage Librem5 battery.
Mär 13 12:36:42 librem systemd[1]: Starting Manage Librem5 battery…
Mär 13 12:36:42 librem systemd[1]: Started Manage Librem5 battery.
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Failed with result ‘exit-code’.
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Scheduled restart job, restart counter is at 4.
Mär 13 12:36:42 librem systemd[1]: Stopped Manage Librem5 battery.
Mär 13 12:36:42 librem systemd[1]: Starting Manage Librem5 battery…
Mär 13 12:36:42 librem systemd[1]: Started Manage Librem5 battery.
Mär 13 12:36:42 librem python3[851]: /usr/bin/python3: can’t open file ‘/usr/bin/manage_librem_battery.py’: [Errno 2] No such file or directory
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Failed with result ‘exit-code’.
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Scheduled restart job, restart counter is at 5.
Mär 13 12:36:42 librem systemd[1]: Stopped Manage Librem5 battery.
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Start request repeated too quickly.
Mär 13 12:36:42 librem systemd[1]: manage_librem_battery.service: Failed with result ‘exit-code’.
Mär 13 12:36:42 librem systemd[1]: Failed to start Manage Librem5 battery.
1 Like
Did you copy the python file to the correct location
sudo cp manage_librem_battery.service /etc/systemd/system/manage_librem_battery.service
sudo cp manage_librem_battery.py /usr/bin/manage_librem_battery.py
There should be /usr/bin/manage_librem_battery.py present. Can you check please?
1 Like
I have a folder named manage_librem_battery.service in my personal folder, it contains those the files and a readme file. I will move them by terminal, because the desktop right click menue appears when tipping on the screen, but I cant interact with it, it directlly disappears again.
EDIT: Ok I moved both of them there. I checked both folders and the files are now there. Before they werent. But I cant create new data for the journal. Will restart the phone and look tomorrow if this creates any new information in the journal.
1 Like
Make sure you follow the steps in the github repo readme correctly
1 Like
Seems to work now. The charging LED hasnt turned on while the desktop loading icon shows that it is conncected to electricity at 83%, so now it should drop to 60% and then start to charge it, right?
EDIT: Ok it seems to be a holding function, overnight it only drops by 1%, under normal circumstances, the battery could be at 100% now or empty if there is no cable plugged into. GREAT!!!
So now I cann finally attach the Anker Powerbank with he Velcrutape and try if I can make it useable in my daily life. But this was a big help now to make the phne useable, thanks!!
2 Likes