@Lakotaubp I don't see how to view what channel I'm on - but I'll go to stable

@supaiku I was thinking to try to update with the desktop tool, but I'd rather not have to reconfigure my apps if that's gonna erase things...

If I'm on an old version with this broken updater, is my only option to refresh entirely with ubports-installer, or is there a way to update without losing my data/apps?

@Lakotaubp It downloads and then says it should restart.

the device build is:
lineage_dumpling-userdebug 9 PQ3a, 190801.002 181 test-keys

@Lakotaubp im on 20.04 - what is the update process supposed to go like?

When I go to update it says it needs to reboot, and does that andloads to fastboot or recovery, but there's no uodate option and no uodae happens.

Is my version broken or something?

oneplus 5t
Os build 2022-w51
I'd upload the about page but its a little tome consuming from this device

@Lakotaubp thanks for the suggestion. whats an appropriate alternative way to enag if I'm interested is support development like ports to other devices and decelopmentvelopment.

I don't have info, but this is the case on other devices like the Pixel XL. it's mentioned on a github issue here:
https://www.bountysource.com/issues/61605333-device-port-marlin-google-pixel-xl-1st-gen

It seems like they figured a work around?

The notes say:

Specific features
Dual-boot
This is an A/B device, so dual boot is possible: I'm currently running Android P in slot A along with Halium being installed in slot B.
TODO: Add dual-boot installation instructions
No recovery
A/B partition scheme means there's no recovery partition anymore. Instead, it's located in initrams of the kernel. At normal boot, bootloader puts skip_initramfs flag into cmdline and Android obeys that. Halium needs initramfs, as some scripts are run there, so there's a dirty hack in the kernel to ignore skip_initrams. Thus, installing TWRP will break Halium and prevent it from booting.
TODO: Research the way Android boots and replicate that behaviour in Halium

I think the answer might be:
Halium needs initramfs, as some scripts are run there, so there's a dirty hack in the kernel to ignore skip_initrams.

How important is the HDMI over USB-C thing? Is it still the case?

What devices that haven't gotten attention have that?

I would also love a Pixel Port...

Other than actually writing code, what would ya'll say the best way to support the Ubuntu Touch app ecosystem currently is?

Is anyone still considering working on this?

I haven't done any serious development but would love to see Ubuntu Touch development continue with newer devices and the 5x seems to be an affordable well spec'ed option - though it does have a history of hardware failures

Any ideas on how to spur development on this vein? Are there any good bounty platforms that could be used?
https://www.bountysource.com/
https://freedomsponsors.org/