Build for Ubuntu Touch 20.04 Focal

Known issues:

• Behavior > Lomiri > Indicators > Date & Time > Show Events has no effect -> should be fixed soon on latest 20.04 devel/rc builds (and OTA-4 🎉)
• System > Make image writable > [Read-Write] Permanent (persists after reboot) only seems to work post-reboot if also .writable_device_image is created (while additionally making android image writable as well of course)?! The following are some of my older notes on this odd issue and I'm not sure where the bug should be filed on UT side:
  • Volla Phone X23 (vidofnir) and Fairphone 4 (FP4) with both having super partition as well as Volla Phone (yggdrasil) without one were tested as broken in this way on my end
  • initrd: mounting /dev/disk/by-partlabel/system (image developer mode) seen in dmesg, remounted as read-only after initramfs is exited, works on last stable 16.04 build without needing also .writable_device_image
  • it appears rootfs gets remounted as read-only due to /dev/root / rootfs defaults,ro 0 0 in /etc/fstab (which is auto-generated by initramfs, so even just removing it doesn't do the trick)
  • check if https://git.launchpad.net/~mattig-schauer/+git/initramfs-tools-halium/commit/?id=96606b6c1fed610dc09813398b55705a23796617 fixes this and propose similar solution upstream (except rw/ro instead of removing line)

To-Do (local changes, pushing tomorrow when committed and cleaned up):

• Set persistent custom GRID_UNIT_PX via lomiri-full-shell systemd user service config drop-in
• Restarting lomiri-full-greeter no longer leaves the shell in a weird state where not all apps launch etc
• Implement (temporary) USB mode switching between RNDIS/MTP via usb-moded D-Bus
• Fix (un)installing apps by communicating with com.lomiri.click D-Bus instead of using pkcon
• Fix Enable SSH access toggle with systemctl start/stop ssh and creating/removing /etc/systemd/system/multi-user.target.wants/ssh.service symlink to avoid read-only rootfs error from systemctl enable --now ssh.service
• Made testing scaling truly a test again instead of removing previously saved setting
• Drop mentions and functionality related to scopes, those are long gone from Ubuntu Touch these days (this doesn't necessarily have to be done in this MR)
  • !100 already exists, but I could include it here too if the author doesn't get back to it