@donieck
That's a possibility, which is why I suggested reinstalling the latest OTA for 20.04 to confirm or disprove this hypothesis.

@donieck
Another option would be to contact your operator to check how to connect your phone to their mobile network (or search for this setting among other users of this provider).
Usualy

in System settings / cellular / Provider and acces point name / Access point name / internet (sorry for the labels retranslated from french)
You'll have to restart to phone after any change.

@donieck
Hello.
Could you to downgrade to 20.04 stable with UBports installer ?
If the SIM card works with this release, try to return under 24.04 stable.
And if the problem is back, please tell us in https://gitlab.com/ubports/porting/community-ports/android11/xiaomi-redmi-9/xiaomi-lancelot/-/issues

@ubuntoutou
Brute force...
Excellent username!

Hello.
Listening to Alfred yesterday during the Q&A (very interesting, as was his conference on UT, which is a must-see), I wondered why it wouldn't be possible to free up space by modifying the UT installation process.
First, install the OS without any applications, and then, on first boot, download the applications that are currently included in the OS and install them in the user space.
This would save space and solve the strange behaviour encountered when attempting to uninstall these applications.

@UBportsNews
The use of snap packages under UT takes place in a specific context (AppArmor, read-only file system, custom OS implementation, etc.).
Are there any links where information is available to understand how snap works in this context?
Thank you to everyone who gives their time and skills to advance this essential OS.

@ozzy03
Hello and welcome.
There is a dedicated Telegram for this purpose:
https://t.me/ubports_devel
and for apps
https://t.me/UbuntuAppDevEN

@gpatel-fr
Not so hard and usefull
you must know which yaml file is used for the wifi in /etc/netplan
as root cd /etc/netplan and cat yaml files.
nano 90-NM-5f1fe55a-2996-4485-b6b3-a75fe76edc62.yaml (ie)
Then in the wifi one
replace

      dhcp4: true 
with
      dhcp4: false
      addresses:
        - [your wanted IP]/24 (or less)
      routes:
        - to: default
          via: [your router IP]
      nameservers:
        addresses: [your DNS1, your DNS2]

save it
and validate it by
netplan apply

@gpatel-fr
You could fix IP (as I did)

@gpatel-fr
It looks like things has changed since the tests we made in march...
Sorry I haven't verified that it was still working
I had some trace in terminal launching (as the service)

sudo systemctl stop ofono.service
sudo /usr/sbin/ofonod -d -P ril --nodetach

To run it as a service
add "-d" to the ExecStart command in /usr/lib/systemd/system/ofono.service.d/lxc-android-config.conf

@gpatel-en
Perhaps you could get more information by putting ofono into debug mode.
stop ofono then
/usr/sbin/ofonod -P stktest,sap,udev,dun,smart,hfp,hfp_bluez5,provision,binder --nodetach
I used it with Marius to know if voLTE was enabled on Xiaomi Redmi Note 9 Pro.
Then you can check 'journalctl -rb -u ofono'

To know if voLTE is enabled, the call experience is really not the same:
Short connexion time and voice quality better.
If the other phone you call is on Android, you will see if it's in voLTE.

@Biplabro
Hello.
Are you connected via ssh or adb?
In that case, the command to copy is CTRL Shift C and the command to paste is CTRL Shift V.

To change the UT interface (which suits me perfectly), search for Launcher modular in the OpenStore.

@zakafx
Because I respect UBports desire to distribute a read-only system that provides users with a secure and controllable experience by default.

@k.blitz
I will respond to you in a private chat.
I do not wish to spread subversive ideas on the forum, but I share the belief that everyone has the right to know and experiment (at their own risk).

@domubpkm
OK, did you change the update channel to RC?

@pparent
On my phone (Xiaomi Redmi Note 9 Pro), in System Settings/Mobile
I can check 2G/3G/4G
and in Operator and Access Point I can check 4G Calls (VoLTE)
(not always immediate)

@sixwheeledbeast
To use UT, you must never relock the bootloader

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

@Escain
Hello.
Perhaps I missed it, but which version of UT are you using?

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