Ubuntu Touch Q&A 93 Saturday 30th Of January At 19:00 UTC
The next Ubuntu Touch Q&A will be the 93rd and we would really appreciate it if you could join us for the latest in Ubuntu Touch development, updates and answers to your questions! Forum questions get priority so post them here before the event or Youtube Livechat https://www.youtube.com/watch?v=jTyO29bnsyY and Telegram during the live show.
Please remember that questions on porting to device **** or it's status, and questions on bugs will not be answered
While development on the technical foundations of UT is regularly covered in Q&A (20.04 transition, Qt 5.12 transition, Lomiri development, new Halium ports etc.) can you shed some light on (under the radar) development in user land? There must be some, because UT has not come to an end, yet.
To name the elephant in the room, what about CalDAV/CardDAV support? That seems to be only half-baked, currently. Is there any development on that front? To quote from the UBports site: With Ubuntu Touch they will have nothing to see. Ubuntu Touch user's response: Because there's no way to share. Since working CalDAV/CardDAV synchronization on a smartphone is a basic requirement like telephony and text messaging these days, would it make sense to back sustainable CalDAV/CardDAV development by the foundation similar to OS development?
Speaking for myself (and only myself), I greatly enjoy hearing about your progress with the technical foundations of UT.
QUESTION: With the transition to Qt 5.12 (a huge accomplishment!) nearing completion for the release of OTA-16, what will be your primary goal for OTA-17?
What is the situation on the removal of the old Oxide browser and what new features are upcoming for Morph to have a smooth transition?
Any thoughts on possible bookmark syncing in Morph?
Once Ubuntu touch is based on 20.04 and using Wayland, how hard do you think it will it be to get flatpak applications working?
How is the migration to 20.04 coming along? Any major roadblocks?
I was wondering if there will a migration to Debian instead? Because of this persons work:
Thanks for awesome work with 5.12 migration. I would love to ask what will change about camera backends regarding pinephone and halium devices support. I have OnePlus 3T, way to get camera working before was to install
gst-droid. Currently on devel installing
gst-droidwill downgrade some packages and taking photos is not working with or without it.
I'm very interested in the possibilities of better user support and stability for Anbox, which could include install/configure tooling for .apk, and inclusion of alternative stores - like Fdroid and the e.foundation appstore. There are specific ecosystem gaps that can be addressed this way. Many users have one important function that a single app addresses, that is their roadblock for adoption. These emerge merely as corner-cases for UBports as a whole, and full feature support for installing Android apps would be one good way of addressing these barriers.
@ubportsnews Hello ubports and all viewers on youtube , I've got a few questions for Q&A
List of supported devices is growing really quickly, and all we know it will grow even faster thanks to recently introduced halium 10. What's your plans to control maturity of so much new devices which you may not have. Are you ready for thousands of potential new ubuntu touch users?
And the last one, what's with lomiri documentation? we've been waiting for it since December