@klh said in My Ubuntu Touch devices participated in Thailand nationwide cell broadcast test: @peat_psuwit do you have a spec for the Thai EBS? Looks like they require a working SIM card? I have no idea where to look for that. I tried searching on web for it, but nothing that look like it. The only thing I can go by is Android's config file. I still maintain that we'll need a CB topic database from e.g. Android and should not not rely on hardcoded set of topics from a non-regional specification. In theory we should only need the table from 9.4.1.2.2 of 3GPP TS 23.041. Hmm interesting. That spec does indeed list all topics I've seen on my Android phone. I think I've seen a different spec cited earlier that doesn't include some of them. (For reference, I've seen the following topics: 4370, 4371, 4372, 4384, 4396) Still, it doesn't seem to provide a grouping of topics for settings (or maybe I miss something). And it would also be useful to have a database for notification heading (e.g. in US the title for 4370 should be "Presidential alert", but that obviously won't fly for Thailand). Unfortunately, the test today is inconclusive on whether we need to explicitly subscribe to topic "4370" or not. We don't already? According to the same table, 4370 is not supposed to be settable by the user and always subscribed (I'm kind of extending the 3GPP definition of MMI here) so this shouldn't be a question - since afaik it's not required to be implemented at modem level, we should check what ofono reports and subscribe to the missing ones. It's not supposed to be settable, but this doesn't seem to be enforced by oFono. Currently our settings pane doesn't subscribe to this topic, but apparently Fairphone 5 subscribes to this topic anyway. Still, I reckon that we should be on the safe side and always add 4370 to the list of subscribed topics. Also, currently there's no boot-time component which will subscribe to mandatory topics automatically (and on some region e.g. Thailand this doesn't seem to be limited to 4370 only; see the linked Android config). The settings pane is the only component which sets the topics. This is problematic because oFono don't have a set of initial topics (besides a small number of built-in ones from ETWS).

@kugiigi NDK is basically a set of C APIs Android exposes to applications, allowing apps written in native code to get access to certain functionalities without calling Java APIs through JNI (Java Native Interface). The good news is that these APIs should largely be usable on Halium-based UT devices as well. So the advantage is that we don't have to rely on bespoke APIs libhybris exposes, which allows us to share more code with upstream which already supports Android (in this case GStreamer). This is not relevant to mainline devices.

Maybe this is the wrong place to post this now that 20.04 OTA-11 is already released. If so, pardon me, I'll happily start a new post. Thanks to the team for another Focal release! Unfortunately I have lost the ability to receive SMS since updating to OTA-11 last night. Outgoing SMS works as normal. I've tried rebooting, powering off, etc. I'm using a Oneplus Nord N10, and was updating from OTA-10. VoLTE is not (and can not be) enabled. Both incoming and outgoing MMS also don't work, and while sometimes glitchy, these normally work for me too. I've tried restarting nuntium.service, which normally fixes things if MMS fail to arrive with no notification, as they presently are, but it's not changing anything here. I've also now re-flashed the system, again on 20.04 OTA-11, and no change. Having trouble finding anything relevant under Logviewer - Messages. Any suggestions appreciated. Also, while I'm replying here, I was sorry to hear about the flooding @peat_psuwit, that sounded like a major storm. Thanks for all you do for UT!

@Charly I can only see SD cards connected via USB, not in the internal reader

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