@oldbutndy Yes, click on the vertical dots on the bottom right of the post you want to delete, and then select Delete.

I have merged your two topics since they are about the same situation.

@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.

@oldbutndy said:

As long as everything it generated was open source, so it could be reviewed.
Otherwise, unsafe.

The problem is, that there is no way to tell. We don't know what the AI was trained on. So we can't know if what it reproduces is in violation of any licenses, proprietary or otherwise.

@Bolly Not harsh at all. But we had to go through the process of warning the user and seeing where things went. Where they went warranted intervention. The situation has now been dealt with and we have posted our stance on the matter going forwards.

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.

@Kadafi that is all very strange.

@grenudi OK, Please stop feeding forum posts to your LLM and then posting long sentiment analyses as answers. It pollutes the discussion thread. Consider this your first and only warning.

Here is a place for open discussion, but forcing people to be confronted with AI generated long-winded and bloated responses is an abuse of their time.

@oldbutndy currently only the Pine64 devices that have a UT port do not require halium. These devices all run a 'mainline' kernel (I put mainline within quotes, because actually no device, and hardly any distro even, runs a pure mainline kernel. Most kernels in the real world come with patches to improve operations on their expected execution environment. These kernels can track mainline more easily though, this is true)

Unfortunately there is currently no maintainer for any of the Pine64 devices, and they are therefore stuck on focal with not yet functioning OTA updates.

EDIT: I had forgotten about the Raspberry Pi port, which is also mainline. And I guess the PDK image could also be counted.

@VoidedKN0X The xenial version of Syncthing installed a set of upstart user services to sync in the background four times an hour for 10 mins each time.

With the move to systemd in focal I never got around to researching how to do something similar with systemd user services, so I reverted to only syncing when the app was open. But I am willing to accept MR's that add back that functionality.

@Kadafi how can your Screenshot folder be from the future?