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.

@flohack

Thanks for looking at the bug and finding a fix so quickly. You guys are awesome.

Mark

@richzrich Do you have adb and fastboot installed?

@fredldotme Is there a way to install version 0.9.6 (which doesn't depend on the Online Accounts feature) and manually create the necessary credential files so we can get GhostCloud working on PinePhone? It would really be nice to have access to my files, contacts, and calendar on my Nextcloud server.

Thanks.

Mark

On the PinePhone there are 4 update channels, the 3 usual plus the kernelupgrade channel.

• Which channel has the latest development packages? I'm especially interested in the kernel and ofono upgrades that were talked about in Q&A 98 on 10 April which will provide a more stable cellular modem connection.

• Where can we see package (kernel,ofono) changes as there is little activity in gitlab?

Thanks to all of the UBports contributors.

I have a Pixel 3a which I was running on the Development Channel. After creating the 2 APN's 1 for internet and 1 for MMS, I was able to send/receive SMS/MMS/Calls & data via LTE worked. I think that was on version 240, and it ran pretty stable for a few days. After updating to version 244 & then 246, I was unable to receive SMS/MMS although I could send SMS (I didn't tryp MMS). I was also only able to get about 18 hours of use with light to moderate use (mostly internet browsing and some texting, minimal calls).

I've since gone back to Android as I need my phone to work.

I'm in the U.S. using StraightTalk on AT&T.

I'm willing to re-install UBports to assist with troubleshooting.

Mark

@hexis

That is where Jumpdrive comes in.

• Burn the jump drive image to an SD card.
• Put it in your Pinephone and boot the phone.
• Connect the Pinephone to your computer via USB.
• Your computer should now show 2 external drives. - One is the SD card, and the other is the internal eMMC.
• Burn the Ubuntu Touch image onto the internal eMMC using Etcher or dd.
• Disconnect the PinePhone from your computer.
• Power off the Pinephone.
• Remove the SD card that has Jumpdrive on it.
• Power on your Pinephone
• Enjoy Ubuntu Touch.

@flohack I can confirm that my Nexus 7 2013 Flo on Release Candidate OS build number 2022-W06/1 the issue is resolved. - Morph-browser is working.

Thanks.

Mark

@yannesc This is probably RCS. I had this issue also.

I disabled the Chat Features in the stock Android Messaging App.

Messages >> | (Hamburger Menu) >> Settings >> Chat features >> Enable chat features

Mark

@moem Thanks. I'll be doing some reading at Rebble.io and then visiting Ebay.

Mark

@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