@Zer0 Then I don't understand what the section I quoted is actually saying.

@Zer0 said:

True multitasking + reliable home: BFB or the spread home button always returns to HomeSpike; running apps stay alive in the background and resume instantly when re-tapped

So apps are no longer suspended when not in focus? How does this impact how long the battery lasts between charges?

@vince.vs The path is. Not a (full) filesystem path
Rather this is probably the left-overs of some app that shared status info to the greeter infographic, which you have since uninstalled.

@Turbolqk said:

@kugiigi I see, I haven't used UT in a few months, so I might've missed a few things.

These things you think you might have missed have been implemented for years, so even the few months ago that you used UT last, you should have come across them.

@AntiMS said:

My Pixel 3a running Ubuntu Touch 24.04 (24.04-1.3) abruptly stopped being able to send/receive texts/calls a few weeks ago.

Did your carrier completely switch over to VoLTE and switch off 2g/3g for calls? That would explain the sudden inability to receive or place calls.

@idonthatevests that would depend on what exactly needs patching. If it is some.module that is loaded at initialization time, but is packaged separately, then a new root image would carry the patch. If it is the kernel itself that needs patching, then the port maintainers would have to step up.

@Question_Asker There is no need to maintain a mirror of the source code if you would be distributing unchanged binaries. In that case simply pointing the customer to the license and the original source code, in whatever form, by link or in writing, is enough to comply with the license.

Only when modifying the source and producing distributing builds based on those modifications, would you be required to link to your own changes.

In any case, the license never requires you to ship the source code with every rrdistribution of your product. It merely requires you to make the source code available. Providing links to the relevant places complies with that requirement.

@MalocDegray said:

Via the phone terminal like @tafitson recommended is possible, but the phone is no longer detected via adb via computer.

When the device is in fasboot/bootloader mode it is never recognized via adb. You need to have fastboot installed and with that command it should be recognized.

@developerbayman This post is two years old. And the OP hasn't been on the forums in over a year. I doubt they will benefit from any advice now.
I will proceed to lock the thread.

@brenno.almeida the source needs to be available if it is an open source app. But as long as it is fully confined it doesn't need to be open source to be published in the store. The 'open' in Open Store originally was because it was also open to unconfined apps, whereas those were not allowed in the Canonical store.

@developerbayman it's just an update of an app that I have had in the store for years now.

This is an open ecosystem. User choice is welcomed. If it is a different app, inspired on Syncthing or no, then there's definitely no objection.

Even if it were the same app, then I am in no capacity to object anyhow. But in the latter case I would rather appreciate collaboration rather than having two distinct versions of the same app in the store.

But since this is not even the case with your app, by all means follow your intuition.

@Moem so it is!

@developerbayman It is never "that simple". If it were, it would already have been done.

A new version (2.0.16) of Syncthing has been uploaded to the Open Store. This release follows the upstream release. See here for the release notes.

@developerbayman wouldn't it make more sense to use a mainline port or the PDK image as a base for a x86_64 port. Then there would be no Halium bits needing to be removed.

@Ehartwork My point is, you are probably not testing VoWiFi at all, since that has not been reported to work on this device by regular users. One developer claims to have gotten it to work on a FP5, but this has not been independently verified.

The fact that what you think is WiFi calling doesn't work when there is no cellular service is a strong indication that WiFi calling is not available on this device.

@Ehartwork said:

WiFi Calling: Does not work without seeing the carrier service. The device works with cellular data turned off, but still within tower range, otherwise it will not work without it.

How can you be sure you are testing VoWiFi? From the sounds of it your are simply calling via your carrier's network. Turning off data has no impact on telephony. It only turns off mobile internet.

@r0lle said:

Maybe this is a Halium thing?

I doubt it. I have had a Pixel 3a in which I installed UT myself several times, and have never seen the logo you are describing on the boot screen.

@projectmoon said:

Can you actually type and backspace without it duplicating words/characters?

I usually turn off word prediction to avoid that. It's usually more trouble than it's worth anyhow.

@r0lle can you take a picture of those logos?