According to an article posted on xda-developers.com, developer Erfan Abdi, has "successfully created a GSI-esque, platform-agnostic Ubuntu Touch image that can be installed on any Project Treble compliant device."
Would you please talk briefly about the UBports Generic System Image (GSI) project and what the project may mean for the future of UT on modern (Android 9+) Android devices?
Not a question, but I just want to say...
Congratulations on your progress toward completing OTA-12! Amazing work!!
I suggest waiting a few months (preferably at least six months) to gauge whether GitHub will change for the worse in any way. If you notice changes for the worse, then plan an orderly exit at that time. But if you don’t notice any changes for the worse, no need to divert precious time from development.
Mir 0.32 release candidate discussed here. Note the logind support is nearly complete.
Would you please talk a little about the goals of the Waylandify project? In particular, is a complete migration away from the mirclient API among the goals of the Waylandify project, or will some of that migration work require a separate future project?
I'm not at all clear what Canonical is planning for their "Anbox Cloud" project. But if the project aims to offer a way to run some Android apps in the cloud (rather than directly on a Linux device), the project seems like a good thing for Ubuntu Touch.
Your initial thoughts on "Anbox Cloud" project?
@erlend said in Ubuntu Touch Q&A 67 Saturday 11th Of January At 19:00 UTC:
I hear last time that.. Mir is going to be replaced with Wayland....
The devs can clear this up better than I can, and so I defer to the devs for a more complete explanation.
But in the meantime, suffice to say that it's not quite correct to say that "Mir is going to be replaced with Wayland." (Mir is a display server, and Wayland is a protocol.) Rather, UBports is replacing the "old" Mir display server with the "new" Mir display server.
The "old" MIr display server used its own (non-Wayland compliant) protocol, while the "new" Mir display server is now Wayland compliant. As of about Mir 1.6, in addition to being Wayland compliant, "new" also supports the legacy protocol that was used by the "old" Mir display server. However, that legacy support will eventually be removed from Mir (probably starting from about Mir 1.7), hence the need to "Waylandify" Ubuntu Touch.
Questions for Q&A: Regarding your efforts to "Waylandify" Ubuntu Touch, have you had a chance to experiment much with moving libertine to use xwayland? And if so, what are your initial impressions regarding the difficulty of the project?
Not a question, but I just want to say...
Congratulations on completing and marking closed the Unity8+Mir upgrade project!
Question for Q&A: Based on your experiences developing for the PinePhone, are pure Linux devices (such as the PinePhone) expected to suffer from fewer bugs compared to ported Android devices that rely on hybris/halium?
From the Q&A 66 Blog:
Marius wanted to have some fun over the holidays so he played around with Focal – what will become 20.04 of Ubuntu. He wanted to see what had been added and removed. Lots has gone, so will need to be put back before we can use it. We will be basing on 20.04, so although fun it is part of our preparation for the future. At this stage we are just scoping out what will need doing.
Gizmochicken, PhoenixLandPirate and others asked a series of inter-related questions – for example, what will you focus after OTA-12? Is there a road-map? What about Nextcloud? Maybe we could create a few project areas and call for contributors around them? For example around the work needed to upgrade from 16.04 to 20.04?
@UniSuperBox and @mariogrip , I want to thank you both for discussing the above questions/suggestions at length during Q&A 66. Speaking for myself, I'm amazed with how much you've accomplished in such a short time, and I see lots of potential in the UBports team.
I understand what you're saying regarding the seemingly never ending need to change priorities, and not wanting to promise more than you can deliver. Even so, having worked in fields related to technology development (albeit not software development) for over thirty years, I continue to recommend that you, at the very least, publish your top priorities for the coming year, along with approximately when you want to achieve each of those priorities (with caveats, if needed). If for no other reason, doing so will help you to think through the most efficient path from A to B.
Sure, you'll almost certainly need to amend your timeline multiple times throughout the coming year. (And I, for one, won't fault you when you do.) But having your priorities written down (and published to community) will help you to keep yourselves on track.
So, once you get past OTA-12, I hope that, even if not a full roadmap, you'll at least publish a list of your top priorities for the coming year. And who knows, maybe a "unicorn" will find something on the list into which he might want to poke his horn. 
Is the current UT build for the VollaPhone using Halium 9? And if so, does the current UT build use the same vendor partition that is used by Volla's modified AOSP?
According to an article posted on xda-developers.com, developer Erfan Abdi, has "successfully created a GSI-esque, platform-agnostic Ubuntu Touch image that can be installed on any Project Treble compliant device."
Would you please talk briefly about the UBports Generic System Image (GSI) project and what the project may mean for the future of UT on modern (Android 9+) Android devices?
@rocket2nfinity That's great news. Thanks much for the info! Much appreciated!!
By the way, I hope that you (and others reading my reply to @Lakotaubp ) realize that my reply to him/her was intended, tongue in cheek, to "take the piss out of" my fellow native English speaking cousin.
@Lakotaubp said in PineTab Anyone?:
As a native English speaker I have learnt to . . .
Agreed and upvoted. But we here in the North American "colonies" spell it "learned" as opposed "learnt" as spelled by the original imperialistic speakers of English. 
@PINE64 I want a Linux device that can be used as a GPS device. This is possible with the PinePhone, but near as I can tell, the PineTab doesn't currently offer GPS. In the future, will PineTab offer GPS via an expansion board?
Regarding the PinePhone vs the newly announced PineTab, will they each be running similar UT builds? And if not, which build (PinePhone or the newly announced PineTab) will initially include more cutting edge features?
@TotalSonic said in Where is Firefox?:
You can install Firefox 76.01 in a Libertine container directly from the UBports default reposotories, and it works ok in OTA-12 in my tests. Relative to the UT native Morph browser pages in Firefox load much slower and scroll with much greater lag . . .
Thanks for the info regarding running Firefox 76.01 in a Libertine container. Genuinely appreciated!
And I commend you on your marketing prowess demonstrated by the Total Sonic webpage opened in your Firefox tab.
If I understood correctly, you mentioned during Ubuntu Touch Q&A 74 that the PinePhone no longer relies on the Mirclient API. Did I understand that correctly? And if so, currently, what are the largest obstacles preventing removal of the need for the Mirclient API from the builds that require Halium/Hybris?
Would you please talk a little about the goals of the Waylandify project? In particular, is a complete migration away from the mirclient API among the goals of the Waylandify project, or will some of that migration work require a separate future project?
How's the packaging of Lomiri Desktop for Debian coming along?
Not a question, but I just want to say...
Congratulations on your progress toward completing OTA-12! Amazing work!!