Powersave mode extrem

[uxes]

@Moem you might wanna know that more applications does this daemon copy thing and after uninstall the service is there https://codeberg.org/tautologia/ubconnect/src/branch/master/ubconnect/daemon/install.sh
for example that smartwatch app

[Moem]

@uxes Thank you for the hint... I took a leap of faith and ran systemctl --user stop ubconnect-daemon.service and got a command prompt... no errors. I took this as encouragement and ran systemctl --user disable ubconnect-daemon.service and it told me something with UBconnect in it was removed. I think that was probably useful!

As for smartwatch apps, I'm still using those, so they can stay.

[Linus67]

@Moem

I was monitoring the journal with “sudo journalctl -f” while I turned the Wi-Fi on and off. I noticed that when turning on the Wi-Fi, a connection attempt by the daemon fails.

sudo journalctl -f
Mai 20 19:14:25 ubuntu-phablet systemd[2850]: ubconnect-daemon.service: Main process exited, code=exited, status=1/FAILUREMai 20 19:14:25 ubuntu-phablet systemd[2850]: ubconnect-daemon.service: Failed with result 'exit-code'.Mai 20 19:14:30 ubuntu-phablet systemd[2850]: ubconnect-daemon.service: Scheduled restart job, restart counter is at 89.Mai 20 19:14:30 ubuntu-phablet systemd[2850]: Started ubconnect-daemon.service - UB Connect Daemon.Mai 20 19:14:30 ubuntu-phablet aa-exec[5041]: [5041] aa-exec: ERROR: Failed to execute "/opt/click.ubuntu.com/ubconnect/current/usr/bin/ubconnect-daemon": No such file or directoryMai 20 19:14:30 ubuntu-phablet systemd[2850]: ubconnect-daemon.service: Main process exited, code=exited, status=1/FAILUREMai 20

[gpatel-fr]

@uxes

dekko does it too.
IIRC every app that is installing a systemd service I have looked at don't remove it when uninstalled.

[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...)

[moodroid]

@Linus67 thanks - that’s great. So when you say set cpu cores to half load, how do I do that? Is that the powersave governor?

[Linus67]

@moodroid

This is my current script

#!/bin/bash
# ====================================================================
# NOKIA 3210 MODUS: CPU throttling + All offline services (Pixel 3a 24.04-1.3 rc)
# ====================================================================

if [ "$EUID" -ne 0 ]; then
    echo "ERROR: Please run the script using: sudo $0"
    exit 1
fi

echo "Enable Nokia 3210 mode..."

# 1. Force CPU cores into power-saving mode
for governor in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do
    if [ -f "$governor" ]; then
        echo "powersave" > "$governor"
    fi
done
echo "[✓] CPU throttling enabled."

# 2. Turn off Wi-Fi
nmcli radio wifi off
echo "[✓] Wi-Fi disabled."

# 3. Turn off location tracking (GPS)
sudo dbus-send --system --type=method_call --print-reply --dest=com.lomiri.location.Service /com/lomiri/location/Service org.freedesktop.DBus.Properties.Set string:com.lomiri.location.Service string:IsOnline variant:boolean:false
echo "[✓] Location tracking disabled."

# 4. Turn off Bluetooth
rfkill block bluetooth
echo "[✓] Bluetooth disabled."

# 5. Turn off mobile data
sudo -u phablet DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/32011/bus" dbus-send --session --type=method_call --print-reply --dest=com.lomiri.connectivity1 /com/lomiri/connectivity1/Private org.freedesktop.DBus.Properties.Set string:com.lomiri.connectivity1.Private string:MobileDataEnabled variant:boolean:false
echo "[✓] Mobile data disabled."

# 6. Greenline-Service stop at user level
XDG_RUNTIME_DIR=/run/user/32011 sudo -u phablet systemctl --user stop greenline.service 2>/dev/null
echo "[✓] greenline.service stopped."

echo "------------------------------------------------"
echo "Success! CPU, wireless modules and GPS are in sleep mode."
sleep 3

These script lines have been compiled from various sources and optimized for my Pixel 3a running UT 24.04-1.3 rc. Many thanks to the experts in this forum for their helpful tips on some of the commands.

[Linus67]

note: Block 6 can be removed if “Greenline” (Alpha Build) is not installed.

# 6. Greenline-Service stop at user level
XDG_RUNTIME_DIR=/run/user/32011 sudo -u phablet systemctl --user stop greenline.service 2>/dev/null
echo "[✓] greenline.service stopped."

[moodroid]

@Linus67 Thanks very much. Will try it out…