@domubpkm uWolf should support DoH, it may even be default. For other apps, the standard linux way (edit /etc/resolv.conf) will always work, and this is what the script you are referring to does.

@Simmonz If you are familiar with mtk client you can unlock the bootloader from there too since Volla devices have mediatek chipsets.

@techwryte It has already been ported to raspberry pi 3/4. See rootfs builder repo. You can build the raspberry image yourself, or grab an older image . I think the default rootfs would also work if you keep the fat partition.

@oldpaint That's the default for Ubuntu 20.04, the new 24.04 images have gcc 13.

@ANDROID2468 There are images for pinephone, pinetab and pinebook. However both pinephone pro and pinetab 2 are supported, so probably the image works for both pro and non-pro?
An older (2023) image is certainly for both phone versions: https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/5124896891/artifacts/download?file_type=archive .

@ANDROID2468 Are you looking for this: https://ci.ubports.com/job/rootfs/job/rootfs-pinephone-systemimage/ ?

Did you fork the repo? If yes, you can push your commit to your copy. Then go to the gitlab ui and make a merge request (there should be a blue button to do that right after you push your commit).
You can also search for how to open a merge request in gitlab documentation and your favourite search engine.

@atarilinux The cp error is normal and happens on all builds, the actual problem is the last one. From my understanding based on an older discussion in the porting telegram group, the retrofitted partition is used for older devices which didn't have the new super partition. However, it shouldn't be impossible to get it working, as others got their device booting, mounting the android partitions is necessary only for getting the android container running.

Anyways, more experienced people are active on the telegram group, so you may want to ask them.

@atarilinux All modern UT devices already work with the super partition. I don't understand what you mean by "implementing" it, the only thing UT has to do is mount them, which is already done.

I am not sure of this is related, but have you formatedthe data partition to ext4?

@bbiw have you tried running lsof with firewall disabled or enabling ufw logs to see which port is being blocked?

@darshpreets There are many such examples, search for "server" in the forum. I remember uses like a web server and even some kind of location tracker in a car.
The system is very stable, considering phones rarely reboot, partly because of the read-only filesystem.
Although the read-only filesystem seems a limitation at first, there are workarounds for every problem which are ultimately more stable than without ro fs.
You can use containers to avoid interfering with the system, such as LXD from the snap package or the default Libertine container.

@liam I have already told you to check if the super partition contains system_ext_a (you can do that by running lsblk while in recovery). If not, skip that command and continue the installation manually.

@danfro I think I found the problem you faced. I put a checkbox in the button row to toggle read-only mode, and when read-only mode is enabled, the TextArea isn't transparent so it is always white regardless of the selected theme (dark/ambiance). This may be a Lomiri Toolkit bug, inherited from the QuickControls' TextArea as that never changes the background color.

As an alternative, Text inside a Flickable can also work, but it doesn't allow selecting text, so you can leave it as-is.

@danfro What about the readOnly property of the existing TextArea? I tried it and it doesn't seem to have any limitation.

@danfro Why are you using a WebView instead of the normal Text type? If the user uses html shouldn't they open it in the browser instead?
It's much simpler (and faster) to use a Text type.

@faveoled If you need custom tooling use this configuration option as shown in the sample deviceinfo file.

@RJDan I don't know about a gui, but dd is preinstalled in every linux system so you can try that. There is also the ISODrive UT app which could work for you, but it doesn't do exactly ehat you want.

@Pingu The bootscreen is device specific, on the FP4 it is in the splash partition. However, someone has to customize it and convert it to the suitable format (it isn't as simple as editing a png). If you want to give it a try you can use this tool from XDA forums.

@lakeview said

It seems that heimdall-flash is for Samsung phones, although I downloaded the UBports Installer from the Google Pixel 3A XL page.

Every UT device uses the same installer, be it Samsung or Google, so of course the installer will depend on that package. If you don't want to install that, use the appimage.