So I gave it a try and set all the ownership in /home/phablet to phablet:phablet, and after a reboot the app actually found some of the new files. Looks like the app can't handle mpc files properly; or at least can't read the tags - they all end up in one "Unknown album" - but that's a different problem.

@bearbobs very cool

@kugiigi said in Manual ip parameters missing in wifi setup: I guess using nmtui/nmcli is easier It is for the idiots like me..... However I use a program to monitor my routers IP and MAC attachments so I can knock a device off if required and can access a device too if required.

@ikoz Actually the --help readout has "init" in parenthesis, that command works too

Hi @ezst036 To clarify what everyone is saying, you have to swipe out the lock screen if you don't have any code set. It's still necessary to unlock the phone. It just doesn't mean what you think it means.

This is a known issue and yes the workaround for now is to enable "save device info" which was the default prior the update anyway. There will be a fix so that rotation will always be saved.

@bbiw I would advise against doing any manual computation for the scaling. If you want to use the native toolkit, use grid unit and the toolkit's components so scaling would works automatically. If not, you could explore using QGuiApplication::setAttribute(Qt::AA_EnableHighDpiScaling); In any case, scaling can still be buggy in UT so you might also be hitting one. For example, there are apps where some elements have bad scaling once you connect to an external display while the app is already open, however the scaling is fixed if you open the app after the external display is already connected.

I wonder if could be related to a faulty charging port or cable? I was having connectivity issues with my OP5t, and it seemed like sometimes it was sometimes charging at a lower rate, despite using the Dash charger adapter or whatever. But then it became hard to charge at all, and eventually I had to replace the port (which thankfully wasn't too hard). Anyway, just a thought. Maybe try another cable for starters?

@MrT10001 i see thank you ill see if anyone filed a report with them

@jaxx About dataqti service, take a look at : https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-poco-x3/xiaomi-surya/-/merge_requests/21 About powersaving, please see : https://codeberg.org/EricHeintzmann/UbuntuTouch/issues/24 Any help will be welcome

@kaleido Great. If you plane to keep on UBT, you can join us in the Telegram chanel t.me/UTForMiatoll

@RJDan Not in UT, no.

I want to know whether we are going for focal OTA-9 soon. Or we are going to 24.04-1.1 noble directly.when noble is to be activated for normal users .Is it possible to use full potential of ubports installer in lomiri-desktop.Also kernel for lomiri desktop be upgraded to mainline kernel.

[image: 1749246080673-screenshot20250606_cropped.png]

Hi @drbsin Just as a reminder, it's always better to report issues on gitlab. On the forum you can try to find out if you're the only one affected by a specific issue or if you're looking for help to accomplish something. The forum is not suited for bug tracking.

@PiotrBujakowski Maybe could you try uWolf. It's in developpment but interresting. https://github.com/ChromiumOS-Guy/uWolf/releases/tag/v0.3.3

also maybe this isnt the app for that ...i have much more ....also lots of python usage so ill need to learn content hub more ...i know the docs but i like to talk about it

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.

@Moem Sorry, yes my translator didn't find laggy.. : but yes, indeed laggy : choppy, jerky... I edited above.

Updated: Now this script is almost unnecessary on Ubuntu/Debian or some Ubuntu/Debian based distros, it can still run the old script fine. But I still do this project so that other Linux distro users can still build without any problems.