After some more testing it seems that VoLTE is not working properly on my FP4. It shows up in the settings and status indicator but as soon as I make a call it drops back to 3G. Is VoLTE officially part of this ota? Is there an up to date guide on how to backup and restore the FP4 on 20.04, I have not been able to find the usual 2 partitions when using adb in recovery mode? I'm willing to try and go back to android, enable/test VoLTE, and restore UT, but backups are a must as it's my daily driver.

@peat_psuwit used ubports-installer to install 24.04-1.1 RC2 with "Wipe Userdata" checked and during the last 24h, calls worked correctly. Thanks.

@bestenaizena Yes, while the option to upgrade to 24.04 was talked about as a major aspect of 20.04 OTA 10, 24.04 isn't released quite yet. From what I understand, now that you have OTA-10 the option will appear to upgrade to 24.04 once it's released.

Thanks @danfro , that's a helpful hint to know.

@oldpaint The framework is set in the clickable.yaml file framework: ubuntu-touch-24.04-1.x And the apparmor version in [yourprojectname].apparmor "policy_version": 2404.1 And to update clickable use clickable update-images Then you can remove unused images with clickable clean-images

Ubuntu Touch 20.04 OTA-9 is released. Thank you everyone involved in the testing. https://ubports.com/blog/ubports-news-1/post/ubuntu-touch-ota-9-focal-release-3962

@peat_psuwit Thanks!

Ubuntu Touch 20.04 OTA-8 is released. Thank you everyone involved in testing. https://ubports.com/blog/ubports-news-1/post/ubuntu-touch-ota-8-focal-release-3953

@peat_psuwit said in On the subject of Ubuntu Touch versioning scheme: We've considered 24.04 OTA-x.y. Unfortunately, (re-)using the word OTA could set the wrong expectation; by using the word OTA, many users will expect incremental, frequent updates (AKA rolling release). Don't worry, users will expect unicorn rainbow farts anyway and while updates are a bit slow, technically UT is a rolling release I'm really sorry that you have this sentiment. I also don't want to change the versioning scheme, but both the technical and practical reasons forced us to re-think how we will version Ubuntu Touch. Don't be, it was mostly a joke, and, while I may not fully agree with the reasoning, it is overall a pretty minor change. I've been on the other side of this experience plenty of times. As a user I get upset about minor changes because they make up a much "larger" part of the user experience vs the experience as a developer where this is an "insignificant" side quest compared to all the development work actually being done Also compare this change to the hot mess that is the current naming schemes from both intel and AMD

There is No update after February 25 for noble next.

@peat_psuwit I overlayed touch.pa for two reasons: to make bluetooth calls work more reliable. So this one maybe get fixed by the MR. to make wired headphones work. For this it was needed to explicitly add the rate=48000 parameter to the load-module command: https://gitlab.com/ubports/porting/community-ports/android10/fairphone/fairphone_fp3/-/blame/halium-10.0-focal/overlay/system/etc/pulse/touch.pa?ref_type=heads#L55

Just wanted to say thank you! OTA-7 arrived tonight on my Redmi Note 9S and I applied it successfully. All seems perfectly fine. So thank you for continuous hard work!

@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

@rocky58 said in CI is now fixed and freeze is lifted: Evidently I am still on the road to ignorance. As we all are. And if never had to work with git that's no surprise. But nowadays most projects I encounter made use of git (can be on-prem, github, gitlab, bitbucket, ...) For a long time I only knew about subversion