Thanks a lot.
The installation went without a hitch.
The camera works much better than in 20.04.
voLTE is still fully functional on my Redmi Note 9 Pro in Belgium with Orange.
There's still the known problem that prevents Bluetooth pairing with the car.
As for the rest, I'm happy to adopt it, the OS is superb!

@O.o.
Welcome!
I made this choice a year and a half ago and I have never regretted it.

@libremax
Extremely interesting.
Necessary information that I was missing...
Thank you for sharing, and a thousand thanks to Alfred and those who make this possible.

@domubpkm
Glad to hear it!.
In the next release, i'll fix this size and will add global theme changes and relooking.

@Technotramp
Could you read this discussion, it's a good start place.
https://forums.ubports.com/topic/9957/installation-guide-redmi-note-9s/26

@kugiigi
The new design is very nice, by the way. Thanks for this!

@Lakotaubp
Confirmed

@uxes Xiaomi Redmi Note 9 Pro (miatoll joyeuse global)
getprop | grep incremental
[ro.system.build.version.incremental]: [986]
[ro.build.version.incremental]: [986]
[ro.odm.build.version.incremental]: [V12.0.1.0.QJZMIXM]
[ro.vendor.build.version.incremental]: [V12.0.1.0.QJZMIXM]
Hallium 10.
20.04 Stable with folowing tweaks and 24.04 daily (without any change).
Operator is Orange Belgium
voLTE, SMS, MMS, access point are OK.
volte.txt

@sixwheeledbeast
Hello.
Did you checked the usb parameters in System parameters?

Hello.
I'm trying the 24.04 (r85) on my Redmi Note 9 Pro.
I had an issue while configuring the device.
I have plugged a usb keyboard and after using the top tool bar to change the keyboard layout to azerty belgium.
The system parameter has crashed after i choose this keyboard.
After this, i can't launch system parameters nor any app on the phone (terminal, camera, ...).
The screen pop up and close just after.
Wondering how to look at the log files...

@PiotrBujakowski
Original Poster I guess.

@snailc
Well, maybe @davidfr could help you.

There is a discussion about this on Telegram (https://t.me/UTonFP5).

From AppLee
You probably need to reinstall Android.
What happened I suppose is that you had already fingerprints registered.
Flashing Android will reset those and then installing Ubuntu Touch again should allow it to set the fingerprints.

It worked for me this way.

And another user had the problem and solved it with a couple of reboot...

gbdomubpkm i'm here.

@nunesfl
Yes, the size on a partition is too small.
You 'll have to add argument to the installer command.:
./ubports-installer_0.10.0_linux_x86_64.AppImage -f ./miatoll.yml
and the miatoll.yml can be downloaded here:
https://github.com/ubports/installer-configs/tree/fd9802a07cf67d489a78331af3426c416c677f23/v2/devices

And check the three boxes during install
And, also, the miatoll.yml have to be located in the same folder as the installer (not sure it's necessary but...)

@wally
The recommended is the joyeuse_global_images_V12.0.3.0
but i have always used joyeuse_global_images_V12.0.1.0 and had no problem with this one (for Focal or Noble)
It's better, while you are in android, to test and activate all the stuff wifi bluetooth voLTE gps etc...

@kimo
Nothing but great phones.
I'd add the Xiaomi Redmi Note 9 Pro, which works perfectly with Ubuntu Touch and which I use daily with great pleasure.
If I had to choose another brand and had a bit of time, I'd also look at the Brax3, which is currently being ported.

@Vlad-Nirky
Hope the new version will fix it too.
Let me know.

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