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

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

@Sander I hadn't tried that! THANKS

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

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.

@sixwheeledbeast Hmm good to know, thank you!

Hello I've managed to send a file using Bluetooth. First to get bluetooth running again, I've reset the device. After this, bluetooth service worked again normally. As advised by @gpatel-fr, I've installed bt-obex using crackle. crackle install bluez-tools I've then opened 3 Terminal tabs to run these tasks in parallel: Terminal 1 # To find the Android phone receiving the file bluetoothctl scan on # Find and copy the MAC address of the Android bluetooth adapter to paste it in terminal 3 Terminal 2 # Start the obexd tool /usr/libexec/bluetooth/obexd Terminal 3 # Make sure that the Android bluetooth device is discoverable # Send the file with bt-obex bt-obex -p [MAC address of the Android bluetooth adapter] /tmp/test-bluetooth.txt On the Android device, make sure that you accept receiving the file from the Ubuntu Touch device and check that the content is sucessfully received.

@viko As has been said, dtbo.img is generally not needed. If the port doesn't boot, the issue is more like due to other reasons. Feel free to check the porting docs I linked you in Telegram.

@maahymot Not that I know of, but I also do not own the Mi A1.

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

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

@bhdouglass One thing that I'm missing in the new site compared to the old one, as a developer, is to be able to have an overview of the stats of all your apps as once.

@Merlu said in Flashing firmware takes an eternity: stuck at the step "flashing firmware" since hours. I take it that 'hours' means literally more than 120 minutes. If it is the case, I'd say that it's abnormally long, yes. It could maybe mean that the download from Internet crashed (network glitch), or that after a successful download the transfer via USB crashed. IMO the #1 probable culprit for this last problem could be a low quality USB cable. In both cases you'd probably expect a good error message, but the installer is not that polished to have faultless (!) error reporting. @Merlu said in Flashing firmware takes an eternity: Is there a risk to brick my phone if i interrupt the process? Possibly but if you are stuck since 3 hours, I don't think there is much else you can do. Normally the low-level firmware, that allows for the phone to be flashed, is not touched by the process, so even if the phone don't start after that, you can try again to flash it, possibly with a better quality USB cable. That's exactly what happened to me when I installed UT.

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

Confirmed! OP N100 Verizon via US Mobile 24.04-1 daily

@Merlu maybe you could give a try to what I advised you in your first thread: https://forums.ubports.com/post/91928 that is, retry the installation with another USB cable.

I honestly don't understand most of these thing. I don't know what NDK is But may I know what's the advantage of this? Would it have better performance? Also, I assume this can only be used on Android devices and not mainline?

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

Best wishes to everyone for 2026! 🥳