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.

@MrT10001 how did you flash 24.04 exactly? for me there is no boot.. install with system -> boot hangs on the bootloader warning screen. install 24.04-1x stable or daily with ubinstaller 0.11.2 on ubuntu -> boot hangs on the bootloader warning screen. downgrade with installer to 20.04 works ! Btw-James what did you managed?

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

I think I might have a similar problem with my Fairphone 5. Today, I received a call, after which I couldn't turn the screen off anymore. The phone wouldn't respond to the power button. I wasn't too bothered by this since I needed to send a message after the call, so I continued using the phone. I started up Waydroid to send the message. After that, I tried to force reboot the phone since the power menu didn't pop up. Unfortunately, the phone booted to a black screen. I could still hear the screenshot sound, though. Now this happens every time, and I can't see anything on the screen. Touch inputs are recognized, and I briefly see the screen lighting up when I run: sudo systemctl restart repowerd However, it doesn't turn the screen back on. I've also tried reinstalling Ubuntu Touch (stable, RC, and daily channels, even 24.04-2.x/daily), but that hasn't made a difference either. I'm aware that a full wipe (including userdata) could help, but I'd prefer to explore other solutions first if possible. Any help is appreciated!

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

@pparent No, it doesn't use a popup. After clicking that field another page does open. I do agree, I too don't see why this should fail. Its not a special function. It might have been simply bad luck or rather bad timing. Maybe the requests had not been synced to this client but my laptop already had them. But I decided to ask anyway, just in case you might have had an idea. So I guess lets not worry about this.

@HarryBass Hmm. I don't have any great answers, but a couple ideas. First, please state what version of UT you're using (20.04 OTA__ / 24.04___), it could help others assist you. This thread is mostly about MMS issues, but at one point the user describes losing SMS messages as well. After a few days of SMS not working, it seems that the Terminal command sudo systemctl restart ofono caused a bunch of undelivered messages to come streaming in. The poster has not described whether they rebooted during the time that SMS wasn't working, but I'd suspect that one would've tried that at some point, and that for some reason the restart ofono command did something that a reboot did not. Receiving SMS half the time seems different, but I thought I'd provide what I could. I have what seems to be unique issues with my OP N10, which also involves undelivered SMS, but if a flickering screen upon shutdown/reboot happens to you, let me know.

Good option for controlling your audio volume in desktop apps is to install pavucontrol in libertine

@DJac I don't know what you ordered and what you received so I can't have any opinion on that. Well, I'll post again the possibilities I see: 1) the hardware you got is defective 2) the hardware you got is functional, but there may be several submodels of the phone and the new camera is not 100% compatible with the previous one. 3) something else was damaged when the phone did fall. 4) there are problems with the repair. Whatever the reason, if you asked for the exact same model that was included in your hardware and you got another variant, the vendor has made a mistake and you can ask for a return.

@oldbutndy The porter is also looking into this. Will update if we figure out why it did not work like the N100.

I've been testing this build, and it works really good! My only problem is that some characters just don't show up, especially q, y, f, g, h, and k.

@danfro nope! Apparently it should have been -2 instead of -1. I've updated it in the original post.