@Ida_ ah, ok. Not iedal, but sometjing. I get less than a second. I am not that quick in reading.

@oldbutndy said: I thought sm-xcx was updating details on specific device pages They are. That means updating the already existing text, not adding new sentences.

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

@richdb Isn't beeper technically working like a bridge (collection of bridges)? There are also other signal bridges out there, or one can self host one.

@Futura Wow, that's disappointing.

@DJac there is still no question for the Q&A of today so this is your chance for the limelight

Is it worth considering starting again? Installing the correct Fairphone Andriod version listed on the ubuntu-touch website and following the install procedures for 24.04 stable? I have none of the issue you mentioned in your multiple threads with my fp5. The only outstanding issue is the fingerprint reader for me at the moment on stable.

@Vlad-Nirky Yeah, there is only daily at the moment. I have researched this issue and albeit not common, it is there and something to be aware of.

okay. great. I update. previous version, less stable on 24.04-2.x. better on 24.04-1.2

@Mario.CH yes, exacly that symptoms.

@CiberSheep to be honest, I disagree here. In my opinion we rather should update our HIG design to cover/allow for other app navigation methods. For instance OP8T (and another device which I don't remember) has the camera exactly where the back button sits. And this back button IS hard to reach with phones getting larger. This is a problem coming up again and again for a reason. Yes, there is no universal back, but there is in-app back.

@mihael said: @pparent Definitely. In the first releses of beta, sound quality was awfull both on desktop and UT. Now the sound quality is good on both. So I think that it was not something related to UT. Great to hear, I will try it again myself when I have the opportunity!

@tacetion so is it up and running with UT? A prototype is well worth keeping, collectors may seek something like that out..... It could also have had a screen replacement...

@projectmoon said in Call for testing: calendar-app: @lduboeuf said in Call for testing: calendar-app: @projectmoon said in Call for testing: calendar-app: @lduboeuf So unfortunately, calendar sync is still broken. The calendar that was syncing (connection to Nextcloud via generic caldav instead of built-in Nextcloud integration) is no longer syncing. Only thing I see in Evolution logs is something about i_cal_time_compare < 0 failed. I turned the Nextcloud integration itself back on for Calendar, and that synced fine... But I don't know if it will sync more later. Sorry, i don't understand, you mean it works or not ? Please also precise on which OS version are you . The sync can be sometimes unstable ( and it always has been). It is sometimes needed to recreate all accounts ( remove them all, reboot, recreate them) Stable 1.2, and the accounts were previously already cleared and removed from Evolution. Re-re-(re?)-creating the accounts shouldn't be necessary, I would hope. What I mean is that the Generic CalDAV Account seemed to stop syncing. But when I re-enabled the Nextcloud Account, that synced fine. I have two Online Accounts set up on the phone. Both point to my Nextcloud instance. Just one is the "proper" Nextcloud Online Account and the other is Generic CalDAV. Yes, there are reports where sometimes it happens and we don't know what is happening. Only by removing the account, then rebooting, then re-creating it fixed the issue. The new backend is more stable regarding that, but not here yet.

Reporting back for future generations, I think I've found the issue. I was retracing my steps and found this: When installing postmarketOS there is a device specific instructionto run "fastboot oem uart enable" command. So I tried to run "fastboot oem uart disable" and then flash UT. So far working like a charm. Did a switch off, did a restart and all works as I'd expect it - also with Libertine set up.

@slowcyclist Interesting find, thanks for the effort. @slowcyclist said: never use their gps for extended periods Yes that's the case for me, although these last days I just tried that, and I got effectively 2 occurences of GPS not updating any more (launched Puremaps and Gps app together to make it more interesting). For me the reason is that the FP5 is gulping energy at such a rate that I try to stop services when not actually in use. The only difference is that the GPS service (lomiri-location-service) never stopped for me (according to systemctl status) so no crash with unaligned errors, although I got the second time (did not think to check for that first time) segfaults and several restarts of sensorfwd service, maybe caused by this problem.

@PhAndersson @gpatel-fr So the fix is in 1.3 daily. Wait 1.3 candidate to test. Thanks.

@oldbutndy said: @Leroy_Linux Running 24.04.1n (daily - but randomly doing the updates), MVNO USMobile > T-Mobile Good to know. I'm running 24.04-1.2 stable and T-Mobile. I misread your post. Somehow I interpreted the phone wasn't working well, but you clearly stated that it's just not a daily driver unless WiFi calling or native VOIP. (neither of which I've used... my requirements are just for the working phone which it has done well thus far). Thanks and sorry for my confusion. Hope you find a way to meet your requirements!

I admire the partnership between UBports and Volla. It's very good to have two new modern high-performance smartphones supporting 5g. This has nothing to do with UT but I am less confident in the future with what we will be able to do with UT as a daily use smartphone and especially with androîd alternatives like Volla OS or others due to upcoming restrictions from Google and the incidious need to use official apps with real Google Play services, Micro G being rarely sufficient. This will not dissuade me from continuing to support Volla.

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