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

@peat_psuwit Hello. As Alfred said in the last Q&A, clickable continues to evolve. After a clickable update-images, how should clickable.yaml and manifest.json be for compiling (and installing) applications on a phone with the latest Noble nigthly build? Is this still relevant? ‘For now, you'll need to get a nightly build of Clickable. After that, specify ubuntu-touch-next-internal as the framework inside clickable.yaml and specify policy_version of the AppArmor profile to 9999. You may also have to make sure your manifest.json specifies @CLICK_FRAMEWORK@ in the framework field so that the correct version is filled in automatically by Clickable (sadly a similar mechanism doesn't exist yet for AppArmor policy - see this issue). When building, you'll have to specify --accept-review-errors for now, as click-reviewer-tools has not been updated.’

@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

@AdhithAdhi I already answered in your other post. Sadly your device has not been ported to focal (yet?).

@lduboeuf We are not using systemd itself on 16.04, and the kernel version requirement is a bit of a misunderstanding. This update still doesn't mean we're using systemd for the init system. However, the systemd source provides many things which we do need, such as udev. Newer kernels are only required for some features of systemd, and newer versions of systemd may require newer kernels, hence the comments relating those two as a concern, along with the need to upgrade to 20.04.

@Flohack @peat_psuwit I believe I got this new version in the rc update from this morning. Thanks to everyone for the amazing job pursuing this... I'm still patiently waiting for my Pro5 to work without noise for bluetooth calls... Again, great job!

@dR0W Ok. It seems like Pulseaudio is unable to enable "voice call mode" on your BT headset for some reason. To help investigate this, please follow this: Disconnect the headset if connected. Run echo 'exec pulseaudio --start -vv --log-target=syslog' >~/.config/upstart/pulseaudio.override to enable additional logging on Pulseaudio. Run initctl stop pulseaudio then initctl start pulseaudio. Note that restarting it won't take the settings above into effect. Now, connect your headset, then have a call. Send me the file /var/log/syslog. I'm not sure if it contains sensitive information or not, so you can PM me if you want. After testing, remove the config file by rm ~/.config/upstart/pulseaudio.override Also, if possible, could you please retry this with the old version of Pulseaudio?

Ok, I have now a fresh flashed Oneplus 3t dev and I installed the GStreamer-droid based camera. In the camera app I see always a 2:2 layout but the pictures I shoot are in the layout I set (16:9 in my example). Screenshot: [image: 1604927264339-screen.png] Picture from the same position: [image: 1604927275434-bild.png] Anybody else with this problem? How could I fix this?