@peat_psuwit said in On the subject of Ubuntu Touch versioning scheme: In the Board of Trustees meeting on 4th February, I've brought the release version numbering up as a discussion topic. The attendees considered the comments on this post and have agreed that it's important to still reference Ubuntu version in our versioning scheme, while it would be beneficial development-wise to have a major-minor release system in place. As such, we've come up with a versioning scheme of "Ubuntu Touch [Ubuntu version]-[release version]" (a variant of option 3). For example, the next version of Ubuntu Touch would be referred to as "Ubuntu Touch 24.04-1.0". We believe this versioning scheme is both understandable and practical. I know I'm too late to the party; but if you're already staying this close to the current naming scheme why not go all the way to 24.04 OTA-1.0? Everyone is familiar with that naming convention already, and introducing a minor version number is "backwards" compatible by calling every previous OTA-x.0 if needed. And soon when UT reaches version parity with ubuntu 24.04 the colloquial OTA-x(.y) will be back in action offering an easy shortcut to identify the current release. Aka I'm getting old and grumpy, but I really can't stand the relentless reshuffling of naming schemes that usually offer no improvement and just increase the mental load on trying to figure out wtf is going on again

@MrT10001 You're right. It doesn't. I had to borrow a computer with windows and succeeded and it works well - just the clock at the top right seems to be in lack of room as it shows only the hour and the colon. I just want to comment a few things. Both links for the EU firmware OxygenOS_10.5.2 and the Global OxygenOS_10.5.3, under the 'How to install Ubuntu Touch OS' section of this device (oneplus nord n100) are point to the same web address (https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_Nord_N100/EU_BE83BA/Q/OnePlus_Nord_N100_EU_OxygenOS_10.5.2.zip). I figured out how to navigate to the correct link for the global image. I wasn't able to flash with any of those EU and Global images. The MSM downloaded software 'complained' it was not the correct product. I found out a web page on XDA with someone's advice on how to trick the software by modifying an xml file that had to be extracted from the ops by decrypting the ops file with a python tool then, after editing the xml file, to encrypt the ops file. Thank you!

@peat_psuwit Good evening. On the Redmi note 9 pro, several of us have installed noble and are experiencing a problem with the camera. I was wondering if it's specific to this model or if the malfunction is general? Regards.

thank you. I missed the "fastboot reboot fastboot" step. My mistake (I should have read more carefully). Thank you very much for your work.

It works. You need to have the OTG USB stick formatted to FAT32 and access it through the file manager on UT, then tap the three bars on the top left and scroll down and it should appear at the bottom.

@aimar All devices are capable of wireless display however it may depend on the port if it's enabled or working. Wired display out is a hardware feature though so you can't just implement it.

Hi @Mario.CH Sorry we didn't take your question during the live show. We didn't think it was the right place. But you raise a valid point, I actually share the same concern and raised a similar topic (before reading your question) to the board of trustees. I hope we can make things better on this front. But it's a complex topic and it takes time to find the right answer.

@AppLee said in New contact backend story: Hi @lduboeuf Thanks for your work. Do you need help? If I can be of any help, please PM me. I rely heavily on my calendar on the phone to sync well with my Nextcloud account. Of course welcome. The issue we are facing is related to an update in signond afaik. So out of my skills Mike is looking at this normally. After that being fixed, testings on contact sync will be ready. But local contact is already there with the new backend already test able. I'm currently working on error feedbacks for user ( re prompt for password, and UI notification on failure with contact sync ). A missing part is also for address book via Bluetooth. Epic: https://gitlab.com/groups/ubports/development/core/-/epics/19

@ricardo65 With the latest daily build, it works with my Redmi Note 9 Pro (Orange provider) For me it's the Lomiri message app that can't send a new SMS. (receive is OK) while SMS sending works in command line with ofono.

@domubpkm @Br1 I can confirm that on volla quintus (OTA-7 and devel channel) isn't working either. Same behavior as @domubpkm , call-recording locks mycrophone and speaker on calls. Nothing is captured on saved file. There os anything i can do to track the problem? (Another interesting thing is that looks like the install-script breaks the camera, it make camera app the capability of record videos. Uninstall the script or change between channels doesn't solve the problem, it is just solved by factory reset )

@ancientsounds in my experience the mediaplayer app only plays mp4 videos encoded in a special manner. If you're lucky, they work, or they just don't. Maybe you were lucky until now. I encode or re-encode my video files with Handbrake with standard settings. There was no file yet, the media player didn't play... Maybe this helps...

I would think the statuses have a meaning, but I was not able to find documentation for that. So I'm calling play() for whatever status shows up From what I tested through clickable desktop I found that Loaded indicates the player is ready to play, and apparently if the status is Loading, it is not. But on the phone no other statuses occur, I tested repeatedly and in a couple of cases I waited for at least 10 minutes for other statuses to show up. No luck.

@Lakotaubp It also got the error a few weeks ago then I just tried it again and it worked. Anyway, let's see if there's any news about it

@dimwitflathead Still need help?

@JDee-Intl Ideally, you have to flash the latest Android 13 from their site. Fairphone OS is Android so they're the same. Latest Android 14 would also work however when I tried that on mine, Fingerprint wasn't working. I'm not sure if that's the exact reason though. Maybe you can try it yourself see if it's the same In any case, Android 13 is still recommended to avoid issues that is not consistent with other people. Also, this isn't the right thread for this

@ancientsounds said in UT on F(x)tec Pro1-X: I haven't tried casting to an external monitor. From I was told, the change in hardware impacted this feature. So no display port over USB type C... Also, what I know is that it doesn't work.