@Alain Can you share a print screen of an example? Just so we can check if it is a post an admin deleted, or the user themselves.

@harrisonpatm Please do! And let us know how you get on.

@harrisonpatm said in How to Get LXD Running on Ubuntu Touch (Focal & Noble):

Unfortunately, didn't work for me. Snapz0r ran and rebooted the device, but afterwords snap still wasn't enabled.

This is on your Pixel 3a XL? And you are running an unmodified Focal (i.e. no additional packages installed via apt on the rootfs)?

@harrisonpatm said in Can I boot to tty/console only?:

I'm only exploring what else I can squeeze out of it, I don't think there's anything wrong with that.

Indeed, quite so! However, this is not the envisioned usage of the OS. You might be able to get it to boot into a console if you manage to disable the splash screen and also stop lomiri-greeter from launching. But you would need an external wired keyboard to operate the device, unless the Bluetooth service is also started early on.

While it may not be exactly what you asked, you might be interested in a post I wrote on installing LXD and running LXD containers on your UT device.

@harrisonpatm you probably want to try postmarket OS on your device for your particular usecase.

@developerbayman There are services on UT... there is just no streamlined or officially sanctioned mechanism yet to describe and bundle services as clicks. Different apps implement different solutions to this problem when they require it.

If the service only needs to be available when the main app is running, some apps launch the background service on startup and terminate it on shutdown. If the service needs to be running independently of the main app, then you could see the app deploying and hooking up systemd user service configurations on first run.

@developerbayman said in full python clickable app prototype:

i need to learn more about clickable service mechanism

That's easy. At the moment, there is none.

How to Get LXD Running on Ubuntu Touch (Focal & Noble)

Here's a rough walkthrough on getting LXD running on UT based on my experience.

If you're on Ubuntu Touch Focal, you’ll need to enable snap support first. Install Snapz0r from the Open Store, run it and initialize snap support. If you're on Noble you can skip this step, since snap support is already enabled.

Next, install LXD. I used version 5.21 specifically, because newer versions gave me trouble on the JingPad. You can install it like this:

$ sudo snap install lxd --channel=5.21/stable

Once LXD is installed, initialize it with:

$ sudo lxd init

Accept all the defaults except for the storage backend. When prompted, choose dir instead of zfs, which tends to be problematic in this environment.

After that, you need to adjust the default profile to allow nested containers and privileged access:

$ sudo lxc profile set default security.nesting true
$ sudo lxc profile set default security.privileged true

Now you can launch your first container. For example, to create one based on Ubuntu Noble:

$ sudo lxc launch ubuntu:noble noble-1

Wait for the container to boot. You can check its status with:

$ sudo lxc list

Once it's up, you can enter the container with:

$ sudo lxc exec noble-1 -- bash

At this point, you should be inside a fully functional Ubuntu container running on Ubuntu Touch.

@Alain A more pertinent question is, what do you expect from this tablet once Ubuntu Touch is installed on it? Most of the experience you gained operation Ubuntu on the desktop will not carry over to using UT.
Installing software vai apt is not supported. Software is installed from the Open Store. https://www.open-store.io. You could browse the apps on there to see if everything you need is there.

There are other options for installing software, but they all have their drawbacks and difficulties.

@Moem This user is the OP of this thread and is updating the 16.04 port to 20.04.

(I elect to attribute the somewhat condescending tone of their last post to be an artifact of translation)

@Ida_ I use Syncthing to get files to and from my devices.

@kuailexs Same goes for you :-). But thanks for answering the question.

@Moem no, I was talking about issues some have been having with other pre-installed apps, in this particular case, the music app.

@dlin please use English on this channel as a courtesy to our international audience.

@ptrkrysik I don't use waydroid myself. But there have been some permissions issues with other users who do use it, so that is why I asked.

@ptrkrysik Do you use Waydroid? Did you share / link your Pictures or Videos folder with the container? In any case, can you check the permissions in those directories?

@hankschwie there are probably other files in your home folder with the wrong permission. You might want to try recursively setting all files and folders in your home directory to ownership phablet:phablet.

Did you by any chance try to share (parts of) your home folder with the waydroid container?

@Moem Looks like it was lots of fun indeed. I've already blocked the dates for 2026.

@captainfunk unless those pictures were really important to you, none that are worth the hassle.

In fact I am not sure how to go about it with a phone.

On a laptop I would make an image of the partition I am trying to recover the photos from, and then work on that image with one of the linux file recovery tools that are available to download. But I would not really know how to get a phone partition imaged.

You see, the thing is, the longer you use your device, the bigger the chances are that those deleted files have already been overwritten by new data, which makes it harder, and eventually impossible, to recover what has been lost.

@pineheap Boot into UT as normal. Then start the Terminal app, enter your password or pin code to gain access. Next enter

sudo reboot -f recovery

Again enter you password / pin code (you will not get any visual feedback when typing). And you should reboot into recovery mode.

Although, I don't think that is the mode you need to be in to reinstall Android.

To enter the bootloader (which is the mode I believe you need to be in) do:

sudo reboot -f bootloader