Status update on the next, Noble-based Ubuntu Touch release, February 2025
-
@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-imageor image-update, i don't remember well -
@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
Great to have Proxmox for those tests.
-
@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. -
@Vlad-Nirky The camera doesn't currently work in the Pixel 3a either.
-
@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. -
@Vlad-Nirky I don't use SMS, so I haven't tried it
-
@arubislander
No problem. Thank you. -
@Vlad-Nirky
SMS are now working well. -
L Lakotaubp referenced this topic
-
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.’
