@MrT10001 i already do that

I have downgraded to Android 13 using the tool from the Fairphone website and then I re-installed Ubunu touch 24.04 stable. Now everythings works as it should. Thanks for the help!

@vverve ubports installer to lito version as unsupported will work ? And, is daily 24.04.2nn the version I want, for best chance at VoLTE functionality ? Or I need to do something special ?

@MrT10001 Alright, will do! Thanks!

@toniox EDL is different on Xiaomi devices. You have to use the MIFlash tool and use a MI account to log in (a complete f*&*&^$$ around to put it politely to get that done), then download the latest fastboot ROM for that device and I mean the latest fastboot ROM, unzip it and direct the MI flash tool to that. Hold Volume UP and Volume down together and plug the device into the PC and it has to be a Windows PC, MiFlash will not work otherwise, ensure you leave the bottom right box ticked for clean and install, do NOT lock the bootloader. Then start the process. If it fails, keep trying, it will work eventually. Unbricked my Mi A3 using this and it took a lot of attempts. The other EDL mode is mutch the same, but requires opening the back, removing the mainboard cover and shorting the two EDL points, which requires fashioning a tool to do so so you can short the points and plug the USB cable in without requiring 4 pairs of hands. EDL mode should work as it is the lowest point of entry to reflash the stock ROM and as the phone boots with that dialogue it should work. What I cannot understand is an Xiaomi repair centre couldn't do this procedure! Any pro repair shop should be able to do this. The other alternative is to buy a broken one and swap mainboards to get a functioning device. It depends how far you want to take this.

I have pushed 4.19.265 to the repos, daily images should pick it up any moment now. We're getting closer!

Best you can do is update to the daily channel of your current baseline Ubuntu Touch version, and not update it for a while. It would have been to risky including the workaround that late in the release process. But yeah, the problem has been identified as being partially caused by opportunistic auto suspend of the phone.

@arubislander yeah I switched up the codenames it’s focal and noble

@pparent thanks for the explanation, it's indeed faster than the more convoluted process I was following. So I did about 6 messages each having 5 photos, lomiri-messaging memory footprint increased steadily by about 100 K for each message (that I never actually sent, it was a dummy number). When I closed lomiri-messaging all this memory was reclaimed by the system, and if I open it again I don't get back the high memory use even if I open the same contact. So there may be a leak but it hardly seems a blocker on my phone - that is, my current use of the phone is that as soon as I have finished using an app, I close it, and each evening I shutdown the phone for the night. You may use your device very differently of course.

@DJac Comme j'ai mis dans la description de l'app pour cela il faut attendre que l'on passe à Qt6. Il faut être patient au niveau de l'upgrade systême, mais je pense qu'on peut maintenant l'espérer d'ici à quelques mois. Ensuite les messages fonctionneront bien! En attendant tu peux utiliser le Morph Qt6 beta, Min browser, ou Chromium for Ut.

Hopefully there'll be a Nextcloud-gpodder integration soon. That's the only thing preventing me from using this instead of Antennapod via Waydroid

@0xecution3r Yeah they wear out over time. I have replaced the ribbon cable and buttons on a lot of used devices. You can mark this topic as solved by marking it as read and then solved.

@bgriffis Next time you need maps, use one of the sensor apps first to get lock (Messwerk, etc). Should lock a lot faster.

I also struggled getting into a development ready state due to the readme inconsistencies. An unfortunate barrier to entry. That said, it looks like this would bring Clickable deps up to date for Noble (once merged): https://gitlab.com/ubports/development/core/lomiri/-/merge_requests/254

@Vlad-Nirky I asked about this in the ubports Matrix channel some time ago, because of course I want to implement the Yubikey challenge-response thing for KeePassRX (it's supported by the underlying Rust library). I was told the OS doesn't have full integration yet, at the OS level. But as a disclaimer, I didn't actually bother trying it myself yet lol. The Yubikey WILL be picked up as a USB device, at least, if plugged in. It shows up as an HID keyboard to make use of the pre-programmed typed password feature thingy of Yubikeys. I don't know if any of the other features of Yubikeys would work yet, though. One way to find out...