Please correct as 20, January, 2026 instead of 2025.Also,my android device sounds the test alarm but not my Ubuntu touch devices.How to enable them.

@kugiigi NDK is basically a set of C APIs Android exposes to applications, allowing apps written in native code to get access to certain functionalities without calling Java APIs through JNI (Java Native Interface). The good news is that these APIs should largely be usable on Halium-based UT devices as well. So the advantage is that we don't have to rely on bespoke APIs libhybris exposes, which allows us to share more code with upstream which already supports Android (in this case GStreamer). This is not relevant to mainline devices.

@Moem and four stickers Thanks

@pparent said in French ID app interoperability.: They have not reached out to me again I followed your path with the MiDNI and they ignored me as well...

@AppLee yeah thats kinda my issue even if something is working i still never feel "its complete" so while some things my work other things are broken for example the nes repo should at least run as it does on my phone ...but alot of things are almost finished but needing some thing fixed like one thing holding it up for example i made a usb image burning app UT does not allow raw block device writes so i gotta figure this out as well ....but at least this way my friends can poke around

@Feynt That's only odd if you believe that UBports has a plan for which devices are going to supported. And such a plan could only happen in a different kind of organisation. You should keep in mind what UBports is, or rather what we are: a community, a loosely connected group of volunteers. Whether a certain device gets ported depends on there being someone who has the skills has the time has the wish has the device. If there is no such person around, then no port is going to happen. Maybe you could even be that person? To find out, you can start reading here: https://docs.ubports.com/en/latest/porting As is forum policy, your topic will now be moved to the Offtopic Area. Thank you for understanding.

@GabrielDistake Hello Gabriel! UBports does not take porting requests. You should keep in mind what it is, or rather what we are: a community, a loosely connected group of volunteers. Whether a certain device gets ported depends on there being someone who has the skills has the time has the wish has the device. If there is no such person around, then no port is going to happen. Maybe you could even be that person? To find out, you can start reading here: https://docs.ubports.com/en/latest/porting As is forum policy, your topic will now be moved to the Offtopic Area. Thank you for understanding.

Late to the discussion, but on desktop the Yubikey requires some packages installed. So integration would not be straightforward, but I guess something can be hacked if need be. To have the OS support it natively is another story as I doubt an app can bring Yubikey's features to other apps, the browser and wherever it is needed...

@Moem said ... most of us have full lives and don't read the forums every day. Me too, usually. I just focused to try to get something working, due to 30 day ebay seller return policy. Failed interaction with Oneplus support ate up 12 days of that.

A related project to look at: https://blog.mariofragnito.it/en-gb/posts/pitv-my-fire-tv-stick-clone/

@nwoo66 In English, please.

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.

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

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