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

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

Merry Xmas!

@gpatel-fr It's really as simple as, if set to English (Canada): Contact: +15145555555 will reliably be found by prediction once I type +151 Contact 15145554444 will not be found no matter what I type Contact (514)555333 will not be found no matter what I type Other contact formats (514) 555-5555, similarly won't be found. Nothing without the initial +. Anyhow, I'm quite happy about the T9! Many thanks to you for making me aware of it, and for your help in diagnosing things. And many thanks to Lionel for creating the function! My extensive (long-winded) testing was to try to be helpful, but I'm quite satisfied with how things function at present. If the phone number predictions get improved for databases as mangled as mine, and various weird international standards, all the better! But sadly, I don't think I'm the person who will succeed with that.

@Bolly Oh... look at that! And to think I never knew!!

@RoobunOne Well, you'd have to make a port. To see if you are up for that, start reading here: Porting Guide

@jukebox3711 That took a long time! I guess it's a busy time for the mail. But it finally reached you, I'm glad to hear that. Thanks for the good news!

@wally Yes, I was adjusting the edges in UI tweaks. However as I stated in other thread I never liked swype OS navigation. Expanding the subject, I also don't like touch OS navigation. Touch screens register the touch "without my consent", i.e. when I just grab the phone. That's wrong, but it's been like that since the beginning of all mobile OSes. I'd love to see an option to enable touch-and-confirm input where you touch and have to swype a bit immediately to make the original touch point registered as touch, otherwise it's meaningless

@Gelukkig said in Apps I really would love: @projectmoon Thanks, I have installed all the apps you mention. For Waydroid I still need a Google account and the purpose is to get rid of Google and Apple accounts The default image of Waydroid does not have Play Services or anything else. As others have said, you can download F-Droid then use that to install Aurora Store, and from there, install apps that are on the Play Store. But as for bluetooth, this will not work in Waydroid. It is a limitation of Waydroid itself.

@enki said in top 3 app wish list for Ubuntu 24.04: Conversation for xmpp chat audio/video client There is an experimental port of Kaidan being developed: https://gitlab.com/alaskalinuxuser/kaidan_0_6_0

@gpatel-fr I see, thank you for clarifying.

@gpatel-fr said in French ID app interoperability.: The recent decision about digital control is concerning troubling for a UT user What are you talking about precisely?

@neinei0612 I'm sorry, that is outside of the scope of this forum.

@bekun Yeah that's the ideal functionality. On Android, that works fine, at least on Samsung phones. In UT, all touchscreens are mapped to the built-in display. I was talking about on the desktops. Gnome have the same issue while KDE Plasma handles it fine.

@jeffreyk Hi, it doesn't work like that. If your device is not on the supported list and a search doesn't show any one porting the device then if you have the skills and knowledge you will have to port UT to that device yourself. The alternative is to get a device that is on the supported list.

@edisss No one knows! There is no list, it depends on whether someone owns the device and the skills, and steps forward to do the work.