Ubuntu Touch Q&A 25 | March 17, 2018


  • Community

    It's time, time, time again!

    It's the Ubuntu Touch Q&A! These are hour-long (or so) livestreams where we get together and talk about what's been happening in Ubuntu Touch over the past fortnight. Episode 24 will be live on March 17, 2018 at 1900 UTC. You can catch it and a countdown on the YouTube live page.

    If you have questions for us, please ask them in this thread!

    Here are some things we'll generally not cover, though:

    • Any question in our FAQ
    • The status of bug reports

    We'll see you on Saturday!



  • Hi and thank you for asking our contribution

    What is absolutly not clear for me in the Q&A is the difference between core devices and legacy devices
    I had to open a thread to understand if my legacy phone is supported, despite the fact that is not clearly said to be. People gently said me it is ok with UBports tool so why is it not clear everywhere ?
    I understood too that even if it will work, some limitations could appear due to the hardware of the BQ E5. This should be highlighted too, IMHO.
    Thanks in advance if you improve the Q&A
    Best regards. Pulsar33



  • @Pulsar33: Thats a good topic. :) I've just checked the device page:

    • I was surprised and delighted seeing a lot more devices listed as core on http://ubuntu-touch.io/devices#/ than I had expected
    • what differs the devices prominently announced on ubports.com from the other devices listed also as core (now)? Are they really more work in progress than the other devices?
    • ubports.com claims, that the nexus 5 is the most available core device. In my opinion the fp2 availability is much better.


  • @unisuperbox Just a thought after using the forum today. Do you think the forum pages would benefit from a dedicated " Welcome / New Users " section similar to the one that can be found or you're directed too from Telegram. The welcome to ubports message though informative and fun just seems a little lost nownow in the general section.
    The project is moving very quickly now from what I can see, and alot of the questions etc are getting more and more technical. I just thought that for any new users who are not that technically minded or who are just starting out as I did a few years back, it might be quite helpful to have a clear easy to find welcome section with a few basic links where simple questions could be asked.



  • Hi,

    I have a few questions.

    I just read that OTA-4 is now "Due by April 30, 2018" . Is this only for devices listed as core devices or will it also be the "official release" for the first Halium devices, especially also the OP3? Also - will these devices from then on be core devices too?

    Thanks for answers



  • As mentioned in this post, as a result of some changes to the graphics stack for 18.04 desktop, Mir's EGL will no longer be supported. And as mentioned in this post, to overcome the loss of Mir's EGL support, moving forward, applications should use Wayland on 18.04 desktop.

    • Have you had a chance to test any applications using Wayland on 18.04 desktop?
    • If so, what are your initial impressions?

    I realize that this is a recent development, and so I imagine you may be waiting for the dust to settle before devoting much time to it.



  • I have a few questions:

    1. Will 16.04 be released only in the dev channel prior to OTA-4?
    2. What is the state of Anbox? Haven't tried it on my Pro5 for a month, and back then it was not very functional.
    3. Is the GPS functional on any xenial device yet? What about bluetooth?
    4. I have installed quite a few apps on my Pro5, but not that many are usable yet. What is the status of apps being repackaged for xenial?
    5. What are the biggest hurdles to get xenial in a working (daily driver) state?

    I am really looking forward to coming 16.04 updates. It is already very smooth on the Pro5 and with a few more bugs fixed, such as google calendar integration, GPS, Dekko, Telegram and some browser issues, I could start to test it as a daily driver.

    Great work, guys!



  • I am a daily user of the Signal app and would be interested in learning if anybody from the team has had any further contact with OpenWhisperSystems regarding support for making the Ubuntu Touch Signal app more stable and feature-complete. @Flohack mentioned something along those lines in https://forums.ubports.com/post/6379 .

    <3 for all of you contributors to UBPorts!



  • @tomoqv said in Ubuntu Touch Q&A 25 | March 17, 2018:

    What are the biggest hurdles to get xenial in a working (daily driver) state?

    In addition to discussing the biggest hurdles to get xenial (16.04) working, I hope that the following questions will also be addressed:

    • What are the biggest hurdles to get bionic (18.04) working?
    • I realize that this topic has been discussed in the past, but with the release of 18.04 just around the corner, any new thoughts regarding the possibly of skipping 16.04, and moving directly to 18.04?


  • @GizmoChicken: Walk up the stairs, don't jump up the stairs... (m.g.) ;)



  • @hummlbach said in Ubuntu Touch Q&A 25 | March 17, 2018:

    Walk up the stairs, don't jump up the stairs... (m.g.) ;)

    Yep, I heard him say that. :)

    And sure, if first walking up the stairs to 16.04 is the shortest route to 18.04 (or if they're already nearly at 16.04), then keep walking up the stairs to 16.04.

    But if 18.04 and 16.04 are in different buildings (to extend the analogy), then in my view, better to walk over to the 18.04 building and start walking up the stairs to 18.04 as soon as possible.

    Of course, I have no idea which better reflects the situation. So that's why I'd like to hear more about: (a) the biggest hurdles to get 16.04 working; (b) the biggest hurdles to get 18.04 working; and (c) whether the devs have any new thoughts regarding the possibly of skipping 16.04, and moving directly to 18.04.



  • @gizmochicken What if 18.04 isn't going in the right direction for UT? I read a fair bit about how x has depreciated, or that there's no longer any development of y. 16.04 was the zenith for convergence and thus for UT, so surely it makes sense to make full use of the features developed there...?



  • @3arn0wl said in Ubuntu Touch Q&A 25 | March 17, 2018:

    What if 18.04 isn't going in the right direction for UT? I read a fair bit about how x has depreciated, or that there's no longer any development of y.

    This thread is probably a better place to ask questions of the UBports devs than of me. But since you asked me . . . :)

    I'd say say that, unless the UBports devs want to maintain their own fork of Mir indefinitely (they don't), or unless the UBports devs want to drop Mir entirely, and move to some other display server (I don't know if that's even feasible), UT must eventually move to the new Wayland-compliant Mir and 18.04.

    If the quickest route to the new Wayland-compliant Mir and 18.04 is through a 16.04 intermediate, I'm all for that. But if completing 16.04 will significantly delay 18.04, then I'm not sure that I see any good reason for completing 16.04.

    But again, I have no idea which better reflects the situation. These are issues better addressed by the UBports devs, and so that's why I'd like to hear more about: (a) the biggest hurdles to get 16.04 working; (b) the biggest hurdles to get 18.04 working; and (c) whether the devs have any new thoughts regarding the possibly of skipping 16.04, and moving directly to 18.04.



  • @3arn0wl said in Ubuntu Touch Q&A 25 | March 17, 2018:

    @gizmochicken What if 18.04 isn't going in the right direction for UT? I read a fair bit about how x has depreciated, or that there's no longer any development of y. 16.04 was the zenith for convergence and thus for UT, so surely it makes sense to make full use of the features developed there...?

    The situation is a bit more nuanced.

    16.04 is much more like 15.04 and has many of the packages Ubuntu Touch depends on, the things that work now will mostly work after recompiling. The recent breakage of the Unity8 desktop on 18.04 is just the tip of an iceberg of changes that make 18.04 difficult.

    But there are also things that don't work now: Convergence needs better support for applications not developed for Ubuntu Touch. For the future, it is necessarily to adopt a newer version of Mir to get Wayland support and use applications that can use Wayland. Updating Mir is something that can be done on a 16.04 base, getting the applications needs 18.04.

    So, for the phone, the right step is to get off 15.04 in the simplest way: 16.04. This provides a stable base on which to consolidate progress, support the phones and prepare the next step.

    The Unity8 desktop is some way from being mature, and doesn't feed directly into the phone goals. Apart from some changes to get it working on 18.04 it needs things from Mir that have not yet been delivered (most significantly the support for X11 applications discussed recently). The work here should probably focus on 18.04 with the intention of preparing the way for the phone.



  • @alan_g :) Thanks for the clarification.



  • Some of the reasons why Ubuntu Touch will first be ported to 16.04, and then later ported to 18.04, are discussed at about 24:06 in the Ubuntu Touch Q&A 25.

    Also, some of the reasons for the delay in bringing Unity8 to the Ubuntu 18.04 desktop are discussed at about 21:22 in the Ubuntu Touch Q&A 25.


Log in to reply
 

Looks like your connection to UBports Forum was lost, please wait while we try to reconnect.