Ubuntu Touch Q&A 130 call for questions
-
Ubuntu Touch Q&A 130
Ubuntu Touch Q&A 130 is planned for this Saturday 16th Dec at 19:00 UTC so it's time for your questions.
Post questions below, but please remember that questions on porting to device **** or its status, and questions on bugs will not be answered.
-
U UBportsNews pinned this topic on
-
When I look at the Gitlab-milestones of UT we will see only one more Update based on Ubuntu 20.04. At the end of April UT will switch to Ubuntu 24.04. Are there also some devices that will be retired after that switch (e.g. of a to old kernel-version)? Especially in my case I would like to know if the Vollaphone (yggdrasil) will be left on 20.04 or if it's "new enough" for 24.04?
BQ Aquaris E4.5 (UT 16.04)
Vollaphone (UT 20.04) -
@kristatos I expect it might be too early to say, as the 24.04 development cycle is still in very early stages.
However, the thing that actually made most devices with older kernels become obsolete was the switch to SystemD as the init system and their kernels lacking support for that because of age. This time around no such fundamental change is taking place, so a safe bet is that if your device supports 20.04, then it will also support 24.04.
Of course as always, it will take actual work from porters to get the devices brought up to the newest version. But if it doesn't happen, it will not be because of old kernels.
So I guess in this specific case it would depend on Volla sponsoring the upbring to 24.04 for yggdrasil.
-
@kristatos What's sure is hardware, software, halium 9 is enough for the volla to be updated to 24.04.
-
QtWebEngine 5.15.15 is already causing issues on some sites. Are you doomed to constantly struggle to update yourself as much as possible? Is there a solution that allows you to reduce your amount of work and leaves the sites compatible for as long as possible (1 year, 2 years... utopian I think...
). -
U UBportsNews referenced this topic on
-
Hi,
On Thursday Dec 07, 2023, my Ubuntu desktop operating system (Ubuntu 20.04.6 LTS) was provided an upgrade of the bluez stack.
<<start date: 2023-12-07 20:18:58
Commandline: aptdaemon role='role-commit-packages' sender=':%.%%%'
Upgrade: bluez:amd64 (5.53-0ubuntu3.6, 5.53-0ubuntu3.7), bluez-cups:amd64 (5.53-0ubuntu3.6, 5.53-0ubuntu3.7), libc6-dbg:amd64 (2.31-0ubuntu9.12, 2.31-0ubuntu9.14), libc6:amd64 (2.31-0ubuntu9.12, 2.31-0ubuntu9. 14), locales:amd64 (2.31-0ubuntu9.12, 2.31-0ubuntu9.14), libc-bin:amd64 (2.31-0ubuntu9.12, 2.31-0ubuntu9. 14), bluez-obexd:amd64 (5.53-0ubuntu3.6, 5.53-0ubuntu3.7), libbluetooth3:amd64 (5.53-0ubuntu3.6, 5.53-0ubuntu3.7)
End-Date: 2023-12-07 20:21:51>>Will such an upgrade also be useful for our Ubuntu Touch?
Greetings Mario
Translated with DeepL.com (free version)
-
@Mario-CH i think this has something to do with the actual security-issue within the bluetooth-stack of Linux, Android and iOS. When I'm right, all this security-fixes should be included in upcoming UT-releases.
-
U UBportsNews referenced this topic on
-
-
I have heard that the aim is to release UT based on Noble on, or very close to, Ubuntu's planned release date.
Is this the plan going forwards for every LTS release? -
Has there been any consideration for changing the stable updates naming scheme?
Currently they are labeled OTA-x and the numbering is reset everytime UT is rebased on a newer version of Ubuntu.
But if we will be keeping up with the LTS releases there are likely to be less OTA's in the interim, because rebasing will occur more frequently. It will then not be immediately clear when a user seeking support says they are, for example, on OTA-2, if that is the previous release or the current one. -
-
@UBportsNews Question: Besides UBPorts, there are a few other Linux on mobile ecosystems around: Plasma Mobile and Gnome Shell on mobile (Phosh). I wanted to ask whether there is any chance that the ecosystems can work (closer) together?
Related to this, is it technically possible to build an app ecossystem where apps run on UbPorts, Plasma Mobile and Gnome Shell mobile? -
Why best SNAP version of the installer is always 0.9.7 beta since a long time ? In the installer, it is also said since a long time to refresh ubports-installer but snap refresh... -- stable give nothing. When will be published a new stable SNAP version of the installer ? Thanks.
-
U UBportsNews referenced this topic on
-
System unpinned this topic on
-
Moving on from a kind of misunderstood question from last week.
Always have advised using the installer for installing UT, but to clarify, would it be possible to have better tutorials and updated links to install the correct Android ROM in order to install UT? (i.e., better instructions for the preparatory steps).
Would it be possible to have big warnings regarding the difficulty of returning to Android on certain devices if UT either doesn't work as expected or it doesn't work for that person?
These are kind of basic things to someone who is not tuned to putting a ROM on a device (and yes I know UT is not a ROM) and may discourage further forays into UT if they are difficult, not well explained or difficult to find the correct files. Not everyone is so tech savvy, but a quite a few want to take control of their device and UT is a viable option on some devices.
-
A arubislander forked this topic on
-
@MrT10001 Just a thought but is that info upto the porter or device maintainer to provide and keep updated and provided so the devices page and installer can be kept accurate?
-
@Lakotaubp It should be, but (big but), people have lives and it is time consuming to do something like this, so it would be quite a project to keep on top of. (XDA-Developers forum is a hive of dead links and old information).
The reason I ask these questions is dealing with some of the issues on this forum and others where non tech savvy people are trying things out and fall at the the first hurdle. I do not want to see these people get put off for life of trying UT and Android ROMs on devices that have been orphaned by their manufacturer.
I see device maintainers and porters could be put in an awkward position of being "owned" (or the feeling of being "owned", something I have experienced a lot in PC and device repair) by someone who has issues, installing and running UT on their device (see some threads on the forums).
The notes are generally fine for someone who is quite tech savvy, but read through the forums and you will get many threads of issues installing and what to do. Then there is the issue of returning to Android which is annoyingly difficult on some devices (ahem, Xiaomi).
It is a difficult one as there is quite a gap between someone who can code and port and someone who is installing for the first time, I would just like to see it a bit more open and helpful.
Apologies for the ramble...
-
@MrT10001 No need to apologize it is an important subject and one of the reasons (mentioned in newsletter) that a new devices page is being prepared( blog on the way soon).
The issue should not be that people have the right to chase a porter/ maintainer or anyone else round and round over an issue but that the info is there to start with.
All info or updated info for the device needs to be clear on the device page and the state of the device port also clear. Is the device daily-driver ready, fully UT featured or in need of some work.
I don't think it should be expected that our community volunteers should have to chase about for info or be expected to know all the ins and outs of every port, if the originator does not do it.
It is also not a problem if someone gets a port just working and stops there. But it should be clear to everyone that it is. -
Hi @Lakotaubp @MrT10001,
However, it is also often forgotten that most of the devices used are already in an older and used condition. This can significantly hinder troubleshooting and test exclusions. An example of this is the simple soiling of the USB ports and/or a weak battery.
As long as people are willing to actively help with the problem (including investing time and reading articles in the forum) in order to find the solution, it is fun to help someone.But I can also see that the already well-founded reasons and solutions for known problems should be summarized in a kind of device wiki, and not laboriously searched for in the forum (with the - sorry - bad search function).
Kind regards Mario
Translated with DeepL.com (free version)
