Since we use towboot we can access our filesystem and fix stuff as needed
After an upgrade which seems to throw a fake 0% and shutdown command at bootup no matter what the battery charge level or plugged in status is;
I am looking for the file which flags shutdown at 0% battery, my battery is charged but now the OS thinks it is dead and will not see charging even done under towboot blue light mountable disk mode.
I have looked at (edited out my local machine to show location in PPp mobian trixie) these files
If I were to change the name of systemd-poweroff.service
could I temporarily 'break' the poweroff even if that is like using a 10Kg hammer on my system to get a live phone to run updates?
plan is to move-rename systemd-poweroff.service to AAAsystemd-poweroff.service run backups and then rename it back
(EDIT)
I did the above and rebooted, now I show 57% after charging from my computer while editing files, I will run updates and fix AAAsystemd-poweroff.service
no apt system updates yet, system is charging so I will wait until tomorrow and hope the un-glitch doesn't re-glitch.
After an upgrade which seems to throw a fake 0% and shutdown command at bootup no matter what the battery charge level or plugged in status is;
I am looking for the file which flags shutdown at 0% battery, my battery is charged but now the OS thinks it is dead and will not see charging even done under towboot blue light mountable disk mode.
I have looked at (edited out my local machine to show location in PPp mobian trixie) these files
Code:
/etc/systemd/logind.conf
/usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.power.gschema.xml
/root/usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.power.gschema.xml
/root/usr/share/polkit-1/actions/org.gnome.settings-daemon.plugins.power.policy
If I were to change the name of systemd-poweroff.service
could I temporarily 'break' the poweroff even if that is like using a 10Kg hammer on my system to get a live phone to run updates?
Code:
/root/usr/lib/systemd/system/systemd-poweroff.service
(EDIT)
I did the above and rebooted, now I show 57% after charging from my computer while editing files, I will run updates and fix AAAsystemd-poweroff.service
no apt system updates yet, system is charging so I will wait until tomorrow and hope the un-glitch doesn't re-glitch.