Powersave mode extrem

[Moem]

@Linus67 said:

I was monitoring the journal with “sudo journalctl -f” while I turned the Wi-Fi on and off.

Thank you! That's a bit above my paygrade.

[Linus67]

@Moem
As @uxes wrote

Run the following commands in the Terminal.

systemctl --user stop ubconnect-daemon.service
systemctl --user disable ubconnect-daemon.service
rm -f ~/.config/systemd/user/ubconnect-daemon.service
systemctl --user daemon-reload
systemctl --user status ubconnect-daemon.service

result:

Unit ubconnect-daemon.service could not be found.

[Moem]

@Linus67 As I said, the first two were what I did, after figuring out they might be helpful.
Can I be a little proud of myself for figuring that out? I'm not a terminal user at all.

[Moem]

@Linus67 said:

rm -f ~/.config/systemd/user/ubconnect-daemon.service

Thanks to this hint, I knew where to find it and removed it using the file manager.
All clear now!

The advantage of using the GUI in this case was that it showed me what else lived there. There was another daemon that was no longer needed. So that was helpful.

[uxes]

@gpatel-fr yes that is just missing thing of click packages since they don’t have some kind of postinstall and postuninstall hooks to insert and remove those systemd services

[gpatel-fr]

@uxes

It's a feature, taken from the click documentation:

4.3.2 Specification
• Only system packages (i.e. .debs) may declare hooks. Click packages must be declarativeinclude code executed outside AppArmor confinement, which precludes declaring hooks.

[Linus67]

@Moem If you're still experiencing increased battery drain when using Wi-Fi,
go to Wi-Fi -> Network Settings -> Saved Networks and tap “Forget” to remove all saved networks. Then reconnect to your home Wi-Fi network.

I also had a few stale connections here—sometimes even two Wi-Fi icons in the status bar.

[Moem]

@Linus67 said:

If you're still experiencing increased battery drain when using Wi-Fi,
go to Wi-Fi -> Network Settings -> Saved Networks and tap “Forget” to remove all saved networks.

Thanks... the truth of the matter is that I've just migrated to a different device. So there are no saved networks. But also I don't know the state of my current battery.

[Linus67]

@Moem
After clearing the saved Wi-Fi connections, power consumption is minimal.

[moodroid]

@Linus67 so what was the conclusion here for light users? Powersave or scaling? Suspension setting on or off? Thanks

[Linus67]

@moodroid The “Prevent background suspension” setting should be set to OFF. As described in the Ubuntu Touch Wiki.

By “Power Save,” I mean the following:

1. Set CPU cores to half load
2. Turn off Wi-Fi
3. Turn off mobile data
4. Turn off Bluetooth
5. Turn off location services
6. Enable 2G (optional)

With these settings, the device enters deep sleep mode and consumes less than 22 mA. (1-2% battery consumption at night) If this is not the case, you will need to check for faulty services or configurations that are preventing deep sleep mode. In my case, I created a script with a log file that records the power consumption of the idle device in a text file. It was always over 200 mA. Only after cleaning up faulty services linked to installations did the consumption drop to ~22 mA.

The battery on my 9-year-old Pixel 3a now lasts about 4 days with moderate use. I call it “NOKIA 3210 mode.” You can be reached via text and phone for days on a single battery charge. If needed, you can also take pictures, check emails and calendar events, send texts, or make calls, and all other features of a modern smartphone are available. (Navigation, internet, NextCloud, cloud music...)