@arubislander Ah! Apple issue. Apology completely forgotten.

@toniox if the phone is mediatek, use spflashtool. its a pain in the *** to do, i recommend using windows for rhis because otherwise you'll need a custom kernel and all the tutorials will use windows. the steps go like this: download drivers, and set them up use bootrom bypass tool flash with sp flash i recommemd dumping nvdata,nvram,nvcfg,protect1,protect2 from NAND using spflashtool before flashing anything at all (think of it like youre phones ID it is needed for service ,wifi ,bluetooth) there is also ways to regenerate the checksums so with lockee xiaomi bootloader you can run custom code but i dont really remember how i managed that one.

@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

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

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