@Keneda said in Smooth Edges (name pending) - Let's Fix the Bugs That Drive You Mad: Yes, kind of. Thanks, interesting. It's worthy of note that - as could be expected - these corporations only provide a way to migrate to their own platform, not from their things to competing services. If you want to go away of me, take care of yourself, they say. Note sure it would be realist to expect otherwise of anyone.

@flohack ?

Solved by first updating to 20.04 OTA-11 and than upgrading to 24.04-1.1

@domubpkm said in Merezhyvo browser: @naz.R said in Merezhyvo browser: So in practice: Sites still share cookies in the usual “per domain” way, But there is never a moment when two different tabs are actively running JavaScript in parallel, only the currently selected tab is alive and executing I understand (I think) what you're saying, but does this change anything about the action / effect of third-party cookies? Does this mean that even if they are there, they are asleep and have no negative spying action? no, it doesn't the third-party cookie blocker is going to be in the next release after the next one, I believe.

@theprivacydad I guess you would have gotten a much better experience 6 months later: and that's an unfortunate coincidence that your testing/review happened just few days before some of the major needs (Signal, KeePass) were released to the Openstore , and some of the issues you mentioned is just about to be addressed: like modern and stable web-browsing. Anyway you will always be welcome to do an update or a new review in few month/years!

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

@GooglyBear I have a portable one. Touch works but not correctly because it maps to the built-in screen so it interacts with the touchpad. I believe this is something that Mir needs to support.

@Lakotaubp Confirmed

@pparent I have installed VLC in Waydroid and it works great so a native app would be awesome.

@jam1388 Yes you just need to make sure the wipe user data is not ticked and your fine. Also if you are already on UT( which you are) no need to resize partitions it use bootstrap. This applies to any reflash if you can't down grade from system settings, updates, channels. I don't have your device but on my FP 5 5g and volte work on 24.04-2.x so it should be the same with yours 2.x daily is just the start of the process if moving to the next version. This issue took out my FP4 as well and that works just as well on24.04-1.x though I know at times it's fun to play on the outer edge where the dragons live : )

Now the microphone is enabled, if some people can test calls, it would be nice to know the level of usability, the presence or not of echo, and the audio quality!

@Futura Do headphones with microphone work? That should at least make the phone a bit more usable. Also, did you post a gitlab issue for it? Maybe the fix isn't so hard as it may seem...

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

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

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

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

@undrwater Thanks for your interest. You can easily integrate TTS support in your application using espeak-ng. However, espeak data takes 20 MBytes of user storage space. If you want this functionality for Soty server, that would require changing communication protocol for both server and client. It also would not be too hard, but I personally think we should look for a more accurate solution for this task, that could be seamlessly integrated in system, such as speech-dispatcher.

said in Enabling MAC randomization: Another could be to stop and disable the mount unit + restarting the phone when staying at home. I have finally decided to finish this matter and found a way to enable randomization (reenable the mount) while keeping the ability to connect automatically to the phone via my local wifi, so i'll be able to test it more seriously. I'll see how it works. With 24.04.1.1 I still don't see any problem with getting the list of networks, I even disabled wifi without intending it and after reenabling it immediately my phone did not crash. Maybe I was lucky this time or the fix for this problem has been merged.

@donieck Could you share the mobile data config working?

The small UX problems have been mentioned, but I think the biggest one is that quite often the touchscreen input mapping breaks. I think it happens especially after an accidental drag & drop trigger, on an image on a website, or on a tab. Then there is a good chance that either a) one touch input seems to be stuck so if you try to just scroll down with one touch, it does a pinch zoom instead, or b) the touch input is clamped to a part of the screen and you don't have touch input outside of that area. This is probably related to the landscape mode issue, but this is easily triggerable even when the phone is in portrait mode and rotation is disabled. I'm not sure you can do much about that, but it is a real issue because the only way to get proper input back I found so far is killing the app and restarting it. This applies to bluetooth audio and usb audio (the latter apparently works now). It does NOT happen with built in speakers: Firefox likes to control the global volume. Example: Play any audio (e.g. https://radiomii.com/ or any app). Go to youtube in uWolf and start a video. Bam, 100% volume blasting your ears. Not sure if MOZ_DISABLE_PULSEAUDIO=1 is really a thing (only 1 google result from last month?) but I tried os.environ["MOZ_DISABLE_PULSEAUDIO"] = "1" and it doesn't make a difference. I tried that because I assume the issue is with how firefox creates a separate stream for every tab/media. In about:config I only saw media.default_volume but not even that seems to do anything about this behavior. Does anyone know if there would be a way to make firefox behave?