Status update on the next, Noble-based Ubuntu Touch release, February 2025
-
Status of Noble-based Ubuntu Touch (UTNext)
Since the last time I made a forum post, the following features has become usable:
- GPS
- NFC
- Phone call & SMS
- Note that MMS is blocked until very recently. We'll have to recheck if it has been fixed or not.
- Camera, include picture and video recording.
Progress is a bit slower than we expected. But we still are progressing nicely.
For app developers: it's now possible to build & test your apps against UTNext
After a long await, you can now start attempting to rebuild your app against Noble-based UTNext. This should allow you to test whether your app has any problem with the Noble-based images, especially if the app was unable to start on them before due to shared library changes.
For now, you'll need to get a nightly build of Clickable. After that, specify
ubuntu-touch-next-internal
as the framework insideclickable.yaml
and specifypolicy_version
of the AppArmor profile to9999
. You may also also have to make sure yourmanifest.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.ubuntu-touch-next-internal
is a framework which corresponds to the on-going development of UTNext. The-internal
part indicates that there is no formal "contract" for this framework. In other words, we don't guarantee forward- and backward- compatibility with any past and future Ubuntu Touch versions. The framework is intended for testing only and is not intended to be published to the Open Store; you'll have to switch to the final framework when it's available.Due to delays and ongoing discussions, we at the core team are still unable to settle on what versioning scheme and what version number we will use for the next Ubuntu Touch release, and subsequently as the final framework name. We'll have a separated post discussing this in more details and allow you to chime in. We're sorry for this; as soon as we're able to finalize this detail, we'll provide an update to you.
Update: please see a separated post for a discussion around version number: https://forums.ubports.com/post/84517
For porters: it's now possible to drop
touch.pa
overlay(for UTNext, at least)now possible on both UTNext and 20.04If your port is one of the port which has to overlay
/etc/pulse/touch.pa
to provide additional arguments topulseaudio-module-droid-discover
orpulseaudio-modules-droid-card-<API>
, it's now possible to instead provide extra arguments using an Deviceinfo property. The property is calledPulseaudioModulesDroid_ExtraCardArgs
[1] and accept all arguments which you may add topulseaudio-modules-droid-card-<API>
. For example, you can put this in your Deviceinfo overlay to set sampling rate of your device's audio chip:PulseaudioModulesDroid_ExtraCardArgs: "rate=48000"
Combined with a change which allow you not to hard-code API level, it should now be possible to drop
touch.pa
overlay entirely. This feature is now merged into UTNext and 20.04, so you'll be able to share your device tarball between 20.04 and UTNext.[1]: In case you're wondering, yes, there are
PulseaudioModulesDroid_ExtraGlueArgs
andPulseaudioModulesDroid_ExtraHidlArgs
as well. However, I believe you won't need them. -
@peat_psuwit
First test, i'm with clickable 8.2.0, got this while doingclickable build --arch=arm64 --accept-review-errors
:- security:policy_groups_exists:utzip:utzip.apparmor
could not find policy groups - security:policy_version_exists:utzip.apparmor
could not find policy for ubuntu/9999.0 - security:policy_version_matches_framework:utzip.apparmor
Invalid framework 'ubuntu-touch-next-internal'
I have checked the docker image, i'm on 24.04.
click-armor and ubuntu-sdk-libs seems old:
click-apparmor 0.5.1~20241107093457.7~2d4aff7+ubports~dev
ubuntu-sdk-libs 24.9+17+0~20250103234741.19+ubports~dev~1.gbp061821 - security:policy_groups_exists:utzip:utzip.apparmor
-