@muskist As far as I have tried and am aware, Noble (24.04.x) does not work on this tablet yet. I have kept all mine on Xenial and Focal after trying to install Noble.

Hello Marius, For me it is priorty between 1 and 2 I have an issue what cost me time and a lot of nerves: For my work I send a lot of voice messages. And every second time the microphone don't work. So I have to start the phone again. Eric H meant, it is a bug and gave me this link: https://gitlab.com/EricHeintzmann/ubuntu-touch/xiaomi-surya/-/issues/26 I would appreciate it very much, when it get fixed. My smartphone is a Xiaomi Poco X3 NFC The chat you will find on: https://forums.ubports.com/topic/11722/no-network-connectivity-microphone-is-not-working?_=1769183571861

I just received another call, and I experienced almost exactly the same behavior. The phone didn't respond to the power button, and the screen wouldn't turn off. However, after a reboot, the brightness level was normal, and everything is functioning as expected now. I'm currently on 24.04-1.1.

@developerbayman That's great! Do you mind if I tinker on it a bit? Then I can upload my copy (like on gitlab) so you can see the changes? Mainly working on adding content hub so the end user can pick roms that they have stored on their phone. With that said, yours comes with alot of roms built in, but aren't there license issues with distributing those roms? For the one I was tinkering on, I dropped all the roms and put in several open source home brew roms, like D Pad Hero I & II, which are GPLv3. I don't want to hijack your project though. Just thought I'd help out with this one, because it is interesting to me. Whatever you release is completely up to you.

@toniox if the phone is mediatek, use spflashtool. its a pain in the *** to do, i recommend using windows for rhis because otherwise you'll need a custom kernel and all the tutorials will use windows. the steps go like this: download drivers, and set them up use bootrom bypass tool flash with sp flash i recommemd dumping nvdata,nvram,nvcfg,protect1,protect2 from NAND using spflashtool before flashing anything at all (think of it like youre phones ID it is needed for service ,wifi ,bluetooth) there is also ways to regenerate the checksums so with lockee xiaomi bootloader you can run custom code but i dont really remember how i managed that one.

@yuu-ä3 System settings offered the upgrade and unwisely I applied it only to find the phone more-or-less bricked. After a few false starts (see my posts) I was able to restore 20.04. My advice: DON'T TOUCH 24.04 on OP6 or 6T until there is an announcement about the port (Unless you are able to contribute to the porting work)

@HarryBass I can't help you much as I use another device, however browsing the bugs on gitlab, maybe there is a problem with the stable version for your device when using Volte as pointed here

@DJac Version 3.1.0 was for Xenial, 16.04. You need to use a newer version for Focal, 20.04. I'd uninstall the other one first if I were you. I did mention this for you on the Matrix channel I mentioned above and Jonatan was unaware that it had disappeared, so perhaps it'll reappear in the OpenStore for those on 20.04 soon.

Bonjour, J'ai installer UT 24.04/daily comme le suggère Ruesaga, et effectivement, le wifi fonctionne. Je vais tenter de prendre un peu plus de temps la semaine prochaine pour tester plus en détail mon redmi avec ubuntu touch. Merci pour votre aide.

@PhAndersson My knowledge of apparmor is basic unfortunately. In particular, interaction with dbus is something I never looked at before UT, and bluetooth and network management with apparmor is totally unknown to me. Yes my suggestion of using network bluetooth was not very well thought out, I was believing that maybe there was special in associating the two, as if there was a right called network_bluetooth. My bad This said, there is something that bothers me in your log: it suggest that there is a denial in the sending FROM the server (the systemd service) TO your app. Usually when a sending is denied, it is the sender that is lacking rights. So following this idea, it could be the system itself that is missing a configuration. However, see above, I have no idea how rights are managed for the bluetooth services. Maybe all that is needed is to add an apparmor profile for the obexd executable, but often the obvious solution is wrong. Note that if you want to test it, there is no need to turn your rootfs r/w, with overlay or bind-root you can 'add' stuff in read only directories. Sorry not to be more specific, but going deep in system administration takes time and concentration and I'm currently in other stuff.

Just to say I switched from Hallon (Tre) to Halebop, now everything works.

Just to say I switched from Hallon (Tre) to Halebop, now everything works.

@pparent said in French ID app interoperability.: This is no longer relevant at this time: hmm, it did not take long for this beast to resurrect: https://www.lemonde.fr/pixels/article/2026/01/22/le-gouvernement-n-a-pas-renonce-a-acceder-au-contenu-des-discussions-sur-les-messageries-chiffrees_6663627_4408996.html

@lduboeuf Will do, thanks.

@tigermoth Aside from the Asus phone from a decade ago what are intel phones? Also, it's not just about UT, the underlying software stack needs to support them first.

@tigermoth without being able to permanently unlock the bootloader this is a non-starter, anyone's feeling notwithstanding.

@ChromiumOS-Guy Thanks. I will try soon.

@a20sporter can we take a look at your deviceinfo file?

@slimjim Works perfect. Thx vm! Didn't get the native OpenVPN in UT running to my VPN Provider, but with Network Manager on the command line and your guide everythings just fine!