@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.

@liam That's why I am asking if the partition exists. Maybe it has already been deleted. Otherwise you can try running the same command on Linux from the android SDK.

@liam Does that partition exist (within super)? If not then you can try running the installation commands (https://github.com/ubports/installer-configs/blob/45a723f31f401050327426128d5f0f2d5407eff0/v2/devices/FP4.yml#L137) manually.

@RJDan Have you tried the waydroid helper app? I think it has workarounds for some problems.

@Eric-H There hasn't been any commit since then, if you want to re-build with a newer rootfs, without doing it on your computer, fork the repository and trigger the pipeline. I don't think it will work, if it did then the developer wouldn't say he gave up on it.
(I don't have the device myself, just explaining the procedure for anyone wanting to test the images.)

@Eric-H You don't have to build them, they are already built: https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a/google-sargo/-/pipelines.

@RJDan You can encrypt them through terminal, the utilities are already installed. There are also apps on the OpenStore that can achieve this: tedit can encrypt text files, and enigma encrypts files with PGP, but it hasn't been updated for 20.04.

Was /data mounted correctly when you pushed the rootfs? Did you format userdata? Also, you seem to have overlaystore enabled but overlayfs in kernel is not enabled (unless I missed something).

Anyway, it is better for you to ask in t.me/ubports_porting, there are more knowledgeable than me people there that can help you, and real-time communication is preferred because porting can take a long time to succeed.

@arjune Yes, and make sure that /data is formatted to ext4 (with fastboot format:ext4 userdata) and mounted when you pushed it.

Be aware that the device will probably fail to boot on first try.

@arjune Yes, just flashing the 2 partitions is enough. Also, boot.img can be flashed in either bootloader or fastbootd mode, while system.img only on fastbootd (it is a sparse image).

TWRP says that boot.img is larger than target device

It should be flashed with fastboot flash boot boot.img, make sure deviceinfo_bootimg_partition_size is set correctly. TWRP is the recovery, I don't get how it is involved.

@captainfunk said in Ubuntu Touch Q&A 168 call for questions:

Are you thinking or planning to implement the screen rotation to 180 degrees ?

It depends on if the porter enabled it. The configuration file is located on /etc/deviceinfo/devices/<codename>.yaml. Taking the Volla X23 configuration file as a random example:

  SupportedOrientations:
    - Portrait
    - Landscape
    - InvertedLandscape

As you can see, there is no "InvertedPortrait" mode enabled. I don't know adding it below will work.

---

Edit: (sorry, just noticed the Q&A was 3 days ago...)

@arjune Don't use the halium-install script. Use only the commands at the end of the standalone kernel method.
Build:

./build.sh -b workdir
./build/prepare-fake-ota.sh out/device_genia_usrmerge.tar.xz ota
./build/system-image-from-ota.sh ota/ubuntu_command images

Install:
Flash boot.img to boot partition.
If you have systempart in your cmdline flash system.img to system, otherwise push rootfs.img to data partition as ubuntu.img.

---

As stanwood said, the telegram porting group is more active.

@Twigg Many questions indeed, I will try to answer them as accurately as I can, so if anyone knows more, feel free to correct me.

Before answering your questions, I think it is necessary to clear any misconceptions about the Android kernel.
Most Android devices don't support mainline Linux, so the upstream kernel can't work on the device, as it is missing specific drivers and device trees. That is because the SoC manufacturers (Qualcomm/MediaTek) use an older kernel as a base to test their new designs, and that old kernel is subsequently used by the device manufacturers (e.g. Fairphone). Of course, neither of them bother isolating the changes to create a pull request to upstream Linux (due to costs etc.). As a result, Ubuntu Touch developers have to do extra patches to make the downstream patched kernel work for them.

Does you mean that the FF5 did not support mainline Linux?

Yes, Fairphone officially didn't, but the community has (see the PostmarketOS port)

Why the change with FF6?

I don't know. Maybe they hope they can attract more Linux enthusiast (like us).

I wonder about the advantages/disadvantages to using mainline Linux vs the Hallum approach

Mainline Linux enables more flexibility and a desktop-like experience. However, it is more difficult to make everything work there, postmarketOS is a great example, as almost none of their devices currently support the same hardware features as they did on Android. Not even Qualcomm themselves have succeeded in fully working mainline Linux kernel, as the recent Snapdragon X Elite chips which were made to compete with x86 still don't have full Linux support.

Halium on the other hand uses the same downstream kernel as Android does, with some adaptations for Ubuntu. It also runs the Android drivers on an LXC container, which allows easier access to hardware. As you can imagine, this has limitations, as we can't change the Android drivers and pulling patches from upstream Linux can break functionality.

I presume that this amounts to a desktop equivilence to doing a clean install of Ubuntu, vs installing it in Windows?

I don't get your analogy. It would be more accurate to say that to install normal Ubuntu, you have to reverse engineer the Windows drivers. However, in Ubuntu Touch's case we can reuse the Android drivers as the Linux kernel remains mostly the same.

From what I have read above, it looks like there haven't been too many changes from FF5 to FF6, so perhaps that makes it easier for Ubuntu Touch to get released on the FF6?

Each device needs its own port, sometimes even devices with the same chip require very different ports. In this case FP6 seems vastly different hardware-wise than FP5 so I don't think they would be similar software-wise.