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

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

@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

And finally, how can we encourage Sander and Felix to continue their series of videos on Youtube (or elsewhere) to get the ball rolling on developing applications for UBT?
Best regards.
Jean-Luc

gbdomubpkm i'm here.

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

Hello.
I'd like to know how the reviews published on the UBPort site are written (dated?) and if they could be revised.
For the Redmi 9 Pro, the review on the page: https://devices.ubuntu-touch.io/device/joyeuse/ is as follows:
“Under heavy development relying only on the device porters. Many features including basic functionality may not work.
It will be the task of the porter to commit the work needed to make the device reach the standards to become fully supported.
These devices are only for those who are prepared to take the risk of using them."

This is very personal but I've been using this smartphone for a year and a half as my only phone and I find Ubuntu Touch ( 1000 thanks to the porters and developers, I love you folks) easy to use, reliable, great.
This comment could be a deterrent for potential new users when the phone works perfectly, supports all the features and seems to me no more complicated than any other.
Thanks to Ubuntu Touch Team for OTA6!
Jean-Luc

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

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

@UBportsNews
Hello.
I'd like to know if there will be any training courses on application development for Ubuntu Touch in the future, and if there are any up-to-date reference books. Last year I took part in jitsi sessions on application development, is this still going on?
Thank you to the people who devote themselves to keeping this environment alive.
Best regards.

@AppLee
Ok i have joined the crowdfunding campain.
Let's cross fingers now.

@AppLee
Thank you for your update.
Maybe do you know if i order a brax3 now, if it will be UBT installable?

@RobTheBold
I can't answer because of my european location and this is a north america specific band.
Perhaps could you ask this question on Telegram miatoll channel?

@Charly
Damn, that's too bad

I guess, it's it's working for xiaomi ( i have made the same test and the ping continue) that could be fixed.
Perhaps could you fill a bug report.

@Charly
Yes or open a terminal and
ping www.google.com
or
ping 195.238.2.21

@Charly
I don't know how it works in a mobile network, but in an enterprise network, when you use voIP, a non-compressible part of the bandwidth is reserved for voice (per 64k). Perhaps your 4G coverage isn't good enough to allow voice and data to coexist, and by giving priority to voice, it switches to 3G, which doesn't work at the same time as 4G, which it keeps active to continue voLTE.
Simple hyopthesis

@Charly
Maybe not the same framework?
I'm using sapot browser.

@PiotrBujakowski
Original Poster I guess.

@AppLee Ok, I understand.
Thanks.

@PiotrBujakowski
Some changes can be made in the yml file used by installer but brick is not so far when making those tries...