Hey all!

First I wanted to say: I've been using the development channel on the Pinephone lately, and I've been super impressed with how fluid it is. I've tried some of the other distros on the Pinephone, and Lomiri / Morph Browser feel much better than Phosh / Epiphany / Firefox. So thanks!

Some questions from me:

1. There is an open issue on the Pinephone issues page regarding the amount of swap space available in the default UBTouch image. Which got me to thinking - if users wanted to test / try changing stuff like this (e.g. try enabling ZRAM, more swap, or even enabling a firewall like one of the above comments mentions), what's the best way to do so? AFAIK the root image is overwritten every update right? So if I'm on the development channel, and I want to play around with system level stuff, this means that every time I update I'd have to redo these changes, right? What is overwritten / reset during an OTA update?
2. Did y'all ever find someone to help with triaging bugs and such? I took a look at some of the ticket queues and honestly I don't even think I'd know where to start (albeit, a lot of that is due to unfamiliarity with your workflow / which tickets would be important). I can sympathize with the struggle contributors must go through to find tickets and triage duplicates and such. Do you have any high-level rundown of which tickets should live where, and how you'd roughly like to sort them? It may be easier to find help if people know the scope of what they're signing up for..
3. There was a recent post about having develop channels for arm64 devices. The Pinephone is ARM64 if I'm not mistaken, and has had a develop channel for a while. Was this mostly for Android-based, ARM64 devices that didn't have this channel before? What is "the normal release schedule" that Marius refers to in that post?
4. When developing apps for UBTouch (via clickable) the apps by default include some Qt components called the Ubuntu.Components 1.3. What are the scope of these components (and other Ubuntu.xxx libraries), and how specific to Ubuntu are they? E.g. are they a part of Lomiri, and are they something that e.g. Manjaro using Lomiri could take advantage of if someone packaged these Qt modules into something more generic / without Ubuntu naming? My thoughts are that while these seem indispensable to developing apps on UBTouch, it would make it a lot easier for folks if these same components could be used on other platforms, so an app on UBTouch could theoretically be packaged for other Linux phone distros as well. Note: I really don't think I understand these well enough to know if I'm abstracting this problem in the wrong way, so apologies if it sounds like rambling nonsense! EDIT: I thought it was weird, and eventually found this post. Seems these were supposed to be renamed to Lomiri.components at some point. How come clickable / the docker images don't have this rename? Looking at the repo it looks like this happened forever ago. Did I download the wrong docker images from clickable?

Anyways, I understand I've asked a lot, but I do appreciate the time taken to help clarify these points! I really appreciate the community being welcoming enough to answer questions like these, even if they've been asked before.

Hi all! I'm new to this community, thanks in part to the Pinephone UBPorts CE. Some questions in no order at all:

Will we ever see clickable desktop support ARM64 machines (e.g. Pinebook Pro)?

What are the expectations for moving to Wayland on UBPorts? Is it expected to eventually make Lomiri faster (in terms of responsiveness, or enabling GPU acceleration in apps, etc)? What do app developers have to worry about in terms of switching over?