Battery life is usually less than expected due to unoptimized software and processors clocking too high. On my devices, I set the CPU governor to 'powersave', which reduces power usage but also performance.
There are multiple scaling governor settings which might not be available on all devices (depends on kernel configuration)

• performance : high frequency; slightly increased performance and battery consumption
• powersave : low frequency; reduced performance and superior batter life
• schedutil : changes according to the scheduler (default on my device)

This command list the available governors to set for each core (should be more than those I listed above)
sudo cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors
Report which governors are currently selected for each core:
sudo cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
Set the scaling governor to powersave to every core:
echo "powersave" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

The commands above do not need mounting root as read-write, any change is reverted on reboot.
I tried to make an app for configuring these (a while ago) but I had trouble with sudo.

@ds2k5 You can enable the SSH server from UT tweak tool.

@Salah I believe it should work fine, as these icons neither large (to fill the partition) nor a dependency to something.
I had modified lomiri's qml by editing some files, and there wasn't any issue.
You can try, and if it fails reflash.

@mihael In the same directory normal Debian-based distros with NetworkManager do:
/etc/NetworkManager/system-connections/WIFI_SSID.nmconnection

@wally Just ported the app to 20.04, changing icons works!
This is the new repository: https://gitlab.com/ikozyris/custom-phablet-tools,
I plan to publish it to the open store if it works for others as well.
Took me ~2 hours.
I might add a way to add custom icons, currently they are downloaded from https://framagit.org/ubuntouch-fr-dev/custom-phablet-tools/raw/media/icons/[APP-NAME.EXTENSION].

@Salah I'm currently rewriting the backend to not require remounting as read-write. Currently this arm64 focal .click works. Screenshot:

@Salah said in Customizing Icons:

If you go to icons folder, you well see several icon folder with icons including the main one which if officially used (suru) and they are not used.

These are available if you click on the top-left icon. Select one from the list

Salah said in Customizing Icons:

have installed it, which apparently not available in Open Store

I submitted the app to the OpenStore, but I was suggested to rewrite the scripts so they don't require remounting the rootfs as read-write. I have made some progress, and the icon names had to be renamed. So the old versions don't work, unless it fetches the icons from a snapshot of a previous version. I can easily fix the hacky version temporary to work fully, but better way for the newer, cleaner method, which is WIP.

Salah said in Customizing Icons:

Is there any way I can Add my icons to this app !!

Yes, you have to rename your icons to match the names of those in the repo. Put them in a folder. Then write that path (absolute path and the last /) in the text box below

@Enrico13011978 But I have changed the backend to not require remounting root as read-write or sudo. I now call it Icon Changer, as I removed the wallpapers.

@kugiigi That is what Fdroid does, if I remember correctly. You submit an app via a pull request, a bot checks the source code and if everything is fine a person reviews the app and it is built on theirs servers from the git repo.

@pepijndevos I think with "Gallium" you mean Halium, which is indeed an abstraction layer between the android hardware drivers (blobs), not just LineageOS, and a normal Linux distro.

Although I don't know much about Sailfish OS, their stack seems close to ours, so you should be able to use most of their kernel code. It wouldn't be as simple as flashing a generic system image.

The rootfs is supposed to be generic, but from my experience every device needs different tweaks (so you can't just flash the rootfs), that is why the overlay method exists, which all new ports use.

You can try adapting the kernel sources to Ubuntu Touch, and then the rootfs probably from scratch. I couldn't find any port source code from Sailfish OS, as Ubuntu Touch has, which is of course necessary.

@cjengle said in Wanting to continue Nexus 5 Dev:

I have been using "clickable create" per Youtube and doc tutorials. Not sure if it's too much different than "clickable init"?

Sorry I meant clickable create not init, didn't have a computer in front of me and couldn't remember the exact command. Should have read the documentation (https://clickable-ut.dev/en/latest/getting-started.html) again.

@cjengle It is recommended to start from the clickable initial projects. Use clickable init create and choose accordingly. Then change on top of them, so you have an initial working hello world. As almost all apps on the Open Store are open source you can get inspiration from their source code.
What app are you missing and want to develop/port?

@jaxx To lower power draw you can change the governor to powersave, see this.

About the crashing qti service, since the device works properly without it working, I believe it should be safe to disable it (don't have a qualcomm device to test this). I thought UT 20.04 and onwards uses exclusively systemd and not init.rc?

@cjengle Yes, clickable now supports Ubuntu Touch 20.04 by default, where all command that had ubuntu have been renamed to lomiri. So, as your Nexus 5 is still on the old 16.04 release (there isn't a newer version) the command is ubuntu-app-launch.
You can configure clickable to use 16.04 by changing the manifest.json.

@cjengle lomiri-app-launch is a command on the Ubuntu Touch phone, not the computer.

TL;DR: use BTRFS or proxy the ZFS via NFS

@RJDan said in zfs on Ubuntu touch:

[...] better supported on linux, it seemed to be a clear win for zfs.

Well, unfortunately that is not the case, ZFS is not supported without adding kernel modules via DKMS. That is because of licensing issues which prevent it from being built-in the kernel like BTRFS and EXT4. DKMS cannot work on Halium kernels as they are based on patched downstream android kernel.

I thought FUSE was an option, but after trying to install it on my device I found out zfs-fuse is deprecated, and I couldn't make it work.

So the only way is to build the kernel with patches for the ZFS module, beforehand. This is however very complex and I wouldn't recommend it.

There is a workaround, to have a NFS/Samba as a proxy to the ZFS file system so that the UT device accesses the file system remotely.

The more straight-forward approach is to change the file system to BTRFS, assuming it meets your use cases. If you only need snapshots and backups, you should be fine.

@RJDan The problem in this case is worse than that of installing packages via apt (which has workarounds).
Zfs needs a dkms package installed which as far as I know cannot work in UT kernels. It should be possible however to compile the kernel with zfs support beforehand.
An other way is to use libfuse to have the filesystem in userspace to not mess up with the OS, you have to search how to do that on your own though.

Also, do you really need all the features of zfs or can btrfs work for you (which is in-tree)?

@jaxx If I understand your questions correctly:

1. cannot get the location with Python
2. USB-OTG
3. Hotspot source auto switch between WiFi/LTE

1
The expected way of getting GPS coordinates is via the Qt interface. You can however check out this Python script which among other things obtains the location, by searching in the output of the test_gps command

2
I remember usb devices working in Ubuntu Touch, could it be a problem with the specific hub?

3
You can theoretically write a script with nmcli/network manager, I will test later if the default hotspot service can work this way.

@saveurlinux Qt 6 is a problem as we are still at Qt 5.12

It should be relatively easy with a script using ffmpeg, either in Libertine or bundled in an app.
The following command should work:

ffmpeg -i input.mp3 -filter:a "atempo=1.5" output.mp3