@pparent very cool

@Charly rsync -rtvP --delete --modify-window=5 --delete /home/phablet/ /media/phablet/STICK/phablet/ or rsync aP --delete /home/phablet/ /media/STICK/phablet Did this preserve the Waydroid directory and its rights?

@zubozrout said in Smooth Edges (name pending) - Let's Fix the Bugs That Drive You Mad: the camera—it’s the main limitation for me. From what I understand, this isn’t something that can be fixed simply by creating a new camera app, as the issue seems to run through multiple levels of the system. As far as I recall, the core limitation is already present in Halium: shots take too long, not all features are exposed, higher resolutions can easily overexpose, and overall the photos look far worse compared to what Android delivers. Not sure exactly what is the problem as there too many you cite; maybe the main problem is that you have high expectations and are an elite user about photo. That's a bit like judging of a computer system by a music expert, these guys can detect one tenth of second of delay, a fourth of a tone, minute details that beotians like me can't even perceive whatever effort they do. And I'm not so atypical from what I gather of the judgement of these music experts on the efforts of spontaneous singers in public events (they are utterly awful - however I never noticed it before being said so). So what's wrong with photo app of UT for someone like me? the focus for near objects. When taking a photo and the subject is half a meter (let's say one foot for our US friends) away, the focus is terrible, like, the keys on a keyboard can hardly be deciphered, and waiting does not provide much relief. In contrast, a Waydroid photo on the same device in exactly the same setup looks correct. This does not look like an unfixable problem, since switching to film, the focus at the same distance is correct. I just tried it and it seems that after taking a short film, the focus is then correct for taking a photo. While this is hardly a workaround, it make me think that for the photo app being usable for ignoramuses like myself (and I'd say 99% of users), it is probably not necessary to rebuild the whole system including Halium.

@Vlad-Nirky I opened terminal, next I opened top, but I didn't find source of the problem

@domubpkm said in Merezhyvo browser: @naz.r Not sure what I'm saying so sorry if I say something stupid: Does certain data pass through a clipboard internal to the app (therefore different from the UT clipboard). If this is indeed the case, would it be possible to have a mechanism that allows its contents to be erased (security)? You’re not saying anything stupid at all - Ubuntu Touch really does have a slightly weird situation with clipboards. Merezhyvo itself doesn’t implement a separate “in-app” clipboard or any clipboard history. When you copy text in the browser, it goes to the clipboard that is exposed to confined apps on Ubuntu Touch. However, because of how Ubuntu Touch sandboxes native apps, Libertine/X11 apps, Waydroid, etc., there isn’t a single global clipboard that everything shares. That’s why text copied in Merezhyvo often can’t be pasted into a native app (and vice versa) - they’re effectively using different system clipboards, not something I created inside the browser. One related security detail: the built-in password autofill never uses the clipboard at all. Saved passwords are sent directly from the browser’s password storage into the page’s form fields over an internal IPC channel, and only live in memory long enough to fill the form. They are not put onto the Ubuntu Touch clipboard and not kept in any separate “hidden” clipboard inside the app.

@Lakotaubp To my knowledge one+n10 24.04-1.x does no volte yet , and , the bloody fun is that bleeding ''dragon'' edge 2.x ,volte OK ,is not having more regressions issues with updates then daily 1.x !!?! if not less ... until now. Fear no spitting fuel/blood flying beast...i guess there will be more gliches untill volte+++ get to noble stable .

@GooglyBear Sorry I can't remember if I did but you can check the Ubuntu Touch repo or Lomiri or Mir. I did asked Mir developers about it and they said even the latest version at that time didn't support it. Fun fact, even Gnome has this problem, it can't properly map multiple touchscreen displays. KDE however does.

@undrwater said in SOTY - Speech-To-Text Recognition on Ubuntu Touch: @idonthatevests I assume you're using LLM for STT. I'm doing that on my desktop in a python venv. No, I use small ASR models. Running LLM on an old mobile CPU for this task would likely make the speech recognition expensive and slow. And I think the same situation would be with attempts to use it for speech synthesis. So, using LLMs for that on mobile OS is probably possible, but only if you implement it for non time-critical tasks. Yet, in my opinion espeak-ng is still a fine option for that and is highly configurable. I'm still figuring my way around how UT is organized (I use gentoo, and it's quite different). There are many things in UT that are not organized yet, but that's what is great about UT for me, that you can do it yourself! Have fun with your research

@donieck Ho. And what's the values in in System settings / cellular / Provider and acces point name / Access point name / internet ? [image: 1764828582699-81241797-8922-44d6-ae68-6dcc0b7eaf57-image.png]

Hy all, In update 224 it is fixed. Glad i din't rush things... Ernst-Jan

@Moem （Apple Push Notification Service，简称APNs）