Forum moderators' stance on AI generated posts

On this forum we would like to foster open, friendly, fair and human interaction. Recently however long posts have been made by humans consisting mostly, if not completely, of AI generated analyses and conclusions. The expressed desire was for the community to engage with the analyses and confirm or refute the conclusions. We deem this to be unacceptable.

Everyone is free to use the tools they want to. However we would like to keep this space an interaction between humans. You may well use an LLM to translate posts or to digest and summarize a great deal of information. But please don't ask it for its opinion on the matter, and if you do, by all means do not copy past its analysis and opinion here. Read the summary and come to your own conclusions based on that. If you feel strongly about them, share them, the conclusions, your conclusions.

Going forward, anyone found to be posting AI analysis and conclusions, those posts will be deleted, and the user will receive one (1) warning. If the user persists then they will be banned.

Thank you for understanding.

What is Syncthing?

Syncthing is a continuous file synchronization program. It synchronizes files between two or more computers in real time, safely protected from prying eyes. Your data is your data alone and you deserve to choose where it is stored, whether it is shared with some third party, and how it's transmitted over the internet.

What does this have to do with Ubuntu Touch?

I have packaged Syncthing into a click. This is based off the work of @ZeroPointEnergy who I am not sure is still active in the community.

My attention was drawn to Syncthing because I was looking for a simple way to sync my ebooks between my tablet and my phone, and the Nexcloud sync app did not play well with my Nextcloud setup.

Cool! Where can I get it?

Syncthing companion snap

Want to use Syncthing as a lightweight backup solution and need to install in on a server? There is now a Syncthing snap packaged by yours truly.

I have questions.

Any suggestions or questions on its functioning on Ubuntu Touch can be posted in this thread. I will do my best to help where possible. Questions on Syncthing in general are better posted on their support forum.

Links:

• main site: www.syncthing.net
• documentation: docs.syncthing.net
• main project: github.com/syncthing/synhthing
• ubuntu touch 'port': gitlab.com/arubislander/syncthing-clickable
• snap package: snapstore.io/syncthing-arubislander
• snap package source: gitlab.com/arubislander/syncthing-snap

@t12392n said in App security (new KeepassRX app):

I wish there was an strict firewall native in Ubuntu Touch so that we would see and control what is allowed to talk. A local Keepass should not talk to the internet.

If the app is confined (as this one is) you don't need to blindly trust that the package in the open store was compiled by the code that is linked, to be sure it doesn't phone home. If you know what to look for, you can download the .click package and examine the contents. The most important is the .apparmor file, which describes what permissions the packages requests from the system.

Here we see that this app is indeed confined, and it only declares the content_exchange policy group. This means that the app will not be able to access the network at all, because the networking policy group is not included in the apparmor.

@Mario-CH said in Ubuntu Touch Q&A 123 call for questions:

I imagine that many UT users (like me) will finally want to pay the long overdue next donation when ...

I couldn't help reacting to this. I understand you are saying this somewhat in jest, but it exposes a common misconception about donations (and one that I have also fallen for from time to time.)

Donations, by their very nature, should not be seen as reward to a project for work done, but as a way to support the work being done at the moment.
While donating doesn't guarantee your issue will be addressed, withholding your donation until some features that is important to you is implemented or fixed will definitely not make that happen any quicker.

@Inglebard said in Device compatibility/lifespan with UT:

why is it not always possible to update the kernel?

To start with your last question. It is not always possible to update the kernel because the proprietary drivers that make the hardware of the device work are compiled against a specific version of the kernel. If a newer version is used, then the drivers may stop working, and they cannot be fixed to work with the newer kernel because the source code for them is not available.

The changes needed to work with Ubuntu 20.04 could in principle be backported to older kernels by someone wanting the see these older devices keep running on later versions of Ubuntu Touch. But that is a huge amount of work in itself, and also just one step in getting some of these devices up to date.

I would like to know what makes a phone compatible with Ubuntu Touch?

The short answer is: Anyone willing to put in the work to make a port of Ubuntu Touch for that phone.

A longer answer would be: If the phone has at least 3 GB of RAM, runs on a relatively new Kernel with sources published, and there is a working Halium version available for the Android version it shipped with, that would make it a good candidate for porting.

I would also like to know how to determine if a device that is compatible with 16.04 or 20.04 will be compatible with 22.04 or 24.04, or even beyond (What is its lifespan)?

This depends on the changes that are introduced in the underlying Ubuntu version that is being targeted. For instance 20.04 no longer supported Upstart as the init system. Everything was moved to SystemD (this had happened earlier, but those versions were skipped as UT targets). This in turn meant that only kernels that could support all the SystemD features that were required in Ubuntu 20.04 to get Ubuntu Touch running, could be supported. Sometimes these features could be backported to older kernels (as is ongoing for the OnePlus One) but since different devices used different kernel versions, this work would most likely need to be re-done for each device for which support was desired.

It is not always clear before starting to work on it, what changes in the new version of Ubuntu will have what impact on Ubuntu Touch. And which changes will cause the most work to adapt to. That is why it is difficult to state beforehand how long any particular device will be able to be supported. You can assume though that once a device gets support for an new version of Ubuntu Touch, you will be able to receive security updates for that device for at least as long as the underlying version of Ubuntu is supported by Canonical. Feature updates might stop earlier due to the need to keep somewhat up to date with the current versions of Ubuntu to benefit the most from the latest improvements to the software components being used in the OS.

Last but not least, the commitment of the porter to the device determines to a very great extent how long and how good support will be for any given device.
Some ports are sponsored by, or done in collaboration with, device sellers, such as Hallo Welt with their Volla Phones, and Fairphone with the FP4. These have a better chance of seeing good support.

Ah...

It is difficult to find the right words to write.

I could write about your encouraging attitude and your clear-sightedness in envisioning a future goal, and dedication to seeing it achieved.

Or about your capacity for keeping people pursuing disparate short term aims onboard, and working together towards the common goal. Keeping all the frogs in the wheelbarrow, so to speak.

Or about your desire to give consideration to every voice in the Community and agonizing over how to do right by everyone.

I could go on, but you know you. Maybe you would see things differently, but this is what I have seen from you.

You have done really, really well by the project. Now go do really really, well by yourself. Hopefully this experience will help you find a way in future to do both, by you, and by whatever endeavor you passionately dedicate yourself to.

I look forward to seeing you shine!

@Linuxlite76 said in Ubuntu Touch Q&A177 call for questions:

someone like Elon Musk

Not 'exactly' like Elon Musk, though.

@ktatar156 Emotions have nothing to do with it. I was simply reacting to your stated requirements.
Of course you can install GApps on Waydroid and download your bank apps from the play store. I wasn't suggesting otherwise. The question is though, if they would run. Does your bank app run on Lineage, or on a rooted device? If that is the case it has a higher chance of also running on Waydroid.

About your question if UT will ever be a succes: Define success. The project will continue as long as there are people willing and capable of continuing it. That is both the strength and the weakness of OpenSource. It doesn't have to become a commercial succes, it doesn't have to become popular overnight. All it needs is a dedicated team of developers and a passionate community that both supports the team and whose members can in time become part of the team.
I would venture to say that since Canonical handed over stewardship of the project to UBports it has given a boost to community involvement in the project. By this metric the project is a bigger success than it ever was under Canonical.

Concerning the lack of flagship Open Source apps like Firefox. On the one hand I could say, bug the publishers of these apps and ask them to support Ubuntu Touch. Why should the burden of packaging and maintainance fall on this project alone? But publishers of Open Source are more likely to consider supporting UT if the software stack is more up to date. Well, there is great news on that front. The work to bring UT to 20.04 is in very advanced stage. And once it is released as stable sometime in the first half of this year, work will immediately continue with rebasing on 22.04, which should also be well advanced by the second half of this year. An up to date software stack opens up many possibilities for supporting additional packaging formats such flatpaks and/or snaps. This would not automagically make the software feel at home on UT (think confinement and application lifecycle) but it would be a start.

Are there any needs? Yes! There are knowledgeable developers who are balancing working on this project with their fulltime jobs and daily lives. Given enough donations and sponsors, the UBports foundation could employ all these developers fulltime and there would definitely be a boost in productivity. (Whether this would impact community involvent, if you wish to discuss this, slide into my dm's or let's start a new thread.)

As it is now, @Keneda already mentioned that coders are very welcome. Experience is a pre, but stick-to-itivness and eagerness to learn can make up for the lack of experience.
There is even a job posting for a developer by the company that makes the Volla phones (these are phones that come with the option of pre-installed UT).

Since some years now the UBports Foundation has been the steward of all the projects that together constitute Ubuntu Touch.

A quick summary of the different bodies that comprise the Foundation can be found here. But the body I wanted to focus on is the Board of Trustees (BoT).

The formal role of the BoT is described in the Statutes of the Foundation. Since this is a formal document, it is written in Legalese, but what it comes down to, very roughly, is that the BoT consists of contributing members of the community who have applied to become a member, and whose application has been approved by another Body of the Foundation, the Membership Committee (MC). Members get to vote at elections for the Board of Directors (BoD, not to be confused with the BSOD :beaming_face_with_smiling_eyes:) and the MC. But crucially, BoT members can nominate themselves to stand up for being elected to any of these two bodies. BoT members also get to vote on issues set before them by the BoD.

The requirement for admittance to the BoT are summerized in this old blogpost:

Anyone, anywhere in the world is eligible to join the Board of Trustees provided they meet some minimum requirements. First, they must legally be able to be a member of such a body. Second, they must be able to show that they have verifiably, not trivially, and not immaterially contributed time and intellectual work towards the Foundation’s objectives over a period of at least three months; and that at the time of their application they have the intention to continue to do so for at least another six months.

Verifiable, non-trivial, non-immaterial contributions of time and intellectual work would include without being limited to:

• time spent on this very forum or in the Telegram channels, helping out user with their issues,
• contributions to documentation
• contributions to code
• app contribution or maintenance
• giving talks on Ubuntu Touch or the UBports community and manning stands at conferences and other venues.
• ...

I am sure many more of the people frequenting these forums are eligible for membership than have applied so far. So my question to you is: Is there anything stopping you from applying? If so, what is it? I am eager to hear your views.

When some users face intermittent issues with some of the preinstalled apps, a strategy that is often employed when trying to resolve these is to uninstall the app with the aim of reinstalling it, to see if that fixes the issue.

This is inadvisable for several reasons:

• You might face issues trying to reinstall the app.
  While some preinstalled apps are also available in the Open Store, they are treated differently. They are not really uninstalled, but hidden. And often reinstalling the app from the Open Store does not un-hide it. There are posts on the forum on how to get these back, but it is a hassle and requires some command line fiddling.
• It will probably not solve the issue you are experiencing anyhow.
  Almost certainly the issues are caused by (meta)data around the application, rather than the application itself. Uninstalling an application in Ubuntu Touch does not remove the application (meta) data. If this is the goal, then using the Ubuntu Touch Tweak Tool, downloadable from the Open Store, is the best way to go.

The TL;DR; of it is: DO NOT UNINSTALL PREINSTALLED APPS UNLESS YOU NO LONGER INTEND TO USE THEM.

@developerbayman To be completely honest, half the time I don't know what you're on about . I just chime in when I see a question I think I can answer. Otherwise, I leave all well enough alone

@developerbayman This thread is not about touch or gestures in Lomiri. It is about gestures on the virtual trackpad that the device becomes when it is connected to a screen wirelessly via Miracast.

@developerbayman I would say, it depends.

Since your work is based on the PDK image, which itself is a developments tool and does not have a read-only rootfs, it is expected that you would also end up with a writable rootfs.

If you are planning to support OTA updates just like on other UT devices, then making the roots r/o would be a requirement. But until that moment, there isn't really that much benefit in having it configured that way.

@lsitongia I had missed the part where you said you were testing PR packages on the device.

@lsitongia I am in the dedicated N10 device group on Telegram, and I have not heard anyone comment on not being able to install 24.04-2.x

As I said on Telegram, maybe your /cache partition was filled, since you mention you had a downloaded -1.x update ready which you did not apply before attempting to upgrade to -2.x. So that was probably the original issue. But now you've done a few things already, so not sure what your current situation is.

If you are OK with starting completely fresh I would go with flashing android and then UT again.

As an aside. It is normal for the device to say it is installing updates after running it through the installer. That is just the last step on device of the installation. Several files are pushed to the cache partition by the installer and then the recovery knows to unpack those files in the correct locations.
It is also normal for the device to show as one thing (billie) in recovery and another thing (lito) in fastboot.

Lastly.. Daily is not recommended for daily use, unless you are interested in helping testing and catching early bugs. If the phone is your daily driver, then 24.04-1.x stable is the channel that you are recommended to be using.

@oldbutndy said:

But, it seems this would end up not reducing the huge number of variations for all the different phone models.

Am I missing something here ?

No, you are on to soimething. People forget that ARM hardware in general and phone hardware in particular is totally not standardized. So to get all the drivers for all that hardware upstreamed would be a huge endeavor. One, frankly that I am not at all convinced that AI is capable of taking on. And even if and when, new hardware keeps coming out with each new generation of devices, so you'd have to practically start from scratch each time.

We saw how just the jump from Pinephone to PinePhone Pro brought in such fundamentally different hardware that the Pro never really caught up, software wise, with the original device.

What makes 'mainline' kernels viable on x86 / x64 server and desktop is the high degree of standardization of the hardware in that area.

@oldbutndy said:

Also, is it possible to retain halium layer for modem-radio and other components for which there is no no kernel driver, but put simple things (I assume turning flashlight LED on & off & PWM for dimming would be easy) into kernel ?
Is that how it already IS being handled ? or does halium translate everything ?

The thing is that any new support for hardware is likely to land in newer version of the kernel. Halium ports are tied to a specific version of the kernel for ABI compatibility with the drivers the device vendor provides. And backporting those new drivers to the older kernels would probably be more work than it's worth.

@gandalf Yes there is. In the terminal, navigate to the folder you no longer want the files indexed and execute the following command:

touch .nomedia

This also works on desktop linux.

@Mario.CH said:

Well, but that internal ad banner that appears at the very bottom of a post when you visit the forum as a guest—that really gets on my nerves, too.

I run pi-hole on my home network. And I never browse the forum without logging in, so I never even knew there was an ad banner anywhere on the forum, tbh.

@developerbayman to be honest, neither you nor I know what the community would or wouldn't mind.

I am somewhat confused though, you appreciate that there are no ads, yet you wonder why there aren't any.

If you can mention any product or service that has increased user satisfaction by including ads, then maybe we can have that conversation.