Status update on the next, Noble-based Ubuntu Touch release, February 2025

[peat_psuwit]

@lduboeuf See https://gitlab.com/clickable/clickable-docker-images/-/merge_requests/150

[lduboeuf]

@peat_psuwit said in Status update on the next, Noble-based Ubuntu Touch release, February 2025:

@lduboeuf See https://gitlab.com/clickable/clickable-docker-images/-/merge_requests/150

Now the framework is fixed
But still have:

security:policy_version_exists:utzip.apparmor
could not find policy for ubuntu/9999.0

my apparmor file:

{
    "policy_groups": ["content_exchange", "content_exchange_source"],
    "policy_version": 9999
}

[nunesfl]

Hello @peat_psuwit
I have a Xiomi Redimi Note 9 Pro, trying to update to 24.04 in order to test it... it works pretty well on 20.04...
But every attempt I do, the installation stucks in the recovery screen with a message 'Error installing Ubuntu update, exit code: 256', it says to see the log but no log is generated...
Would you have any clue why I may be receiving that error message ?
Thanks,

[Lakotaubp]

@nunesfl You have already asked this question here and have an answer https://forums.ubports.com/topic/10423/noble-based-devel-images-now-available-on-most-devices-with-20-04-devel-image/29 Please do not post the same same question in two places it is confusing and the answer does not change.

[nunesfl]

Sorry @Lakotaubp I thought I did not send the other post replay... I will pay attention to that...
Would you help me with this question ?

[Vlad Nirky]

@nunesfl
I have answered on the other post.

[Vlad Nirky]

Hello.
I'm testing the 24.04 and i'd like to know where I can give feedbacks (here?)
Regards.

As you will probably have noticed, English is not my main language.
Sorry in advance for any language errors

[Vlad Nirky]

@lduboeuf
Hello Lionel.
Could you, in some words, explain what you have done with this info?
I'm landing in gitlab with the next change but how could i use it?
Sorry for this beginner question...

[lduboeuf]

@Vlad-Nirky said in Status update on the next, Noble-based Ubuntu Touch release, February 2025:

@lduboeuf
Hello Lionel.
Could you, in some words, explain what you have done with this info?
I'm landing in gitlab with the next change but how could i use it?
Sorry for this beginner question...

humm, i've just followed the instruction from Ratchanan ?.
Haven't tried again since...

[Vlad Nirky]

@lduboeuf
And how have you fixed 'ubuntu-touch-next' is not a supported framework ?

[lduboeuf]

@Vlad-Nirky said in Status update on the next, Noble-based Ubuntu Touch release, February 2025:

@lduboeuf
And how have you fixed 'ubuntu-touch-next' is not a supported framework ?

just updated the docker images via clickable update-image or image-update, i don't remember well

[Vlad Nirky]

@lduboeuf
Thank you Lionel.
It build the click and as the apparmor is not verified, with clickable install it push the click on the phone and the app (pure QML) is running.

[Vlad Nirky]

@Vlad-Nirky
Great to have Proxmox for those tests.

[Vlad Nirky]

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

[arubislander]

@Vlad-Nirky The camera doesn't currently work in the Pixel 3a either.

[Vlad Nirky]

@arubislander
Thanks for the answer!
Have you tried texting with the phone?
On mine, it doesn't work via messages but well on the command line via ofono.

[arubislander]

@Vlad-Nirky I don't use SMS, so I haven't tried it

[Vlad Nirky]

@arubislander
No problem. Thank you.

[Vlad Nirky]

@Vlad-Nirky
SMS are now working well.

[Vlad Nirky]

@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.’