@Sander Testing testing 1. 2. 3... YES It works! What a great app this has become. It's a winner!

@jonius said in Issues with clickable gdb / gdbserver: @Talkless I just realized that I lost track of this one back then. Do you still encounter the crashes you were trying to debug? Sorry I haven't tried to build or debug PureMaps since forever. Honestly I just use OSMAnd via Waydroid. A bit defeating UT purpose but it just works for me.

@viko Happy New Year! The dtbo.img contains part of the device tree, and as such it is important. However, during porting it is often not necessary to change that information, and in those cases the file is not provided. If the file is not in the artifacts downloaded from GitLab, then most likely it is not needed. (Disclaimer: that is my experience from my own port.) Do you look at generic install instructions, or instructions specific to the port?

Yes, Mi A1 is not my primary phone, I just use it for testing. Is there any other newer port which I can test? something like GSI flashing?

Best wishes to everyone for 2026! 🥳

@trynafindbhumik You just got your answer on the Telegram group, so just for completeness: No, each device needs its own port, and there is no port for that device. That means it's not supported. Supported devices are listed on https://devices.ubuntu-touch.io/ This topic will now be moved to off-topic.

@oldbutndy i think ,proove me wrong ,volte is only working on 24.04-2.x for oneplus n10 .

@sixwheeledbeast Hmm good to know, thank you!

@MrT10001 okay , i formated userdata partion to ext4 and flash again but this problem continues...

you might want to teach her to force shutdown, which is a little tricky for this model, just in case

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!

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