@vverve I recently installed UT on my Nord N10 5g BE2026, and I am using a daily image which shows as 24.04-1.x (2026-02-17/2).

VoLTE works for me.

I'm using a Redpocket SIM on AT&T as my carrier.

@fredldotme / @mrt10001 Thanks for the information.

A lot of great work by volunteers!

@lk108 No, I just got Ubuntu Touch on this phone so it wasnt a space issue.

Maybe the porter knows why the fscrypt was set to v2. And was for a good reason

@projectmoon
Thanks. I had thought all /etc was mounted rw. I see that is not the case.

I mounted the filesystem rw and edited the file. It did allow the encryption. BUT, I think that may have broke the installation. While encrypting, it crashed the OS. Now after a reboot, I enter my password and it keeps asking me to setup the phone, like a fresh install.

DON'T do what I just did unless you want to loose data!

So I'm going to reinstall with a wipe.

I'm setting up a Oneplus Nord N10 with Ubuntu Touch, and I wanted to encrypt my home partition.

I'm running 24.04-1.x Daily

I went into Settings > Security & Privacy > Encryption

It ends up: Error Encryption failed. Please try again later.

In the journal I get:

[ERROR] fscrypt encrypt: kernel is too old to support v2 encryption policies\n\nv2 encryption policies are only supported by kernel version 5.4 and later.\nEither use a newer kernel, or change policy_version to 1 in /etc/fscrypt.conf.\n"

The kernel is 4.19 so there is no version 2 available.

I tried to edit /etc/fscrypt.conf but it is readonly. The file permissions are root:root 666 and it is not marked as immutable. I'm puzzled why root can't edit the file.

Any solution to allow encryption?

Thanks.

Mark

@triplemaya

You don't see the arrow on the right side of the text entry box?

I recently discovered the droidian project which is also using libhybris and halium. Is there any collaboration between Ubuntu Touch and Droidian.

@Pingu
Via fastboot flash an appropiate recovery and dtbo image.

I would use a TWRP recovery image, and a dtbo image from LineageOS.

fastboot flash recovery twrp.img

fastboot flash dtbo dtbo.img

Without flashing the dtbo, you won't be able to boot to recovery.

Please give us the old color scheme. Wow, this is hard on my eyes.

@chris_bavaria
Sorry, I for some reason thought you were on 20.04. I'm surprised that systemctl commands work on 16.04 which uses upstart hence the service command.

Is something else using the port 22? Does the netstat command work? - I don't have quick access to a Ubuntu Touch install at the moment so I don't know if that command is available.
netstat -tulnp

@chris_bavaria

systemctl enable ssh means to start the service at boot time. So if you reboot the phone after entering that the ssh server daemon would start.

But, you don't have restart the phone to start the ssh server daemon, you can just enter
systemctl start ssh

If you want to do that in one step you can enter
systemctl enable --now ssh

@helium75

Did you mean to say that Fluffychat doesn't support encryption as in end-to-end encryption?

Fluffychat DOES support encryption. Checkout the information in this forum post.

Mark

@777funk In the US, all of the providers have turned off 3g service and voice over LTE (VoLTE) is required for voice calls. Ubuntu Touch currently does not have VoLTE.

Search the forums for VoLTE to see the discussions.

Maybe there is a bug preventing the OS from powering off the device.

Can you boot to recovery or bootloader and power off from there? That would help determine if it's a hardware or software issue.

Aren't all of the tablet Home Assistant dashboards just an Android tablet in kiosk mode with just the browser running?

I don't know if Ubuntu Touch has a kiosk mode, nor if you could lock it down to just the browser.

@cliffcoggin

You should open a bug report here .

Is your WiFi access point using 2.4 GHz or 5 GHz? I see 1 issue where Dalton states that the Nexus 5 has some issue with 5 GHz - although that bug report is about connecting not auto-connect.

@cliffcoggin please correct me if i have gotten the details wrong.

The phone has been connected to your WiFi access point. You have entered and saved the WiFi access point's password in the phone.

Now, on occasion (1 time out of 10 of leaving and returning to the WiFi access point's coverage range) the phone does not auto-connect to your WiFi access point.

On the occasions when the phone doesn't auto-connect to your WiFi access point, the neighbor's access point as well as your access point are listed in the available access points when the WiFi menu is opened. To connect to your WiFi access point, you just select it from the WiFi menu and the phone connects.

Is this what is happening?

@cliffcoggin

Do you have a password set on your WiFi access point?

If you disable WiFi on the phone and then re-enable it, when you force the reconnect to it do you have to enter the password?

It seems odd to me that your phone would prefer to connect to a WiFi access point you have never connected to over your own that you have connected to.

@richzrich Do you have adb and fastboot installed?

@hexis

Happy to hear you got it installed.

You should change the status of you post from unsolved to solved

Mark