And some pics: [image: 1780593457929-photo_2026-06-04_08-50-30.jpg] [image: 1780593457952-photo_2026-06-04_08-50-38.jpg] [image: 1780593457970-photo_2026-06-04_08-50-42.jpg] [image: 1780593457991-photo_2026-06-04_08-50-46.jpg]

gpatel-fr said: I realize belatedly that I did not think of giving some advice about the problem of returning back to a newer version once the goal of revert to a previous one has been achieved. It would be easy to imagine that it will be easy, but it's not as straightforward as following the usual procedure. When going from 1.1 -> 1.2 -> 1.3, history of these upgrades was recorded. If the phone is rudely returned to 1.1 and the user asks it to update back to 1.2, it will look at this history and conclude 'I have nothing to do !'. So the way to go in this case is to delete all this history in the lower part of the phone screen by swiping to the right and pushing the red trash button for all theses updates, and then the normal update behaviour will be restored back to normal.

@vince.vs said: I don't know how to use your information in a terminal; copy and past doesn’t work, copy & paste work in UT terminal, but it's a lot easier to connect to the phone with ssh when both the phone and a computer are connected with wifi.

@domubpkm The app itself would be doable but the packages aren't doable since they ust replace system files so translations can't be processed. I mean it's doable but it'll take for someone to modify each file manually and create separate packages per language

Hi @Thomasb98, There is a documentation: https://docs.ubports.com/en/latest/porting/introduction/ Hope it helps... It seems feasible because this device is supported by lineageos and kernel source code is available: https://wiki.lineageos.org/devices/PL2/ Do you have the version with 4 GB of RAM or the one with 3 GB?

Those still requiring a token after converting to the global ROM, can you check if the boot loader image flashed? Maybe try flashing it manually. Ruben says it should be called LK.IMG Ruben thinks it might not have flashed, and reflashing it might unlock it without token.

@sm-xcx I just updated from 16.04 to 24.04 today. The one thing that sticks out to me is that it shows zero signal strength for both VOLTE signal and Wi-Fi signal. As soon as I make a phone call some signal strength appears (but I think it is switching to 2G). Wi-Fi is odd too: it might show zero signal strength, but when I go to Wi-Fi settings and choose my home Wi-Fi network, the signal strength comes back. It is enough for me to wonder if it is using Wi-Fi, so I plugged in an ethernet adapter before accessing the internet. There was also a bit of sluggishness. I noticed it earlier when I went to System Settings, then System Information, then Check for Updates, then tried to return to System Settings, and the settings just froze. However, on subsequent tries it is working normally.

Again... must be a football thing https://explorer.ooni.org/domain/www.ubports.com?since=2026-05-11&until=2026-06-11 https://explorer.ooni.org/domain/repo.ubports.com?since=2026-05-11&until=2026-06-11 https://explorer.ooni.org/domain/repo2.ubports.com?since=2026-05-11&until=2026-06-11

@MrT10001 yes, but trust me qemu static emulation or box64 can go a long way, not to mention you can just compile it on aarch64. if you use NixManager you can probably get all the compilation dependencies and compile natively on device.

@arubislander Hello. I use a ubikey to secure KeePassXC on on my laptop and it would be intersting to have ot working on UT.

OK, found the solution on 'WayDroid on Ubuntu Touch' Telegram group channel Thanks "aleasto" for sharing this solution. Start WayDroid session (by either taping "WayDroid" in launcher or waydroid session start in terminal) When WayDroid session loads, open Terminal on Ubuntu Touch Run the following commands (I think the first prop should be fine, but just in case, I set those 2 props) $ waydroid prop set persist.waydroid.cursor_on_subsurface true $ waydroid prop set persist.waydroid.cursor_force_shm true Restart the WayDroid session to apply prop changes. (By either tapping "Waydroid Stop" then "Waydroid" in launcher or waydroid session stop then waydroid session start in terminal) And from now, hovering mouse cursor to Waydroid window will no longer crashes the Waydroid window. And enabling Show taps on developer options no longer crashes Waydroid window but the taps no longer shows when touches.

Hallo Pparent, thanks for the hint