@naz.R said in Merezhyvo browser: One related security detail: the built-in password autofill never uses the clipboard at all. Glad to hear that!

@lduboeuf Don't worry alarms can be setted again relatively fast, and calendar events... principally was in CalDAV remote server so... nothing losed. I don't know what happened. Aproxly ten days ago simply just stop working, until... now. Thanks again and if you want to try somehing for debbuging, let me know.

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

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

@vverve said in VOLTE status: Did not saw any signs of a 5G here passing some said as well covered area.... I don't think Fizz provides 5G under any of their plans. Thank you both for reporting on your tests!

@moem @zakafx "Average user" and "Daily Driver" is a bit hard to define once we bring in apps. For my case, I'll just define it as can I use my phone as a phone with anticipating some app or web functionality. Similarly, I would also look at how easy is it to break the phone functionality or the OS. For me, if the phone actually worked, the Google Pixel 3a Ubuntu Touch would be 95% daily drivable for me. The camera would be the only other main issue. I define "daily driver" if I can use the phone for personal, work, and travel. I think this type of average user would be more aware of what life was like before smartphones or wants to detach from the current things whatever they may be. Maybe they just want something different too or are more developer focused? Ubuntu Touch meets most of these points. Now, if I'm a person who needs a lot of apps because I grew up with apps and that is my expectation and what I am used to, any Linux phone could potentially be a hardpass....unless it is a Steam machine or latest social media thing or something I guess. Not sure what is all popular these days. As for me, if the phone works, I know a number of people who may be interested in Ubuntu Touch. I may have to help them with general setup and how to use the phone to get what they need though. A number of the "main" apps people use have web-based ways to use them or have an alternative in the store, a way to use the app with Waydroid, etc. I think the smooth edges initiative could help with this. In time, we can expect more apps, etc. However, that does not mean it can't be daily driveable for an average user. It just might be those who have to wait a bit more till it can meet their needs. Those needs kind of depend on the person and how they satisfy those needs can happen in different ways. I can see both sides, and both sides are right. We just have to look at a target population first and then see where and how we can get population growth.

@pparent very cool

@undrwater it depends on the kernel, hence on the particular port for your phone/tablet, more details in this post

@Vlad-Nirky The first one is for fat32 fs because it has no rights. If you want copy the rights you need a linux file system like ext4 as target. If you copy to an ext4 usb stick and use rsync with sudo, all different rights should be applied correctly. Thanks for the info of the return of rsync. Will it be possible to have ext4 on the internal micro SD card in the future? Greetings Charly

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

@fair For the Fairphone 5 I've implemented something which should help you, it's available in latest daily channels. The change is here: https://gitlab.com/ubports/porting/reference-device-ports/android11/fairphone-5/fairphone-fp5/-/commit/13884b434abf95f643f41f04c62b22e73be9fe1c What it does is keep the device awake once Waydroid starts. That means it won't opportunistically autosuspend anymore while Waydroid is running.

@d4f0 @messayisto thanks for your replies, I'm beginning to think that there is nothing wrong neither in force-adb nor in systemd (!) and the problems comes from the device tree of the FP5, that is, the kernel configuration. Changing force-adb could be an easy work around but mostly wrong. I'll try to explore the FP5 kernel code to see if I can find the problem all by myself (enthusiasm level: ) Edit: created this gitlab issue to make the problem more visible.

@gpatel-fr said in French ID app interoperability.: The recent decision about digital control is concerning troubling for a UT user What are you talking about precisely?

@haagch Pleased your issue is fixed.

@idonthatevests Can you link the SAR model you're using? Also, I'm not getting the microphone icon on the UT Translator app. enableSTT=true is set on the conf file, and Soty server is running (configured not to be killed by the tweak tool). I am getting "failed to load Vosk model" in the Soty server, but not sure why. I unzipped the model into ~/.local/kl.soty/en, and permissions look good. Can soty be started from the terminal?

for app - CinnyUT for developer - danfro who is always very helping for other users. Thank you.

Aaand today is working with no problem. May be related to football, the end of the world or something

@gpatel-fr said in Crazy stuff: sudo snap install signal-desktop: @pparent Yes I ack that they are open because I think I understand why. The idea is here but solving it is another story because there is always an effort for every result and sometimes the result is not worth it. Well I don't think you should be so pessimistic: First because if they are showing some interest in porting their app, I don't know why suppose they are not willing to really do so. Second because Qt6 is supposed to enable cross-platform development easily. Third because you don't how the userbase of UT will evolve in the next years, let's how it could grow significantly making it more attractive to port some apps. Of course the port might not happen overnight.