@Kadafi said: using Ubuntu in a mobile phone is simply amazing! Word, sibling Glad to hear you're experiencing the freedom that UT brings! Tell your friends!

@gpatel-fr it does not work. The symptoms are the same.

@mihael Not on all devices, I expect. Some need a more complicated song and dance to unlock.

@Moem yeah ... that is why I replied to MarcelloTogg - to see if cups WORKED for them, or they WANTED cups to work for them.

@MrT10001 Thanks for your reply. I actually had UT running on another x306f which unfortunately slipped out of my hand and fell from the balcony of a hotel room on the 4th floor (true story ). Rúben doesn't mention EDL on https://gitlab.com/ubports/porting/community-ports/android11/lenovo-tab-m10-hd/lenovo-m10-hd/-/blob/main/README.md?ref_type=heads

@gpatel-fr @FlavioMala, indeed the newer Bluetooth stack had the side effect of breaking usb_tethering. I could fix it by applying a small patch and recompiling the kernel. The patch is attached to the issue.

@lduboeuf This has been my experience using a Oneplus N10. Since VoLTE landed, idle drain has seemed notably less pronounced. A very nice surprise, especially on a device with an aged battery.

@projectmoon I installed the package qtubuntu-qt6 provided by Ubports into my bundle, the same that is used in Morph Qt6 version.

@gpatel-fr Ok I'll wait a little bit more time before the upgrade though... Thanks!

Thanks for the tip @OtaDr , but it looks like I have a corrupted FASTBOOT (black screen).

@k.nacke im finally back with the tablet, can you teach me how to port a device

@Moem said: @oldbutndy Sorry, no idea! I would hope that someone looking for information would get their info at the source: our webpage. Not an AI summary that may or may not be correct. I may be oldfashioned... but I always try to look for the original source. Agreed, but I restarted my search 2025 December via Google and I know I also read the UT device page (because I made a spreadsheet then, comparing the top choices, and included details such as wireless ext display). I don't remember device page clearly saying VoLTE not working, main developer carrier NOT using VoLTE, and therefore low likelihood of P3A XL ever getting good VoLTE, and no native VOIP app for current UT release. So, I ordered the 3A XL, installed UT (great easy process, but it IS easy on an unlocked Pixel, and I had already been through similar process with LineageOS, on P XL, and 4XL.) I also don't remember in early December, whether Nord N10 5G was yet working for VoLTE, but by late that month I got replies to forum questions suggesting I try it (since 1 person had it working in USA on T-Mobile). That meant 'possible', at least. (so, I bought 1 !) All I am trying to say here is we need to keep striving to make sure the main UT landing pages are accurate, especially for critical details: examples (1) do any device pages clearly state that some highly promoted devices are missing bands required by some carriers in some countries ? or (2) on another brand, if you brick the main board during UT install, you effectively cannot get a part replacement in any country but France (if I understand that thread correctly). Those 2 facts might cut 2 of the MOST recommended options for US purchasers. So, last I checked, Nord N10 5G is not highlighted, but if in USA, and you want a phone that works on VoLTE now, and lasts a bit into the future, Nord N10 5G is the ONLY economical viable option ? If google quick search gets it wrong, and Dive Deeper gets it wrong, but people find UT device page and critical info NOT obvious, and new people waste time & money, isn't that at least partially our fault ? I understand that someone IS doing their best to update the tiny details, on device pages, but I was told that is completely different from adding a sentence to a paragraph on a web page (I did not know that). That is why I tried yesterday to see if I could improve the data that Google fed to people. I hate feeling helpless. I have no idea how to edit a webpage. (and I did not yet bother to ask Google about it.), And, since I am a newbie & keep finding conflicting info all over, I would not want to edit a page unless I was POSITIVE about it. I don't want to make anything WORSE !

@grenudi Thanks for linking that thread, though I've not had time to read it fully now. I am aware of the Halium approach vs. the mainline Linux approach, and I am somewhat (at least superficially) familiar with the downsides and upsides of each. I will try to read it in its entirety during the week to gain more insights. I am mostly interested in a mainline distro on my phone, but my plan with this second hand device is to familiarize myself with all possibilities available that will run on my device. postmarketOS is what I plan to try after Ubuntu Touch. I've been quite stoked about the recent progress posts on Mastadon by Luca Weiss (and his FOSDEM talk) on getting stuff like the camera and the battery gauge working. I understand these things are not trivial with the locked down mobile chipsets, even for someone directly employed at Fairphone. I'm testing them out in this order in hope of being able to contribute over longer time to testing stuff for postmarketOS.

“Sounds really interesting! If the UT port on the FLX1 turns out stable, it could be a solid alternative. Dual boot support is a nice bonus too—curious to see if they’ll eventually make it work with the main storage

No problem for devices with MTK Power Bypass. @arubislander said: Unless you don't mind your battery degrading, because the device would be constantly plugged in to the charger, you would have to device a routine for charging and discharging the device.

@KJU said: About adb&fastboot from the UT terminal, though, any such barrier there? There shouldn't be, no. I happened to pull a file from one UT device to another via ADB. So I know that works. In haven't tested fastboot myself, but I see no reason it wouldn't work.

@gpatel-fr You are correct. "How to enable developer mode" states enable USB debugging (<- me bad - didn't see correctly), ADB, or Android D... Bridge". Sheng-Cheih P.s. i'll try again after shower nap - so sleepy now.

@projectmoon The main problem that currently prevents using Wayland for electron apps, is that the On-Screen-Keyboard cannot work with GTK+Wayland+Mir1.x . By the way the Merezhyvo Browser ( popriatary app ! ) is an electron app using Wayland, but it has found it's way around this problem by coding it's own OSK inside the app itself, which is not really a way I want to go. (Especially for Signal because I want to modify the code only as strictly necessary, and also because for Signal there are other problems when it comes to using it in Wayland mode with Mir1.x). Anyway I've already tried it (see in the Signal UT topic), and reallu the best is to wait for Mir2.x, I hope it won't be in too long.

@sermountain Dualboot with UT is not supported by UBports but directly from Volla. You may get some help here of other users, but not very likely since Volla support does not participate in this forum.

@arubislander said: it is not the case for video codecs either indeed. This week-end I tried seriously to add ffmpeg codecs to my FP5 with 24.04-1.2 stable and basically succeeded, see https://gitlab.com/ubports/development/core/lomiri-messaging-app/-/issues/359#note_3122981838 So it is possible to play ALAC files with the existing UT applications (mediaplayer...). The fact that it is slower than when accelerated by the hardware is true of course, but a not too old processor like the FP5 one is powerful enough to handle simple video files without acceleration (did not try 4K though).